Build toward something. Then keep building.
Strategic growth doesn't happen reactively. It happens when a dedicated team, a shared roadmap, and a sprint cadence are all pointed in the same direction — toward revenue outcomes specific to your store.
The Capacity Plan is how stores that are ready to grow actually do it. Not by adding features when they come up. By building systematically, with a picture of where you're going and a team that knows how to get there.
Tell us about your store.
maturity assessment.
Tell us where your store is, what you're building toward, and what's in the way. We come back within one business day with a direct read.
This starts where the Growth Build ends.
The Capacity Plan is built for stores with a solid foundation — either from a Growth Build we completed, or from a store we've assessed and confirmed is ready for strategic execution.
Building features on a rocky foundation doesn't compound. It creates rework. Before a Capacity Plan engagement begins, we assess where your store stands. If the foundation is solid, we move into discovery. If it needs work, we'll tell you — and the right path forward is a Growth Build first.
This isn't gatekeeping. It's the difference between building something that compounds and building something that fights itself.
Explore Growth Build + RoadmapStrategy and execution working together.
Most development engagements separate strategy from execution. You get advice from one source and development from another — and they don't talk. The roadmap is generic. The development is reactive.
The Capacity Plan puts them in the same room. We assess your store, identify the real bottlenecks, and build a roadmap based on what actually moves revenue at your stage. Then we execute it — in sprints, with regular strategy calls, and with the roadmap evolving as you learn what's working.
It's not a retainer for reactive work paid up front. It's a dedicated team moving your store toward specific revenue outcomes, systematically.
A North Star, not a static plan.
The roadmap we build in discovery is not a fixed six-month plan. It's a North Star — a prioritised picture of where the store is going, built from what we know about your category and what the data tells us about your specific situation.
As you build and learn, the priorities shift. Features that seemed critical get deprioritised. Opportunities you didn't see at the start come into view. The roadmap absorbs that. Every strategy call is an opportunity to look at what's working, what's not, and reprioritise accordingly.
This is what makes execution compound: you're not just building features, you're building toward a moving target that gets sharper over time.
- — Discovery assessment of your store's current state and bottlenecks
- — Pattern recognition from stores we've built and grown in your category
- — Data from your own store — what's converting, what's losing customers, where revenue is leaking
- — Your commercial goals and the timeline you're working toward
- — Findings from sprint retrospectives
- — New opportunities identified in strategy calls
- — Changes in your commercial environment — new campaigns, new product lines, seasonal shifts
- — Performance data from features already built
Discovery, sprints, strategy calls, iteration.
The engagement has a clear rhythm. It starts with discovery, moves into sprint-based execution, and iterates continuously through strategy calls.
Discovery Phase
The engagement starts here. We assess your store, identify the real bottlenecks, and build the initial roadmap. This phase is paid — you're not getting strategy for free and then leaving.
- ✓ Assessment of current store state against your commercial goals
- ✓ Identification of the highest-leverage bottlenecks
- ✓ Initial roadmap — prioritised, with reasoning for each item
- ✓ Sprint structure and cadence agreed for the engagement
Sprint Cadence
Work is executed in sprints — typically two weeks for faster-paced stores, monthly for larger clients with more complex work.
| Sprint type | Cadence | Best for |
|---|---|---|
| Two-week | Every 2 weeks | Higher velocity, frequent pivots |
| Monthly | Monthly | Larger clients, complex features |
Strategy Calls
Every sprint ends with a strategy call. We review what was built, look at what the data shows, and reprioritise the roadmap for the next sprint.
- ✓ Keep roadmap priorities aligned with commercial reality
- ✓ Catch opportunities and blockers before they become expensive
- ✓ Maintain shared context between the client and the team
- ✓ Ensure execution is always pointed at the highest-leverage next step
What Gets Built
Everything in the roadmap is a feature or initiative that moves revenue.
- ✓ Custom feature builds to spec
- ✓ App integrations — fully configured, not just installed
- ✓ CRO implementations — layout changes, checkout flow, trust signals
- ✓ Performance improvements — speed, mobile, conversion architecture
- ✓ Data and tracking improvements — so you can see what's actually working
If a sprint reveals that something urgent needs to happen outside the roadmap, we handle it — but the roadmap stays the primary guide. Reactive work doesn't displace strategic execution.
Is this the right engagement?
- ✓ You've completed a Growth Build and you're ready to execute the roadmap systematically
- ✓ You have a store with a solid foundation and you've outgrown tactical support — you want a partner building toward revenue outcomes, not just executing tickets
- ✓ You want a dedicated team that knows your store, your category, and your commercial goals — not a freelancer you have to brief from scratch every time
- ✓ You're ready for a genuine working relationship: regular calls, shared context, and a team that pushes back when something in the roadmap is wrong
- ✕Your store's foundation is not solid — a Growth Build comes first
- ✕You're looking for reactive support without the strategic layer — Store Support is the right engagement
- ✕You're not ready for the dialogue that strategic execution requires — calls, aligned priorities, and shared ownership of the roadmap
Month-to-month. Built for impact.
The Capacity Plan runs month-to-month. There's no fixed six-month commitment from the start.
That said: the goal is to run for three to six months to make the biggest impact possible. A roadmap compounds over time — the second sprint builds on the first, and by sprint four you're building on a fundamentally stronger store than you started with. The shorter the engagement, the less of that compounding you see.
The discovery phase is paid. You're not getting a free strategy session that you can take elsewhere after month one.
After discovery, you're in a monthly sprint cadence. You can exit with notice. But the merchants who see the biggest results are the ones who commit to the process long enough to let it compound.
Where it starts.
The Capacity Plan assumes a solid foundation. Most clients come to it from a Growth Build — where the foundation was built properly and the roadmap was mapped at handover. If you haven't done a Growth Build yet, that's the right starting point.
Explore Growth Build + RoadmapReady to grow intentionally?
Tell us about your store and where you are. We'll assess whether the foundation is ready for a Capacity Plan engagement — and come back within one business day with a direct read.
Tell us about your store