The week after the April filing deadline is often the first time a tax practice can breathe, at least until the extensions come due. Take the managing partner of a hypothetical eight-person accounting firm, finally reading the “AI readiness assessment” she paid for over the winter. It runs to 38 slides: market charts, a five-level maturity model in different colors, and a closing recommendation to “build an AI-first culture.” Not one slide mentions the hundreds of “did you get my W-2?” emails her staff answered in March.
The deck isn't wrong, exactly. It just isn't about her firm. A useful audit is narrower and far more specific, and you can tell a good one from a bad one by what's in your hands when it's over.
What an AI opportunity assessment (or audit) actually is
Think of it as a time-and-motion study with a technology lens. Someone follows real pieces of work through your business, from the moment a request arrives to the moment it's done, noting every hand-off, every re-keyed field and every stretch of waiting. Then they ask which of those steps a machine could take over safely, and which it should never touch.
It isn't a software evaluation, a strategy offsite or a sales call with homework attached. Those have their uses, but they answer different questions. The audit answers one: where, specifically, would automation save time or money in this business, and what should happen first?
The three things you should walk away with
1. A workflow map drawn from real work
The map shows how work really moves, not how the org chart says it should. It's built by following a handful of actual requests, ideally on a screen-share with the person who does the work. A good map is plain enough that your staff recognize their own day in it, and specific enough to show where the minutes go.
| Step | Who | Where | Time per client | Friction |
|---|---|---|---|---|
| Request documents | Admin | Email template | 5 min | Sent from memory; no per-client checklist |
| Chase missing items | Admin | Email and phone | 15 min over three weeks | Same 1099s requested twice |
| Rename and file uploads | Staff accountant | Portal, then shared drive | 10 min | Each “scan_003.pdf” opened to identify it |
| Compare with last year | Preparer | Prior-year return | 10 min | Missing K-1 found the week of the deadline |
The times are estimates from the people doing the work, and a good audit says so. Writing assumptions down is what lets you argue with them.
2. A scorecard you can check
Every candidate gets ranked on effort, risk and likely return, with a sentence explaining each rating. The ranking alone is the least valuable part. What you're paying for is the reasoning: when the scorecard says “high return,” you should see the assumption behind it, such as three admin hours a week from January to April, and be able to decide whether you believe it.
A good scorecard also has a column for what you already own. Accounting platforms, reservation systems and practice-management suites add automation features every year, and a fair audit checks those before suggesting anything new.
| Candidate | Effort | Risk | Return | Already covered? |
|---|---|---|---|---|
| Answer the phone during dinner service | Low | Low | High | No |
| Reply to catering inquiries the same day | Low | Low | Medium | Partly: the website form only |
| Check supplier invoices for price changes | Medium | Low | Medium | No |
| Draft replies to online reviews | Low | Low | Low | Yes: a feature in the review tool, unused |
| Forecast weekly prep quantities | High | Medium | Uncertain | Partly: POS sales reports |
3. One first project, scoped
The audit should end with one recommendation specific enough to price: the system's job, the software it plugs into, the things it must never do, who owns it on your side and the number that will show whether it worked. Here's a quick test: if two different builders could quote from it and come back with comparable numbers, it's scoped well enough.
Flowchart
How a sound audit runs
- StartInterviews with the owner and a few staff who handle the work daily
- StepFollow five to ten real requests from arrival to finish, timing each hand-off
- StepList every step that is repeated, re-keyed or stuck waiting on someone
- DecisionCan software you already pay for handle this step?YesStepNote the setting or feature to switch on; no new build neededNo
- StepScore what's left on effort, risk and return, with assumptions written out
- A personOwner reviews the scorecard and picks the first project
- DoneA written plan: map, scorecard and a one-page project scope
Before and after
Slideware vs. a useful audit
Slideware assessment
- 01Opens with industry trends and a maturity model
- 02Interviews the partners only
- 03Recommends an “AI culture” and a platform
- 04No times, no assumptions, no owner named
ResultA deck that ends up in a drawer
Useful audit
- 01Opens with five to ten real requests
- 02Talks to the people doing the work
- 03Checks what current software already does
- 04Scores candidates with written assumptions
- 05Scopes one first project tightly enough to price
ResultA plan you could hand to any builder
Red flags in an audit proposal or report
- A tool is named before your work is mapped. If the proposal already says which platform you'll buy, the conclusion was written first.
- Nobody talks to staff. Owners know the strategy; the front desk and the bookkeepers know where the hours go.
- Numbers with no working. “Save hours every week” without the counts behind it is a sales line, not a finding.
- Everything scores high. If nothing is ranked low or ruled out, it isn't really a ranking.
- The plan only works with the auditor. You should be able to act on it yourself, with another vendor or with your own staff.
- Copies of your files leave the building. An auditor needs to see how work flows, not keep your clients' documents.
Protecting client data during the audit
Accounting firms have specific reasons to care about that last flag. Sections 7216 and 6713 of the tax code carry criminal and civil penalties, respectively, for preparers who improperly use or disclose return information. The FTC's Safeguards Rule names tax preparation firms among the businesses that must keep a written information security program and oversee their service providers, and an auditor watching your workflow is a service provider for as long as the work lasts.
The practical answer is simple. Sign a confidentiality agreement before the first session. Walk through real files on a screen-share with your own staff at the controls, rather than exporting anything. Make sure the auditor's notes capture steps and times, not taxpayer details.
Restaurants hold less regulated data, but the same habits protect payroll records and supplier pricing. None of this is legal advice, and requirements differ from state to state; your attorney or state CPA society can tell you what applies.
Before you sign: free offers and the engagement letter
Software vendors, resellers and IT providers sometimes offer a free “AI assessment.” Some are genuinely useful, but many are pre-sales, and the finding tends to be that you need whatever the assessor sells. Ask two questions up front: will the report include options from other vendors, and will it say so if the answer is to change nothing? If either answer is no, treat it as a sales meeting and judge it that way.
For a paid audit, put these in the engagement letter:
- The deliverables by name: a workflow map, a scorecard with its assumptions, and one scoped first project.
- Who owns the report: you do, and you can share it with any builder.
- How data is handled: confidentiality terms, no copies of client files, and what gets deleted when the work ends.
- Whose time it needs: the hours expected from the owner and staff, so the audit doesn't collide with your busiest weeks.
- What's out of scope: building, buying or reselling anything, unless you agree to it separately.
How to prepare so the audit is worth it
You'll get more out of any audit, including one you run yourself, if you gather a few things first:
- 01A list of the software you pay for, and who actually uses each one.
- 02Two weeks of rough counts: calls, emails, web forms, invoices, or whatever arrives most.
- 03Three recent examples of work that went wrong or took far too long.
- 04An hour with the owner, plus half an hour each with a few of the staff who handle the work day to day.
- 05An answer to “what would you hand off tomorrow if you could?” from everyone on the team.
If you'd rather have someone run it, our AI consulting work follows this shape, and you keep the plan whether or not we build anything. To try a lighter version first, the five-question test takes an afternoon, and the ROI worksheet helps you check the return column yourself.