How an engagement runs
Map, Build, Adopt.
One workflow at a time, starting with the one costing you most. Every step pays for the next.
Free. One workflow you pick, mapped in two pages: how it runs, how it should, what the gap costs a month. Thirty minutes of your time. No cost worth fixing, no pitch.
Fixed price, weeks not months. Built on the tools you already have, run by your own team.
Then the next one. Savings reported every month in dollars and FTE. You own everything.
If a build doesn't do the job, we rework it until it does.
01 Before it goes live
Checked, or it does not go live.
-
Checked against real work
It runs against past cases that went wrong before it goes live.
-
Counted, not estimated
Per workflow: what it cost before and after, reported every month in dollars and FTE.
-
You can switch it off
The old way stays until you say so.
See it at Burnham RNG, where calculator regression tests now catch a change that moves a number.
02 When not to automate
Four times the map says no.
- 01
The volume is too low to pay back.
- 02
The process still changes every month.
- 03
The data lives only in heads and voice notes.
- 04
A named expert's judgement is the product.
03 The trust stack
The terms we work under.
Send this page to your IT lead.
- Who we are
- Founder-led engineers and analysts in India, working with firms in the US, UK, UAE, Australia and India.
- Before the first call
- An NDA and a data handling note, signed first. No credentials needed.
- Price
- Every build is fixed price, agreed after the free map, in weeks not months.
- If a build falls short
- We rework it until it does the job.
- Ownership
- Your infrastructure, your accounts, your code and documentation. No lock-in.
- Reversibility
- Every change logged, anything can be put back, and you hold the off switch.
- Regulated workflows
- We put in writing which rules apply before we build, and design to them.
- If something goes wrong
- We switch it off first, then send a written account of what happened.
04 Questions
Straight answers, before you ask.
01 What does Map, Build, Adopt actually mean?
It is three stages, one workflow at a time. Map: free, one workflow you pick, mapped in two pages with what the gap costs a month. Build: fixed price, weeks not months, on the tools you already have, run by your own team. Adopt: then the next workflow, with savings reported every month in dollars and FTE.
02 How do you measure ROI on automation?
We put a monthly cost on the workflow before we touch it, then report what it costs after, every month, in dollars and FTE. The map records how long the work takes and what it gets wrong. The return is that difference, counted rather than estimated, and it decides which workflow is next.
03 How do you test an automation before it goes live?
We run it beside the old way on your real data until the two match. Before it takes over, we also run it against cases that went wrong in the past and show you where it holds and where it does not. Nothing gets switched off on faith.
04 When should we not automate?
Do not automate when the volume is too low to pay back, the process still changes every month, the data lives only in heads and voice notes, or a named expert's judgement is the product. In those cases the map says skip, and we say so before you spend anything.
05 Are you a consultancy or an AI agency?
We are both, in order, one workflow at a time. The map says what the gap costs, we build the fix on the tools you already use, and your team runs it. Then we move to the next workflow. If the honest answer is that a workflow is not worth fixing, the map says so.
06 What does it cost?
The map is free. Every build after it is fixed price, agreed once the map shows what the gap costs, so you know the number before we start and it never runs by the hour. Each workflow is sized so its savings can pay for the next one.
07 What if a build does not do the job?
We rework it until it does. Every build is checked against the job the map described before your team runs on it, and the monthly report shows whether it is still doing that job. If it slips, we fix it first and explain what changed.
08 Who owns what you build?
You do, all of it. The systems run on your infrastructure and your accounts, the code is yours, and documentation ships as a deliverable. There are no vendor logins and no lock-in, so nothing goes dark if we part ways, and another team can pick it up.
09 What happens if an automation misbehaves?
You switch it off, and we fix it. Every system has an off switch you hold, every change is logged, and anything can be put back. When a check fails we stop the system first, then send you a written account of what happened and what changed.
10 Who are you, and where are you based?
We are a founder-led team of engineers, consultants and analysts based in India. We work with companies across the US, UK, UAE, Australia and India. Both founders are engineers, and the people on your first call are the people accountable for the work.
11 Do we have to move to new tools?
Almost never. We build inside the tools you already pay for, because moving systems is expensive and is rarely the real problem. If a new tool genuinely earns its place, we say so and show the maths before anything changes, and you decide.
12 How do we start?
Book a call and pick the workflow costing you most. We map it free in two pages: how it runs, how it should, and what the gap costs a month. It takes thirty minutes of your time, NDA first, no credentials. If the map shows no cost worth fixing, you keep it and hear no pitch.
Start with one workflow, mapped free.
Thirty minutes of your time. No cost worth fixing, no pitch. The map is yours either way.