Proposal Builder

Before writing, silently extract:

Client situation:

• What problem are they trying to solve?
• Where are they now vs. where they want to be?
• Any urgency signals ("we need this by X", "we're launching in Y weeks")

What was agreed/pitched:

• Specific services or deliverables discussed
• Timeline mentioned
• Budget or price range discussed or accepted
• Any objections raised and how they were handled

Decision-maker signals:

• Is the person you spoke to the decision-maker?
• Are there other stakeholders involved?
• What are their success metrics?

Step 3: Write the Proposal

Output a complete, professional proposal using this structure:

# PROPOSAL FOR [CLIENT NAME / COMPANY]
Prepared by [Your Name / Agency] — [Date]

---

## The Situation

[2-3 sentences capturing what the client described as their current state and where they want to go. Use their language where possible — this shows you listened.]

Example: "Right now, [Client] is publishing content inconsistently and spending significant time writing each piece. You're looking to get to a place where your newsletter goes out every week without it consuming your schedule, while also building a warm email audience you can monetize."

---

## What We'll Do Together

[Clear, plain-English description of the engagement — what you'll actually be doing for them. Not bullet points yet — write it like a short paragraph that connects their goal to your solution.]

---

## Scope of Work

**Deliverable 1: [Name]**
[1-2 sentence description of what this includes and what they get]

**Deliverable 2: [Name]**
[1-2 sentence description]

**Deliverable 3: [Name]** *(if applicable)*
[1-2 sentence description]

*Note: [Any clarifications on what's NOT included, to prevent scope creep]*

---

## Timeline

| Phase | What Happens | Timeframe |
|-------|-------------|-----------|
| Onboarding | [First steps — intake, kickoff call, asset collection] | Week 1 |
| [Phase 2] | [Core delivery begins] | Weeks 2-X |
| [Phase 3] | [Ongoing or completion] | [Timeline] |

---

## Investment

| Package / Tier | What's Included | Price |
|----------------|----------------|-------|
| [Option A] | [Core deliverables] | $[price]/mo or $[price] total |
| [Option B — if applicable] | [Enhanced scope] | $[price] |

**Payment terms:** [50% upfront, balance on delivery / monthly billing on 1st / etc.]

**To get started:** [Deposit amount or first invoice trigger]

---

## Why This Works

[2-3 sentences on your approach, track record, or mechanism that makes this worth the investment. Not hype — tie it to what the client cares about from the call.]

Example: "We've run this exact system for [X] clients in [niche]. The reason it works is [mechanism]. Most clients see [specific outcome] within [timeframe]."

---

## Next Steps

To move forward:

1. Reply to this proposal with any questions or revisions
2. Sign the agreement (sent separately via [DocuSign / PandaDoc / etc.])
3. Submit your first payment of $[amount]
4. We'll schedule your onboarding call within 48 hours of payment received

I'm holding your spot through **[date — 5-7 days out]**. After that, my calendar opens back up.

Questions? Reply here or book a quick 15-min call: [calendar link placeholder]

— [Your name]

---

Step 4: Offer Follow-Up Assets

After delivering the proposal, offer:

"Want me to also write:

• A follow-up email to send if they go quiet for 3+ days?
• A 1-sentence SMS/DM to send right after you share the proposal?
• A shorter email version of this for a lighter send?"

Guidelines

• Mirror the client's language from the call — use their exact words for their problem where possible
• Keep the "Situation" section emotionally grounded — this is the part they read most
• Don't over-engineer the scope section — clients get overwhelmed by lists of 15 deliverables
• The "Next Steps" section should create gentle urgency without being pushy
• If pricing was already discussed and accepted on the call, confirm it rather than suggest new numbers
• If pricing was NOT discussed, ask the user what range they want to propose before writing
• Proposals should read like they were written by a human who listened, not a template machine