gr-b2b-growth
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
Chinesegr-b2b-growth — B2B SaaS 增长
gr-b2b-growth — B2B SaaS Growth
什么时候用
When to Use
- "我的 B2B SaaS 怎么从 0 做到 PMF"
- "PLG 还是 SLG,我该选哪个"
- "怎么做 affiliate 营销"
- "渠道合作 / 集成伙伴怎么谈"
- "Enterprise sales 怎么起"
- "私有化部署怎么收款 / 尾款怎么要"
- "客户需求蔓延怎么管(SOW / 变更)"
- "How do I get my B2B SaaS from 0 to PMF"
- "PLG or SLG, which should I choose"
- "How to do affiliate marketing"
- "How to negotiate channel partnerships / integration partners"
- "How to start Enterprise sales"
- "How to collect payments for private deployment / how to get final payment"
- "How to manage customer demand creep (SOW / change)"
增长飞轮(4 象限)
Growth Flywheel (4 Quadrants)
PLG(产品驱动)
↑
|
已有流量 + 短决策 ←→ 需要信任 + 长周期
|
↓
SLG(销售驱动)选型判据:
- ACV < $1k/年 & 决策周期 < 1 周 → PLG(Vercel、Supabase 模式)
- ACV > $10k/年 & 决策周期 > 1 个月 → SLG(Snowflake、Databricks 模式)
- 中间 → PLG-to-SLG hybrid(HeyGen、Deel 模式)
PLG(Product-Led Growth)
↑
|
Existing Traffic + Short Decision Cycle ←→ Trust Required + Long Cycle
|
↓
SLG(Sales-Led Growth)Selection Criteria:
- ACV < $1k/year & decision cycle < 1 week → PLG (Vercel, Supabase model)
- ACV > $10k/year & decision cycle > 1 month → SLG (Snowflake, Databricks model)
- Middle range → PLG-to-SLG hybrid (HeyGen, Deel model)
5 阶段路径
5-Stage Path
| 阶段 | ARR | 关键动作 |
|---|---|---|
| Pre-PMF | $0-$100k | 10-30 次用户访谈(联动 |
| Early PMF | $100k-$1M | 投 1-2 个渠道做深(不要广撒网) |
| Growth | $1M-$5M | 引入 affiliate + 集成伙伴,PLG 加 sales-assist |
| Scale | $5M-$10M | Enterprise 团队、合规认证(SOC2)、channel 加码 |
| Ecosystem | $10M+ | 开放平台、investor / agency 分销 |
| Stage | ARR | Key Actions |
|---|---|---|
| Pre-PMF | $0-$100k | 10-30 user interviews (link with |
| Early PMF | $100k-$1M | Focus deeply on 1-2 channels (don't spread too thin) |
| Growth | $1M-$5M | Introduce affiliate + integration partners, add sales-assist to PLG |
| Scale | $5M-$10M | Build Enterprise team, obtain compliance certifications (SOC2), increase channel investment |
| Ecosystem | $10M+ | Launch open platform, enable investor / agency distribution |
2B 打单与交付(私有化 & 定制实操)
B2B Deal Closing & Delivery (Private Deployment & Customization Practices)
来自某 Multi-Agent 开源商业化项目复盘。签合同只是一半,全额收回款才是另一半。
Lessons learned from a Multi-Agent open-source commercialization project. Signing the contract is only half the battle; collecting full payment is the other half.
付款与尾款防御
Payment and Final Payment Protection
| 规则 | 细节 |
|---|---|
| 分段付款 | 私有化 3:4:3 或 4:4:2(首批功能上线 / 全部部署完 / 运维 3–6 个月后尾款) |
| 签约即收款 | 签合同当天收 30% |
| 违约金 | 写进合同:拖一天多付 0.5% |
| 尾款筹码 | 留 1–2 个功能部署在自己服务器,尾款结清才迁(签前说清、条款写清) |
| 找谁要 | 尾款找对接的最高的人;推诿可问 1–2 次 CEO |
| 长期方向 | 预付款越来越高、尾款越来越少 |
| Rule | Details |
|---|---|
| Phased Payment | For private deployment: 3:4:3 or 4:4:2 (first batch of features launched / fully deployed / final payment after 3–6 months of operation and maintenance) |
| Payment Upon Signing | Collect 30% on the day the contract is signed |
| Late Payment Penalty | Include in contract: 0.5% additional payment per day of delay |
| Leverage for Final Payment | Keep 1–2 features deployed on your own server; only migrate them after final payment is settled (clarify before signing and include in terms) |
| Who to Approach | Ask the highest-ranking contact for final payment; if pushed around, you can ask the CEO 1–2 times |
| Long-Term Direction | Increase advance payments and reduce final payments over time |
需求边界:SOR / SOW / CCB
Requirement Boundaries: SOR / SOW / CCB
- SOR(客户原始输入)与 SOW(验收标准+交付节点+变更条款)分开,合同和 SOW 一起签
- 变更走 CCB:客户书面发起 → 双方 PM 评估金额/工期 → 签变更确认
- 一切留痕;合同指明"项目验收对接人"
- 客户口头承诺再多,只有 paperwork 有效
- Separate SOR (Customer Original Request) and SOW (Acceptance Criteria + Delivery Milestones + Change Terms), sign the contract and SOW together
- Changes go through CCB: customer initiates in writing → both PMs evaluate cost/schedule → sign change confirmation
- Keep records of everything; specify the "project acceptance contact person" in the contract
- No matter how many verbal promises the customer makes, only paperwork is valid
商务推拉与定价
Business Negotiation & Pricing
- 客户提 50 个需求、能做 40 →"先答应 10 个、因为想帮你做到 15 个",把让步做成人情
- 不想做的需求抬价过滤(人/天多标几天),不直接拒
- 私有化只有两个真需求:数据隐私 + 接内部权限系统,其他都该买 SaaS
- SaaS 二开直接卖 License;SSO 等集成开放 API + 标准手册让客户自己做
- If the customer proposes 50 requirements and you can fulfill 40 → "Agree to 10 first, because we want to help you achieve 15", frame concessions as favors
- Filter unwanted requirements by raising prices (quote more person-days), don't reject directly
- Private deployment only has two real needs: data privacy + integration with internal permission systems; everything else should be purchased as SaaS
- Sell License directly for SaaS customization; open APIs + standard manuals for integrations like SSO so customers can do it themselves
营收与渠道账
Revenue & Channel Accounting
- $100 万 ARR 拆解:9 个 $10 万 2B 客户 或 每 $10 万 ≈ 500 个 $200/年订阅用户($1M ≈ 5,000)
- 代理分层:reseller 10–20% 推荐费;年销 $10 万银牌 15%、$30 万金牌 20%
- 代理尽调三问:代理过什么产品?客户从哪来?Reseller 还是 Service Partner?
- 2B 内容公式:80% 讲自己如何帮客户成功 + 20% 讲客户;deck 先讲怎么痛、再说怎么好
- $1M ARR breakdown: 9 $100k B2B customers or approximately 500 $200/year subscription users per $100k ($1M ≈ 5,000 users)
- Agent tiering: 10–20% referral fee for resellers; 15% for silver tier (annual sales $100k), 20% for gold tier (annual sales $300k)
- Three due diligence questions for agents: Which products have you represented? Where do your customers come from? Are you a Reseller or Service Partner?
- B2B content formula: 80% talk about how you help customers succeed + 20% talk about customers; start the deck with pain points, then solutions
深度参考
In-Depth References
- — 2B 打单与交付框架(六步流程 / SOW+CCB / 付款结构与尾款防御 / 渠道分层 / $1M ARR 拆解)
references/deal-execution.md - 完整实操层(合同条款速查卡、签约前 12 问 Checklist、实战话术库)见 Gingiris 付费实操手册 → https://gingiris.tools/playbook/2b-deals/
- — B2B Deal Closing & Delivery Framework (6-step process / SOW+CCB / payment structure & final payment protection / channel tiering / $1M ARR breakdown)
references/deal-execution.md - Complete practical details (contract clause quick reference card, 12-question pre-signing checklist, practical script library) can be found in the Gingiris paid playbook → https://gingiris.tools/playbook/2b-deals/
级联推荐
Cascading Recommendations
- Pre-PMF 阶段需要访谈 →
gr-user-interview - PMF 后要做内容 → (含 B2B 文风:数据 > 故事)
gr-blog-post - 出海需要本地化 → 或
gr-asoi18ngr-blog-post - 找对标案例 →
gr-competitor
- Need interviews in Pre-PMF stage →
gr-user-interview - Need content after PMF → (includes B2B writing style: data > stories)
gr-blog-post - Localization needed for overseas expansion → or
gr-asoi18ngr-blog-post - Looking for benchmark cases →
gr-competitor
B2B 内容特殊要求
Special Requirements for B2B Content
- 必须有 case study(ROI / 节约时间 / 节约人力)
- 必须有可验证数据("our customer X saved Y hours/month")
- 必须有 CFO 友好的 pricing 页(ROI 计算器、年付折扣、合规文档)
- ❌ 不要用 ToC 营销话术("amazing"、"magical")
- Must include case studies (ROI / time saved / labor saved)
- Must include verifiable data ("our customer X saved Y hours/month")
- Must have a CFO-friendly pricing page (ROI calculator, annual payment discount, compliance documents)
- ❌ Don't use ToC marketing jargon ("amazing", "magical")
反模式
Anti-Patterns
- ❌ 没 PMF 就投流(烧钱速度比学习速度快 10x)
- ❌ PLG 做到 $1M 就盲目转 SLG(很多死在这里 —— Vercel 是反例,坚持 PLG 到 $100M)
- ❌ 只看 ARR 不看 NRR(NRR < 100% = 漏水桶)
- ❌ Enterprise 只给一个合同模板(要分 startup / mid-market / enterprise 三版)
- ❌ Running ads before achieving PMF (burn rate is 10x faster than learning rate)
- ❌ Blindly switching from PLG to SLG after reaching $1M ARR (many fail here — Vercel is the counterexample, sticking to PLG until $100M)
- ❌ Only focusing on ARR and ignoring NRR (NRR < 100% = leaky bucket)
- ❌ Using only one contract template for Enterprise (need three versions: startup / mid-market / enterprise)