Change still moves through a lot of UK businesses on spreadsheets, shared calendars and a thread of approval emails. It works until it doesn’t: a server change collides with a finance close, an audit asks for evidence nobody can produce, or two teams ship at the same time and take a service down. At ByteGears we build custom change management systems that put structure around all of that, shaped to how your organisation actually governs change.
“Change management” covers two related jobs. One is IT change control: patches, deployments, infrastructure work, with a Change Advisory Board, risk scoring and a calendar. The other is organisational change: process redesigns, system rollouts, the people side of getting a change adopted. Most packaged tools are good at one and weak at the other. A bespoke system can carry both.
Where off-the-shelf change management systems fall short
Packaged platforms solve a real problem, and for a lot of teams they are the right answer. The trouble starts when 70 to 80 percent of the tool fits and the remaining slice is the part that actually matters to you.
- Workflows assume generic ITIL. Vendor approval chains are built for a standard model. Real governance has conditional routing, multi-business-unit sign-off and risk thresholds that don’t fit the template, so teams end up working around the tool.
- Per-user pricing climbs faster than headcount. Mid-market platforms typically run from roughly £15 to £80 per user a month, and enterprise tiers run higher. Every requester and approver adds cost. Past a couple of hundred users that becomes a budget line nobody planned for.
- Collision detection is shallow. Most tools only flag a date and time overlap. They don’t know you have one DBA, shared test infrastructure or a team at capacity, so they miss the conflicts that actually cause outages.
- The CMDB rarely matches reality. Impact analysis is only as good as the dependency data behind it. Generic configuration models drift from your real topology, so “approved” changes still cause unexpected downtime.
- It doesn’t join up with your stack. Change data sits apart from incident tracking, asset management and your project tools. You end up with CSV exports, manual reconciliation and no single source of truth.
- Big platforms are slow and risky to land. A full enterprise rollout can run 12 to 18 months and well into six figures of professional services, and a meaningful share of those projects stall or get abandoned.
The cost shows up as slow approvals, low adoption, audit findings, and the occasional avoidable outage.
What’s different about a ByteGears custom change management system
We build in the UK, and the approach is straightforward.
Designed around your governance. We map your change categories, approval stages, risk model and blackout windows before anyone writes code. The system supports the way you already make decisions instead of forcing a new one.
Fixed cost, not per-seat. You own the system. There is no per-user meter on change approvals, so a requester in another department isn’t another line on an invoice. For larger organisations that is usually where the build pays for itself.
IT change and organisational change in one place. Run CAB-governed technical change and people-side transformation through the same platform, with visibility into how they connect.
Honest collision detection. We model your real constraints, shared infrastructure, scarce specialists, team capacity, so the calendar flags conflicts that matter and stops blocking changes that don’t.
Built for UK rules. Immutable audit trails, segregation of duties and UK data residency from the start, with FCA, Bank of England operational resilience, DORA, ISO 27001 and CQC requirements designed in where they apply.
Fits your existing tools. Direct API and webhook integration with your incident system, CMDB, identity provider and chat tools. No per-action middleware tax.
Features we build into change management systems
Every build starts with a credible core and then adapts to your governance:
-
Change request submission. A clear web form, or an API for automated requests, capturing title, justification, affected service and requested window.
-
Classification and risk scoring. Standard, normal and emergency change types with high, medium and low risk, scored automatically or by rule against your own thresholds.
-
CAB approval workflows. Multi-stage routing, technical review, business owner, final CAB sign-off, with escalation when an approver is unresponsive and delegation when someone is away.
-
Change calendar and blackout windows. A shared timeline of scheduled changes, with freeze periods for finance closes, peak trading or regulatory exercises, and collision detection tuned to your resources.
-
Impact analysis and CMDB. A configuration model and dependency graph aligned to your real architecture, so a proposed change shows which services and users it touches.
-
Audit trail and segregation of duties. An immutable record of every action, approver and timestamp, with controls that stop one person requesting, approving and implementing the same change.
-
Status tracking and rollback plans. Clear states from submitted through scheduled, implemented and verified to closed, with documented rollback procedures and success criteria.
-
Reporting dashboards. Change volume, approval dwell time by stage, risk heat maps, change success rate and compliance-ready reports.
-
Role-based access and notifications. Granular permissions plus alerts and approval requests in email, Slack or Teams.
-
Integration framework. Connectors to incident and problem management, identity providers, and CI/CD pipelines that can auto-create change records for code deployments.
How we build it
Discovery and design (2 to 4 weeks). Workshops to document change categories, approval workflows, CMDB scope and integration needs. Getting this right is the single biggest factor in whether the system gets adopted.
MVP build (6 to 9 months). Agile cycles with regular demos. The first release is a working system: submission, classification, a one or two-stage approval workflow, a change calendar with basic collision detection, an audit trail and role-based access.
Pilot and rollout (2 to 4 weeks). A limited user group tests real workflows, we refine, then move to a phased go-live rather than a risky big-bang cutover.
Phase 2 and beyond. CMDB-driven impact analysis, advanced risk modelling, multi-team workflows, chat-based approvals, DevOps integration and organisational change features are added once the core is bedded in.
We deliberately keep early scope tight. The most common reason these projects overrun is scope creep, “just one more integration”, so we agree an MVP and defer the rest.
What it costs
Custom development costs more upfront than a subscription. Over time, for the right organisation, the ownership maths works.
- No per-user meter. Once you are past roughly 150 to 200 active users, per-user SaaS pricing alone can run into tens of thousands a year before support tiers and add-on modules. A fixed-cost system removes that growth.
- You own the system and the data. No vendor roadmap dependency, no proprietary data model to escape, no expensive migration when you outgrow a template.
- Lower implementation risk. A focused 6 to 9 month build is a smaller bet than a 12 to 18 month enterprise platform programme that may not land.
- Faster, fitted approvals. A workflow built for your decision-making, with safe low-risk changes auto-approved, removes friction across the whole organisation.
We won’t put a guaranteed payback figure on the page. Book a free consultation and we’ll work through real numbers against your headcount, integrations and the platforms you’re comparing.
Where these systems get used
Change governance looks different by sector, and a bespoke build can reflect that:
- Financial services: CAB control aligned to FCA rules and Bank of England operational resilience; change freezes around stress-testing windows; DORA-ready audit trails for ICT change.
- Healthcare and care: clinical sign-off on changes to patient record and medication systems; documented change control for CQC and safeguarding processes.
- Manufacturing: production change scheduling that avoids peak windows; ISO 9001 change-control evidence; coordinated changes across supplier and quality systems.
- Technology and software: changes auto-created from CI/CD pipelines; collision detection across microservice deployments; fast-track emergency paths for security patching.
- Retail: POS and pricing changes scheduled into low-traffic windows; blackout periods over Black Friday and Christmas; omnichannel coordination.
- Public sector: auditable change records for public-facing systems; cross-department approvals; change history preserved for Freedom of Information requests.
- Professional services: controlled changes to client-facing CRM, billing and project systems, with documentation ready for external audit.
If your change process is genuinely standard and your team is happy to adapt to a vendor’s model, an off-the-shelf tool may be the sensible choice, and we’ll tell you so. Where your governance, compliance needs, integrations or scale push past what a template handles, a custom system is worth the investment. Book a free consultation and we’ll give you a straight answer either way.
Common Questions About Custom Change Management Systems
How does custom development cost compare to SaaS change management tools?
A custom build costs more upfront than a per-user subscription. The maths usually shifts once you pass roughly 150 to 200 active users, where per-user pricing on the mid-market platforms starts running into tens of thousands a year before support and add-ons. Beyond that point, owning a fixed-cost system that fits your governance tends to look better over a three to five year horizon. We will give you an honest comparison for your headcount and integrations rather than a generic promise.
What's the typical development timeline?
Most builds deliver a working MVP in 6 to 9 months: change submission, classification, a one or two-stage CAB approval workflow, a change calendar with basic collision detection, an audit trail and role-based access. More involved features, such as CMDB-driven impact analysis, multi-team workflows or DevOps integration, usually follow in a second phase. That compares with 4 to 8 weeks for a templated SaaS rollout and 12 to 18 months for a full enterprise platform implementation.
Can the system handle both IT change and business transformation?
Yes, and that is one of the better reasons to build rather than buy. Most off-the-shelf tools specialise in one or the other: ITIL-style technical change, or people-side organisational change. A custom platform can hold both, so you can see how an infrastructure change connects to a wider process or system rollout instead of running two disconnected tools.
Can you integrate with our existing ITSM and DevOps tools?
Yes. We commonly integrate with incident and problem tracking, asset management or a CMDB, identity providers such as Azure AD and Okta via SAML or OAuth, and communication tools like Slack and Microsoft Teams for approvals. For DevOps teams we can auto-create change records from CI/CD pipelines in Jenkins, GitHub Actions or similar. Integration is done directly through APIs and webhooks rather than per-action middleware.
What about data security, audit trails and compliance?
Every build includes an immutable audit trail (who changed what, when, why and with what approval), segregation of duties so one person cannot request, approve and implement the same change, role-based access control, and encryption in transit and at rest. We host in the UK, which keeps GDPR data residency clean. Where it applies we design around FCA and Bank of England operational resilience expectations, DORA, ISO 27001, ISO 9001 and CQC change-control requirements.
Do you provide training and ongoing support?
Yes. Training is tailored by role: a deeper session for CAB members and change managers, a shorter one for change requesters, and a brief overview for executives who mainly need reporting. After go-live we offer flexible support, from ad-hoc fixes to scheduled reviews, and we stay available to evolve the system as your process changes.