How we work
Five steps, the same on every project. Nothing touches a live client file until you've watched it work.
The five steps
Intro call
Thirty minutes. You describe the work that's eating the week, and we say plainly whether it's something we do.
Process map
We write down the current process step by step, with the people who actually run it, before opening any system.
Written scope
What gets built, what it connects to, what it won't do, and what it costs. Agreed in writing before work starts.
Build and test
Built against a sandbox or demo company first, then run alongside your current process until the results match.
Handover
A plain-language runbook, credentials in your firm's name, and a walkthrough for whoever will own it day to day.
Ground rules for touching client data
Your clients trust you with their books. These rules are how that trust carries through to anything we build.
Read-only first
An integration proves itself reading data before it's allowed to write anything to a ledger.
Your accounts, your keys
Connections run under accounts your firm owns, so you can revoke access in one step from inside Xero or QuickBooks.
Only the data the job needs
We take the fields a workflow uses and nothing else, and don't keep copies we have no reason to hold.
A person signs off
Anything that changes a client's numbers can be set to wait for a named person to approve it.
Failures get noticed
Every build alerts on a failed or stuck run, so a problem reaches us before it reaches your client.
You own what's built
The workflows, the code and the documentation are yours. If we stop working together, it keeps running.
Before you hire anyone to automate client data, ours included, the seven questions in our due-diligence article are the ones to ask.
How work is priced
Each project is quoted in writing after the process map, before any build work starts. The quote says exactly what's included, so there are no open-ended hours. Platform costs (an n8n or Make subscription, for example) are estimated from your actual volumes and named in the scope, and the subscriptions are yours.
After handover
Every build alerts on a failed or stuck run, and the runbook says what to check and how to pause it. Ongoing support is optional and is set out in the scope, so you know before you start who fixes what. Nothing depends on AVROQ staying involved.