If you run an accounting practice, your real product isn't tax returns. It's the body of context you've built around each client — the prior years, the audit trail, the email where the client mentioned the rental property that didn't appear on the 1099, the IRS letter from 2023 you knew you'd need again. That context is the reason a client stays with you instead of switching to whoever their cousin uses. It's also the thing that goes most stale during tax season, because you don't have time to re-load it for every client.
AI notes earn their keep when they hold that context for you and surface the right slice of it on demand. Not "ask AI a tax question." Ask the agent: what's the relevant history on this client, what changed this year, what does my own working file from last year say about how I handled the same issue. That's the version of AI that fits a CPA workflow. Adjacent professional-services workflows like AI notes for lawyers follow the same client-file shape — and on the regulated-data side, AI notes for compliance and audit preparation goes deeper on the audit-trail mechanics.
A client file that's actually a file
The shape that works best for accountants is one top-level page per client, with sub-pages for engagement letter, prior-year notes, current-year working file, correspondence log, and any open advisory questions. Capy supports unlimited page nesting, so you can let complex clients sprawl into ten sub-pages — one per entity, one per K-1, one per rental property — without picking a shape in advance.
The client file lives in your vault as plain markdown. That matters because the agent can read across all of it at once. When a client calls in March asking why their refund is smaller than last year, you don't have to load five tabs. You ask the agent: pull last year's working file, this year's, and the engagement letter, and explain the variance in one paragraph. The agent reads the actual files and writes the actual answer.
Tax-season triage without losing the thread
The hardest week of tax season isn't the volume of returns. It's the interruptions. A client texts a question while you're heads-down in another return. You have to context-switch into their file, find the answer, write back, and rebuild your concentration on the original return. The interruption tax is the killer.
A working setup: keep an inline database called "client questions" inside your main vault page, with rows for client name, question, status, due date. The database lives directly in the page via the :::database::: directive, so you don't have to switch to a separate tracker. When a question comes in, you log it in fifteen seconds and stay in the return you were in. At the end of the day, you batch through the open questions with the agent: read each client's file, draft a response that cites their actual numbers, queue them up for review.
The batching is the real win. You're not doing twenty context switches; you're doing one focused hour where the agent has loaded the context for you and you're just confirming the answers.
Working with PDFs the IRS sends, finally
A lot of the document load in an accounting practice is PDF — IRS notices, K-1s, 1099s, brokerage statements, audit reports. Most of those PDFs are not searchable in any useful way until you've manually pulled the numbers out.
Drop the PDF on a Capy page. It auto-converts to markdown via docstrange, which means the agent can read every line of a fifty-page brokerage statement, find the wash-sale adjustments, and write a summary you can drop into the working file. Same for IRS notices: the agent reads the notice, identifies the section of code being cited, and pulls the relevant prior-year file from the client's vault for cross-reference. You're not OCR-ing in your head at midnight.
PDF→markdown also makes "chat with this notice" work as a real workflow rather than a demo. The conversion runs once when you upload; from then on, the agent treats the PDF as searchable text indistinguishable from any other note.
Drafting compliance memos without starting blank
Most compliance memos in a small practice are rewrites of memos you've already written. The new client's S-corp election question is the same question you wrote up for three other clients in 2024. The reasonable-comp analysis is the same analysis with different numbers. The hardest part is finding the prior memos and adapting them.
Tell the agent: read the four memos in my "memos" folder that touch on reasonable compensation, draft a v1 memo for this client using the structure of the strongest one, swap in this client's numbers from their working file. You get a draft that sounds like your prior memos because it descends from your prior memos. You spend the saved time on the parts that genuinely are new — the specific facts of the client's situation and any judgment call that doesn't have a clean precedent in your file. This in-place editing is the Cursor-for-documents idea — an agent acting on your file, not a chat window you copy-paste out of.
The 27-tool agent that ships with Capy can search across the vault, read individual files, and write into a new page in one instruction. You don't pipeline the steps yourself.
Recording calls with speaker labels for the audit trail
Client calls are part of the work product. If a client tells you on a call that a piece of equipment was placed in service in March, that's information you're obligated to act on, and three months later when the IRS asks how you knew, you'd like to be able to point at the source.
Record the call inside Capy. The transcript comes back with speaker diarization — "Speaker 1: …" labels — so you can see who said what, not just a wall of text. Park the recording and transcript on the client's page. When you write the working file later, you can quote the client's own words directly and cite the date of the call. If the client ever disputes the treatment, you have the audit trail in the same place as the return.
This isn't legal advice on retention; talk to your professional standards body about how long you have to keep recordings and what disclosures clients are entitled to. The mechanical capability is here. The compliance posture is yours to set.
Year-end planning that doesn't restart from zero
The hardest part of year-end planning isn't the projections themselves. It's loading enough context per client to know what's worth raising. Every November you re-read every client's file to figure out who has a Roth conversion question, who has carryover basis to think about, who's likely to trip an AMT issue.
A vault makes that scan a lot less work. Ask the agent: across all my client files, find every client who had a capital-gains spike in the last two years, has a charitable-giving pattern in their notes, and hasn't been flagged for a Roth conversation. The agent reads the files and gives you a short list. You pick the ones worth a conversation and draft outreach.
The agent doesn't replace your judgment about who needs a call. It just makes the scan that surfaces the candidates a fraction of the work it used to be.
What Capy isn't, for accountants
Worth being clear on the shape. Capy is single-user — one CPA, one vault. If you want a multi-user firm workspace where every senior, manager, and intern shares files with role-based permissions, this isn't that. It's also cloud-hosted; your vault sits on our servers, not on your machine. For most solo and small-practice accountants, the cloud-vault shape with one integrated agent is a strict upgrade over the current reality of files-in-Drive plus a tax-software inbox plus a chat tool. If your professional rules require keeping data on your own hardware, this isn't the right fit and we'd rather you know up front.
A small first test
The cheap way to see whether this fits your practice is to load one complex client's last two years of working files, the relevant correspondence, and any IRS notices on file, and then ask Capy to write a one-page summary of where that client stands going into this season. If the summary is materially better than the one you'd write from memory, you've got a sense of what the agent is doing for you across the rest of your book. If you're a fractional executive working across several clients, the per-client vault shape generalizes to your engagement portfolio.
Try Docapybara free. Load one client and see whether the summary surprises you.