About AI Pathway
The workflow, not the model. And proof you can run yourself.
The method
Twenty years in software, and this firm started in the trades: plumbers, electricians and builders losing money to missed calls, slow quotes and invoices nobody chased. What we learned there is that the leak is in the workflow, not the model. Any good model can hold a conversation; what decides whether the job gets booked and the invoice gets paid is the order of the checks, the one record written once, and the step that should not be hand-rolled. So we publish each workflow as a free open standard, run the risky step as a paid insert, and build alongside you when it has to survive a real business. Voice is how some of those jobs get done. It is not the company.
Andrew Forkes, Principal Consultant, is the person you meet on the audit and the build. AI Pathway, Office Voice and workmylist are products of Four Mile Pty Ltd as trustee for the Four Mile Trust (ABN 48 949 885 135).
Test it yourself in a minute
There are no client results to quote yet, so here is proof you can stage instead. Each test names what passing looks like.
Mark the top invoice paid
In the Debtor Chasing stub, mark the highest-ranked invoice paid, then run the chase.
Pass: That customer is not rung, and the log row says which ledger read stopped it.
Start a standard red
Run npx @aipathway/conformance init booked-after-hours-build-standard in an empty folder, then run the harness it writes.
Pass: Every check starts red. Nothing passes until something you built earns it.
The order to build in
Cash first. One job on the phone needs nothing underneath it: a number is pointed, the job is written into the system you already run, and the money it brings back pays for what comes next.
Then the foundation. Anything that answers a question reads from a register of how the business works. Build the assistant before the register and it answers from whichever copy of the manual it found.
Stopping is allowed. Most businesses fix the first job and the foundation and go no further this year. Every step is priced on its own for that reason.
How the standards stack on each other: combining the standards.
What changed in the standards
Recent changes, newest first.
- New: the Review Request standard. Every customer asked for a Google review the same way once the job is finished, one reminder then stop, unfinished jobs held with the reason, low scores to the owner, and no review gating. Runnable stub and a Microsoft 365 plan.
- New: the Next Service standard. Warranty and service reminders with due dates worked out from a written schedule, a reminder with consent, one follow-up, and a yes written back to the job system as one booking request. Runnable stub and a Microsoft 365 plan.
- New: the Document Filing standard. The daily office run: every document from every door matched to its record by the number printed on it, entered, filed once, one exceptions list, and a close that adds up. Runnable stub and a Microsoft 365 plan.
- New: the Remittance Split standard. When one deposit pays many invoices, each remittance line is matched by invoice number and the deposit is applied as one batch payment equal to it, with every exception left to a person. Runnable stub and a Microsoft 365 plan.
- Every build standard now integrates with Office Voice, never workmylist. Database Reactivation and Open-Home Feedback name Office Voice's governed single call for people who asked to be rung; the Work the List insert is gone; the Just-Sold Pack and Price One-Pager name no product. workmylist stays a separate real estate product.
- Database Reactivation gains the daily call list: a capped list for a person each morning, a reason and a drafted opener per row, outcomes written back the same day. Two new checks; the pass test is now check 14.
- New: the Price One-Pager standard. Comparable sales chosen by written rules, a range worked out from them, the agent's estimate kept apart, underquoting flagged, with a runnable stub, a free Google Sheet and a Microsoft 365 plan.
- New: the Open-Home Feedback standard. Follow-ups you approve, replies sorted, offers and complaints to the agent, and a vendor report of counts and buyers' own words, with a runnable stub, a free Google Sheet and a Microsoft 365 plan.
- New: the Just-Sold Pack standard. When a property sells, the neighbours hear about it with the real sale facts, and a person approves every message. Runnable stub, a Google Sheet template and a Microsoft 365 plan.
- New: the Simpro Claude Connector standard. Claude on your own Simpro, on a key you create and can delete, with a runnable stub and a Microsoft 365 plan.
- Booked After Hours and Debtor Chasing follow what shipped: one call per customer, state public holidays, a confirmed address, consent before SMS, typed hand-offs.
- Booked After Hours, Follow-Up and Invoice Out lead with the done-for-you path, then build it yourself.
- Debtor Chasing rewritten to match what Get Paid runs in production.
- Cash Seam published: one record from the call to the chase.
- Every standard reviewed to say what production does today, and nothing more.
- Quote Out reached production: a draft from your own price list lands in Xero for a person to send.
- Invoice Out: ServiceM8 and Simpro need the owner's own key, said plainly.
- Invoice Out published, plus seven standards so every diagnosis category has one.
Start with the workflow, not the tool.
Eight minutes, no email. Or the $500 audit, credited against any work that follows.