Qualify the opportunity before writing the proposal.
Confirm the client's problem, the consequence of leaving it unresolved, the decision process, and the timing. Ask what they have already tried and what would make a new approach worth considering. If the work is outside your expertise or available capacity, resolve that before you write a persuasive document.
A proposal should summarize a conversation both sides recognize. When key information is missing, send a short clarification request. Producing a longer document does not make an uncertain opportunity more qualified.
Build a scope that can be reviewed.
Write down the outcome, deliverables, exclusions, responsibilities, timeline assumptions, and review process. Distinguish the change you will work toward from the outputs you control. For example, you may control delivering a set of approved pages; you do not control the client's total revenue.
- Deliverables: What will exist when the project is complete?
- Acceptance: What criteria will the client use to review it?
- Inputs: What must the client provide, and when?
- Changes: How will extra requests affect the scope?
- Approval: Who decides, and how is that decision recorded?
Estimate the work using your own time and cost assumptions. Include review time and a realistic allowance for revisions. A fee that looks attractive before delivery may look different once those hours are included.
Give the model a bounded drafting task.
Use only information you are authorized to process. Remove sensitive details that the model does not need. Supply the verified notes and ask for a structure you can edit.
Using only the approved notes below, draft a proposal with these sections: situation, intended outcome, deliverables, exclusions, client inputs, milestones, review process, and next decision. Do not invent prices, deadlines, results, credentials, or guarantees. List missing information under Questions to resolve.
Add your notes after the instruction. Read the questions before the draft: they often reveal why the proposal is not ready. Resolve them with the client or label the assumptions explicitly.
Review facts, commitments, and buyer clarity.
Check the proposal against the discovery notes line by line. Verify names, quantities, prices, dates, and dependencies. Make sure each deliverable has a clear boundary and that the draft does not imply work you have not priced.
Next, read it as the buyer. Can they explain what they are buying, what they need to provide, how decisions happen, and what happens next? Replace jargon with concrete descriptions of the work. Remove decorative language that adds confidence without adding information.
Keep commercial and legal terms aligned with the agreement you actually use. Do not accept model-generated clauses simply because they sound formal. Get appropriate professional advice when the terms require it.
Send one next step and record the decision.
When you send the proposal, name the decision you need and offer a practical way to resolve remaining questions. Record the sent version, date, contact, and next action in your opportunity board. A follow-up date is a planning field; it does not mean a reminder was sent.
After the decision, capture the reason for a win, loss, or delay when the client provides one. Separate those facts from your interpretation. Review which questions repeated and which assumptions created friction. Use that evidence to improve discovery and the next proposal.
When the project is accepted, move the agreed scope and responsibilities into your onboarding checklist. That handoff keeps the work you sold connected to the work you deliver.
Build on this
Connect the next part of your workflow.
The AI Lead & Proposal System supports qualification, discovery, and proposal review. The member workspace helps you record opportunities and plan project margins.
Explore the Systems Stack