Skip to main content
Labs // Estimator

Sketch your stack. See the questions that matter.

Choose the areas your project touches, like ERP, mobile, AI, and integrations, and see the dependencies and discovery questions that decide how big it really is.

Planning workbench // No delivery estimate

Sketch the system surface area

Select the parts involved to create a discussion map. This tool surfaces dependencies and discovery questions; it does not predict project duration or cost.

What areas are in scope?

Current sketch

2 system areas

2 integrations · 1 data source

Questions to take into discovery

  • Which system owns each important business record?
  • How should retries, duplicate events, and failures be reconciled?
  • What does a successful first release need to prove?

Questions, not quotes

Timelines depend on data quality, integrations, and how quickly decisions are made. The estimator deliberately gives no timeline or cost; it shows what needs answering first.

How the questions are chosen

Every map also asks what a successful first release needs to prove.

When you selectYou'll be asked
ERP or data migrationWhich system owns each important business record?
Mobile or offline workWhat must users be able to do without connectivity?
AI or documentsWhich results require review before they affect a business record?
Cloud or infrastructureWho owns backup checks, alerts, and recovery steps?
One or more integrationsHow should retries, duplicate events, and failures be reconciled?
More than one data sourceHow will data definitions and quality be aligned across sources?

Why these questions decide the size of a project

Most project overruns come from a small set of unanswered questions: two systems both believing they own the customer record, an offline requirement discovered late, an AI feature with no agreed review step, or integrations that fail silently. Each one can add weeks once a project is underway, and each one is cheap to answer at the start.

Use the map as an agenda. Bring the questions to your team, note who can answer each one, and you will walk into any discovery conversation, with us or anyone else, already ahead.

Using the map

  1. Step 01

    Select the areas

    Tick every area the project touches, even the ones that feel minor.

  2. Step 02

    Count integrations and sources

    Include spreadsheets and manual exports; they count too.

  3. Step 03

    Answer what you can

    Write down answers and owners for each question.

  4. Step 04

    Bring the rest to discovery

    Unanswered questions become the discovery agenda.

What usually changes the size of a project

Two projects that look identical on a feature list can differ several times over in effort. The difference is usually in the parts that don't show in a demo: how messy the existing data is, how many systems need to stay in sync, how strict the access rules are, and how much of the old system must keep running during the change.

The estimator surfaces those questions so you can answer them before anyone quotes. Clear answers make estimates tighter and projects calmer.

Questions to answer before asking for a quote

  • Which systems must exchange data, and in which direction?
  • Who owns each piece of data when systems disagree?
  • How much historical data needs to move?
  • Which workflows can change, and which must stay as they are?
  • What happens if the new system is unavailable for an hour?

From map to discovery

The map is a conversation starter. In a discovery phase, each question it raises becomes a short piece of work with an owner: a data sample to review, an API to test, a workflow to walk through with the people who do it. That's how an estimate stops being a guess.

Frequently asked questions

Why doesn't it give a timeline?
Because an honest timeline depends on details a form can't capture, such as data quality and integration behavior. Discovery answers those questions and produces a real estimate.
Can I share the result?
Take a screenshot or bring your selections to a discovery call.
Does it include costs?
No. See the pricing page for engagement models.
Is anything I select sent to you?
No. The map is built entirely in your browser, and nothing is stored or sent unless you choose to share it with us.
Can I use it for a project with another partner?
Of course. The questions apply to any project, whoever builds it.
What if I don't know the answer to a question?
That's normal, and useful to know. Unanswered questions become the first tasks in a discovery phase.