API-only product growth audit
API-only products are sold to developers, billed per-call (or per-month with quota), and live or die on docs quality + uptime. No UI to optimize — every dimension lives in the developer experience. Same 7-factor framework, calibrated for DX-driven growth.
What changes for API-only
- Acquisition: developer channels (GitHub stars, npm/pypi installs, Hacker News, Stack Overflow answers, technical blogs). Generic SEO is secondary — search-intent is mostly “how do I X with Y?” queries that require documentation depth, not marketing landing pages.
- Activation: time-to-first-API-call. Target <5 minutes from landing to working request. The TTFV equivalent for APIs is “working code in a real terminal,” not “account dashboard visible.”
- Engagement: daily API call volume per active developer. Strong signal: developers reading docs while writing code (referrer = docs.your-domain sustained for ≥10 minutes).
- Retention: API calls/dev/week consistency. The killer is the 2-week gap — if a developer doesn't call your API for 14 days, churn rate jumps to 70%+. Send proactive low-usage reminders BEFORE the gap.
- Advocacy: word-of-mouth via team-internal Slack channels. Cross-developer referrals are 5× more durable than consumer referrals. k-factor target ≥0.4.
- Monetization: usage-based (per-call) is the default. Free tier of ~1000 calls/mo for evaluation. Paid: $10-50/1000-calls typical. SaaS tier on top if customer enterprise-level. Math floor: cost-per-call × call-volume must clear infrastructure costs.
- Performance: p99 latency <500ms is the baseline. Uptime 99.9% is table stakes — 99.95%+ separates enterprise-ready from hobby. Edge deployment (Cloudflare Workers, Vercel Edge) for sub-100ms p99.
Common API-only growth-friction patterns
1. Docs that show what but not why
Every endpoint documented; no concept guides; no architectural overview. Developers spend hours figuring out the mental model. Add a 1-page “How it works conceptually” page + 3-5 example use-cases with full code.
2. No interactive playground
Developers want to test before signing up. Curl-only docs = 50% activation hit vs sites with an in-browser playground (Stripe pattern). Free quota with instant API key on signup = the minimum.
3. SDK coverage gaps
TypeScript + Python = 80% of API consumers in 2026. Go + Rust + Ruby = the next tier. If you have curl-only, you're losing developers who don't want to write HTTP plumbing. Auto-generated SDKs from OpenAPI spec are minimum-viable.
4. Uptime/status page hidden
Developers check status.your-domain when their app breaks. If you don't have one, they assume the worst. Status page + RSS feed + Twitter status account = the minimum trust infrastructure for paid API customers.
Run your API-only audit
60-second 7-factor wizard. For APIs, also track usage-per-developer-per-week — that's the canonical retention KPI for this archetype.
Related
- Audit for B2B SaaS (UI + API hybrid)
- Performance deep-dive — p99 latency as retention floor
- Activation deep-dive — TTFV for developer audiences