Estimate the completed-work rate for support conversations using workload-specific operating assumptions. Adjust the inputs to match measured production behavior, then use the primary estimate and supporting metrics to compare deployment choices, identify constraints, and document a repeatable planning baseline. The calculator runs locally in your browser and does not send operational data to a server.
Daily completed work multiplies successful hourly throughput by operating hours.
Successful tasks per hour is the useful completed-work rate. Gross throughput shows raw attempt capacity, and unsuccessful attempts expose the volume that may need retries or human handling.
The formula assumes workers remain available and cycle time is stable. Queues, rate limits, variable generation length, and downstream systems can lower realized throughput.
With 40 concurrent workers, a 6-second cycle, 94% completion, and 24 operating hours:
Define success consistently, such as a completed response that passes validation without a retry or human takeover.
Include them only if their cycle time and concurrency are represented; otherwise keep human capacity in a separate model.
The completion-rate adjustment treats unsuccessful attempts as lost throughput. If retries consume worker time, ensure the measured cycle and success rate reflect them.
Yes. Use the hours during which this capacity is available if the service is scheduled or constrained.
Arrival patterns, batching, token length, rate limits, and dependent services can prevent continuous use of all workers.
| Variable | Meaning |
|---|---|
| Concurrent workers | Simultaneous processing slots |
| Average cycle time | Seconds occupied per attempt |
| Completion rate | Share producing a successful task |
| Operating hours | Daily availability window |