ITSM procurement often starts with a licence table. The problem is that a licence table rarely shows the full cost of the platform in year three.
Agent growth, additional departments, AI add-ons, storage, integrations, implementation work, infrastructure and renewal terms can all change the economics after the initial purchase. That is why total cost of ownership, or TCO, is a more useful comparison than the first-year quote.
1. Agent and user growth
A platform that starts with one team may later expand to IT, facilities, HR or other ESM processes. Instead of modelling only today's agent count, build a realistic three-year growth scenario.
Check how pricing changes when more agents are added, whether there are licensing thresholds and whether expanding into additional departments requires a different plan.
2. Add-ons and separately priced capabilities
AI, advanced reporting, additional environments, extended integrations or extra storage may be priced separately from the core licence. Treat them as individual TCO lines rather than assuming every advertised capability is included in the base plan.
For example, the local AI module in Mint Service Desk is a paid add-on for On-Premises ticket workflows.
3. Infrastructure and environment operations
Deployment architecture changes where the cost appears. In Cloud, more of the infrastructure cost is included in the service. With On-Premises, the organisation pays for servers, storage, backup, monitoring and administrator time. Managed combines the product with an agreed provider-operated environment.
This does not make one model automatically cheaper. It changes who pays for which part of the operating model.
4. Implementation and ongoing development
Initial configuration may be relatively straightforward, but new workflows, automations, forms and integrations require additional work. Estimate which changes the internal team will handle and which will require vendor or partner support.
If the platform is expected to expand beyond IT, include future ESM implementation work in the three-year model from the start.
5. Integrations need maintenance
The cost of an integration does not end when the connection goes live. APIs, permissions, data structures and business processes change. Critical integrations need ownership and an ongoing maintenance budget.
In the current Mint Service Desk scope, REST API access is available for Managed and On-Premises rather than standard Cloud, so deployment choice can also influence the technical scope of the project.
6. Renewal and scaling rules
Review what happens after the first contract term. Ask how pricing changes when you add agents, exceed storage limits, expand into another department or renew after the initial period.
If introductory pricing applies only in year one, the TCO model should use the expected renewal conditions for later years rather than the entry price alone.
How to model ITSM TCO over three years
A useful model should include at least three scenarios: today's environment, moderate growth and a broader multi-department rollout. For each scenario, calculate:
- licences and agent count,
- paid add-ons and modules,
- storage and infrastructure,
- backup and monitoring,
- implementation and process development,
- integrations and maintenance,
- administrator time,
- renewal and scaling costs.
This turns the price from a single number into a model that reflects how the platform will actually be used.
The cheapest licence is not always the lowest TCO
The cheapest licence in year one is not always the lowest-cost option in year three. A higher entry price can still produce a lower TCO if it includes capabilities that another model requires you to purchase or operate separately.
Before making a buying decision, compare the operating model rather than only the licence table. Current Mint Service Desk options are available on the pricing page, or you can contact the Mint team to discuss a specific deployment scenario.
