When should you use it?
- You draft proposals, project plans, deal reviews or requirements from CRM records, estimates and call notes
- AI drafts have slipped in plausible numbers or dates that nobody could trace
- Several systems hold overlapping data and they do not always agree
Not for: Brainstorming or marketing copy, where inference and opinion are the point; Teams without reliable records to draft from; the output will be mostly open questions; Skipping review: high-impact documents still need a named person to approve them
What do you need, and what do you get?
You need
- The source records: CRM export, scoping estimates, SOW or contract, call notes and your document template
- The document type and audience, internal or customer
- Who signs off before the draft is shared
You get
- A draft in your template where each statement cites the record it came from
- A conflicts list showing both values and their sources whenever records disagree
- An open-items section for anything not confirmed, with no estimate standing in for a missing figure
- A freshness check noting sources whose values have not changed in a long time
How does it work, step by step?
- Gather the recordsExport or attach the CRM entry, estimates, contract terms and call notes for this one client or deal.
- Set the rulesTell the AI to use only those records, cite a source for each line and avoid words such as likely or probably.
- Surface conflictsWhere two records disagree, both values and their sources go into a conflicts list for you to settle.
- Label what is missingUnconfirmed dates, numbers or scope items appear as open items, never as estimates dressed up as facts.
- Check freshnessAsk it to note when each source's values last changed, not just when the record was touched.
- Sign offA named person reviews and approves before the document reaches a customer or becomes a commitment.
The prompt
Our own prompt, inspired by Antonio Perrone and written to work in Claude, Claude Cowork and ChatGPT. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Draft a {document_type} for {client_or_deal} for {audience}, using only the attached records: {record_list}. Follow my template: {template}. Rules: 1) Every statement must cite the record it came from in brackets. If no record supports it, leave it out. 2) If records disagree on a number, date or scope item, do not choose. Add both values with their sources to a 'Conflicts' list at the top. 3) Anything not confirmed goes in an 'Open items' section. Never fill a gap with an estimate or words such as likely. 4) For each source, say when its values last changed, if you can tell, and flag any that look stale. Mark the draft 'For review by {approver}' and do not send or share it.
Inspired by Antonio Perrone: LinkedIn post: three rules for AI-drafted client documents without guesswork. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- A record's last-updated date can change without any value changing. Judge freshness by the data itself.
- Citations only help if someone checks a few of them. Spot-check before sign-off.
- Long source packs can push the model to summarize loosely. Draft one document per deal or client.
Our take
The most damaging AI drafting errors in client work are rarely obvious mistakes; they are confident, reasonable-looking numbers that came from nowhere. Perrone's three rules target exactly that. Requiring a source for each line makes invention visible, refusing to let the model pick between conflicting records keeps the decision with the person accountable for it, and an explicit open-items section stops estimates from passing as facts. His example of a feed whose timestamps refreshed daily while the values stayed frozen for a year is a useful warning for anyone pulling from CRMs or synced spreadsheets. Our one addition is a freshness check on values, not dates, which we built into the prompt. The rules cost a little polish, since early drafts read sparse. In our dry run with a fictional IT services deal (a CRM record, a scoping estimate, a SOW and two call notes), the draft deal review cited a source on every line, flagged that the SOW said 120 hours while the estimate said 140, listed the go-live date as open because no record confirmed it, and noted that the CRM's hourly rate had not changed since last year.
Where the time goes back: Drafts arrive with their sources, conflicts and gaps already marked, so review becomes a quick check instead of re-verifying every line by hand.
FAQ
Which tools does this need?
Will the drafts be shorter?
Source and credit
Inspired by Antonio Perrone. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- LinkedIn post: three rules for AI-drafted client documents without guesswork
- Creator
- Antonio Perrone
- Published on
- Original date
- Oct 22, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Claude
- AI dry run
- Oct 28, 2026: passed. Dry-run tested by our AI test agent on sample input. Every line sourced, conflict surfaced instead of chosen, gaps named, stale value flagged, sign-off kept.
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 28, 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.