Weighted Pipeline vs Commit: Which Number to Trust
Weighted pipeline vs commit: one is an average over many deals, the other a named list you would bet on. Learn what each is for and why they must never merge.
Weighted pipeline versus commit is the difference between an average and a bet: the weighted pipeline is every open deal times its stage probability, good for judging next quarter, while the commit is a named list of deals you would stake your credibility on closing this period. They answer different questions, and the damage comes from treating one as the other.
There is also a third figure, best case, and the three belong side by side every time you report.
Weighted pipeline vs commit: two questions, two numbers
Start with the questions, because the numbers follow from them.
- Do we have enough pipeline to hit next quarter? That is a question about averages over time.
- Which deals will actually close this month? That is a question about specific deals.
The weighted pipeline answers the first. The commit answers the second. Neither can stand in for the other, and a good deal of forecasting grief is simply someone asking one question and quoting the answer to the other.
| Figure | How it is built | Best used for | Wrong to use for |
|---|---|---|---|
| Weighted pipeline | All open deals multiplied by their stage probabilities | The long range: is there enough pipeline for the coming quarter | Predicting a single month |
| Commit | Specific deals, named one by one, that you would stake your credibility on | The near term: this period's likely closes | Judging whether the pipeline is healthy overall |
| Best case | Commit plus the deals that could close if things go well | Showing the upside | Reporting as if it were commit |
Why the weighted pipeline fails on a single month
The weighted figure is arithmetic on averages, and averages need volume to behave. A month contains a handful of deals. No deal closes for a fraction of its value: it closes for all of it, or for none of it. Multiply a sizeable deal by a probability below one and you get a number that the deal will never actually produce.
Over a long enough run and across enough deals, the misses and hits cancel and the weighted figure turns out to be a fair description of what the pipeline is worth. Over one short period it is, in the guide's phrase, fiction with a currency symbol. A founder who plans a month around it is planning around a number that cannot happen.
With a small pipeline the problem gets worse. When you only have a dozen open deals, one large one can outweigh the rest, and the total tells you nothing about any outcome you will see. That is why the large deals should be named individually and not left inside a total. If you are still working out the probabilities that feed it, see how to set stage probabilities.
What the commit is, and what it is not
The commit is a list, not a calculation. Each deal on it is there because someone would stake their credibility on it closing in this period, and each is listed by name. It is deliberately small and deliberately specific.
It is also not a feeling. A deal belongs in commit because it meets written criteria, not because the number is short and someone would like it to be longer. Those criteria deserve their own treatment, which they get in how to decide what goes in sales commit.
Because the commit is named, it can be inspected. You can walk it deal by deal each week, ask what has happened since last time, and take out any deal that no longer qualifies. A weighted total cannot be interrogated in that way, since there is no single thing inside it to ask a question about.
The third number: best case
Best case is the commit plus the deals that could close if things go well. It is legitimate, and it is useful, as long as it is labelled as the upside and not as the plan.
The failure is presenting best case as commit. The gap between the two is information: it tells the reader how much of the period depends on things going well. Collapse that gap and you guarantee a miss, and you damage trust in every later figure, because the reader learns that the number you quote is the optimistic one.
How to report all three, every time
The simplest habit is to write the three numbers next to each other whenever you share a forecast. Nothing else needs to change. Once they sit together, the gaps between them become something you can read instead of something to be embarrassed about.
| If you see | It may mean |
|---|---|
| Weighted pipeline far above commit | Stale deals or optimistic stages are inflating the weighted figure |
| Commit well above recent closing trend | Something is different this time, and you should ask what |
| Best case barely above commit | Little upside is left; the period depends on the named deals |
| Trend well above both | The pipeline may be under-recorded |
The trend in the last two rows is a third estimate that fails differently from the other two: what you have actually closed in recent months, projected forward. Comparing all three is how a forecast is checked against itself, and it is described in how to calibrate a sales forecast.
Which number may bear which decision
Decide in advance which figure each kind of decision is allowed to rest on, and write it down while things are calm. A strong pipeline week is exactly when someone will want to lean on the biggest number available.
| Decision | Figure it may rely on |
|---|---|
| Taking on a person | Revenue already contracted plus the commit, and never the upside figure |
| A short marketing experiment | The weighted pipeline can reasonably support it |
| A timeline for raising money | The commit, discounted by how often your dates have slipped |
| The cash plan | Commit converted to cash terms; weighted pipeline only as a labelled upside line; best case not at all |
The cash plan row is worth a moment. A hiring offer is hard to take back, so it should sit on the sturdiest figure you have. The way commit becomes a cash figure is covered in how to turn a sales forecast into a cash plan.
How the weighted figure inflates without anyone noticing
Even for its proper job, the weighted pipeline can be quietly wrong, and it helps to know the usual causes before you rely on it.
- Old deals. A deal that has been open for about twice the typical length of your sales cycle is no longer an average deal at its stage. It has stalled, and the percentage on its stage no longer fits it. Old deals inflate the weighted figure more quietly than anything else.
- Borrowed probabilities. Software defaults describe nobody's pipeline. Percentages that feel authoritative drift further from reality every quarter they go unchecked.
- Deals never marked lost. A pipeline that only grows is not healthy, it is unweeded. Hopeful deals that nobody closes out keep adding value to the total.
- Stages entered on hope. If a deal can move forward because the seller feels good about it, the probability attached to that stage stops meaning anything.
Each of these is a maintenance failure, not an arithmetic one. The sum is correct; what goes into it is not. That is why the weekly routine of looking at what changed, and at the oldest open deals, matters as much as the formula. If a weekly review is missing, the weighted figure will look steady while the pipeline underneath it ages.
The same goes for the commit, from the other direction. Its typical failure is not stale deals but a list padded to reach a number. A written entry rule is the defence, and so is a rule about slipping dates, which is covered in how to handle slipping deals.
A short test for any forecast figure you are handed
When someone shows you a number, ask three things before you act on it.
- Which of the three figures is this: weighted, commit or best case?
- Is it being used for the question it was built to answer, near term or long range?
- Are the other two figures sitting beside it so the gaps are visible?
If the answer to the first question is unclear, the number has already been blurred, and the safest response is to ask for it to be restated before any decision is made from it.
A way to keep the two apart in your head
Think of the weighted pipeline as a measure of the field and the commit as a list of the crops you are sure of. The field tells you whether there is enough growing to feed you next season. It does not tell you what you will pick on Thursday. When someone asks about Thursday, point at the list, and when someone asks about next season, point at the field.
This is only an aid to memory, not a rule from the method. The rule is simply that each question gets its own figure, and the figures are never merged.
What the habit changes in practice
Teams that keep the three figures separate stop having two particular arguments. The first is the panic over a healthy pipeline, which happens when someone reads a low commit for a short period as a verdict on the whole pipeline. The second is the quiet overhiring that happens when a large weighted total is treated as money already won.
Both mistakes come from the same place: using a figure for a question it was never built to answer. Separate the figures and each one can be right about its own job.
Frequently asked questions
Which is more accurate, weighted pipeline or commit?
They are accurate about different things. The weighted figure is a fair description of the pipeline's worth over time and across many deals. The commit is a better guide to a single near-term period, because it is built from specific, named deals.
Should the commit and the weighted pipeline ever match?
There is no reason for them to. They are built differently and answer different questions. When they diverge, the divergence is the finding, so look at why before trying to close the gap.
Is best case a bad number?
No. It is legitimate as the upside. The failure is reporting it as if it were commit.
What if I only have a few deals?
Then lean on the commit and name every large deal individually. A weighted total built from a handful of deals is a polite fiction, so use it with care.
The full method, with the checklists, is in The Sales Forecast Playbook, a free 33-page playbook.