b2b-marketing-playbook

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

📦 Install

📦 安装

bash
clawhub install b2b-marketing-playbook
What you get after installing:
  • LinkedIn content cadence + DM-to-demo conversion sequences
  • Cold email templates with personalization formulas and follow-up timing
  • ABM targeting framework with pipeline velocity and CAC benchmarks

bash
clawhub install b2b-marketing-playbook
安装后你将获得:
  • LinkedIn内容发布节奏 + 从私信到演示的转化流程
  • 带有个性化公式和跟进时机的冷邮件模板
  • 包含流程速度和CAC基准的ABM目标框架

B2B Marketing Playbook — LinkedIn + Cold Email + Webinar Pipeline

B2B营销手册 — LinkedIn + 冷邮件 + 网络研讨会流程

🌍 Language / 语言: 中文 | English | 日本語 | 한국어
Three proven channels woven into one repeatable pipeline for B2B SaaS.
  • LinkedIn engine: Content cadence, engagement pods, and DM-to-demo flow
  • Cold email sequences: Subject lines, personalization, and follow-up timing
  • Webinar funnel: Topic selection, promotion, and post-webinar nurture
  • ABM layer: Account-based targeting for enterprise deals
  • Metrics dashboard: Pipeline velocity, SQL rate, and CAC benchmarks
🌍 语言: 中文 | English | 日本語 | 한국어
将三个经过验证的渠道整合为一个可重复的B2B SaaS营销流程。
  • LinkedIn引擎: 内容发布节奏、互动群组、私信到演示的转化流程
  • 冷邮件序列: 主题行、个性化设置和跟进时机
  • 网络研讨会漏斗: 主题选择、推广和会后培育
  • ABM层: 针对企业客户的基于账号的目标定位
  • 指标仪表盘: 流程速度、SQL转化率和CAC基准

Enterprise Deal Mechanics (added 2026)

企业客户交易机制(2026年新增)

Marketing gets the meeting; these rules get the money. Distilled from a multi-agent OSS commercialization retrospective:
Cash structure
  • Stage private-deployment payments 3:4:3 (or 4:4:2): tranche one when the first features go live, two at full deployment, the final slice after 3–6 months of operations.
  • 30% due the day the contract is signed — no exceptions. Write a 0.5%-per-day late penalty into the contract text itself.
  • Retain leverage: keep 1–2 features running on infrastructure you control until the final invoice clears. Disclose this before signature and codify it in the terms.
  • Chase overdue balances at the top of the customer's org chart, not with your day-to-day contact; if your champion stalls, one or two escalations to the CEO are fair game.
Scope defense
  • Split the customer's raw wishlist (SOR) from the signed commitment (SOW carrying acceptance criteria, delivery milestones, and change clauses). The SOW is signed alongside the contract, same day.
  • Every modification flows through a change-control step: written request → both project managers price the impact on cost and schedule → signed amendment. Verbal enthusiasm on calls binds nobody — paper or it didn't happen.
  • Name the acceptance sign-off person in the contract; keep records of every meeting and decision.
Negotiation posture
  • They ask for 50 features and you could build 40: commit to 10, then "stretch" to 15 as a favor. Generosity you planned is leverage; generosity they extracted is lost margin.
  • Price unwanted work high instead of declining it — the quote does the refusing.
  • Only two requests genuinely justify on-prem: data privacy and internal permission-system integration; everything else belongs on SaaS. SaaS customization → sell a license. SSO-style integrations → open your API plus standard docs and let the customer build.
Revenue arithmetic
  • $1M ARR = nine ~$100K enterprise accounts (typical split: $30–50K standard service + $30K implementation + $20K training) or five hundred $200/yr subscriptions. Run each leg as its own closed loop.
  • Partner economics: referral resellers earn 10–20%; silver tier (>$100K/yr sold) 15%; gold (>$300K) 20%. Vet any partner with three questions — what they carried before, where their customers come from, reseller vs service partner.
  • Content ratio that closes: 80% "how we made customers successful," 20% about yourself. Decks open with the buyer's pain, then the fix.
营销负责获取会面机会;这些规则负责促成交易。提炼自多Agent开源软件商业化回顾:
现金结构
  • 阶段式私有部署付款比例为3:4:3(或4:4:2):第一笔款项在首批功能上线时支付,第二笔在完全部署时支付,最后一笔在运营3-6个月后支付。
  • 合同签署当日需支付30%款项——无例外。在合同文本中明确写入每日0.5%的逾期罚款条款。
  • 保持主动权:在最终发票结清前,保留1-2个在你方控制的基础设施上运行的功能。签署合同前需披露此条款并将其纳入合同细则。
  • 向客户组织架构的高层追讨逾期款项,而非对接的日常联系人;如果你的内部支持者拖延,向CEO escalate一两次是合理的。
范围管控
  • 将客户的原始需求清单(SOR)与签署的承诺(包含验收标准、交付里程碑和变更条款的SOW)分开。SOW需与合同在同一天签署。
  • 所有修改都需经过变更控制流程:书面请求→双方项目经理评估对成本和进度的影响→签署修正案。电话中的口头承诺不具备约束力——必须落实到书面才算数。
  • 在合同中指定验收签字人;保留所有会议和决策记录。
谈判姿态
  • 客户要求50个功能,而你方可以开发40个:先承诺10个,然后“额外”提供15个作为优惠。你方主动给出的慷慨是筹码;客户强求的慷慨会损失利润。
  • 对非必要工作报高价而非直接拒绝——报价本身就是拒绝。
  • 只有两种情况真正需要本地部署:数据隐私和内部权限系统集成;其他所有需求都适合SaaS模式。SaaS定制→销售许可证。SSO类集成→开放API并提供标准文档,让客户自行开发。
营收计算
  • 100万美元ARR = 9个约10万美元的企业客户(典型拆分:3-5万美元标准服务 + 3万美元实施费用 + 2万美元培训费用)500个每年200美元的订阅客户。将每个渠道作为独立的闭环运营。
  • 合作伙伴分成:推荐经销商分成10-20%;白银等级(年销售额超10万美元)分成15%;黄金等级(年销售额超30万美元)分成20%。用三个问题筛选合作伙伴——他们之前代理过什么产品、客户来源、是经销商还是服务合作伙伴。
  • 促成交易的内容比例:80%“我们如何帮助客户成功”,20%关于自身。演示文稿从买家的痛点切入,然后给出解决方案。

Related Gingiris Skills

相关Gingiris技能