Somebody is re-typing what a computer could just copy.
Every business has one. The job someone does forty times a week that produces nothing new — reading something out of one screen and typing it into another.
We work out what’s really going on, build the thing that does it instead, and then keep it running.
Describe the job you do twice. I’ll tell you straight, for free.
It’s nearly always data moving between two systems.
The industries change. The shape almost never does — something arrives, a person reads it, and a person puts it somewhere else. That middle step is the one we remove.
Inbox → your system
Enquiries, orders and forms landing as email, then getting re-keyed into a CRM or job system.
- Pulls the fields out of an email written for a human
- Matches the customer instead of creating a fourth copy of them
Nothing falling through
Quotes that go quiet, jobs that finish but never get invoiced, follow-ups nobody owns.
- Chases on a schedule and logs what came back
- Escalates to a human instead of silently giving up
The Monday morning spreadsheet
The report someone assembles by hand, or the sheet three people keep half-updating.
- Builds itself from the systems the data already lives in
- One version, current, without anyone maintaining it
We’ve built these for delivery, trades and service businesses. The trigger changes; the job is the same one.
Not a template. A build, scoped to your mess.
Every one starts with an hour working out what really happens — including the parts nobody wrote down, and the ones that only make sense once you know which mistake is the expensive one.
That’s the whole job. Anyone can wire two apps together on a good day. The value is knowing what the exceptions are before they bite, and being the one who fixes it when something upstream changes.
We build most of it in Make.com, sometimes Zapier or custom code, and we’ll tell you which and why.
One call. What comes in, what you do with it, and every “except when…” you can think of.
Wired into the systems you already run. No new software for your team to learn.
We push real cases through and check what lands. You watch it run before you trust it.
APIs change, formats change, edge cases turn up. That’s what the monthly covers.
If you can describe it, it’s probably automatable.
Say the job out loud. “When an email comes in, I open it, copy these bits into that system, and file it” — yes, almost certainly.
“It depends, you sort of get a feel for it” — probably not, or not all of it. That’s a useful answer too, and it’s free.
Describe it and we’ll tell you
Some of it shouldn’t be automated, and we’ll tell you which.
Most jobs have a corner that looks mechanical but isn’t. A handful of customers who get treated differently for reasons nobody has written down — the only way to know is that the team just knows.
We could guess at a rule. It’d be wrong occasionally, and quietly wrong is worse than manual. So that part stays manual, and it goes in the scope that way rather than being discovered later.
The other one is platforms that simply won’t let you. Some systems won’t send an attachment by API no matter who’s asking. When we hit one of those we’ll tell you, rather than bill you to find out.
Rules you can write down. Same input, same output, every time.
Mostly mechanical, occasionally needs a human — so it stops and asks instead of guessing.
Judgement that lives in someone’s head. Automating it means being confidently wrong.
Some things the software won’t let anyone do. Better to know in the scoping call.
A build fee, then a small monthly to keep it running.
The build depends on how many edge cases fall out of the scoping call. A one-path automation and a five-path one aren’t the same job, and we won’t pretend otherwise.
The monthly isn’t a subscription to software you could buy yourself. It’s us watching it and fixing it when something upstream changes — because automations don’t break loudly. They break quietly, and you find out a week later when something’s gone missing.
You get a real number after the scoping call, before anything is built.
Straight answers
How do I know if my job can be automated?
Describe it out loud. If it sounds like a sequence of steps that happen the same way each time, yes. If it sounds like judgement built up over years, probably not — or only partly.
Tell me either way and you’ll get a straight answer before you spend anything.
What tools do you use?
Mostly Make.com, sometimes Zapier, occasionally custom code where the platform can’t do what’s needed.
You could learn Make yourself and plenty of people do. What you’re paying for is someone who’s already made the mistakes, and who picks up the phone when it breaks.
Do I need new software?
No. The point is that it works with what you already run — your inbox, your job system, your accounting. Your team’s day doesn’t change. The typing just stops.
What happens when it breaks?
It will, eventually. Someone changes an email template, an API version gets retired, a supplier reformats something. That’s normal and it’s not a sign anything was built badly.
The monthly covers us noticing and fixing it. Without that, the usual pattern is an automation that quietly stops working and nobody realises for a fortnight.
How long does it take?
Simple ones, days. Ones with several paths and a lot of exceptions, a couple of weeks — most of which is testing rather than building.
We won’t switch it on live until you’ve watched real cases go through it.
Is this the same as the AI receptionist?
No, and plenty of businesses take one without the other. This is backend work — nothing touches your phones unless you want it to.
If you do want the phone side, that’s the AI receptionist.
Will you take over something someone else built?
Sometimes. If it’s in Make or Zapier and readable, usually yes. If it’s undocumented custom code, it’s often cheaper to rebuild than inherit — we’ll tell you which after a look.
Tell me what you’re re-typing.
Describe the job somebody does over and over. I’ll tell you whether it’s automatable, what it’d take, and what it’d cost — or that it isn’t worth it, which happens more often than you’d think.
No calendar invite needed. Write it in the box.
Free to ask, and I’ll tell you if it isn’t worth automating. If it is, you get a real number before anything gets built.