I'm Damon Millar. I'm a UK accountant, fractional CFO and business advisor, and I run a practice built on quarterly reviews and forward tax planning rather than filing last year's numbers and disappearing.

I built this library because the AI conversation in our profession keeps stalling in the same place. Everybody knows the tools can do something. Almost nobody has been shown where to point them, so the technology ends up writing newsletters while the manual work carries on exactly as it did.

The manual work is the point. That's where your team's hours go and that's where the margin is.

If you'd rather talk it through than read all of it, book thirty minutes with me.

Book a call →

How to use this

Twenty minutes, then you're running.

📋 Before anything else, download the prompt spreadsheet. Every prompt in this handbook is in it, filterable by category, frequency and review level. Read the handbook once. Work from the spreadsheet after that.

1. Open a Claude Project. One per client, or one per work type if your practice is organised that way. A Project holds files and standing instructions, so you set the context once instead of re-typing it every session.
2. Paste one of the four system prompts from the next section into the Project's custom instructions. That's the standing brief. It sets the accounting standards, the tax jurisdiction, the tone and the rules about what the model must not do.
3. Upload the source data. Trial balance, general ledger detail, aged debtors, bank CSV, whatever the task needs. Section 12 covers exporting cleanly from Xero, QuickBooks, Sage and Dext.
4. Paste a prompt from the library. Replace anything in [SQUARE BRACKETS] with your client's details.
5. Review the output. Every time. See the next page for why.

Don't start with the hardest thing you do. Start with a report you write monthly for a client you know inside out, because you'll spot a wrong answer instantly. Once you trust the pattern, move outward.

The three rules

Everything in this library depends on these. Skip them and you'll get plausible nonsense with a professional font.

Rule 1: Feed it the numbers, don't describe them