A 12-month breakdown of Monthly Recurring Revenue (MRR) from Autotask billing items, covering Feb 2025 through Jan 2026. This report tracks revenue trends, identifies seasonal patterns, and highlights a declining trajectory that needs attention. PSA
A 12-month breakdown of Monthly Recurring Revenue (MRR) from Autotask billing items, covering Feb 2025 through Jan 2026. This report tracks revenue trends, identifies seasonal patterns, and highlights a declining trajectory that needs attention. PSA
The data covers the full scope of Autotask PSA records relevant to this analysis, broken down by the key dimensions your team needs for day-to-day decisions and client reporting.
Who should use this: MSP owners, finance leads, and operations managers tracking profitability
How often: Monthly for financial reviews, quarterly for strategic planning, on-demand for pricing decisions
A 12-month breakdown of Monthly Recurring Revenue (MRR) from Autotask billing items, covering Feb 2025 through Jan 2026. This report tracks revenue trends, identifies seasonal patterns, and highlights a declining trajectory that needs attention. PSA
Key revenue metrics across the 12-month period (Feb 2025 to Jan 2026) from Autotask PSA billing data.
EVALUATE
ROW(
"TotalRevenue", [Revenue - Total],
"TotalCost", [Cost - Total],
"TotalProfit", [Profit - total]
)Revenue - Total by month, Feb 2025 through Jan 2026. Y-axis scaled from EUR 600K to EUR 1.4M.
EVALUATE VAR _data = ADDCOLUMNS(VALUES('BI_Autotask_Billing_Items'[item_date]), "YM", FORMAT('BI_Autotask_Billing_Items'[item_date], "YYYY-MM"), "Revenue", CALCULATE(SUM('BI_Autotask_Billing_Items'[extended_price]))) RETURN TOPN(6, GROUPBY(_data, [YM], "MonthlyRevenue", SUMX(CURRENTGROUP(), [Revenue])), [YM], DESC)The 12-month revenue data tells a clear story. After a strong April 2025 peak of EUR 1,341,613, monthly revenue has been on a consistent downward trajectory. The period from May through August 2025 held relatively stable around EUR 1.03M to 1.08M, but from September onward the decline accelerated.
The final three months are the most concerning. November dropped to EUR 927,813, December fell further to EUR 887,195, and January 2026 hit the 12-month low at EUR 770,865. That January figure sits 25% below the 12-month average and 42.5% below the April peak.
There is a seasonal component worth considering. Q4 often sees contract renewals deferred or paused over the holiday period, and January can reflect billing gaps from December closures. But a decline this steep across five consecutive months points to something beyond seasonal variation. Contract churn, pricing pressure, or a shift in service mix are all worth investigating.
The Q2 2025 spike in April is also worth understanding. If that month included one-time project billing or a large contract activation, the "peak" may not represent a realistic target. Separating recurring revenue from one-time billing items would clarify whether the baseline MRR is actually around EUR 1.0M rather than EUR 1.3M.
Revenue has dropped every month since September 2025, falling from EUR 1,002,352 to EUR 770,865 in January 2026. That is a 23.1% decline in five months. If this trajectory continues, February 2026 revenue could land below EUR 700K. The root cause likely sits in contract churn, reduced billing hours, or lost accounts.
April 2025 hit EUR 1,341,613, which is 30.7% above the 12-month average. This kind of spike typically signals one-time project work, hardware pass-through billing, or a large new contract going live. Without separating recurring from non-recurring billing items, MRR benchmarks may be artificially inflated.
The June through August period showed consistent revenue between EUR 1.03M and 1.06M with low volatility. This three-month window, free from obvious seasonal distortion, is probably the best indicator of true MRR capacity. Getting back to this range should be the first recovery milestone.
Steps to stabilize and recover MRR based on the data patterns above.
Pull all contracts that ended, downsized, or paused between October 2025 and January 2026. Quantify the revenue lost from each. This is the fastest way to identify whether the decline comes from a few large accounts or widespread attrition. Use the revenue by contract type query to break this down by service category.
The current Revenue - Total measure includes all billing item types. Create a filtered measure that excludes project milestones, hardware, and ad-hoc line items. This gives you a clean MRR number that is not distorted by one-time spikes like the April 2025 peak.
Based on the mid-year baseline of EUR 1.0M to 1.06M, a drop below EUR 950K signals trouble before it becomes a crisis. Configure a Power BI data-driven alert on the Revenue - Total measure with a monthly evaluation. This gives leadership a 30-day early warning before revenue slides further.
EVALUATE
SUMMARIZECOLUMNS(
'BI_Autotask_Contracts'[contract_type_name],
"Revenue", SUM('BI_Autotask_Billing_Items'[total_amount])
)This report uses the Revenue - Total measure, which sums all billing items regardless of type. True MRR would exclude one-time charges like project milestones, hardware sales, and ad-hoc billing. To get a pure MRR figure, filter the billing items table by contract type to include only recurring managed services agreements.
Revenue figures come from the BI_Autotask_Billing_Items table, which captures every invoiced line item from Autotask PSA. The total_amount field represents the billed amount in euros. Data is grouped by the year_month dimension from BI_Common_Dim_Date to produce the monthly breakdown.
Yes. Copy any query from the toggles above and paste it into DAX Studio or the Power BI Desktop performance analyzer. The queries reference standard Proxuma data model tables and measures that exist in every Proxuma Power BI deployment.
Connect Proxuma Power BI to your PSA, RMM, and M365 environment, use an MCP-compatible AI to ask questions, and generate custom reports - in minutes, not days.
See more reports Get started