Find out which work in your business a machine should do, and what it would save.
Two weeks mapping how your work runs today, ranked by what automating it would save and cost in rupees or dollars, including what to leave alone. You keep the report whether or not you hire us.
What we look at
- How comparable businesses run the same work
- What firms of your size and kind already hand to software, what they still do by hand, and why.
- Your processes as they run today
- Interviews with the people who do the work, and a look at the systems it passes through.
- The money
- Hours and cost per month now, the cost to build and run a tool, and how long it takes to pay back.
- What not to automate, and why
- The work that should stay with a person, a rule or a better spreadsheet, with the reason for each.
- Data and privacy
- What can leave your machines and what can't, and what that means for where a tool would run.
- People
- Who would need training, and what happens to the time a tool gives back.
What you receive
One written report, yours to keep and to take to any team.
Not included
- Writing or deploying code (that's a pilot)
- Negotiating with vendors
- Advice after the readout call
- A map of each process as it runs today, built from your systems and your team's own account of them
- A ranked list of candidates, each with the hours it takes now and an estimate to build and run
- A written list of what not to automate, with the reason for each
- The integration risks we found, such as rate limits, duplicate records and documents that change format
- A recommended order of work
- A money table for each candidate: hours and cost now, cost to build and run, and when it pays back
- Guardrails for each candidate: what a tool may do on its own, what a person checks, and what it never touches
- A training plan for the people who would use or run it
- A pilot proposal for the first candidate, attached. You are free to ignore it
How it runs
The intake form
Straight after you pay: the process to start with, the systems it touches, the one question you want answered, and dates that suit your team.
Interviews and systems
We talk to the people who do the work and watch it run in the systems it passes through.
Analysis
We cost each candidate, rank them, write down what to leave alone, and draft the guardrails and the training plan.
The readout call
We take you through the report and answer your questions. It is yours from that moment, whether or not you hire us.
Sample audits
The first sample audits go up this week.
Price
from $3,500Prices for the United States, where you're visiting from.
Credited in full against a pilot started within 90 days. On-site days are available, with travel billed at cost.
Questions before you buy
Why pay for an audit?
Because the report is the product, not a step in a sale. A free assessment is paid for by the build it recommends, so it tends to recommend one. Ours is paid for up front, which leaves it free to say a process isn't worth automating, and it's written so that any team can build from it.
Can we take the report to another vendor?
Yes. It is written for that: each candidate comes with its process map, the systems it touches, the risks we found and the costs, which is what any engineering team needs to quote it.
Do you need access to our data?
Not to copy any of it. We interview the people who do the work and watch it run on a screen share. Where a system's settings or limits matter, we ask for a read-only login you can revoke at any time. If you'd rather we didn't see personal data, blank it out; the audit doesn't need it.
What if you find nothing worth automating?
That is a valid result. You get the reasons, the don't-automate list and the numbers behind it, which is worth having before anyone tries to sell you a build.