Gather the inputs
You need four things. The customer's request. The agreed scope. Your approved pricing. Your usual terms. Is something missing? Then it stays a question. It doesn't become a confident guess. And test with redacted examples.
Keep client notes apart from your reusable business brief. One customer's confidential details don't belong in a template you use for everyone.
Try this briefing structure
Here's what I'd type. Draft a proposal using only the scope, approved pricing and meeting notes I've given you. Use our house style. Include deliverables, exclusions, timeline and next step. Mark missing facts as questions. Don't invent dates, discounts or payment terms.
For a follow-up, ask for a short message that sums up the next step you agreed. Then ask for a separate list of anything uncertain. That way a guess can't slip into your email as a promise.
A fictional worked example
Picture a made-up consultant. Their meeting note says the client wants a reporting template. There's no deadline in the note. No price either.
A good draft describes the template and asks you to confirm timing and cost. A bad draft invents a Friday deadline and a discount. Both sound polished. Only one tells the truth. Which would you rather send? This illustrates a review rule. It's not a client result.
Review before sending
Check the recipient. The scope. The figures, dates and exclusions. The attachments and the tone. Work out totals outside the draft. Make one person responsible for approval. And keep the final version where your team can find it. Then run this list.
- Does every commercial claim have a source we approved?
- Have we included anything from another customer?
- Does the next step match what we actually discussed?
- Are draft notes and unanswered questions resolved?
Measure the complete task
Time how long your usual process takes. Then time the new one: prep, AI drafting, fixing and review. Use a few examples, including messy ones. Count the mistakes as well as the minutes.
Only automate the repeatable parts once you trust the workflow. Sending automatically is a separate decision. You'll need controls for exceptions, duplicates and customers whose situation has changed.