The question that hides in the question
"Should we use WordPress or build custom?" is really asking: where does this site's complexity live? WordPress wins when complexity lives in content — publishing, structure, commerce on standard rails. Custom wins when complexity lives in workflow — bespoke logic, unusual data, integrations shaped like your business rather than like a template. Most projects answer this in ten honest minutes; the expensive mistakes come from answering it by preference instead.
When WordPress is the right call
- Marketing sites, content-heavy publications, standard commerce — the work WordPress dominates for structural reasons.
- Editing matters: a CMS your team can actually operate is worth real money forever.
- Speed to launch and budget discipline: the ecosystem solves problems custom would bill you to invent.
- SEO surface: the tooling and structure are mature and well-understood.
When custom is the right call
- The product is the site: logins, workflows, data models, calculations — software, not pages.
- Requirements fight every platform: unusual catalogs, complex permissions, multi-step user journeys.
- Performance or security requirements are strict enough that controlling every line is the cheaper road.
- Integrations are deep enough that plugin glue becomes the fragile, unmaintainable kind.
The economics, side by side
| WordPress (done properly) | Custom build | |
|---|---|---|
| Build cost | $3k–25k typical | $15k–80k typical |
| Time to launch | Weeks | Months |
| Running cost | Hosting + maintenance + plugin licenses | Hosting + a developer relationship |
| Change cost | Cheap within the CMS, moderate at the edges | Cheapest where the product lives, priciest at the design edges |
| Hiring pool | Enormous | Smaller, seniorer, pricier |
The pattern nobody says out loud: WordPress costs less to start and more at the extreme edges; custom costs more to start and less where the product actually lives. Budget for where you will be in three years, not where you are at kickoff.
The hybrid most growing businesses actually need
WordPress for the marketing surface, custom for the one workflow that deserves it — a portal, a configurator, a customer area — integrated cleanly. This is frequently the honest answer for businesses told they must choose: the fork is not binary at the system level, only at the feature level.
The disqualifying reasons for each
Do not choose WordPress because it is what the developer knows, and do not choose custom because it sounds more serious. Both are how businesses pay for someone else's comfort. Send the brief — this practice builds both, which is exactly why the recommendation that comes back argues from your requirements instead of a stack preference.