gingiris-b2b-growth

B2B SaaS Growth — PLG / SLG Playbook

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

🌍 Language: English | Chinese

"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)

Signal	Motion	Reference
ACV < $1k/yr and decision < 1 week	PLG	Vercel, Supabase
ACV > $10k/yr and decision > 1 month	SLG	Snowflake, Databricks
In between	PLG-to-SLG hybrid	HeyGen, Deel

The 5-stage path

Stage	ARR	Key move
Pre-PMF	$0–$100k	10–30 user interviews; confirm the must-have before anything else
Early PMF	$100k–$1M	Invest in 1–2 channels deeply — do not spray
Growth	$1M–$5M	Add affiliate + integration partners; PLG gets sales-assist
Scale	$5M–$10M	Enterprise 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").

Benchmark	Threshold
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 this	4-8%+ signup-to-paid, and smoother fundraising

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

Freeze paid ads, influencer pushes, and launch campaigns until the benchmark is hit.
Find the persona with the highest willingness to pay - talk to one user 5 times if needed.
Resist FOMO from competitors' PR; hold the line for months.
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

Rule	Detail
Staged payments	Private deployment splits 3:4:3 or 4:4:2 — first features live / full deployment / final payment after 3–6 months of ops
Collect on signature	30% due the day the contract is signed
Late penalty	Written into the contract: 0.5% per day overdue
Final-payment leverage	Keep 1–2 features deployed on your own servers until the last payment clears — say it before signing, write it into the terms
Who to chase	Chase the tail payment with the highest-ranking contact; if your champion stalls, escalate to the CEO once or twice
Long-term direction	Every 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 ARR	Breakdown
Enterprise route	9 × $100k 2B customers
Subscription route	~~5,000 × $200/yr subscribers (≈500 per $100k) per $100k (≈5,000 for $1M)

Channel tier	Terms
Reseller	10–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.

Chinese version

Choose your growth engine (flywheel)

        PLG（产品驱动）
              ↑
   已有流量 + 短决策
   ←─────────────────────────────────→
   需要信任 + 长周期
              ↓
        SLG（销售驱动）

Signal	Engine	Benchmark
ACV < $1k/year and decision < 1 week	PLG	Vercel、Supabase
ACV > $10k/year and decision > 1 month	SLG	Snowflake、Databricks
Middle	PLG-to-SLG hybrid	HeyGen、Deel

5-stage path

Stage	ARR	Key actions
Pre-PMF	$0–$100k	10–30 user interviews, first confirm must-have
Early PMF	$100k–$1M	Go deep on 1–2 channels, don't spread thin
Growth	$1M–$5M	Bring in affiliate + integration partners, PLG plus sales-assist
Scale	$5M–$10M	Enterprise team, compliance (SOC 2), double down on channels
Ecosystem	$10M+	Open platform, investor / agency distribution

Conversion first: refine signup→paid first, then scale

Counterintuitive but battle-tested: before the signup→paid conversion rate reaches the baseline, don't scale—ad ROI won't be positive ("suicidal marketing").

Benchmark	Baseline
ToC AI signup→paid	≥1.5% before you can scale (good products 6–8%, best seen ~40%)
ToB AI signup→paid	>10–15% before you can scale
Results of real executors	Signup→paid 4–8%+, and fundraising goes more smoothly

SOP (200+ teams have heard it, fewer than 10 have actually finished executing it):

Before hitting the target, freeze ad spend, influencers, and launch campaigns.
Find the persona with the highest willingness to pay at the current stage—if necessary, "talk to one user 5 times."
Resist the FOMO from competitor PR, and hold out for a few months.
Evidence: a coached ToC product went quiet for about half a year and got signup→paid to 6–8%—about 10,000 registered users reaching ~$5,000 MRR—after which the scaling curve took off and fundraising went smoothly.

Unit economics compared at both ends:

Classical product-ism: Gamma, HeyGen, and Lovable all did ~500–1,000 user interviews over about half a year before scaling (oral industry reference). HeyGen's "signup to paid in 5 minutes" flow was distilled from ~1,800 interviews—only 1 free credit is given, and the paywall sits at the peak of the aha moment.
Counterexample of burning money on ads (anonymous): cost per signup of tens of dollars, cost per paying user of hundreds of dollars.

