AI workflows
Pick one job. Stop doing it by hand.
A workflow is one job, wired up once. It starts on its own and the result lands where your team already looks.
A focused custom build for work whose steps can be settled in advance. If they can't, an assistant may be the better fit.
Get in touchThe jobs worth wiring up
The best candidate is something boring that happens often and could be written down as a list of steps.
Usually it's where the software you already pay for stops just short. The CRM assigns the lead but won't draft the reply. Xero has the numbers but nobody pulls them together. The information is all there - it just needs a person, every time.
If someone does it the same way each time, it can probably run without them.
The same job, twice
One that turns up everywhere: an enquiry lands, and somebody has to answer it.
How it runs today
- 9:14amThe enquiry lands in the shared inbox.
- 11:40amSomeone notices it between other work.
- 11:52amThey read it twice and work out what's actually being asked for.
- 1:20pmThey go hunting for what you charged the last person who wanted something similar.
- 2:05pmThey check Xero to see whether this lot have bought from you before.
- 3:30pmThey start the reply, then get pulled onto something else.
- Next dayIt goes out. Nobody copies it into the CRM.
A day and a half, and the trail ends in one person's sent items.
Wired up
- 9:14amThe enquiry lands. It gets read and sorted into what they're actually after.
- 9:15amPast quotes for similar work and their history in Xero get pulled in, and a reply is drafted.
- 9:16amThe reply is ready as a draft, with the enquiry assigned in your CRM.
Ready in minutes for someone to review and send. The trail's already where it should be.
An example, not a case study. The tools named are ones people actually use - yours would run on whatever you already have.
Jobs like these
Common work where a wired-up job quietly earns its keep.
A single job can connect a few tools and still land near the minimum build. More variations, exceptions, approvals or custom connections push it into a larger one.
Keep records up to date
A new customer or job gets entered in one system, then copied into the others by hand. Sooner or later one gets missed.
What it does. When the first record is created, it adds the matching details to the other systems and flags anything it can't match.
The weekly numbers, pulled together
Every Friday someone opens Xero and the CRM, copies the same figures into a spreadsheet and writes the same summary. It takes an hour and nobody looks forward to it.
What it does. On the day you pick, it pulls the same figures from the same places, lays them out your way and posts the summary in Slack. Anything outside the range you've set is flagged at the top.
Different files into one format
Data turns up in a different shape every time: supplier lists, exports, forms. Someone re-keys or reformats each one by hand to match how you work.
What it does. When a file lands in the inbox or shared folder, it maps the formats we've agreed into your standard layout and flags anything it can't match.
A first draft from the notes
A quote, proposal or job brief still gets written from scratch each time, off scattered notes and half-remembered calls.
What it does. Once your notes are in, a first draft is waiting in your usual template, built from similar past work and linked on the job. You edit something concrete instead of staring at a blank page.
How a build goes
Find what's worth doing
- An honest look at whether AI belongs in the job at all, and where to start if it does. It begins with a free call, and often that's enough to see the first move.
Build the first useful thing
- One job, scoped and fixed-price before I start. I keep the first build small and hand it over in a form people can actually use.
Hand it over and let it run
- A clever one-off in someone's chat window isn't much use. I document the instructions, limits and checks so it follows an agreed method each time, and the setup stays with the business instead of living in one person's chat history.
The first month of hands-on support after go-live is included, settling anything that isn't working as agreed. After that, ongoing care is optional.
When it isn't worth wiring
A job that runs twice a year won't repay the build. Neither will one where the rules change every time you look at them, or one that's a mess on paper - automating a mess just gets you a faster mess.
Some work needs a person to look at it. Where getting it wrong costs more than the hours it saves, leave it alone. You'll hear that on the call rather than after the invoice.
When the steps change every time
If the job has to choose the tools and steps as it goes, a fixed set of steps won't cover it. An assistant can.
Often that's the one you already pay for, set up properly in a single session.
More about AI assistantsGet a read on a job of your own.
Describe one repetitive job and you'll know in a minute, including when the answer is to leave it alone. No email needed.
What it costs
If the job looks like a fit and is clear enough to price, I send a short scope and fixed-price proposal.
A workflow build
One recurring job, wired up across the tools it needs. More variations, approvals or custom connections make it a larger build.
The price is fixed once we agree the scope.
All prices are in AUD, plus GST.
After launch
This is a one-off build, not a subscription. The first month of support is included.
Ongoing care is available if you want it. We scope it separately once we know what is actually running.
Which job keeps eating the week?
Tell me what it is and roughly how often it happens. I'll tell you whether it's worth wiring up, and what it would take.