AutoLoopers
Contact Us Get A Demo
AutoLoopers
Get A Demo

Most automation fails before the software is chosen.

The tool is almost never what went wrong. We find the leak first, put a number on it, and only then build something that beats the number. Everything below is the method, including where you can walk away from it.

Book the diagnosis Read the method first

The tool was never the problem.

Automation usually dies somewhere between the demo and an ordinary Tuesday. Three versions of it we keep walking into.

The shelf tool

Bought at end of quarter discount speed. Two workflows shipped, then the two people who understood it got busy. Still billing, no longer running.

The eternal pilot

The demo was genuinely good: clean data, the happy path, applause in the room. Production is where the scanned PDFs live. It was scoped to succeed, not to survive.

The wrong thing, automated well

It shipped, it runs, it is even elegant, and the operations budget never moved. Nobody had checked where the hours were actually going.

95%

of enterprise GenAI pilots return nothing measurable to the P&L.

MIT NANDA, 2025
30%+

of GenAI projects were predicted to be abandoned after proof of concept.

Gartner, 2024
30 to 50%

of early RPA projects failed to deliver, before AI was even the excuse.

EY, via Forbes, 2018

Those are our category’s numbers, not somebody else’s. Worth knowing what sits underneath the first one: the failures traced to workflows and diagnosis rather than to the technology.

Everyone in this row is paid to want something.

Nobody in it is a villain. Incentives just point where they point, so read the last line on each, ours included.

The platform vendor

Licenses, renewed yearly

Which makes them want

Adoption, whether or not it saves you an hour

The dev shop

Billable hours

Which makes them want

A longer build. The meter is the business model

The strategy consultancy

Recommendations

Which makes them want

A deck you approve. Delivery is someone else’s problem

AutoLoopers

A measured outcome, month to month

Which makes us want

Your hours back, fast. It is the only way we keep the engagement

Three steps. An exit after every one.

Step one

Find the real problem

We trace one workflow end to end and count every manual touch. The painful step usually sits upstream of the complaint.

TimeboxThe first week
You supplyTwo hours, plus read access
You holdThe Leak Map
ExitKeep the map, or hand it to anyone
Step two

Measure what it costs

Minutes per run, times runs per week, times what an hour really costs. Every input is shown, and a guess is labeled as a guess.

TimeboxDays, not weeks
You supplyThirty minutes to check our inputs
You holdThe Number, one page
ExitIf it comes out small, we say so
Step three

Build what beats the number

In your accounts, under your logins, starting with your worst inputs. Done means it runs without us, watched and documented.

TimeboxWeeks two to six
You supplyOne person who approves what it may do
You holdThe system, plus its Runbook
ExitYou own it either way

Three documents. Open any of them.

One per step, yours to keep whatever happens next, and written for whoever has to use it. Including the person who replaces us.

Step one
The Leak Map · client onboarding · two to three pages

Where the 34 minutes actually go

Form submittedautomatic
Rekeyed into the CRM8 min by hand
Documents chased12 min by hand
Folder createdautomatic
Kickoff email6 min by hand
Approvals chased4 min by hand
Invoice raised4 min by hand
Touches per run14
Of those, by hand5
Longest wait2.4 days
Human time, per run34 min

One step is a third of it. That is the step we price first, and it is rarely the one anybody complains about.

Step two
The Number · one page

Four inputs. Every one of them checkable.

34minutes per runmeasured, twelve runs
×
41runs per weekfrom your calendar
×
$38loaded cost per houryour estimate
+
4.1%error reworkmeasured
What doing nothing costs, a year$46,800
Human time, per week23.2 hrs
Per week$883
Per month$3,900

Three of these were measured and one is your own estimate, so the only number you have to take on trust is one you supplied.

Step three
The Runbook · ten pages

Page ten, in full

1 to 4What runs, and when
5 to 8What can break, and what happens then
9How to switch it off
10How to run it without us
How to run it without usp. 10
  1. Everything runs from your own accounts. Sign in as an admin and every workflow is listed under Automations, in the order it fires.
  2. Each one names its trigger, the systems it touches, and the person who approves anything customer facing.
  3. A run that fails lands in the Exceptions queue with the original message attached. Nothing is discarded and nothing retries silently.
  4. To stop a workflow, switch it off. Nothing downstream depends on it, and the manual path in section two still works.
Runbook · Client onboarding · page 10 of 10
Written forYour team
Needs us to read itNo
Pages on leaving usTwo

Written for whoever has to trust it at 2 a.m. and has never met us. A vendor you can leave is a vendor you can check.

One overlooked task. One year.

A second engagement, unrelated to the one above. Same method, on a task nobody had ever put a number to.

$0

a year, on one task nobody had timed

11 documents 12 minutes each 238 hours a year

Measured, rounded and anonymized. Yours will differ.

Document chase, this clientmeasured
W9 form3 chases36m
Certificate of insurance5 chases61m
Signed scope2 chases21m
Bank details2 chases26m
Brand assets4 chases47m
Six more, same pattern14 chases2h 9m
11 documents, every time238 hours a year

