Most sales teams measure reps on activity: calls made, emails sent, hours logged. Those numbers are easy to collect and easy to game. What a manager needs is a number that shows whether the rep is producing. That’s why we use a weekly booked-meeting benchmark: 10 booked meetings a week is good, and 30 is great.
Every new rep commits to about ten calling blocks a week, roughly 30 hours of focused dialing and follow-up. Against that time, 10 booked meetings is one booking for every three hours on the phone. That’s a realistic floor for someone who knows the product and the script. Thirty a week is what a rep reaches when the list is tight, the opener is landing, and follow-up is disciplined. It’s meant to be a stretch.
Why a fixed number instead of a ramp curve? Ramp curves get negotiated. A rep who books four meetings in week one can always argue that week two will be better, and the conversation drifts. A fixed benchmark ends that early. If the target is 10 and a rep is at 2 by the end of week three, something specific is wrong, and you can look at it. Is the list wrong? Is the opener landing? Are they calling in the right windows? Without a fixed number, you’re left asking vague questions like “how’s it going?”
The benchmark also gives reps a clear gate. New reps start on our consumer campaign, where the platform is simple and pay per qualified meeting is lower. They need to book 40 meetings there before moving to the higher-paying B2B campaigns. At 10 a week, that takes about four weeks. At 30 a week, it takes under two. The team record for the gate is five days. That shows the benchmark isn’t theoretical.
Here’s how we read it in practice:
A rep who books 3 meetings in week one isn’t failing. They’re learning the platform, and the gate has no deadline pressure yet. The question is whether they’re on a curve toward 10 by week four. If they book 3 again in week two, that’s a signal to listen to their calls, not a verdict on their future.
A rep who hits 10 with calls that are short and unqualified isn’t on track either. The benchmark counts qualified meetings for a reason. Pay follows qualification, and so should the scorecard.
A rep who regularly hits 30 is doing something worth copying. The useful work is finding out what they do differently in the first 60 seconds of a call and in their follow-up sequence, then writing it down so the next person starts higher.
Support matters during the ramp too. New reps get direct messaging access to the founder during onboarding, so a stuck point on Tuesday doesn’t wait until the Friday review. Short feedback loops matter more than long reports.
If you’re setting this up for your own team, three things make a benchmark work:
- Define “booked” and “qualified” in writing before the first week starts. Vague definitions turn every number into an argument.
- Pick a floor and a stretch. One number tells you whether someone is OK. Two numbers tell you where to coach.
- Review it weekly, on the same day, against the same data. A benchmark you check once a month is just a suggestion.
A single number won’t make a rep good. But it does make it obvious, early, when a rep needs help, and that’s usually the difference between a ramp that works and one that quietly stalls.