Revenue Forecasting for Consulting Firms: From Guesswork to Real-Time Projections

Revenue forecasting in consulting is deceptively hard. Unlike product companies with recurring subscriptions, consulting revenue depends on a web of variables: who's assigned where, at what rate, for how long, and whether the pipeline will convert in time to fill upcoming gaps.

Most firms rely on a combination of spreadsheets, past-quarter averages, and optimism. The result is forecasts that look reasonable in January and fall apart by March. The gap between projected and actual revenue isn't a rounding error. For a 50-person firm, it can mean 100,000 EUR or more per quarter.

Why traditional forecasting fails in consulting

The core problem is that consulting revenue is assignment-driven. Every dollar of revenue traces back to a specific person, on a specific project, at a specific rate, on specific days. Change any one of those variables and the number shifts.

Spreadsheet forecasts typically start with a top-down assumption: last quarter's revenue plus some growth percentage. But that ignores the reality on the ground. If two senior consultants leave, a major project ends early, or a deal slips by three weeks, the forecast is already wrong. And because the spreadsheet doesn't update itself, no one knows until the month closes.

Bottom-up forecasts are more accurate but brutally time-consuming to build manually. You need to sum up every active assignment, account for time off and holidays, factor in rate changes, and then layer in pipeline deals with probability weightings. By the time you finish, the inputs have changed.

The building blocks of an accurate forecast

A reliable revenue forecast for a consulting firm needs four inputs. First, confirmed assignments: who is working on what project, at what rate, on which days. This is your baseline, the revenue you can count on if nothing changes.

Second, time off and holidays. A consultant billing 1,200 EUR per day who takes two weeks of vacation in Q2 represents 12,000 EUR less revenue than a naive calculation would suggest. Every holiday and PTO day needs to be subtracted from the projection.

Third, project end dates. If a project ends in six weeks and there's no follow-on work lined up, that consultant's contribution to revenue drops to zero. Your forecast needs to reflect the cliff, not assume the project continues indefinitely.

Fourth, pipeline deals with probability weightings. A deal at 80% likelihood that would start next month and staff three people for six months is worth including, but at a discounted value. A deal at 20% is noise. The ability to layer weighted pipeline revenue on top of confirmed revenue gives leadership a range rather than a single number.

Real-time beats monthly

The biggest shift firms can make is moving from periodic forecasting to continuous forecasting. When your revenue projection updates automatically as assignments change, you don't need a monthly forecasting ritual. You just look at the dashboard.

If a project manager extends an assignment by two weeks, the forecast adjusts. If someone goes on unexpected leave, the impact is visible immediately. If a deal closes and you promote simulation assignments to real ones, the revenue appears in the projection the same day.

This isn't about precision for its own sake. It's about reaction time. A firm that sees a revenue gap six weeks out can do something about it: accelerate a deal, extend a project, or adjust hiring plans. A firm that discovers the same gap in a month-end report can only explain it.

Connecting sales pipeline to capacity

Revenue forecasting doesn't exist in isolation. It's tightly connected to capacity planning and sales. The best forecasting setups let you answer a simple question: if we win this deal, what happens to our numbers?

This is where simulation becomes critical. By modeling a potential deal as a hypothetical project with assigned consultants, rates, and dates, you can see its impact on both revenue and utilization before you commit. You can compare scenarios: what if we win Deal A but not Deal B? What if both close but Deal B starts a month late?

When sales, delivery, and finance all look at the same projection, decisions get better. Sales knows which deals to prioritize based on available capacity. Delivery knows what's coming and can prepare. Finance can give the board a forecast that's grounded in reality, not hope.

What good forecasting looks like in practice

A well-run consulting firm should be able to answer these questions at any time: What is our projected revenue for the next 3 months based on current assignments? Where are the gaps, and how large are they in EUR? Which pipeline deals would fill those gaps if they close? What's our best-case and worst-case scenario?

If answering any of these takes more than 30 seconds, there's room to improve. The data already exists in your assignments, rates, and pipeline. The question is whether it's connected and visible, or scattered across spreadsheets that someone updates when they have time.

Start with what you have

You don't need perfect data to start forecasting better. Begin with confirmed assignments and rates. That alone gives you a baseline projection that's more accurate than a top-down guess. Then layer in time off and holidays to refine it. Then add project end dates so you can see where revenue drops off.

Pipeline integration and scenario modeling come next, but even without them, an assignment-based forecast puts you ahead of most firms. The goal is to replace the quarterly forecasting scramble with a living projection that leadership can trust and act on.