Revenue Backlog

Goal of the analysis:

The goal of the Revenue Backlog analysis is to quantify the committed but unrecognized revenue that a SaaS company has secured from customers, typically through long-term contracts or multi-year subscriptions. Revenue backlog represents the future revenue that will be recognized over time as services are delivered. This analysis helps assess the company’s future revenue potential and financial stability, giving insight into how much revenue has already been secured for upcoming periods.

Data required:

  1. Total contracted revenue: The total value of all active contracts or subscriptions that are yet to be fully recognized as revenue.
  2. Revenue recognized to date: The portion of contracted revenue that has already been recognized as revenue.
  3. Remaining contract duration: The time remaining on active customer contracts, which helps estimate when the backlog will be recognized.
  4. Customer segmentation (optional): Data on backlog by customer segment or contract size to identify concentration risks or growth opportunities.

Detailed step-by-step instruction on how to conduct the analysis:

  1. Identify the total contracted revenue:
    • Collect data on the total value of all current contracts or subscriptions, including both short-term and long-term agreements. This represents the total revenue that will eventually be recognized over the life of the contracts.
  2. Calculate the revenue recognized to date:
    • Determine the portion of the contracted revenue that has already been recognized. This can be based on the services that have already been delivered or the time that has passed during the contract period.
  3. Calculate the remaining revenue backlog:
    • Subtract the recognized revenue from the total contracted revenue to determine the revenue backlog.
    • Use the formula: Revenue Backlog = Total Contracted Revenue – Revenue Recognized to Date
    • For example, if a SaaS company has $10 million in contracted revenue and has already recognized $4 million, the backlog is: Revenue Backlog = $10M – $4M = $6 million
  4. Segment backlog by time:
    • Break down the revenue backlog by the period over which it will be recognized (e.g., next quarter, next year). This gives insight into how much of the backlog will be realized in the near term versus the long term.
    • If relevant, use the formula: Revenue Backlog per Period = Total Revenue Backlog / Number of Remaining Periods
    • For example, if the backlog is $6 million and there are 12 months left in the contracts, the monthly backlog recognition would be: Revenue Backlog per Month = $6M / 12 = $500,000 per month
  5. Segment backlog by customer or contract size (optional):
    • Segment the revenue backlog by customer type (e.g., small business, enterprise) or contract size to assess concentration risk or identify opportunities for growth. For instance, a large backlog tied to a few key customers might indicate revenue risk if those customers churn or reduce their contracts.

Format of the output of analysis:

The output is typically presented as the total Revenue Backlog and can be broken down by time and customer segments. Example format:

  • Total Contracted Revenue: $10 million
  • Revenue Recognized to Date: $4 million
  • Revenue Backlog: $6 million
  • Backlog Recognition per Month: $500,000
  • Backlog by Customer Type:
    • Small Business: $1 million
    • Mid-market: $3 million
    • Enterprise: $2 million

This format provides a clear picture of the company’s future revenue and when it will be recognized.

How to interpret results:

  • High revenue backlog: A high backlog indicates a strong pipeline of committed future revenue, giving the company financial stability and predictability. This is particularly important for SaaS companies with subscription-based models, as it shows that a large portion of future revenue is already secured.
  • Low revenue backlog: A low backlog suggests that the company has a limited amount of committed revenue for future periods. This may indicate reliance on new customer acquisitions or renewals to drive future revenue growth. Low backlog can lead to uncertainty about future financial performance.
  • Concentration in specific segments: If a significant portion of the backlog is concentrated in a few large customers or a specific customer segment, this could be a risk if those customers churn or reduce their contracts. Diversifying the customer base can mitigate this risk.

Steps a company can take to improve on this measure:

  1. Focus on securing long-term contracts:
    Increase efforts to secure multi-year contracts or long-term subscription commitments from customers. This will boost the backlog and provide more revenue certainty over time. Offering discounts for longer contract commitments can incentivize customers.
  2. Expand upsell and cross-sell opportunities:
    Work on increasing the value of existing customer contracts by offering additional features or services that drive higher subscription levels. This will increase the total contracted revenue and, in turn, the backlog.
  3. Improve renewal rates:
    Focus on customer retention and renewal strategies to ensure that current contracts are extended. A high renewal rate ensures a consistent revenue backlog as contracts are renewed before they expire.
  4. Diversify the customer base:
    If the backlog is concentrated in a few large customers or specific segments, focus on acquiring new customers in other segments or industries. This diversification reduces the risk of revenue loss if a major customer churns.
  5. Track backlog trends over time:
    Monitor backlog trends to ensure the company is consistently building future revenue. If the backlog is declining, this could indicate issues with customer retention, new sales, or contract renewals that need to be addressed.
  6. Align sales and customer success teams:
    Ensure that the sales team is aligned with customer success to drive upsells and renewals. By working together, these teams can maximize the backlog by securing both new contracts and renewals.