Your Forecast Is a Capacity Plan, Not a Sales Target

Most companies treat the forecast as a sales artefact. Sales owns it, sales defends it in the board meeting, and everyone else finds out what it said when the work lands. That works while the company is small enough that everyone can see everything. It stops working at the exact moment growth becomes the point.

Two different questions, one number

A forecast is answering two questions at once, and most only answer the first.

The first is commercial: what will we close, and when. That is pipeline coverage, conversion rates, sales cycle length, the usual apparatus.

The second is operational: if we close that, can we deliver it. Do we have the people, the lead times, the onboarding capacity, the cash to fund the working capital it consumes. When the forecast only answers the commercial question, it is not a plan. It is a wish with a spreadsheet attached.

What that looks like when it goes wrong

The failure is rarely dramatic. It looks like a quarter where sales hits the number and the company still has a bad quarter — because delivery slipped, onboarding queued up, churn crept in at the back door while the front door was celebrating. Or it looks like the reverse: a sales team told to slow down mid-quarter because operations cannot absorb what is already signed, which does more damage to a commercial culture than a missed target ever does.

Both are the same failure. The number was set without reference to the constraint that actually governs it.

Building the other half

The fix is not complicated, but it does require someone to own both sides of it.

Start from the constraint, not the ambition. Every business has one thing that governs how fast it can grow — engineers, production slots, onboarding hours, cash. Find it, quantify it, and express the forecast in units of that constraint before you express it in revenue. If the constraint is 40 onboarding hours a week, the revenue ceiling is arithmetic, not aspiration.

Make the assumptions explicit and shared. A forecast that says "€2M next quarter" hides everything interesting. A forecast that says "€2M, assuming we hire two people in month one, that average deal size holds, and that implementation stays at six weeks" can be argued with — and the arguing is the point. Assumptions that are written down get challenged; assumptions that live in someone's head get discovered in the retrospective.

Give the constraint a named owner. Not "operations will figure it out". A specific person accountable for whether the capacity the forecast assumes actually exists by the time it is needed.

Reforecast when the constraint moves, not when the calendar says so. Quarterly cadence is fine for reporting. It is far too slow for a business where a single senior hire slipping by six weeks changes what is deliverable.

Why this sits between the two roles

This is the clearest example I know of a problem that belongs to neither function alone. Ask a sales leader to own it and the capacity assumptions stay optimistic, because they are not the ones who have to staff them. Ask an operations leader to own it and the number becomes conservative, because sandbagging is the safe play when someone else sets the target.

It only resolves when one person is accountable for both the commitment and the ability to meet it. At Assembly, where I led revenue and operations together and we took the business to 3x its revenue run-rate in a year, the commercial result rested on operating decisions far more than on sales execution in isolation — who was resourced where, what the forecast actually assumed, whether pricing and delivery lined up at all.

The test

Take your current forecast to whoever runs delivery and ask one question: if every deal in here closes on schedule, what breaks first?

If they can answer immediately, you have a plan. If they have never been asked, you have a target — and the difference will show up in about two quarters.