This question comes up in nearly every early conversation with a new client, and the honest answer is “it depends” — but not for the reasons most people expect. The choice between WordPress and a custom build has less to do with which technology is “better” and more to do with who will run the site day to day, and where the business is headed.
What WordPress is actually good at
WordPress runs a large share of the web for a reason: it’s mature, well-documented, and — critically — it lets a non-technical person update content without calling a developer every time. If your business needs to publish blog posts, update a schedule, swap out photos, or edit copy regularly, and you don’t have (or want) an in-house developer, WordPress with a well-built custom theme is often the right call. Cultural institutions, studios, and small service businesses we’ve worked with fall squarely into this category — the value is in giving the client full control after handoff.
The caveat: WordPress is only as good as the theme and plugins behind it. A bloated page-builder theme with a dozen plugins can be just as slow and fragile as people assume “WordPress” always is. A clean, custom-built WordPress theme performs completely differently from a stock template stacked with add-ons.
What a custom build is actually good at
A custom-built site — using something like Astro, Next.js, or a similar modern framework — makes sense when the site needs to do something a CMS template can’t: a genuinely custom interactive tool, tight integration with other software, unusual performance requirements, or a product that is the business, not just its marketing site. If you’re building a SaaS product, an internal tool, or something with real application logic, custom development isn’t a luxury — it’s the only option that actually works.
The tradeoff: without a CMS, content updates typically require a developer, unless a lightweight content layer is built in specifically for that purpose. That’s a fair trade for a product, and often the wrong trade for a site whose entire job is being updated by a marketing team every week.
The real question to ask yourself
Not “which technology is more modern,” but: who is going to update this site six months from now, and how often?
- If the answer is “someone on our team, regularly, without help” — you want a CMS, most often WordPress, built cleanly and without bloat.
- If the answer is “rarely, and mostly by whoever built it” — a custom build gives you more flexibility and typically better performance, without much practical downside.
- If the site itself is the product — the choice isn’t WordPress vs. custom, it’s custom, full stop.
What we tell clients who ask us directly
We build both, and we recommend based on the actual answer to that question above — not based on which one is more interesting to build. A local business that needs to post updates weekly and has no developer on staff gets steered toward a clean WordPress build nearly every time, because the alternative is a site that goes stale the moment we hand it off. A founder building a product gets steered toward a custom build, because a CMS would only get in the way.
The wrong choice in either direction shows up the same way: six months after launch, either the client is paying a developer for every small text change, or they’re stuck with a bloated, slow site because the CMS template promised more flexibility than it could actually deliver cleanly. Getting this one decision right early saves far more time than it costs to think it through upfront.
