Turn meeting notes into a proposal you can review and send.

Capture the decision, not every word.

After a useful conversation, the next job is making the agreement clear. Your proposal should show that you understood the problem, explain what you will deliver and make the next decision easy.

Start with your notes, a permitted transcript or the relevant email thread. Include the client's goal, agreed scope, known constraints, decision-maker and next step. Check your assistant provider's data policy before sharing confidential material.

Separate facts from missing details.

Here is a fictional example: a team copies approved requests from email into a weekly tracking sheet. They want one place to see what needs attention. The notes say that two people will review a first version, but do not state a budget or launch date.

A useful draft can describe the current problem, proposed review process and questions still to answer. It should not invent a budget, promise a deadline or turn an early idea into an agreed requirement.

• Confirmed: requests currently arrive by email and are copied into a tracking sheet.
• Proposed: one shared view of requests and their status, to discuss with the client.
• Still to confirm: scope, price, timeline, access and who gives final approval.

Ask for a proposal built around the real scope.

Give the assistant your actual offers, prices, writing examples and notes. Ask it to keep missing information visible and distinguish what is agreed from what is proposed. Review the draft yourself before sending it.

A useful structure is the client's problem, desired outcome, recommended work, deliverables, exclusions, price, timeline and next step. Include only the sections the decision needs. More pages do not make an unclear scope clearer.

Check the numbers and promises.

Use the prices you supplied. Check quantities, totals, taxes, third-party costs, payment terms and validity dates. A polished document can still contain an expensive mistake.

Read the proposal beside the original notes. Check the recipient, responsibilities, exclusions and approval process. Do not promise savings, revenue or delivery dates just because they would make the proposal sound stronger.

• Is every included deliverable supported by the agreed scope?
• Are optional items clearly separate?
• Do totals match the actual price list?
• Are missing dates and decisions still marked for confirmation?
• Does the recipient know what to do next?

Keep the process for the next conversation.

The Proposals and Client Decks Playbook brings six skills together: proposal, quote, client deck, decision-maker summary, follow-up and case-study writing. Its shared business profile keeps your offers, prices and voice available across the process.

The current package includes a worked example and Word, Excel and PowerPoint outputs in supported setups. It works with Claude Code, Codex and the Claude app; file creation depends on the assistant and setup. Python 3 is required for files on your computer. The product page explains those requirements.

A free template or a process you write yourself may be enough. The playbook is an option when the included examples, files and repeatable routine fit your work. Follow-up drafts still need your review before they are sent.