C4B Practice
Browse by Chapter
#39Chapter 06 — Deal Intelligence: Strategy, Negotiation & Pipeline Mastery
I need to generate a customized proposal for a deal with multiple stakeholders. Each stakeholder evaluates through a different lens. Help me build a proposal that speaks to each one.

**Deal overview:**
- Prospect: [company name and what they do]
- What we're proposing: [product/service, scope, pricing structure]
- Deal size: [value]
- Implementation timeline: [estimated]

**Stakeholder personas (who will read this proposal):**

Persona 1 — [Name, Title, e.g., CFO]:
- What they care about: [e.g., payback period, TCO, risk mitigation]
- What they fear: [e.g., cost overruns, budget surprises, poor ROI]
- Evidence that matters to them: [e.g., financial projections, case study ROI data]

Persona 2 — [Name, Title, e.g., CTO]:
- What they care about: [e.g., integration depth, migration risk, security]
- What they fear: [e.g., vendor lock-in, technical debt, disruption to current stack]
- Evidence that matters to them: [e.g., architecture diagrams, integration specs, security certifications]

Persona 3 — [Name, Title, e.g., End-User Team Lead]:
- What they care about: [e.g., ease of adoption, training timeline, daily workflow impact]
- What they fear: [e.g., another tool nobody uses, steep learning curve, workflow disruption]
- Evidence that matters to them: [e.g., user testimonials, adoption metrics from similar companies]

**Generate a proposal with:**

1. **Executive Summary** — Written for the executive sponsor. Strategic alignment, business outcomes, why now.
2. **For each persona, a dedicated section** that leads with their priorities, addresses their fears, and uses the type of evidence that resonates with them. Each section should feel like it was written specifically for that reader.
3. **ROI Section** — Financial justification with payback period, TCO comparison vs. status quo, and conservative projections. **Use only numbers I provide or flag with [NEEDS INPUT] — do not invent financial projections.**
4. **Implementation Plan** — Phased, with milestones that address each persona's concerns (CTO sees integration checkpoints, end users see training milestones, CFO sees cost gates).
5. **Risk Mitigation** — Proactively address the top fear of each persona.

Use the prospect's language from our conversations, not generic marketing language. If they said "we're drowning in manual processes," write "manual processes" not "operational inefficiencies."
Claude for Sales
Claude for Sales

These prompts are excerpts from the book. Get the full collection with explanations and use cases.

Get the Book