This is the first question on almost every discovery call: "Should we just use WordPress? Or Shopify? Why would we pay for custom code?"
It's a fair question, and there's no single right answer — there's a right answer for what you're trying to do. The honest version of this post isn't "custom code wins, always." It's a breakdown of what each option is actually good at, where each one runs out of road, and how to tell which situation you're in.
WordPress: fast to launch, expensive to maintain
WordPress powers a huge share of the web for a reason — it's cheap to start, there's a plugin for almost anything, and you don't need an engineer to get a basic site live. If you're running a content-heavy site, a blog, or a simple brochure site on a tight budget, it's a reasonable starting point.
Where it breaks down is later, not on day one. Every plugin you add is a dependency you don't control — when one breaks after a WordPress core update, or two plugins conflict with each other, you're debugging someone else's code, not yours. Security patching becomes a recurring chore, not a one-time setup. And performance has a ceiling: a WordPress site loaded with page builders and plugins struggles to hit the Core Web Vitals scores that both Google and your visitors actually notice. Most "why is my site slow" support tickets we see trace back to plugin bloat, not hosting.
WordPress is a good decision when the site is simple, the budget is tight, and someone non-technical needs to edit content constantly without touching code. It's a worse decision when the site is central to how you make money, or when you know you'll need custom functionality down the line.
Shopify: the right call for straightforward ecommerce
If you're selling physical products and your commerce needs are standard — cart, checkout, inventory, shipping, payments — Shopify is genuinely good. It handles PCI compliance, payment processing, and the parts of ecommerce that are painful to build from scratch, out of the box. For a huge number of stores, that's exactly what's needed, and building that from zero in custom code would be reinventing a wheel that already rolls well.
The friction shows up when your business doesn't fit the standard commerce flow. Custom pricing logic, unusual product configurators, tight integrations with an internal system, or a checkout experience that needs to work differently than Shopify's default — all of that means stacking apps, and app costs add up fast, both in subscription fees and in the transaction fees you pay unless you're on Shopify Payments. Every app is also, again, a dependency with its own update cycle and its own way of breaking.
Shopify is the right call when your commerce needs are standard and you want to launch quickly with minimal engineering overhead. It's the wrong call when your business model doesn't fit inside "add to cart, checkout, ship" — or when the storefront experience itself is meant to be a competitive advantage.
Custom code: full control, at a real cost
Building on a framework like Next.js or React means there's no plugin ecosystem to fight, no page builder bloat, and no functionality ceiling — if it can be built, it can be built the way your business actually works, not the way a template assumes it works. Performance is something you control directly instead of something you hope for after installing a caching plugin. And because there's no dependency graph of third-party plugins, there's less that breaks silently after an update you didn't ask for.
The tradeoff is upfront cost and time. Custom code needs an engineering team, not just a designer with a theme license, and a basic version of "just make it work" takes longer than clicking through a template wizard. It's not the right call for every business, and we'll tell you that on a call — a five-page brochure site for a local business almost never needs a custom-built backend.
It's the right call when the website is core to revenue, when you're going to outgrow what a template offers within the year anyway, or when the way your product or service works doesn't map cleanly onto "blog" or "standard storefront."
How to actually decide
A rough framework that holds up in practice:
Pick WordPress if you need a simple, content-driven site, budget is the primary constraint, and you're comfortable with ongoing plugin maintenance.
Pick Shopify if you're selling standard physical products and your commerce logic doesn't deviate from cart-checkout-ship.
Pick custom code if the site is central to how you make money, your requirements don't fit a template, performance and control matter, or you're already anticipating outgrowing a platform within 12-18 months.
The mistake we see most often isn't picking the "wrong" platform on day one — it's not revisiting the decision once the business has outgrown it. A WordPress site that made sense at 50 monthly visitors doesn't necessarily make sense at 50,000. The right question isn't "which platform is best" in the abstract, it's "which platform is right for where this business is now, and how soon will that change."
If you're not sure which bucket you're in, that's a fifteen-minute conversation, not a guess — get in touch and we'll give you a straight answer, even if that answer is "you don't need custom code yet."