Automation pilot · for accounting firms
Pick one job your team does by hand. In the two weeks after we start, we build the first part and test it in your systems.
At the end you also get a list of what else in that job is worth automating, and an estimate of what each would cost. The two weeks start the day we go through the job with the person who does it. If we're waiting on your logins or the signed scope, we hand over that much later.
If we sent you a role breakdown, reply to that email instead. Jesse can start with the job it suggested.
How the three days are spent.
01 · Half a day
See how it's done now
For the half day, the person who does the job takes us through it. Together we pick the first part to build, one that fits in two days.
02 · Two days
Build the first part
We build it in your firm's own systems and test it on your real work. Before it's switched on, the person who does the job spends about an hour checking it.
03 · Half a day
Hand over the list
The list ranks what else in the job is worth automating, best first, and puts an estimated price on each. We'll quote any line at a fixed price. You decide what gets built, if anything.
The code and the list
Once you've paid for the pilot, you can use and change the code we wrote for your firm, whether or not you hire us again. You keep the list too. We leave a plain-English guide to the code for whoever looks after it next.
A one-page scope before the build
It says what the software will do and what it leaves to your staff, and names anything it won't touch. It also estimates any monthly running cost. We don't start building until you've signed it.
A job someone does by hand every week or every month.
- Documents and workpapers
- Keeping the list of which documents are in and which are missing, and filing each against its job. If FYI or Karbon already does part of this, we build around it.
- Client onboarding
- Sending the engagement letter and the ID request, then chasing both until they're back. Your staff check the ID.
- Supplier invoices
- Your practice's own, or those of clients whose books you keep. Software can read each one, or take what Dext or Hubdoc has read, and suggest the coding and the job. Anything it isn't sure of goes to your staff.
- The monthly report
- The management report, debtors, WIP and lock-up that a junior rebuilds by hand. If your practice system holds the figures, software can build the report on a schedule.
How it's built.
The finished software uses AI only to read documents and suggest coding. The rest is ordinary code. You can trace every number to where it came from, and your staff check anything that doesn't match.
No firm has done this pilot yet, but we've built two tools for accounting firms. The trust audit tool does the routine checks on a real estate agent's trust account audit and hands back the working papers. Vigil checks offshore bookkeeping in Xero before the BAS, and it's in a paid pilot with a Sydney firm.
Logins and client data.
- The software you already have
- We build around the software you pay for now, such as Xero, MYOB, XPM, APS, FYI, Karbon and Microsoft 365. If we can't connect one, we'll tell you before we build anything.
- Access
- Your firm sets up the logins and decides what each one can see. Jesse uses them for the pilot only, and you switch them off at handover. We start building once they work. We sign a confidentiality agreement first, yours or ours.
- Your clients' documents
- They stay in your firm's systems unless a step needs AI to read them. For that step, the scope names the AI service and the country it runs in. Nothing goes to it until you've signed. Your staff keep that step if the service doesn't suit your firm. Jesse sees the documents we test the build on.
- After handover
- The software runs in your systems under a login your firm owns, and you pay any running cost directly. If it doesn't do what the scope says, we fix it free. We quote a fixed price for changes, and for repairs after a supplier's update.
Tell us about the job.
The button opens an email to Jesse with a few lines to fill in. Or, if we sent you a role breakdown, just reply to it.
Ask about a pilotOr write to info@mushin.com.au and put “An automation pilot” in the subject.