Twenty years. Millions of sites. Zero rewrites. That’s not luck — that’s pragmatism nobody taught us in school.
There are two types of developers. The first picks a stack based on architectural beauty. The second picks based on whether the client will pay rent this month. I’ve been in both camps, and I can tell you: the first type writes more Twitter threads about technology. The second answers to their accountant.
The Math Nobody Says Out Loud
| Parameter | WordPress + Elementor | Next.js + Custom API |
|---|---|---|
| Development time | 40–60 hours | 200–300 hours |
| Project budget | €3,000–5,000 | €15,000–25,000 |
| Time to launch | 1–2 weeks | 2–3 months |
| Who edits copy | The client | Only a developer |
| Landing conversion | identical | identical |
Both sites convert. But one lets you take three more projects in the same timeframe.
I’ve watched solo founders burn two months on a “performant” Next.js build for a landing page. WordPress + Elementor = 8 hours. Both convert. One pays your rent this month.
“Janky” ships features. “Elegant” ships wireframes.
Why We Snob WordPress in the First Place
Yes, the codebase is janky. Yes, PHP has a weird heritage. I’m not going to argue that. But here’s the nuance we keep ignoring: “messy” describes the implementation, not the outcome.
When I started out, I thought WordPress was for non-programmers. That was a mistake that cost me real contracts. Because while I was building the “proper” architecture on a custom stack, the client was waiting. And a client who waits is a client who starts looking at other developers.
The real pattern: technical people optimize for elegance. Clients optimize for ROI.
Fortune 500 companies don’t care about your tech opinions. They care about uptime, plugins, and not hiring a full engineering team to change copy. That’s why enterprises use WordPress — not because they don’t know React exists.
The Psychology of Technical Snobbery
Here’s the uncomfortable truth: we often choose complex stacks not because they’re better for the client, but because they’re more interesting for us. Human nature. Simple is boring.
But here’s what I’ve noticed: developers who moved from “WordPress is for beginners” to “WordPress is my fastest revenue tool” didn’t become worse engineers. They stopped confusing implementation complexity with solution value.
Some of them tripled their income. Not because they got worse at coding. Because they stopped burning 200 billable hours proving they’re smarter than a plugin.
Stop burning 200 billable hours proving you’re smarter than a plugin.
Where WordPress Actually Loses
Honesty matters. WordPress isn’t the answer to everything.
If you need a complex real-time interface, custom business logic with dozens of interconnected entities, or an API serving a mobile app — yes, a different approach is needed. An SPA is justified when your “content site” is actually an application.
But most clients coming to a freelancer or small agency need a website, not a platform. A brochure site. A landing page. A blog with a CMS. A portfolio. And for those jobs, spending 200+ hours is not quality — it’s self-deception.
Your custom API might need a SPA. Your content site doesn’t.
The Practical Takeaway
I’m not saying “always use WordPress.” I’m saying: start with “what does the client actually need,” not “what do I find interesting to build.” If after an honest answer you still need Next.js — great. But if the answer is “a brochure site with a blog,” don’t punish the client for your desire to play with new tech.
What’s the last project you shipped in WordPress that paid better than your “proper” stack?
I write about WordPress, Laravel, and AI in production — real cases, not tutorials. Follow if this resonates.