Does one-time revenue count in the Rule of 40, and how should a data license be shown?

The short answer: keep the license out of the headline score

The Rule of 40 adds a software company's revenue growth rate to its profit margin and asks whether the total reaches 40. A one-time data license distorts both halves at once: it lifts growth and margin in the year it is booked, then makes the following year's growth look weaker because the comparison base now includes revenue that will not repeat.

The fix is presentation, not avoidance. Report the headline Rule of 40 on recurring revenue (or on total revenue excluding the license), label it, and show the license on its own line in a reported-to-clean bridge. Buyers, lenders and the board then see the cash event and the underlying business separately, which is what a diligence team would reconstruct anyway.

How the Rule of 40 is built, and where a license leaks in

There is no official definition. Each company picks a growth measure and a margin measure, and that choice decides how far a one-time item moves the score.

Whatever definitions you use, apply them to every period and state them in a note to the KPI pack.

Illustrative: one company, with and without the license

Illustrative and fictional. A vertical software company grows recurring revenue 18% a year at a steady 17% EBITDA margin, so its clean Rule of 40 score is 35. In year one it signs a one-time data license worth 6% of the prior year's revenue, with a small amount of internal preparation cost.

Nothing changed in the underlying business, yet the reported score swings from comfortably above 40 to well below it. A buyer's quality-of-earnings team would strip the license out and then ask why the headline metric was not presented clean in the first place. Showing both columns avoids that conversation.

How to present a data license to buyers, lenders and the board

1. Headline on recurring revenue. Publish the Rule of 40 on recurring revenue, or on total revenue excluding the license, and say so in the label.
2. Separate line in both bridges. Add a line called data license (non-recurring) to the revenue bridge and the EBITDA bridge, with directly attributable preparation costs alongside it.
3. Keep it out of SaaS metrics. The licensee is not a subscription customer, so the payment stays out of ARR, net revenue retention, logo counts and CAC payback.
4. Explain the terms in one paragraph. State what was licensed (an agreed set of operational records), that the company kept ownership, that the license is typically exclusive for AI training for an agreed term, and that the payment was one-time. A plain summary of what is in a data license agreement helps here.
5. Agree recognition with your auditors early. Under ASC 606, a company assesses whether a license is a right to use the IP as it exists when granted, recognized at a point in time, or a right to access it over the license period, recognized over time (Deloitte's revenue recognition roadmap sets out the distinction). The answer depends on the contract, so involve the controller before signing; the controller's guide to booking a one-time license lists the questions to settle.
6. Mark the roll-off. In trailing-twelve-month reporting, note the quarter the license leaves the window so nobody mistakes the drop for a slowdown.

What a public filing shows about separating license revenue

The clearest public precedent sits in a registration statement. In its February 2024 Form S-1, Reddit disclosed that in January 2024 it had entered data licensing arrangements with an aggregate contract value of $203.0 million and terms of two to three years, and that it expected to recognize a minimum of $66.4 million of that revenue in 2024 (Reddit Form S-1).

Two lessons carry over to a private software company. Contract value is not annual revenue, so say how much lands in each period. And the filing set out the arrangements' total value, term and expected first-year recognition explicitly, which is the level of clarity a buyer will expect. Those arrangements involved continuing data access over several years, which differs from the one-time license of an agreed set of records that SourceX arranges, but the presentation principle is the same.

Is a license worth doing if it does not help the headline metric?

Often, yes, because its value shows up elsewhere. A one-time payment, typically received within about 60 days of invoicing once the buyer selects the data, is cash the company did not have to raise or borrow. It needs no new product, no added headcount and no dilution.

The Rule of 40 was never designed to capture that kind of event, which is exactly why the clean presentation matters: it lets the company take the cash without muddying the metrics that drive its valuation multiple. The same logic applies to every other EBITDA definition in the capital structure. Before anyone assumes a license moves vesting, check whether one-time revenue counts toward management incentive targets.

What this means if you introduce software companies

Software portfolio companies are among the strongest candidates because they keep years of structured, outcome-labeled records: support tickets with resolutions, pull requests and code review comments, Jira histories, product specifications, release notes and customer success notes. The baseline is a US company with 50+ full-time employees at peak (contractors excluded), several years of documented operations, rights to license the material and an authorized sponsor; the full list is on who qualifies.

When you raise it with a CFO, lead with the presentation point. Finance leaders worry first about metric hygiene, and showing that the license sits outside the Rule of 40 and ARR removes the main objection. Operating partners can usually screen several software companies in a single pass.

Partners earn 25% of the eligible platform fees SourceX collects from the referred company's licensing deals, capped at $100,000 per referred company. The reward becomes payable only after the buyer pays and SourceX receives its fee; it is never deducted from the company's proceeds, and no reward is guaranteed.

Limits and open questions

• The Rule of 40 has no standard definition, so investors may recompute it their own way. Consistency across periods matters more than the choice of measures.
• Revenue recognition for a data license depends on its terms and your auditors' judgment; nothing here determines how a specific license must be accounted for.
• Lenders, earnout counterparties and incentive plans may define EBITDA differently from your KPI pack, so check each document on its own terms.

This is general information, not legal, tax or financial advice. Confirm accounting and reporting treatment with your auditors and advisers before acting.

Next step

Use the network opportunity finder to list software companies in your portfolio or network that keep deep operational records, then register as a partner to make the introduction. A CFO who prefers to start directly can apply at sourcex.si/apply.