The workflows, prompts, and hands-on labs to move faster, with the compliance side handled honestly so you can use it on real client work.
Copy-paste workflows for the work you already do, built from what 300+ accountants told us they actually use AI for. Each one is skimmable in five minutes and usable the same day.
The most common use, ~39% of accountants.
Draft client emails, follow-ups, and plain-English explanations in seconds, in your voice.
Open the module~31% of accountants.
Structure the question, organize the analysis, and draft the memo, with every citation verified against primary source.
Open the module~28% of accountants.
Turn rough notes into clean internal memos and client-ready deliverables.
Open the module~17% of accountants.
Automate the repetitive steps and package them into reusable skills you run again and again.
Open the module~15% of accountants.
Pull and tidy data out of messy statements, PDFs, and spreadsheets.
Open the modulePractice on realistic (synthetic) data and feel where AI helps and where your judgment is non-negotiable. The principle throughout: code computes, AI drafts, you decide.
Tap Ask the Lab in the corner any time. Answers are grounded in the research below and cited, so you get a straight read instead of vibes, even when the rule itself is still unsettled.
No one has the final word on AI in tax and accounting yet. So we did the research: here is what is settled, what is not, and exactly what we do in the meantime. The goal is not to be the authority, it is to be the place that is transparent about it.
The cited bedrock: IRC §7216/§6713, the FTC Safeguards Rule and the WISP, the AICPA Code, SSTS, and Circular 230.
Read the foundationWhen AI use needs written client consent, broken down component by component, with every cite verified against the regulation.
Open the frameworkThe "but I heard…" claims about AI and §7216 that practitioners get wrong, each checked against the primary source.
See what people get wrongThere is no AI-specific §7216 ruling yet, and the proposed Circular 230 change is not final. Here is exactly what is unsettled, and why the conservative read is the safe one until the bodies that govern us weigh in.
See what is still openThe plain-English rules that keep AI use defensible: anonymize or use an approved tool, verify before you rely, and you sign.
Read the guardrailsStrip a client's identity from a note before any of it goes to AI, entirely in your browser.
Open the redactorReady-to-adapt consent language for when taxpayer information goes to a third party, including an AI service.
Get the templateThe honest, cited answer to the question every firm asks before touching AI, written first-person by a practicing CPA.
Read the essaySoon: share the protocols you use and what you are hearing back from your state board, and see how other firms are handling the same gray areas. For now, bring it to Ask the Lab.
Want the deep version? The 12-lesson Regulatory Study Guide walks the full stack: §7216, FTC/WISP, AICPA, Circular 230, state law, and local models.
Can this client data go into AI? A four-question read with the governing cite.
Strip client identity from a note before AI sees it, in your browser.
Look up a tool or a task and what to verify before client data goes in.
The §7216, WISP, and SSTS jargon, decoded.
A weekly community of accountants building with AI, out in the open. Share what you are building, see what others are, and work the compliance side out together.
Join the AI Lab