Let's grow your business. 2 new positions just opened Wednesday, 9 September. Book a free call today.
Uncategorised 15 min read

How to Calculate Sales Close Rate and the Mistake Most Teams Make

How to Calculate Sales Close Rate and the Mistake Most...: Email, SMS and voice outreach from an AI sales agent converging into a booked calendar appointment.
Email, SMS and voice outreach from an AI sales agent converging into a booked calendar appointment.

Sales close rate is deals won divided by the opportunities that reached a decision — won plus lost — measured on the cohort those deals came from. Get the denominator wrong and the same 76 wins report as 6.3%, 15%, 25.3%, 38% or 40%. Same team, same deals, five answers.

How do you calculate sales close rate?

The formula has three parts, and only the first is the one people argue about:

Close rate = deals won ÷ (deals won + deals lost), counted on a defined population of opportunities, measured after that population has had time to decide.

  • Numerator: opportunities marked closed-won in the period.
  • Denominator: opportunities from the same population that reached a terminal outcome — closed-won or closed-lost. Not opportunities still open.
  • Population: a stated stage. “Enquiries”, “qualified opportunities” and “sales conversations attended” are three different populations and give three different rates.
  • Clock: the population is defined by when it was created, and reported only once it is old enough to have resolved.

This matches how the major CRMs define it. Salesforce’s own reporting documentation gives the win-rate summary formula as WON:SUM / CLOSED:SUM — won opportunities over closed opportunities, with open pipeline excluded from both sides (Calculate Win Rate on Closed Opportunities in a Report, Salesforce Help). Most spreadsheets built by hand do not do this.

A close rate without a stated denominator, a stated stage and a stated window is not a metric. It is a number someone chose.

How it works

How to calculate a sales close rate you can defend

01

Pick the population

Choose one stage and name it: enquiries received, qualified opportunities, or sales conversations attended. Each gives a different rate from the same deals.

02

Fix the cohort window

Select opportunities by created date, not by close date. Wait until that cohort is older than twice your median days-to-close before reporting it.

03

Count decided outcomes

Split the cohort into won and lost. Open opportunities stay out of both the numerator and the denominator until they decide.

04

Divide, then label it

Wins divided by won plus lost. Publish the number with its stage, its window and its open count attached, or it will be misread.

Four steps in order. Skipping step two or three is what produces two people in the same meeting quoting different close rates for the same team.

MAKE MORE SALES.

Pay-Per-Result pricing — We scale sales HARD aligned to your interests, better than anyone else.

The mistake most teams make: open deals in the denominator

The single most common miscount is dividing wins by every opportunity created, including the ones still sitting in the pipeline undecided. This is the open-pipeline error, and it does two bad things at once.

First, it always understates. An open deal is not a loss. Putting it in the denominator books it as one before the prospect has said anything.

Second — and this is the part that causes internal arguments — the number moves when the pipeline grows, even if nothing about selling changes. Add 100 fresh opportunities today and your close rate falls this afternoon. A metric that gets worse when you generate more demand is not measuring sales performance.

Statisticians have a name for the underlying problem: the open deals are censored observations. Their outcome exists but has not been observed yet. The correct handling is to exclude them from the ratio, not to score them as failures.

The Decided-Deals Rule: an open opportunity is neither a win nor a loss. It stays out of the denominator until it decides.

Want this done for you? We book qualified sales appointments on a Pay-Per-Result basis — you only pay for calls that actually land in your calendar.

Worked example: how the same 76 deals produce five close rates

Illustrative inputs, not a client account, chosen so you can substitute your own numbers.

Take one month’s demand for a services business. March generated 1,200 enquiries. Of those, 620 were contacted, 300 met the qualification criteria, and 200 attended a sales conversation. By the end of June the March cohort had fully resolved: 76 won, 124 lost, 0 open.

Seventy-six deals. Here is every close rate that can honestly be computed from them:

Denominator used Count Rate What it actually measures
All enquiries received 1,200 6.3% The whole funnel: marketing, contact rate, qualification and closing combined
Enquiries contacted 620 12.3% Everything from first conversation onward. Blames the closer for a follow-up gap
Qualified opportunities 300 25.3% Includes qualified people who never showed up to a call
Sales conversations attended, decided outcomes only 200 38.0% The sales close rate. What the person running the call controls
Same cohort, measured at day 30 (30 won, 45 lost, 125 still open) 200 15.0% Nothing. The open-pipeline error, measured too early
Same cohort at day 30, decided outcomes only 75 40.0% An early read, biased high — fast decisions skew toward yes

