Living Document · Updated April 2026

Ship Small. Learn Fast. Scale When Ready.

A bootstrapped, kill/go-signal-driven plan — start with one bike and 20 parts, grow only when the data justifies it. Updated April 8, 2026 strategy session.

12
Months to Evaluate
1
Launch Bike
20+
Verified Parts at Launch
5
Roadmap Phases
$0
Infra Cost at Launch
01

12-Month Timeline

Seasonal Peak: March – June

Plan major feature launches and content campaigns to land before riding season. Infrastructure scaling should be provisioned by late February each year.

Weeks 1 – Month 12+ at a glance
W1
W3
M2
M6
M12
Ph 0 · Data Seeding
Ph 1 · Launch
Ph 2 · Expand
Ph 3 · Monetize
Ph 4 · Scale or Exit
02

Growth Trajectory

Year 1
25K
Monthly Active Users
$30K
Annual Revenue
50
Bikes Covered
Infrastructure: <$100/mo
Team: 1–2 people
Year 2
100K
Monthly Active Users
$422K
Annual Revenue
200
Bikes Covered
Infrastructure: ~$500/mo
Team: 3–5 people
Year 3
300K
Monthly Active Users
$1.6M
Annual Revenue
500+
Bikes Covered
Infrastructure: ~$2K/mo
Team: 6–10 people
03

Roadmap Phases

Phase 0 · NOW — Weeks 1–4
Data Seeding — "Before the Ship"
Pick the launch bike, seed the data, flip the switch on affiliates
1Launch Bike (MT-07 or Ninja 400)
20+Verified Parts
3Affiliate Programs Applied
$0Infra Cost (Netlify + Neon free tier)

Product (P0 Features)

  • Compatibility lookup — bike to confirmed-fit parts
  • Affiliate links on every part card
  • 30-second contribution flow for community submissions
  • Long-tail SEO pages per part/bike combination
  • Deploy on Netlify + Neon free tier

Scope Cuts (Not in P0)

  • No community features (profiles, feeds, social)
  • No mod stacking or conflict detection
  • No white-label or API
  • No LLM integration
  • No aggressive monetization
  • No adjacent verticals

Business

  • Apply to RevZilla, Rocky Mountain ATV/MC, and Partzilla affiliate programs
  • Manual data entry — quality over quantity
  • Social/gallery features deferred to Phase 1/2
Milestone "Site is live on Netlify, one bike is seeded with 20+ parts, every part card has an affiliate link, and Google can index each part/bike SEO page."
LiveSite on Netlify
20+Parts with Affiliate Links
1/weekReddit Post
BasicAnalytics

Product

  • Full site live — compatibility lookup, affiliate links, contribution flow
  • SEO-optimized pages for each part/bike combination
  • Basic analytics (Plausible or Fathom)
  • Mobile-responsive design

Growth

  • Reddit distribution: 1 post/week in relevant subreddits
  • Track affiliate clicks, conversions, and contribution rate
  • Social/gallery features deferred until traffic justifies them
Milestone "A rider Googles '[part] for [launch bike]' and lands on our page. They find a confirmed-fit part and click an affiliate link."
10–20Bikes Covered
MonthlyRevenue Check-Ins
GrowingOrganic Search Traffic

Product

  • Add 9–19 more bikes from top sellers 2018–present
  • Seasonal content (riding season, gift guides)
  • Monitor contribution rates per bike
  • Shareable build pages (if contribution data supports it)

Growth

  • Reddit + forum engagement cadence
  • SEO compounding from part/bike pages
  • Monthly revenue check-ins vs kill/go signals
  • Contributor profiles (deferred from Phase 0/1)
Milestone "A rider on any of the top 10 best-selling bikes 2018–present can find verified, affiliate-linked parts in under 3 minutes."
>30KMAU Trigger
MonthlyRevenue Check-Ins
Kill / GoSignals Evaluated

Product (if traffic warrants)

  • Shareable build pages
  • Contributor profiles
  • Begin retailer outreach for data partnerships

Business

  • Monthly revenue check-ins vs kill/go signals
  • Retailer outreach only if traffic exceeds 30K/month
  • No aggressive monetization below traffic threshold
  • Manufacturer partnerships gated on retailer data traction
Milestone "We have a clear answer: is affiliate revenue + organic growth enough to keep going, or is retailer partnership the next unlocking move?"
Kill / GoDecision Made
12 monthsData to Decide

If GO: Scale

  • Retailer subscription program
  • Manufacturer data partnerships
  • Expanded bike coverage (200+ bikes)
  • Engineering hire if revenue supports it

If KILL: Archive

  • Archive as a passion project with pride
  • Keep live as a static reference (zero cost)
  • Document learnings for next project

Kill/Go Signals

  • GO: Traffic growing organically, affiliate revenue covering costs, contributor rate positive
  • KILL: No organic growth after 9 months, affiliate revenue flat, no retailer interest
Milestone "We have a clear, evidence-based answer on whether to scale or archive. No ambiguity."
04

Swimlane View

Lane Ph 0
W1–4		 Ph 1
W3–4		 Ph 2
M2–6		 Ph 3
M6–12		 Ph 4
M12
Product
  • 1 bike seeded
  • 20+ verified parts
  • Compatibility lookup
  • Affiliate links
  • 30-sec contribution flow
  • SEO pages per part/bike
  • Full site live on Netlify
  • Basic analytics
  • Mobile-responsive
  • 9–19 more bikes
  • Seasonal content
  • Shareable builds (if warranted)
  • Contributor profiles
  • Retailer outreach (if >30K MAU)
  • Revenue check-ins
  • Kill/go evaluation
  • GO: retailer subscriptions + mfr partnerships
  • KILL: archive as passion project
