Skip to content
OakVertics

Strategy

Product Discovery

A structured, time-boxed engagement that turns an ambition into a validated plan: the problem worth solving, the smallest version that proves it, what it will cost, and the risks that could sink it.
Fixed-scope, fixed-price engagement
2–4wkFixed-scope, fixed-price engagement
Accuracy of the resulting build estimate
±15%Accuracy of the resulting build estimate
Discoveries where we advise not to build
1 in 5Discoveries where we advise not to build

Capabilities

What this actually involves

The specific work, not a list of technologies.

Problem framing

Stakeholder and customer interviews that separate the stated request from the underlying business problem worth funding.

Solution shaping

Concepts pressure-tested against feasibility and cost, narrowed to a scoped MVP with an explicit list of what is deliberately excluded.

Technical feasibility

Architecture options, integration constraints and spikes on the genuinely uncertain parts, so estimates rest on evidence rather than optimism.

Commercial modelling

Build cost, running cost and a business case with the assumptions made visible and challengeable.

Deliverables

What you receive

Everything below transfers to you on completion — code, infrastructure and documentation included.
  • Validated problem statement and success metrics
  • Prioritised feature set with explicit exclusions
  • Clickable prototype of the core journey
  • Technical architecture and integration plan
  • Delivery roadmap with phased milestones
  • Costed estimate and business case

Typical stack

FigmaMiroNotionMazeLinearTechnical spikes

Ideal for

  • Founders preparing to raise or commit capital
  • Enterprises building an internal business case
  • Teams with a large backlog and no agreed sequence

Common questions

What clients ask first

If your question isn't here, ask it directly — you'll get a straight answer.

What if discovery says we should not build it?

That is a successful outcome and it happens in roughly one engagement in five. Learning that for the cost of a discovery is considerably cheaper than learning it after a full build.

Do we have to build with you afterwards?

No. The outputs are yours and are deliberately written so any competent team can execute against them. Many clients take them to competitive tender.

How long does it take?

Two weeks for a focused product, four for something spanning multiple systems or stakeholder groups. It is fixed price and fixed scope.

Related

Often delivered alongside

UI/UX Design

Interfaces that reduce effort and increase completion.

AI Enablement

AI that changes a metric, not a demo that impresses a boardroom.

SaaS Development

Multi-tenant products built to be sold, not just shipped.

Start the conversation

Need product discovery?
Let's talk specifics.

Six questions gets you a recommended package, an indicative timeline and a technology plan. No sales call needed to get a useful answer.

  • Reply within 4 business hours
  • No cost, no obligation
  • NDA on request before you share anything

Two ways to begin

Scope your projectInteractive · about 60 secondsBook a consultation30 minutes with an engineer
newbusiness@oakvertics.com