Product Discovery

Start your project now. Commit to the full build later.

In 2–4 weeks, you get a plan your developers can build from and an estimate you can take to your board.

Start with Discovery →
5 documents in 2–4 weeks

Five documents your build starts from

A development team writes these documents in the first weeks of any project. With Discovery, you have them before you commit the build budget, and they stay yours.

Five documents. Click one to see a preview.

1

Requirements document

What we're building, and in what order. Every vendor prices the same scope, so you can compare quotes.

Preview ↗
2

System and integration map

What you have today, and how it connects. You know which systems to keep and which to replace.

Preview ↗
3

Integration gap map

What your current systems can't do yet. Every gap has a fix, and the estimate prices each one.

Preview ↗
4

Architecture concept

How it will be built. The main technical decisions are made before you pay for code.

Preview ↗
5

Roadmap and estimate

What it will cost, and when it will be ready. You can approve the budget one phase at a time.

Preview ↗
No paperwork for its own sake

Each document exists because a decision in the build depends on it. We agree on the set at kickoff and leave out what your project doesn't need.

The team took full ownership from day one. They defined the requirements, handled the design […] In three months, we delivered the device and the app to our client just before Christmas. The client rated both the functionality and the design 10 out of 10.
Chris Bray
Chris BrayFounder and CEO, Speedvirtual
Read the case →

Built around your starting point

The set of documents is the same. What goes into them depends on your situation.

You already have a product, a CRM and internal tools

Discovery focuses onWhat you have today: your systems and how data moves between them

You walk away withA list of what to keep and what to replace, a gap map, and changes in priority order

What it lets you doFix the right thing first, without breaking what already works

You have an idea for something new

Discovery focuses onThe first version: what goes in and what can wait

You walk away withA scope for version one, an architecture concept, an estimate and a roadmap

What it lets you doTake the project to budget approval with numbers behind it

Case · PriceMDs · US healthcare

PriceMDs' internal platform was half built, and the team had stopped relying on it. We rebuilt it module by module. Today the company runs the whole operation in one system, and the documents that staff once assembled by hand are now generated automatically.

What you have at the end of each week

  1. Week 1

    Scope agreed

    You have: written goals for Discovery and a list of the systems and people it covers.

    How: one kickoff session. You give us access to the product, code and documentation.

  2. Week 1–2

    Current setup mapped

    You have: a first draft of the system map and a list of early findings.

    How: sessions with the people who use your systems every day.

  3. Week 2–3

    Solution defined

    You have: draft requirements and an architecture concept to review. You confirm every scope decision.

    How: our analysis between sessions, then a review with your team.

  4. Week 3–4

    Plan and estimate delivered

    You have: the full set of documents, a walkthrough of the solution and, if you want one, a proposal for the build.

Who's involved From our side, a business analyst and a technical lead. From yours, the product owner and the people who know how things run today.

Useful no matter who builds it

Any team can build from these documents.

If we build it

The full cost of Discovery comes off the build. The people who ran Discovery stay on the project, so development starts without a second onboarding.

If another vendor builds it

You send every vendor the same requirements and get quotes you can compare. Nobody bills you to analyze the project again.

If your own team builds it

Your developers start from requirements in priority order and an agreed architecture. The roadmap shows what to build first.

Coming from a non-technical background myself, I really appreciated how collaborative the team is. They take the time to understand what we're trying to accomplish first, then work alongside us to find the most efficient and effective way to get there.
Annie Delaney
Annie DelaneyCo-Founder & CEO, Rayz Kidz
Read the case →

Format and price

Price
From [$X]
If you build with us
The full cost of Discovery comes off the build
Duration
2–4 weeks, depending on scope and how much already exists
Team
A business analyst and a technical lead
Format
Working sessions + async research and follow-ups
Pricing model
Time & materials, with scope and cost agreed before we start
What's included
Requirements
System and integration map
Gap map
Architecture concept
Roadmap and estimate
  • Working sessions with your team
  • A final walkthrough of the solution and the estimate
  • A proposal for the build, if you want one
  • All five documents, yours to keep
Start with Discovery →

Questions

We always felt they put real effort into understanding our needs and keeping the work moving forward. The impact has been concrete. […] We had very limited visibility in how product is used before. After the implementation we have created live dashboards, automated weekly reports that is now used across teams.
CHAOS Architects OyReal estate analytics, FinlandRead their case →
Isn't this a lot of paperwork before any real work?

It is the real work. A development team has to produce these documents before it writes code, with or without Discovery. Here you get them in 2–4 weeks, and you see the full cost of the build before you commit to it. If you continue with us, the cost of Discovery comes off the build.

What if we already know what we want to build?

Then we have a head start. We start from your idea and from everything you've already written down, and we use it as it is. Discovery adds what a build still needs: detailed requirements, an architecture and an estimate.

What if we already have a product and a team?

That's usually when Discovery is most useful. We start from what exists, and your team stays involved the whole time.

What if Discovery shows we don't need to build anything new?

Then you'll know before you spend the build budget, and you keep the documents. Sometimes the right move is an integration or a process change, and we'll say so.

Can development start right after Discovery?

Yes. The business analyst and the technical lead stay on the project, so the build starts from what we've already learned.

Do we have to build with you afterwards?

No. The documents are yours. You can continue with us, use your own team or take them to another vendor.

What do you need from us?

Access to the product, code, documentation and tools, plus time with the people who know how the business and the systems run today.

Let's plan your Discovery

Tell us where you're starting from. On the first call, we'll agree on what Discovery will cover and what you'll have at the end.

2–4 weeks From [$X] Full cost comes off the build
Leave your details
We reply within one business day.