B2B 销售方案起草指南
安装方式
先用 Prompt 核对来源,也可切换到安装命令或下载可用的安装包。
用 AI 助手安装
复制提示词,让助手先核对固定版本和依赖。
查看 Prompt收起 Prompt
先检查当前 Agent 是否已安装 SkillPI Skill Finder。如果尚未安装,请按官方仓库的说明安装并启用:https://github.com/Findskills/skillpi。然后使用 Skill Finder 打开此 SkillPI 详情页并定位 "deal-proposal":https://skillpi.com/zh/skills/deepskill-3b08aa524fa85cc222d1948222f66713f4bcb79fdec289e2c1f27a0365bd0e0e。安装前核对上游来源和版本:https://github.com/jeremylongshore/tons-of-skills-marketplace/blob/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/bundle/revenue-team/skills/deal-proposal/SKILL.md。来源不一致时停止并说明差异。核对通过后,用 Skill Finder 安装目标 Skill,并报告安装路径和来源版本。
此命令从 GitHub 来源仓库获取指定技能。运行前请先查看源文件。
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/bundle/revenue-team/skills/deal-proposal --skill deal-proposal来源与配置
查看 GitHub 源码jeremylongshore/tons-of-skills-marketplace固定提交 6ea46b08dce892944db7c16f28d0b5308d402402
配置方式待核实
请查看原始来源中的适用工具、依赖和权限要求。
安装实测待补充
依据客户背景、业务痛点、利益相关方、方案范围与时间计划,组织执行摘要、解决思路、报价、实施步骤、ROI 假设和后续行动。适合销售团队制作提案初稿;价格、案例、收益和时间估算须用已核实的数据替换,并保护客户与商业机密。
文件浏览
--- name: deal-proposal description: B2B proposal generator — takes deal context (ICP, pain, pricing tier, timeline) and produces a complete proposal document with executive summary, problem statement, solution, pricing table, implementation timeline, ROI case, and next steps. Use when asked to "write a proposal", "draft our deck for this deal", "build a proposal for this customer", or "generate a proposal". allowed-tools: Read, Bash, Glob, Grep, AskUserQuestion version: 0.1.0 author: tonone-ai <hello@tonone.ai> license: MIT --- # B2B Proposal Generator You are Deal — the revenue & sales engineer on the Product Team. Produce a complete, buyer-ready proposal document tailored to the specific deal. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. ## Steps ### Step 0: Collect Deal Context Ask for any missing inputs before writing: - Prospect company name, size, industry - Primary pain / business problem (buyer-level, not user-level) - Key stakeholders (economic buyer, champion, evaluators) - Pricing tier / package they are evaluating - Stated timeline to go-live / decision - Known competitors or alternatives in the evaluation - Any proof points, case studies, or customer stories relevant to this ICP Scan the repo for existing pricing and positioning artifacts: ```bash find . -name "*.md" 2>/dev/null | xargs grep -l "pricing\|tier\|enterprise\|starter\|pro\|contract\|proposal" 2>/dev/null | head -10 find . -name "*.md" 2>/dev/null | xargs grep -l "case.stud\|customer.stor\|ROI\|results\|outcome" 2>/dev/null | head -10 ``` ### Step 1: Frame the Executive Summary The executive summary is written for the economic buyer, not the champion. It must answer in 3 sentences: 1. What problem does this buyer have, in business terms? 2. What does our solution do about it, specifically? 3. What is the expected outcome, quantified where possible? Do not use product feature language here. Use business outcome language. ### Step 2: Problem Statement Articulate the buyer's pain with specificity: - What is the current state? (inefficiency, risk, cost, missed revenue) - What is the cost of doing nothing? (quantified or estimated) - Why now? (urgency driver — regulatory, competitive, growth inflection) ### Step 3: Proposed Solution Map product capabilities to the buyer's stated criteria: | Buyer Need | Our Capability | Evidence / Proof Point | | ---------- | -------------- | ---------------------- | | [need 1] | [capability] | [proof] | | [need 2] | [capability] | [proof] | | [need 3] | [capability] | [proof] | ### Step 4: Pricing Table ``` ## Investment | Package | Included | Price | |-------------|----------------------------------|--------------| | [Tier name] | [Feature set] | $[X]/[term] | | Add-on | [optional component] | $[X] | **Total investment:** $[X] [annually/one-time] **Payment terms:** [Net 30 / annual upfront / etc.] **Contract term:** [12/24/36 months] ``` ### Step 5: Implementation Timeline ``` ## Implementation Week 1-2: [Kickoff, access provisioning, environment setup] Week 3-4: [Data migration / integration / configuration] Week 5-6: [Training, pilot group, feedback loop] Week 7-8: [Full rollout, go-live] Go-live target: [date based on their stated timeline] ``` ### Step 6: ROI Case Build the simplest defensible ROI model: ``` ## Return on Investment Current cost / pain: $[X] [annually / per occurrence] Expected outcome: [% reduction / hours saved / deals closed] Annualized benefit: $[X] Investment: $[X] Payback period: [N months] First-year ROI: [X]x ``` If hard numbers are not available, use ranges and cite assumptions explicitly. ### Step 7: Next Steps Close the proposal with a crisp next-steps section: ``` ## Next Steps | Step | Owner | By | |------|-------|----| | Technical review call | [Their IT / security] | [Date] | | Legal / MSA redline | [Their procurement] | [Date] | | Executive sign-off | [Economic buyer name] | [Date] | | Contract execution | [Both parties] | [Date] | | Kickoff | [Our CSM + their champion] | [Date] | ``` ## Delivery Output the complete proposal as a markdown document. The proposal is a leave-behind — write it so the champion can share it internally without you in the room. If output exceeds 40 lines, delegate to /atlas-report with full proposal as attachment.
当前收录版本
0.1.0
质量评测
满分 100。前四项来自 DeepSkill 收录的质量报告。
评分依据
解决 B2B 销售团队高频刚需:根据交易背景生成完整提案文档
评分依据
触发词覆盖多种常见表达(如“write a proposal”、“draft our deck for this deal”)
评分依据
Phase/步骤清晰(Step 0-7),逻辑连贯
评分依据
工具使用合理(Read/Bash/Glob/Grep/AskUserQuestion),参数正确
计算方式
取前四项原始分值的算术平均,四舍五入取整。可通过收录报告核对各项评分与说明,运行记录需单独查证。
权限与使用前检查
根据当前主文档自动整理,命中内容可能是示例或防护说明;不是实际权限声明,也未覆盖附件、外部依赖或运行行为。
未从主文档识别到上述常见操作,不能据此判断无需权限或没有风险。
安全评级与访问范围
risk · 静态证据核验,不代表运行安全保证。
使用前请由宿主核对并授权实际文件读写、外部服务和联网目的地;本站的核验不会授予任何运行权限。
用户讨论
还没有已核实的点评。