MarqIQ
Browse all help topics
Explainer8 min read

How a stage win rate and a slip are measured

Last updated 26 September 2026Available onFree TrialProBusinessEnterprisePartnerNeedsHubSpotSalesforcePipedriveThe Forecast accuracy analysis needs a deal's change history for its stage, its forecast category and its close date. Only these three tools carry it. Verified on a live HubSpot portal; Salesforce reads Opportunity History and Pipedrive its per-deal changelog, neither of which has yet run against a customer account.

A stage's win rate counts every closed deal that was ever in that stage, whether it moved forwards from there or was lost from there. Everything on the Forecast accuracy tab is read from each deal's change history, as the fields stood before the deal was decided, because your tool rewrites probability and close date at the moment a deal closes. If you want the win rate over your whole pipeline rather than per stage, read Read the Executive Read for a connected tool instead.

Before you start

One finished sync of a tool that carries deal history, and closed deals in it. The tab reads MarqIQ's copy of your deals, not a live call to the tool, and nothing on it changes anything in the tool.

Why history and not today's values

Your tool sets probability to 100% or 0% and the close date to the real one the moment a deal closes. Judging those fields as they stand today would make every forecast ever made look perfect, so each field is read from what it said before the deal was decided.

Which deals are judged at all

Only closed deals, and only those that were open long enough to have been forecast. A deal created and closed inside 14 days was never forecast; it was logged after the fact. Those deals are counted and named on the tile Logged after the fact, and they are in no rate on the tab.

A closed deal carrying no created date is judged, because there is no span to measure it against. Where your store holds many of those, read the Closed deals judged tile as the outer edge rather than an exact population.

The other three tiles state the population directly: Closed deals judged, Won and Lost. Read them before anything else on the page, because every percentage below rests on them.

Where your store holds more closed deals than were read, the method note says so and gives both numbers — an even sample of the closed deals in that tool.

The stage win rate

For each stage, MarqIQ takes the judged deals whose history shows them in that stage at any point before they closed, and counts how many of those were won.

  • A deal counts at every stage it passed through, so one deal appears in several rows. The rows do not add up to your deal count, and should not.
  • A deal lost from a stage is counted at that stage. Excluding it would mean each stage's win rate measured only the deals that got past it, which is a different and much flattering question.
  • Deals that are still open are in no row. A win rate is over closed deals.
  • Where the stage belongs to one pipeline, only deals in that pipeline, or deals with no pipeline recorded, are counted against it.

The table prints four columns: the stage, what your pipeline says the probability is, what it has been, and the number of closed deals behind that. The fourth column is the denominator — quote it with the third.

When a stage is called optimistic

A verdict appears only with at least 30 closed deals behind the stage and a probability configured in the tool. Below 30 the cell is blank rather than guessed at.

BadgeWhat it means
says more than it deliversThe configured probability sits more than five points above the top of the 95% range for the real win rate. Even the generous reading of your own data does not reach it
says less than it deliversThe configured probability sits more than five points below the bottom of that range
No badgeEither the two agree, or there are fewer than 30 closed deals, or the stage carries no probability

The five-point margin is there so a stage set to 60% against a real 58% is not paraded as a fault. The finding raised from this is a fault rather than a risk when two or more stages are optimistic, or when the worst one is out by 20 points or more.

Take care

A weighted pipeline is every open deal's amount multiplied by these percentages. An overstated stage inflates the weighted number the board sees every month, before a single rep has been optimistic. Reset each stage from the Has been column, and do it once a year from that year's closed deals.

A ladder that is set and switched off

Pipedrive lets a pipeline switch its deal-probability setting off while the stage probabilities sit there looking maintained. Where that is true, MarqIQ says it once, names every pipeline it is true of, and still judges those stages against what really closed — because the probabilities are what the team wrote down.

What a Commit turned into

Where your workspace has a forecast-category field, MarqIQ reads what it said 14 days before each deal was decided, and groups the judged deals by that value. The card What each forecast call turned into prints, for every category, how many were won out of how many.

Fourteen days is the look-back because it is far enough out to be a forecast and close enough in that the call should hold. A deal open for fewer than 14 days has no reading at that moment, which is why those deals are excluded from the whole tab.

A finding is raised on the commit-like category — the one whose value reads as a commitment rather than a best case or a pipeline bucket — only when it has at least 30 deals behind it and the top of its 95% range is still under 80%. Below 65% it is a fault rather than a risk.

Why only one or two owners are named

An owner is named only with five or more deals in that category. A single bad quarter on two deals is not evidence about a person, and a rumour is what it becomes once it is written down.

  • An owner is listed as reliable when at least four in five of their deals in that category were won, on five or more deals.
  • An owner is listed among the misses when their rate sits 15 points or more below the category's own rate, on five or more deals.
  • Each name carries its two counts — “3 of 11” — so nobody is described by a percentage alone.
  • The reliable owners are named before the misses, because the fix is usually to write down what they require before they use the category.

How far a close date slips

Slip is measured on won deals only, against the close date as it stood 30 days before the deal closed — the value read from history, not the one on the record now.

  • A won deal open for fewer than 30 days has no reading at that moment and is left out.
  • The figure needs at least 30 won deals with a readable date that far back. Below that, no slip is claimed at all.
  • Three numbers are printed: the median days late, the share that closed no more than a week after the forecast date, and the share that closed more than a month after it.
  • A deal that closed early is inside that first share. It is a count of deals not more than a week late, not of deals within a week either side.
  • A negative median means the typical deal closed on or before the date it was forecast for, and the sentence says so rather than printing a minus sign.

A finding is raised when three in ten won deals closed more than a month late, and is a fault rather than a risk at five in ten. The damage is stated plainly: a forecast right about who will buy and wrong about when still misses the quarter, and hiring and spend are planned against the when.

What the tab cannot tell you

  • Nothing about open deals. Every figure is on deals that have closed.
  • Nothing about a field your tool does not keep history for. Where history could not be read, the headline says so instead of showing an empty table.
  • Nothing about a stage that has fewer than 30 closed deals behind it. The row is still shown, with its counts, and no verdict.
  • Nothing about deals logged after the fact, beyond how many there were.

If it did not work

The stage rows add up to more deals than you have

Why: A deal is counted at every stage it passed through, so one deal appears in several rows.

Fix: Read each row against its own Closed deals column, never against the total. For the pipeline-wide win rate, use the Win rate tile on the Executive Read.

A stage you rely on carries no verdict

Why: Fewer than 30 closed deals reached it, or no probability is configured on it in your tool.

Fix: Widen the Created range, or set a probability on that stage. The counts in the row are usable either way.

“Closed deals have enough history to judge a forecast against” names a small number

Why: Most of your closed deals were open for fewer than 14 days, so they were never forecast.

Fix: Check the Logged after the fact tile. A large number there usually means deals are created at the point they are won, which is a recording habit rather than a forecasting one.

No slip figure appears

Why: Fewer than 30 won deals carry a readable close date from 30 days before they closed.

Fix: Nothing to fix in MarqIQ. Where your tool keeps no history on the close date, that figure will never appear for it.

A rep you expected to see is not named

Why: They have fewer than five deals in that category, which is the floor for naming anybody.

Fix: Read the category's own rate instead, and wait for the count. The floor is there so one quarter does not become a rumour.

Next steps

Related articles

Was this article helpful?