What is a developer tools or API business worth?

A developer tools or API business sells something other companies build into their own products, and that changes what a buyer is paying for. Beyond the invoice total, ask whether the usage behind it will still be there under new ownership. For two businesses with the same revenue, it is worth asking whether customers’ production code calls the service every minute or whether they could swap it out in an afternoon. This guide explains how to read that difference, what may be discounted, and how reported earnings get recast. It is general discussion of method, not an appraisal of any business, and it gives no multiple because none would be reliable.

Usage revenue is read by cohort, not by account count

Metered and tiered billing makes revenue move with customer behaviour, so it helps to ask how the same group of accounts spends over time. One useful lens is net revenue retention, which follows existing customers and shows whether their usage grows or shrinks once new sign-ups are stripped out. A business that adds many small accounts while its established accounts quietly cut usage can look healthy by account count and weak by retention. It also helps to separate a steady base from one-off spikes, such as a customer’s load test or a one-time migration, and to ask how many free-tier developers ever become paying ones. Our glossary entries on recurring revenue and customer churn cover the vocabulary.

Integration depth and the cost of switching

Switching away from an API that sits in the path of a customer’s production system can mean rewriting calls, retesting and accepting the risk of an outage during the move, whereas a tool a developer runs on a laptop may involve none of that. A buyer therefore has reason to ask where the product sits in the customer’s architecture, how many languages the SDKs cover, and whether the documentation answers questions before they become support tickets. The versioning and deprecation history is worth reading too: ask whether old versions kept working and changes were announced early, or whether migrations were forced without warning, which can point to churn that has not yet shown up in the numbers.

What gets discounted

Several features of an otherwise sound business are risks a buyer may weigh against the price, and a seller who understands them can work on them before going to market.

• A few high-usage accounts that could self-host the capability or move to a competitor, especially where no contract commits them to a term.
• Rate-limiting, billing and usage-metering logic that is undocumented or that only the founder can explain, because a buyer cannot rely on revenue it cannot reproduce.
• API keys, cloud accounts and billing-platform logins held in the founder’s personal name rather than the company’s.
• Dependence on an upstream platform or third-party API whose terms the business does not control.
• Customers on pay-as-you-go terms with no minimum commitment, compared with customers who agreed to spend in advance.

How the earnings get recast

Recasting turns the owner’s accounts into the earnings a new owner could expect, and in this sector it has its own adjustments. Hosting and infrastructure costs may rise with usage, so margin per unit of usage matters as well as headline revenue, and cloud credits or discounts that will not carry over need adjusting for. The founder’s pay can be reset to what it would cost to hire the engineers who keep the service running, including on-call cover. Government incentives are worth separating from operating earnings. The CRA says an SR&ED claim submitted with an income tax return gives access to two incentives, a deduction against income and an investment tax credit, so they result from the claim rather than from the customers. Whether any claim history comes with the business depends on the deal structure, which our answer on SR&ED credits and a change of control explains.

Why two similar-looking APIs price differently

One thing to ask is who is buying. BDC notes that a strategic buyer is often willing to pay more because they see synergies, and the buyer’s strategic interests are among the factors it says can affect the final selling price. A larger developer-platform or infrastructure company that could reach its own customers with the capability may be that kind of buyer, while a buyer valuing only the cash flow has only what the existing accounts reliably produce to go on. Part of it is the founder’s role. BDC notes that buyers may insist on a reduced price when a seller cuts all ties, and that vendor financing, an earn-out or a phased transfer of ownership are ways for a seller to stay involved.

Part of it is ownership of the code. Under the Copyright Act the author is, subject to the Act, the first owner of a work, but where an employee under a contract of service or apprenticeship made it in the course of employment the employer is the first owner in the absence of any agreement to the contrary, subject to the section’s own exceptions. An assignment of copyright is not valid unless it is in writing and signed by the owner or the owner’s duly authorized agent, and CIPO lets owners register assignments. Code written by people who were not employees, with no written assignment, can leave the business owning less than a buyer assumed. See who owns the code for how buyers check.