Note the last two rows against the fourth. At day 30 a little over a third of the cohort had decided, which is what a 45-day median looks like at that point. The decided-only method reported 40.0% when the cohort’s true rate was 38.0%: the 75 deals that decided first won at 40.0%, and the 125 that took longer won at 36.8%. Decided-only is the right method and it is still slightly optimistic early. The all-opportunities method was out by 23 percentage points — it reported less than half the true rate.

Nobody in this example got better or worse at selling. The 6.3% and the 38.0% describe the same 76 deals.

The second mistake: measuring a period instead of a cohort

The other error is subtler and survives longer because it looks reasonable: dividing deals closed this month by opportunities created this month. Those are two different populations, because they are two different months. If your deals take about six weeks to close, this month’s wins came out of a cohort created six weeks ago, and you are dividing one month’s output by a different month’s input.

HubSpot documents the underlying property plainly: Days to close is “the time between Create date and Close date” (HubSpot’s default deal properties). If that median is 45 days, a monthly close rate is comparing wins that came out of one month’s opportunities to the opportunities created six weeks later.

The distortion is exactly calculable, assuming deals close about n months after creation. If the true cohort close rate is r, opportunity creation is growing at g per month, and the lag is n months, then:

Reported period close rate = r ÷ (1 + g)n

Two conditions, and the second is the whole point of this page. First, deals have to close roughly n months after they are created; where closing times are spread out, the reported rate is r × E[(1 + g)−L] over the lag distribution L, and the direction of the error is the same. Second, r and the period denominator have to be measured on the same population. If r is your close rate on attended conversations, the period denominator has to be opportunities created that month — attended conversations too. Divide this month’s wins by this month’s enquiries instead and you have stacked the population error on top of the timing one, and the number falls further again: on the cohort above that method reports about 4.5% at +25% monthly growth, against a true enquiry-to-customer rate of 6.3%.

With a true close rate of 38% on attended conversations and a six-week lag (n = 1.5, matching the 45-day median in the worked example), here is what the period method reports while the sales team’s performance is held perfectly constant:

Monthly growth in opportunities created True cohort close rate Reported period close rate Error
+50% 38.0% 20.7% −17.3 pts
+25% 38.0% 27.2% −10.8 pts
+10% 38.0% 32.9% −5.1 pts
0% (flat) 38.0% 38.0% 0.0 pts
−10% 38.0% 44.5% +6.5 pts
−25% 38.0% 58.5% +20.5 pts
−50% 38.0% 107.5% +69.5 pts

Read the last row. A team whose opportunity creation halves reports 107.5% — an impossible value for wins divided by decided deals, and the tell that the period method was never computing a rate at all — it measures your growth rate wearing a sales metric’s name. This is why scaling businesses conclude their closers have gone soft in the exact quarter they turned up the ad spend, and why a business in decline gets a flattering number on the way down.

If we can’t make you money, we don’t deserve yours.

Pay-Per-Result pricing — performance-based alignment.

50,769+
AI-booked appointments
Average sales lift — median closer to 4×
Pay-Per-Result
Performance-based alignment

Which close rate should you use for which decision?

There is no single correct denominator. There is a correct denominator per decision, and the discipline is stating which one you used every time you say the number out loud.

The decision you are making Denominator to use In the example
Judging a closer or coaching call technique Sales conversations attended, decided outcomes only 76 / 200 = 38.0%
Setting an appointment target to hit a revenue number Sales conversations attended, decided outcomes only 38.0% — so 100 sales for the year needs ~263 attended conversations
Deciding what you can pay for a lead All enquiries received 76 / 1,200 = 6.3% enquiry-to-customer
Working out whether the problem is upstream or at the close Both, side by side 6.3% vs 38.0% — the gap is the upstream loss
Weighting an open pipeline for a forecast Historical decided-outcome rate by stage, applied to open deals Never the raw all-opportunity rate
Comparing yourself to a published benchmark Whichever one the benchmark used — and if it does not say, do not compare

That last row is not a throwaway. Most published close-rate benchmarks do not disclose their denominator, which makes them unusable for comparison. If you are weighting open deals to build a number for the board, the stage-level decided-outcome rate is the input worth having — more on how that feeds a model in our note on AI sales forecasting and pipeline accuracy.

When is the number old enough to trust?

A cohort reports a truthful close rate only once nearly all of it has decided. The practical test we use:

The Two-Cycle Rule: do not report a cohort’s close rate until the cohort is older than twice your median days-to-close. Before that, report it as provisional with the open count printed next to it.

In the worked example the median was around 45 days, so March’s cohort was reportable from about the end of June — not on 30 April, when it would have read 15% or 40% depending on which mistake you made. The cost of the rule is that your newest and most interesting cohorts are the ones you may not conclude anything from. Inconvenient, and still correct.

