Most teams reach for an ITSM platform at a recognisable moment: the IT service desk has outgrown a shared inbox and a spreadsheet, SLA breaches are creeping in, or an auditor has asked for documented change approvals you can’t produce. The off-the-shelf platforms solve part of that, but they also ask you to run incident, change and asset processes the vendor’s way, and they bill you per agent every month.
I build custom IT service management software around how your service desk operates and what your sector requires, then hand you the code. It connects to the tools you already run, and ByteGears is senior-led, so implementation, training and later changes come from the person who wrote it.
If your processes are standard ITIL, your integrations are light and your agent count is stable, Freshservice or Jira Service Management may be the sensible choice. Custom software earns its place when your workflows, integrations, compliance profile or scale don’t fit the templates.
Where off-the-shelf ITSM platforms fall short
The big platforms are capable. The friction shows up in predictable places:
- Per-agent pricing that punishes growth. Starting with a small IT team feels cheap. Add a second site, then Facilities and HR onto the same tool, and the licence multiplies. Some organisations resort to shared logins, which breaks the audit trail.
- Workflows that don’t bend far enough. Mid-market tools offer drag-and-drop approval chains, but rules like “if the change touches patient data, require a compliance review”, “emergency changes get a 30-minute fast track”, or “respond in one hour for the trading floor, four for everyone else” often fall outside the templates. Enterprise platforms can be customised to fit, but only with consultants and proprietary scripting.
- Integration costs that exceed the licence. The system you most need to connect, a legacy billing system, an ERP, an OT or SCADA estate, is usually the one with no connector, and middleware like Zapier adds latency and a monthly fee per connection.
- A CMDB that’s an afterthought. Lightweight tools track a flat asset list. When an outage hits, you need to know which services depend on which configuration items.
- Vendor lock-in. Proprietary configuration languages and data models mean leaving costs as much as staying. Moving tens of thousands of tickets, custom fields and workflows off a platform is a project in itself.
- Generic compliance. GDPR support is usually there, but FCA change controls, NHS Data Security and Protection Toolkit evidence and freeze-window calendars often need manual workarounds.
The result is exports to Excel, side processes the tool never sees, and a bill that grows faster than the value.
What I build instead
Designed around your process. I map your incident, request and change workflows before writing code: how tickets get triaged, who approves what, how SLAs are defined by service and priority.
The full ITIL set, only the parts you need. Incident, request, problem and change management, plus a CMDB that models dependencies between services and assets. You’re not paying for hundreds of features you’ll never open.
Approval chains that match your hierarchy. A change over a cost threshold needs finance sign-off, a security-classified change goes to a cleared approver, an emergency change takes a fast-track path. The audit trail records which path was taken and why.
You own it. A fixed-price build instead of a per-agent subscription. The code, the database and the data are yours, on standard frameworks and open APIs, so you can host it where you choose and have anyone maintain it later.
It connects to what you’ve got. Sign-on and user sync with Entra ID or Active Directory, email-to-ticket, Teams or Slack, monitoring tools that raise incidents automatically.
Modules I build into ITSM projects
The first release covers the incident and request modules below with a starter set of articles and single sign-on; the rest follows in later phases.
Incident management. Incidents from the portal, by email or from a monitoring alert, triaged and assigned by category and priority, tracked against SLA with escalation when a target is at risk. Each incident links to the affected service, the configuration items involved and any related problem or change.
Self-service request portal. A service catalogue with request templates, conditional fields and approval chains, so routine requests for access, equipment or software don’t land in the agent queue as raw tickets.
Problem management. Spot recurring incident patterns, record root cause, workaround and permanent fix, and link the problem to the change that resolves it.
Change management. Standard, normal and emergency change types, each with its approval workflow, risk level, business justification and rollback plan. A change calendar and freeze windows keep non-emergency changes out of audit periods and financial close.
CMDB and asset management. Hardware, software licences and services as configuration items, with the relationships that matter: which server runs which application, which service depends on which switch. Lifecycle from purchase to disposal, warranty and contract dates, and alerts before a licence or warranty expires. Agents see the full ticket history for any asset.
Knowledge base. Articles and runbooks for agents and staff, linked from incidents, with a prompt to write an article when a ticket is resolved so the library grows from real fixes.
SLA tracking and escalation. SLAs tied to service and priority, or to the business unit and its impact, with escalation on time or on conditions pulled from other systems.
Reporting. Incident volume, mean time to resolve, SLA adherence, change success rate, satisfaction scores and team performance, laid out the way your managers want to read them.
Mobile and field support. A mobile web app that installs on a phone, with offline ticket updates, photo capture and on-site asset lookup for field technicians.
Compliance and audit. Role-based access, a complete audit trail of every change and approval, retention policies, and subject access request and breach-handling support.
How the project runs
- First Gear, five days, £495. I document how incidents, requests and changes flow today, where the workarounds are and what your data looks like, then build a working prototype on your own categories and services. The prototype comes with a one-page plan and a fixed price for the build, with the £495 counted towards it. Migration is where most ITSM rollouts come unstuck, so the plan covers what to bring across: at minimum open and recent tickets, users, knowledge base articles and SLA definitions, with older history and asset records where they earn their place.
- First release, live within a month. Incident management, the request portal, a starter knowledge base, a lightweight asset inventory, basic reporting and single sign-on.
- Go-live. User acceptance testing, role-based training, then a phased rollout, often piloting with one or two teams first, with a rollback plan ready.
- Later phases. Problem management, change management with full approval chains, a deeper CMDB, advanced reporting and the integrations specific to your estate, each about a month and fixed-price. Launch comes with a 30-day fix guarantee and a free first month of hosting, then an optional plan or your own servers.
Four things make or break an ITSM rollout: enough time spent understanding the current process, clarity about historical data quality, SLAs set against what your team can achieve today rather than an aspiration, and resisting the urge to copy every quirk of the old system. The plan deals with all four.
What it costs and what you own
A build needs more money up front than a SaaS subscription. Over a few years the comparison shifts:
- SaaS pricing is per agent, per month, and it compounds. Every new agent, site or service team adds to the renewal. A build is a fixed price, then a flat monthly plan or your own hosting.
- Watch the hidden costs on both sides. SaaS quotes rarely include implementation, custom integration work, data migration, premium support or module add-ons. A build has its own up-front work too: migrating a large ticket backlog can be a real share of the project, which is why it is scoped in First Gear.
- No vendor lock-in. You can change hosting, bring maintenance in-house or hand it to another supplier without paying to escape a proprietary platform.
An ITSM build from me usually costs £2k to £10k, fixed once First Gear is complete. Incident, request and a basic asset register usually fit in one build. A full ITIL set with problem and change management, a proper CMDB and several integrations comes as further fixed-price phases.
Where custom ITSM earns its keep
Financial services. FCA-regulated firms need to prove that critical changes were approved, by whom and when, with segregation of duties enforced rather than assumed. ITSM data can also sync with in-house monitoring or fraud systems that no SaaS connector covers.
Healthcare and NHS. Incident urgency is measured by patient impact, so a clinical system outage escalates differently from a slow printer. Audit trails and access logs are built to support CQC inspections and the NHS Data Security and Protection Toolkit.
Manufacturing and logistics. When IT downtime stops a production line, impact is measured in lost output. A CMDB that maps IT and OT equipment to specific production lines lets incidents escalate on business impact and ties recurring outages back to root cause.
Education. SLAs that respect the academic calendar: a registration system down in enrolment week is critical, the same system down in August is not. Portals serve students and staff separately, IT, facilities and library requests can share one system, and public bodies need the portal to meet the accessibility regulations for public sector websites.
Government and public sector. Security classifications, cleared approvers and UK data residency rarely map onto a commercial platform’s approval model. A custom build enforces the right approval before deployment.
Professional services. Client service requests and SLAs tracked alongside internal IT, with time linked to client projects for billing.
Telecoms. Outage handling that coordinates IT, network operations, customer service and communications, with customer-impact detail standard escalation models don’t capture.
Multi-team service management. Organisations delivering IT, Facilities and HR services on one platform with shared ticketing, approvals and reporting instead of three tools.
If your SLA reporting is for customers of an outsourced service, service level management software is the closer fit. Tell me how your service desk runs today and where it hurts, and I’ll tell you whether a build is worth it.
Common Questions About Custom IT Service Management Platforms
How does a custom ITSM build compare in cost to ServiceNow or Freshservice? ›
SaaS ITSM is priced per agent per month, and the bill climbs every time you add a team, a site, or Facilities and HR onto the same tool. Implementation, integrations beyond the native connectors, premium support and module add-ons often come on top. A custom build is a fixed price set at the end of First Gear, most of mine land between £2k and £10k, and the running cost is a flat monthly plan rather than a per-seat licence.
Is a service desk the same as a help desk? ›
In the UK, "service desk" usually means the IT team supporting your own staff, run on ITIL lines: incidents, service requests, changes and the assets behind them. A help desk usually means support for your customers. This page covers the IT service desk. Customer support ticketing has its own help desk software page.
What's the typical development timeline? ›
First Gear takes five days and gives you a working prototype of your incident and request flow. The first release, covering incident management, a self-service request portal, a starter knowledge base and single sign-on, then goes live within a month. Problem and change management with approval chains, a fuller CMDB and further integrations follow in later phases, each about a month with its own fixed price.
Can you build proper ITIL processes, or just a ticketing tool? ›
The full ITIL set where you need it: incident, request, problem and change management, plus a CMDB that models the relationships between your services and the assets underneath them. In a custom build the approval chains, SLA definitions and asset categories match how your organisation works, rather than a vendor's templates.
Can you integrate with our existing systems? ›
Yes. Common links are Microsoft Entra ID (Azure AD) or on-premises Active Directory for sign-on and user sync, email-to-ticket, Microsoft Teams or Slack for notifications and approvals, monitoring tools such as Datadog or Nagios that open incidents automatically, Jira for development handoff, and finance or ERP systems for asset and contract data. Legacy and unusual systems are part of the design, not an expensive extra.
What about data security and compliance? ›
UK GDPR handling is built in, including subject access requests, retention policies, and anonymising old records instead of deleting them so audit trails stay intact. The asset register and change records can serve as evidence for the ISO 27001 controls on asset inventory and change management. For regulated sectors I structure audit trails, segregation of duties and change freeze windows around FCA, CQC or NHS expectations, with hosting on UK infrastructure.