Revenue per selling hour measures closed-won revenue against the hours a rep spends in live buyer contact. Calls, demos, negotiations, and onsite meetings count. Pipeline reviews, CRM updates, internal syncs, and travel do not. The metric turns selling time into a dollar rate, which puts every internal process on the same scale as the number the rep is paid to hit.
How to Calculate It
Revenue Per Selling Hour = Closed-Won Revenue in Period / Buyer-Facing Hours in Period
Worked example with hypothetical inputs. A rep closes $600,000 in a quarter. Calendar and call recording data show 320 buyer-facing hours across those 13 weeks, roughly 24 hours per week. Revenue per selling hour is $1,875.
That rate is what a two-hour weekly forecast call actually costs. Twenty-six hours per rep per quarter at $1,875 is $48,750 of foregone selling capacity per rep. The meeting may still be worth it. The point is that the trade is now priced instead of assumed.
Why the Denominator Is the Hard Part
Most teams get the numerator right and the denominator wrong. Revenue is already in the CRM. Buyer-facing hours usually are not.
Build the hour count from systems that observe rather than ask. Calendar events carrying at least one external email domain give you meeting time. Dialer talk time gives you call time. Meeting recorders give you actual duration instead of scheduled duration, which matters because a 60-minute demo that ends in 34 minutes is a different signal entirely. Filter internal events by attendee domain so team standups never inflate the number.
What the Metric Actually Decides
Two decisions get easier once the rate exists.
The first is tooling versus headcount. If a $40,000 annual tool returns four selling hours per rep per week across ten reps, the recovered capacity at $1,875 per hour is worth far more than the license. The break-even is about 21 selling hours a year across the ten reps, roughly two hours per rep. State the threshold and test the tool against it.
The second is where the constraint really sits. A team with high revenue per selling hour and few selling hours has a calendar problem, and more reps will not fix it. A team with many selling hours and a low rate has a targeting or win rate problem, and the fix lives upstream in qualification rather than in activity volume. Sales velocity tells you how fast deals move. This tells you how much each hour of movement is worth.
Where It Misleads
The rate rewards scarcity. A rep who stops prospecting and services three late-stage deals will post an excellent number for one quarter and an empty pipeline for the next. Pair it with pipeline created per rep and with pipeline coverage so the short-term rate cannot hide a long-term hole. Read it quarterly, never weekly. Deal timing swings the numerator far too hard over any shorter window to be worth acting on.
Frequently Asked Questions
How do you calculate revenue per selling hour?
Divide closed-won revenue for the period by the number of buyer-facing hours in the same period. A rep who closes $600,000 in a quarter across 320 buyer-facing hours produces $1,875 per selling hour.
What counts as a selling hour?
Live contact with a buyer. Discovery calls, demos, technical validation sessions, pricing negotiations, and onsite meetings all count. Pipeline review, CRM data entry, internal enablement, proposal formatting, and travel do not.
Where should the hour count come from?
Systems that record time without asking the rep. Calendar events with at least one external attendee, dialer talk time, and meeting recorder duration are all reliable. Self-reported time logs are not, because reps estimate under pressure and round toward whatever the manager rewards.
Can revenue per selling hour be gamed?
Yes, by shrinking the denominator. A rep who books fewer meetings and closes the same revenue posts a higher rate while generating less pipeline for next quarter. Always read the metric alongside total selling hours and pipeline created.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like revenue per selling hour into prescriptive action for your team.
Schedule a Demo