BuyWhere
← Back to documentation

BUY-2896_us_launch_growth_playbook

BUY-2896: US Launch Growth Playbook

Owner: Reach Prepared: 2026-04-18 Launch date: 2026-04-23 Window: 2026-04-23 to 2026-06-18

Goal

Acquire the first 1,000 US developers and AI-agent builders who create a BuyWhere API key during the first 8 weeks of the US launch.

For this plan, "user" means a US signup tied to API-key creation or developer account activation. We should not mix this with downstream end-consumer traffic from apps built on BuyWhere.

Core Hypothesis

BuyWhere can win early US growth by targeting builders already trying to ship shopping agents, deal bots, and product-comparison workflows. The strongest wedge is not generic e-commerce messaging. It is the concrete pain of scraper maintenance, product normalization, and agent tool reliability.

North-Star Metrics

Metric8-week targetWhy it matters
US signups1,000Top-line acquisition goal
Activated in 24h350Measures first-use quality, not just traffic
Activated in 7d220Measures repeat value and onboarding fit
Docs-to-signup conversion10%Validates content and CTA quality
Signup-to-first-query median timeunder 15 minutesMeasures onboarding friction
Free-to-Pro conversions40Early monetization signal
Referral-driven signups120Tests compounding growth loop

Funnel Model

These are modeled targets, not observed baselines. They should be replaced once 7 days of launch data exists.

Funnel stageTarget rateImplied volume
Landing/docs visitors to signup8%12,500 visitors for 1,000 signups
Signup to activated_24h35%350 activations
Signup to activated_7d22%220 retained activations
Signup to Pro within 30 days4%40 Pro accounts

Channel Mix

ChannelSignup targetShareWhy this channel is in the mix
Community and founder-led distribution32032%Highest intent audience for "stop scraping" positioning
SEO and launch content26026%Compounds over the full 8-week window
Direct outreach and ecosystem partnerships18018%Converts warm builders faster than broad paid
Referral loop12012%Creates a second-order acquisition engine
Paid search and retargeting12012%Captures active intent after messaging is proven

Channel Ranking by Expected CAC and Volume

This ranking is directional for launch planning. It should be re-scored with observed CAC and activation data after the first 7 days.

RankChannelExpected CACExpected volume ceilingRationale
1Community and founder-led distributionLowestHighTime-intensive but cash-light, with the strongest message-market fit for early AI-agent builders
2SEO and launch contentLowHighContent has slower ramp than social/community but compounds and supports launch discovery
3Referral loopLowMediumCheap incremental acquisition once activation is working, but depends on initial user quality
4Direct outreach and ecosystem partnershipsMediumMediumHigher labor cost per signup, but strong conversion quality from warm relationships
5Paid search and retargetingHighestMediumUseful for intent capture only after messaging is validated; easiest channel to overspend

Week 1 Targets by Channel

Week 1 covers 2026-04-23 to 2026-04-30 and is designed as a launch burst plus instrumentation validation window.

ChannelWeek 1 signup targetWeek 1 activation targetPrimary metricGuardrail
Community and founder-led distribution8534 activated_24hsignup rate from tracked community clicksNo more than 2 low-context posts per community
SEO and launch content4012 activated_24hblog/docs visitor-to-signup conversionCTA CTR on launch pages must stay above 5%
Direct outreach and ecosystem partnerships5525 activated_24hreply/DM-to-signup conversionPrioritize warm intros over cold list volume
Referral loop104 activated_24hreferral signup shareOnly trigger once first-query success events are stable
Paid search and retargeting00n/a in launch weekPaid remains off until launch-week messaging baseline is clear

Total week 1 target: 190 signups and 75 activated_24h. The remaining gap to the phase target should come from launch-day spikes and direct follow-up if Product Hunt, Reddit, or partner traffic outperforms plan.

Channel Strategy

1. Community and Founder-Led Distribution

Hypothesis: Developers already discussing MCP, tool-calling, shopping agents, and price-comparison workflows will convert if the message is concrete and technical.

Primary surfaces:

Target:

  • 320 signups
  • Visitor to signup conversion: 12%
  • Activated_24h: 40%

Execution:

  • Publish 2 high-value launch posts during launch week
  • Ship 3 to 5 substantive community replies per day for the first 14 days
  • Route all links through channel-specific UTM tags
  • Push "MCP quickstart" and "compare prices across Amazon, Walmart, Target" as the primary proof points

2. SEO and Launch Content

Hypothesis: Bottom-funnel search demand exists around price comparison APIs, shopping-agent infrastructure, and merchant-specific comparisons. BuyWhere should win by shipping intent-specific pages faster than larger but less agent-native competitors.

Primary assets already in repo:

Target:

  • 260 signups
  • Visitor to signup conversion: 6%
  • Activated_24h: 30%

Execution:

  • Publish the US launch announcement on 2026-04-23
  • Add 3 "build with BuyWhere" posts over the next 3 weeks:
    • price comparison API for AI shopping agents
    • how to avoid scraper maintenance for shopping agents
    • MCP quickstart for commerce tools
  • Expand the current US compare page set to 20 pages by 2026-05-15
  • Add CTA blocks on every US content page pointing to docs and free API signup

3. Direct Outreach and Ecosystem Partnerships

Hypothesis: Warm outreach to AI-agent builders, developer advocates, and ecosystem operators will outperform cold paid acquisition for the first 100 to 250 signups.

Primary targets:

Target:

  • 180 signups
  • Reply/DM to signup conversion: 15%
  • Activated_24h: 45%

Execution:

  • Secure 20 warm ecosystem conversations by 2026-05-07
  • Prioritize directory listings and community intros over generic email blasts
  • Offer a launch incentive for the first 100 US developers: higher free quota or white-glove onboarding

4. Referral Loop

Hypothesis: Developers who successfully get to first query are likely to know at least one other builder working on adjacent tooling.

Target:

  • 120 signups
  • Referral share of total signups: 12%

Execution:

  • Position referral as "invite another builder, both get extended quota for 30 days"
  • Trigger referral prompt after first successful query and after day-3 email click
  • Measure via referral_signups, referral_code_used, and signup_referrer

Retention Hook Strategy

Retention needs to start inside the first session, not after a generic lifecycle email. The initial hook is "get to a successful product query quickly, then give the builder a reason to come back with live pricing value."

1. First-Query Activation Hook

Hypothesis: Users who complete a real comparison query in the first session are materially more likely to return in 7 days.

Execution:

  • Push every launch CTA toward an MCP quickstart, playground query, or merchant comparison example
  • Show a "run this query next" prompt immediately after first success
  • Trigger a 24-hour reminder only for signups that have not reached first query

Primary metric:

  • first_query_latency_seconds
  • activated_24h

2. Email and Lifecycle Drip

Hypothesis: A short technical email sequence tied to product progress will improve activated_7d without creating low-intent engagement.

Execution:

  • Day 0: send quickstart email with the top 3 US merchant examples
  • Day 2: send "build a price comparison agent in 10 minutes" walkthrough
  • Day 5: send a case-study or template email featuring a concrete agent workflow
  • Day 7: send referral or extended-quota offer to users who reached first query but have not returned

Primary metric:

  • email click-to-return rate
  • activated_7d

3. Deal and Price-Change Hooks

Hypothesis: Users who set a tracked product or merchant workflow are more likely to build recurring usage than users who only test one static query.

Execution:

  • Prompt activated users to save one product, category, or merchant comparison after first successful query
  • Offer optional deal-alert or price-change notifications for saved comparisons
  • Include a launch-week example using Amazon vs Walmart vs Target to demonstrate recurring monitoring value

Primary metric:

  • saved comparison rate
  • week-2 retained activation rate

5. Paid Search and Retargeting

Hypothesis: Paid acquisition works only after organic messaging proves which framing converts. The highest-intent paid entry points are search terms around APIs, MCP, and price comparison infrastructure, plus lightweight retargeting of docs visitors.

Target:

  • 120 signups
  • CAC ceiling: $30 per signup
  • Activated_24h: 30%

