The Reality of SaaS ITSM Costs
Before exploring how to optimise your infrastructure, it is vital to understand what commercial ITSM platforms truly cost. Current market data reveals that pricing has successfully drifted away from the actual value delivered.
Enterprise-Grade Pricing for Mid-Market Challenges
ServiceNow, a major force in the industry, prices its core ITSM product at approximately £70–£100 per user per month for standard licences. By 2025–26, richer bundles are reaching £100–£150. If you have a 50-person IT team with 20 active fulfillers, your baseline cost could reach £21,000–£43,200 annually — before implementation or tailored customisation is even considered.
Jira Service Management, often seen as an accessible alternative, prices its Premium tier at £47–£55 per agent. Their Enterprise tier is custom-priced, with estimates suggesting costs exceeding £120,000 per year for larger deployments. Freshservice, frequently positioned as cost-effective, uses tiered pricing where advanced features — like AI assistance and deep automation — are reserved for higher tiers, raising total spend by 30–50% above the headline price.
The Renewal Escalation
The initial contract is rarely the main challenge. The real test comes at renewal. Contract price increases typically range from 5–20% annually. Analysis for 2026 suggests a likely range of 8–12%, with some aggressive cases reaching 25%.
Model a three-year scenario with a modest 10% annual uplift on a £20,000 baseline: costs grow from £20,000 in Year 1 to £24,200 in Year 3. Your total three-year spend reaches £66,200 for a platform you do not own — and that figure does not include implementation costs, which can range from £25,000 to over £2,000,000 depending on scale.
The Feature Utilisation Gap
Perhaps the most ineffective aspect of SaaS pricing is paying for features you never use. Research shows that companies use only about 49% of their provisioned SaaS licences, with 30–50% of licences going entirely unused. For ITSM, this means you are likely paying a premium for advanced modules — change management dashboards, AI routing — that your team has never activated. You are renting capabilities that remain idle while your subscription costs increase every year.
Understanding Lock-In Architecture
The SaaS model is often designed to make leaving more expensive the longer you stay. Understanding these mechanics is essential to making better long-term decisions.
The Data Export Challenge
Major platforms often impose default export limits — such as 10,000 records at a time. For an organisation with years of incident history and knowledge base articles, retrieving your complete dataset is not a simple task. It requires custom scripting and significant manual effort. This is not a technical oversight. It is an architectural choice that increases your departure costs.
The EU has recognised SaaS lock-in as a systemic issue. The EU Data Act now legally requires cloud providers to remove technical and contractual obstacles to switching services. This legislation ensures data can be transferred in a commonly used format — a clear signal that SaaS lock-in is a serious regulatory concern, not merely a commercial inconvenience.
The Configuration Trap
Beyond data, the deeper challenge lies in your workflows. Every custom automation and SLA definition you create is stored in a proprietary language and schema. Moving to a new platform means rebuilding your logic from the ground up. This creates a fragile architecture that locks you into a specific vendor's roadmap. Assessing alternatives becomes expensive not because they are inferior, but because of the effort required to recreate your existing setup.
The Renewal Leverage
Because vendors understand the high cost of your departure, they hold significant leverage during renewals. Switching costs — including retraining, re-implementation, and migration — can range from £33,000 for small environments to over £130,000 for mid-sized ones. When your cost to leave is that high, a 15% price increase can feel, unfortunately, reasonable.
You are paying for the privilege of staying.
The Compliance Dimension and Regulatory Standards
While the financial costs are high, the regulatory risks of inadequate ITSM infrastructure are even more significant. For regulated UK sectors — finance, law, and healthcare — your ITSM platform must generate genuine audit evidence.
Software Audit Exposure
The link between IT Asset Management maturity and audit liability is direct. In 2025, reports showed that 62% of organisations were audited by software vendors. The consequences are serious, with many organisations facing financial liabilities exceeding £1 million.
Most failures stem from "licence-creep" — installing software on more devices than you have licensed because you lack an accurate detection method. ISO 19770-1:2017 provides a process framework to prevent this, but many organisations still operate at maturity levels that will not withstand a professional audit.
Rising UK Regulatory Standards
Information Security Governance
Enforcement focus has shifted toward larger fines for security failures and data losses, often linked to poor system visibility and weak configuration management.
Technology Security as Core Duty
New guidance explicitly states that firm size or budget constraints are no longer valid excuses for non-compliance. Current technology security measures are now a core regulatory duty.
Operational Resilience Mapping
Operational resilience rules require organisations to map the technology and third parties supporting their business services, and to identify and manage vulnerabilities within interdependent systems.
Beyond Spreadsheets
When audits fail, it is rarely due to a lack of intent. It is because the infrastructure to provide evidence — immutable audit logs, asset registers — simply was not there.
A Better Way — Building Your ITSM Infrastructure
Building your own system is not just about saving money. It is about operational independence and regulatory security. UNUS London has constructed a system that proves this is achievable — and has documented every component.
Your Tech Stack: Open and Owned
Compliance by Design — Not by Label
The UNUS London ITSM system does not apply compliance as a label. It enforces compliance at the database layer, meaning the standards cannot be circumvented by user behaviour, configuration drift, or system updates.
Software Asset Management — ISO/IEC 19770-1
The Software Asset Management module maintains a software catalogue (sw_catalog) and licence entitlement registry (sw_license_entitlements) that calculates the Effective Licence Position in real time. The formula is deliberately simple:
When ELP < 0 → Over-deployment detected → Automatic non-compliance flag triggered.
Monthly ELP snapshots retained in compliance_snapshots table → Immutable audit trail.
Hardware Asset Lifecycle — ITIL 4
ITIL 4 lifecycle management is implemented through hardware asset tracking with enforced status transitions. Assets must pass through defined states:
No ad-hoc status changes permitted. No undocumented disposals. Every transition is timestamped and logged with full chain of custody.
Unit Notation — IEC 80000-13:2008
All memory and storage capacity fields use correct SI binary notation — GiB (gibibyte), not GB — with COMMENT ON COLUMN metadata referencing IEC 80000-13 to document unit conventions at the schema level. This ensures that every data field in the system is unambiguously defined against a published international standard.
Access Control & Audit Logging — ISO/IEC 27001:2022
ISO/IEC 27001:2022 controls are implemented through Row Level Security (RLS) policies enforcing persona-based permissions, immutable audit triggers blocking UPDATE and DELETE on audit log tables, and query logging aligned to ISO/IEC 27001 §A.12.4.
Knowledge Management — ISO 9001:2015
ISO 9001:2015 alignment is implemented through the Knowledge Base module with AI-assisted classification, mandatory human approval gates (is_approved = TRUE required for publication), and full document lifecycle tracking. Quality cannot be bypassed — it is enforced by the schema.
What the System Actually Does — The Operational Picture
The ITSM system demonstrated in the UNUS London video comprises the following operational capabilities, each enforcing standards as a natural output of normal operations rather than as an audit exercise performed retrospectively.
Ticketing & SLA Management
ITIL 4-aligned ticketing with automated routing, SLA tracking, escalation triggers, and knowledge retrieval. Every support interaction is logged, resolved, and closed within the database with a complete chain of custody.
AI-Assisted Document Lifecycle
AI-assisted document ingestion and classification using Mistral and Google Gemini, with mandatory manager approval before publication. ISO/IEC 27001-aligned access control ensures only authorised roles can publish knowledge assets.
Live Device Register
Live device register with SCCM integration for automated asset discovery and normalisation. Full ITIL lifecycle tracking. IEC 80000-13-compliant capacity notation throughout.
Real-Time ELP Calculation
Real-time Effective Licence Position calculation, automated compliance flags, monthly snapshot archiving, and SCCM-sourced deployment data. ISO/IEC 19770-1 aligned at schema level.
Continual Improvement Practice
Automated status checks across the entire IT estate, feeding into a compliance dashboard. Continual Improvement per ITIL 4 Clause 7.6 — not as a policy statement but as a live, automated system.
CAB-Gated Change Records
CAB approval gates, timestamped change records, rollback documentation, and immutable status trails that satisfy SOC 2 Type II Change Management controls as a natural output of normal operations.
Real-time visibility across all modules from a single PostgreSQL source of truth, producing governance intelligence rather than simply operational metrics. This is the difference between a tool that tells you what happened and a system that proves you were compliant when it did.
A Structured Cost Comparison
The following figures illustrate the potential savings for a typical UK organisation with a 10–20 person IT team over a three-year horizon.
| Cost Component | Commercial SaaS ITSM | UNUS London Build |
|---|---|---|
| Year 1 Licence | £15,000–£27,000 | £0 |
| Implementation | £20,000–£150,000 | Internal time only |
| Year 3 Licence (with increases) | £18,150–£32,670 | £0 |
| 3-Year Total Infrastructure | Included in licence | £2,700–£4,500 |
| Code Ownership | Never | Day 1 |
| Data Portability | Restricted by design | Complete |
| Compliance Enforcement | Configurable (bypassable) | Schema-level (immutable) |
The UNUS London Model — Build Once, Own Forever
At UNUS London, we do not just offer advice. We help you build tailored compliance infrastructure. We transfer complete ownership to you on Day 1. There is no ongoing dependency on us.
You can also access our full ITSM system through the UNUS London Governance Academy. We provide thorough build guides, SQL scripts, and n8n workflow files that you can import directly into your own instance. We have designed this for CTOs and IT Directors who need to optimise their compliance infrastructure without an enterprise-grade budget.
The SaaS trap is real, but so is the way out. You do not need a massive subscription to achieve enterprise-grade service management. The UNUS London ITSM system delivers high standards of alignment with a tech stack you own completely — and the architecture proves compliance cannot be bypassed, not even by your own team.
It is "Can we afford another audit without it?"
Watch the ITSM System in Action
The full demonstration of the UNUS London ITSM build — PostgreSQL schema walkthrough, n8n workflow, compliance views, and live ELP calculation — is now live on the UNUS London YouTube channel.
Watch the Demonstration Join the Governance AcademySources & Citations
- Block64 (2025). The Software Audit Surge: Why 62% of Companies Faced Vendor Audits in 2024. block64.com
- BSA / Pinsent Masons. BSA wins £18 million in software piracy fines. pinsentmasons.com
- CloudNuro (2025). The Hidden Costs of ITSM: What Vendors Won't Tell You. cloudnuro.ai
- Flamingo (2025). The Vendor Lock-In Trap: Why Your MSP Renewal Just Got More Expensive. flamingo.run
- Getmonetizely (2024). ServiceNow vs Jira Service Management: Complete ITSM Pricing & Feature Comparison.
- ICO Enforcement Analysis (2024–2025). ico.org.uk
- IDC MarketScape: Worldwide IT Service Management Software 2024 Vendor Assessment.
- ISO/IEC 19770-1:2017. Software asset management — Part 1: IT asset management systems.
- IEC 80000-13:2008. Quantities and units — Part 13: Information science and technology.
- ISO/IEC 27001:2022. Information security, cybersecurity and privacy protection — ISMS requirements.
- ITSM.tools. ITIL 4 Adoption Levels. itsm.tools
- Ivanti (2024). IT Asset Management Survey of 1,600 IT professionals.
- Licenseware (2025). Software Price Increases 2025–2026.
- Najar.ai (2025). SaaS Vendor Lock-In: How to Mitigate Risk and Ensure Flexibility.
- Perspectium (2025). How to Increase ServiceNow Export Limit. perspectium.com
- SolarWinds. The True Cost of ITSM: On-Prem vs SaaS.
- URM Consulting (2025). Analysis of Enforcement Action by the ICO in 2025. urmconsulting.com
- UK Government Cyber Security Breaches Survey 2024. gov.uk
- ATS Connection (2026). SRA IT Requirements for Solicitors. atsconnection.co.uk
- EU Data Act (Regulation (EU) 2023/2854), Chapter VI.
- SaaS Management Index 2024. dailyhostnews.com