The routine parts of your week, handed to software
I come into a business, sit with the people doing the work, and write down how it actually runs: every step, every decision, what each one needs. Then the routine parts get handed to software, and the people stay on the parts that need a person.
Name one job that shouldn't need a person. It's free to ask.
Higgins based · onsite in Canberra · built around the tools you already use
Whichever one of these is eating your week
If yours is not here, ask anyway. The job that annoys you most on a Tuesday afternoon is usually the right one to start with.
Enquiries that sit in an inbox until someone gets to them
Read, sorted, replied to within seconds and landed in your phone, with the details already in the system. Nobody waits, nothing gets lost.
The follow-up nobody sent
Quotes that went quiet, jobs that finished without a review ask, customers who have not been back. Sent on their own, and you approve the words once.
The same details typed into three places
Inbox to spreadsheet to job system, by hand, every time. Entered once and moved between systems that never talked to each other.
Bookings done over the phone and written on paper
A booking that lands in the calendar, confirms itself to the customer, and reminds them the day before.
The same twenty questions, answered again every day
Answered from your real information, on the site or in the inbox, with the ones that need you handed to you.
Nobody knows the numbers until the end of the month
The week's enquiries, jobs, money and stalls pulled together on their own and put in front of you on Monday.
Documents that take an hour to assemble
Quotes, reports and letters built from the details already in the system, in your format, ready to check and send.
The team wants to use AI and does not know where to start
Hands-on sessions on your real work rather than slides. You leave able to do it yourself, which is the point.
What this looks like written for one real business
In July 2026 a Canberra real estate agency was hiring an in-house AI and technology person. I made the shortlist and they went with someone who had more years than me, which is a reasonable thing to decide. Before the interview I'd mapped their appraisal chain into seven stages, worked out what I'd build first, and written up what I'd do about the systems that didn't talk to each other.
That write-up was a redacted document on this site until 10 September 2026, when it was taken down. The work behind it is the same work described on this page.
Map first. Build second. Watch it run on real work.
Every decision in the process gets written down and assigned: code decides, AI decides, or it stays with a person. You end up holding the inventory, the decision map and the plan, and then you pick which parts are worth building. Nothing gets automated that should not be.
The first build is free. Name one job in your week that shouldn't need a person and I'll put a rough working version in front of you so you can test it against real work instead of arguing about it in theory. No charge, nothing owed either way.
Tell me the job that annoys you
The thing somebody does by reading and retyping, or the follow-up that never happens. One is enough to start.
I map how the work actually runs
Onsite, alongside the people doing it. Every step, every decision, every system and subscription, and what each one costs in time.
A rough working version, fast
Built around the tools you already use, put in front of you, and tested on real work. You see it run before anyone talks about money.
Then the parts worth doing properly
You pick what you care about from the map. What gets built stays looked after, and if you want to learn how it works, I'll teach you.
One person, and it is this one.
There is no call centre, no ticket queue and no subcontractor. You message me, I answer, and I do the work.
- I build it myself. I've been programming since primary school and I write the software. No agency, no offshore team, no account manager between you and the person who built it.
- I work with what you already run. The inbox, the job system, the spreadsheet, the phone. Replacing a system is the last resort, and I'll say so if it is genuinely the answer.
- Every decision is written down before it is automated. Which ones code makes, which ones AI makes, which stay yours. You hold the map.
- I'd rather be judged on something running than on a document. Which is why the first version is free and built fast enough to argue with.
What I will tell you not to automate
Anything that needs judgement, a relationship or a signature. The quote for the tricky job, the call to the customer who is unhappy, the decision about who to hire. Software around those steps, never instead of them, and the map says plainly which is which.
And if the honest answer is that a cheap off-the-shelf tool already does the thing, I will name it and set it up for you rather than build something. A custom build is for the job nothing off the shelf fits, and most businesses have two or three of those, not twenty.
Learn to do it yourself
Some businesses would rather hold the skill than hire it. Hands-on sessions for one person or a team, using your real work rather than slides, on the AI tools and on building with them. You leave able to do the next one without me, which is the point, and it's often the better answer than a build.
How the automation, the website and the lead system fit together as a whole is on the offers page, and what a hands-on visit looks like is on inside your business.
Onsite in Canberra, remote anywhere
The mapping is better done in the room, watching the work happen, and I'm in Higgins so most of Canberra is a normal drive. The building happens at my desk and the result runs wherever your systems do, so distance matters for the first week and not much after that.
Name the job.
A text is the fastest way to reach me. One sentence about the job that shouldn't need a person is enough. I'm back to you within a day, usually much faster, with an honest read on whether it is worth automating and what a rough version would take.