Spend guardrails:

  • Week 1: $0 paid until launch messaging is live
  • Weeks 2-3: $500 search test
  • Weeks 4-8: scale only if signup CAC stays below $30 and activated_24h CAC stays below $85
  • Total phase budget cap: $1,500

Recommended campaigns:

  • Search: "price comparison API", "shopping API", "product catalog API", "MCP ecommerce API"
  • Retargeting: docs visitors and pricing-page visitors only

Do not prioritize:

  • Broad LinkedIn prospecting
  • Meta awareness campaigns
  • Sponsorship-heavy newsletter buys before conversion data exists

Weekly Plan

Phase 0: Launch Prep

Timeline: 2026-04-18 to 2026-04-22

Targets:

  • Launch assets finalized
  • UTM map finalized
  • Growth dashboard ready
  • Signup and onboarding experiments defined

Actions:

  • Finalize all US launch copy and CTA links
  • Confirm docs, signup, and MCP quickstart paths are working
  • Ensure channel-specific UTMs map into signup_discovery_path and signup_referrer

Phase 1: Launch Burst

Timeline: 2026-04-23 to 2026-04-30

Targets:

  • 250 signups
  • 90 activated_24h

Actions:

  • Launch blog post, LinkedIn founder post, X thread, Reddit post, Product Hunt presence
  • Execute the first 5 placements already queued in BUY-2681
  • Run founder-led DM and comment follow-up on every engaged thread

Phase 2: Prove Activation

Timeline: 2026-05-01 to 2026-05-14

Targets:

  • additional 300 signups
  • activated_24h rate at or above 35%

Actions:

  • Launch onboarding experiments
  • Publish first two problem-solution SEO posts
  • Start paid search test only after the launch week conversion baseline is clear
  • Promote referral loop after first-query success

Phase 3: Scale Repeatable Winners

Timeline: 2026-05-15 to 2026-06-18

Targets:

  • additional 450 signups
  • 40 total Pro conversions

Actions:

  • Scale the best two organic channels
  • Expand comparison and FAQ content
  • Increase retargeting only if it beats search on activated CAC
  • Push weekly proof posts featuring real use cases, example queries, and implementation snippets

Experiments

Every experiment needs a hypothesis, a metric, and a decision date.

ExperimentHypothesisSuccess metricDecision date
Landing page headline: "Stop scraping" vs "Build shopping agents faster"Pain-first copy will lift signup conversion+15% signup rate2026-05-02
CTA: "Get free API key" vs "Run your first product query"Action-first CTA will improve activated_24h+10% activated_24h2026-05-02
Docs-first vs playground-first onboardingPlayground-first will reduce time to first querymedian first query time under 10 min2026-05-07
Founder post vs technical post on LinkedInTechnical framing will attract higher-quality buildershigher activated_24h per click2026-05-07
Referral offer: extra quota vs onboarding callExtra quota will drive more shares at lower ops costreferral signup rate above 10% of weekly signups2026-05-14

Instrumentation and Reporting

Use the fields already present in the growth schema:

  • signup_discovery_path: channel and campaign source
  • signup_referrer: post, thread, or partner identifier
  • signup_experiment_variant: landing page and onboarding tests
  • activated_24h
  • activated_7d
  • first_query_latency_seconds
  • playground_used
  • docs_first
  • referral_signups

Reporting cadence:

Leading Indicators to Watch

If these are weak, top-line acquisition will miss:

  • Docs CTR to signup below 5%
  • Activated_24h below 25%
  • Median first query time above 20 minutes
  • Paid CAC above $30 per signup
  • Referral share below 5% after week 3

Immediate Next Moves

  1. Ship this playbook and align Lyra on the 8-week target model.
  2. Lock the launch-week UTM map across blog, social, Product Hunt, Reddit, Discord, and directory submissions.
  3. Define the first two growth experiments in the signup flow before 2026-04-23.
  4. Treat launch week as a measurement sprint, not a vanity posting sprint.
  5. Reforecast the 1,000-user target on 2026-04-30 using real launch-week conversion data.

References