Analysis
Most forecasts multiply deal value by a stage probability nobody has checked. The gap between that number and the win rate, and how to measure it in your CRM.
The short answer
A sales forecast is usually wrong because it multiplies deal value by a configured stage probability that nobody checked against outcomes. On one pipeline, Contract Sent was set to close nine in ten and closed about half, a $1.34M gap on a $4.02M weighted pipeline. Measure each stage's real conversion on your closed deals and forecast from that.
How Kaypo answers this on your pipeline
30 minutes with the founder
Thirty minutes on your pipeline or the example one. Pick a time and it is booked.
Almost every CRM ships default probabilities per stage, and almost every company keeps them. The forecast is that percentage times the deal value, summed.
The assumption is that every deal in a stage behaves like every other deal in that stage. It is testable in one query, and it is almost never tested.
Early stages were roughly honest. Late stages were not. Contract Sent configured to close nine in ten, and closing about half. The gap widened the later the stage, which is the opposite direction to how confidence usually runs.
On a $4.02M weighted pipeline that is $1.34M of difference. It does not surface in a quarterly review because the forecast and the outcome are looked at months apart by different people.
One query against your closed deals. If your configured probabilities match your observed rates, you have learned something worth knowing. If they do not, you now know the size of the gap.
Weight a deal by what has actually happened on it rather than by the stage somebody dragged it to. Kaypo scores each deal from buyer behavior, shows the inputs, and back tests the weights against your own closed deals so the number is checkable rather than inherited.
Then it sends the reading to each rep in Slack every morning, which is the part that decides whether any of it changes behavior.
Configured probability against observed win rate, per stage
select stage,
count(*) as closed_deals,
round(avg(probability)::numeric, 1) as configured_pct,
round(100.0 * sum(case when is_won then 1 else 0 end)
/ nullif(count(*), 0), 1) as actual_pct
from deals
where closed_at >= now() - interval '12 months'
and stage is not null
group by stage
having count(*) >= 10
order by configured_pct desc;Recorded in the sandbox, the same example pipeline you can open yourself. Pick any part.
Deals. Every open deal, scored on what the buyer did.
Usually because it multiplies deal value by a stage probability that was set once and never checked against outcomes. The gap tends to be widest in the latest stages, where the configured number is most optimiztic.
Start by measuring your own observed win rate per stage from closed deals rather than using configured defaults. Then weight individual deals by what has actually happened on them.
The product page for this: How Kaypo works.
Reviewed November 8, 2026 against the product as it behaves today.
30 minutes with the founder
Bring this question and your own deals. Pick a time and it is booked.
Next step
The real product on invented B2B software companies. Nothing to connect and no signup.
Open the Overview in the sandboxThe whole product on an example pipeline: scores, next steps, plays and agents. No signup and no call.
$1,500 a month, or $15,000 a year, for one admin and up to 15 users. Free for 14 days, no card.
Or get the free report on your own closed dealsOr talk it through with a person, 30 minutes