yepai-sales-proposal
Proposal strategy, win theme development, executive summary craft, competitive positioning, and RFP response architecture.
name: yepai-sales-proposal description: >- Proposal strategy, win theme development, executive summary craft, competitive positioning, and RFP response architecture. user-invocable: false disable-model-invocation: false metadata: {"openclaw":{"emoji":"🏹"}} tags: [sales] license: MIT-0
Proposal Strategy Criteria
When building proposals, responding to RFPs, or crafting win narratives, apply these frameworks.
Win Theme Development
Every proposal needs 3-5 win themes — client-centric statements connecting your solution to the buyer's most urgent needs.
A strong win theme:
- Names the buyer's specific challenge, not a generic industry problem
- Connects a concrete capability to a measurable outcome
- Differentiates without mentioning a competitor
- Is provable with evidence
Weak: "We have deep experience in digital transformation" Strong: "Our migration framework reduces cutover risk by staging critical workloads in parallel — the same approach that kept [client] at 99.97% uptime during a 14-month transition"
Three-Act Proposal Narrative
- Act I — Understanding: Demonstrate you understand their world better than expected. Mirror their language, constraints, political landscape.
- Act II — Solution Journey: Walk evaluators through your approach mapped to Act I challenges. Win themes do heaviest work here.
- Act III — Transformed State: Quantified outcomes, timeline milestones, risk reduction. Evaluator should think about implementation, not evaluation.
Executive Summary Structure
The most critical section — many evaluators read only this. Not a summary; it's the closing argument placed first.
- Mirror the buyer's situation in their language (2-3 sentences)
- Introduce the central tension — cost of inaction or opportunity at risk
- Present your thesis — how your approach resolves it (win themes here)
- Offer proof — 1-2 evidence points (metrics, similar engagements)
- Close with the transformed state — specific expected outcome
Keep to one page. Every sentence earns its place.
Content Quality Rules
- No empty adjectives. "Robust," "cutting-edge," "world-class" are noise. Replace with specifics.
- Every claim needs evidence: a metric, case study, methodology detail, or named framework.
- Never directly criticize competitors. Frame strengths as benefits creating organic contrast.
- Pricing comes after value. Build ROI case before the buyer sees a number.
Deliverable: Win Theme Matrix
# Win Theme Matrix: [Opportunity Name]
## Theme 1: [Client-Centric Statement]
- **Buyer Need**: [Specific challenge from RFP/discovery]
- **Our Differentiator**: [Capability, methodology, or asset]
- **Proof Point**: [Metric, case study, or evidence]
- **Sections**: [Where this theme appears across the proposal]
## Competitive Positioning
| Dimension | Our Position | Competitor Approach | Our Advantage |
|-----------|-------------|-------------------|---------------|
| [Factor] | [Specific] | [Likely approach] | [Why ours matters more] |
Deliverable: Executive Summary Template
# Executive Summary
[Buyer] faces [specific challenge in their language]. [1-2 sentences demonstrating deep understanding.]
[Central tension: what happens if unaddressed — quantified.]
[Solution thesis: 2-3 sentences, win themes surface naturally.]
[Proof: One concrete evidence point.]
[Transformed state: 12-18 months post-implementation, specific and measurable.]
Download
ZIP package — ready to use
Skill Info
- Creator
- Yepai
- License
- MIT-0
- Downloads
- 0
- Published
- Oct 26, 2026
- Updated
- Oct 29, 2026