Recurring Revenue
The Recurring Revenue module forecasts income from subscriptions, contracts, or any other recurring billing arrangement. It supports two complementary input approaches: Subscription Management (tracking customers and churn) and Subscription Model (modelling revenue growth by product).
When to use Recurring Revenue
Use this module when:
- Your revenue is based on subscriptions, retainers, or recurring contracts
- You want MRR/ARR metrics in your forecast and dashboard
- You need to model customer churn, new customer acquisition, and upsell/expansion
Creating the module
- In your Scenario, click Add a budget.
- Choose Recurring Revenue.
- Follow the setup wizard.
Step 1 — Introduction
Set the forecast period and select your products (or subscription tiers). Each product in the module represents a distinct revenue line — e.g. "Starter Plan", "Growth Plan", "Enterprise".
You can configure the module with one or both input modes per product.
Step 2 — Subscription Management (optional)
Subscription Management tracks the customer lifecycle — new customers, churn, and the resulting active subscriber count over time.
To enable Subscription Management, click the Use existing contracts toggle at the top of the step to set it to On.
For each product:
| Input | What it means |
|---|---|
| Start date | When tracking begins for this product |
| End date | Forecast end for this product |
| Churn rate (%) | Percentage of active subscribers who cancel each month |
| New customers / month | Planned new customer additions |
| Integration sync | Pull actual subscriber counts from a connected integration (Stripe, Teamleader) |
The integration sync type determines how data is loaded:
- Dynamic: Reads period-by-period changes (more granular, requires integration support)
- Snapshot: Takes a point-in-time subscriber count from the integration
Subscription Management drives the subscriber count that Subscription Model uses to calculate revenue.
Step 3 — Subscription Model
The Subscription Model defines how much each subscriber pays and how the revenue is recognised.
For each product:
| Input | What it means |
|---|---|
| New customers | Number of new customers per month (can override Subscription Management) |
| Monthly growth % | Optional growth rate applied on top of new customers |
| Period distributions | How revenue is spread within a billing period (e.g. for annual contracts paid upfront, how is the revenue recognised monthly?) |
| Billing information | Billing frequency, price per period |
Revenue recognition
For products with annual billing (e.g. a customer pays €1,200/year upfront), the Subscription Model can spread recognition over 12 months (€100/month) rather than booking the full amount in month 1. Configure the period distribution to match your accounting policy.
Step 4 — Mapping
Assign budget accounts for each product's revenue. You can map:
- All products to a single "Recurring Revenue" budget account
- Each product to its own account (for per-product P&L reporting)
- Revenue recognition accounts separately from billing accounts (for deferred revenue)
Step 5 — Result
Review the monthly recurring revenue forecast showing:
- MRR per product
- Total MRR / ARR
- New MRR, churned MRR, net MRR change per month
- Revenue recognition amounts (if deferred revenue is configured)
Integrations
Connect Stripe or Teamleader to pull actual subscriber data into the Subscription Management step. Once connected:
- Past months use actual subscriber counts from the integration
- Future months use your configured growth/churn assumptions
- You get an actuals + forecast view in one module
Dashboard metrics
The Revenue dashboard shows the Recurring Revenue module output with:
- MRR trend over time
- New vs. churned MRR waterfall
- ARR (MRR × 12)
- Net Revenue Retention
These metrics are calculated directly from the module's subscriber and revenue data.
Combining modes
You can use Subscription Management without Subscription Model (just track customers, no revenue model yet), or Subscription Model without Subscription Management (model revenue growth without tracking individual customers). Using both gives the fullest picture.