Product Strategy & Discovery

Know what to build before you invest in delivery.

Situations

When this service helps

Most product failures begin before anyone writes a line of code. Teams commit to delivery while they should still be learning, with their assumptions about users, markets and business models untested.

What it can look like from the inside

  1. Stakeholders disagree on priorities, but the work goes ahead anyway.
  2. The roadmap fills with features that feel urgent but have little evidence behind them.
  3. Budgets are agreed before anyone has said what success looks like, or why this investment matters more than the alternatives.
  4. Assumptions about users, markets and business models are never put to the test.

Who it suits

  • FoundersValidating a new idea.
  • Product leadersPreparing a major initiative.
  • ExecutivesNeeding alignment before committing capital.

It's most valuable when the stakes are high, such as a new product line, a platform modernisation or a pivot, and when internal teams sense misalignment but lack a structured way to resolve it.

Underneath all of this is uncertainty that nobody has made visible. When an organisation can't say what it doesn't yet know, it tends to compensate with confidence, and that confidence is expensive.

Less suited toTeams that already have a validated direction and need execution capacity alone. In those cases, we say so early.

Deliverables

What we deliver

We produce clarity, not volume. A useful outcome might be a focused brief, a prioritised opportunity map or a decision not to build, any of which is worth more than a hundred-page document that nobody reads.

What we do

  1. Understand the business, not the backlog

    We begin with the commercial objective, who the users are and what they're trying to accomplish, and what has been tried before and what it taught you.

  2. Map assumptions explicitly

    Every product direction rests on beliefs about behaviour, willingness to pay, technical feasibility and organisational capacity. We name those beliefs and prioritise them.

  3. Test the assumptions that matter

    We design small experiments to test the beliefs that matter most.

  4. Facilitate difficult conversations

    Strategy isn't a solo activity. We help stakeholders see the same problem and weigh the trade-offs together.

What you leave with

  • A focused brief

    In place of a document that nobody reads.

  • A prioritised opportunity map

  • Tested assumptions and named risks

    Assumptions are tested where testing is possible, and the remaining risks are named rather than hidden.

  • Priorities and success measures

    A view of what to build first, what to defer and why.

  • A practical path forward

    A foundation for delivery that holds up once engineering begins.

  • A shared language for decisions

    Something the team can use for the decisions that come later.

Client work

Discovery in practice

Retreve

Business users needed answers without relying on technical teams, and Retreve made enterprise intelligence accessible through natural conversation.

Extant's role was to turn Retreve's early vision into a product that people could understand long before the platform reached technical maturity.

Industry
Enterprise AI / Business Intelligence
Role
Product Definition & Commercial Readiness
Engagement
  • Product Strategy
  • Product Discovery
  • Brand Strategy
  • Experience Design
  • Product Experience Model™
Read the Retreve case study

Collaboration

How we work together

Strategy isn't a solo activity.

Our part

We start with your business rather than your backlog, and we push back on feature lists that arrive before the problem is understood. Just as firmly, we resist endless analysis that avoids a decision, so discovery has a defined end.

Together

We help stakeholders see the same problem and weigh the trade-offs side by side. You leave with a shared language for the decisions that come later.

Decisions it leads to

Discovery clarifies which assumptions matter most to test, what to build first and what to defer. Sometimes it ends in a decision not to build at all. Either way, you commit with enough confidence and with your eyes open about what remains uncertain.

We optimise for clarity over speed. If a week of discovery prevents three months of building the wrong thing, that's a trade we'll always recommend.

Outcomes

  1. A product direction you can defend.
  2. Alignment on what comes first, and why.
  3. Risks named, not hidden.
  4. A foundation for delivery.

What clients leave with

Clients leave discovery with a product direction they can defend. Stakeholders are aligned on what to build first, what to defer and why, and assumptions have been tested where testing was possible, with the remaining risks named rather than hidden.

What they take away is a foundation for delivery: priorities, success measures and a practical path forward that holds up once engineering begins.

Questions

Practical questions

Is discovery just a workshop and a set of wireframes?

No. Discovery is often rushed through as a workshop, a deck and a set of wireframes before the build begins, but that isn't really discovery. We start by understanding the business, map the assumptions explicitly and design small experiments to test the ones that matter most.

Who is this work for?

It suits founders validating a new idea, product leaders preparing a major initiative and executives who need alignment before committing capital. It's most valuable when the stakes are high and internal teams sense misalignment but lack a structured way to resolve it.

What if we already know what we want to build?

If you already have a validated direction and mainly need execution capacity, this probably isn't the right engagement, and we'll tell you so early.

What do we have at the end?

A clear product direction you can defend, with stakeholders aligned on what to build first and what to defer. You also have a foundation for delivery: priorities, success measures and a practical path forward. Depending on what discovery uncovers, that might take the form of a focused brief or a prioritised opportunity map, or it might be a decision not to build.

Will discovery always lead to a build?

Not necessarily. A decision not to build can be worth more than a hundred-page document that nobody reads. Good discovery has a defined end: enough confidence to commit, with your eyes open about what remains uncertain.

Will you challenge our plans?

Yes. We push back on feature lists that arrive before the problem is understood, and just as firmly on endless analysis that avoids a decision.

Discovery isn't about reducing risk to zero. It's about choosing which risks to take deliberately.

The best product organisations treat discovery as continuous: not a gate before build, but a habit of questioning whether the current direction still deserves investment. We help clients build that habit, rather than delivering a one-off exercise.

Ready to move on this?