1. Gather the raw client context
- Discovery call transcript or notes
- Onboarding questionnaire answers
- CRM deal notes and qualification fields
- Relevant email thread snippets
- Client website, offer, pricing page, and positioning notes
- Known stakeholders, decision criteria, deadlines, and constraints
2. Build the client brief
- Client goal in one sentence
- Current pain and why now
- Business model and buyer type
- What success means in measurable terms
- Risks, constraints, and non-negotiables
- Language the client used verbatim
- Open questions that must be answered before final proposal
3. Create your Proposal Brain
- Past winning proposals by offer type
- Case studies tagged by industry, problem, and outcome
- Pricing rules and scope boundaries
- Delivery process, timeline, and handoff rules
- Common objections and your approved responses
- Claims that need proof before appearing in a proposal
4. Generate the first draft with source rules
- Tell AI which client brief and proposal examples to use
- Require every claim to point to a source note or case study
- Ask for gaps before asking for a final proposal
- Draft executive summary, scope, outcomes, timeline, pricing logic, and next step
- Separate client-facing copy from internal assumptions
5. Run the quality gate
- Remove generic AI language
- Check that the proposal names the client's real problem
- Verify pricing, dates, and deliverables against source files
- Mark all unsupported claims
- Confirm that the next step is specific and easy to accept
- Save the final proposal and review notes back into the Proposal Brain
Copy-paste starter prompt
You are my Proposal Brain.
Use only the source material I provide:
1. Client brief
2. Discovery notes
3. Past proposal examples
4. Case studies
5. Pricing and scope rules
First, identify missing information that would make the proposal risky.
Then draft a proposal with:
- Executive summary
- Client problem
- Recommended approach
- Scope and deliverables
- Timeline
- Pricing logic
- Proof points
- Risks and assumptions
- Next step
Rules:
- Do not invent claims, numbers, dates, or outcomes.
- Mark anything unsupported as [NEEDS SOURCE].
- Reuse the client's own language where it clarifies the problem.
- Keep the first draft direct, specific, and consultant-grade.What this is not
Not a blank proposal prompt
Not a replacement for sales judgment
Not permission to invent proof