The startup could grow by leveraging an existing platform with a large user base. Use this skill when:
Common platforms to leverage: iOS/Android App Stores, Chrome/Firefox Web Stores, Facebook/Twitter APIs, Slack app directory, Shopify/WordPress plugins, VS Code extensions, Product Hunt.
→ Check prompt for: customer profile, demographics
→ If missing, ask: "Who are your target customers, and which platforms do they already spend time on?"
→ Check prompt for: product type, technical form factor
→ If missing, ask: "What form does your product take? Mobile app, web app, browser extension, Slack bot, etc?"
SUFFICIENT: target audience + product form factor + candidate platforms known
PROCEED WITH DEFAULTS: audience known, infer platform candidates
MUST ASK: audience is completely unknown
Use TodoWrite:
ACTION: List every platform with substantial presence of your target audience. Include:
Write to platform-map.md with estimated audience presence per platform.
WHY: Founders default to "the App Store" and miss the 10 other platforms their customers use. A developer-tool company targets VS Code Marketplace, not the Apple App Store. A productivity tool for remote teams targets Slack App Directory. Mapping reveals the best-fit platforms, not just the biggest ones.
ACTION: For each promising platform, identify what the platform's users need that the platform itself doesn't provide well. These gaps are the parasitic growth opportunities.
Classic examples:
The pattern: find what users of the big platform are struggling with, and provide the solution.
WHY: Platforms can't fix every user need — their priorities are constrained. Gaps are persistent. A startup that solves a real gap becomes the default solution for that gap and rides the platform's growth.
IF no clear gap exists → the platform isn't the right channel.
ACTION: Build the smallest product that bridges platform users to your solution. The bridge should:
Airbnb's "Post to Craigslist" feature: one button that cross-posted Airbnb listings to Craigslist. Users didn't need to leave Craigslist to discover Airbnb. This drove tens of thousands of Craigslist users to Airbnb.
WHY: A full standalone product requires users to switch platforms and learn new interfaces. A bridge meets users where they are. Bridges have higher conversion because they reduce context-switching cost.
ACTION: When a new platform launches, being on Day-1 produces:
Evernote's strategy: launched on every new platform on Day-1 (iPhone, iPad, Android, Kindle Fire). Phil Libin: "We really killed ourselves to always be in all of the App Store launches on day one."
Prepare:
WHY: Platform launch days are high-attention moments. Being in the launch-day lineup produces outsized awareness for minimal cost. Missing the window means competing with hundreds of late-arriving apps. Evernote's Day-1 strategy made the company a household name on iOS specifically because they were first.
IF no new platform is launching soon → focus on Step 3's bridge strategy on existing platforms.
ACTION: Platform leverage is powerful but risky. Platforms change rules, APIs, and access policies. Mitigate:
Cautionary tale: Zynga's Facebook dependency. When Facebook changed its platform policies and algorithm, Zynga's growth cratered. Similar issues for companies dependent on Google's SEO algorithm, Twitter's API, Facebook's News Feed.
Airbnb's Craigslist dependency: eventually Craigslist blocked the "Post to Craigslist" feature. Airbnb had by then built its own brand and growth, but the dependency was always a risk.
WHY: Platform dependency creates tail risk. The platform giveth and the platform taketh away. Mitigation isn't paranoia — it's the standard practice of any company with substantial platform exposure.
Four markdown files:
platform-map.md — Platforms where target audience spends timeplatform-gaps.md — Unsatisfied needs per platformbridge-solution.md — Minimal solution design bridging platform to productplatform-dependency-plan.md — Dependency risk mitigation planScenario: Developer tool for VS Code
Trigger: "We built a code quality tool for JavaScript developers. How do we get users?"
Process: (1) Platform map: VS Code Marketplace is where JavaScript devs live. Secondary: GitHub Marketplace, Chrome Web Store (for dev tools extensions). (2) Platform gaps: VS Code doesn't have integrated AI code quality checking — gap. (3) Bridge solution: VS Code extension that installs with one click, runs in the background, shows issues inline. (4) Day-1 strategy: watch for VS Code's next major release and be ready to integrate with new APIs. (5) Dependency risk: build a parallel web version and capture emails.
Output: Platform-native strategy with VS Code Marketplace as primary channel.
Scenario: Consumer app exploring Product Hunt
Trigger: "We're launching a new consumer app next month. Should we launch on Product Hunt?"
Process: (1) Yes, Product Hunt is an aggregator for early-adopter consumer audiences. (2) Gap: not a traditional gap, but Product Hunt is where new products get discovered. (3) Bridge: simple launch with demo video, founder story, 24-hour engagement. (4) Day-1 strategy: coordinate launch with Hacker News submission, Reddit (if appropriate subreddit), and Twitter thread. (5) Dependency: Product Hunt alone is not sustainable — use it as a launch moment, not an ongoing channel.
Output: Multi-platform launch plan with Product Hunt as the focal day-1 event.
Scenario: Chrome extension opportunity
Trigger: "Our web research tool could work as a Chrome extension. Worth the effort?"
Process: (1) Platform map: Chrome Web Store has 3B+ users, strong discovery for productivity tools. (2) Gap: Chrome's default search and bookmarking don't help with research workflows — clear gap. (3) Bridge: extension that works inline in the browser without requiring a separate app. One-click install, zero onboarding. (4) Day-1: not a new platform but consider launching via Hacker News and r/productivity as the first 48 hours. (5) Dependency: Chrome Web Store has removed extensions before (policy changes). Build a web app fallback and capture emails.
Output: Chrome extension as primary channel, web fallback for dependency mitigation.
This skill is licensed under CC-BY-SA-4.0.
Source: BookForge — Traction: A Startup Guide to Getting Customers by Gabriel Weinberg and Justin Mares.
Install related skills from ClawhHub:
clawhub install bookforge-bullseye-channel-selection — Select Existing Platforms via Bullseyeclawhub install bookforge-viral-growth-loop-design — Embedded virality overlaps with platform leverageclawhub install bookforge-engineering-as-marketing — Tools on platforms are a parallel patternOr install the full book set from GitHub: bookforge-skills
共 1 个版本
暂无安全检测报告