Founders
How to choose a pricing unit for AI customer support agents
AI customer support agents: Choose a pricing unit that the buyer can understand and the team can measure.
Choose a pricing unit that the buyer can understand and the team can measure. Compare how the unit tracks customer value, usage variability, and delivery cost. A familiar seat model may fit one workflow and create confusion in another.
Start with the decision
Write a sample bill under several usage patterns. Ask buyers what they believe they are paying for and what would make a bill surprising. Keep the charging unit distinct from the internal unit used to track cost.
The illustrative scenario
This is an educational workbook. The company or fund and all numerical inputs below are fictional. They are not ADIN results, customer claims, market benchmarks, or a forecast.
The fictional team drafts replies to delivery and refund questions for an online retailer. A support manager owns the queue, while finance controls refund authority. Seasonal peaks change the mix of easy and difficult tickets.
A reply that sounds fluent can still promise the wrong refund. Keep suggested language separate from permission to change an order or issue money.
A monthly cost bridge with visible assumptions
For this exercise, assume 1200 completed units in a month, 7 minutes of human work per unit, and a fictional labor rate of $30 per hour. The labor rate, service cost, and revenue are invented inputs. They are not current vendor prices, customer results, or a suggested commercial offer. A reply that sounds fluent can still promise the wrong refund. Keep suggested language separate from permission to change an order or issue money.
The bridge subtracts only the costs shown. The remainder is not an accounting gross margin or profit figure: other expenses, taxes, timing differences, and classifications are outside this simplified model. A negative result is useful information about the assumptions, rather than evidence that an entire product category cannot work.
Now change one input. If the workflow requires twice the review time, the human-work line doubles even when the provider's unit price stays constant. If volume rises, distinguish a genuinely fixed cost from a cost that will step up. Reconcile the model with observed delivery logs before using it to support a pricing or fundraising claim.
| Item | Illustration |
|---|---|
| Completed workflow units | 1200 |
| Assumed revenue for this month | $1,800.00 |
| Variable service cost | 1200 × $0.08 = $96.00 |
| Listed fixed delivery cost | $250.00 |
| Human work at an assumed $30/hour | $4,200.00 |
| Remainder after these listed costs | -$2,746.00 |
Use this worksheet
Answer the questions with a source, date, owner, and next action. Mark an unknown as unknown. Use public or permissioned information and involve a qualified specialist when a question requires expertise beyond the team’s competence.
- What event is billed?
- Can the buyer predict usage?
- What value does the unit represent?
- What costs vary with it?
- What bill would be unexpected?
Questions specific to this scenario
- Who can approve a refund?
- Which issues require a human handoff?
- Does the test include peak-season complaints?
Use anonymized ticket histories, escalation reasons, reviewer edits, and repeat-contact counts. Record whether a customer issue was actually resolved rather than counting a generated reply as success.
A concrete next test
Choose one ordinary delivery question, one refund exception, and one repeat complaint. Have the support owner trace each from intake to a usable resolution. Record where draft quality, authorization, and customer follow-up require different evidence or different people.
Interpret the result
A pricing unit is useful when it supports a clear commercial conversation. Do not infer willingness to pay from an arithmetic cost model alone; test the proposed value and packaging with the actual buyer.
Compare the draft-and-review workflow with the current queue, including time spent fixing errors and handing cases back to people.
Sources and method
These primary resources provide background for the concepts. The fictional scenario, calculations, and worksheet are ADIN educational examples; the sources do not report or validate those invented results. Reviewed October 11, 2026.