Chatbot Break-Even Calculator: Model Time Value and Costs

What the break-even calculation measures

This calculator asks whether the value you assign to released staff time covers software and setup costs. It does not assume the chatbot creates sales, replaces a person or avoids every conversation. Your coverage input should describe enquiries that are successfully handled without the manual task, after checking answer quality. An answer followed by the same manual work has not released that time.

Use loaded hourly cost consistently. If setup cost already includes a person’s implementation time, do not add the same hours again as monthly upkeep. Include vendor usage charges in the software input. If costs rise with volume or a new pricing tier, recalculate each scenario with its actual cost; the fixed-cost break-even expression does not model a changing tariff.

Formulas and units

Covered enquiries per month

Eligible monthly enquiries × covered share ÷ 100.

Net hours released per month

Covered enquiries × (manual minutes − review minutes) ÷ 60 − monthly upkeep hours.

Net modeled monthly value

Net hours × loaded hourly cost − monthly software cost − (setup cost ÷ setup months).

Break-even eligible enquiries per month

Round up: [software cost + setup cost ÷ setup months + upkeep hours × hourly cost] ÷ [hourly cost × (manual minutes − review minutes) ÷ 60 × covered share ÷ 100].

With a positive fixed cost burden, a zero or negative denominator means extra volume cannot pay that burden back. When the fixed burden and marginal time value are both zero, the model is already balanced at zero enquiries. Zero volume can still incur software, setup and upkeep costs. Hours display to one decimal place and money to whole currency units to avoid suggesting the assumptions are more precise than they are.

Worked example: 200 eligible enquiries

Assume 200 eligible enquiries per month, six manual minutes each, 50% successful coverage, one review minute per covered enquiry and one upkeep hour per month. That covers 100 enquiries and releases 100 × (6 − 1) ÷ 60 − 1 = 7.3 hours. At 30 currency units per hour, the modeled time value is 220. With software costing 50 per month and no setup cost, net modeled value is 170 per month.

Break-even occurs at 64 eligible monthly enquiries under those same assumptions. At 30% coverage, net modeled value drops to 70; at 70%, it rises to 270. These are arithmetic scenarios, not observed results or HostDesk prices. Releasing 7.3 hours is useful only if the business can use that time; it does not automatically remove 220 from payroll.

Collect evidence before committing

1. Time a representative sample of current enquiries. Separate active staff work from waiting.
2. Use a small pilot to measure successful coverage and review effort. Check failures and difficult policy questions, not only routine FAQs.
3. Run a conservative coverage scenario and include maintenance. A positive result that disappears after modest changes needs better evidence.
4. Check the website enquiry workload calculator next: a positive monthly business case does not prove the team can cover a peak day.

For a repeatable baseline, use the pilot measurement plan. If you are comparing providers, use the vendor evaluation scorecard to test claims with the same inputs and acceptance cases.