How it works
From the kickoff call
to a system you own.
Seven days, on your real paperwork, in your own account.
The seven days
The call is the start line.
Nothing before kickoff counts against the seven days. From there it is on us.
Kickoff
A 30 minute call. You name the three to five things you want gone, we take access, and the clock starts.
We build
On your real paperwork, not a sample. Your last month of invoices, your variations, your contract.
You see it run
Live, on your own jobs, with your own supplier names in the output.
Tighten and hand over
Your wording, your formats, your edge cases. Walkthrough recorded, playbook written, everything in your account.
The infrastructure we install
Five layers. In this order.
The back end goes in before a single automation runs.
Memory
Your business written into files the AI reads every time: rate card, job codes, suppliers, contract terms, your wording. Kept current on the monthly.
Skills
A written procedure per job, trained on your formats. A claim is built the same way every time because the way is written down.
Connectors
Wired to Xero, your job software, your drive and your inbox, with a Chrome extension so it works where you work.
Workflows and triggers
When this happens, that happens. A file lands, a date arrives, an email comes in, and the work starts without anyone opening a laptop.
The human check
By default every output is a draft a person approves. Where you want a task to run fully automatically, it does, and the playbook says which is which.
Then the automations
Three to five of them at Level 1, named by you, built on this. They hold because the layers underneath them do.
Included with every level
No matter which one you take.
Your own written playbook
What each automation does, what a human checks, who owns it. One page each.
A recorded walkthrough
Yours to keep. A new staff member is running the same day.
Branded templates
Progress claim, variation and client report in your branding.
A prompt library
The wording that works, so your team stops guessing at it.
72 hour priority fix
Broken is fixed inside 72 hours. You are never stranded.
One swap, first 30 days
Wrong automation? We swap it. No charge, no argument. And we call you at day 30. Not a survey, a call.
The three rules
And they are the whole agreement.
The hours stack
If your build includes two hours a month and you add a support tier with one, that month you have three. They add together. They do not replace each other.
Everything monthly runs while the monthly is paid
The training hours and the founder hours inside your build keep running for as long as you are on a support tier. Stop the monthly and the build is still yours, on your machine, working. The hours and the new automations are what stop.
Seven days, or the first month is free
Built, loaded and running on your own paperwork within seven days of the kickoff call. If we miss it, your first month of support costs you nothing.
Your tools, not ours
We build inside what you already run.
Xero, your job tracking software, your drive, your inbox, your phone. Connectors are wired to the tools you have, so the output lands where you already look for it. No new platform, no new login for your team.
Where a tool has no way in, we go through the one that does. A receipt coded in Xero is read by the job software that syncs with Xero. We tell you which path it is before we build it.
What we will never do
You decide what runs on its own.
By default every output is a draft you approve. Where you want a task fully automatic, sending, chasing, filing, it runs that way. Either way you are not the one typing it out at nine at night.