This debate usually gets argued as ideology. One side says "premade themes are junk," the other says "custom software is a money trap." Both are wrong. The right question isn't which one is better — it's which one lowers your total cost, in your specific situation.
First, let's define cost correctly
Most decisions get made by looking only at the first invoice. But the real cost is this:
Total cost = Initial build + (Annual maintenance × years) + revenue lost to constraints
That third term is almost never calculated, and it's usually the biggest one. The campaign you couldn't run because the theme wouldn't allow it, the integration you couldn't add, the customer who left because the site was slow — those are costs too.
When a premade theme is the right call
If most of the following apply to you, a premade theme is the smart choice:
- Your business fits a standard mold (a brochure site, a portfolio, a simple blog, a basic catalog).
- Getting live fast matters more than being perfect — you're testing an idea, for example.
- Budget is genuinely tight and your priority is just being visible.
- The site doesn't need to talk to your business processes — no orders, inventory, or ledgers.
- Your traffic is low; performance won't make a marginal difference.
In this case, having custom software built is paying for flexibility you don't need. I regularly tell clients with this profile that they don't need custom software.
When custom software is the right call
If two or more of these signals apply, the math changes:
- Plugin pile-up: the site needs 25+ plugins to stay standing, and every update is a gamble.
- Process mismatch: you've started running your business the way the theme allows. The tail is wagging the dog.
- Integration requirement: you need to connect to an ERP, invoicing, custom shipping, or a dealer system.
- Performance ceiling: the theme is so bloated that optimizing it costs more than rewriting it.
- Scale: you have serious traffic or data volume; every slowdown hits revenue directly.
- Product differentiation: the site itself is your competitive edge — if a competitor can copy it outright, it isn't one.
I go deeper on where that threshold sits and how to migrate gradually in the custom CMS post.
The overlooked third option
Framing this as binary is misleading. In practice, the most cost-effective outcome usually comes from a hybrid approach: take a mature platform for the boring parts (content management, users, sessions) and write only the part that makes your business different from scratch.
That's exactly what I did on the WebWizz project: the front end is fully custom, but I didn't reinvent content management. The team runs their portfolio, blog and incoming leads through their own panel — while the design looks like no theme on the market.
A decision tree
If you want to decide in five minutes, work through these questions in order:
- Will the site exchange data with your business processes? → If yes, lean custom.
- If no: is that likely to change within 12 months? → If it's likely, consider a hybrid.
- If no: is monthly traffic above 20,000 visitors? → If yes, a custom front end for performance.
- If no: is standing out visually from competitors commercially critical? → If yes, custom design on a stock backend.
- If all no: get a premade theme and spend the money on content and advertising instead.
One last warning
Starting with a premade theme and moving to custom later is possible, and it's often the right sequence. But when you do it, protect one thing above all: don't break your URL structure. If addresses change during the migration and you don't set up 301 redirects, you'll reset years of accumulated search rankings overnight. Spend more time on that redirect map than on the new site itself.
A related cost line worth checking before you commit either way: what actually sets the price on a corporate website build.