How to Forecast Sales When You Only Have 20 Deals

Why percentage forecasting fails at small scale

Most CRMs offer a weighted forecast: assign each stage a probability, multiply, sum. It looks rigorous and it is actively misleading for a small pipeline.

Take twenty deals at 50%. The weighted forecast says you will close half the total value. What will actually happen is that some whole number of those deals closes, and the outcome could plausibly be six or fourteen. The weighted number describes an average across many pipelines, not a prediction about yours.

Worse, it produces a comforting figure that is wrong in a specific direction. Percentage weightings are usually set optimistically, and applying an optimistic average to a small sample gives you a number that is confidently too high, every quarter.

The three-bucket method

Sort every open deal into one of three buckets using evidence, not feeling. The bucket is determined by what the customer has done, never by how the conversation felt.

1. Committed

   The customer has said yes and only mechanics remain: signature, paperwork, a start date. Nothing substantive is unresolved.

   The test is strict. If procurement has not started, or legal has not seen it, or a stakeholder is still unmet, it is not committed however confident the rep is.

   Counts at full value

2. Likely

   They have confirmed budget, named a decision date, and you have met everyone who has to agree. There is a real chance and a real risk.

   This bucket is where forecasting discipline lives. Be strict about the three conditions, because a soft likely bucket is how forecasts miss.

   Counts at your own historical rate

3. Possible

   Genuine interest, but something material is missing: no confirmed budget, no date, or a stakeholder you have not met.

   Count this at zero for the current period. Not because these never close, but because forecasting them is guessing and their upside belongs in the range rather than the number.

   Counts at zero

The bucket rules must be written down and applied the same way by everyone. A bucket that means something different to two salespeople is a bucket that means nothing.

Reporting a range

Give three numbers rather than one, and be explicit about what each assumes.

The gap between floor and ceiling is itself information. A very wide gap means the quarter depends on a few uncertain deals, which is a risk worth naming out loud rather than averaging away.

For the expected figure, use your own conversion rate on the likely bucket rather than a generic percentage. After two or three quarters you will know it: some teams close 60% of likely, others 35%. Yours is the only one that predicts your business.

Getting more accurate over time

Record the forecast, then record what happened. Every period, in writing. Without this you cannot improve, because you will remember the quarters you called correctly.

Look at your own error, and its direction. Consistent over-forecasting almost always means the likely bucket is too generous. Consistent under-forecasting usually means deals are being held in possible out of caution.

Track stage duration. Once you have thirty or forty closed deals, you know your median time in each stage. A deal well past that median is not on track, whatever bucket it sits in, and this is the single most useful number a small sales team can compute about itself.

Never move a deal's bucket without new evidence. The most common forecasting failure is a deal quietly promoted to likely near the end of a period because the number needs it. Every promotion should be traceable to something the customer did.

Review buckets weekly, not at period end. The weekly pipeline review is where buckets get tested against the nine questions, and a deal that cannot answer them is a deal in the wrong bucket.

All of this depends on records that reflect reality: honest stages, dated next steps, and dead deals actually closed. A forecast built on a pipeline containing six deals nobody has touched in three months is arithmetic performed on fiction, which is why the rules in CRM data hygiene come first. Kin keeps stage, next step, and the meeting history that justifies them on one record, so the bucket a deal sits in can be checked against what actually happened rather than against how it felt.