Sales capacity planning for SDR teams
Forecast what a roster will deliver: bookings-per-hour rates per SDR and client project, manager overrides, and working days net of public holidays.
What this gets you
A per-rep, per-project bookings-per-hour rate that improves as evidence accumulates
Manager overrides layered on top for cases the data has not caught up with
Working-day counts net of public holidays for the relevant country
An arithmetic answer to "can we take this client on in six weeks"
Absences and per-user work-hour overrides already in the model
Can we staff the next client?
Most teams answer by instinct. A proper answer needs three numbers: meetings per hour for each SDR, on each client, and the hours each SDR will actually be available in those weeks. For a quick estimate on your own numbers, try the meetings per hour calculator.
How a capacity forecast is built
- 1
Rate per SDR and client
A Bayesian estimate of meetings per hour that starts near a prior and moves toward observed results.
- 2
Manager override
Stored on top of the computed rate, visible as an override, revertible.
- 3
Available hours
Work hours per user, minus absences and public holidays for the account’s country.
- 4
Capacity vs demand
Rate × hours per week, against confirmed and tentative projects.
Rates that hold up on small samples
Two bookings in a rep’s first three hours is not 0.67 meetings per hour. The Bayesian rate stays conservative until there is enough history: twenty hours on a project gives a rate you can plan against, two hours does not.
When a team lead knows something the data does not yet, such as a rep ramping up or a new list, they set an override. It never overwrites the computed estimate.
Hours that match the calendar
Today
- Weekdays counted as working days, so holiday months look like underperformance
- Vacation and sick days noted in a calendar, not in the forecast
- Part-time SDRs planned as full-timers who keep missing targets
With Dialbrew
- Working days = weekdays minus public holidays, from a cached holiday table
- Absences are records that reduce available hours
- Account work hours with per-user overrides
The holiday rule applies platform-wide to every count of working days, billable days, expected hours and capacity. The country defaults to the account’s setting.
Where the hours actually went
Work-time variance compares expected hours with logged hours, so drift shows while you can act on it. Money per hour relates revenue to hours spent, per SDR and per client project.
The caveat
A forecast is still a forecast. The platform is built towards a six-week horizon within ±15%. That is a design target, not a measured guarantee.