Software Contracts
The number of distinct active software product or service agreements you hold at a point in time.
◆ Count
Formula
What it measures
A point-in-time headcount of distinct live software agreements (month-end snapshot). It includes SaaS subscriptions, software licenses, and software maintenance plans. It excludes professional-services-only contracts, expired or churned agreements, and any non-software revenue line — only standing software agreements that are live as of month-end are counted.
Why it matters
Software Contracts measures the breadth of your software customer base independent of price. A vendor with 1,000 software contracts has wider market penetration than one with 100 high-ticket deals, and the count moves for reasons revenue alone hides. Your board and finance team watch it because it isolates three signals: acquisition momentum in the software line (new agreements added), retention health (non-renewals pull it down), and the installed base available for expansion. Separating it from total contracts is what tells you whether your recurring software business is healthy when you also sell implementation services.
How to read it
Read Software Contracts as a snapshot headcount, never as a single hero number — track it as a trend. A count of 250 means 250 distinct live software agreements as of month-end. Month-over-month growth (250 to 280) means new bookings and renewals outran churn and non-renewals; flat or falling means the reverse. Watch three things together: the absolute count (penetration), the net month-over-month change (new minus churn), and the composition by product tier or region (where growth concentrates). Then cross-read against software revenue: if contracts climb but revenue is flat, your average revenue per contract is eroding.
What good looks like
Good
Software contracts grow month-over-month on new wins and renewals, with new additions comfortably outpacing churn and non-renewals.
Watch
Count is flat or wobbling, with new sales roughly cancelled out by non-renewals or customers dropping the product.
Bad
Count is shrinking as churn outruns new bookings — a sign of weak product-market fit or competitive pressure in the software line.
Watch-outs
- Double-counting renewals. A multi-year deal that renews in the same period is still one live agreement, not two — update the record so the expiring and renewing rows don't both count.
- Including expired, pilot, or trial contracts past their end date. Any agreement whose end date precedes the measurement date is inactive — lean on the status field and end-date logic to exclude them cleanly every month.
- Mixing software and services on bundled deals. For a single agreement covering software plus professional services, decide once whether it counts as a software contract (software component is live) and apply that rule consistently month to month.
- Reading the count without revenue. Growing contracts alongside flat or falling software revenue signals pricing pressure, downgrades, or a slide to cheaper tiers — always pair the count with average revenue per contract.
Worked example
Hypothetical
You sell three software products: Product A (a SaaS app), Product B (a licensed desktop tool), and Product C (a recurring support plan). On June 30 you have 180 live Product A agreements, 95 Product B, and 160 Product C — some customers hold more than one — for a software contracts count of 435. In July you add 15 Product A customers, 2 Product B agreements renew with no churn, and Product C loses 3 to churn while gaining 5. Your July 31 count is (180+15) + (95+2) + (160-3+5) = 454, a net gain of 19 contracts.