There's a question I get asked at the start of almost every project: "Should we build this on WordPress, or code it from scratch?"
It sounds like a technical question. It isn't.
It's a business question. And the answer depends entirely on what the site needs to do over the next year or two — not on which option sounds more impressive.
Most business owners get pushed toward one answer or the other before anyone asks the right questions. An agency that only builds custom sites will tell you WordPress is limiting. A freelancer who only does WordPress will tell you custom code is a waste of money.
Both are wrong. Neither is right.
Here's the actual framework I use when deciding.
The short answer
If you want a clear starting point:
- WordPress is usually the right choice for a standard business website, a blog, a simple store, or anything where content changes regularly.
- Custom code is usually the right choice when the site needs to behave like an application — with custom logic, complex workflows, or non-standard integrations.
- Most small businesses need WordPress. Most "we need custom code" decisions are based on a misunderstanding of what custom code actually buys you.
The real answer depends on what you're trying to build. Let's unpack it.
Who WordPress is actually for
WordPress powers roughly 40% of the web. That's not because it's trendy — it's because for a large category of websites, it's genuinely the right tool.
WordPress is the right choice when:
You're building a content-driven site. Business websites, portfolios, blogs, service pages, landing pages, and directories all fit here. The structure is standard and the value comes from the content, not the engineering.
You need to update the site yourself. WordPress gives you a real admin panel. You can change text, swap images, add blog posts, and update products without calling a developer. For a business owner, this is enormous.
You want to launch quickly and affordably. A well-built WordPress site can go from brief to live in days, not weeks. Custom code, even with modern tools, takes longer.
Your functionality is standard. Contact forms, basic SEO, analytics, a simple shop — these are solved problems in WordPress. There's no need to reinvent them.
You want a large support ecosystem. If something breaks, there are thousands of developers who can help. That's worth more than people realise.
A small business website built on WordPress is not "the cheap option." It's the right option for a huge percentage of real-world use cases. The mistake isn't choosing WordPress. The mistake is expecting it to do something it wasn't designed for.
Who custom code is actually for
Custom code — using frameworks like Next.js, React, or plain HTML/CSS/JS — is the right choice when the site needs to behave more like software than like a document.
Custom code makes sense when:
The site has real logic. User accounts, dashboards, multi-step processes, custom calculations, membership areas, or anything where the site responds dynamically to the user. This is where custom code shines.
You need custom integrations. If your site needs to talk to a CRM, an ERP, a proprietary internal system, or an API that doesn't have a ready-made plugin, custom code is usually the cleaner path.
Performance is genuinely critical. Custom-coded sites can be extremely lightweight. No plugin overhead, no unused CSS, no bloat. For businesses where page speed directly impacts revenue, this matters.
You want complete design control. A custom build gives you total freedom over layout, interaction, and animation. No theme limitations, no fighting a page builder.
You plan to scale into a product. If the website is really the first version of an application, building on a platform designed for content will eventually hit a ceiling. Custom code avoids that migration later.
Custom code is not "more serious." It's a different tool for a different job.
The honest comparison
Here's how the two options actually compare on the things that matter:
| Feature | WordPress | Custom Code |
|---|---|---|
| Best for | Content sites, blogs, standard business sites, simple stores | Apps, dashboards, complex logic, custom integrations |
| Build time | Days to a few weeks | Weeks to a few months |
| Upfront cost | From $50 for a standard site | From $250 for a custom build |
| Ongoing cost | Hosting ($5–$30/mo), theme/plugin renewals | Hosting (often free on Vercel), minimal renewals |
| Ease of updates | Very easy — admin panel | Depends on setup — may need a developer for changes |
| Design flexibility | High, but constrained by themes | Total control |
| Performance ceiling | Good, if built well | Excellent |
| Scalability | Good for content, limited for apps | Excellent for both |
| Maintenance | Plugin updates, security patches | Less ongoing, but code needs upkeep |
The pattern: WordPress wins on speed, ease, and cost. Custom code wins on flexibility, performance, and scale.
The decision framework
Stop asking "which is better." Ask these five questions instead.
1. Does the site need to do something unusual? If the answer is no — if it's a standard business site with pages, a contact form, and maybe a small shop — WordPress is almost always right. If the answer is yes, custom code starts to make sense.
2. Will the site change often? If content, products, or blog posts will be updated regularly by non-technical people, WordPress's admin panel is a huge advantage. If the site is mostly static, this matters less.
3. What's the real budget — for the build and the first year? WordPress has a low upfront cost but ongoing costs (hosting, premium plugins, maintenance). Custom code has a higher upfront cost but lower ongoing costs. Budget for the full picture, not just the launch price.
4. Who will maintain it? If you want to make changes yourself, WordPress. If you'll always have a developer available, custom code is viable.
5. What happens in two years? This is the biggest one. If you expect the site to grow into an application — with user accounts, real-time features, or complex workflows — building on WordPress now means a rebuild later. If you expect it to stay a website, WordPress is the better long-term choice.
The middle ground nobody talks about
The WordPress vs custom code debate is usually framed as binary. It isn't.
- WordPress with custom development — a bespoke theme and targeted custom code, on top of WordPress. Best of both worlds for many businesses.
- Headless WordPress — WordPress manages the content, and a custom frontend (React, Next.js) displays it. Great for performance-critical sites that still need easy content editing.
- Custom code with a CMS — a custom-built site with a content management layer added. More work upfront, but the flexibility of custom with the ease of a CMS.
You don't have to pick a side. The right answer is often a blend.
The bottom line
WordPress is not the "cheap" option, and custom code is not the "premium" option. They're two tools for two different jobs.
If you're building a standard website — one that presents your business, tells your story, and lets people get in touch or buy — WordPress will do everything you need at a fraction of the cost.
If you're building something that behaves like software — with real logic, real interactions, or real integrations — custom code will save you from a painful rebuild later.
The mistake isn't choosing the wrong tool. It's choosing the tool before you've defined what the project actually needs to do.
If you're unsure which one fits your project, that's exactly the kind of thing worth a short conversation. We build both — so we'll tell you which one makes sense, not which one costs more.
Want to know what each option actually costs? Read our honest pricing breakdown.
