Product Strategy & Discovery

Many products fail because no one needed them, not because they were badly built. Teams commit to a scope based on the loudest opinion in the room, spend months on it, and find out too late. Discovery replaces that guess with evidence: you talk to users, test ideas cheaply, and decide what to build first with clear reasons you can show to others.

Evidence before commitment

Interviews, data, and prototype tests show whether an idea is worth building before you spend on it.

A scope you can defend

Every item on the roadmap is tied to a user need and a business goal, so priorities are easy to explain.

A plan the whole team shares

Product, design, engineering, and leadership leave with the same picture of what comes first and why.

User research

Interviews, surveys, and observation to understand what people are trying to do and where they get stuck.

Opportunity and market review

A look at alternatives, competitors, and demand, to find where your product can be different.

Prototyping and testing

Clickable prototypes tested with real users, so you learn from them before writing production code.

Product vision and roadmap

A clear statement of what the product is for, and a phased roadmap with the reasons behind the order.

Measures and metrics

A small set of measures that show whether the product is working, and the tracking needed to see them.

Costing and business case

Estimates of build and running costs, and a case for investment that finance and leadership can review.

• Who is this for, and what do they need?

  How we find out

  Interviews with your target users and a review of any data you already have on how they behave today.

  What you get

  A clear description of your users and their top problems, in their words.

• Which idea should we pursue first?

  How we find out

  We score ideas on user value, business value, effort, and risk, and test the riskiest assumption first.

  What you get

  A ranked list with a recommended starting point.

• Will people actually use it?

  How we find out

  A prototype tested with real users, watching what they do rather than only what they say.

  What you get

  Test findings, with what to change and what to keep.

• What goes in the first release?

  How we find out

  We draw the line between what is essential and what can wait, and agree it with you and your team.

  What you get

  A scoped first release and a phased roadmap behind it.

• What will it cost, and what will it return?

  How we find out

  Build and running estimates, with the measures that show whether the product is paying off.

  What you get

  A business case with ranges, not a single optimistic number.

1. Phase 1

   1 week

   Frame

   • Agree goals, constraints, and what you already know
   • List assumptions and rank them by risk
   • Plan who to talk to and what to test

   You receive

   Discovery plan and a ranked list of assumptions.

2. Phase 2

   2 to 3 weeks

   Research

   • Interview users and the people who support them
   • Review data, feedback, and competing products
   • Map the current journey and its pain points

   You receive

   Research findings and a map of the user journey.

3. Phase 3

   2 to 3 weeks

   Prototype and test

   • Design a clickable prototype of the main idea
   • Test with five to eight users and improve it twice
   • Check feasibility with a senior engineer

   You receive

   A tested prototype and a list of what users valued most.

4. Phase 4

   1 week

   Decide

   • Agree the first release and the roadmap behind it
   • Estimate cost and set the measures of success
   • Present the recommendation to your leaders

   You receive

   Product vision, roadmap, estimate, and business case.

How we keep it honest

Evidence, not opinion

Every recommendation points back to something we saw, heard, or measured, and we say so when evidence is thin.

Research done properly

Participants give consent, their details are protected, and recordings are deleted when the work ends.

Your users, your findings

Notes, recordings, and prototypes are handed to you in full when the work is done.

Open to challenge

Assumptions and trade-offs are written down, so anyone on your team can question them.

Willing to say stop

If the evidence says the idea will not work, we tell you, and that is a useful result.

Tools we use

Research

Zoom, Dovetail, UserTesting, Typeform, Maze

Prototyping and design

Figma, FigJam, Framer, Miro

Analytics

PostHog, Amplitude, Mixpanel, Google Analytics, Hotjar

Planning

Linear, Jira, Productboard, Notion, Aha!

Estimation and business case

Spreadsheet models, scenario ranges, and cost breakdowns your finance team can review

Reporting

Short written findings, a roadmap, and a presentation for your leaders

We use whatever your team already uses for planning and feedback, so findings stay with you.