Decision memo
A short written record of what was decided, what was rejected and why — the document your team can take to a board, investor or co-founder.
Product Strategy Sprint
Two weeks to a product decision you can defend.
A fixed-scope engagement for founders and product teams who need to decide what to build, what to cut and what ships first — before the next build budget is committed.
Fixed fee $4,500–$7,500. Scope agreed before kickoff.
Not sure yet? Take the 2-minute strategy scorecard →10 working days
One decision memo
US & UK teams
Build optional
What you leave with
Six artefacts, one decision.
The sprint is not a workshop series. It ends with a written decision and a plan your team can execute without translating it first.
Problem and ICP statement
The job the product does, who has it, and the evidence that the buyer would pay for a better answer.
Opportunity map
The realistic options ranked against evidence, effort and commercial upside, with the ones to stop named explicitly.
First-release boundary
What the first release contains, what waits, and the difference between a demo, an MVP and a product someone will buy.
Sequenced roadmap
A delivery order tied to dependencies and outcomes, with the assumptions that would change the order made visible.
Metrics and handoff
Two or three success measures, plus a working session with your team so the plan survives contact with execution.
Two weeks
Four decisions, in a fixed order.
The schedule is deliberately tight. A shorter decision cycle is usually a better decision, because it forces the trade-offs into the room instead of parking them for later.
Days 1–3
Frame
Stakeholder sessions and customer evidence. We map the constraint, the commercial pressure and what has already been tried.
Days 4–6
Decide
We test the problem, audience and value against evidence, then narrow the options to the ones worth building.
Days 7–9
Sequence
We define the first-release boundary, sequence the roadmap and name the assumptions the plan depends on.
Day 10
Hand off
We walk your team through the decision memo, the roadmap and the success metrics. Questions are answered live.
Fit
A good sprint starts with the right team.
The sprint works when someone on your side can make a decision and the team is willing to change the plan when the evidence says so.
A strong fit
- Founders deciding what the first release should contain.
- Funded teams preparing the next release or a board update.
- Product leaders inheriting a build and needing a defensible plan.
- Teams whose roadmap keeps changing without a decision underneath it.
Probably not a fit
- Teams that only need design production or engineering capacity.
- Products that need a visual refresh rather than a direction.
- Businesses looking for a slide deck with no decision attached.
- Teams that have already committed the build and cannot change scope.
Cost
A fixed fee, agreed before the work starts.
Strategy work should not be priced by the hour, because the value is in the decision rather than the time spent. The sprint is scoped and quoted after a fit call, then held for the engagement.
Read the digital product strategy guideProduct Strategy Sprint
$4,500–$7,500
Fixed fee for two weeks. One sprint at a time.
Included
- Stakeholder and customer interviews
- Decision memo
- First-release boundary
- Sequenced roadmap
- Success metrics
- Team handoff session
Not included
- Design production
- Engineering or build work
- Ongoing advisory retainer
- Paid user research recruitment
After the sprint
The plan does not require us.
There are three honest outcomes. All three are useful, and the decision memo is written so any of them can be executed.
Build with Zyvor
The plan becomes the brief for design and engineering. You keep the same decision record from strategy through launch.
Build in-house
Your team takes the memo and roadmap and runs delivery. The handoff is designed so this works without us.
Stop and save the budget
If the evidence does not support the build, the honest outcome is to stop. That is a valid result of the sprint.
Not sure where to start?
Run a free product diagnosis.
Zyvor Intelligence helps founders turn a SaaS or AI business problem into a clearer read on the root causes and what to fix first. It is free to start and takes a few minutes.
Questions
What to expect before you book.
How is this different from a discovery phase?
Discovery usually produces research. The sprint produces a decision: what the first release contains, what waits and what the roadmap is. Research is an input; the decision memo, first-release boundary and roadmap are the output.
What do you need from us during the two weeks?
A founder or product owner who can make decisions, access to customer evidence, and two working sessions. We handle the analysis, synthesis and writing. You are not expected to produce documents for us.
Do you work remotely?
Yes. Sessions run over video with overlap for US and UK teams. Most engagements never need an in-person workshop, and the written output is designed for distributed teams.
Can you also build the product afterwards?
Yes, but the sprint does not depend on it. You can build with Zyvor, build in-house from the plan, or stop. The decision memo is written so any of those paths can be executed without us.
What if we need more than two weeks?
Products with several stakeholder groups, existing customers and a larger surface usually take three to four weeks. We scope that after a fit call rather than stretching the fixed sprint.
What does the fixed fee include?
Two weeks of work, stakeholder and customer interviews, the decision memo, first-release boundary, sequenced roadmap, success metrics and a handoff session. Design production, engineering and ongoing advisory are separate.
Prefer to send a note first? Contact Zyvor.
Start here
Bring the product and the decision you are trying to make.
A 20-minute fit call is enough to tell whether the sprint is the right next step. If it is not, we will say so and point you somewhere better.