Start your project now.
Commit to the full build later

Product Discovery is the first phase of development. In 2–4 weeks, our business analyst and technical lead work with your team to map how things run today and agree on what to build. If you continue with us, the full cost of Discovery comes off the build.

2–4 weeks From [$X] Starts within 2 weeks of your call
Start with Discovery →

Big projects are hard to start

A big project means a big decision. People on the team see it differently, and nobody can say yet what it will cost. So the budget waits for answers, and the problem stays where it was.

That's a normal place to be when the project matters. Discovery lets you start the work now and decide on the full budget once you have the answers.

See how Discovery works ↓

Discovery is where the build begins

Every project starts by working out how things run today and what needs to change. Discovery is that work, done together with your team. From the first week, we:

  • talk to the people who run your processes and use your systems
  • go through your product, code and tools
  • write requirements and a technical concept
  • make scope decisions with you as findings come up

You get findings and decisions every week, so the project is moving before the final documents are ready.

CRM ERP Ops platform Sheets Portal manual export
System map, week 2 draft. Illustrative.
Case · PriceMDs
For a US healthcare cost-containment company, we sat down one by one with a nurse, a coordinator and a manager. They would use the platform every day, so we built it together with each of them.
Read the case →
Where you start

Two starting points, one first step

AYou're growing

You already have a product, a CRM and internal tools

Your company grew, and your tools grew with it. Now they don't always fit together. For you, starting means sorting out what you have: what to keep and what to build next.

It's for you if
  • important work still happens in spreadsheets and chats
  • data moves between systems by hand
  • one or two people know how everything connects
  • a new tool fixed one thing and added one more system to keep in sync
You getsystem map · priorities · change plan
BYou're building new

You have an idea for something new

You know what you want to build. The project is waiting for a budget decision, and that decision needs answers you don't have yet. For you, starting means getting the project moving and building the case for the budget: scope, concept and estimate.

It's for you if
  • the idea is clear to you and harder to explain to the board or investors
  • you need an estimate you can defend
  • vendor quotes are hard to compare because each one assumes a different scope
  • the project keeps slipping to next quarter
You getscope · concept · estimate
Discovery · 2–4 weeks
Build

Different situations, same first step: a few weeks of work that turn where you are now into a plan you can approve.

Documents you can build from

At the end of Discovery, you have what a development team needs to start building. The exact set depends on the project, and we agree on it at kickoff.

Five documents. Click one to see a preview.

11 / 5

Requirements document (BRD)

Business and technical requirements in priority order, based on how your business and systems work today.

Preview ↗
22 / 5

System and integration map

The systems involved, what each one does, how they connect and where changes are needed.

Key for growing companiesPreview ↗
33 / 5

Integration gap map

Gaps in the current setup and where a third-party or custom integration may be needed.

Key for growing companiesPreview ↗
44 / 5

Solution architecture concept

A high-level view of the proposed components, data flows and integration layers.

Key for new productsPreview ↗
55 / 5

Roadmap and estimate

A phased development plan with budget and timeline, based on the agreed scope.

Key for new productsPreview ↗
We were looking for a partner to take on outsourced software development and AI engineering. What we valued most was the team's responsiveness and genuine willingness to engage throughout. Communication stayed open, and they put real effort into understanding our needs.
CHAOS Architects OyRead their case →

Results from the first week

Discovery is a series of working sessions with your team, and we do the research and analysis between them. The whole cycle takes 2–4 weeks.

  1. Kick off

    Week 1

    We agree on the goals and who we should talk to, and you give us access to the product, code, documentation and tools.

    You get: an agreed scope and a schedule of sessions.
  2. Map how things run today

    Week 1–2

    We go through workflows, systems and integrations with the people who use them every day.

    You get: first findings and a map of how your systems connect.
  3. Define the solution

    Week 2–3

    Our business analyst and technical lead turn the findings into requirements and a technical concept. We confirm every scope decision with you.

    You get: draft requirements and architecture to react to.
  4. Walk through the result

    Week 3–4

    We walk you through the proposed solution and the estimate, including what's still open.

    You get: the full set of documents and, if you want to build with us, a proposal.
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 work today.

Decide on the build when you're ready

Discovery is part of the project. After it, you choose how to continue.

Path 1

Build with us

The full cost of Discovery comes off the build. Development starts from the documents we already have, with the same people who ran Discovery.

Path 2

Take it elsewhere

The documents are yours. Your own team or another vendor can build from them.

Either way, you've worked with the people who would lead your build and seen how they make decisions before signing a larger contract.

Format and price

Duration
2–4 weeks, depending on scope and how much already exists
Start
Within 2 weeks of the first call
Team
A business analyst and a technical lead
Ilya KislenkaGregory Paprauka
Format
Working sessions + async research and follow-ups
Pricing model
Time & materials, with scope and cost agreed before we start
Result
Requirements, technical concept, roadmap and estimate
From [$X]
price of Discovery
2–4 wks
from kickoff to final walkthrough
100% credited
the full cost of Discovery comes off the build if you continue with us
Start with Discovery →

Questions

What if we already have a product and a team?

That's usually when Discovery is most useful. We start from what already exists and help you decide what should change. Your team stays involved the whole time.

What if we already know what we want to build?

That's a good starting point. We check the idea against your current processes and technology and define the scope before development starts. Sometimes the idea survives intact. Sometimes we find a simpler way to get the same result.

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 same business analyst and technical lead stay on the project, so the build starts from what we've already learned, with no second round of onboarding.

Do we have to build with you afterwards?

No. The documentation is yours. You can continue with us, use your internal team or take it to another vendor.

What do you need from us?

Access to the relevant product, code, documentation and tools, plus time with the people who understand how the business and systems work today.

Start here

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 when to start. We can begin within 2 weeks of the call.

See who we've already worked with: Pluto TV, CHAOS Architects, WhiteWater and Rayz Kidz.

Leave your details
We reply within one business day.