Storefront strategy
A choice between keeping your theme, going headless and going composable, made for the team and budget you have and costed beyond launch day.
Who this is for
- Merchants whose storefront has become slow or hard to change, and who are unsure whether a new theme or a rebuild is the answer
- Teams on Adobe Commerce weighing Hyvä against a headless rebuild with PWA Studio or ScandiPWA
- Agencies that want a second opinion before committing a client to a frontend stack
What you get
A frontend decision with reasons
A faster current theme, a headless rebuild and a composable setup compared in writing on your catalog, extensions, team skills and budget.
A cost you can plan with
Build, extension compatibility and the years of maintenance after launch estimated in hours.
An API layer that holds up
Missing endpoints, custom attributes and caching gaps in the GraphQL or REST layer found and fixed before the frontend depends on them.
A storefront your team owns
Build, rescue or code-review support until launch, so your developers can maintain it afterwards.
How it works
Week 1
Assess
Week 2
Decide
From week 3
Build
In detail
Going headless means two codebases, an API layer that must cover every feature your store uses, and extensions that often ship without frontend support. Composable goes further and splits parts such as search or checkout into separate services, each with its own contract and its own bill. For many merchants a faster theme delivers most of the speed at a lower cost and risk. For others, such as a content-heavy brand or a team already strong in React, a headless storefront is the right call.
I compare the options on your catalog, extensions, integrations, team skills and traffic. Each one is priced for the build and for the years of maintenance after it. I write down one recommendation and the risks I see. If you already run a headless storefront that has become slow or hard to change, I start from the code and the API layer and fix what blocks you first.
You get a decision with its cost over time, and a storefront your developers can maintain without me.
Most of my work is on Adobe Commerce, where the usual candidates are a Hyvä theme, PWA Studio or ScandiPWA. I have worked with all three. At Guidance I maintained a ScandiPWA headless storefront in production, including the GraphQL work behind it, for an 8-figure-GMV merchant in e-learning and digital content.
The engagement starts with a two-week assessment. If you go ahead, I either lead the build or review the work of your team or agency until launch.
Questions
Do we need a headless storefront?
Not always. For many merchants a faster theme delivers most of the speed at lower cost and risk. For others, such as a content-heavy brand or a team already strong in React, headless is the right call. The assessment compares the options for your store.
How long does the assessment take?
Two weeks. The first covers your theme, extensions, integrations, team skills and the pages that carry revenue. In the second you get a written comparison of the options, with cost, risk and one recommendation.
Do you also build the storefront?
If you go ahead, yes. From week 3 I either lead the build or review the work of your team or agency until launch, in small releases. Your developers can maintain the storefront afterwards without me.
Our headless storefront is already slow. Can you help?
Yes. I start from the code and the API layer and fix what blocks you first. That includes missing endpoints, custom attributes and caching gaps in the GraphQL or REST layer.
Related case study
−50 %Typical page load
Halving page-load times for an 8-figure e-learning store
Read the case study