Make the next decision clearer.
- Separate a current pipeline snapshot from results measured across a cohort.
- Write down the numerator, denominator, date basis and exclusions.
- Pipeline value, bookings, revenue and cash are different quantities.
- Use sample calculations to validate reports before using them in decisions.
Start with a metric contract
A metric contract is a short definition that makes a number reproducible. It specifies the business question, included records, formula, date basis, currency treatment and exclusions. It also names the person responsible for changes. Without that agreement, two accurate queries can produce different answers to what appears to be the same question.
For example, “win rate this month” could refer to opportunities created this month, opportunities closed this month or opportunities expected to close this month. Each group answers a different question. A dashboard label should identify the chosen basis so people do not compare unlike figures.
The definitions below are suggested conventions, with illustrative arithmetic you can check. They are not benchmarks for every business or a claim about the reports available in a particular Meibo plan. Validate the implementation against your own data and keep the assumptions alongside any exported report.
Separate snapshots from cohorts
A snapshot describes the records in scope at a particular moment. Open pipeline value at the end of Tuesday is a snapshot. A cohort follows a defined group over time, such as all opportunities first qualified in September. The cohort can later show what happened to those opportunities, including those still unresolved.
Dividing this month’s wins by this month’s new opportunities usually mixes different groups. The wins may have started months earlier. That calculation can exceed 100% or change sharply because of timing, without reflecting a change in the probability of winning a new deal.
Preserve the dates needed for the question. Created date, first qualified date, stage-entry dates, actual closed date and expected close date have different meanings. An expected date that changes during the sales process should not substitute for the actual close date when measuring historical results.
If the system does not store past states, be explicit about the limitation. A current export cannot reconstruct every previous stage transition or last month’s forecast. Start collecting the required history and describe what the available data can support. Do not manufacture missing events from today’s stage.
Open pipeline value: what is currently in play?
Define open pipeline value as the sum of the agreed amount field for open opportunities in the selected scope at a stated time. Specify whether the amount represents total contract value, first-year value, a proposed fee or another basis. Mixing annual subscriptions with multi-year contract totals produces a number that is difficult to interpret.
For three illustrative open deals of £10,000, £20,000 and £30,000 on the same amount basis, the open pipeline value is £60,000. It is potential business in the records. It is not automatically expected bookings, recognised revenue or cash available to spend.
Keep amounts in separate currencies unless you have an explicit conversion rule. If you use a reporting currency, record the rate source and date and apply it consistently. Also distinguish an unknown amount from zero: a missing value is incomplete information, while zero is a numerical claim.
A stage-weighted calculation multiplies amounts by assigned stage probabilities. HubSpot documents this approach for its weighted board amounts [1]. With illustrative probabilities of 20%, 50% and 80%, the same three deals produce £36,000: £2,000 plus £10,000 plus £24,000. Those percentages are assumptions, not evidence that £36,000 will close in a given period.
| Measure | Illustrative inputs | Result |
|---|---|---|
| Open value | £10,000 + £20,000 + £30,000 | £60,000 |
| Weighted value | £10k × 20% + £20k × 50% + £30k × 80% | £36,000 |
| Closed-deal win rate | 8 won ÷ (8 won + 12 lost) | 40% |
| Pipeline coverage | £120,000 eligible ÷ £40,000 remaining target | 3× |
| Median won cycle | 10, 20, 30, 40, 100 days | 30 days |
Win rate: which decisions are included?
One useful convention is closed-deal win rate: won opportunities divided by won plus lost opportunities, using actual close dates within a defined period. If 8 opportunities were won and 12 were lost, the result is 8 divided by 20, or 40%. Show the counts next to the percentage so the reader can judge the sample size.
Under this convention, still-open opportunities are excluded because their outcome is unresolved. That makes the metric a description of decisions completed in the period. It does not measure the eventual success rate of everything created during that period, and it may overrepresent deals with shorter cycles.
For a creation or qualification cohort, follow that original group and report won, lost and still-open counts separately. A cohort with 8 won, 12 lost and 10 still open has 30 opportunities. The eventual win rate is not yet known. Reporting only the resolved cases without showing the remaining ten can give a misleading impression.
Use consistent treatment of reopened deals, duplicate records and no-decision outcomes. Decide whether a later reopening creates a new opportunity or updates the existing one, and preserve the history needed to interpret reports. Segment results where the buying process differs, rather than comparing unrelated teams as though their inputs were identical.
Stage conversion: where does progression change?
Define stage conversion using a consistent set of opportunities that entered the starting stage. Then specify the event that counts as success and the observation window. For example, of 25 opportunities that first entered discovery in a selected cohort, 15 had reached proposal by the review date: 60% had progressed by that date.
The other ten are not necessarily lost. Some may still be in discovery, have skipped to a later stage or have closed. Report those outcomes separately and explain how skipped stages are treated. If a deal returns to discovery, count unique opportunities for this definition rather than counting every entry as a new deal.
A ratio between today’s number of proposals and today’s number of discovery deals is not a stage-conversion rate. Those are different groups with different arrival times. Use it as a snapshot comparison if it is useful, but label it accordingly.
Investigate a change before diagnosing a problem. A lower progression rate could reflect stricter qualification, a different acquisition channel or a cohort that has not had enough time to progress. The number identifies a question. Deal evidence and process context help explain it.
Deal age and sales cycle answer different questions
Open deal age measures elapsed time from a defined starting event to the snapshot date. Sales cycle measures elapsed time between a starting event and an outcome. Choose whether the starting event is creation, qualification or another consistent milestone. Changing it halfway through a report changes the meaning of the result.
For a small illustrative set of closed-won cycle lengths of 10, 20, 30, 40 and 100 days, the median is 30 days and the mean is 40 days. Both are valid summaries, but the long deal affects the mean more strongly. Keep the sample size and range visible, especially when there are few outcomes.
A closed-won cycle describes wins. It does not describe how long lost opportunities take, or how long unresolved opportunities have been waiting. Report those groups separately when the distinction matters. An apparently improving cycle can coincide with a growing backlog of old open deals.
Use age as a review signal with context. A tender awaiting a published decision date is different from a proposal with no buyer response. Compare similar processes and inspect the next action before declaring a deal unhealthy. A single universal “stale after seven days” rule may not fit your business.
Coverage: align the pipeline with the target
Pipeline coverage compares relevant open pipeline with a remaining target on the same basis. In an illustrative example, £120,000 of eligible open opportunities divided by a £40,000 remaining bookings target produces 3× coverage. The opportunity set must match the target period, currency and amount definition.
Decide what makes an opportunity eligible. A deal expected to close next year should not casually support this quarter’s coverage. Neither should two mutually exclusive proposals for the same purchase be treated as independent opportunities without adjustment.
Three times coverage does not guarantee target attainment, and it is not a universal recommended ratio. The useful level depends on conversion, timing, deal concentration and the reliability of the inputs. A pipeline dominated by one large uncertain deal behaves differently from many smaller opportunities.
When the remaining target is zero, the ratio is undefined and should display as not applicable. Do not show infinity as a success badge. Preserve the underlying pipeline and target values so users can understand why the ratio is unavailable.
Validate the dashboard with a small known dataset
Before relying on a report, calculate a small sample by hand. Include an open deal, a win, a loss, a missing amount, a reopened opportunity and dates near a reporting boundary. Confirm that the report includes and excludes each case according to the metric contract. Check the reporting timezone, especially around month end.
Compare the record list behind a total with the expected population. A correct-looking sum can hide a duplicated deal and a missing deal of similar value. Test grouping, currency handling and any filters carried over from a saved view. Record the date and scope of the check.
Use the metric dictionary download to document the definitions alongside these sample calculations. Review changes deliberately, and annotate breaks in comparability when the process or amount basis changes. The next pipeline review can then discuss the business question behind the number instead of debating how it was produced.
Pipeline metric dictionary.
Document the formula, population, date basis and exclusions for each measure. Use the included arithmetic examples to check your own report definitions.
Download CSVOpens in spreadsheet software. Planning worksheet, not a direct CRM import file. All example rows are illustrative.Common questions.
What is a good pipeline win rate?+
There is no single useful benchmark for every process. Compare consistently defined groups, show the sample size and investigate changes in qualification, deal mix and timing.
Is weighted pipeline a revenue forecast?+
It is a model-based amount. A forecast also needs a period, credible timing and appropriate assumptions. Weighted open value alone does not establish when bookings, revenue or cash will occur.
Can we calculate conversion from a board screenshot?+
A screenshot shows a snapshot. Cohort conversion requires evidence about which opportunities entered a stage and what happened to them over an observation period.
Which metric should a small team start with?+
Start with the decision you need to make. Open opportunities with owners and dated next actions can support daily work; consistent value and outcome definitions support later analysis. Build a small trusted set before expanding.
Sources & methodology.
Meibo’s recommended framework, with primary documentation for the specific product facts cited above. This is AI-assisted editorial content. Examples, diagrams and calculations are illustrative; they are not customer results or independent research findings.
- HubSpot — Set up and manage object pipelines
Primary documentation for the stage-weighted amount calculation. Other metric definitions and worked examples are Meibo’s stated reporting conventions, not vendor benchmarks.
Sources checked 6 October 2026. Read the editorial policy or suggest a correction.