Growth
  • Netlify + Neon deploy
  • SEO pages indexed
  • Reddit: 1 post/week
  • Affiliate click tracking
  • Reddit + forum engagement
  • SEO compounding
  • Seasonal content
  • Monthly revenue check-ins
  • Kill/go signals monitored
  • Scale or graceful exit
Revenue
  • Apply to 3 affiliate programs
  • First affiliate clicks live
  • Affiliate revenue growing
  • Monthly check-ins
  • Retailer partnerships if >30K MAU
  • GO: subscriptions + data partnerships
  • KILL: zero cost static archive
Team
 Solo founder Solo founder Founder + PT community mgr (if warranted) Founder + PT community mgr GO: first engineering hire / KILL: solo
Partnerships
  • RevZilla affiliate
  • Rocky Mountain ATV/MC
  • Partzilla
  • Forum moderator outreach
  • Reddit community relationships
  • Retailer outreach begins if traffic >30K/mo
  • GO: mfr partnerships + retail scale
05

North Star Metrics

01
Affiliate Clicks / Month
The primary early revenue signal. Every click is a rider who trusted our compatibility data enough to go buy. Flat clicks after 3 months = a kill signal.
02
Organic Search Traffic
Long-tail SEO pages per part/bike combo are the growth engine. If Google is sending traffic without paid spend, the content strategy is working.
03
Contribution Rate
Community submissions per week. If riders are adding parts without prompting, the flywheel is real. If not, we have a data quality problem to solve manually.
04
Monthly Revenue vs Kill/Go Threshold
Checked monthly from Month 3 onward. Kill signal: no affiliate revenue growth after 9 months. Go signal: traffic growing organically + positive contribution rate.
05
Monthly Active Users (MAU)
Retailer outreach gated at 30K MAU. Below that threshold, stay lean and focus on SEO + affiliate. Vanity at low numbers, a trigger at high ones.
06

Risk Register

Risk Likelihood Impact Mitigation
Data Quality Erosion
Community-submitted errors degrade trust scores
 High High Reputation-weighted verification; graduated confidence scores; manual audit queue for flagged records. Trust is the product.
Community Engagement Stall
Early adopters don't contribute or contribute inconsistently
 Medium High 30-second contribution flow lowers friction to near zero. Direct Reddit/ADVrider outreach to power users from day one. Contributor profiles deferred to Phase 2 — ship the tool first, layer recognition later.
Affiliate Commission Cuts
RevZilla / Amazon reduce commission rates
 Medium Medium Diversify to 4+ affiliate programs by end of Phase 1. Phase 3 retailer subscriptions provide non-affiliate revenue base by Month 13.
Incumbent Response
RevZilla, Cycle Gear, or OEMs copy the feature
 Medium Medium Neutral positioning is the moat — incumbents can't credibly be neutral. Community data network effects create switching costs. Retailer data partnerships in Phase 3 deepen that moat before any incumbent can replicate it.
Seasonal Traffic Variability
March–June peak creates non-linear cost and revenue spikes
 High Low Auto-scaling infrastructure. Use off-season (Oct–Feb) for major feature work and data seeding. Pre-provision by late February each year.
07

Investment Thesis

Stage 1 — Phase 0–1
$0
Zero-Cost Bootstrap
Weeks 1–4
Netlify + Neon free tier. Affiliate revenue covers any costs that arise. No outside capital needed. No infra spend until traffic demands it.
Stage 2 — Phase 2–3
$0–5K
Bootstrapped
Months 2–12
Solo founder plus optional part-time community manager only if contribution volume warrants it. Affiliate revenue funds growth. No outside capital unless kill/go signals clearly say go.
Stage 3 — Phase 4
TBD at M12
Data-Driven Decision
Month 12
Capital only if kill/go signals say scale. If retailer interest is real and traffic exceeds 30K MAU, a small engineering hire may be warranted. Otherwise archive and move on.
08

Resource Reality

Phase 0–2

Solo Developer + Part-Time Community Manager

The founder handles all product, engineering, and growth. A part-time community manager (contractor, ~10 hrs/week) handles moderation, contributor outreach, and forum presence. This is the maximum viable team for bootstrapped Phase 0–2. Efficiency comes from tight scope and ruthless prioritization.

Phase 2–3

First Engineering Hire or Contractor

Shareable build pages and contributor profiles (Phase 2), plus retailer data partnerships and deep SEO automation (Phase 3), require consistent engineering attention alongside content work. A part-time contractor or second engineer unlocks Phase 3 velocity without outrunning revenue.

Phase 3

First Critical Hire: Dedicated Partnership Lead

Retail partner relationships cannot be managed part-time. A dedicated partnership lead is required to sign and retain the first 10 retail partners. This is the hire that unlocks the subscription revenue model. Timing: hire at the start of Phase 3 or when MRR exceeds $10K.

Phase 4

Scale or Exit: Explicit Decision Point at Month 12

Month 12 is a formal kill/go evaluation against pre-defined signals. If go: retailer subscriptions and manufacturer partnerships require a small sales function and additional engineering depth. If kill: archive gracefully as a passion project. Team composition scales with the decision, not ahead of it.