How to
Build quota from capacity, ramp and your own historical productivity per rep, then compare it to the top down number. The gap between them is the conversation, and pretending it does not exist is how a year gets missed in month two.
Take productive reps, adjust for ramp on anybody new, multiply by what a tenured rep has actually delivered historically, and apply an attainment assumption below 100%.
That is what the team can plausibly produce. It is usually lower than the board number.
A top down number divided by headcount produces a quota nobody believes, and a quota nobody believes stops functioning as a target within a quarter.
Show both numbers and name the difference. That is a resourcing conversation, not a quota conversation.
A rep hired in month two is not a full rep this year. Most plans assume they are, and most misses trace back to that assumption.
Quota without a coverage plan is a number with no route to it. Divide by your actual win rate to get required pipeline, and check whether anybody has a plan to create it.
Questions
Multiply productive reps by historical productivity per tenured rep, adjust for ramp, and apply an attainment assumption below 100%. Then compare to the top down number and discuss the gap openly.
Plans that assume every rep hits fully are planning to miss. Model attainment below 100% and check that required pipeline coverage actually exists.
It arrives in Slack
Every morning, each rep gets one message naming the deals on their own book that moved overnight, biggest mover first, with the reason beside each number and the deals that have gone quiet underneath.
$99 a month, cancel any time.. Everyone on the team. No per seat charge. Connect a CRM and it runs. No implementation fee. 14 day trial. No card.
Related reading
Pipeline coverage is open pipeline divided by quota. The standard 3x rule is a guess, and your own win rate gives you a better number.
Win rate benchmarks are mostly useless because everybody counts differently. What to measure instead, and the three ways the number gets inflated.
One is arithmetic, the other is a promise. Teams that conflate them get surprised twice.
Conversation intelligence has a well known adoption curve: heavy use for a quarter, then managers only. What causes it and what to do.
Reviewed September 20, 2026 against the product as it behaves today.