If the math doesn’t clear, we tell you to keep doing it by hand.

That sentence costs us projects. It’s also the only reason a stranger should believe the rest of this page: a method that can tell you no is worth more than one that always says yes.

The tangle becomes one line.

CRM Mail Sheets Docs Billing AutoLoopers Client Human approves

Five tools in, one path out, with one approval kept exactly where human judgement matters.

Your accounts, your logins

Built where you can see it, suspend it, or take it over.

Ugliest edge case first

Your worst inputs go in first. The easy ones are never what break.

A human where judgment lives

Anything customer facing or money moving waits for a person.

Deterministic first

AI is used narrowly, and gated wherever a wrong answer would cost you.

Your tools will change under you.

A vendor retires an API on a Friday night. A supplier redesigns their invoice template and tells nobody. Nothing failed on your side either time, and neither was preventable, so we design for the drift rather than for the demo.

Catch

Every run is watched. A failed step retries, then routes itself to a person.

Contain

Failures take one item down, never the pipeline. The other 41 invoices carry on.

Escalate

A named person on every workflow. When it cannot decide, it asks.

Learn

This month’s exception is next month’s rule, and one short note a week tells you what ran and what was caught. That is the maintenance.

Degrade

If a tool dies, the manual path is still documented in the Runbook.

Don’t take our math. Run yours.

The same arithmetic we’d do in step two, with no email gate and no “book a call to see results.” The sliders start at the shape we see most often; drag them to yours. If it comes out small, keep doing it by hand. Sincerely.

What doing nothing costs, per year at 1.3× salary
$43,776

1,152 hours · 7.2 months of a person

“Who are you, exactly?”

“They turned a detailed business process into a working system.”
Hinesh ChauhanPresident, Evolut Consult

A small operations practice, and this page is not pretending otherwise. No four hundred person delivery organization, no analyst report with our name in it, one published client. If that disqualifies us we understand, and the method above is yours to take anyway.

Being early is not only a discount on credibility. It changes what you get, structurally, and here is that trade in both directions.

You give
You get

A bet on a firm without a famous logo wall.

The principals, not a pod. Whoever is on your first call is who ends up in your systems.

Patience with a client roster that is still short.

Outsized care. Our next client will read about you, so a mediocre outcome costs us more than it costs you.

A month at a time. Nothing longer is asked for.

A vendor who has to earn it again every four weeks, with deliverables that already work without us.

Two hours of your process owner’s time to start.

Speed. No account layer and no workshop billed as a deliverable. Diagnosis starts the week you say yes.

Said to us, and answered in the open.

Six things people say on the first call. Open any of them.

We tried automation. It created more work than it saved.
Fair. It usually does.

Whatever failed was almost certainly built before anyone diagnosed it, and scoped to survive a demo rather than a Tuesday. That is what the first two steps are for, and why the worst inputs go in first. You are never asked to trust our optimism, only arithmetic you can check on inputs you approved.

Honestly, most of this AI talk sounds like hype.
Mostly, it is.

Operations rarely needs intelligence. It needs reliability. Most of what we build is deterministic and frankly dull: data moving between systems on a schedule, with receipts. AI earns a narrow place, reading a messy document or drafting a reply for a human to approve, and it is gated wherever a wrong answer would cost you something. When a vendor leads with the model rather than your workflow, that is the tell.

Couldn’t we just do this ourselves with Zapier?
Maybe, and maybe you should.

The first two steps tell you what to build, and the Leak Map is yours to hand to whoever you like. What clients actually pay for is everything after that: the edge cases, the monitoring, the 3am failure, the upkeep as your tools drift underneath you. If somebody on your team has real ownership and real time for that, doing it yourselves is a good answer. The calculator above tells you what their hours are worth.

Why not just hire an ops person instead?
Sometimes you should, and we will say so.

A hire is the right call when the work needs judgment forty hours a week. It is the wrong call when the work is rekeying and chasing, because you would be paying a salary for something a system does without sick days, and whoever you hired will spend their first year resenting it. Most strong teams end up doing both. The hire you eventually make gets a better job for what was automated before they arrived.

What happens to our data?

Systems are built in your accounts, under your logins, on permissions you grant and can revoke in an afternoon, inside the tools your data already lives in. Nothing of yours is copied onto our systems. Where part of a build has to run on our infrastructure we tell you which part and why before we start, information passes through it rather than being kept, and the Runbook documents every connection we make. The security page sets this out in full.

What if you disappear in a year?

Everything keeps running, because nothing lives with us. The systems are in your accounts, the Runbook explains what runs and how to switch it off, and your team has already operated it without us in the room, which is part of the definition of done. Worth knowing that the usual legal default runs the other way round: a vendor owns what it builds unless the contract says otherwise. Ours says otherwise, in writing.

Thirty minutes. One workflow.
A real number.

Book the diagnosis