Back to Details

joint-solution-blueprint

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Joint Solution Blueprint Skill

联合解决方案蓝图Skill

When to Use

适用场景

  • Launching or refreshing a co-built integration or packaged service.
  • Equipping field teams with architecture, value props, and proof points.
  • Coordinating enablement across product, marketing, and partner teams.
  • 推出或更新与合作伙伴共同构建的集成或打包服务。
  • 为现场团队提供架构、价值主张和证明要点。
  • 协调产品、营销和合作伙伴团队之间的赋能工作。

Framework

框架

  1. Use Case Definition – target persona, pain point, and success metrics.
  2. Architecture Overview – system diagram, data flows, dependencies, security notes.
  3. Value Narrative – customer outcomes, ROI proof, competitive differentiation.
  4. Go-To-Market Plays – positioning, pricing principles, launch checklist, asset library.
  5. Support & Lifecycle – roles, escalation paths, roadmap commitments.
  1. 用例定义——目标用户画像、痛点和成功指标。
  2. 架构概述——系统图、数据流、依赖关系、安全说明。
  3. 价值叙事——客户成果、ROI证明、竞争差异化优势。
  4. 上市（GTM）行动方案——定位、定价原则、启动清单、资产库。
  5. 支持与生命周期——角色、升级路径、路线图承诺。

Templates

模板

  • One-page solution brief with messaging + CTA.
  • Architecture diagram checklist.
  • Launch plan with tasks, owners, and deadlines.
  • 包含信息传递和CTA的单页解决方案简介。
  • 架构图检查清单。
  • 包含任务、负责人和截止日期的启动计划。

Tips

提示

  • Keep diagrams simple enough for sales decks, with appendix for technical deep dives.
  • Include customer stories or beta insights to increase credibility.
  • Pair with 
    build-co-sell-playbook
    so reps know how to pitch + progress deals.
  • 确保图表足够简洁，适用于销售演示文稿，可在附录中加入技术深度内容。
  • 包含客户案例或Beta版洞察以提升可信度。
  • 搭配
    build-co-sell-playbook
    使用，让销售代表了解如何推介并推进交易。