The agent payback formula
Monthly saving = employees on the process x salary with payroll taxes x share of their work the agent takes, minus support and model costs. Payback in months = one-time agent price / monthly saving.
Take the salary not as take-home pay but with payroll taxes. In Russia, the single rate of social contributions under Article 425 of the Tax Code is 30% up to the cap and 15.1% above it, so the calculator counts the salary with taxes, and the factor is shown in the caption under the sliders.
If you prefer ROI (return on investment), take the yearly saving, subtract the one-time price, and divide the result by the same one-time price.
For one agent, the one-time price is the pilot: with us, from $1,499 for 14 days. If there are several agents and they work with the same data, count an AI department from $4,999.
What to enter into the calculator
The calculator below is the same as on the home page: three sliders and a choice of format.
1. “Employees on routine work”: how many people work on the process the agent will take. Not the whole department, only those who answer these requests or do these operations.
2. “Salary per person”: the average salary of these employees before taxes. The calculator adds payroll taxes by itself.
3. “Share of work for AI”: the part of the working day the agent will take. The next section explains how to estimate it from your own data.
4. “Format”: “One agent”, “Department”, or “Business”. For one process, choose “One agent”, and the pilot price goes into the calculation. The calculator has already subtracted support of $480 a month.
On the right you will see “Saving per year” net of the one-time price, “Per month”, and “Payback” in months. If payback shows “no”, the saving is less than the support fee.
Payback calculator
How much your AI department saves.
An estimate. Salary with payroll taxes ×1.3. Support at $480 a month is already subtracted.
- Savings per year
- $22,001
- Per month
- $2,250
- Payback
- 3 mo.
How to measure the share of routine before a pilot
The share of routine decides almost everything: with the same headcount and salary, the saving rises and falls with it. You do not guess it; you count it from your own data.
1. Export a month of requests or operations from the CRM, email, or telephony.
2. Label a sample: typical (the answer is in the rules or the price list) and complex (it needs a person, a decision, or an exception).
3. Time how many minutes an employee spends on one typical request.
4. Share = time on typical requests / all working time of these employees. In the first month, assume less than the labeling showed: the agent will not take all the typical work at once.
According to MIT NANDA, 95% of generative AI pilots have no measurable effect on profit. Without a “before” number, you will not know which group your pilot fell into, and a labeled sample becomes both the base of the metric and the test set.
What to subtract from the saving
The calculator subtracts only support. Subtract the rest yourself, or in half a year the report will not match the calculation.
1. Support: with us, from $480 a month. Without it, half a year later the agent answers from an old price list.
2. Model and server: payment for cloud model tokens or rent of a server for an open model. This is the variable part, counted by the number of requests per month; prices are collected on the page about the running costs of an agent.
3. Your people’s time: the process owner reviews disputed answers and updates the knowledge. If there is no such person, the saving shifts by months.
4. The share that stays with people: the agent takes typical work, and complex work stays with employees. A calculation on the full salary gives a number that the report will not confirm.
When an agent will not pay back
According to McKinsey (November 2025), 88% of organizations use AI, and 39% see an effect on EBIT, the company’s operating profit. Using AI and earning from it are not the same: an agent pays back where there is a lot of repetitive work.
1. The routine is less than one employee’s workload: the agent gives quality, such as replies at night and on weekends, not savings.
2. The process is not described: the first weeks go to rules, not to results.
3. The data lives in people’s heads: the price list, stock, and customer history are not collected in a system, and the agent has nothing to read.
4. The saving is less than support: the calculator shows “no”, and that is an honest answer, not a reason to adjust the sliders.
How to check the calculation after launch
The metric from the calculation goes into the pilot contract: what it was, what it should become, and how to measure it. After 14 days, you put the real share of work the agent took into the same formula.
If the number is below the calculation, the reason is usually visible in the log: people do not pass requests to the agent, the knowledge is out of date, or the process has changed. How to track the metric every week is described on the page about launching an agent.
A company-wide impact calculation, when there are many processes and agents, works the same way but takes into account the rollout order and the total budget. The AI roadmap method covers it, and an example for an AI department is in the article about payback.