Day-0 charging discipline

Start charging from day 0. Allow a pricing test adjustment period, but be brave about charging—even $1 plants the mindset that "this is not a free product." Paying users vote with their feet; free users just voice opinions.
Don't wait until the paid version is built: first put up a (deliberately vaguely worded) pricing page + contact form. Actual test: in two weeks, dozens of price inquiries came in; the ratio was about 70% community free / 20% individual / 10% team—users' wording shifted from "is this free" to "roughly how much does it cost."
The points where a product's users truly payno more than 3. Instrument to find them, and put the paywall there.

The PLG→SLG watershed and lean headcount efficiency benchmarks

Below ~$1M ARR：PLG + organic + regular paid acquisition is enough; above ~$1M ARR (and most ToB): you must have SLG / local KA channels to scale sustainably.
Benchmarks for people efficiency (recalled from podcast narration, approximate figures): Notion reached the million-user scale with about 4–8 people; ClickUp reached $1M ARR with about 24 people; multiple 8–10 person teams in the same space reached a million dollars in revenue. Iron rule of operations:More than 25 people and still not at $1M revenue = the problem is the organization, not the market.
The inbound-style SLG paradigm (narrated by the founder in person): the Mattermost Community Edition ranks in search→users self-serve a trial→proactive inbound, going from ~$100K per deal to $1M per deal, without needing to maintain a large sales team. Dify only sells the standardized private deployment edition ($30–50K per deal, with one engineer dispatched to deploy it), and all customization requests are forwarded to partner vendors.

The B2B outbound threshold when the product is not fully ready

Don't wait for the customer to have all their workflow materials ready: first use public information to make a rough demo, directly ask for the materials they already have during the meeting, then iterate based on the real process.
Break requirements into standard product / guided configuration / paid customization; for any configuration that affects the product experience, provide a minimum quality standard and acceptance checklist, and do not leave it entirely to the customer to figure out on their own.
Prioritize starting with smaller customers and frontline operators who are easier to reach; separately sample about 10 large enterprises for validation, to avoid mistaking procurement-process and internal-coordination difficulty for product requirements.
Before outbound, check each CTA one by one: change unfinished login or trial entry points to waitlist / Beta applications, and don't let potential customers get stuck at the very first step.
Record the funnel uniformly as 触达 -> 回复 -> 会议 -> 合格测试 -> 激活 -> 付费, and reuse proven copy and objection handling across owners.

2B deal closing and delivery (private deployment & customization)

Signing the contract is only half; collecting full payment is the other half. Distilled from a retrospective on a Multi-Agent open-source commercialization project.

Payment structure and final-payment defense

Rule	Details
Staged payments	Private deployment 3:4:3 or 4:4:2 —— final payment after the first batch of features goes live / all deployment is complete / 3–6 months of operations
Payment upon signing	Collect 30% on the day the contract is signed
Late fee	Write it directly into the contract:0.5% more for each day of delay
Final-payment leverage	At delivery, leave 1–2 features deployed onyour own server, and migrate them only after the final payment is settled —— make this clear before signing the contract and write it clearly in the terms
Whom to ask	For the final payment, go directly tothe highest-ranking person involved in the contact; if the contact person deflects, you can ask the CEO 1–2 times
Long-term direction	For each deal: higher and higher upfront payment, smaller and smaller final payment

Requirements boundary management: SOR / SOW / CCB

