Find out where your margin leaks, in one week.

We spend a week with the people doing the work, then hand you five build-ready assets: a model of how your business runs today, a clickable prototype, a costed roadmap, a written proposal, and the hours and cost behind every item.

Book your discovery week See what you get

From $2,000, fixed and paid when you book. Full refund any time before the gathering starts.

  • Up to two weeks Often one. Gathering with your team, then processing on our side.
  • About six hours Of your team's time, all of it in the gathering.
  • Five assets Build-ready, and yours to keep whatever you do next.
Why we look before we build

Every business leaks in a different place

Someone retypes the same order into three systems. Nobody planned it that way, it accumulated.
One person knows how a process works, and it stops when they are away.
Growing means hiring another coordinator, because the work scales with volume.
The numbers that run the business are assembled by hand every month.
Nobody can say what any single process costs to run.
You can usually feel it before you can point at it. The discovery week is how we point at it, in numbers, so the first thing we build is the thing that pays back first.
What the week produces

A costed, sequenced plan you could hand to any developer

Not a slide deck. A model of the operation as it runs today, a prototype you can click, and a roadmap where every process carries its hours, its cost and its payback. Specific enough that another vendor could build from it.
Every process costed, with the payback on each
Sequenced so the first build pays for the second
The technology decision written down per item
A prototype to react to before code is written
All of it yours, whatever you do next

How the week runs

Three stages. The only part that needs your team is the first one.

  1. 1

    Step 1. Gathering

    We sit with the people doing the work and trace real jobs end to end: where data is retyped, where work waits, where errors get in. About six hours of your team’s time, and that is the whole ask.

  2. 2

    Step 2. Processing, on our side

    We build the process model, the prototype and the roadmap, cost every candidate, and write the proposal. Nothing further is needed from you.

  3. 3

    Step 3. Handover

    The five assets, walked through live and yours to keep. A simple operation is often done inside week one. Nothing runs past week two.

Book your discovery week
Two consultants sitting with an operations manager, tracing a process map on the wall beside them

The five assets

Each one is something a developer, an operator or another vendor can pick up and act on. All five are yours regardless of what you do next.

  • BPMN process model

    How the business runs today, one swimlane per actor. Bottlenecks in red, first automation targets in amber.

  • Clickable prototype

    A working front end you can click through before anyone writes production code.

  • Written proposal

    Scope, milestones, the technology decision behind each choice, what is out of scope, and the price.

  • Sequenced roadmap

    Every process costed and sequenced by payback, with the technology call on each. A live spreadsheet rather than a picture of one.

  • Hours and cost per item

    So you can judge any single item against the cost of a hire, and stop after the first if that is the right call.

Real deliverables

Two of the five, built from a real engagement and then reworked so we can show them here. The client is not named, the numbers have been changed, and the shape of the work is theirs.

BPMN process model of a materials supplier dispatch and delivery operation, four swimlanes, bottlenecks marked
The as-is model of a dispatch and delivery operation. One swimlane per actor, every handoff between them, and the bottlenecks marked where work waits.
Automation roadmap spreadsheet with each process costed, sequenced by payback, with technology and phase per row
The roadmap: every process costed and sequenced by payback, with the technology call on each row. A live spreadsheet, so changing the blended hourly rate recalculates every figure.

What it costs

Team size decides the price, because team size decides how long the gathering takes. One price, agreed before you start.

  • 1 to 20 people $2,000 One week of gathering
  • 21 to 50 people $4,000 Two weeks, more ground to cover
  • 51 or more Let us talk Scoped and priced on a short call
Book your discovery week

Paid when you book. Full refund any time before the gathering starts. Builds after that run $2,000 a week, one process at a time.

You own everything.

All work runs in your accounts, on your tools, documented in plain language. The proposal is priced and the prototype is clickable, so nothing about the set depends on us building it. Take it to your own team or to another vendor.

Book your discovery week

Six questions, then payment by card. We come back within one business day to put the gathering in the calendar.

  • Under 51 peopleYou see your price and pay here.
  • 51 or moreThe form routes you to a short call instead. We scope and price it there.
  • Changed your mindFull refund any time before the gathering starts.

Companies we have done this for

Questions people ask first

What will you actually build for us?

The gathering decides it, and the roadmap says so explicitly. For some clients it is a change of software, for others an automation layer with n8n over the tools they already have, for others a custom internal product. Usually it is a mix, sequenced by what pays back first.

Can I pay for the week right here?

Yes. Answer the questions in the form, and if the week is a fit you pay by card at the end of it. You get a receipt immediately and we come back within one business day to book the gathering.

What if we change our mind after paying?

You get the full amount back, any time before the gathering starts. Email [email protected] and it is refunded the same day. Once the gathering has begun the work is underway, so the fee stands and you keep every asset it produces.

How long does it take?

Up to two weeks, and often just one. A week gathering with your team, then processing on our side, with the assets landing at the end of week one or week two depending on how much ground there is to cover. Builds after that run two to eight weeks per process, at $2,000 a week.

Do we need our own tech team?

No. The engineers, the analyst and the support are ours. Your side needs one person who knows how the business runs and can make decisions.

Why does the price depend on our team size?

Because the gathering does. Tracing how work moves through a fifteen-person company takes a week. Doing it across forty people means more interviews, more processes and more handoffs to follow, so it takes two. The deliverables are the same five assets either way.

What if the roadmap says we should not automate anything?

Then it says that, and you keep the assets anyway. We would rather tell you at the handover than sell you a build that does not pay back.

What happens after the handover?

Whatever you decide. The proposal is priced and the prototype is clickable, so you can take the set to your own team or to another vendor. If you build with us it is one process at a time, in the order that pays back first, at $2,000 a week.