Explain a Tax Concept to a Confused Client
Explain a tax concept in plain English with a concrete example and decision implication.
This prompt turns an intimidating tax concept into a plain-English explanation aimed at one specific client and their specific situation, ending with the decision or action it actually implies. It's built for the moment a small business owner's eyes glaze over and you need them to understand a concept well enough to make a call — not pass an exam. The required structure (concept, why it matters to them, concrete numbers, the decision, the common mistake) keeps the explanation grounded in their reality instead of a textbook.
You are a CPA explaining [TAX CONCEPT] to a small business owner client. Their situation: [SITUATION]. Goal: they understand it well enough to make a decision. Format: (1) the concept in 2 sentences, (2) why it matters for their situation specifically, (3) a concrete example with their kind of numbers, (4) the decision or action it implies, (5) one common mistake to avoid. No jargon without immediate translation.
What you can expect back
1. The concept (2 sentences) If you elect S-corp status, the IRS requires you to pay yourself a 'reasonable salary' - real wages for the work you do - before taking the rest as profit distributions. Salary gets hit with payroll tax; distributions don't. 2. Why it matters to you That split is the entire tax savings of going S-corp. Set the salary too low and the IRS can reclassify your distributions as wages and add penalties; set it too high and you lose the benefit. 3. Example with your numbers On ~$120k net: pay yourself, say, a $70k reasonable salary (taxed for Social Security/Medicare) and take ~$50k as distributions (no payroll tax). That can save roughly $7-8k a year versus paying self-employment tax on the full $120k. 4. The decision this implies Decide whether the savings justify the added cost of payroll filings and a tax return for the S-corp - usually yes around your income level. 5. Common mistake to avoid Don't pay yourself a token $20k salary to dodge payroll tax. That's the single biggest audit trigger here.
Illustrative example — your results will vary by tool and inputs.
Get sharper results
- 01Put real numbers from the client's situation in [SITUATION] — '$120k net, one owner, no employees' produces a usable example, while 'a small business' produces a vague one.
- 02Add the client's actual question or worry ('they think S-corp is free money') so the explanation corrects the specific misconception they're carrying.
- 03Ask it to flag where the answer depends on facts you haven't given ('this changes if you have employees') so you don't hand over advice that's true only by accident.
- 04Have it write at a stated reading level ('explain like they have no finance background') to keep the jargon-translation rule honest.
- 05Because tax rules change and vary by state, ask it to note the year and any state-specific caveats, and verify specifics against current IRS guidance before relying on numbers.
Adapt it for your case
Ask for the explanation formatted as a short email you can send directly, with a warm opening and a clear 'let's discuss' close.
Have it explain the concept as a side-by-side ('staying sole prop vs electing S-corp') with the tax outcome of each at their income level.
Add 'use one plain everyday analogy' so an especially numbers-averse client gets an intuitive mental model alongside the example.
Common questions
Can I rely on the numbers it gives?
Treat them as illustrative. Tax rates, thresholds, and rules change yearly and vary by state, so verify any specific figures against current IRS guidance and the client's full facts before advising.
Will it oversimplify and mislead the client?
It can, which is why the prompt asks it to flag the decision and a common mistake. Add 'note any important exceptions' so the simplification doesn't quietly drop a caveat that matters to this client.
How do I keep it from using jargon?
The prompt already requires immediate translation of any term. Reinforce it by naming the client's background ('no accounting knowledge') so the model calibrates the language accordingly.
You may also need
Follow Up On a Late Invoice (Firmly, Politely)
Generate a tiered follow-up email for a late invoice — friendly, firm, or final notice.
Push Back on Scope Creep Without Damaging the Relationship
Draft a collaborative, firm reply that handles scope creep without damaging the relationship.
Restructure a Document for Better Flow
Reorganize a document for logical flow while preserving all original content.
De-escalate an Angry Customer Support Email
Draft an empathetic, ownership-taking reply to an angry customer that's human, not corporate.