本文へ移動
cccskills
無料GitHub で公開

gingiris-b2b-growth

🇺🇸 B2B SaaS Growth — PLG vs SLG Playbook — Diagnose whether your problem is distribution, pricing, or PMF. PLG/SLG selection by ACV and sales cycle, the 5-stage path from $0 to $10M ARR, NRR discipline, affiliate & channel motion, enterprise tiering. Built from HeyGen, Deel, Vercel, Supabase, Snowflake patterns. 🇨🇳 B2B SaaS 增长 — PLG vs SLG 决策手册 — 诊断你的瓶颈是分发、定价还是 PMF。

按 ACV 和销售周期选 PLG/SLG,$0 → $10M ARR 的 5 阶段路径,NRR 纪律,联盟与渠道打法,Enterprise 分层。提炼自 HeyGen、Deel、Vercel、Supabase、Snowflake。

🇯🇵 B2B SaaS グロース — PLG vs SLG プレイブック — 課題が流通・価格・PMFのどれかを診断。ACVとセールスサイクルでPLG/SLG選定、$0→$10M ARRの5段階パス、NRR規律、アフィリエイト&チャネル。

🇰🇷 B2B SaaS 성장 — PLG vs SLG 플레이북 — 병목이 유통·가격·PMF 중 무엇인지 진단. ACV와 세일즈 사이클로 PLG/SLG 선택, $0 → $10M ARR 5단계 경로, NRR 규율, 제휴 & 채널. Triggers: "B2B growth" | "B2B SaaS" | "PLG" | "SLG" | "product-led growth" | "sales-led growth" | "PLG or SLG" | "SaaS pricing" | "ARR growth" | "NRR" | "go to market" | "enterprise sales" | "affiliate" | "PMF" | "B2B 增长" | "PLG 还是 SLG" | "SaaS 定价" | "渠道合作" | "PLG/SLG 선택"

インストール方法を見る

含まれるファイル(6)

  • SKILL.md19.5 KB
  • .gitattributes2.4 KB
  • README.md9.9 KB
  • references/deal-execution.md3.1 KB
  • references/en/deal-execution.md3.8 KB
  • references/podcast-evidence.md667 B

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

B2B SaaS Growth — PLG / SLG Playbook

Podcast-derived stage evidence and claim boundaries: references/podcast-evidence.md.

🌍 Language / 语言: English | 中文

"People like it but revenue isn't growing" is rarely one problem. It's usually a mis-matched motion: a PLG product run with an SLG playbook, or vice versa. Start by diagnosing the motion, then walk the staged path.


English Version

Pick your motion (the flywheel)

        PLG (product-driven)
              ↑
   existing traffic + short decision
   ←─────────────────────────────────→
   needs trust + long cycle
              ↓
        SLG (sales-driven)
SignalMotionReference
ACV < $1k/yr and decision < 1 weekPLGVercel, Supabase
ACV > $10k/yr and decision > 1 monthSLGSnowflake, Databricks
In betweenPLG-to-SLG hybridHeyGen, Deel

The 5-stage path

StageARRKey move
Pre-PMF$0–$100k10–30 user interviews; confirm the must-have before anything else
Early PMF$100k–$1MInvest in 1–2 channels deeply — do not spray
Growth$1M–$5MAdd affiliate + integration partners; PLG gets sales-assist
Scale$5M–$10MEnterprise team, compliance (SOC 2), channel acceleration
Ecosystem$10M+Open platform, investor / agency distribution

Conversion-first: grind signup-to-paid before you scale

Counter-intuitive but field-proven: do not scale traffic until signup-to-paid conversion clears the bar. Below it, paid traffic is negative-ROI ("suicide marketing").

BenchmarkThreshold
ToC AI signup-to-paid>= 1.5% before scaling (good products: 6-8%; best seen ~40%)
ToB AI signup-to-paid> 10-15% before scaling
Teams that actually executed this4-8%+ signup-to-paid, and smoother fundraising

The SOP (200+ teams heard it; fewer than 10 executed):

  1. Freeze paid ads, influencer pushes, and launch campaigns until the benchmark is hit.
  2. Find the persona with the highest willingness to pay - talk to one user 5 times if needed.
  3. Resist FOMO from competitors' PR; hold the line for months.
  4. Proof case: one coached ToC product stayed quiet for ~6 months, reached 6-8% signup-to-paid - ~$5,000 MRR on ~10,000 registered users - then scaled, and the growth curve (and fundraising) took off.

