Turnkey ITSM: Live in Weeks, Not Years
The industry has trained buyers to expect year-long ITSM projects and paywalled modules. It doesn't have to be that way. A blueprint for standing up incident, change, problem, request, CMDB and AI-assist under one license — and going live in weeks.
The year-long implementation is a choice, not a law
Most enterprise ITSM projects are slow for structural reasons, not technical ones. Scope is negotiated before anyone has looked at the actual ticket volume. The tool is customised to reproduce the old process instead of replacing it. And every stakeholder adds one more approval step, because adding is free and removing is political.
When we run implementations, the first working session is not about the tool at all. It is about the ten request types that make up most of the volume, and the three approval chains that actually carry risk. Everything else is noise that can be absorbed into a later iteration.
What 'turnkey' actually means
A turnkey go-live is not a small go-live. It is a disciplined one. The difference is in what you refuse to build in phase one:
- Incident, service request and knowledge — live in the first wave, because they touch every user on day one.
- Change and problem — configured with real approval logic, but only for the change classes that genuinely need review.
- CMDB — seeded from discovery and asset data you already have, not drawn from scratch in workshops.
- Integrations — identity and email first; everything else queued by measured demand, not by stakeholder seniority.
The two decisions that decide the timeline
First: pick a platform whose licensing does not fragment the design. When every module is a separate commercial conversation, the project plan becomes a procurement exercise. An all-inclusive platform keeps the design conversation technical, where it belongs.
Second: appoint one business owner with authority to say 'that is good enough for go-live'. Projects stall in the space between six stakeholders who can each say no and none who can say yes. The fastest implementations we have delivered all had a single empowered owner; the slowest all had a committee.
What you give up — honestly
A weeks-long go-live means some edge cases are handled manually for a while. Some reports arrive in month two instead of week one. A few teams will keep a familiar spreadsheet longer than they would like.
The trade is deliberate: a live system collecting real usage data teaches you more in a month than a year of design workshops. The organisations that struggle are not the ones that went live with eighty percent of the scope. They are the ones that never went live at all.
The takeaway
If your ITSM project plan is measured in years, ask which parts of the timeline are engineering and which are negotiation. The engineering is almost never the long pole.
Related
How we deliver Halo ITSM