API-first companies (Stripe, Twilio, Plaid) share a distinct GTM, pricing, and metrics profile. What investors look for and how to pitch one.
API-first companies sell developer primitives — payments, messaging, identity, data — through code, not sales. The business model is distinct enough that it deserves its own playbook.
The product is an endpoint, not a UI. Adoption starts with a developer running a curl command. Pricing is usage-based. Sales-assist appears only at enterprise scale. Documentation is the marketing.
Signed-up developers, active developers (calling the API in the last 30 days), API calls per active developer, revenue per active developer, time from signup to first call, time to $100 spend. NRR matters as much as it does in SaaS.
Free tier generous enough to prototype. Usage-based tiers with volume discounts. Enterprise plans with committed spend, dedicated support, and SLA. Flat SaaS pricing on an API is almost always wrong.
Developer adoption without revenue conversion. Free-tier abuse. Hyperscaler encroachment (AWS/GCP shipping a competing primitive). Documentation that doesn't get someone to first successful call in under 15 minutes.
Investor directory · Fundraising library · Articles A–Z · Company funding database