Every WordPress project an agency takes on starts at the same fork in the road. Start from an existing theme and get to a launch fast, or build a custom theme and control every part of the result. The decision feels small at kickoff and turns out to be one of the most consequential calls on the project, because the agency is the one who maintains the site afterwards. You do not just live with the choice at launch. You live with it on every change request, every plugin update, and every new feature for the life of the client relationship.
Get the choice right and the project is profitable and pleasant to maintain. Get it wrong and you spend the next two years fighting a build that does not fit, eroding the margin you won at the pitch. This is the framework we use, as a white-label partner to agencies, to make that call on each project.
The Real Question Is Not Cost, It Is Fit
The instinct is to frame this as cheap versus expensive. A theme is fast and cheap to start, a custom build is slower and pricier, so use a theme unless the budget is big. That framing leads agencies astray, because the upfront cost is the smallest part of the equation.
The real question is fit, across the whole life of the project. How closely does the client's need match what a theme provides out of the box? The further the requirement sits from what existing themes do well, the more a theme costs you in customisation, workarounds, and maintenance, until at some point the cheap option has quietly become the expensive one. This is the same logic we lay out in WordPress vs custom full-stack: buying an existing system and bending it, versus building one that fits, is a tradeoff that only resolves over time.
So the decision is not what costs less to launch. It is what costs less to own, given how far the project sits from the well-trodden path.
When a Theme Is the Right Call
A theme is the correct, profitable choice more often than purist developers like to admit. Reach for one when the project sits comfortably inside what themes already do well.
That means a fairly standard site. A marketing site, a brochure site, a blog, a small business presence. The structure is conventional, the client's needs are met by what a good theme already provides, and the value you add is design configuration and content, not custom engineering. Forcing a custom build here is over-engineering the client is paying for and you are maintaining for no reason.
It also means a tight budget or timeline where the client genuinely accepts the constraints of a theme. If the work fits and the client is happy within the theme's box, a theme delivers real value quickly and leaves margin in the project.
And it means a client who will not need much beyond launch. If the site is largely static and the change requests will be content, not structure, a clean theme build is easy to maintain and the custom flexibility would never be used.
The key discipline with themes is restraint. A theme used as intended is great. A theme stretched far past its design, with a dozen plugins and heavy code edits layered on to force it somewhere it was never meant to go, is the worst of both worlds. It carries the bloat of a theme and the fragility of a custom build, with none of the cleanliness of either.
When Custom Earns Its Cost
A custom build earns its higher upfront cost when the project sits far enough from the standard path that a theme would have to be fought rather than configured.
That is the case when the client has genuinely specific functionality. Custom post types, bespoke workflows, integrations with other systems, a content model that does not map onto what themes assume. When you would spend the saved time and more bending a theme into shape, building clean is cheaper over the life of the project.
It is the case when the brand demands it. A client for whom looking distinct is part of the value is poorly served by a theme thousands of other sites use. We wrote about the storefront version of this in why so many Shopify stores look the same, and the same dynamic applies to WordPress. Sameness is a real cost for a brand even when it never appears on an invoice.
It is the case when performance matters and the theme route would not get there. Themes carry code for features the site does not use, and that weight has a cost. A lean custom build is faster, and where speed affects conversion or ranking, that difference pays back.
And it is the case when you expect the site to grow. If the client will keep extending it, a clean custom foundation makes every future change easier, where a stretched theme makes each one harder than the last. The custom build is an investment in the maintainability of a relationship you intend to keep.
The Maintenance Question Agencies Forget
The factor agencies most often underweight is who maintains the site, and the answer is almost always the agency. That reframes the whole decision, because you are not optimising for launch day. You are optimising for the two years after it.
A clean build, whether a well-used theme or a tidy custom site, is cheap to maintain. Change requests are quick, updates are safe, and the work stays profitable. A stretched, plugin-heavy, hacked-together build is expensive to maintain regardless of how fast it launched. Every change risks breaking something, every update is a gamble, and the time you spend is time you cannot bill at a rate that makes sense.
This is why the cheap-to-launch option is so often the expensive-to-own one. The cost does not show up at delivery. It shows up slowly, in the margin that drains out of a client relationship that should have been profitable, on a build that was never going to hold.
The Capacity Problem Underneath
There is a reason agencies default to themes even when custom is the right call, and it is rarely a pure technical judgement. It is capacity. Custom WordPress work needs developers the agency may not have, and hiring for it is slow and risky against an unpredictable pipeline. So the agency reaches for a theme because it is what the current team can deliver, not because it is what the project needs.
That is a real constraint, but it should be named as a capacity decision rather than disguised as a technical one. The honest move is to recognise when a project genuinely needs custom and then solve the capacity question, whether by hiring against sustained demand or by using a white-label development partner for the builds that need it. We work through that exact decision in how to scale an agency without hiring. Defaulting to a theme to dodge a capacity gap means delivering the wrong build for the wrong reason, and paying for it in maintenance later.
How to Decide on Each Project
Run each WordPress project through a short test before you quote. How standard is the requirement, and how far does it sit from what themes do well? How much will this client need beyond launch, structurally rather than just content? How much does brand distinctiveness matter to the value? And who will maintain it, with what budget, over what period?
If the project is standard, light on future change, and the client is happy within a theme's box, use a theme and keep it clean. If the project has real custom needs, a brand that demands distinction, performance requirements, or a clear growth path, build custom and treat the upfront cost as an investment in a maintainable relationship. And if the only thing pushing you toward a theme is that you lack the capacity to build custom, solve the capacity problem rather than shipping the wrong build.
The agencies that stay profitable on WordPress are not the ones that always build custom or always use themes. They are the ones that match the approach to the project, every time, with the full life of the build in view.