Use the calculator below to estimate how many leads your AI voice agents can handle. Throughput depends on how many calls run in parallel, how long each call lasts, and how often your system triggers the next batch — the tool shows the realistic steady-state limit, not an optimistic best case.
Accurate lead processing forecasts accounting for Batch Frequency.
How often your Vercel function wakes up to trigger the next batch of calls.
Every Minute (Avg)
Per Cron Run (3m)
Every 10 Minutes
Every Hour
Per 8-Hour Shift
Per 24 Hours
Current Bottleneck: Cron Frequency
Your calls are finishing in 1m, but your cron only triggers every 3m. You have 2.0 minutes of idle time where slots are empty. Your maximum throughput is limited to 10 leads every 3 mins.
If calls started immediately as slots opened.
Realistic output based on 3m batching.
It estimates how many leads or calls your AI voice setup can process per minute, hour, shift, and day based on concurrency (parallel calls), average call duration, number of accounts, and how often your batch job wakes up.
Capacity is the lower of two limits: the theoretical throughput (concurrency ÷ average duration × accounts) and the cron-restricted throughput (concurrency × accounts ÷ batch interval). The calculator reports the realistic lower bound so you plan for steady-state volume, not a best case.
A cron bottleneck happens when calls finish faster than your batch job triggers the next round. For example, 1-minute calls with a 3-minute batch interval leave 2 minutes of idle capacity. Reducing the batch interval or switching to a queue-based trigger removes the bottleneck.