WordPress vs Custom Code: Which Should a Small Business Pick?
Past the marketing — when WordPress is the right call, when a custom Next.js build pays off, and how to read between the lines on quotes.
You've got two quotes. One agency wants €5,000 to build it on WordPress. Another wants €25,000 to build it from scratch in Next.js. The price gap is 5x. Why?
Both can be the right answer. Picking the wrong one bites you 1-2 years in — either through speed problems or through maintenance cost.
When WordPress is the right call
WordPress runs 43% of the web for a reason. It makes sense when:
- Someone on your team will publish content regularly. A marketing assistant, you yourself — anyone who can use a CMS panel to add posts, photos, products.
- Budget is tight. A clean corporate site fits in the €2,500-€7,500 range.
- Your year-over-year changes are small. Adding a service, writing blog posts, swapping photos.
- You need the plugin ecosystem. WooCommerce for e-commerce, Yoast for SEO, Contact Form 7 for forms — instant solutions.
To be clear: WordPress isn't bad. Badly-implemented WordPress is bad.
When custom (Next.js / React) actually pays off
You'll feel WordPress's limits if you want any of these:
- Lighthouse 100 / perfect performance. Even tuned WordPress tops out around 80-90. Next.js with static export hits 100/100.
- Complex business logic. Member areas, dashboards, custom calculations, API integrations — in WordPress these become plugin-on-plugin stacks that break at random.
- A platform that'll grow for years. 10 pages today, 200 multilingual pages in two years, eventually with a mobile app — a clean codebase is worth it.
- Premium positioning. If you sell expensive services, customers notice site speed. A boutique hotel losing reservations on a 4-second load can't afford WordPress's overhead.
Hidden cost: WordPress over time
WordPress requires ongoing work:
- Plugin updates — once or twice a month. Skip them and you've got security holes; do them and your theme might break.
- Premium plugin licenses — Elementor Pro €60, Yoast Premium €100, ACF Pro €50 — €200-€500/year on top.
- Hosting overhead — proper WordPress hosting runs €15-50/month.
- Hack risk — out-of-date plugins are doors. We see "site got hacked" tickets at least once a year per client running WordPress.
A statically-deployed Next.js site:
- No plugins = no updates
- Hosting under €5/month
- No database to hack
Year 1, Next.js costs more. By year 3, the totals are even. By year 5, Next.js is cheaper.
Decision matrix
| Your situation | Recommended |
|---|---|
| 5-10 page corporate site, tight budget | WordPress |
| Heavy blog/content publishing | WordPress (or headless WP + Next.js) |
| Boutique hotel, restaurant, premium retail | Next.js |
| Lighthouse 100 / speed is a priority | Next.js |
| 3+ year digital investment plan | Next.js |
| E-commerce, 1000+ orders/month | Shopify or Next.js + Stripe (WooCommerce strains) |
| One-and-done, no ongoing budget | WordPress (live with whatever happens in 5 years) |
Two common mistakes
1. Going cheap on WordPress to "save and upgrade later." Upgrading later means rebuilding from scratch. WP-to-Next.js migration is essentially a new project.
2. Going Next.js for the prestige and having no one to maintain it. Custom code needs a developer for every change. If you don't have an annual development budget, WordPress is more comfortable.
Next step
If you've got two quotes and aren't sure which is the right call for you, send them over. 15-minute call — we'll give you an honest read. Sometimes our answer is "WordPress is fine for this." We're not selling against ourselves on principle.