Still doing quotes, follow-ups and admin after dinner?
A payslip that builds itself.
AI automation for the work that fills your evenings: follow-up, admin, chasing, reminders, reporting. Built into a system that does it while you are on the job.
A build for Vexor
Trips in. A draft pay run out.
For Vexor, I built the step between the trip tracker and payroll. Each driver’s trips for the week become pay lines in a draft pay run in Xero. A person checks it and approves it. Nothing is finalised on its own.
The second job
The admin is the second job.
Reply to the enquiry. Send the quote. Chase the quote. Confirm the booking. Remind the customer. Ask for the review. Update the spreadsheet. Every one of those is five minutes, and there are forty of them a day. That is the job nobody hired you for and it is why the business cannot grow past the hours you have.
Automate the steps. Keep the decisions.
I map what happens from enquiry to invoice and build the steps a system can do, across the tools you already use. The parts that need judgement, like approving pay or a price, stay with a person, with everything ready for them.
You can see every action the system takes, so nothing happens that you cannot check.
What I build
Systems that run without you.
I map what happens in your business from enquiry to invoice, find every step that is a person doing something a system could do, and build the system. New enquiry: instant reply, notification, follow-up sequence. Quote sent: chased on a schedule until answered. Job done: review request, invoice, reminder. Each piece is built for your process, not a generic template, and it keeps working after I have finished.
- Instant response to every enquiry, on the channel it came in on
- Quote follow-up sequences that chase until they get an answer
- Booking confirmations, reminders and no-show recovery
- Review requests timed to the moment the customer is happiest
- Reporting that tells you what came in, what converted and what is stuck
How it works
Four steps. The map first.
01
I map the process
Every step from first contact to final invoice, and who does what. The map shows where the hours go.
02
I pick the wins
The steps that cost the most time or lose the most work get built first. Usually enquiry response and quote follow-up.
03
I build and connect
The automations run across the tools you already use. Nothing has to be replaced to make it work.
04
I hand over and watch
You see every action the system takes. I review the first month with you and extend from there.
Asked before you did.
Often built alongside
Asked before you did.
Almost everything between an enquiry arriving and an invoice being paid that does not need your hands on a tool: replies, follow-ups, bookings, reminders, review requests, reporting and the moving of information between systems.
Usually not. I build around what you have. If a tool is genuinely the problem I will say so, but replacing things is the exception, not the starting point.
Not when they are timed and written properly. A reply within a minute of enquiring, a confirmation, a reminder the day before: these are things good businesses do. The automation just makes sure they happen every time.
A CRM gives you the building blocks. Most businesses never assemble them, or assemble them once and never look again. I build the whole process, test it, and keep it running as the business changes.
Yes. Every message sent, every task created and every handoff is logged, and you get a summary so you know what happened without having to check.
The first pieces, usually enquiry response and follow-up, are typically live within a couple of weeks. The rest is added in stages so you are never handed a system you have not seen working.
What you get back
You stop doing the same ten admin tasks every day and get those hours back.
Where do your hours go?
Tell me what the admin looks like in a normal week. I will show you which parts a system takes off you first.