Files of Tipping playbooks
wondelai/
Show the full text136 lines
Tipping Playbooks
Table of Contents
- From One Network to a Repeatable Playbook
- Invite-Only Mechanics
- Designing the Waitlist
- Paying Up: Subsidies and Guarantees
- Supply Pre-Commitment
- Picking the Next Market
- Anti-Patterns
- Measuring Tipping: Liquidity Metrics
- The Expansion Checklist
From One Network to a Repeatable Playbook
The tipping point is the stage where launching new networks shifts from heroic one-off effort to repeatable process — each market, campus, or segment tips faster and cheaper than the last because the playbook, brand spillover, and supply relationships compound. The deliverable of this stage is not a growth number; it is a launch kit: the documented sequence that took network #1 from zero to self-sustaining, ready to run against networks #2 through #N.
A launch kit contains:
- The target-network selection scorecard and the data behind the last pick
- The seeding sequence with owners and timelines (who recruits the hard side, in what order)
- Flintstoning hours and budget actually spent, by week
- Invite mechanics, referral rewards, and the copy that worked
- Subsidy levels with the taper schedule and the observed guarantee gap over time
- The liquidity bars that define "tipped" for one network
- The timeline and cost of every prior launch, for comparison
Invite-Only Mechanics
Invite-only looks like marketing scarcity; it is actually network construction. It does three jobs at once:
- Density by design. Every new user arrives knowing at least one person inside — their inviter. Invites travel along real social graphs, so the network copies itself in clusters instead of random scatter.
- Curation. Early users define culture and quality. Gating membership lets you choose who sets the norms, and keeps spam out while you are too small to fight it.
- Scarcity and social proof. Outsiders see something worth queuing for, and every invite arrives as a personal endorsement rather than an ad.
Parameters to tune:
| Parameter | Starting Point | Tuning Signal |
|---|---|---|
| Invites per user | 3-5 | Raise for high-quality, well-connected cohorts; cut if quality drops |
| Earn-more rule | Active users unlock more invites | Reward contribution, not bare signup |
| Cohort release | Admit by cluster (team, city, community), not first-come-first-served | Singles admitted alone hit zeroes; clusters arrive live |
| Vouching | Inviter standing affected by invitee behavior | Spam appearing → tighten vouching |
| Gates | Geographic or segment caps to protect liquidity | Don't admit demand where supply isn't ready |
Calibration classics: Gmail spread through scarce invites that people traded and begged for; Facebook gated campus by campus and didn't open general registration until the model was proven; the same mechanics get rerun by every breakout social app. The point teams miss: process the waitlist by network cluster, never by signup order.
Designing the Waitlist
- Capture the graph at signup. Company domain, city, school, club, interest — whatever defines your atomic network unit. A waitlist without graph data is just a mailing list.
- Score clusters, not individuals. Admit a cluster when it can form an atomic network on arrival — for example, eight or more people from one team, or two hundred in one zip code.
- Let applicants move themselves up by recruiting their cluster. "Get three coworkers on the list and skip ahead" turns the waitlist into a seeding engine.
- Communicate honestly. Show position, expected wait, and exactly what unlocks access. A silent or fake queue burns the trust you are trying to manufacture.
- Instrument the referral tree. Track who invited whom, conversion per branch, and which super-inviters' branches retain best — those people are your future community hires and ambassadors.
Paying Up: Subsidies and Guarantees
When organic density would take too long, buy it. Money converts into liquidity — the one asset competitors cannot copy-paste.
- Earnings guarantees (supply side). Pay the gap between guaranteed and organic earnings; the cost falls automatically as real demand arrives. Uber's launch playbook leaned on driver guarantees so riders never saw an empty map.
- Demand-side coupons. First-order discounts, time-boxed to launch. Design them to create a habit (three uses) rather than a single trial.
- Fee holidays and reduced take-rates for launch cohorts, with a published step-up schedule.
- Hero subsidies. Overpay a handful of anchor suppliers — the famous restaurant, the prominent creator — whose presence pulls both sides in.
Manage it like CAC:
| Metric | Definition | Healthy Direction |
|---|---|---|
| Cost per tipped network | Total subsidies ÷ networks reaching the live bar | Falling with each launch |
| Guarantee gap | Guaranteed minus organic earnings per supplier | Trending to zero by week 8-12 |
| Subsidized share | % of transactions touched by any subsidy | Declining on schedule |
| Post-taper retention | Supply and demand retention after subsidies step down | Flat curve = real network; cliff = rented usage |
Integrity rules: publish taper schedules up front, and never book subsidized activity as evidence of organic product-market fit — you will fool your own roadmap before you fool anyone else.
Supply Pre-Commitment
For marketplaces, sign the hard side before demand launch so day one has full shelves:
- Set the supply bar from your liquidity targets. Example: 40 vetted providers are required for a sub-two-hour time-to-match in one zip cluster at projected demand.
- Pre-sign with commitments in both directions. Guaranteed earnings or fee holidays in exchange for defined availability windows and response-time SLAs.
- Stage onboarding before opening demand. Profiles, photos, background checks, payment details — done before the first customer searches.
- Open demand gradually. Waitlist or geofence customers so the fill rate stays above bar from the first hour. A launch where the first hundred customers all get served beats one where a thousand try and half fail.
Picking the Next Market
Score candidates 1-5 on each criterion; expand to the top scorer, not the biggest:
| Criterion | Question |
|---|---|
| Adjacency | Does it border (geographically or socially) a tipped network, so awareness and members spill over? |
| Density potential | Can we hit atomic size with known playbook effort? |
| Hard-side availability | Is supply discoverable and recruitable — existing pros, creators, organizers? |
| Competitive gap | Is the incumbent weak, absent, or neglecting this segment? |
| Economics | Do unit economics work at this market's price points and behavior? |
| Operational reach | Can we staff, visit, and support it without heroics? |
Anti-Patterns
- The big-bang launch. Maximum simultaneous awareness — press exclusives, TV, launch-day stunts — fills the product faster than density can form. Hundreds of thousands of strangers land in empty rooms, churn, and immunize the market against your second chance. Google+ is the canonical corpse: hundreds of millions of registered users, almost no live networks, eventually shut down. Rule: press is for harvesting demand into networks that already work, not for creating networks.
- Vanity signups. Registered users are not networks. A signup that arrives without its counterparties is a future churn statistic. Cohort everything by network and by "arrived with connections vs. arrived alone."
- Launching everywhere shallowly. Ten cities at 5% density lose to one city at 80%. Anti-network effects run in all ten simultaneously.
- Demand before supply. Marketing spend that delivers users into zero states is paying to manufacture detractors.
- Skipping the bars. Expanding because the board meeting is Tuesday — rather than because network #1 holds its live bar without founder pedaling — replicates a broken loop at scale.
Measuring Tipping: Liquidity Metrics
Define "live" and "tipped" mechanically, so nobody can argue a network into health:
| Metric | Definition | Example Bar |
|---|---|---|
| Fill rate | % of demand requests fulfilled | >80% sustained for 2+ weeks |
| Time-to-match | Median wait from request to match | <10 min for rides; <2 h for services |
| Weekly active networks | Networks above the activity threshold (e.g., a team with 5+ actives) | 60% of launched networks |
| Magic-moment rate | % of new users hitting the magic moment in week one | >40% |
| Zero rate | % of sessions hitting an empty state | <10% and falling |
| Repeat rate | % of users transacting again within 30 days | Rising cohort over cohort |
| Organic share | % of new users arriving via invites and word of mouth | >50% by the tipping point |
| Post-subsidy retention | Activity retention across taper step-downs | No cliff at step-down dates |
Two practices make these metrics honest. First, report them per network with a live/forming/dead status — averages across networks are where dead launches hide. Second, pair every demand metric with its supply twin (fill rate with utilization, time-to-match with provider idle time) so you can see which side to throttle or subsidize next.
The Expansion Checklist
Before green-lighting network #N+1:
- Current cohort holds its live bars for 4+ weeks without founder flintstoning
- Launch kit updated with what this launch actually cost and which steps mattered
- Next market selected by scorecard, with explicit adjacency to a tipped network
- Supply pre-commitment targets signed before any demand spend
- Subsidy budget approved with a published taper schedule
- Demand gating plan (waitlist or geofence) in place to protect fill rate
- Per-network dashboard rows created with the same bars as prior launches
- A named owner accountable for this market reaching its live bar
| 1 | # Tipping Playbooks |
| 2 | |
| 3 | ## Table of Contents |
| 4 | |
| 5 | [From One Network to a Repeatable Playbook] |
| 6 | [Invite-Only Mechanics] |
| 7 | [Designing the Waitlist] |
| 8 | [Paying Up: Subsidies and Guarantees] |
| 9 | [Supply Pre-Commitment] |
| 10 | [Picking the Next Market] |
| 11 | [Anti-Patterns] |
| 12 | [Measuring Tipping: Liquidity Metrics] |
| 13 | [The Expansion Checklist] |
| 14 | |
| 15 | ## From One Network to a Repeatable Playbook |
| 16 | |
| 17 | The tipping point is the stage where launching new networks shifts from heroic one-off effort to repeatable process — each market, campus, or segment tips faster and cheaper than the last because the playbook, brand spillover, and supply relationships compound. The deliverable of this stage is not a growth number; it is a **launch kit**: the documented sequence that took network #1 from zero to self-sustaining, ready to run against networks #2 through #N. |
| 18 | |
| 19 | A launch kit contains: |
| 20 | |
| 21 | The target-network selection scorecard and the data behind the last pick |
| 22 | The seeding sequence with owners and timelines (who recruits the hard side, in what order) |
| 23 | Flintstoning hours and budget actually spent, by week |
| 24 | Invite mechanics, referral rewards, and the copy that worked |
| 25 | Subsidy levels with the taper schedule and the observed guarantee gap over time |
| 26 | The liquidity bars that define "tipped" for one network |
| 27 | The timeline and cost of every prior launch, for comparison |
| 28 | |
| 29 | ## Invite-Only Mechanics |
| 30 | |
| 31 | Invite-only looks like marketing scarcity; it is actually network construction. It does three jobs at once: |
| 32 | |
| 33 | **Density by design.** Every new user arrives knowing at least one person inside — their inviter. Invites travel along real social graphs, so the network copies itself in clusters instead of random scatter. |
| 34 | **Curation.** Early users define culture and quality. Gating membership lets you choose who sets the norms, and keeps spam out while you are too small to fight it. |
| 35 | **Scarcity and social proof.** Outsiders see something worth queuing for, and every invite arrives as a personal endorsement rather than an ad. |
| 36 | |
| 37 | Parameters to tune: |
| 38 | |
| 39 | | Parameter | Starting Point | Tuning Signal | |
| 40 | |-----------|----------------|---------------| |
| 41 | | Invites per user | 3-5 | Raise for high-quality, well-connected cohorts; cut if quality drops | |
| 42 | | Earn-more rule | Active users unlock more invites | Reward contribution, not bare signup | |
| 43 | | Cohort release | Admit by cluster (team, city, community), not first-come-first-served | Singles admitted alone hit zeroes; clusters arrive live | |
| 44 | | Vouching | Inviter standing affected by invitee behavior | Spam appearing → tighten vouching | |
| 45 | | Gates | Geographic or segment caps to protect liquidity | Don't admit demand where supply isn't ready | |
| 46 | |
| 47 | Calibration classics: Gmail spread through scarce invites that people traded and begged for; Facebook gated campus by campus and didn't open general registration until the model was proven; the same mechanics get rerun by every breakout social app. The point teams miss: process the waitlist by network cluster, never by signup order. |
| 48 | |
| 49 | ## Designing the Waitlist |
| 50 | |
| 51 | **Capture the graph at signup.** Company domain, city, school, club, interest — whatever defines your atomic network unit. A waitlist without graph data is just a mailing list. |
| 52 | **Score clusters, not individuals.** Admit a cluster when it can form an atomic network on arrival — for example, eight or more people from one team, or two hundred in one zip code. |
| 53 | **Let applicants move themselves up by recruiting their cluster.** "Get three coworkers on the list and skip ahead" turns the waitlist into a seeding engine. |
| 54 | **Communicate honestly.** Show position, expected wait, and exactly what unlocks access. A silent or fake queue burns the trust you are trying to manufacture. |
| 55 | **Instrument the referral tree.** Track who invited whom, conversion per branch, and which super-inviters' branches retain best — those people are your future community hires and ambassadors. |
| 56 | |
| 57 | ## Paying Up: Subsidies and Guarantees |
| 58 | |
| 59 | When organic density would take too long, buy it. Money converts into liquidity — the one asset competitors cannot copy-paste. |
| 60 | |
| 61 | **Earnings guarantees (supply side).** Pay the gap between guaranteed and organic earnings; the cost falls automatically as real demand arrives. Uber's launch playbook leaned on driver guarantees so riders never saw an empty map. |
| 62 | **Demand-side coupons.** First-order discounts, time-boxed to launch. Design them to create a habit (three uses) rather than a single trial. |
| 63 | **Fee holidays and reduced take-rates** for launch cohorts, with a published step-up schedule. |
| 64 | **Hero subsidies.** Overpay a handful of anchor suppliers — the famous restaurant, the prominent creator — whose presence pulls both sides in. |
| 65 | |
| 66 | Manage it like CAC: |
| 67 | |
| 68 | | Metric | Definition | Healthy Direction | |
| 69 | |--------|------------|-------------------| |
| 70 | | Cost per tipped network | Total subsidies ÷ networks reaching the live bar | Falling with each launch | |
| 71 | | Guarantee gap | Guaranteed minus organic earnings per supplier | Trending to zero by week 8-12 | |
| 72 | | Subsidized share | % of transactions touched by any subsidy | Declining on schedule | |
| 73 | | Post-taper retention | Supply and demand retention after subsidies step down | Flat curve = real network; cliff = rented usage | |
| 74 | |
| 75 | Integrity rules: publish taper schedules up front, and never book subsidized activity as evidence of organic product-market fit — you will fool your own roadmap before you fool anyone else. |
| 76 | |
| 77 | ## Supply Pre-Commitment |
| 78 | |
| 79 | For marketplaces, sign the hard side before demand launch so day one has full shelves: |
| 80 | |
| 81 | **Set the supply bar from your liquidity targets.** Example: 40 vetted providers are required for a sub-two-hour time-to-match in one zip cluster at projected demand. |
| 82 | **Pre-sign with commitments in both directions.** Guaranteed earnings or fee holidays in exchange for defined availability windows and response-time SLAs. |
| 83 | **Stage onboarding before opening demand.** Profiles, photos, background checks, payment details — done before the first customer searches. |
| 84 | **Open demand gradually.** Waitlist or geofence customers so the fill rate stays above bar from the first hour. A launch where the first hundred customers all get served beats one where a thousand try and half fail. |
| 85 | |
| 86 | ## Picking the Next Market |
| 87 | |
| 88 | Score candidates 1-5 on each criterion; expand to the top scorer, not the biggest: |
| 89 | |
| 90 | | Criterion | Question | |
| 91 | |-----------|----------| |
| 92 | | Adjacency | Does it border (geographically or socially) a tipped network, so awareness and members spill over? | |
| 93 | | Density potential | Can we hit atomic size with known playbook effort? | |
| 94 | | Hard-side availability | Is supply discoverable and recruitable — existing pros, creators, organizers? | |
| 95 | | Competitive gap | Is the incumbent weak, absent, or neglecting this segment? | |
| 96 | | Economics | Do unit economics work at this market's price points and behavior? | |
| 97 | | Operational reach | Can we staff, visit, and support it without heroics? | |
| 98 | |
| 99 | ## Anti-Patterns |
| 100 | |
| 101 | **The big-bang launch.** Maximum simultaneous awareness — press exclusives, TV, launch-day stunts — fills the product faster than density can form. Hundreds of thousands of strangers land in empty rooms, churn, and immunize the market against your second chance. Google+ is the canonical corpse: hundreds of millions of registered users, almost no live networks, eventually shut down. Rule: press is for harvesting demand into networks that already work, not for creating networks. |
| 102 | **Vanity signups.** Registered users are not networks. A signup that arrives without its counterparties is a future churn statistic. Cohort everything by network and by "arrived with connections vs. arrived alone." |
| 103 | **Launching everywhere shallowly.** Ten cities at 5% density lose to one city at 80%. Anti-network effects run in all ten simultaneously. |
| 104 | **Demand before supply.** Marketing spend that delivers users into zero states is paying to manufacture detractors. |
| 105 | **Skipping the bars.** Expanding because the board meeting is Tuesday — rather than because network #1 holds its live bar without founder pedaling — replicates a broken loop at scale. |
| 106 | |
| 107 | ## Measuring Tipping: Liquidity Metrics |
| 108 | |
| 109 | Define "live" and "tipped" mechanically, so nobody can argue a network into health: |
| 110 | |
| 111 | | Metric | Definition | Example Bar | |
| 112 | |--------|------------|-------------| |
| 113 | | Fill rate | % of demand requests fulfilled | >80% sustained for 2+ weeks | |
| 114 | | Time-to-match | Median wait from request to match | <10 min for rides; <2 h for services | |
| 115 | | Weekly active networks | Networks above the activity threshold (e.g., a team with 5+ actives) | 60% of launched networks | |
| 116 | | Magic-moment rate | % of new users hitting the magic moment in week one | >40% | |
| 117 | | Zero rate | % of sessions hitting an empty state | <10% and falling | |
| 118 | | Repeat rate | % of users transacting again within 30 days | Rising cohort over cohort | |
| 119 | | Organic share | % of new users arriving via invites and word of mouth | >50% by the tipping point | |
| 120 | | Post-subsidy retention | Activity retention across taper step-downs | No cliff at step-down dates | |
| 121 | |
| 122 | Two practices make these metrics honest. First, report them per network with a live/forming/dead status — averages across networks are where dead launches hide. Second, pair every demand metric with its supply twin (fill rate with utilization, time-to-match with provider idle time) so you can see which side to throttle or subsidize next. |
| 123 | |
| 124 | ## The Expansion Checklist |
| 125 | |
| 126 | Before green-lighting network #N+1: |
| 127 | |
| 128 | [ ] Current cohort holds its live bars for 4+ weeks without founder flintstoning |
| 129 | [ ] Launch kit updated with what this launch actually cost and which steps mattered |
| 130 | [ ] Next market selected by scorecard, with explicit adjacency to a tipped network |
| 131 | [ ] Supply pre-commitment targets signed before any demand spend |
| 132 | [ ] Subsidy budget approved with a published taper schedule |
| 133 | [ ] Demand gating plan (waitlist or geofence) in place to protect fill rate |
| 134 | [ ] Per-network dashboard rows created with the same bars as prior launches |
| 135 | [ ] A named owner accountable for this market reaching its live bar |
| 136 |
Discussion
Browse more free Claude skills.