Prepare client proposals without inventing commitments

Separate confirmed inputs from assumptions

Record the buyer’s need, requested deliverables, dates, approved fees and responsible decision-maker. Put unclear scope in an open-questions section. A plausible price or delivery date is still unapproved if it was not supplied.

Build a scope-first structure

Use objective, deliverables, client inputs, assumptions, exclusions, review gates and next step. The draft should distinguish what is included from optional work. If pricing is missing, show To be confirmed rather than allowing a model to fill it in.

Fictional example

A fictional web designer receives a request for a five-page site. The brief confirms pages and an enquiry form but no maintenance or advertising. A useful outline names those as separately scoped items and asks who supplies approved copy. It cannot promise launch timing until inputs and review dates are agreed.

Approve commercial facts before sending

The service owner checks scope, price, payment terms and responsibilities. AI drafting is not approval of a contract. Keep a source copy of the approved offer and compare the final proposal against it. Use the follow-up to ask for the next decision, not to invent urgency.

Qualify the brief before drafting

Ask what the buyer needs, why the request exists, who approves the scope and which facts are confirmed. A request for a “complete website” does not identify pages, languages, forms, content ownership, integrations or maintenance. Use a requirements table with Confirmed, To clarify and Out of scope columns. The clarification step may solve more of the problem than generating a polished proposal immediately.

Maintain one approved commercial source

Store the current offer definition, approved fee rules, exclusions and payment terms in a controlled source. The draft should use that source rather than an old example proposal whose price happens to look plausible. Date the version and identify the owner. If a discount needs approval, the assistant can flag it as a question; it cannot approve it. This also reduces inconsistency when a proposal, follow-up email and presentation are prepared together.

Build a proposal that makes the next decision easier

Start with the buyer’s objective in their language. Follow with concrete deliverables, client inputs, milestones, dependencies, review rounds, fees if confirmed and exclusions. End with the decision required to proceed. Do not make the document longer simply because the tool can. A proposal should make scope assessable. For example, “five agreed pages and one enquiry form” is easier to assess than “a complete digital transformation solution”.

A reusable drafting instruction

Use: “Prepare a proposal outline from the following approved brief. Preserve prices and terms exactly. If a required commercial field is missing, label it To be confirmed and add it to the questions section. Separate included deliverables, client responsibilities, assumptions and exclusions. Do not claim an agreement has been signed, payment received or capacity reserved. Finish with a concise follow-up email asking for the next decision.” Paste only information permitted for the chosen tool and account.

Compare the final draft against the source

The reviewer should check every number, deliverable, deadline, legal entity and payment detail against the approved brief. Check whether polished wording quietly expanded the scope: “support included” could imply an ongoing obligation that was never agreed. Check consistency across the proposal and follow-up. Where legal provisions are involved, use your actual approved terms and the appropriate reviewer; drafting assistance is not legal validation.

Measure proposal usefulness

Track time from a complete brief to a reviewed proposal, correction count, repeated clarification questions and whether the buyer understood the scope. A faster first draft is not useful if it creates more negotiation or operational rework. Start with anonymised or fictional samples, include incomplete briefs and confirm the draft consistently flags gaps. The useful output is a reviewed proposal grounded in your offer, not a document that merely sounds persuasive.

Before you use the result

• Separate approved facts from assumptions.
• Identify missing information and the person who owns it.
• Check prices, promises and consequential fields.
• Review the work in the format the audience will actually see.

Questions to ask next