Buyer guide · Return · 9 min guide

Count contribution and capacity separately — and plan for the downside.

Estimate return from two sources kept apart: extra completed bookings or orders, valued at their contribution (revenue minus the variable cost of delivering them), and staff time freed, which only becomes cash if hours or hiring actually change. Spread setup over a realistic period, compare against the full monthly cost, and test a downside case before deciding. Cost per completed booking is the monthly cost of the workflow divided by the bookings or orders it helped complete.

Reviewed by: HumAI delivery teamLast reviewed:

01

Inputs you need

Use your own records for a recent, normal month. Rough numbers are fine if you note where they came from.

  • Monthly requests by channel
  • Share that become completed bookings or orders
  • Contribution per completed booking or order
  • Staff minutes spent per request today
  • Monthly operation and usage cost
  • One-off setup cost and the period to spread it over
02

Use contribution, not revenue

A completed booking worth a certain amount in revenue does not add that amount to profit. Subtract the variable cost of delivering it — materials, commissions, delivery, payment fees — and use what remains. If extra bookings need extra staff, include that too.

03

Treat setup separately

Spread one-off setup over the period you expect the workflow to run unchanged, often twelve months, and add it to the monthly cost. Also report the payback period on its own so the setup decision is visible.

04

Hypothetical worked example

Hypothetical: every number below is invented in generic currency units to show the maths. They are not HumAI prices or results. A business receives 600 requests a month and completes 50% of them (300). After launch it completes 55% (330): 30 extra bookings at a contribution of 40 units each is 1,200 units. Monthly operation and usage cost 700 units; setup of 3,600 units spread over 12 months adds 300, so the monthly cost is 1,000 units.

  • Hypothetical net: 1,200 − 1,000 = 200 units per month
  • Hypothetical break-even: 1,000 ÷ 40 = 25 extra bookings
  • Hypothetical cost per completed booking: 1,000 ÷ 330 ≈ 3 units
  • Downside (52% completion, 12 extra bookings): 480 − 1,000 = −520 units
05

Capacity freed is not cash saved

In the same hypothetical, saving four minutes on each of 600 requests frees 40 staff hours a month. That is valuable capacity — faster replies, more follow-up, less overtime — but it only becomes a cash saving if rotas, overtime or hiring plans actually change. Report it separately from contribution.

06

Check the result after launch

Agree the measures before launch and review them monthly against the baseline. If the downside case is what happens, change the scope or stop; a decision based on evidence is the point of the calculation.

Illustrative calculator

Try the maths with your own numbers.

The starting values are the hypothetical example above, in generic currency units. They are not HumAI prices or results. Replace them with your own records and the figures from your proposal. Nothing you type leaves this page.

Extra completed bookings per month
30
Contribution from extra bookings
1,200
Monthly cost including spread setup
1,000
Net per month
200
Extra bookings needed to break even
25
Cost per completed booking
3

Staff hours freed per month

40

Capacity, not cash: this only becomes a saving if rotas, overtime or hiring actually change. Keep it apart from the net figure.

A sound ROI estimate

  1. 01Uses contribution, not revenue
  2. 02Spreads setup and shows payback
  3. 03Includes a downside case
  4. 04Keeps capacity freed apart from cash saved
  5. 05Shows cost per completed booking
  6. 06Is checked against real results monthly

Sources and further reading

Read next

All guides