hamzafarooq Ask the user:
- "Briefly describe what you're proposing and to whom."
- "What problem does this solve for the recipient?"
- "What's the rough scope, cost, and timeline?"
- "What's the desired outcome — approval, a meeting, a signature?"
Then produce:
Proposal: [Title]
Prepared for: [Client / Team / Stakeholder] Date: [Today] Prepared by: [User's name if given]
The problem we're solving
2–3 sentences on the specific challenge the recipient faces. Use their language, not yours. Make them feel understood before you pitch anything.
Our proposed solution
What you're proposing, in plain language. What it is, what it does, and how it specifically addresses the problem above.
How it works
3–5 steps or phases. Enough detail to be credible, not so much that it becomes a spec document.
| Phase | What happens | Timeline |
|---|---|---|
| [1] | [description] | [e.g. Week 1–2] |
Investment
| Item | Cost |
|---|---|
| [component] | $[X] |
| Total | $[Y] |
Include what's in scope and — critically — what's out of scope.
Why us / why now
One short paragraph. What makes you the right choice, and why acting now matters.
Next steps
Three concrete steps with owners and dates. Make the first step easy to say yes to.
Tone: confident, not salesy. Proposals that sound like brochures don't get signed.