Back to Details

client-proposal-generator

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Client Proposal Generator

客户提案生成器

A production-grade consulting proposal generator that transforms a brief description into a complete, professionally formatted proposal document. This skill researches the client company for personalization, structures the proposal using proven consulting frameworks, and produces a document ready to send to a prospect.
这是一款生产级别的咨询提案生成器，可将简短描述转化为完整、格式专业的提案文档。该工具会调研客户公司以实现个性化定制，采用经过验证的咨询框架构建提案，生成可直接发送给潜在客户的文档。

What This Produces

生成成果

A single 
proposal.md
(or 
proposal-{client-name}.md
) file containing:
  1. Cover page with client name, your firm name, date
  2. Executive summary (personalized to client's situation)
  3. Understanding of the client's challenges (demonstrates you listened)
  4. Proposed approach and methodology
  5. Scope of work with deliverables
  6. Timeline with milestones
  7. Team and qualifications
  8. Investment (pricing in 3 tiers)
  9. Terms and conditions
  10. Next steps and call to action
  11. Appendix (optional: case studies, team bios, references)
将生成单个
proposal.md
（或
proposal-{client-name}.md
）文件，包含以下内容：
  1. 包含客户名称、贵司名称、日期的封面页
  2. （针对客户情况个性化的）执行摘要
  3. 对客户挑战的理解（体现你认真聆听了需求）
  4. 拟议方案与方法论
  5. 包含交付成果的工作范围
  6. 包含里程碑的时间线
  7. 团队成员及资质
  8. 投资方案（3层级定价）
  9. 条款与条件
  10. 后续步骤与行动号召
  11. 附录（可选：案例研究、团队简历、参考资料）

When to Use

使用场景

  • After a discovery call when you need to follow up with a proposal
  • When a prospect asks "can you send me a proposal?"
  • When responding to an RFP or RFI
  • When creating proposals for internal project pitches
  • When templating proposals for repeated service offerings
  • 发现性沟通后，需要跟进发送提案时
  • 潜在客户询问“能否给我发一份提案？”时
  • 响应RFP或RFI时
  • 为内部项目推介创建提案时
  • 为重复服务项目制作提案模板时

Execution Protocol

执行流程

Step 0: Gather Input

步骤0：收集输入信息

Collect from the user (or extract from conversation context):
Required inputs:
  • client_name
    -- The prospect company name
  • contact_name
    -- Primary contact (who receives the proposal)
  • problem_description
    -- What problem they need solved (even a vague description works)
  • your_company
    -- Your company/firm name (or default to what is in the user's context)
Optional inputs (will be inferred or defaulted if not provided):
  • rough_scope
    -- Any known scope details (timeline, budget range, team size)
  • your_services
    -- Description of your service offerings
  • pricing_model
    -- fixed | retainer | milestone | hourly | hybrid (default: 3-tier fixed)
  • proposal_tone
    -- consultative | enterprise | startup | technical (default: consultative)
  • include_case_studies
    -- boolean (default: false, since fabricated case studies are worse than none)
  • output_path
    -- Where to write the file (default: current directory)
  • currency
    -- USD | EUR | GBP | etc. (default: USD)
If the user gives a one-liner like "Write a proposal for Acme Corp about redesigning their data pipeline," extract what you can and infer the rest.
从用户处收集（或从对话语境中提取）以下信息：
必填输入项：
  • client_name
    -- 潜在客户公司名称
  • contact_name
    -- 主要对接人（提案接收人）
  • problem_description
    -- 他们需要解决的问题（即使描述模糊也可）
  • your_company
    -- 贵司/事务所名称（若未提供则使用用户语境中的默认值）
可选输入项（若未提供则自动推断或使用默认值）：
  • rough_scope
    -- 已知的范围细节（时间线、预算范围、团队规模）
  • your_services
    -- 贵司服务内容描述
  • pricing_model
    -- fixed | retainer | milestone | hourly | hybrid（默认：3层级固定定价）
  • proposal_tone
    -- consultative | enterprise | startup | technical（默认：consultative）
  • include_case_studies
    -- 布尔值（默认：false，因为虚构案例比没有案例更糟）
  • output_path
    -- 文件输出路径（默认：当前目录）
  • currency
    -- USD | EUR | GBP | 其他（默认：USD）
如果用户仅提供一句话，例如“为Acme Corp撰写一份关于重新设计其数据管道的提案”，则提取可用信息并推断其余内容。

Step 1: Client Research

步骤1：客户调研

Research the client company to personalize the proposal. This is what separates a template from a real proposal.
调研客户公司以实现提案个性化，这是区分模板化提案与真实定制提案的关键。

1a. Web Research

1a. 网络调研

Use WebSearch and Bash to gather:
  1. Company overview -- What they do, industry, size, location, founding year
  2. Recent news -- Funding, acquisitions, product launches, leadership changes (last 6 months)
  3. Technology signals -- Job postings (indicate tech stack and pain points), GitHub repos, tech blog posts
  4. Industry context -- Current trends and challenges in their sector
  5. Competitors -- Who they compete with (positions your proposal in context)
  6. Company values/culture -- From their about page, mission statement, LinkedIn
使用WebSearch和Bash收集以下信息：
  1. 公司概况 -- 业务范围、行业、规模、所在地、成立年份
  2. 近期动态 -- 融资、收购、产品发布、领导层变动（近6个月）
  3. 技术信号 -- 招聘信息（体现技术栈与痛点）、GitHub仓库、技术博客文章
  4. 行业背景 -- 其所在领域的当前趋势与挑战
  5. 竞争对手 -- 竞品情况（帮助定位提案）
  6. 公司价值观/文化 -- 来自官网关于我们页面、使命宣言、LinkedIn

1b. Structure Research Findings

1b. 整理调研结果

Organize findings into a research brief:
undefined
将调研结果整理为调研简报：
undefined

Client Research Brief: [Client Name]

客户调研简报: [客户名称]

Company Overview

公司概况

  • Industry: [industry]
  • Size: [employee count, revenue if public]
  • Founded: [year]
  • HQ: [location]
  • What they do: [1-2 sentence description]
  • 行业: [行业]
  • 规模: [员工数量，上市公司可包含营收]
  • 成立时间: [年份]
  • 总部: [地点]
  • 业务内容: [1-2句话描述]

Recent Developments

近期动态

  • [Event 1 -- date, significance]
  • [Event 2 -- date, significance]
  • [事件1 -- 日期、重要性]
  • [事件2 -- 日期、重要性]

Industry Context

行业背景

  • [Trend 1 affecting their sector]
  • [Trend 2 affecting their sector]
  • [Challenge specific to their industry]
  • [影响其行业的趋势1]
  • [影响其行业的趋势2]
  • [其行业特有的挑战]

Technology Signals

技术信号

  • [Hiring for X suggests need for Y]
  • [Using tool Z based on job postings]
  • [招聘X岗位暗示需要Y能力]
  • [根据招聘信息判断使用工具Z]

Competitive Landscape

竞争格局

  • [Competitor 1 -- what they do differently]
  • [Competitor 2 -- market positioning]
  • [竞品1 -- 差异化业务]
  • [竞品2 -- 市场定位]

Personalization Hooks

个性化切入点

  • [Specific detail to reference in the executive summary]
  • [Pain point to mirror in the problem statement]
  • [Opportunity to connect your solution to their recent news]

If web research is unavailable or returns limited results, note this and proceed with what is available. A slightly less personalized proposal is better than no proposal.
  • [可在执行摘要中引用的具体细节]
  • [可在问题陈述中呼应的痛点]
  • [将解决方案与其近期动态关联的机会]

如果网络调研不可用或结果有限，记录此情况并基于现有信息继续推进。一份略有欠缺的个性化提案也比没有提案好。

Step 2: Problem Framing

步骤2：问题框架构建

Transform the user's problem description into a structured problem statement. Use the consulting standard of framing problems in terms of business impact.
将用户提供的问题描述转化为结构化的问题陈述。采用咨询行业标准，从业务影响角度构建问题框架。

2a. Problem Decomposition

2a. 问题分解

Break the stated problem into:
  1. Root problem -- The fundamental issue (e.g., "legacy data pipeline cannot scale")
  2. Symptoms -- Observable manifestations (e.g., "reports take 6 hours to generate")
  3. Business impact -- Revenue, cost, risk, opportunity cost (e.g., "delays decision-making by 24 hours")
  4. Stakeholders affected -- Who feels the pain (e.g., "operations team, executive leadership, customers")
  5. Urgency drivers -- Why now (e.g., "upcoming product launch requires real-time analytics")
将提出的问题分解为以下部分：
  1. 核心问题 -- 根本问题（例如：“遗留数据管道无法扩展”）
  2. 症状表现 -- 可观察到的现象（例如：“报告生成需6小时”）
  3. 业务影响 -- 收入、成本、风险、机会成本（例如：“决策延迟24小时”）
  4. 受影响的利益相关者 -- 受困扰的群体（例如：“运营团队、高管层、客户”）
  5. 紧迫性驱动因素 -- 为何是现在（例如：“即将到来的产品发布需要实时分析能力”）

2b. Challenge Articulation

2b. 挑战阐述

Write 3-5 bullet points that demonstrate understanding of the client's situation. These will become the "Understanding Your Challenges" section. The tone should be: "We have listened, we understand the stakes, here is what we heard."
撰写3-5个要点，体现对客户处境的理解。这些内容将成为“对您挑战的理解”部分。语气应体现：“我们认真聆听了，理解其中利害，以下是我们的总结。”

Step 3: Solution Design

步骤3：解决方案设计

Design the proposed approach based on the problem and your services.
基于问题与贵司服务内容设计拟议方案。

3a. Methodology Selection

3a. 方法论选择

Choose or adapt a methodology framework:
Problem TypeMethodologyStructure
Technology modernizationDiscovery -> Design -> Build -> Migrate -> Optimize5-phase waterfall with agile sprints
Process improvementAssess -> Map -> Redesign -> Implement -> MeasureLean/Six Sigma influenced
Strategy / advisoryResearch -> Analysis -> Recommendations -> RoadmapClassic consulting engagement
Product developmentDiscovery -> Prototype -> Build -> Test -> LaunchAgile product development
Data / analyticsAudit -> Architecture -> Build -> Validate -> DeployData engineering lifecycle
Organizational changeAssess -> Design -> Pilot -> Roll Out -> SustainChange management framework
选择或调整合适的方法论框架：
问题类型方法论结构
技术现代化Discovery -> Design -> Build -> Migrate -> Optimize5阶段瀑布模型+敏捷迭代
流程改进Assess -> Map -> Redesign -> Implement -> Measure受Lean/Six Sigma影响的框架
战略/咨询Research -> Analysis -> Recommendations -> Roadmap经典咨询项目框架
产品开发Discovery -> Prototype -> Build -> Test -> Launch敏捷产品开发框架
数据/分析Audit -> Architecture -> Build -> Validate -> Deploy数据工程生命周期
组织变革Assess -> Design -> Pilot -> Roll Out -> Sustain变革管理框架

3b. Phase Definition

3b. 阶段定义

For each phase, define:
Phase N: [Phase Name] -- [Duration]

Objective: [What this phase achieves]

Activities:
- [Activity 1]
- [Activity 2]
- [Activity 3]

Deliverables:
- [Deliverable 1 -- concrete, tangible]
- [Deliverable 2]

Milestone: [What marks the end of this phase]

Client involvement: [What you need from the client during this phase]
为每个阶段定义以下内容：
阶段N: [阶段名称] -- [时长]

目标: [本阶段要达成的成果]

活动:
- [活动1]
- [活动2]
- [活动3]

交付成果:
- [交付成果1 -- 具体、有形]
- [交付成果2]

里程碑: [标志本阶段结束的节点]

客户参与度: [本阶段需要客户提供的支持]

3c. Deliverables Inventory

3c. 交付成果清单

Create a master list of all deliverables across all phases:
#DeliverablePhaseFormatDescription
D1Discovery Report1PDF/PresentationCurrent state assessment with findings
D2Solution Architecture2Technical DocumentProposed system design
D3Implementation Plan2Project PlanDetailed execution roadmap
...............
创建所有阶段的交付成果总清单：
#交付成果阶段格式描述
D1发现报告1PDF/演示文稿现状评估及调研结果
D2解决方案架构2技术文档拟议系统设计
D3实施计划2项目计划详细执行路线图
...............

Step 4: Timeline Construction

步骤4：时间线构建

Build a realistic project timeline.
构建合理的项目时间线。

4a. Duration Estimation

4a. 时长估算

Project TypeTypical DurationNotes
Quick audit / assessment2-4 weeksDiscovery + report
Strategy engagement4-8 weeksResearch heavy, lighter implementation
Technology implementation8-16 weeksBuild-heavy, requires testing
Full transformation12-24 weeksMulti-phase, organizational change
Ongoing advisory / retainer3-12 monthsMonthly cadence
项目类型典型时长说明
快速审计/评估2-4周发现阶段+报告
战略咨询4-8周侧重调研，实施内容较少
技术实施8-16周侧重开发，需要测试
全面转型12-24周多阶段，涉及组织变革
持续咨询/ retainer3-12个月月度节奏

4b. Timeline Format

4b. 时间线格式

undefined
undefined

Timeline

时间线

Overview

概述

  • Start date: [upon contract execution / specific date]
  • End date: [estimated completion]
  • Total duration: [X weeks/months]
  • 开始日期: [合同签署后/具体日期]
  • 结束日期: [预计完成日期]
  • 总时长: [X周/月]

Phase Timeline

阶段时间线

PhaseDurationStartEndKey Milestone
1. Discovery2 weeksWeek 1Week 2Discovery Report delivered
2. Design3 weeksWeek 3Week 5Architecture approved
3. Build6 weeksWeek 6Week 11MVP deployed to staging
4. Test & Refine2 weeksWeek 12Week 13UAT sign-off
5. Launch & Handoff1 weekWeek 14Week 14Production deployment
阶段时长开始结束关键里程碑
1. 发现2周第1周第2周交付发现报告
2. 设计3周第3周第5周架构获批
3. 开发6周第6周第11周MVP部署到预发布环境
4. 测试与优化2周第12周第13周用户验收测试通过
5. 上线与交接1周第14周第14周生产环境部署

Key Dates

关键日期

  • Kickoff meeting: [Week 1, Day 1]
  • Mid-project review: [Week 7]
  • Go/no-go decision: [Week 12]
  • Final delivery: [Week 14]
  • 启动会议: [第1周，第1天]
  • 项目中期评审: [第7周]
  • 继续/终止决策点: [第12周]
  • 最终交付: [第14周]

Dependencies and Assumptions

依赖关系与假设

  • Client provides access to systems and stakeholders within 5 business days of kickoff
  • Client designates a project sponsor and day-to-day point of contact
  • Feedback on deliverables provided within 3 business days
  • Timeline may adjust based on discovery findings (Phase 1)
undefined
  • 客户在启动后5个工作日内提供系统访问权限与利益相关者对接
  • 客户指定项目发起人与日常对接人
  • 交付成果反馈在3个工作日内提供
  • 时间线基于上述假设；客户输入延迟可能导致时间线延长
undefined

Step 5: Team Composition

步骤5：团队组成

Present the team that will deliver the work.
介绍将负责交付工作的团队。

5a. Role Framework

5a. 角色框架

Standard consulting team structure:
RoleResponsibilityTypical Allocation
Engagement LeadClient relationship, strategy, quality10-20%
Project ManagerTimeline, coordination, status reporting25-50%
Senior ConsultantAnalysis, recommendations, architecture50-100%
ConsultantResearch, implementation, documentation100%
AnalystData gathering, support tasks, QA50-100%
Subject Matter ExpertDomain expertise, reviews10-25% (as needed)
标准咨询团队结构：
角色职责典型投入占比
项目负责人客户关系、战略、质量管控10-20%
项目经理时间线、协调、状态汇报25-50%
高级顾问分析、建议、架构设计50-100%
顾问调研、实施、文档撰写100%
分析师数据收集、支持任务、质量保证50-100%
领域专家领域专业知识、审核10-25%（按需）

5b. Team Section Format

5b. 团队部分格式

undefined
undefined

Your Team

您的专属团队

We will staff this engagement with a focused team combining strategic vision and hands-on execution.
[Name], Engagement Lead [Title at your company]. [X] years of experience in [relevant domain]. Previously led similar engagements for [types of companies]. Responsible for overall engagement quality and strategic alignment. Allocation: [X]% throughout the engagement.
[Name], Senior Consultant [Title]. Specializes in [relevant specialization]. [Brief relevant background]. Responsible for [key deliverables]. Allocation: [X]% during Phases [N-N].
[Continue for each team member]

Note: If the user has not provided team details, use placeholder names and roles. Never fabricate specific people or credentials.
我们将为该项目配备一支兼具战略视野与实操能力的专注团队。
[姓名]，项目负责人 [贵司职位]。拥有[X]年[相关领域]从业经验。 曾为[企业类型]领导过类似项目。 负责项目整体质量与战略对齐。 投入占比：[X]%（全程）。
[姓名]，高级顾问 [职位]。专注于[相关专业领域]。 [简短相关背景]。 负责[关键交付成果]。 投入占比：[X]%（第[N-N]阶段）。
[为每位团队成员继续撰写]

注意：如果用户未提供团队详情，使用占位姓名与角色。切勿虚构具体人员或资质。

Step 6: Pricing

步骤6：定价

Build the pricing section with 3 tiers. The 3-tier model is a proven approach: the middle tier is the target, the lower tier makes the middle look reasonable, the upper tier captures ambitious buyers.
构建包含3个层级的定价部分。3层级模型是经过验证的有效方法：中间层级为目标选项，下层让中间层看起来更合理，上层覆盖有更高需求的客户。

6a. Pricing Model Selection

6a. 定价模型选择

ModelWhen to UseStructure
Fixed Fee (3 tiers)Well-defined scope, predictable work3 packages at set prices
RetainerOngoing advisory, fractional rolesMonthly fee for X hours/month
Milestone-BasedLong projects, client wants to de-riskPayments tied to deliverable acceptance
Hourly/Daily RateUndefined scope, staff augmentationBlended or role-based rates
HybridMix of defined deliverables + ongoing supportFixed for phases + retainer for support
Default to 3-tier fixed fee unless the user specifies otherwise.
模型使用场景结构
固定费用（3层级）范围明确、工作可预测3个固定价格套餐
Retainer持续咨询、 fractional角色月度费用，包含每月X小时服务
里程碑式长期项目、客户希望降低风险付款与交付成果验收挂钩
小时/日费率范围不明确、人员扩充混合或基于角色的费率
混合模式既有明确交付成果又有持续支持阶段固定费用+支持retainer
除非用户指定，否则默认使用3层级固定费用模型。

6b. Three-Tier Pricing Framework

6b. 三层级定价框架

undefined
undefined

Investment

投资方案

We have structured three engagement options to align with your priorities and budget.
我们设计了三种合作选项，以匹配您的优先级与预算。

Option A: [Tier Name -- e.g., "Foundation"]

选项A: [层级名称 -- 例如：“基础版”]

[Price]
Best for: [One sentence describing who this is for]
Includes:
  • [Deliverable 1]
  • [Deliverable 2]
  • [Deliverable 3]
Duration: [X weeks] Team: [Roles involved]
[价格]
最适合：[一句话描述目标客户]
包含：
  • [交付成果1]
  • [交付成果2]
  • [交付成果3]
时长：[X周] 团队：[涉及角色]

Option B: [Tier Name -- e.g., "Accelerator"] (Recommended)

选项B: [层级名称 -- 例如：“加速版”]（推荐）

[Price]
Best for: [One sentence -- this should be the most compelling]
Everything in Foundation, plus:
  • [Additional deliverable 1]
  • [Additional deliverable 2]
  • [Additional deliverable 3]
  • [Additional deliverable 4]
Duration: [X weeks] Team: [Roles involved]
[价格]
最适合：[一句话 -- 这应是最具吸引力的选项]
包含基础版的所有内容，外加：
  • [额外交付成果1]
  • [额外交付成果2]
  • [额外交付成果3]
  • [额外交付成果4]
时长：[X周] 团队：[涉及角色]

Option C: [Tier Name -- e.g., "Transformation"]

选项C: [层级名称 -- 例如：“转型版”]

[Price]
Best for: [One sentence describing the full-scope option]
Everything in Accelerator, plus:
  • [Premium deliverable 1]
  • [Premium deliverable 2]
  • [Premium deliverable 3]
  • [Ongoing support component]
Duration: [X weeks] Team: [Full team]
undefined
[价格]
最适合：[一句话描述全范围选项]
包含加速版的所有内容，外加：
  • [高级交付成果1]
  • [高级交付成果2]
  • [高级交付成果3]
  • [持续支持服务]
时长：[X周] 团队：[完整团队]
undefined

6c. Pricing Guidelines

6c. 定价指南

Consulting rate benchmarks (adjust based on market, geography, and specialization):
Firm SizeJunior RateSenior RatePrincipal Rate
Solo / boutique$150-250/hr$250-400/hr$400-600/hr
Mid-market firm$200-350/hr$350-500/hr$500-800/hr
Big 4 / enterprise$300-500/hr$500-800/hr$800-1500/hr
To calculate tier prices:
  • Estimate hours per role per phase
  • Apply blended rate
  • Tier 1: 60-70% of full scope price
  • Tier 2: 100% of target price (the one you want them to buy)
  • Tier 3: 140-160% of target price
If the user provides a budget range, reverse-engineer the tiers to bracket that range.
咨询费率基准（根据市场、地域与专业领域调整）：
事务所规模初级费率高级费率负责人费率
个人/精品事务所$150-250/小时$250-400/小时$400-600/小时
中型事务所$200-350/小时$350-500/小时$500-800/小时
四大/企业级$300-500/小时$500-800/小时$800-1500/小时
计算层级价格：
  • 估算每个阶段每个角色的工时
  • 应用混合费率
  • 层级1：全范围价格的60-70%
  • 层级2：目标价格的100%（希望客户选择的选项）
  • 层级3：目标价格的140-160%
如果用户提供预算范围，反向推导层级以匹配该范围。

6d. Payment Terms

6d. 付款条款

undefined
undefined

Payment Terms

付款条款

  • 50% upon contract execution
  • 25% at mid-project milestone ([specific milestone])
  • 25% upon final delivery acceptance
OR (for retainer):
  • Monthly invoicing, net 30
  • 3-month minimum commitment
  • 60-day cancellation notice
OR (for milestone):
  • Payment upon acceptance of each phase deliverable
  • Invoiced within 5 business days of milestone acceptance
  • Net 30 payment terms
undefined
  • 合同签署后支付50%
  • 项目中期里程碑支付25%（[具体里程碑]）
  • 最终交付验收后支付25%
或（针对retainer）：
  • 月度开票，账期30天
  • 最少3个月承诺期
  • 60天取消通知期
或（针对里程碑式）：
  • 每个阶段交付成果验收后付款
  • 里程碑验收后5个工作日内开票
  • 账期30天
undefined

Step 7: Terms and Conditions

步骤7：条款与条件

Standard consulting terms to include:
undefined
包含标准咨询条款：
undefined

Terms and Conditions

条款与条件

Scope

范围

This proposal covers the scope described herein. Work outside this scope will be addressed through a change order process with separate estimation and approval.
本提案涵盖此处描述的工作范围。超出本范围的工作将通过变更单流程处理，包含单独估算与审批。

Change Orders

变更单

Changes to scope, timeline, or deliverables will be documented in a written change order signed by both parties before work begins on the change.
对范围、时间线或交付成果的变更将记录在书面变更单中，经双方签署后再开展变更工作。

Intellectual Property

知识产权

All deliverables become the property of [Client Name] upon final payment. [Your Company] retains the right to use general methodologies, frameworks, and non-proprietary tools developed during the engagement.
所有交付成果在最终付款后归[客户名称]所有。 [贵司]保留在项目中开发的通用方法论、框架及非专有工具的使用权。

Confidentiality

保密

Both parties agree to keep confidential all proprietary information shared during the engagement. A separate NDA can be executed upon request.
双方同意对项目期间共享的所有专有信息保密。可应要求签署单独的NDA。

Assumptions

假设

  • Client will provide timely access to stakeholders, systems, and data as needed
  • Client will designate a single point of contact for day-to-day coordination
  • Feedback on deliverables will be provided within [3-5] business days
  • Timeline estimates assume the above; delays in client inputs may extend the timeline
  • 客户将按需及时提供利益相关者、系统与数据的访问权限
  • 客户将指定单一日常对接人
  • 交付成果反馈将在[3-5]个工作日内提供
  • 时间线估算基于上述假设；客户输入延迟可能导致时间线延长

Validity

有效期

This proposal is valid for 30 days from the date of submission.
本提案自提交之日起30天内有效。

Limitation of Liability

责任限制

[Your Company]'s total liability shall not exceed the total fees paid under this engagement.
undefined
[贵司]的总责任不超过本项目下支付的总费用。
undefined

Step 8: Assemble and Write the Proposal

步骤8：组装并撰写提案

Combine all sections into the final document. Apply professional formatting.
将所有部分组合成最终文档，应用专业格式。

Document Structure

文档结构

markdown
undefined
markdown
undefined

[Proposal Title]

[提案标题]

[Your Company] | Proposal for [Client Name]

[贵司名称] | 为[客户名称]准备的提案

Prepared for: [Contact Name], [Contact Title] Prepared by: [Your Name/Team], [Your Company] Date: [Current Date] Proposal #: [Auto-generated: PROP-{YYYY}-{NNN}] Valid through: [Date + 30 days]
提交给: [联系人姓名], [联系人职位] 提交人: [您的姓名/团队], [贵司名称] 日期: [当前日期] 提案编号: [自动生成: PROP-{YYYY}-{NNN}] 有效期至: [日期+30天]

Table of Contents

目录

  1. Executive Summary
  2. Understanding Your Challenges
  3. Proposed Approach
  4. Scope and Deliverables
  5. Timeline
  6. Your Team
  7. Investment
  8. Terms and Conditions
  9. Next Steps
  10. Appendix (if applicable)
  1. 执行摘要
  2. 对您挑战的理解
  3. 拟议方案
  4. 范围与交付成果
  5. 时间线
  6. 您的团队
  7. 投资方案
  8. 条款与条件
  9. 后续步骤
  10. 附录（如适用）

1. Executive Summary

1. 执行摘要

[2-3 paragraphs. Personalized to the client. Reference their specific situation, recent news, or industry challenges from the research phase. State the problem, the proposed solution at a high level, and the expected outcome. End with a confidence statement.]
[2-3段。针对客户个性化定制。引用调研阶段获取的客户具体情况、近期动态或行业挑战。陈述问题、拟议方案的高层级内容及预期成果。结尾表达信心。]

2. Understanding Your Challenges

2. 对您挑战的理解

[This section mirrors the client's pain points back to them, demonstrating that you have listened and understand the stakes. Use the problem framing from Step 2. 3-5 bullet points or short paragraphs, each addressing a specific challenge.]
[本部分呼应客户的痛点，体现您认真聆听并理解其中利害。使用步骤2构建的问题框架。3-5个要点或短段落，每个针对一个具体挑战。]

3. Proposed Approach

3. 拟议方案

[Methodology overview. Explain your approach in terms the client can understand. Avoid jargon. Focus on the "why" behind each phase. Include a visual timeline or phase diagram if possible.]
[方法论概述。用客户易懂的语言解释您的方案。避免行话。重点阐述每个阶段的“原因”。如有可能，包含可视化时间线或阶段图。]

Phase 1: [Phase Name]

阶段1: [阶段名称]

[Description, activities, deliverables]
[描述、活动、交付成果]

Phase 2: [Phase Name]

阶段2: [阶段名称]

[Description, activities, deliverables]
[Continue for all phases]
[描述、活动、交付成果]
[为所有阶段继续撰写]

4. Scope and Deliverables

4. 范围与交付成果

In Scope

包含范围

[Bullet list of everything included]
[所有包含内容的要点列表]

Out of Scope

排除范围

[Explicit list of what is NOT included -- this prevents scope creep]
[明确列出不包含的内容 -- 这可防止范围蔓延]

Deliverables Summary

交付成果摘要

#DeliverablePhaseFormat
[Table from Step 3c]
#交付成果阶段格式
[来自步骤3c的表格]

5. Timeline

5. 时间线

[Timeline from Step 4]
[来自步骤4的时间线]

6. Your Team

6. 您的团队

[Team section from Step 5]
[来自步骤5的团队部分]

7. Investment

7. 投资方案

[Pricing section from Step 6]
[来自步骤6的定价部分]

8. Terms and Conditions

8. 条款与条件

[Terms from Step 7]
[来自步骤7的条款]

9. Next Steps

9. 后续步骤

To move forward:
  1. Select your preferred option (A, B, or C)
  2. Schedule a follow-up call to discuss any questions or adjustments
  3. Sign the agreement -- We will send a formal engagement letter based on your selected option
  4. Kick off -- We can begin within [X business days] of signed agreement
We are excited about the opportunity to partner with [Client Name] on this initiative. Please do not hesitate to reach out with questions.
[Your Name] [Your Title] [Your Email] [Your Phone]
推进流程：
  1. 选择您偏好的选项（A、B或C）
  2. 安排跟进会议以讨论任何问题或调整
  3. 签署协议 -- 我们将根据您选择的选项发送正式项目函
  4. 启动项目 -- 签署协议后[X个工作日]内可开始
我们很荣幸有机会与[客户名称]合作推进此项目。如有任何问题，欢迎随时联系。
[您的姓名] [您的职位] [您的邮箱] [您的电话]

Appendix

附录

A. About [Your Company]

A. 关于[贵司名称]

[Brief company overview -- 1 paragraph]
[简短公司概况 -- 1段]

B. Relevant Experience

B. 相关经验

[2-3 brief case study summaries, IF the user has provided real ones. NEVER fabricate case studies -- omit this section if no real examples are available.]
[2-3个简短案例研究摘要，仅当用户提供真实案例时。 切勿虚构案例研究、团队简历或资质。]

C. Glossary

C. 术语表

[Define any technical terms used in the proposal, if the audience is non-technical]
undefined
[定义提案中使用的技术术语（若受众为非技术人员）]
undefined

Step 9: Quality Check

步骤9：质量检查

Before delivering, verify:
  • Client name is correct and consistent throughout
  • Contact name is correct
  • Company research is accurate (no hallucinated facts)
  • All sections are present and complete
  • Pricing tiers are internally consistent (each tier adds to the previous)
  • Timeline is realistic (phases add up, dependencies make sense)
  • No placeholder text remains (no 
    [TODO]
    or 
    {variable}
    markers)
  • Tone matches the selected style (consultative, enterprise, startup, technical)
  • Terms and conditions are reasonable
  • Out-of-scope section is present (prevents expectation mismatch)
  • Next steps are clear and actionable
  • No fabricated case studies, team bios, or credentials
  • Dates are current (proposal date, validity period)
  • Currency is correct
  • Document reads well end-to-end (no jarring transitions between sections)
交付前，验证以下内容：
  • 客户名称在整个文档中正确且一致
  • 联系人名称正确
  • 公司调研内容准确（无虚构事实）
  • 所有部分完整且存在
  • 定价层级内部一致（每个层级在之前层级基础上增加内容）
  • 时间线合理（阶段时长总和正确，依赖关系合理）
  • 无占位文本残留（无
    [TODO]
    或
    {variable}
    标记）
  • 语气符合所选风格（consultative、enterprise、startup、technical）
  • 条款与条件合理
  • 排除范围部分存在（防止预期不符）
  • 后续步骤清晰且可执行
  • 无虚构案例研究、团队简历或资质
  • 日期为当前日期（提案日期、有效期）
  • 货币正确
  • 文档通读流畅（各部分过渡自然）

Step 10: Deliver and Summarize

步骤10：交付与总结

  1. Write the file to the specified output path
  2. Present a summary to the user:
undefined
  1. 将文件写入指定输出路径
  2. 向用户呈现总结：
undefined

Proposal Generated

提案已生成

File: proposal-acme-corp.md Client: Acme Corp (attention: Jane Smith) Type: Technology modernization proposal Pricing tiers:
  • Foundation: $X
  • Accelerator: $Y (recommended)
  • Transformation: $Z Timeline: 14 weeks (Accelerator tier) Word count: ~3,200 words
文件: proposal-acme-corp.md 客户: Acme Corp（对接人：Jane Smith） 类型: 技术现代化提案 定价层级:
  • 基础版: $X
  • 加速版: $Y（推荐）
  • 转型版: $Z 时间线: 14周（加速版） 字数: ~3,200字

Personalization Applied

应用的个性化内容

  • Referenced their recent Series B funding
  • Addressed industry-specific compliance requirements
  • Tailored approach to their current tech stack (Node.js + PostgreSQL)
  • 引用了其近期B轮融资
  • 提及了行业特定合规要求
  • 根据其当前技术栈（Node.js + PostgreSQL）调整了方案

Review Recommendations

审核建议

  • Verify team member names and bios before sending
  • Confirm pricing aligns with your rate card
  • Consider adding a case study if you have a relevant one
  • The "Out of Scope" section may need adjustment based on your discovery call notes
undefined
  • 发送前验证团队成员姓名与简历
  • 确认定价与贵司费率卡一致
  • 如有相关案例，考虑添加
  • “排除范围”部分可能需要根据发现性沟通记录调整
undefined

Proposal Tone Variants

提案语气变体

Consultative (Default)

Consultative（默认）

  • Partner language ("we will work together to...")
  • Questions woven in ("have you considered...?")
  • Empathetic problem framing
  • Moderate formality
  • 合作伙伴式语言（“我们将共同协作以...”）
  • 融入问题（“您是否考虑过...？”）
  • 共情式问题框架
  • 中等正式度

Enterprise

Enterprise

  • Formal language throughout
  • Risk mitigation emphasis
  • Governance and compliance focus
  • Reference to established methodologies by name
  • Higher perceived authority
  • 全程正式语言
  • 强调风险缓解
  • 关注治理与合规
  • 提及知名方法论名称
  • 更高的权威感

Startup

Startup

  • Direct and energetic
  • Speed and iteration emphasis
  • Lean methodology references
  • Budget-conscious framing
  • Practical over polished
  • 直接且充满活力
  • 强调速度与迭代
  • 引用Lean方法论
  • 关注预算的框架
  • 实用优先于精致

Technical

Technical

  • Architecture diagrams and system design
  • Technical trade-off analysis
  • Detailed technology recommendations
  • Less business context, more implementation detail
  • Aimed at technical decision-makers
  • 架构图与系统设计
  • 技术权衡分析
  • 详细技术建议
  • 较少业务背景，更多实施细节
  • 针对技术决策者

Pricing Calibration by Engagement Type

按项目类型校准定价

Engagement TypeTier 1 RangeTier 2 RangeTier 3 Range
Strategy / advisory (4-8 weeks)$15K-30K$30K-60K$60K-100K
Technology assessment (2-4 weeks)$10K-20K$20K-40K$40K-75K
Implementation (8-16 weeks)$50K-100K$100K-200K$200K-400K
Full transformation (12-24 weeks)$100K-200K$200K-500K$500K-1M+
Monthly retainer$5K-10K/mo$10K-20K/mo$20K-50K/mo
These are calibration ranges, not fixed prices. Adjust based on:
  • Client company size and budget
  • Geographic market
  • Your firm's positioning and reputation
  • Complexity of the specific engagement
  • Competitive landscape for this deal
项目类型层级1范围层级2范围层级3范围
战略/咨询（4-8周）$15K-30K$30K-60K$60K-100K
技术评估（2-4周）$10K-20K$20K-40K$40K-75K
实施（8-16周）$50K-100K$100K-200K$200K-400K
全面转型（12-24周）$100K-200K$200K-500K$500K-1M+
月度retainer$5K-10K/月$10K-20K/月$20K-50K/月
这些是校准范围，而非固定价格。根据以下因素调整：
  • 客户公司规模与预算
  • 地域市场
  • 贵司定位与声誉
  • 具体项目的复杂度
  • 该项目的竞争格局

Error Handling

错误处理

IssueResponse
No client name providedAsk before proceeding -- this is the one required field
Minimal problem descriptionGenerate a proposal with broader framing; flag sections that need client input
Web research returns nothingProceed without personalization, note it, suggest the user add details
User provides no pricing guidanceUse mid-market rates from the calibration table
Scope is extremely vagueCreate a "Discovery Phase" as the first tier, full engagement as tiers 2-3
User asks for a one-page versionGenerate an executive summary version (Section 1 + pricing + next steps)
User wants a different format (PDF, DOCX)Generate the markdown and suggest using a PDF/DOCX conversion skill
Client is a competitorWarn the user (in case it is accidental) but proceed if confirmed
问题响应
未提供客户名称继续前询问用户 -- 这是唯一必填字段
问题描述极少生成范围更广的提案；标记需要客户输入的部分
网络调研无结果不使用个性化内容继续推进，记录此情况并建议用户添加细节
用户未提供定价指导使用校准表中的中型市场费率
范围极其模糊将“发现阶段”作为第一层，完整项目作为第2-3层
用户要求单页版本生成执行摘要版本（第1部分+定价+后续步骤）
用户需要其他格式（PDF、DOCX）生成markdown文件并建议使用PDF/DOCX转换工具
客户是竞争对手警告用户（以防意外），但确认后继续推进