Building a 3-to-5-Year Financial Forecast for Your MSP
How to build a multi-year MSP forecast from the drivers that move it, test it with three scenarios, and keep it honest enough that a lender or buyer will believe it.
Last updated: October 7, 2026
Written by Rhett Collver, Managing Partner, C4 Solutions
An MSP financial forecast projects revenue, margin, profit, and cash 3 to 5 years out by modeling the drivers behind them, like new MRR, churn, price increases, and gross margin by service. Year one gets monthly detail. Later years, annual.
What the model has to do
A forecast earns its keep when it changes a decision. Multi-year pro forma plans are core work in our fractional CFO service, and you can build a useful first version yourself. Model drivers, not totals. Keep year one monthly. Run a base case, an upside, and a downside, and forecast cash separately from profit, since a profitable MSP can still run short of money while it waits on clients to pay. Then compare forecast to actual every month or quarter, because that track record is what makes a lender or buyer believe the next five years.
Five-year forecasts lie. Upward, usually.
That isn’t cynicism. A study of private companies in the Review of Accounting Studies found that managers’ one-year revenue forecasts ran slightly pessimistic, while five-year revenue forecasts were hugely optimistic. Near-term caution, long-term fantasy. Anyone who has built a hockey-stick spreadsheet for a bank will recognize the pattern.
Stopping isn’t the fix. Build the forecast from the handful of drivers you can actually see and measure in an MSP, so that when year three goes sideways you know which assumption broke. Plenty of owners skip this because they don’t track the drivers in the first place. In ScalePad’s 2026 MSP trends research, only 58% of MSPs said they track monthly recurring revenue and 44% track net revenue retention. Hard to forecast a number you don’t measure.
What Is an MSP Financial Forecast?
An MSP financial forecast is a forward projection of revenue, gross margin, operating expenses, EBITDA, and cash, built from the operating drivers that produce them. A 3-to-5-year version, sometimes called a pro forma, connects the growth plan to what the business could be worth and how much cash it needs along the way.
Owners mix up three documents that do different jobs.
| Budget | Forecast | Pro forma | |
|---|---|---|---|
| Question it answers | What are we committing to spend and earn? | Where are we actually heading? | What does the business look like if the plan works? |
| Horizon | One fiscal year | Rolling 12 to 18 months | 3 to 5 years |
| Updated | Once a year | Monthly or quarterly | When strategy or the market shifts |
| Who reads it | Your leadership team | You and your finance lead | Lenders, investors, buyers |
Your multi-year model belongs in the third column, built with the logic of the second.
How Far Out Should the Forecast Go?
Five years if anyone outside the company will read it, with the first year broken out by month. That’s the shape lenders expect, and it’s the same structure the SBA recommends for any business plan.
SBA guidance asks for a five-year financial outlook with forecasted income statements, balance sheets, cash flow statements, and capital expenditure budgets, and it suggests quarterly or even monthly projections for the first year. Good advice for an MSP too.
Detail should fade with distance. Year one by month, because you’ll run the business against it. Years two and three? Quarterly or annual. Years four and five annually, and honestly labeled as directional. Pretending to know your August 2030 tool spend helps nobody.
Plan for bad years as well as good ones. BLS data shows 50.6% of private establishments born in March 2013 were still operating five years later. Your MSP is past the startup stage, so those odds aren’t yours. The point stands. Five years is long enough for something to go wrong.
Which Drivers Belong in the Model?
Only the ones that actually move an MSP’s revenue and cost. Starting MRR by service, new MRR added each month, revenue churn, price increases, seats per client, project revenue, gross margin by service line, and labor capacity.
| Driver | Where the number comes from | What it moves |
|---|---|---|
| Starting MRR by service | PSA agreements tied to invoices | The base every other line grows from |
| New MRR per month | The last 24 months of closed deals, and sales capacity | Revenue growth, onboarding projects |
| Monthly revenue churn | Lost and downsized clients over 24 months | How fast growth slows as the base gets bigger |
| Price increases | Renewal dates and contract terms | Margin, with little added cost |
| Gross margin by service | Labor and tools assigned to each line | Which growth actually pays |
| Labor capacity | Endpoints or agreements per tech today | When the next hire lands |
Margin by service is where owners get surprised. A long-standing Taylor Business Group rule of thumb, published by Kaseya back in 2016, sets the bar at a 65% gross margin or better on every agreement, with MRR making up more than 60% of total revenue. Old benchmarks. Still useful ones. If your managed services line sits at 48% and licensing at 12%, growing licensing faster than managed services makes revenue climb while margin falls.
Price increases deserve their own line, with real dates. On one C4 sales consulting engagement, the client raised prices 15 to 25% across its core services and lost only a small share of low-value clients, and margins improved. Your result may differ. Model it anyway, on the renewal dates in your actual contracts rather than a blanket January 1 bump.
Labor turns smooth growth into steps. If each tech carries about 400 endpoints, client number 31 might trigger hire number six, and that salary shows up a month or two before the new MRR does. Draw it that way.
How Do You Turn Drivers Into a Forecast?
Rebuild your history by driver, set year one month by month, roll the later years forward annually from the same drivers, and only then build the profit and loss, cash flow, and balance sheet on top.
- Pull 24 months of history from the PSA and accounting system. MRR at each month end, new MRR, churned MRR, project revenue, and cost of service by line.
- Set the drivers for year one from that history, adjusted for anything you know is coming. A big client’s renewal. A planned price increase. A hire already approved.
- Model hiring as steps triggered by capacity, not as a smooth percentage of revenue.
- Build the P&L first. Then cash. Then the balance sheet. Years two through five come from the same drivers, rolled forward annually.
- Write every assumption on one page in plain English. If you can’t explain a number to your banker in a sentence, it shouldn’t be in the model.
Take a hypothetical MSP with $150,000 in MRR, a $1.8 million annual run rate, and run it under three sets of assumptions.
| Downside | Base | Upside | |
|---|---|---|---|
| New MRR added per month | $2,500 | $3,500 | $4,500 |
| Monthly revenue churn | 1.5% | 1.0% | 0.75% |
| Annual price increase | 2% | 4% | 5% |
| MRR at end of year 1 | $153,000 | $173,000 | $189,000 |
| MRR at end of year 3 | $162,000 | $223,000 | $275,000 |
| MRR at end of year 5 | $168,000 | $266,000 | $355,000 |
| Annual run rate, year 5 | $2.0 million | $3.2 million | $4.3 million |
Look at the base case closely. Sales effort never changes, yet growth slides from about 15% in year one to about 8% in year five, because the same 1% monthly churn takes a bigger bite out of a bigger base. Owners who forecast a flat 15% a year for five years are quietly assuming their sales team gets better every single year. Maybe it will. Put that in the model as a decision, with the hire and the budget attached, rather than burying it in a growth rate.
Downside barely moves. At 1.5% monthly churn, nearly every new dollar of MRR just replaces one that walked out the door.
How Should the Three Scenarios Differ?
By a few drivers, changed on purpose. A downside case should break specific things, like losing your largest client in year two or a churn spike. An upside case should require a specific decision, like a second salesperson or a new security line.
Anchor the base case to the market. Service Leadership reported 9.6% revenue growth for MSPs in 2025, up from 7.1% the year before. Omdia expects the managed services market to grow about 10% in 2026, with managed security growing faster, from $93 billion to $106 billion, according to Acronis’s summary of the Omdia forecast. A base case at 30% a year needs a reason the market isn’t giving you.
Check your optimism against your peers. In the same ScalePad research, 36% of MSPs expected 1 to 10% growth in 2026, 39% expected 11 to 25%, and 13% expected 26 to 50%. Expecting isn’t achieving, of course.
Big upside does happen. One of C4’s MSP clients grew from $2 million to $3.5 million in revenue at 20 to 30% a year after narrowing its growth to three channels. That’s a real result, and it took a deliberate plan. Treat it as an upside case with named causes, not as the default.
Where Does the Cash Go?
Into the gaps between when you pay and when you’re paid. MSPs fund new hires, hardware, and licensing commitments before clients pay for them, so a profitable forecast can still run short of cash.
Microsoft licensing is the sharp edge. Microsoft’s new commerce terms allow a prorated refund on per-user subscriptions for just seven days after purchase, and the partner owes the bill even if the customer stops paying. Annual commitments for a client who leaves in month three stay on your bill for the rest of the term, and your forecast should show that cost landing whether the client pays you or not.
Other timing gaps to model.
- New techs, paid for a month or two before the client MRR that justified them arrives
- Hardware bought for a client project before the invoice is paid
- Annual prepaid agreements, which help cash now but create work you still owe
- Receivables. If clients pay in 45 days, your cash forecast should say 45.
- Quarterly estimated taxes and owner distributions
Inside year one, keep a rolling 13-week cash view alongside the monthly forecast. It’s the early warning that the annual model can’t give you.
How Does the Forecast Connect to Value?
Through EBITDA and credibility. Buyers pay a multiple of earnings, and a forecast that you’ve hit before makes them more willing to pay for the growth it shows.
EBITDA is the simple part. Service Leadership’s top performers have kept adjusted EBITDA at 19% or higher six years in a row, and the average provider’s enterprise value rose roughly 15% from 2024 to 2025. Margin you build into the forecast, and then actually deliver, turns into price.
Credibility is harder. S&P Global’s research on big debt-financed buyouts found just 8% of companies topped management’s projected EBITDA in year one after the deal. Buyers know that. They discount projections by default. What changes their mind is a record, eight or more quarters of forecast next to actual, with the misses explained. That record is worth more than any single year of the plan. Our framework for building an MSP to sell covers the rest of what buyers look for, and our roadmap for growing an MSP from $1M to $10M shows where the drivers tend to change as you scale.
Keeping It Honest
Compare forecast to actual on a set schedule. Monthly for year one. Quarterly for the full model. Write down why each big variance happened, then decide whether it changes a driver or was a one-off.
Resist the plug. When the model doesn’t hit the number you wanted, the temptation is to nudge churn down or new MRR up until it does. Don’t. Change a decision instead, like adding a salesperson, cutting a losing service, or raising prices, and let the model show what that decision costs and returns.
Keep version history, too. A future buyer will want to see what you forecast this year.
Who Should Build It?
You can build the first version yourself in a spreadsheet. A bookkeeper usually shouldn’t, because forecasting isn’t bookkeeping. A fractional CFO makes sense once the forecast starts driving real decisions, like a big hire, a debt facility, an acquisition, or a sale.
If you’re under $1 million in revenue with one main service line, a solid annual budget and a clean monthly close may be all you need for now. Build the multi-year model when there’s a decision riding on it.
C4 Solutions is a growth and M&A advisory firm for MSPs and technology companies, based in Irvine, California. Our vCFO service runs as a standalone engagement focused on growth planning, transaction readiness, and exit value. It builds 3-to-5-year pro forma plans, scenario models, and margin plans, usually on a monthly or quarterly cadence depending on scope, with project-based work around a sale or acquisition. One MSP CEO in Southern California put it this way in a testimonial on our homepage. “Bringing in a vCFO completely transformed our financial operations.”
If you’re comparing options, our guide to fractional CFO services for MSPs lays out how the providers differ. And if you’d like a second opinion on the forecast you already have, book a growth assessment with C4.
Forecasting Questions From MSP Owners
How accurate can a 5-year forecast really be?
Not very, past year two, and that’s fine.
The value isn’t in predicting year five. It’s in knowing which driver matters when year two misses, and having a record of forecast against actual that a buyer or lender can check.
Budget or forecast, does the difference actually matter?
It does, because a budget is a commitment and a forecast is your best current read on where the business is heading.
You set the budget once a year and hold the team to it. You update the forecast every month or quarter, and when the two drift apart, that gap is the conversation your leadership meeting should be having.
How do I forecast MRR when clients add and drop seats every month?
In two layers. Forecast clients won and lost, then forecast seat changes inside the clients you keep.
Your PSA history gives you both. Net seat growth inside existing clients is a driver in its own right, and for some MSPs it adds more MRR than new logos do.
Should project revenue go in the forecast?
Keep it, but on its own line, tied to the new clients and renewals that create it.
Onboarding projects follow new MRR. Refresh projects follow hardware age. Blend projects into recurring revenue and you’ll overstate the part of the business buyers pay the highest multiple for.
How frequently should I update the forecast?
Monthly for year one, quarterly for the full model.
Rebuild it from scratch only when something structural changes, like an acquisition or a new service line.
Do I need a pro forma if I’m not selling or raising money?
Arguably more than the owners who are.
Sellers build a pro forma because a buyer asks for one. Owners who aren’t selling build one to decide when to hire, what to charge, and how much cash to keep, and they end up with a forecast track record years before they ever need it.
Build the forecast before you need it.
Book a Growth Assessment Call and we’ll review your numbers, then tell you whether a 3-to-5-year pro forma, a cleaner monthly close, or neither should come first.
Book a Growth Assessment Call