Client onboarding
An engagement letter, identity verification, and a list of source documents, collected from a client who has other things on. Three rounds of chasing is normal, and each round costs somebody a slot in their week.
Services / Accounting practices
// accounting
AI operations for accounting practices.
The compliance work has a deadline attached to every piece of it. Most of the stress is not the work itself, it is knowing what is outstanding and who owes it.
$ qdp scope --practice accounting
client_onboarding: “engagement letter, ID, source documents”
lodgement_tracking: “per client, not per memory”
document_collection: “chased without you writing the email”
workpapers: “drafted from the file before review”
// scoped to your practice. owned by you.▋
Where the hours go in a practice.
Almost none of this is judgment work. It is collection, tracking and assembly, done by people whose time is worth considerably more than that.
Lodgement dates
Every client carries their own set, and the consequence of missing one lands on the practice rather than the client. Most firms hold this in a spreadsheet plus the memory of whoever has been there longest.
Document collection
The same request, sent again, worded slightly more firmly. It is not difficult work and it is not quick, and it is the part that most reliably slips when the practice gets busy.
Workpapers and queries
Assembled from a file that already contains everything needed. Reviewers spend the first part of every review reconstructing what the preparer already worked out.
What we would build for you.
Every build starts from your workflows rather than a template, so treat these as the shape of the work rather than a menu.
Onboarding that collects itself
The engagement letter goes out, identity and source documents are requested, and outstanding items are followed up on a schedule you set. Your team sees a status rather than a to-do list, and steps in when something is genuinely stuck.
A deadline register that watches itself
Lodgement dates tracked per client with the work that feeds them, so nothing depends on somebody remembering. Reminders go out early enough to be useful, and escalate only when a date is at real risk.
Workpapers drafted from the file
First-draft workpapers and queries assembled from what the file already holds, so review starts from a draft rather than a blank page. The preparer checks and corrects. The judgment stays with your people.
What we can tell you before you have seen it work.
Our published case study is an architecture practice, not a firm like yours. We would rather say that plainly than dress up a testimonial from an adjacent industry, so here is what stands behind the work instead.
You see the plan before you commit
The assessment produces a written Automation Map: what is worth automating in your firm, in priority order, with an honest recommendation on each. It is free, and it is yours to keep whether or not you go ahead.
The scope is the contract
If your system does not do what we scoped within 30 days of launch, we fix it free or refund you in full. We do not promise business outcomes we cannot control. We promise the system does what we said it would.
You own the code and the IP
Once the project is paid for, everything in it is yours. No per-seat licence and nothing to unwind if you want to take it in-house. You could do that tomorrow. We would just rather you did not have to.
$ qdp start --practice accounting
See what we’d build for your practice.
Book a free 30-minute assessment. You’ll leave with your Automation Map and an honest recommendation, even if it’s “not yet.” No pitch deck. No hard sell.
30 minutes · no obligation · you keep the Automation Map either way