Use case #22 · CPA
Head of tax with no tech background prototypes a client onboarding flow and tax organizer with Claude Code
- Client comms
- Intermediate
- Claude, Claude Code
- Source checked · Journal of Accountancy article
The short version
What they did
Wozena, the firm’s head of tax, built a working prototype of a new client onboarding flow and tax organizer using Claude and Claude Code. The article does not say whether the prototype is in use with clients.
Result (as claimed)
The article says that “in a few hours, Susan Wozena, CPA, the firm’s head of tax — with no tech background — created a working prototype of a new onboarding and tax organizer using Claude and Claude Code.”
Prompt
I’m the tax lead at an accounting firm, using Claude Code to prototype onboarding and a tax organizer for individual clients. I’ll provide [our reviewed question list], [which answers trigger each follow-up] and [the document checklist].
1. Build a single HTML file I can open and click through in a browser. Group contact details, household details, income sources and life events clearly.
2. Show follow-up questions and document requests only when the relevant screening answer calls for them. Use fictional data and sample upload controls.
3. Give me a table of every question and the answer that makes it appear, plus a short test checklist.Keep the wording simple and friendly. Ask me about missing rules instead of inventing tax questions. Don’t store answers or upload real files. This is a prototype for checking the questions and flow before deciding how to build a client version.
Do it yourself
These steps are my suggested way in, not Susan Wozena’s setup.
Level: Intermediate for a clickable prototype with Claude Code. Drafting the question list in a chat is Beginner.
What you need
- Your current organizer or engagement intake checklist.
- A chat assistant such as Claude, and Claude Code or a similar coding agent for the prototype.
- Fake client data only. No real client details go into a prototype.
Start simple
- Paste your current organizer questions into a chat. Ask it to sort them into yes/no screening questions and the follow-ups each one unlocks.
- Review the list. Cut what you never use and add what you always chase clients for.
- Paste the case’s Prompt with your reviewed list, and ask for a single HTML file you can open in a browser.
- Click through it as three fake clients: a W-2 renter, a retiree, and a household with a side business.
- Write down every question that showed when it shouldn’t, or didn’t show when it should.
Take it further
- Use Claude Code to turn the prototype into a small app with saved answers and a document checklist per client.
- Map each question to the return line or form it feeds, so staff know why it is asked.
- Before any real client uses it, have someone who knows your client portal decide where it lives and where uploads are stored.
Check your work
- Compare the follow-up logic with your own checklist. The AI will add plausible questions you don’t need and miss state-specific ones.
- Test the empty and odd paths: no answers, every answer yes, a mistyped date.
- A prototype that collects client data is a security question. Keep it on fake data until it runs on systems you trust.
Before you rely on it
- This is general information about how accountants use AI, not professional guidance for your engagements.
- You stay responsible for the work under your professional standards, including review and sign-off. An AI tool’s output is a draft, not evidence.
- Before you send client data to an AI tool, read the tool’s data and training terms, and get any client consent you need. For tax return information, that includes IRC section 7216.
Source checked. The link, author, date and quote were confirmed against the source. The result itself has not been reproduced. Prompt adapted for this library, inspired by the case. Business size: Eight people. Results are quoted as the source claimed them and never improved. Spot an error or a broken link? Email charlie@cbarmorecpa.com.