Platform Strategy: Shopify vs Headless

The platform decision most brands get wrong

The headless conversation in DTC has become a religion. One camp insists that any brand past ten million in revenue must be on a composable stack. The other insists that Shopify theme development can take you to a hundred million and anything else is consultant driven theater. Both are wrong in the same way. They answer a business question with an architectural opinion.

The right way to make a platform decision is to treat it like any other capital allocation choice. A replatform is a multi hundred thousand dollar project with a six to twelve month execution window and ongoing operating cost that will outlive the founding team. It should be approved on the basis of a business case that shows revenue or margin uplift larger than the total cost of ownership, not on the basis of a blog post the head of engineering read last week. Most brands have never built that business case. They have built a vibe.

The second mistake is treating the decision as binary. Shopify versus headless is not a single choice. There is Shopify theme, Shopify theme with an advanced section based system, Shopify Hydrogen, Next.js on Shopify Storefront API, Next.js on a composable stack with a separate commerce engine, and a dozen hybrid variations. Each has a different cost curve, a different ceiling, and a different failure mode. Treating the decision as two options forces teams to argue about the wrong thing.

Our approach

We run platform strategy as a three to five week engagement. The output is a decision document, not a roadmap. The document recommends a platform direction, shows the supporting numbers, and lays out the next ninety days of work regardless of the direction chosen.

• Step one, current state audit. We audit the existing stack. Theme architecture, app stack, performance, content operations, integration health, engineering throughput, and backlog of blocked work. We measure how much of your current pain is platform and how much is execution.
• Step two, growth plan alignment. We read the twelve to eighteen month growth plan. International expansion, channel expansion, personalization ambitions, content velocity, bundle and subscription plans. We map each plan item against platform capability.
• Step three, option definition. We define three to four concrete platform options. Usually these are stay and optimize, go hybrid, go Hydrogen, go Next.js composable. Each option gets a scope, a cost estimate, and a timeline.
• Step four, total cost of ownership model. We build a three year TCO model for each option. Platform fees, build cost, ongoing engineering, app and CMS licenses, infrastructure, and the opportunity cost of slower iteration.
• Step five, recommendation. We recommend a direction with the numbers behind it. We also recommend the ninety day next steps, which are almost always platform agnostic. Fix the obvious performance issues, clean up the content model, reduce the app stack, whether or not you replatform.

What you get

• A current state audit document with named platform pain points and their root causes.
• A growth plan to platform capability map that shows which planned initiatives are blocked by the current stack and which are not.
• Three to four concrete platform options with scopes, costs, and timelines.
• A three year total cost of ownership model for each option, including opportunity cost of iteration speed.
• A recommended direction with the business case behind it.
• A ninety day platform agnostic plan that starts work the Monday after handover.

Timeline

The engagement runs three to five weeks.

• Week one, audit and interviews. We audit the stack and interview engineering, ops, and marketing leads.
• Week two, option definition and growth plan alignment. We draft the platform options and map them to the growth plan.
• Weeks three and four, TCO modeling and recommendation. We build the cost model and draft the recommendation.
• Week five, handover. We run a working session with leadership and hand over the decision document.

Mini case anatomy

A composite. A twenty eight million dollar beauty brand, four years old, on a heavily customized Shopify theme with thirty eight installed apps. The founder had been told by two different agencies that the brand needed to go headless. The engineering lead was skeptical. The CFO was alarmed by the six figure quote.

The audit found that the theme was running at a Core Web Vitals LCP of three point eight seconds. The immediate assumption was that headless would fix it. The data said otherwise. Twenty two of the thirty eight apps were injecting render blocking scripts. Eight of them were unused or duplicated. The hero image on the homepage was a six megabyte uncompressed asset. A two week app audit and image optimization pass took LCP to one point nine seconds without any platform change. The performance argument for headless collapsed.

The real argument for headless was different. The brand was planning a content heavy expansion into education and ingredient storytelling. The theme's content model could not support structured ingredient data, and the editorial team was blocked on every new content format. A hybrid approach was recommended. The PDP and the ingredient library would move to Next.js with a headless CMS, the rest of the site and checkout would stay on Shopify. The TCO model showed the hybrid cost paying back in fourteen months through reduced content production time and higher PDP conversion.

The brand shipped the hybrid eight months later. The full replatform the other agencies had proposed would have taken fourteen months and cost two point six times as much for a smaller business case. The decision document is still in the shared drive, referenced every time a new agency pitches a replatform.

FAQs

Context to read alongside. The ecommerce strategy hub covers how platform strategy interacts with the rest of the strategy work. If the recommendation points at headless, the headless development hub and the Hydrogen build and Next.js commerce pages cover execution. Operators making this decision often read headless Shopify versus Liquid and the Shopify speed optimization playbook. If the decision is to stay on Shopify and optimize, Shopify development is the next step. For alternate platform comparisons, see Shopify versus BigCommerce.