SOR(customer's original input) and SOW(acceptance criteria + delivery milestones + change terms) separately;sign the contract and SOW together。
Changes always go through CCB：Customer initiates in writing first → project managers from both sides assess impact (amount / schedule) → both sides sign a change confirmation document.
Keep records of everything (meetings / conversations / acceptance records); the contract specifies the "project acceptance contact person."
Client gets carried away chatting and makes promises?Only paperwork is valid.

Business back-and-forth

Client raises 50 requirements, internally judged that 40 can be done → "Agree to 10 first, and since we want to help you, we'll do 15" — turn concessions into personal favors.
Requirements you don't want to doPrice inflation filter(mark a few extra person-days), no need to refuse directly.
Private deployment requirements only havetwo real points: data privacy + integration with internal permission systems; everything else should buy SaaS.
SaaS customization → directly sell License; integrations such as SSO → open APIs + standard manuals, let the client do it themselves.

Revenue and channel accounts

$1M ARR breakdown	Composition
2B route	9 enterprise clients at $100K each
Subscription route	each $100K ≈ 500 subscribers at $200/year ($1M ≈ 5,000)

Agent tiering	Conditions
Reseller	10–20% referral fee
Silver (annual sales >$100K)	15%
Gold (annual sales >$300K)	20%

Three questions for agent due diligence: what products have they represented before? Where do customers come from? Reseller or Service Partner?

2B content formula: 80% talk about how you help clients succeed + 20% talk about clients; deck narrative "first talk about the pain, then talk about how good it is."

Special requirements for B2B content

Must have case studies(ROI / time saved / labor saved).
Must have verifiable data（"customer X saved Y hours/month"）。
Must have a CFO-friendly pricing page(ROI calculator, annual payment discount, compliance documents).
❌ Don't use ToC language ("amazing", "magical").

Anti-patterns

PLG signal gate (2026 meeting notes update)

Free DAU does not equal PLG being established. First define an activation event directly related to value, then look at 注册 → 激活 → 重复使用 → 付费/合格扩张。
Exclude internal, test, and campaign-gifted users, and cohort by registration month; users who only log in but do not complete the core task are not counted as activated.
Before the product achieves stable activation and retention, do not expand paid acquisition, and do not blindly add sales team members; go back to interviews, onboarding, and pricing experiments.
Introduce sales-assist when team usage, seat growth, security/procurement needs, or clear expansion intent appear, rather than handing free users to sales as soon as you see them.
All conversion thresholds should note the date, sample scope, and data source; historical cases are used to form hypotheses, not as permanent cross-product standards.
❌ Investing in traffic without PMF (burning money is 10x faster than learning).
❌ Blindly going from PLG → SLG at $1M (Vercel stuck with PLG until $100M).
❌ Only looking at ARR and not looking at NRR(NRR < 100% = leaky bucket).
❌ Only giving one contract template (split into three versions: startup / mid-market / enterprise).

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

Join the go-global community and purchase the resource pack · Community & Resources

Join the go-global community: Add on WeChat staywildgrow, leave the message "Join community" and you're in.
Purchase the resource pack: Add on WeChat staywildgrow, inquire about purchasing the Gingiris go-global resource pack, price 599 RMB。
Join the global growth community: Add staywildgrow on WeChat and send "Join community" (join the community).
Get the resource pack: Add staywildgrow on WeChat to purchase the Gingiris global growth resource pack for CNY 599.

The community and resource pack are optional entry points and do not affect the installation and use of this open-source Skill.

The community and paid resource pack are optional; neither is required to install or use this open-source skill.

About this skill

English Version

Pick your motion (the flywheel)

The 5-stage path

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

Day-0 pricing discipline

PLG-to-SLG watershed and lean-team benchmarks

Pre-product B2B outreach gate

Enterprise deal execution (private deployment & custom 2B)

Payment structure & final-installment defense

Scope control: SOR / SOW / CCB

Commercial push-pull

Revenue & channel math

B2B content is different from B2C

Anti-patterns

What to do next

Chinese version

Choose your growth engine (flywheel)

5-stage path

Conversion first: refine signup→paid first, then scale

Day-0 charging discipline

The PLG→SLG watershed and lean headcount efficiency benchmarks

The B2B outbound threshold when the product is not fully ready

2B deal closing and delivery (private deployment & customization)

Payment structure and final-payment defense

Requirements boundary management: SOR / SOW / CCB

Business back-and-forth

Revenue and channel accounts

Special requirements for B2B content

Anti-patterns

PLG signal gate (2026 meeting notes update)

Join the go-global community and purchase the resource pack · Community & Resources