01 / 06
Product discovery
Customer interviews, support and sales data, product analytics and win–loss evidence read together, so the unmet need is found before a solution is argued for.
Evidence first
Product Strategy & Vision
A roadmap is a list of dates. A strategy says what you are betting on.
Product Strategy & Vision finds the product experiences worth building next, tests them against real demand and real capability, and turns them into a sequence your teams can run with measures already attached.
An illustrative opportunity map: six opportunities plotted by fit with the ambition and strength of evidence, re-scored for retention, expansion and efficiency, with the top three listed.
What it covers · 6 parts
From an opportunity list to a sequence with owners
Opportunities are scored on evidence of demand, feasibility and fit, then sequenced so each release makes the next one cheaper.
02 / 06
Opportunity mapping
Needs, pains and jobs arranged as an opportunity tree, so ideas are judged against the outcome they serve rather than against each other.
Opportunity tree
03 / 06
Product vision & north star
One articulation of where the product is going, the north star metric and the three or four inputs that move it, written so a team can use it to say no.
Vision · north star
04 / 06
Business case
The value case for each bet: who pays, what it displaces, what it costs to build and to run, and the packaging questions it raises.
Value · cost · packaging
05 / 06
Roadmap & sequencing
Now, next and later, ordered by evidence and dependency, with the assumption each bet rests on stated in the open.
Now · next · later
06 / 06
Vision prototype
A high-fidelity prototype or short film of the future product, used to align leadership and test the idea with customers before a line of production code exists.
Concept · alignment
How it runs
Ten weeks, four questions closed
Each phase settles one question. Nothing carries forward that the evidence did not support.
-
Listen Wk 01–03
Customers, lost deals, support tickets, product analytics and the teams closest to the work. Demand evidence gathered before any solution is discussed.
- Research plan
- Interview findings
- Demand evidence
Gate · Have we heard enough to map?
-
Map Wk 03–05
Opportunities structured and sized, the current product assessed against them, and the capability gaps that matter named.
- Opportunity map
- Capability gaps
- Sizing model
Gate · Is every opportunity sized and sourced?
-
Shape Wk 05–08
The leading bets shaped into concepts and a vision prototype, tested with customers and sized with engineering.
- Concepts
- Vision prototype
- Test findings
Gate · Did the leading concepts hold up with customers?
-
Sequence Wk 08–10
A vision, a north star metric and a sequenced roadmap with owners, measures and the assumptions still to be proven.
- Product vision
- North star & inputs
- Sequenced roadmap
Gate · Does every roadmap item trace to evidence?
Timings are typical and shorten when the evidence already exists.
Assumption tracker · what you will see
Every bet rests on assumptions. We track each one to a verdict.
The board the strategy is steered by: each assumption behind a bet, the test that settles it and where it stands today.
Untested 1
Teams will switch from spreadsheets if import takes under a minute
Bet 2 · Desirability
Test: fake-door import, week 6
Testing 2
Finance leads, not IT, choose this tool
Bet 1 · Buyer
6 of 12 interviews done
Usage-based pricing is acceptable below 50 seats
Bet 3 · Viability
Price test live, n = 214
Held 1
Month-end close is the moment of pain
Bet 1 · Problem
11 of 12 interviews, 3 data sources
Broken 1
A mobile app is needed at launch
Bet 4 · Scope
2% of sessions on mobile · bet dropped
What you keep
A strategy that fits on one page. With the evidence under it.
The north star, the bets and the roadmap, each traced to the research that justified it and kept where your teams plan.
/handover/02-strategy/
Product Strategy & Vision
- Product visionOne page · Deck
- Opportunity map & evidence packBoard · Sheet
- North star metric & input treeSheet · Dashboard
- Business case per betModel · Sheet
- Sequenced roadmap · now / next / laterRoadmap · Board
- Vision prototypeFigma · film
- Assumption & experiment backlogSheet
/handover/README
In every handover
- Decision record, with evidence linksDoc
- Assumption tracker, final statesSheet
- Research consent & retention logSheet
- Walkthrough session, recordedVideo
What changes
A roadmap people can explain. Three measures that prove it.
Strategy works when leaders say the same thing unprompted and every item on the roadmap can point to its reason. Baseline, target and instrument are agreed in week one.
-
Outcome 01
A reason for every item
Each roadmap entry traces back to an opportunity and the evidence behind it, so priority calls stop being a contest of seniority.
-
Outcome 02
Alignment that survives the quarter
One vision and one metric, understood the same way by product, design, engineering and the board.
-
Outcome 03
Bets sized before they are made
Cost, effort and the assumption most likely to break, all named before a team is assigned.
-
01 Roadmap items traced to evidenceItems linked to a sourced opportunity92%from 35%target 90%
-
02 Leaders who state the same north starUnprompted survey, before and after84%from 25%target 80%
-
03 Bets with a sized cost and a testRoadmap items with effort range and kill criterion86%from 10%target 80%
The stack
Evidence in, roadmap out. Analytics and planning tools you own.
The research, analytics and planning tools we use to size opportunities and hand the roadmap to delivery. Technologies we work with, not partnerships.
- Figma
- Miro
- Notion
- Confluence
- Jira
- Linear
- PostHog
- Mixpanel
- Google Analytics
- Looker
- HubSpot
- Salesforce
Frameworks we build to
Ambition checked against obligation. Before it reaches the roadmap.
Frameworks each bet is checked against while it is still cheap to change. Frameworks we build to, not certifications we hold.
-
WCAG 2.2 AAWeb Content Accessibility Guidelines
Perceivable, operable, understandable and robust content, including 2.2 criteria such as focus not obscured, target size and accessible authentication.
How we apply itContrast, focus order and target size checked in the design file, then keyboard and screen-reader passes on every key journey before sign-off.
-
GDPRGeneral Data Protection Regulation (EU) 2016/679
Lawful basis, data-subject rights, data protection by design and by default, breach notification and DPIAs for high-risk processing.
How we apply itResearch participants give recorded, specific consent; recordings and notes have a retention date and are deleted on it.
-
DPDP Act 2023Digital Personal Data Protection Act, 2023
Notice and consent, duties of data fiduciaries, rights of data principals, breach intimation and added duties for significant data fiduciaries, with the DPDP Rules.
How we apply itConsent notices for India-based participants and users, with data-principal requests answerable from the research log.
-
ISO 9001:2015Quality management systems
Requirements for a quality management system built on process control, risk-based thinking and continual improvement.
How we apply itEvery stage ends at a written gate with an owner, and design QA against the approved source before anything is called done.
Services & packages
Decide what to build next. Then decide the order.
Commission a single piece of research, a vision your leadership can agree on, or the full strategy and sequenced roadmap. Every engagement ends with decisions and measures, not a list of features.
- Categories
- 04
- Services
- 15
- Packages
- 04
How to buy
- 01Pick services. Enquire about one, or add several to a brief.
- 02Choose how to engage. A sprint, a fixed project or an ongoing team.
- 03Send the brief. We reply within one working day.
Start a project
Ways to engage. Same team, same standard.
Three ways in, from a two-minute question to a formal RFQ. Each is read in full by the lead for the work, and anything already in your brief goes with it.
Or book a thirty-minute call-
01
For a first conversation, a press request, or anything that does not need a scope yet.
You get A reply from a lead, not a sales queue
-
02Most useful
Goals, audiences, a budget band and timing. Enough for us to come back with a shape, not only questions.
You get Options and a first scope after one call
-
03
Your pack, your deadlines, and the procurement and security rules the work must meet.
You get Receipt confirmed and a named bid lead
How it is priced
Each package shows how it is priced. Every engagement starts with a written scope and a quote agreed before work begins.
Opens a project brief with this package chosen.
-
In your brief
- Typical length
- 1–3 weeks
- Pricing
- Fixed fee
-
In your brief
- Typical length
- 4–12 weeks
- Pricing
- Fixed price
-
In your brief
- Typical length
- Ongoing · 6-month minimum
- Pricing
- Monthly fee
-
In your brief
- Typical length
- 6–18 months
- Pricing
- Programme fee · by statement of work
Compare what each package includes
| Package | Every engagement includes | Best for |
|---|---|---|
| SprintOne fixed question, answered in one to three weeks. |
|
Discovery, a diagnostic, a prototype or a decision you need to make soon |
| ProjectA defined scope, delivered for a fixed price. |
|
Work you can describe up front: an identity, a system, a set of tools |
| RetainerReserved monthly capacity to run, improve and extend what we built. |
|
Brands and products after launch that need a steady team without hiring one |
| EnterpriseA multi-workstream programme with governance, a dedicated team and SLAs. |
|
Large organisations running change across markets, portfolios or business units |
Questions
Asked before the vision workshop.
Anything else goes straight to the people who would do the work.
Ask a questionQ01How is this different from writing a roadmap?
A roadmap says what and when. A strategy says why those and not the alternatives, what has to be true for each to work, and what you will stop doing. We produce both, in that order.
Q02Do you work from our data or gather new research?
Both. Analytics, support tickets, CRM and win–loss data show what is happening; interviews show why. Neither on its own justifies a year of engineering.
Q03What is a north star metric, and can we have more than one?
A north star is the single measure that best proxies the value customers get, with three or four input metrics a team can actually move. One per product is the point of it. A second is usually a sign the product is really two.
Q04Who owns the roadmap afterwards?
Your product leadership. We write it with them and hand over the model, the evidence and the assumption backlog. A standing quarterly review can be agreed if it helps the plan stay current.
Q05Can this run alongside an existing delivery team?
Yes. Strategy work runs in parallel with delivery on a short feedback loop, so what the team learns shipping this quarter reshapes what is planned for the next.
Keep going
A strategy needs somewhere to land. These turn it into product.
Consulting settles how to build it; Experience Design turns the first bet into something people can test.
01 · Pairs well
Before anyone commits
Design Consulting & Solutioning
Turning new capabilities into a technology strategy teams can actually ship.
Explore Consulting
03 · Pairs well
Designed, tested, built
Experience Design & Development
Fast, rigorous iterations that shape and validate an experience before big bets get made.
Explore Experience
The discipline
From signal to shipped
Product & Experience Design
All five capabilities, the loop they share and how an engagement moves through it.
Back to the overview
Let’s build what happens next.
Tell us what you’re building. We’ll answer straight.
Three ways to start
Every engagement starts with a written scope and a quote agreed before work begins.
Choose one of the three ways above