A Shopify Plus retainer with a roadmap, shipped every month.
When does a Shopify brand need Core?
- Launch is done, and the list of things you want next keeps growing.
- You have no in-house engineers and do not want to hire a team.
- Your current support agency fixes things but never moves the store forward.
- Improvements ship in bursts, then stall while a new vendor is briefed.
- Peak trading is coming, and changes need a plan and a freeze.
How does a month of Core run?
- 01Agree the roadmapA prioritised list of improvements, owned together and kept in your client portal.
- 02Plan the monthWe choose what ships next against the capacity reserved for you.
- 03Build and previewWork lands on a preview for you to see before it goes live.
- 04Approve and releaseYou approve in the client portal; we release and check it in production.
- 05Report and resetWhat shipped, what it changed and what moves up the list next.
A roadmap with a place in every month.
- Reserved senior engineering capacity, not a bank of hours
- A prioritised roadmap, reviewed with you
- Releases every month, previewed before they go live
- Requests, approvals and deliverables in your client portal
- A performance budget the roadmap is held to
- A code freeze and release plan for peak trading
What usually goes wrong.
- Treating the retainer as a bank of hours. Hours reward busyness; a roadmap rewards what ships.
- Shipping features nobody measured first. Agree what each change should improve before building it.
- Letting every request jump the queue. Priorities change at planning, not by whoever asks last.
- Releasing big changes just before peak trading. Freeze, test and launch earlier; peak is not a test.
Launch pages and accounts, now in production.
For a clinical skincare brand’s consumer store we redesigned the product page around the buy box, built launch pages as reorderable theme sections, and run one theme across five stores, with third-party scripts behind one consent-gated loader.
See case studiesWhat teams ask about a Shopify Plus retainer.
How is Core different from Care?
Care keeps a stable store current: upkeep, API versions and fixes. Core is built around a standing roadmap of improvements, with reserved senior capacity, planned with you and shipped every month. Choose Core when you want the store to move, not just hold.
How many hours do we get each month?
We do not sell hours. Core reserves senior capacity for your roadmap, and we agree what ships each month against it. You pay a fixed fee for a defined scope, with a six-month minimum, and changes outside it are quoted in writing.
We already have a support agency. Why switch?
Switch only if something is missing. Core is built around a roadmap: what the store should do next, in what order and why. If your current agency keeps things running but nothing moves forward, that is the gap Core is for.
Where do requests and approvals happen?
In your client portal. Requests, deliverables and approvals sit in one place, so you can see what is planned, what is ready for you to review and what has shipped, without chasing anyone over email.
What happens before Black Friday?
We plan peak trading into the roadmap: what must ship early, what waits until after, and when changes stop. A code freeze and a release plan are agreed with you, so peak is not the moment anything is tested for the first time.
Next steps
Related programs- Start hereTalk about a partnershipA short call to agree the tier, the first priorities and how we report.
- Engineering partnershipEmbeddedEmbedded is the deepest tier of our Engineering Partnership.
- Shopify Plus developmentPerformance & Conversion SprintA fixed-fee sprint for Shopify Plus stores that are slow or run too many apps.
Start here
Bring the list you want shipped.
Tell us what is live and what you want next. We’ll say whether Core fits, or whether a three-week Architecture Review should come first.