Calculator
What do repetitive tickets actually cost you?
Enter your headcount and salaries. The first set of numbers is your own payroll arithmetic — it does not depend on believing anything about us.
Skip the sliders: request a demo and we read your real ticket history instead.
What repetitive work costs you now
Arithmetic on the figures you entered. No assumption about us.
Annual cost
$110,000
Monthly cost
$9,167
Hours per month
347 hrs
Full-time equivalents
2.0 FTE
What 50% automation would return
A scenario at the rate you set on the left.
Annual saving
$55,000
Hours freed / month
173
FTEs freed
1.0
About that second slider
This calculator asserts no rate of its own. Everything above runs on the numbers you entered and our published prices, so the slider is your assumption and the figure above it is your own payroll — neither depends on believing anything about us.
Up to 72% is an owner-set modeled coverage ceiling, not a measured customer resolution rate. The operating model counts ticket types, not ticket frequency or successful executions. Each launch workflow is scoped and supervised with your team. The public operating model classifies 508 of 600 ticket types as resolution-ready. That classification is not a recommended value for the slider; use your own measured workload and label estimates as assumptions.
Bring your workload assumptions to a demo. Any analysis of real ticket history needs an agreed scope and appropriate access first.
The whitepaper · 10 pages · PDF
Resolution readiness: a denominator for "our AI resolves X% of tickets"
Every vendor claims a resolution rate. This is what a denominator for one looks like.
Questions
How this is calculated
The model is deliberately simple enough to check by hand.
Why do you not just tell me how much you will automate?
The calculator uses your entered workload, cost assumptions and our published prices. Up to 72% is an owner-set modeled coverage ceiling, not a measured customer resolution rate. The operating model counts ticket types, not ticket frequency or successful executions. Each launch workflow is scoped and supervised with your team. The Agentic MSP Operating Model classifies 508 of 600 ticket types as resolution-ready; that classification does not measure how often those tickets occur or are successfully completed in your environment. Review the model at https://mspagentic.ai/the-model/ and measure your own workflow before estimating realized savings.
Where does the hours figure come from?
A 2,080-hour working year per technician — 40 hours across 52 weeks — multiplied by your headcount and the share of time you said goes to repetitive work. Nothing else is assumed.
What counts as a repetitive ticket?
Examples include password resets, account unlocks, access and licence requests, onboarding and offboarding. Classify a representative sample of your own tickets and record the time spent; do not substitute an unsupported industry percentage for your baseline.
Can you run this against our real numbers?
We can discuss your workload and cost assumptions during a demo. Reviewing actual ticket history requires separately agreed access, scope and data handling. A calculator scenario is not measured customer savings.
Want the detail behind the model? See how the agents work or compare it against a plan.
See it against your own ticket history
A demo runs this model on your real queue instead of an estimate.