The rule also exposes a data-hygiene problem most CRMs have: opportunities that are dead but never marked closed-lost. They sit open forever, they never age out, and they quietly corrupt every close-rate calculation on both methods. Auto-closing anything with no activity for three times your median cycle fixes more measurement problems than any dashboard.

What close rate tells you about your reps, and what it does not

Close rate is the metric most often used to judge a salesperson and most often caused by something the salesperson never touched. If the denominator is enquiries or contacted leads, you are grading a closer on response times, follow-up persistence and show-up rates — three things that belong to lead flow and process. In the example, the entire distance between 6.3% and 38.0% happened before anyone sold anything: 580 enquiries were never contacted, 320 contacted people never qualified, and 100 qualified people never made it into a conversation.

That is why the diagnostic order matters: compute both ends first, and only investigate call technique if the attended-conversation rate is the weak one. Response speed is the best-documented upstream driver — we keep the numbers in our lead response time benchmarks for Australia — and attendance is the other, covered in how to improve sales appointment show rates. Both move the number a manager gets blamed for.

Being explicit about our own claims, since this is a page about measurement honesty: in our own client work at LeadsNow we typically see roughly a 300% lift in conversion for a business moving from 2020-era manual operations to 2026 AI-driven operations, and most of that lift lands upstream of the close — in contact rate and set rate, not in closing skill. Our component figures are the same kind of operator claim: speed to lead alone around 3x, doubling contact rate around 2x, doubling set rate around 2x. Those do not multiply. 3 × 2 × 2 is 12x and we do not see 12x, because the levers overlap — fixing speed to lead is part of how contact rate improves, and contact rate is part of how set rate improves. These are observations from running campaigns, not a study with a sample size and a window. Where we do publish a figure with a stated method, we publish the method: our 7x average sales lift methodology defines the window and discloses that the median is closer to 4x.

What it costs to measure this properly

The method above is complete and you can run it yourself. Here is honestly what it takes, because the effort is the reason most teams do not.

  • Five fields, populated every time: opportunity created date, current stage, closed date, outcome (won/lost), and a disqualification reason. Four of these are CRM defaults. The fifth is the one that decays.
  • A cohort report, not a period report. HubSpot’s funnel reports count “the number of contacts or deals in each stage that moved through all the selected stages during the specified time range” (HubSpot funnel report types) — useful, but you still have to choose the window deliberately rather than defaulting to “last month”.
  • Setup: roughly two to four hours to build the cohort report and the auto-close rule, once. Then about 30 minutes a month.
  • The part that breaks: reps marking deals closed-lost. Wins record themselves because they are attached to money. Losses do not, and a pipeline where losses go unrecorded reports a close rate that drifts upward for months.
  • The skill: whoever owns the report has to be willing to say “this cohort is not old enough” to a founder who wants the number today.

The alternative to policing this is removing the ambiguity at the source: if the only thing that enters the pipeline is a qualified, attended conversation booked against fixed criteria, the denominator defines itself. That is the model we run — 50,769+ AI-booked sales appointments since 2017 and 1M+ leads generated, two aggregates that we print separately and that nobody should divide by each other, since they span nine years, different clients and different populations (many of those appointments came from clients’ own databases rather than from leads we generated) — on AI appointment setting priced per booked qualified appointment rather than on a retainer, which only works if both sides agree what counts. This page sits in our pipeline-stage series covering each stage from enquiry to close; the close stage is the one where the definition argument is worth having first, because every downstream forecast inherits it.

Frequently asked questions

What is the formula for sales close rate?

Close rate = deals won ÷ (deals won + deals lost), for a stated population of opportunities, measured after that population has had time to resolve. Salesforce’s reporting documentation uses the same denominator, giving the win rate summary formula as WON:SUM / CLOSED:SUM — won over closed, with open opportunities excluded (Salesforce Help).

Should open deals be included in the close rate denominator?

No. An open deal has no outcome yet, so scoring it as a loss understates the rate and makes the number fall every time you add pipeline. Exclude open opportunities from both the numerator and the denominator, and report the open count alongside the rate so nobody mistakes a young cohort for a finished one.

Is close rate the same as win rate?

In most CRMs they are the same calculation, and Salesforce and HubSpot both label it “win rate”. In practice teams use “close rate” more loosely — often meaning enquiry-to-customer across the whole funnel, which in the worked example above is 6.3% rather than 38.0%. If the two words are being used in the same meeting, make someone state the denominator.

Why did my close rate drop when we increased lead volume?

