When should you use it?
- Marriage, a new child or a move makes last year's return useless as a guide
- You want a ballpark to plan spending, not a filed return
- You are comfortable running a small local web app
Not for: Replacing the preparer who signs your return; Complex situations such as business income across several states
What do you need, and what do you get?
You need
- Expected W-2 wages and withholding for each job
- Investment income: interest, dividend and gain figures
- Filing status, dependents and where you live and work
You get
- A single-page calculator with refund or balance due per jurisdiction
- A line-by-line breakdown from income to tax after credits
- Inputs saved in the browser so you can return later
How does it work, step by step?
- Describe the household preciselyState the tax year, filing status, dependents, state and city so the agent can scope the rules.
- Let it look up current tablesAllow web lookup for brackets, standard deduction and credit phase-outs, and ask it to cite where each figure came from.
- Keep tax logic separate from the screenAsk for one calculation module per jurisdiction so each can be checked on its own.
- Check edge rules you know applyTest cases such as a city tax that applies only to earned income or a credit that phases out above an income threshold.
- Use it for planning onlyCompare the estimate with your preparer's final return and adjust withholding if they differ.
The prompt
Our own prompt, inspired by Brian Donelan and written to work in Claude Code. Values in lime are placeholders.
Build a small local web app that estimates my [tax year] tax refund or amount owed for federal, [state] and [city] taxes. Household: [filing status], [number] dependents, living and working in [city]. Inputs: wages and withholding per job, interest, ordinary and qualified dividends, short and long-term gains. Look up current brackets, deductions and credit phase-outs and list the source for each. Keep each jurisdiction's math in its own module and show the full calculation path. Store inputs only in the browser.
Inspired by Brian Donelan: How Claude Code Built My Tax Refund Calculator — And Saved Me $300. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Tax tables change yearly; rerun the lookup each year instead of trusting last year's code.
- A browser app that stores data locally is fine for planning, but do not put account numbers or SSNs into it.
Our take
New parents in Columbus, Ohio, filing as a married couple for the first time were quoted about three hundred dollars for a refund estimate. Brian Donelan instead described the household to Claude Code, which looked up 2025 brackets and credits and built a browser calculator covering federal, Ohio and city tax that updates as inputs change. This is a sensible home use of a coding agent: the output is a planning tool, the stakes of a rough estimate are low, and he kept the professional for the signed return. The part worth copying is the structure, with one checkable module per jurisdiction and a visible computation path, so you can spot a wrong bracket instead of trusting a single number. Ask the agent to show sources for every rate, and sanity-check against a reputable online estimator before making decisions. Use it for planning only. Update tables when tax year changes. Do not file from the calculator alone.
Where the time goes back: Modeling three tax systems by hand in a spreadsheet takes hours; a described app produced the estimate quickly and can be rerun with new numbers.
FAQ
Did this replace the CPA?
What stack did the agent choose?
Source and credit
Inspired by Brian Donelan. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- How Claude Code Built My Tax Refund Calculator — And Saved Me $300
- Creator
- Brian Donelan
- Published on
- Medium
- Original date
- Jan 31, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Claude Code
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; nothing was sent, filed, purchased or published.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.