Software Revenue
Total revenue recognized from selling software, combining recurring subscriptions and one-time licenses or non-recurring software services.
◆ Currency
Formula
Built from
What it measures
Software Revenue is the slice of total company revenue that comes from selling software — excluding hardware, physical products, and standalone professional services. It breaks into two flows: recurring (subscription fees, SaaS contracts, annual maintenance) that repeats predictably, and non-recurring (upfront license fees, implementation, one-time customization) that lands once. You sum both to get the total software value recognized in the period.
Why it matters
You track Software Revenue separately because it tells a different story than total company revenue. A business doing $10M total but only $4M in software is a services company wearing a software costume. Investors and boards scrutinize the recurring-versus-non-recurring split because subscription revenue is worth more: it's predictable, sticky, and easy to forecast. Operators use Software Revenue to judge the health of the product business on its own — independent of low-margin services. If software shrinks while services grow, you have a product-market-fit problem: customers are paying you to make the software work, not for the software itself.
How to read it
Read Software Revenue as a period total and a trend, never as a single number. Always compare month-over-month, quarter-over-quarter, and year-over-year. Growing software revenue signals real product adoption; flat or declining is a red flag. Then split it: if growth is coming entirely from large one-time license or setup fees, your subscription base may be stalling underneath a healthy-looking top line. Compare the software growth rate to total company growth — if software lags, acquisition is drifting away from the product. Segment by product line or customer type to see which offerings carry the business and which are dead weight.
What good looks like
Good
Software revenue growing faster than total company revenue, with the recurring share rising and one-time deals shrinking as a portion of the mix.
Watch
Growth flat or carried by a few large one-time license or setup deals; recurring revenue eroding as a percentage of total software revenue.
Bad
Software revenue declining, or non-recurring revenue outweighing recurring; contracts are short, episodic, or services-led rather than subscription-led.
Watch-outs
- Not separating recurring from non-recurring. A spike driven entirely by setup or license fees hides a stagnating subscription base — always break out the recurring component before celebrating top-line growth.
- Folding in unrelated professional services. Custom dev work a customer buys separately from the software is services revenue, not software revenue — bundle it in and you overstate product strength and muddy your software gross margin.
- Recognizing non-recurring revenue in the wrong period. Upfront license fees belong in the period the obligation is satisfied (delivery/acceptance), not smeared across months or pulled forward to signature.
- Mismatching the accrual term. A 27-month contract accrues at TCV ÷ 810 days, not the 365-day rate of an annual deal — using the wrong denominator silently mis-states every period.
Worked example
Hypothetical
A software company in June has three active contracts: (1) an annual SaaS subscription worth $12K, active all month; (2) a new license and implementation sale of $50K, delivered and recognized on June 15; and (3) a quarterly maintenance contract of $9K covering Q2. June Software Revenue is the recurring accruals plus the one-time license: ($12K ÷ 365 × 30) + $50K + ($9K ÷ 90 × 30) ≈ $54K.