Platform Economics Vocabulary: API Monetisation, Unit Economics, and Developer ROI

When Engineering Meets Economics

Platform engineering is increasingly a business discipline as much as a technical one. Senior platform engineers, principal engineers, and platform product managers need to justify infrastructure investment in business terms — and to understand the economic model of the platforms they build. This requires a vocabulary that bridges software engineering and economics.

Two-Sided Platform Fundamentals

A two-sided platform (or two-sided market) is a product that creates value by facilitating interactions between two distinct user groups, each of which is valuable to the other. Classic examples include payment networks (merchants and consumers), app stores (developers and users), and API platforms (developers building integrations and the end users who benefit from them).

Network effects — the phenomenon by which a platform becomes more valuable as more participants join. “Our API marketplace exhibits network effects: each new integration partner increases the value proposition for all connected platforms.”

Liquidity — in a two-sided platform context, the degree to which one side of the market can reliably find what it needs from the other side. “Low liquidity is the biggest challenge for new integration marketplaces — you need enough connectors to be useful, but connectors won’t invest in building without enough users.”

Chicken-and-egg problem — the bootstrapping challenge of a two-sided platform: you need participants on both sides simultaneously, but neither side wants to join without the other. “We solved the chicken-and-egg problem by launching with a curated set of hand-built connectors before opening the platform to third-party developers.”

Unit Economics

Unit economics describes the revenue and costs associated with a single unit of your business model — typically a customer, a transaction, or a usage event.

CAC (Customer Acquisition Cost) — the total cost of acquiring a single paying customer, including marketing, sales, and onboarding. “Our developer-led growth model has reduced CAC by 60% compared to traditional enterprise sales.”

LTV (Lifetime Value) — the total revenue expected from a customer over the duration of their relationship with the product. “An LTV:CAC ratio above 3:1 is generally considered a healthy indicator of sustainable growth.”

DAC (Developer Acquisition Cost) — the cost of acquiring a developer who builds on your platform. This is a meaningful variant of CAC for API businesses. “Our DevRel investment of £200k last year resulted in 800 new API integrations — a DAC of £250 per integration, which compares favourably to our enterprise channel.”

Gross margin — revenue minus the direct cost of delivering the service, expressed as a percentage of revenue. Infrastructure costs are a major gross margin lever for API businesses. “Improving our WASM compression reduced compute costs by 18%, which directly improved gross margin.”

API Monetisation Models

Freemium — a model where the base tier is free and users pay for higher usage limits or advanced features. “Our freemium tier allows 10,000 API calls per month, which is sufficient for developers to evaluate and build with the platform before committing to a paid plan.”

Usage-based pricing (UBP) — also called consumption-based pricing. Customers pay in proportion to how much they use the product. “We migrated from a flat subscription to usage-based pricing, which aligned our revenue more directly with the value customers derive.”

Seat-based pricing — charging per user seat, common in SaaS. Less aligned with API products, which are typically consumed by machines rather than individuals.

Tiered pricing — offering different feature sets or usage limits at different price points. “Our three-tier pricing model (Developer, Growth, Enterprise) is designed to accommodate the economics of individual developers, funded startups, and large enterprises.”

Rate limit — the maximum number of API calls a customer can make in a given time window. Rate limits are a key mechanism for enforcing pricing tiers and protecting infrastructure from abuse.

Developer ROI Language

When justifying a developer platform investment to non-technical stakeholders, frame everything in terms of return on investment (ROI).

Time to first API call — the time it takes a new developer to make their first successful API request. This is a north star metric for developer onboarding quality. “Reducing time to first API call from 45 minutes to under 5 minutes doubled our trial-to-paid conversion rate.”

Integration velocity — how quickly developers can build and ship integrations with your platform. “High-quality client libraries and code samples improve integration velocity, which translates directly to faster time-to-revenue for our partners.”

Developer churn — the rate at which developers stop using your platform. High developer churn is expensive because acquiring developers is costly and churned integrations represent lost recurring revenue.

Five Example Sentences

1. “The platform exhibits strong network effects — each additional connector increases the value of the marketplace for all existing integrators.”
2. “Our unit economics analysis showed a LTV:CAC ratio of 4.2:1 for developer-sourced customers, compared to 2.1:1 for customers acquired through outbound sales.”
3. “We adopted usage-based pricing because it eliminates the friction of large upfront commitments and aligns our revenue directly with the value customers are extracting.”
4. “Reducing time to first API call from 30 minutes to under 3 minutes was the single highest-ROI improvement we made to the developer experience this year.”
5. “The developer acquisition cost through our open-source strategy is £180 per active integrator, which is six times lower than our paid acquisition channels.”

Communicating to Leadership

The most effective platform engineers who communicate upward translate everything into business outcomes. Don’t say “we improved the SDK”. Say “we reduced time to first API call by 83%, which improved our trial-to-paid conversion rate by 22% and is projected to add £340k in annualised revenue.” Numbers, causality, and business impact — that is the language of platform economics.