Who it’s for
• Product and engineering leaders • New initiatives or repositioning • Teams debating “what exactly are we building?”
Problems we solve
• Vague problem statements and shifting scope
• Weak value proposition and unclear fit
• Too much solution, not enough evidence
What you get
• Problem statement and target segments/JTBD
• Outcome metrics and acceptance criteria
• Simple product narrative and demo story
• Experiment plan to validate assumptions
Timeline & format
• 2–3 weeks • 4–6 workshops + async reviews • Remote with optional customer interviews
Outcomes
• Clear product brief the team can rally behind
• Evidence‑driven backlog and first‑proof plan
• Fewer reworks and tighter stakeholder alignment
Investment (indicative)
• £8k–£12k fixed, based on scope and research depth
Mini case
B2B SaaS team wrestling with feature creep; we reframed the problem, set three success metrics, and dropped time‑to‑first‑value by 30% after launch.
FAQ
Do we need design/UX ready? No—lo‑fi artefacts are enough at this stage.
What if we already have a roadmap? We stress‑test it against customer jobs and outcomes, then adjust.
Can you run customer calls? Yes—light discovery calls are included where helpful.