Almost always because you are dividing this month’s wins by the opportunities created this month — two populations separated by a month or more, because this month’s wins came out of an earlier cohort. With a true close rate of 38% on attended conversations, a six-week sales cycle and opportunity creation growing 25% a month, that method reports 27.2% indefinitely while nothing about the sales team has changed. Divide by this month’s enquiries instead and it reads lower again, about 4.5% against a true 6.3%. The formula only works when the rate and the denominator are measured on the same population; switch to a cohort measurement and the effect disappears.

How long should I wait before measuring a cohort’s close rate?

Twice your median days-to-close. HubSpot defines that property as “the time between Create date and Close date” (HubSpot default deal properties), so pull your own median rather than assuming an industry figure. A 45-day median means a cohort is reportable at about 90 days.

Can a close rate be over 100%?

Only if you are computing it wrongly. Dividing deals closed this period by opportunities created this period will exceed 100% when opportunity creation falls sharply — with a 38% true rate, a six-week lag and creation halving each month, the period method reports 107.5%. An impossible number is the clearest available proof that the denominator is not the population the numerator came from.

Pay-Per-Result appointments

See if we’re a fit

We book qualified sales appointments for you and you pay on results, not retainers. Our booking page asks a few quick questions so you find out in two minutes whether that model suits your business.

  • 50,769+ appointments booked without cold calling.
  • Pay-Per-Result pricing — you pay for booked, qualified calls.
  • Pick your own time on our live calendar, no phone tag.

View all articles

Pay-Per-Result · No retainers

Turn this into booked sales calls.

Our AI agents — trained on 50,769+ booked appointments — fill your calendar with pre-qualified buyers. You only pay when calls land.

Keep reading

Related on Leads Now AI

The thesis behind everything we do

Why Pay-Per-Result is the only marketing pricing model that aligns the agency with you

Leads Now AI is a 100% Pay-Per-Result marketing agency. You only pay when a qualified booked appointment lands on your calendar — priced one of two ways — pay-per-result, at roughly 1–5% of your closed-deal value per appointment, or a revenue share of 10–20% of the sales we help you generate. Both bill on outcomes. Not on clicks. Not on lead-form fills. Not on retainer months. Not on “strategy hours.” If the calendar stays empty, you owe zero. See full pricing →

1. Incentives align

The agency only succeeds when you succeed. We eat the cost of bad ad creative, bad lists, ICP mismatches and no-shows. You never pay for our learning curve.

2. Self-selecting shortlist

Only an agency confident in its delivery can operate this model. The pool of Pay-Per-Result agencies is tiny precisely because most agencies can’t survive on it. Pick from the agencies who can.

3. Cost cannot detach from revenue

Sized to 1–5% of closed-deal value, your acquisition cost stays sustainable across LTV bands. A $500-membership business and a $50,000-engagement business can both run the model profitably.

4. No retainer trap

The standard engagement carries no monthly retainer — nothing arrives on your invoice regardless of outcome. No 6 or 12-month lock-in, no clawback on appointments already delivered, cancel any time with 7 days notice. Early-stage businesses that need the sales systems built first are quoted scoped groundwork up front, never a standing fee.

5. De-risks the pilot

Test before commitment. A small scope-based setup fee covers hard build costs; everything after that is purely outcome-linked. There’s no “we’ll see how it performs after $30k of spend.”

6. Forces agency discipline

If our AI agents qualify poorly, if our reminders fail, if our no-show recovery doesn’t fire — we eat the cost. That’s why the show-rate benchmark sits at 60–75%+.

The volume argument

A fully-ramped human SDR produces on the order of $200,000 a year. They work one conversation at a time, sleep, take leave, and cap out at a territory. Our agents work every lead in the list in parallel — responding in seconds, following up indefinitely without getting bored, and adding capacity without adding headcount.

At 100 qualified booked appointments a month against a $5,000 average deal value, that is $500,000 of booked pipeline every month — roughly what one SDR produces in two and a half years.

Read that precisely: booked pipeline means appointments multiplied by your average deal value. It is not closed revenue — closing is your side of the table, and your close rate decides what lands. The inputs above are a worked example; we size them to your actual deal economics before quoting. What we can evidence on our own numbers: 1,425 qualified appointments in 9 months from our own outbound (3.9% list-to-appointment), 50,769+ appointments delivered since 2017, database reactivation converting 4.4–8.9% on dormant CRM lists, and a 60–75%+ show rate.

The proof: 50,769+ AI-booked sales appointments delivered since 2017 across coaches, consultants, RTOs, course creators, finance brokers and B2B service firms in Australia, USA, UK, Canada, NZ and Europe. Named clients include Sam Tajvidi (121 Brokers), Marcus Wilkinson (Iron Body), Foundr, SheSells.online and Lambda Academy. Wikidata Q139846230. See full Pay-Per-Result pricing →