API-First

An API-first business packages a capability — payments, messaging, mapping, identity, compute — and sells access to it programmatically. The customer is a developer, and the product is consumed inside someone else's application rather than used directly.

Pricing is usually usage-based, so revenue grows alongside a customer's own success. Adoption depends heavily on documentation, reliability, and developer experience.

Customers are billed for what they consume — API calls, messages sent, records processed, compute used. Revenue therefore grows as the customer's own product grows, without any renegotiation. The trade-off is that revenue also falls if a customer's usage declines.

• Net revenue retention, typically strong from usage expansion
• Usage growth within existing accounts
• Time to first successful API call — a proxy for developer experience
• Gross margin after underlying infrastructure or carrier costs
• Customer concentration by usage volume

Net revenue retention well above parity driven purely by usage growth. Gross margin healthy after infrastructure costs, not just at the revenue line. A broad base of developers adopting without sales contact. No single customer representing an existential share of volume.

• Infrastructure API — compute, storage, or networking
• Communications API — messaging, voice, or video
• Data API — access to a proprietary or aggregated dataset
• Embedded finance API — payments, lending, or banking primitives

• What is net revenue retention from usage expansion alone?
• What is gross margin after underlying infrastructure cost?
• How concentrated is usage among the top customers?
• What stops a large customer building this in-house?
• How long does a new developer take to reach first successful call?