Automations that mean business.
The repeat work in your business, handed to something that does it the same way every time, at the same speed, whether or not anyone remembered.
- Starts with
- A form, a sale, a new record, a date, or a fixed schedule.
- Runs on
- The tools and accounts you already have, connected to each other.
- Watched
- Steps retry on their own, and a person hears about the rest.
One enquiry, start to finish.
An automation is a chain of small, boring steps. Here is one of them running, including the part where something didn't answer.
- 0.0sEnquiry form submittedkitchen refit, west sideTrigger
- 0.4sMatched to a customer already on fileno second record createdStep
- 0.9sJob opened and assignedwith the enquiry attached to itStep
- 1.6sCalendar didn't answer. Tried again.second attempt, no one had to noticeRetry
- 2.1sReply sent, three times to pick fromread on a phone, in their time zoneStep
- 2.3sTeam notifiedbefore anyone opened a laptopDone
You approve how it behaves once. After that it runs the same way every time, including the times nobody is watching.
What we actually automate.
Not a category. The specific jobs that quietly eat a week and only happen when somebody remembers them. A few of these use an AI model, in the places where reading something messy is the actual work.
Enquiry response
A new enquiry gets a real answer in seconds, with your availability attached, instead of tomorrow morning when someone gets to the inbox.
when a form is submittedQuotes and invoices
Drafted from the record that already exists, so nobody retypes a line item into a second system and no one invents a total.
when a job is approvedReminders
Appointment reminders, arrival windows, and confirmations that go out on time whether or not anyone is at a desk that day.
when a booking is a day awayReview requests
The ask goes out once, while the work is still fresh, without anybody having to decide to send it.
when a job is marked doneMessy inbound
An email that buries the actual request three paragraphs down gets read, summarised, and filed against the right job before anyone opens it.
when a message landsFirst drafts
A reply written for you to glance at and send, not one that goes out on its own. You stay the last step, because that's the step worth keeping.
when a question needs answeringRecords in step
The tools you already pay for kept agreeing with each other, instead of one person exporting spreadsheets every Friday.
when anything changesReports
The numbers you actually check, compiled and delivered on a schedule, already in the shape you read them in.
when Monday morning comes roundHandoffs
Work moving to the right person with the context attached, instead of sitting in an inbox waiting to be noticed.
when a stage changesIf a person on your team does it the same way every time, it is a candidate. Bring the list you already keep in your head to the call.
Inside the step that needs judgment.
Most of a run is rules. One or two steps are reading, and that is where an AI model belongs: turning something a customer wrote badly into something the rest of the run can actually use.
“Hi, sorry to bother you again, my wife rang last week I think she spoke to someone. Anyway we finally had the surveyor out and he says the beam is fine so we're good to go ahead. Can we still get in before the school holidays? Also the quote had our old address on it. Thanks, Dave”
- Customer
- Already on file, quoted in March
- About
- The back extension, not a new job
- Actually asking
- Can we start before the school holidays
- Also flagged
- The quote has their old address on it
That is the whole of the AI in most of the automations we build: one step, doing the reading, handing back something a person can approve in seconds. What an agent does, and where it stops.
The hundredth run, not the first.
Anyone can demo an automation once. Keeping it running through expired logins, changed forms, and a tool having a bad Tuesday is the actual job.
It retries.
A tool that doesn't answer isn't a lost job. Steps retry on their own, and the run carries on from where it stopped rather than starting the morning over.
It tells us.
When something genuinely needs a person, the alert reaches us. You find out from your agency, not from a customer asking why nobody called back.
It's yours.
Everything runs on your own accounts, against your own data, documented in plain language. Nothing important to your business ends up locked inside something you rent from us.
Questions about automations.
If yours isn't here, ask us on your call.
Do we have to replace the tools we already use?
For automation work, usually not. Automations are the wiring between tools, so in most cases they connect what you already have and leave your team working where they already work. If something you rely on genuinely can't be connected, you'll hear that on the call, not after the invoice.
Is this AI, or just automation?
Both, in different places, and the split is deliberate. Most of what gives you your week back is ordinary dependable logic: this happened, so do that. Where the actual work is reading something a person wrote badly, summarising it, or drafting a reply, an agent does that step. Anything with money, a date, or a promise attached still waits for you.
What happens when an automation breaks?
Steps retry on their own, so a tool that goes quiet for a moment isn't a lost job. When something genuinely needs a person, the alert reaches us and we fix it. Automations sit on top of tools that change without warning, so they need looking after: that's what a support plan is for.
Can we start with one automation?
Yes, and it's usually the right way in. We take the single job costing you the most time, build that one, and let it run for a while before deciding what's next. Each one is scoped and quoted in writing before work begins, same as everything else we do.
Let's get your business running.
Tell us what you're building, or untangling. You'll hear back within a day.