Calculator· By the RemediateDesk team · Published October 15, 2026 ·All guides
Run your own numbers
Example values are filled in so you can see how it behaves. Replace every one with your own.
Tickets about a machine's behaviour, not account or licence requests.
The input to measure in a pilot rather than assume.
Approving commands and reading the summary.
Salary plus overhead, not the wage alone.
Cost is the published base for 250 endpoints ($599) plus $2 for each resolved ticket ($90).
For reference, live from our platform: sessions that resolved took a median of 4.7 minutes, measured across 183 resolved sessions. That is the AI's own working time and does not include your review.
How the calculation works
Everything above is arithmetic on figures you enter, and the price comes from the same constants as the pricing page.
- Tickets the AI resolves = endpoint tickets per month × the share it resolves.
- Hours returned = resolved tickets × (minutes a technician would have spent − minutes of review and approval still needed) ÷ 60.
- Value = hours returned × your loaded technician cost per hour.
- Cost = the published base for your endpoint count + a charge for each resolved ticket.
- Net = value − cost. Break-even is the number of resolved tickets at which net reaches zero.
The input that matters most is the one we can't give you
Resolution rate varies enormously between fleets, ticket mixes and how much freedom you grant. A figure from someone else's queue is a guess about yours, so the default is deliberately modest and clearly marked as an example.
The right way to fill it in is a pilot: run on a slice of your own endpoints for a month and read the resolved count, the number that needed a technician to steer, and the number that ended as “insufficient evidence”. Use your measured numbers and the calculator stops being a forecast.
Costs that are easy to forget
- Review time. Approving a command and reading a summary is not free. The review-minutes field exists so the saving is not overstated.
- The tickets it hands back. Those still land on a technician, ideally with the investigation already done, which is worth something but is not a resolved ticket.
- Tickets that come back. A fix that does not last costs twice. Count recurrences from your own PSA during the pilot.