Sales Velocity
"Sales Velocity is the revenue a pipeline produces per day, calculated from the number of opportunities, average deal value, win rate and sales cycle length."
What is a Sales Velocity?
Sales Velocity is the revenue a pipeline produces per day, calculated from the number of opportunities, average deal value, win rate and sales cycle length. Related product: Chat Agents.
Reviewed by Jaffar Jawed, Co-Founder · Last reviewed
Deep Dive
Sales velocity is the formula sales leaders use to see whether the pipeline is getting faster or just bigger. It multiplies the number of qualified opportunities, the average deal value and the win rate, and divides by the length of the sales cycle in days. The result is revenue per day. Voice and chat agents touch three of the four inputs: they add opportunities by answering leads that would have gone unanswered, they shorten the cycle by removing the wait at the start, and they can lift win rate by handing reps a qualified prospect with context.
How it works. Pull the four inputs from the CRM for a fixed window, usually a quarter. Opportunities are deals that passed the sales-qualified stage. Deal value is the average closed-won amount. Win rate is closed-won divided by closed total. Cycle length is the average days from opportunity creation to close. Multiply the first three, divide by the fourth. Track it monthly and, more usefully, split it by source channel and by whether the first contact was handled by an agent or a person, so the effect of automation shows up in the inputs rather than being argued about.
Why it matters for sales leaders. Most pipeline reviews look at opportunity count, which rewards stuffing the pipeline with weak deals. Velocity punishes that, because weak deals lower win rate and lengthen the cycle. It also exposes the cost of slow first contact: a deal that sat three days before the first call carries those days in its cycle length for the rest of its life.
Example. A commercial cleaning company has 40 opportunities a quarter, an average contract of $9,000, a win rate of one in four and a 45-day cycle: 40 × 9,000 × 0.25 ÷ 45 is $2,000 of pipeline revenue per day. It adds a chat agent to its website and a voice agent to its inquiry line. Over the next quarter opportunities rise to 52, because evening and weekend inquiries now get answered and qualified, and the cycle shortens to 38 days, because the first meeting is booked in the first conversation instead of after a callback. Win rate and deal value are unchanged. Velocity becomes 52 × 9,000 × 0.25 ÷ 38, about $3,079 per day, and the company can attribute the change to specific inputs.
Sales velocity vs lead response time. LRT measures the wait before the first reply on a single lead. Sales velocity measures the output of the whole pipeline. LRT is a leading indicator that moves within days of a change; velocity is a lagging one that needs a full cycle to show it. Use LRT to tune the agent and velocity to justify it.
What to measure. The four inputs separately, by channel and by first-touch handler; the share of opportunities created outside business hours; days from first contact to first meeting; and velocity for agent-first versus rep-first deals over the same window. A velocity gain driven only by opportunity count, with win rate falling, means the qualification criteria need tightening.
Botcadence chat agents and voice agents create and qualify opportunities at any hour and sync them to the CRM with the transcript, which is where the cycle-length and source data for this calculation come from; see the sales chatbot use case.
Related Technology
See Sales Velocity in a Botcadence agent
Start on the Free plan and configure an agent that uses Sales Velocity on your own website chat or WhatsApp number. No card needed.
Get Started FreeWebsite chat live in about 5 minutes
Common Questions
Sales Velocity FAQs
Opportunity count and cycle length. Unanswered after-hours leads become opportunities, and booking the first meeting in the first conversation removes the days a deal would have spent waiting for a callback.
Monthly for the trend and quarterly for decisions, because the cycle-length input needs enough closed deals to be stable. Smaller teams should use a rolling 90-day window.
Yes, within a short window, if the cycle shortens but fewer deals have closed yet. Read it alongside closed-won revenue over the same period, never alone.
Tag them by first-touch handler and report both views. The combined number is the pipeline; the split shows whether agent-sourced deals win at the same rate as rep-sourced ones.