Lead Follow-Up Capacity Calculator: Can Your Team Keep Up?

A weekly workload plan, with explicit limits

Use this tool for one eligible enquiry pool with comparable task effort and productive time. It is a deterministic batch model. It does not predict first-response time, staffing requirements, queue waiting-time distributions or revenue. No CRM account is required; enter anonymous aggregates only.

A packet contains initial review and handling plus the planned follow-ups. Use tasks belonging to the same weekly boundary. Untouched backlog is counted in equivalent full packets. Partially completed cases, multi-week sequences and different service classes need a separate work estimate or richer model.

Inspect the arithmetic

Packet minutes = first-task minutes + follow-up count × follow-up minutes. Available minutes = people × productive hours each × 60. Weekly whole-packet capacity = floor(available minutes ÷ packet minutes). The calculation uses hundredths of a minute so supported decimal inputs retain an exact capacity boundary.

New-work hours = new leads × packet minutes ÷ 60. Weekly surplus = capacity − new leads. Next-week backlog = max(0, current untouched backlog + new leads − capacity). With positive existing backlog and positive surplus, planned clearance weeks = ceiling(backlog ÷ surplus). If surplus is zero or negative, no finite clearance is available. With no existing backlog, clearance is zero even if new work will create a future backlog.

Zero productive hours is valid and gives zero capacity; workload as a percentage of zero hours is undefined. A zero-minute packet is rejected because it cannot define meaningful capacity. Whole packets complete within each week and partial-packet minutes do not carry forward. This conservative batching choice is not a claim about how a real team must schedule work.

Worked example and stress case

The defaults are synthetic: 120 arrivals, 12 initial minutes, two four-minute follow-ups, two people with 25 hours each, and 60 untouched packets waiting. Packet effort is 20 minutes; available time is 50 hours; new work is 40 hours; capacity is 150 packets; surplus is 30; next backlog is 30; conditional clearance is two weeks.

Reducing productive hours per person to 15 gives 30 team hours and 90 packets of capacity. The next backlog becomes 90. It cannot clear while new arrivals remain at 120 each week. This is a scenario, not an observed failure or a sales forecast.

Export the assumptions with the result

Editing any field clears the previous result. Reset restores synthetic numbers; review the scope note before reusing them. Copy or download the JSON to keep definitions and limitations alongside your plan. A missing required field produces an error rather than being silently treated as zero.

A positive weekly surplus does not prove sufficient coverage at every time of day. Review arrival peaks, actual first handling, case complexity and ownership exceptions. Do not convert this tool's clearance weeks into a customer service promise.

Sources and limitations

Checked October 20, 2026: HubSpot lead management (updated September 25, 2026) distinguishes owner-based workspace visibility. Microsoft assignment rules (page date June 15, 2026) describes record-based capacity and availability. Our time model is an original synthesis, not either product's algorithm. No response-time or sales improvement is promised; examples are synthetic.