proposal-writer
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseProposal Writer
提案撰写专家
Strategic expertise for crafting winning sales proposals, pricing presentations, and RFP responses that close deals.
提供打造能促成交易的获胜销售提案、定价演示和RFP响应的专业策略支持。
Philosophy
核心理念
Great proposals don't describe your product. They describe your buyer's future success.
The best sales proposals:
- Lead with outcomes, not features — Buyers care about their results, not your capabilities
- Make the decision easy — Remove friction, objections, and confusion
- Tell a story — Context → Challenge → Solution → Success
- Respect the reader's time — Every section earns its place
优秀的提案不是在描述你的产品,而是在描述客户的未来成功。
最佳销售提案具备以下特点:
- 以成果为导向,而非功能 — 客户关心的是他们的结果,而非你的能力
- 简化决策流程 — 消除阻力、异议与困惑
- 讲述完整故事 — 背景 → 挑战 → 解决方案 → 成功
- 尊重读者时间 — 每个章节都有存在的价值
How This Skill Works
技能运作方式
When invoked, apply the guidelines in organized by:
rules/- — Proposal architecture, components, flow
structure-* - — Executive summary, C-level communication
executive-* - — Pricing presentation, anchoring, packaging
pricing-* - — Statement of Work, deliverables, timelines
sow-* - — RFP response strategy, compliance, win themes
rfp-* - — Formatting, layout, visual hierarchy
design-* - — Competitive positioning, follow-up, negotiation
strategy-*
调用本技能时,请应用目录下按以下类别整理的准则:
rules/- — 提案架构、组件与流程
structure-* - — 执行摘要、高管层沟通
executive-* - — 定价演示、锚定策略、包装方案
pricing-* - — SOW(工作说明书)、交付成果、时间线
sow-* - — RFP响应策略、合规性、赢单主题
rfp-* - — 格式排版、布局设计、视觉层级
design-* - — 竞争定位、跟进策略、谈判技巧
strategy-*
Core Frameworks
核心框架
The Proposal Pyramid
提案金字塔
┌─────────────────┐
│ Executive │ ← Why this matters (1 page)
│ Summary │
├─────────────────┤
│ Solution & │ ← How we solve it (2-3 pages)
│ Approach │
├─────────────────┤
│ Investment & │ ← What it costs (1-2 pages)
│ Timeline │
├─────────────────┤
│ Proof & │ ← Why trust us (1-2 pages)
│ Credibility │
└─────────────────┘ ┌─────────────────┐
│ 执行摘要 │ ← 为何重要(1页)
│ │
├─────────────────┤
│ 解决方案与 │ ← 我们如何解决问题(2-3页)
│ 实施路径 │
├─────────────────┤
│ 投入与时间线 │ ← 成本明细(1-2页)
│ │
├─────────────────┤
│ 资质与案例证明│ ← 为何信任我们(1-2页)
│ │
└─────────────────┘Proposal Types by Deal Stage
按交易阶段划分的提案类型
| Type | Purpose | Length | Timeline |
|---|---|---|---|
| One-Pager | Early qualification | 1 page | Same day |
| Solution Brief | Mid-funnel engagement | 3-5 pages | 2-3 days |
| Full Proposal | Final presentation | 8-15 pages | 5-10 days |
| RFP Response | Formal bid | Variable | Per deadline |
| SOW | Contract scope | 3-10 pages | Post-verbal |
| 类型 | 用途 | 篇幅 | 交付周期 |
|---|---|---|---|
| 单页提案 | 早期资质审核 | 1页 | 当日交付 |
| 解决方案简报 | 中期漏斗转化 | 3-5页 | 2-3天 |
| 完整提案 | 最终演示 | 8-15页 | 5-10天 |
| RFP响应 | 正式投标 | 可变 | 按截止日期 |
| SOW | 合同范围界定 | 3-10页 | 口头确认后 |
The CLOSE Framework
CLOSE框架
Every proposal section should CLOSE:
- Context — Where the buyer is today
- Loss — What it's costing them (pain)
- Outcome — The desired future state
- Solution — How you get them there
- Evidence — Proof it works
提案的每个部分都应遵循CLOSE原则:
- Context — 客户当前处境
- Loss — 现状带来的损失(痛点)
- Outcome — 期望的未来状态
- Solution — 我们如何帮他们达成目标
- Evidence — 成功案例佐证
Pricing Presentation Matrix
定价演示矩阵
| Element | Purpose | Placement |
|---|---|---|
| Value Summary | Anchor on ROI before price | Before pricing |
| Investment Options | Give control, not ultimatum | 2-3 tiers |
| Package Comparison | Make preferred option obvious | Side-by-side table |
| Terms & Conditions | Reduce friction | After pricing |
| Next Steps | Create momentum | Final section |
| 要素 | 用途 | 位置 |
|---|---|---|
| 价值摘要 | 在报价前锚定ROI | 定价内容之前 |
| 投资选项 | 给予客户选择权,而非最后通牒 | 2-3个层级 |
| 方案对比 | 让首选方案一目了然 | 并排表格 |
| 条款与条件 | 减少决策阻力 | 定价内容之后 |
| 下一步行动 | 创造推进动力 | 最后章节 |
Proposal Win Factors
提案赢单因素
┌─────────────────────────────────────────────────────────────┐
│ PROPOSAL SUCCESS │
├─────────────────────────────────────────────────────────────┤
│ │
│ 40% — Relationship & access (built before proposal) │
│ 25% — Solution fit (do you solve the problem?) │
│ 20% — Presentation (is it compelling and clear?) │
│ 15% — Pricing (is it defensible and competitive?) │
│ │
└─────────────────────────────────────────────────────────────┘┌─────────────────────────────────────────────────────────────┐
│ 提案成功关键因素 │
├─────────────────────────────────────────────────────────────┤
│ │
│ 40% — 客户关系与对接权限(提案前已建立) │
│ 25% — 解决方案匹配度(是否能解决客户问题?) │
│ 20% — 演示效果(是否有吸引力且清晰易懂?) │
│ 15% — 定价策略(是否合理且具备竞争力?) │
│ │
└─────────────────────────────────────────────────────────────┘Proposal Components
提案核心组件
| Component | Required | Purpose | Common Mistakes |
|---|---|---|---|
| Cover Page | Yes | First impression, branding | Generic, no personalization |
| Executive Summary | Yes | Decision-maker snapshot | Too long, feature-focused |
| Understanding | Yes | Prove you listened | Assumptions, not discovery |
| Solution Overview | Yes | What you propose | Feature dump |
| Approach/Methodology | Depends | How you'll do it | Too technical |
| Timeline | Yes | When they get value | Unrealistic dates |
| Investment | Yes | Total cost of ownership | Hidden costs surface later |
| Team/About Us | Optional | Build confidence | Self-congratulatory |
| Case Studies | Recommended | Social proof | Irrelevant industry |
| Terms & Conditions | Yes | Protect both parties | Buried gotchas |
| Next Steps | Yes | Drive action | Vague, no urgency |
| 组件 | 是否必填 | 用途 | 常见误区 |
|---|---|---|---|
| 封面 | 是 | 第一印象、品牌展示 | 通用模板,无个性化定制 |
| 执行摘要 | 是 | 决策者快速概览 | 篇幅过长,以功能为导向 |
| 需求理解 | 是 | 证明你倾听了客户需求 | 基于假设,而非调研结果 |
| 解决方案概述 | 是 | 阐述你的提案内容 | 堆砌功能,无针对性 |
| 实施路径/方法论 | 可选 | 说明执行方式 | 过于技术化,客户难以理解 |
| 时间线 | 是 | 明确价值交付节点 | 时间安排不切实际 |
| 投入成本 | 是 | 总拥有成本 | 隐藏成本后续才暴露 |
| 团队/关于我们 | 可选 | 建立客户信任 | 自吹自擂,与需求无关 |
| 案例研究 | 推荐 | 社交证明 | 案例与客户行业不相关 |
| 条款与条件 | 是 | 保护双方权益 | 隐藏陷阱,未清晰说明 |
| 下一步行动 | 是 | 推动后续动作 | 表述模糊,缺乏紧迫感 |
Anti-Patterns
反模式(需避免)
- Feature dumping — Listing everything you can do vs. what they need
- One-size-fits-all — Using templates without customization
- Price-first — Showing cost before establishing value
- Competitor bashing — Direct attacks backfire; focus on your strengths
- Wall of text — No visual hierarchy, hard to scan
- Jargon overload — Internal terminology the buyer doesn't know
- Missing next steps — Proposal ends with no clear action
- Over-promising — Timelines and outcomes you can't deliver
- Ghosting — No follow-up strategy after sending
- 功能堆砌 — 罗列所有能做的事,而非客户需要的内容
- 千篇一律 — 使用通用模板,未做个性化定制
- 先报价后讲价值 — 在建立价值感知前就展示成本
- 贬低竞争对手 — 直接攻击竞品会适得其反;应聚焦自身优势
- 文字墙 — 无视觉层级,难以快速浏览
- 术语过载 — 使用客户不懂的内部术语
- 缺失下一步行动 — 提案结尾无明确行动指引
- 过度承诺 — 无法兑现的时间线与成果
- 提交后失联 — 发送提案后无跟进策略