Most teams reach for an ITSM platform at a recognisable moment: the help 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 your incident, change and asset processes the way the vendor designed them, and they bill you per agent every month for the privilege.
ByteGears works the other way round. We build custom IT service management software around how your service desk actually operates and what your sector actually requires, then hand you the code. It’s developed in the UK, it connects to the tools you already run, and your support comes from people you can reach in your own working hours rather than a ticket queue in another timezone.
To be straight about it: if your processes are standard ITIL, your integration needs are light and your agent count is stable, a mid-market SaaS platform like Freshservice 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 tends to show up in predictable places:
- Per-agent pricing that punishes growth. Starting with 50 agents feels cheap. Add a second site, then Facilities and HR onto the same tool, and the annual licence can quadruple. ServiceNow and BMC Helix sit around the £80 to £130 per agent per month mark; the cost grows with headcount, not with the value you get.
- Workflows that don’t bend far enough. Mid-market tools offer drag-and-drop approval chains, but conditional logic like “if the change touches patient data, require a compliance review” or “emergency changes get a 30-minute fast track” often falls outside the templates. Enterprise platforms can be customised to fit, but only with consultants and proprietary scripting.
- Integration costs that exceed the licence. Native connector counts look impressive, but the system you most need to connect, a legacy billing mainframe, an ERP, an OT or SCADA estate, is usually the one with no connector. Custom integration work on a SaaS platform routinely runs into five or six figures.
- 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, and many platforms can’t tell you cleanly.
- Vendor lock-in. Proprietary configuration languages, vendor-specific data models and bespoke integrations mean leaving costs as much as staying. Organisations stay on a platform they’ve outgrown because the switch is priced like a new project.
- Generic compliance. GDPR support is usually present, but FCA change controls, NHS Data Security and Protection Toolkit evidence, and freeze-window calendars often need manual workarounds.
The result is a pile of exports to Excel, side processes the tool never sees, and a bill that’s convenient on day one and uncomfortable by year three.
What ByteGears builds instead
We’re a small UK shop, and we build ITSM platforms around the processes a real service desk runs every day.
Designed around your process
We map your incident, request and change workflows before anyone writes code: how tickets get triaged, who approves what, how SLAs are defined by service and priority. The software supports that, rather than reshaping it.
The full ITIL set, only the parts you need
Incident, request, problem and change management, plus a CMDB that models the dependencies between your services and the assets underneath them. You’re not paying for hundreds of features you’ll never open.
Approval chains that match your hierarchy
Conditional routing built for your organisation: a change over a cost threshold requires a 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-cost build instead of a per-agent subscription. The code, the database and the data are yours, on standard frameworks and open APIs, so nothing locks you in.
It connects to what you’ve got
Active Directory or Azure AD for SSO, email-to-ticket, Teams or Slack for notifications and approvals, monitoring tools that raise incidents automatically. API-first design means legacy and unusual systems are part of the plan, not an expensive surprise.
Built for UK compliance
Developed in the UK, with GDPR handling, audit trails, retention policies and segregation of duties built into the architecture, and aligned with FCA, CQC, NHS or ISO 27001 expectations where your sector demands it.
Support from people you can reach
Implementation, training and day-to-day questions handled by the UK team that wrote the code, in your working hours.
Modules we build into ITSM projects
A build can include any of the following. The MVP usually covers incident management, the request portal, a starter knowledge base and SSO; the rest follows in a second phase.
Incident management
Create incidents from the portal or by email, triage and assign by category and priority, track against SLA with escalation when a target is at risk. Incidents link 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 like access and equipment 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 for good.
Change management
Standard, normal and emergency change types with the approval workflow, risk level, business justification and rollback plan for each. A change calendar and freeze windows keep non-emergency changes out of audit periods and financial close.
CMDB and asset management
Track 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 procurement to retirement, plus warranty and contract dates.
Knowledge base
Searchable articles and runbooks for agents and end users, linked from incidents so the same question stops coming back.
SLA tracking and escalation
SLA definitions tied to service and priority, with automatic escalation when response or resolution time is at risk.
Reporting and dashboards
Incident volume, MTTR, SLA adherence, change success rate and team performance, laid out the way your managers and executives want to read them, without exporting to a spreadsheet first.
Mobile and field support
A mobile-responsive interface, or a native app where field technicians need offline ticket updates, photo capture and on-site asset lookup.
Integrations
SSO via Active Directory or Azure AD, email-to-ticket, Teams and Slack, monitoring tools that open incidents on a threshold breach, and finance or ERP systems for asset and contract data.
Compliance and audit
Role-based access control, a complete audit trail of every change and approval, configurable retention policies, and DSAR and breach-handling support built in.
How we deliver the project
We build in phases so you have a working system early and can steer the rest.
1. Discovery and architecture (weeks 0 to 2)
We document how incidents, requests and changes flow today, where the workarounds are, and what the data looks like. We also do an honest assessment of the legacy data you want to bring across, because migration is where most ITSM rollouts come unstuck.
2. MVP development (weeks 2 to 10)
Core incident management, the self-service request portal, a starter knowledge base of around 50 to 100 articles, a lightweight asset inventory, basic reporting and SSO. Regular check-ins so you see progress.
3. Go-live with the MVP (weeks 10 to 12)
User acceptance testing, role-based training, then a phased rollout, often piloting with one or two teams before everyone moves. A rollback plan is in place in case anything needs it.
4. Phase 2 (weeks 12 to 20)
Problem management, change management with full approval chains, a deeper CMDB with service dependencies, advanced reporting and the integrations specific to your estate.
Most builds run 12 to 20 weeks end to end. We’ve found a few things make or break an ITSM rollout: enough time spent in discovery, honesty about historical data quality, setting SLAs against what your team can actually achieve today rather than an aspiration, and resisting the urge to replicate every quirk of the old system. We plan around all four.
What it costs and what you own
A custom build needs more money up front than a SaaS subscription. Over a few years the comparison usually shifts:
- SaaS pricing is per agent, per month, and it compounds. Every new agent, site or service team adds to the renewal. A custom build is a fixed development cost, then a predictable annual support figure, typically a percentage of the build rather than a per-seat charge.
- Watch the hidden costs on both sides. SaaS quotes rarely include implementation, custom integration work, data migration, premium support or module add-ons. Together those can match or exceed the licence. A custom build has its own up-front costs, and migrating a large incident backlog can be a meaningful share of the project, which is why we scope it honestly at the start.
- No vendor lock-in. Because you own the code and the data on standard frameworks, you can change hosting, bring maintenance in-house or hand it to another supplier without paying to escape a proprietary platform.
- A longer useful life. A well-maintained custom platform should serve you for five to seven years, often longer, without the migration project that comes with outgrowing a mid-tier SaaS tool.
As a rough guide, a focused MVP covering incident, request and a basic CMDB is a smaller engagement; a full ITIL build with problem and change management, a proper CMDB and several integrations is larger; and deep compliance, automation and legacy integration work sits higher again. We give you a clear figure during a free consultation, scoped to the modules and integrations you actually need. For organisations with steady or growing agent counts, the crossover against SaaS usually lands somewhere in the two-to-three-year range.
Where custom ITSM earns its keep
Bespoke ITSM tends to pay off where the workflow, the compliance burden or the integration landscape doesn’t fit a template:
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. Custom audit trails and change controls are structured for regulator inquiries, and ITSM data can sync with proprietary monitoring or fraud systems that no SaaS connector covers.
Healthcare and NHS
Incident urgency in healthcare is measured by patient impact, not generic IT severity, so an EMR outage escalates differently from a slow printer. Custom workflows align with clinical urgency, and audit trails and access logs are built to evidence CQC inspections and the NHS Data Security and Protection Toolkit.
Manufacturing and logistics
When IT downtime stops a production line, impact is best measured in lost output, not ticket priority. A CMDB that maps IT assets, including OT and SCADA equipment, to specific production lines lets incidents escalate on real business impact and ties recurring outages back to root cause.
Education
Universities and schools need SLAs that respect the academic calendar: a registration system down during enrolment week is critical, the same system down in summer is not. Custom prioritisation handles that; generic ITSM does not.
Government and public sector
Security classifications, cleared approvers and UK data residency requirements rarely map onto a commercial platform’s approval model. A custom build enforces the right approval before deployment and can be hosted on UK sovereign infrastructure.
Professional services
Legal, accounting and consulting firms tracking client service requests and SLAs alongside internal IT, often on a single platform.
Telecoms
Outage handling that coordinates IT, network operations, customer service and communications, with customer-impact granularity that standard ITSM escalation models don’t capture.
Multi-team service management
Organisations that deliver IT, Facilities and HR services and would rather run one platform with shared ticketing, approvals and reporting than juggle three tools.
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 or a site. A custom build is a fixed cost up front, then a predictable annual support figure rather than a per-seat licence. For organisations with steady or growing agent counts, the maths usually crosses over within two to three years. The bigger saving is often hidden costs: SaaS implementation, custom integrations beyond the native connectors, premium support tiers and module add-ons can together exceed the licence itself. We give you a clear figure during a free consultation based on the modules and integrations you actually need.
What's the typical development timeline?
A working MVP covering incident management, a self-service request portal, a starter knowledge base and SSO usually lands in 8 to 12 weeks. Problem management, change management with proper approval chains, a fuller CMDB and additional integrations follow in a second phase, taking most projects to 12 to 20 weeks end to end. Deep integration work, such as a legacy mainframe or OT systems, extends that. By comparison, enterprise SaaS rollouts like ServiceNow routinely run 9 to 18 months.
Can you build proper ITIL processes, or just a ticketing tool?
We build 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. The difference with a custom build is that the approval chains, SLA definitions and asset categories match how your organisation actually works, rather than being squeezed into a vendor's templates.
Can you integrate with our existing systems?
Yes. Common ITSM integrations include Active Directory or Azure AD for SSO and user sync, email-to-ticket, Microsoft Teams or Slack for notifications and approvals, monitoring tools like Datadog or Nagios for automatic incident creation, and finance or ERP systems for asset and contract data. We build API-first, so connectors to legacy or unusual systems are part of the design rather than an expensive bolt-on.
What about data security and compliance?
We build UK GDPR handling in from the start, including data subject access requests, retention policies and the distinction between deleting and anonymising historical records so audit trails stay intact. For regulated sectors we can align with ISO 27001 controls and structure audit trails, segregation of duties and change freeze windows around FCA, CQC or NHS expectations. Hosting can sit on UK infrastructure such as AWS London or Azure UK.
Who owns the platform, and are we locked in?
You own the code, the database and the data. The platform is built on standard frameworks and open APIs, so it can be hosted where you choose and maintained by your own team or another supplier later. There is no proprietary scripting language to lock you in, and no per-agent renewal that escalates each year.
Do you provide training for our team?
Yes. Training is role-based: longer hands-on sessions for service desk agents, focused workshops for asset and change managers, and short reference guides for approvers and end users. Documentation is written around your implementation, not a generic manual.