Unit economics, both ends:

  • Interview-driven path: Gamma, HeyGen, Lovable each ran ~500-1,000 user interviews within roughly half a year before scaling (self-reported industry accounts). HeyGen's 5-minute signup-to-pay flow was distilled from ~1,800 interviews - 1 free credit, paywall exactly at the aha moment.
  • Burn path (anonymized counterexample): tens of dollars per signup, hundreds of dollars per paying user.

Day-0 pricing discipline

  • Charge from Day 0. A pricing-test window is fine, but collect money - even $1 plants the "this is not a free product" perception. Paying users vote with their wallet; free users just have opinions.
  • Don't wait for the paid tier to exist: ship a (deliberately vague) pricing page with a contact form. Field result: dozens of price inquiries within two weeks; inquiry mix ~70% community-free / 20% personal / 10% team - and the question shifts from "is this free?" to "how much?"
  • Users genuinely pay for at most ~3 points in any product. Instrument usage, find them, gate there.

PLG-to-SLG watershed and lean-team benchmarks

  • Below ~$1M ARR: PLG + organic + light paid marketing is enough. Above ~$1M ARR (and most ToB): you need SLG / local key-account channels to keep scaling.
  • Lean-team bar (podcast-recalled figures, treat as approximate): Notion ~4-8 people at million-user scale; ClickUp ~24 people at $1M ARR; several 8-10 person teams in the same space at $1M revenue. Operator rule: over 25 people without $1M revenue = the org is the problem, not the market.
  • Inbound-heavy SLG pattern (founder's own account, self-reported): Mattermost's community edition drives search ranking, self-serve trials, then inbound deals - growing from ~$100k contracts to ~$1M contracts without a large sales team. Dify sells a standardized on-prem edition at ~$30-50k per deal with a single deploy engineer, routing custom work to partner vendors.

Pre-product B2B outreach gate

  • Do not wait for prospects to prepare perfect workflow documents. Build a rough demo from public evidence, ask for whatever artifacts already exist during the call, and refine after observing the real workflow.
  • Segment each request into standard product / guided setup / paid customization. If setup quality affects the product experience, publish minimum standards and an evaluation checklist instead of leaving the buyer to improvise.
  • Start with reachable operators and smaller accounts; test roughly ten named enterprise accounts separately because procurement and internal politics make them a different motion.
  • Before outreach, remove or replace every broken CTA with a waitlist or explicit beta path. Outreach may precede a finished product; a dead first step may not.
  • Measure the funnel as contacted -> replied -> meeting -> qualified test -> activated -> paid, and reuse winning messages across owners.

Enterprise deal execution (private deployment & custom 2B)

Winning the contract is half the job — getting paid in full is the other half. Distilled from a Multi-Agent open-source commercialization project retro.

Payment structure & final-installment defense

RuleDetail
Staged paymentsPrivate deployment splits 3:4:3 or 4:4:2 — first features live / full deployment / final payment after 3–6 months of ops
Collect on signature30% due the day the contract is signed
Late penaltyWritten into the contract: 0.5% per day overdue
Final-payment leverageKeep 1–2 features deployed on your own servers until the last payment clears — say it before signing, write it into the terms
Who to chaseChase the tail payment with the highest-ranking contact; if your champion stalls, escalate to the CEO once or twice
Long-term directionEvery new deal: prepayment up, tail payment down

Scope control: SOR / SOW / CCB

  • Keep SOR (customer's raw asks) separate from SOW (acceptance criteria + delivery milestones + change terms); sign the SOW together with the contract.
  • All changes go through a CCB: customer initiates in writing → both PMs assess impact (cost / schedule) → both sides sign a change confirmation.
  • Leave a paper trail for everything; name the acceptance contact in the contract.
  • Customer gets excited on a call and promises the moon? Only paperwork counts.

Commercial push-pull

  • Customer asks for 50 features and you could do 40 → "we can commit to 10, and because we want this to succeed we'll stretch to 15." Turn concessions into favors.
  • Requests you don't want → price them up (pad the person-days) instead of refusing outright.
  • Private deployment has only two legitimate drivers: data privacy + internal permission-system integration. Everything else belongs on SaaS.
  • SaaS customization → sell a License. SSO and similar integrations → open API + standard docs, let the customer build it themselves.

Revenue & channel math

Path to $1M ARRBreakdown
Enterprise route9 × $100k 2B customers
Subscription route~~5,000 × $200/yr subscribers (≈500 per $100k) per $100k (≈5,000 for $1M)
Channel tierTerms
Reseller10–20% referral fee
Silver (>$100k/yr sales)15%
Gold (>$300k/yr sales)20%

Reseller due diligence — three questions: what did you resell before? where do your customers come from? reseller or service partner?

2B content formula: 80% how you helped customers succeed + 20% about the customer. Deck narrative: pain first, then the fix.

Deep dive: references/deal-execution.md. The full operator layer (contract-clause quick cards, the 12-question pre-signing checklist, negotiation scripts) ships with the Gingiris paid field manual → https://gingiris.tools/playbook/2b-deals/

B2B content is different from B2C

  • Must have a case study (ROI / time saved / headcount saved).
  • Must have verifiable numbers ("customer X saved Y hours/month").
  • Must have a CFO-friendly pricing page (ROI calculator, annual discount, compliance docs).
  • ❌ No B2C hype words ("amazing", "magical").

Anti-patterns

  • ❌ Paid acquisition before PMF — you burn cash 10× faster than you learn.
  • ❌ Forcing PLG → SLG at $1M just because. Vercel held PLG to $100M.
  • ❌ Watching ARR but ignoring NRR. NRR < 100% = a leaking bucket.
  • ❌ One contract template for everyone — split startup / mid-market / enterprise.

What to do next

  • Pre-PMF → run formal user interviews to find the must-have.
  • Post-PMF, need content → move to the blog/SEO workflow (B2B voice: data > story).
  • Going global → localize the listing and pricing.
  • Benchmarking a rival → run a competitor teardown.

中文版

选你的增长引擎(飞轮)

        PLG(产品驱动)
              ↑
   已有流量 + 短决策
   ←─────────────────────────────────→
   需要信任 + 长周期
              ↓
        SLG(销售驱动)
信号引擎对标
ACV < $1k/年 且 决策 < 1 周PLGVercel、Supabase
ACV > $10k/年 且 决策 > 1 个月SLGSnowflake、Databricks
中间PLG-to-SLG 混合HeyGen、Deel

5 阶段路径

阶段ARR关键动作
Pre-PMF$0–$100k10–30 次用户访谈,先确认 must-have
Early PMF$100k–$1M投 1–2 个渠道做深,不要广撒网
Growth$1M–$5M引入 affiliate + 集成伙伴,PLG 加 sales-assist
Scale$5M–$10MEnterprise 团队、合规(SOC 2)、渠道加码
Ecosystem$10M+开放平台、investor / agency 分销

转化优先:先磨注册→付费,再放量

反常识但实战验证:注册→付费转化率没到基准线之前,不要放量——投放 ROI 打不正("自杀式营销")。

Benchmark基准线
ToC AI 注册→付费≥1.5% 才可放量(好产品 6–8%,最好见过 ~40%)
ToB AI 注册→付费>10–15% 才可放量
真正执行者的结果注册→付费 4–8%+,融资也更顺

SOP(200+ 团队听过,真正执行完的不到 10 个):

  1. 达标前冻结投放、红人、launch campaign。
  2. 找出当前阶段付费意愿最高的画像——必要时"和一个用户聊 5 次"。
  3. 抵抗竞品 PR 带来的 FOMO,顶住几个月。
  4. 实证:一个被辅导的 ToC 产品沉寂约半年,注册→付费做到 6–8%——约 1 万注册用户做到 ~$5,000 MRR——之后放量曲线起飞、融资顺利。

单位经济学两端对照:

  • 古典产品主义:Gamma、HeyGen、Lovable 都在约半年内做了 ~500–1,000 场用户访谈再放量(口述行业参照)。HeyGen 的"注册到付费 5 分钟"链路提炼自 ~1,800 场访谈——只给 1 个 free credit,付费墙卡在 aha moment 最高点。
  • 烧钱投放反例(匿名):单个注册成本几十美金、单个付费用户成本几百美金。

Day-0 收费纪律

  • 从 day 0 开始收钱。 允许 pricing test 调整期,但要勇敢收费——哪怕收 $1,也种下"这不是免费产品"的心智。付费用户用脚投票,免费用户只是发表意见。
  • 不要等付费版做出来:先挂一个(刻意写模糊的)pricing 页 + contact 表单。实测:两周收到几十个问价;比例约 70% community free / 20% 个人 / 10% team——用户口径从"这免费吗"变成"大概多少钱"。
  • 一个产品用户真正付费的点不超过 3 个。做埋点找到它们,把卡点设在那里。

PLG→SLG 分水岭与精简人效基准

  • ~$1M ARR 以下:PLG + organic + 常规投放足够;~$1M ARR 以上(及多数 ToB):必须配 SLG / 本地 KA 渠道才能持续规模化。
  • 人效基准(播客口述回忆,按约数看):Notion 约 4–8 人时已达百万用户量级;ClickUp 约 24 人做到 $1M ARR;同赛道多个 8–10 人团队做到百万美金营收。操盘铁律:超过 25 人还没到 $1M 营收 = 组织有问题,不是市场有问题。
  • Inbound 型 SLG 范式(founder 面授口述):Mattermost 社区版带搜索排名→用户自助试用→主动 inbound,从 ~$10 万一单做到 $100 万一单,无需养大型销售团队。Dify 只卖标准化私有部署版($3–5 万美金/单,派一个工程师部署),定制需求全部转给合作 vendor。

产品未完全就绪时的 B2B 外联门槛

  • 不等客户把工作流资料准备齐:先用公开信息做粗版 demo,在会上直接索取已有材料,再基于真实流程迭代。
  • 把需求拆成 标准产品 / 引导式配置 / 付费定制;凡是会影响产品体验的配置,都提供最低质量标准与验收清单,不能完全交给客户自行摸索。
  • 优先从更容易触达的小型客户和一线操作者开始;大型企业单独抽样约 10 家验证,避免把采购流程和内部协同难度误判成产品需求。
  • 外联前逐个检查 CTA:未完成的登录或试用入口改成 waitlist / Beta 申请,不能让潜客第一步就卡死。
  • 漏斗统一记录为 触达 -> 回复 -> 会议 -> 合格测试 -> 激活 -> 付费,跨负责人复用已验证的文案和异议处理。

2B 打单与交付(私有化 & 定制)

签下合同只是一半,全额收回款才是另一半。提炼自某 Multi-Agent 开源商业化项目复盘。

付款结构与尾款防御

规则细节
分段付款私有化部署 3:4:3 或 4:4:2 —— 第一批功能上线 / 全部部署完 / 运维 3–6 个月后付尾款
签约即收款签合同当天收 30%
违约金直接写进合同:拖一天多付 0.5%
尾款筹码交付时留 1–2 个功能部署在自己服务器,尾款结清才迁 —— 签合同前说清楚、条款里写清楚
找谁要尾款直接找对接的最高的人;对接人推诿可问 1–2 次 CEO
长期方向每一单:预付款越来越高、尾款越来越少

需求边界管理:SOR / SOW / CCB

  • SOR(客户原始输入)与 SOW(验收标准 + 交付节点 + 变更条款)分开;合同和 SOW 一起签。
  • 变更一律走 CCB:客户先书面发起 → 双方项目经理评估影响(金额 / 工期)→ 双方签变更确认文件。
  • 一切留痕(会议 / 对话 / 验收记录);合同指明"项目验收对接人"。
  • 客户聊嗨了拍胸脯?只有 paperwork 有效。

商务推拉

  • 客户提 50 个需求、内部判断 40 能做 →"先答应 10 个,因为想帮你所以做到 15 个"——把让步做成人情。
  • 不想做的需求抬价过滤(人/天多标几天),不用直接拒绝。
  • 私有化需求只有两个真点:数据隐私 + 接内部权限系统,其他都该买 SaaS。
  • SaaS 二开 → 直接卖 License;SSO 等集成 → 开放 API + 标准手册,让客户自己做。

营收与渠道账

$1M ARR 拆解组成
2B 路线9 个 $10 万企业客户
订阅路线每 $10 万 ≈ 500 个 $200/年订阅用户($1M ≈ 5,000)
代理分层条件
Reseller10–20% 推荐费
银牌(年销 >$10 万)15%
金牌(年销 >$30 万)20%

代理尽调三问:之前代理过什么产品?客户从哪来?Reseller 还是 Service Partner?

2B 内容公式:80% 讲自己如何帮客户成功 + 20% 讲客户;deck 叙事"先讲怎么痛,再说怎么好"。

B2B 内容特殊要求

  • 必须有 case study(ROI / 省时 / 省人力)。
  • 必须有可验证数据("customer X saved Y hours/month")。
  • 必须有 CFO 友好的 pricing 页(ROI 计算器、年付折扣、合规文档)。
  • ❌ 不用 ToC 话术("amazing"、"magical")。

反模式

PLG 信号门(2026 会议纪要更新)

  • 免费 DAU 不等于 PLG 成立。先定义一个与价值直接相关的激活事件,再看 注册 → 激活 → 重复使用 → 付费/合格扩张。

  • 剔除内部、测试和活动赠送用户,并按注册月份做 cohort;只有登录、没有完成核心任务的用户不算激活。

  • 产品未达到稳定激活与留存前,不扩付费投放、不盲目加销售团队;回到访谈、onboarding 和定价实验。

  • 当团队使用、席位增长、安全/采购需求或明确扩张意图出现时再引入 sales-assist,而不是见到免费用户就交给销售。

  • 所有转化阈值注明日期、样本范围与数据来源;历史案例用于形成假设,不作为跨产品的永久标准。

  • ❌ 没 PMF 就投流(烧钱比学习快 10x)。

  • ❌ 到 $1M 就盲目 PLG → SLG(Vercel 坚持 PLG 到 $100M)。

  • ❌ 只看 ARR 不看 NRR(NRR < 100% = 漏水桶)。

  • ❌ 只给一个合同模板(分 startup / mid-market / enterprise 三版)。


By Iris (生姜 Iris) · ex-COO @ AFFiNE, 150+ AI startups advised · Install: npx skills add Gingiris-1031/gingiris-b2b-growth

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

AI Agent Workflow & Skill Architecture Guide — turn expert work into measurable, reusable agent systems. Covers workflow discovery, skill decomposition, harness design, evaluation, human escalation, observability, cost control, and multi-agent orchestration. Includes a measured marketing-delivery case: 15 people × 3–4 weeks reduced to one strategist + AI in 5 days. By Gingiris.

日本語の概要は準備中です。原文の説明を表示しています。

Gingiris-1031/gingiris-skills842026年10月8日 更新

Launch your AI product to global attention — the playbook behind Manus, Devin, and AFFiNE's breakout launches. Covers AI-specific GTM strategy, hype cycle management, waitlist tactics, and multi-market rollout for maximum day-one impact.

日本語の概要は準備中です。原文の説明を表示しています。

Gingiris-1031/gingiris-skills842026年10月8日 更新

First AI Product Launch — Zero to Live in 30 Days. Step-by-step guide for shipping your first AI product from idea validation to paying customers. Includes day-by-day timeline and real examples. By @WeiYipei.

日本語の概要は準備中です。原文の説明を表示しています。

Gingiris-1031/gingiris-skills842026年10月8日 更新

Beginner-friendly App Store Optimization guide covering keyword research, screenshot design, rating management, and A/B testing for iOS and Android. By @WeiYipei — practical ASO for indie developers and small teams.

日本語の概要は準備中です。原文の説明を表示しています。

Gingiris-1031/gingiris-skills842026年10月8日 更新

Complete B2B marketing pipeline combining LinkedIn content, cold email sequences, and webinar funnels. Designed for SaaS founders doing $0–$1M ARR who need predictable lead generation. By @WeiYipei.

日本語の概要は準備中です。原文の説明を表示しています。

Gingiris-1031/gingiris-skills842026年10月8日 更新

community-ambassador-playbook

無料日本語概要

You launched an ambassador program. 3 applications. One ghosted after week 2. Should you lower the bar? Offer more perks? Spam influencers? This gives you the community & ambassador operations SOP with volunteer, paid tutorial creator and code-contributor tracks — from pre-launch checklist to recruitment to tiered management to retention to governance. Built from Notion (20M users, real ambassador interviews), AFFiNE (60K stars), Asana, and ClickUp programs. By @WeiYipei. 🇨🇳 你搞了个大使计划。来了3个申请。一个第二周就消失了。该降门槛?加福利?群发KOL?这份SOP给你从启动前置条件到招募到留存到治理的完整社区/大使运营方法论。基于 Notion(2000万用户,大使真实访谈)、AFFiNE(60K stars)、Asana、ClickUp 实战案例。 🇯🇵 アンバサダープログラムを立ち上げた。応募3件。1人は2週間で消えた。基準を下げる?特典を増やす?このSOPは、事前チェックリストから採用、段階管理、リテンション、ガバナンスまでの完全なコミュニティ&アンバサダー運営フレームワークを提供します。Notion(2000万ユーザー)、AFFiNE(60K stars)の実例から構築。 🇰🇷 앰배서더 프로그램을 시작했습니다. 지원 3건. 하나는 2주 만에 사라졌습니다. 기준을 낮출까요? 이 SOP는 사전 체크리스트부터 모집, 단계별 관리, 리텐션, 거버넌스까지 완전한 커뮤니티 & 앰배서더 운영 프레임워크를 제공합니다. Notion(2000만 사용자), AFFiNE(60K stars) 실전 사례에서 구축. Triggers: "ambassador program" | "community building" | "community management" | "DevRel" | "developer relations" | "community growth" | "大使计划" | "社区运营" | "社区搭建" | "コミュニティ運営" | "アンバサダー" | "커뮤니티 운영" | "앰배서더" | "open source community" | "user retention"

Gingiris-1031/gingiris-skills842026年10月8日 更新

Gingiris-1031 のスキルをすべて見る

このスキルの問題を報告する