Proposal outline from discovery notes

Why it works

• Architect framing pushes structure over sales poetry.
• Messy notes plus success picture keep the outline buyer led.
• No invented prices or timelines protect trust.
• Scope, out of scope, and open questions prevent silent assumptions.
• Thirty day success picture anchors the proposal to a near outcome.

Common mistake

Adding deliverables that sound nice but were never requested on the call.

Variation for

For trades, replace scope with job phases like diagnose, repair, verify.

Same prompt, five AIs

You are my proposal architect.

Context: I ran a discovery call. Notes: [paste messy notes]. Buyer: [buyer name or role]. Company: [company]. Problem they named: [problem]. What success looks like in 30 days: [success picture]. I must not invent scope they did not ask for.

Constraints:
- Use only what appears in the notes or brackets
- No prices, no timelines you invent
- Flag gaps as Open questions
- Plain language a busy owner can skim

Output format:
1. One sentence problem summary
2. Proposed scope bullets (max 6)
3. Out of scope bullets (max 4)
4. Open questions (max 5)
5. Suggested next meeting agenda (3 lines)

Related terms