WordPress for large organizations

Large WordPress sites, rebuilt so your staff can run them.

We redesign, rebuild, and migrate WordPress sites for companies, public agencies, colleges, and nonprofits: thousands of pages, dozens of editors, and real accessibility and security requirements. Senior US engineers, from the first audit to the years after launch.

When it is time

The site works. Running it does not.

Most large sites are not broken. They are slow to change, hard to keep accessible, and risky to update. These are the usual reasons organizations call us.

An accessibility deadline

ADA Title II, Section 508, or an internal policy now requires WCAG 2.1 AA, and the current theme was never built for it.

Editors keep breaking pages

A page builder lets anyone change anything, so layouts drift, headings break, and accessibility erodes with every edit.

Updates are a gamble

Core and plugin updates get skipped because the last major upgrade broke permissions, forms, or layout.

Too many sites

Departments, programs, and campaigns each grew their own site, with different themes, logins, and owners.

An older platform

Content is stuck in an older CMS or a hosted site builder that the organization has outgrown.

The vendor holds the keys

Hosting, plugin licenses, and the domain sit in someone else’s account, and nobody is sure what happens if you leave.

What we do

The whole site, not just the homepage.

One accountable team for design, build, migration, accessibility, hosting, and support. Take all of it, or only the parts you need.

01

Redesign and information architecture

Navigation built from analytics, search logs, and the tasks people actually come to do. Wireframes, a clickable prototype, and usability testing with real visitors before visual design is final.

02

A custom theme on locked block templates

Each template fixes the layout and exposes only the fields an editor should change. Staff get visual editing with preview, and cannot break the design or the accessibility by accident.

03

Content migration at scale

Every page, post, document, and form is inventoried and classified: migrate, consolidate, rewrite, archive, or retire. Scripted migration with field mapping, manual work where it matters, and sign-off by each content owner.

04

Accessibility you can show

Built to WCAG 2.2 AA. Automated checks on every template, then manual testing with keyboard, NVDA, and VoiceOver at 200% and 400% zoom. An Accessibility Conformance Report before acceptance, and no overlay widgets.

05

Documents and plain language

PDF remediation into tagged, accessible documents, or conversion to web pages. Plain-language rewriting where pages have grown dense, always reviewed by a person.

06

Hosting, performance, and recovery

Load-balanced hosting behind a CDN and web application firewall, separate development, test, and production environments, encrypted off-site backups, and a restore that is actually tested. We can also work on hosting you already have.

07

Security and update discipline

Single sign-on with MFA, least-privilege roles, security headers, activity logging, and a small plugin footprint. Updates go through a test environment with visual and accessibility checks before they reach production.

08

Integrations

Single sign-on through Microsoft Entra ID or another SAML or OIDC provider, CRM and form systems, event calendars, maps, dashboards, payments, and the catalogs and directories that already exist elsewhere.

09

Search, forms, and languages

Site search with pinned results, accessible forms migrated from what you have, and translation, from automated machine translation to fully managed multilingual content.

10

Governance and editorial workflow

Department roles, review and approval steps, revisions that stay in draft until approved, and an owner and review date for every page, so stale content is reported, not discovered.

11

SEO and analytics continuity

Redirect maps built from your highest-traffic pages, and analytics, Search Console, and tag management carried over so reporting has no gap at launch.

12

Training and support after launch

Role-based training that is recorded, editor and administrator guides, a warranty period, and a support plan sized to what you actually need, with monthly reports.

Accessibility

Accessible on launch day, and still accessible a year later.

Most sites pass an audit at launch and drift after that. Every edit, upload, and new page is a chance to break something. So we build accessibility into the templates, put a checker inside the editor, and scan the site on a schedule after launch.

Automated tools find only part of the problems. The rest takes a person with a keyboard and a screen reader working through real tasks, which is how we test.

How a project runs

Seven steps, each signed off before the next.

Weekly written status, a decision log, and a risk register throughout. Changes to scope are written down and approved, not absorbed.

  1. 01

    Measure

    We crawl and count the current site before we quote: pages, documents, forms, plugins, integrations, editors, and an accessibility baseline.

  2. 02

    Plan the structure

    Content inventory, sitemap, wireframes, and a clickable prototype tested with real users.

  3. 03

    Design

    Visual design built on your brand and on accessible components from the start.

  4. 04

    Build

    Theme, templates, integrations, and workflow, delivered in short cycles with working demos.

  5. 05

    Migrate

    Scripted and manual migration, redirect maps, and automated checks on page counts, links, and images.

  6. 06

    Test and train

    Accessibility, browsers, performance, security, and a full restore test. Editors are trained on the real site.

  7. 07

    Launch and support

    A go or no-go review, DNS cutover, two weeks of close monitoring, then warranty and ongoing support.

No lock-in

Everything is in your name.

If you ever change vendors, including away from us, nothing is lost and nothing has to be pried loose.

Accounts and licenses

Hosting, domain, CDN, and plugin licenses are registered to your organization.

Code and content

You own the theme, the custom code, the content, and the data, in a repository you control.

Standard WordPress

No proprietary framework. Any competent WordPress developer could maintain the site.

Documented handover

Editor and administrator guides, recorded training, and help moving to another provider if you choose to.

Who you work with

You talk with the people who do the work.

The first call is with the people who will open the repo. No salesperson in the middle. Nothing sent overseas.

Thirty years building software. Twenty of them running this company in Las Vegas. The job is not to sell you the biggest project. Sometimes the honest answer is you do not need one.

See how the work is run →

Questions before a WordPress project

Should we rebuild our WordPress site or fix the one we have?

It depends on the theme, the plugins, and how the content is structured. We look first. Sometimes a new theme on the existing content is enough. Sometimes the content model is the problem, and a rebuild is cheaper than continuing to patch it. We will tell you which, and why.

Can you move us to WordPress from another CMS or a site builder?

Yes. We export through the platform’s API where one exists, crawl the site to catch everything else, and map each content type to its WordPress equivalent. Nothing is carried forward just because it exists.

Do you use page builders?

No. Page builders make it easy to change anything, which is the problem on a site with many editors. We build a custom theme on the WordPress block editor with locked templates, so editors keep visual editing without the ability to break the layout.

Do we have to use your hosting?

No. We can host and run the site, or work on the hosting you already have. Either way, the accounts, domain, and plugin licenses are in your organization’s name.

Who owns the site when it is finished?

You do: the theme, the custom code, the content, and the data. The code is standard WordPress, documented, and kept in a repository you control, so any competent WordPress developer could maintain it.

How is the project priced?

At a fixed price, after we have measured the current site. The size of the content, the number of integrations, and the accessibility work on documents drive the cost more than page design does. Ongoing support is priced separately and sized to what you need.

Discuss a WordPress site

Send us the address. We will tell you what we see, what we would change first, and what it would take. The first conversation is free.