How to Write a Case Study for a Financial Planning or Accounting Practice (Without Overstepping Compliance)

06 August 2026·4 min read

Quick answer: Case studies are one of the most persuasive content assets a financial planning or accounting practice can publish — but they're also one of the easiest to get wrong. Use anonymised or composite clients, describe your process rather than promising a specific outcome, avoid any implication that results are typical or guaranteed, and always get compliance sign-off before publishing. Done properly, they build trust without the regulatory risk. 💖

Most financial planners and accountants avoid case studies altogether because the compliance risk feels too high — and honestly, some of the fear is justified, because the ones that do exist are often written badly. Real client names without documented consent. Specific investment returns presented like a track record. A single spectacular outcome framed as what clients can expect. Done well, a case study doesn't need any of that to be persuasive — it just needs to show your process and judgement clearly. 💖

What most practices get wrong

The biggest mistake is presenting a single outstanding result as though it's representative, without any balancing context — this can create a misleading impression even if every individual fact stated is true. The second is using identifiable client details (name, photo, specific numbers) without clear, documented consent. The third is describing outcomes in a way that implies a guarantee ("we grew their portfolio by X%") rather than describing the advice process and reasoning that led to a decision.

The Compliant Case Study Structure:

Use a composite or anonymised client ("a client in their early 50s approaching retirement") unless you have specific, documented consent to identify a real individual
Situation: the client's starting position and the problem they came to you with, described generally
Process: the advice process, questions you asked, options you considered — this is where your expertise actually shows, and it carries far less compliance risk than outcome claims
Outcome, framed carefully: describe what changed for the client's situation, not a specific percentage return or guaranteed figure, and include a general disclaimer that results depend on individual circumstances
Sign-off checklist: compliance/AFSL review, written consent if any real client details are used, and a standard disclaimer added to every published case study

Accounting firm, business restructure: An accounting firm wanted to showcase a business restructure that saved a client significant tax. Rather than quoting the exact dollar figure as a headline claim, the case study focused on the process — how the firm identified the structuring opportunity, what was considered, and why — with a general note that outcomes depend on each business's specific circumstances. It read as more credible, not less, because it demonstrated judgement rather than just a number.

Financial planning practice, retirement client: A practice wanted to feature a retirement planning client but didn't have documented consent to use real identifying details. We built the case study around a composite “client in their late 50s, transitioning to retirement” instead, describing the actual advice process used with several real clients in similar situations — achieving the same trust-building effect without any consent or identification risk.

SMSF specialist practice: An SMSF specialist practice wanted to highlight a complex compliance resolution for a client. The case study described the specific compliance issue in general terms, the steps taken to resolve it, and the general category of outcome (avoided a compliance breach) without disclosing any client-identifying or overly specific financial detail — useful for prospective clients facing a similar issue, without any real consent complexity.

How to actually write and publish one

Choose whether you're using a real, consenting client or a composite — default to composite unless consent is clean and documented
Draft using the Situation → Process → Outcome structure above, keeping outcome language general
Add a standard disclaimer to every case study: results depend on individual circumstances, past performance isn't indicative of future results, general information only
Send to your compliance team or AFSL for review before publishing — every time, not just the first one
Keep a record of the sign-off and any consent documentation in case it's ever queried

💡 Process beats outcome, every time. Prospective clients aren't actually looking for a promise of a specific result — they're looking for evidence you'll handle their situation with the same judgement and care. A case study that shows your thinking is more persuasive, and far lower risk, than one leaning on a headline number.

Mistakes to avoid

Presenting one outstanding result as typical, without balancing context
Using real client details without documented consent
Language that implies a guaranteed or typical outcome
Skipping compliance review because "it's just a blog post"
No disclaimer on the published piece

Please note: general information, not legal or compliance advice — requirements differ between AFSLs and practices, so always check current ASIC guidance and your own compliance obligations before publishing client case studies.

Frequently asked questions

Can I ever use a real client's name and photo?

Yes, with clear, documented, informed consent — the client needs to understand exactly what will be published and where. Even then, many practices still choose to keep specific financial figures general, since consent to be named doesn't automatically make every possible outcome claim compliant.

Isn't a composite client less persuasive than a real one?

Not necessarily — what makes a case study persuasive is specificity of situation and clarity of process, not whether the name is real. A well-written composite grounded in genuine advice scenarios reads just as credibly as a named client, without the consent overhead.

Do the same rules apply to accountants and financial planners equally?

The regulatory frameworks differ — financial planners sit under AFSL and ASIC requirements, while accountants have their own professional body standards — so the specific rules aren't identical. The general principles here (avoid implying guaranteed outcomes, get consent, get sign-off) apply broadly to both, but always check the specific requirements for your profession and licensee.