AI for Accounting Firms.
Most firms don't actually need ChatGPT. They need their own knowledge to be findable, and their March to be quieter than last March. That's the work AI is genuinely good at.
- $$
Internal SOP search that returns real answers
Staff ask questions in plain English. The tool searches your SOP doc and email archive, returns cited answers with the source paragraph, flags anything it isn't sure about. Stops the same five questions from hitting the senior partner every March.
- $
Client onboarding pack drafting
New client signs the engagement letter. AI generates the request list, intake checklist, and welcome email tailored to their entity type and services. Manager reviews before send.
- $$
Document classification on intake
Client emails or uploads a pile of receipts and statements. AI sorts and tags them — what's a T4, what's a vendor invoice, what's missing — into the right folder before a human touches them.
- $
Plain-English client summaries
After year-end, AI drafts a one-page client letter summarizing the return in language they understand — what changed, what to do differently next year, what to keep an eye on. Partner edits and signs.
- $$
Engagement letter and proposal drafts
Quick call with a prospect, then AI drafts the engagement letter or fixed-fee proposal pulling from your standard template and the call notes. Partner reviews and sends same-day instead of three days later.
- $$
CRA correspondence first-pass
When a CRA letter comes in, AI reads it, summarizes what's being asked, suggests the response approach, and flags the deadline. Doesn't reply for you. Just stops the letter from sitting in someone's inbox for two weeks.
How I think about this.
Things people ask before getting started.
Do we really need this, or is a ChatGPT Team plan enough?
For a lot of firms, a Team plan plus some training is genuinely the right starting point. The work I do is what comes after that — when you've realized your staff aren't asking ChatGPT, they're still asking the senior partner, because the answers live in your SOP doc and your email archive, not on the public internet. If your team isn't already using off-the-shelf tools, start there. Come back when the bottleneck is your own knowledge.
Will the AI ever send a CRA response or sign anything?
No. The CRA correspondence use case drafts a summary, suggests an approach, and flags the deadline. A partner reads it and decides what to do. Same for engagement letters and pre-auth-style narratives — drafted, never sent. The point of the build is to stop letters from sitting in someone's inbox for two weeks, not to remove the human from the legal and professional liability chain.
What does an internal SOP search tool actually cost?
For a firm of ten to twenty staff, the build I described in the accounting note ran a fraction of the $30k another shop had quoted. Typical range for this kind of internal knowledge tool is $6k to $20k depending on how messy the source documents are. Cleaning the SOP doc is often the largest single line item — more than the AI part. Annual hosting and model costs after that are usually a few hundred a month.
What happens during tax season if it breaks?
I don't ship anything in February. Builds either go live in October-November so they're hardened by the time March hits, or in May-June after season ends. If something breaks during season, the tools are designed to fail closed — staff can still do everything by hand, the AI just stops drafting. The worst case is your March looks like last March. I'd rather build that fallback in than promise it'll never break.
Is this a fit if we're a sole practitioner?
Sometimes. If you're a one-partner firm with a few staff, the document classification and client onboarding pack drafts often pay back fastest. The internal SOP search is overkill — when there's one person who knows everything, you don't need a search tool over your own brain. The plain-English client summary use case tends to be the surprise win for sole practitioners with a lot of owner-operator clients.
Don't see your situation here?
Most engagements start with a use-case nobody's built before. Tell Echo what you're actually trying to make happen.
Talk To Echo About Your Situation