Halo ITSM Implementation

Halo ITSM Complex Deployment Plan.
Built for complexity. Delivered with rigour.

The Complex Deployment Plan is a structured 17-week programme for organisations with deeper requirements — more integrations, more stakeholders, more process. Four phases, each closing with a customer sign-off gate before the next begins.

Delivered by Allied ESM × Powered by Halo

17
Weeks
4
Phases
4
Sign-off gates
£60,000
Fixed price

What sets this apart from Standard

  • 3-week discovery with multiple workshops
  • 5-week build phase for complex requirements
  • Dedicated Solutions Architect throughout
  • 3-week customer-led UAT with fix cycle
  • Dedicated training and go-live preparation
  • Sign-off gate closes every phase
Halo

Accredited Partner

One of only a small number of partners exclusively dedicated to the Halo ecosystem globally.

HALO Official Partner HALO Certified Partner
Delivery Approach

Phase by phase

Four phases, each with a defined scope, a dedicated effort budget, and a formal customer sign-off before moving on.

P1
Weeks 1–4
Discovery & Design

Understand before we build

Project kick-off and governance model
Multiple structured workshops — ITSM processes, categories, SLAs
Integration design — directory, email, and third-party systems
Design document produced and reviewed
🔏 Build spec agreed and signed off
P3
Weeks 10–13
UAT

Your team puts it through its paces

Customer-led testing of the full build
Issue log raised and reviewed with the consultant
Defect fixes, stabilisation, and minor enhancements
🔏 Solution confirmed ready for go-live
P2
Weeks 5–9
Build

Configure to the spec

Core config — directory integration, ticket types, SLAs
Workshop outputs built out across weeks 5–8
Integrations configured and tested
Portal, automations, and reporting activated
🔏 Build reviewed and signed off
P4
Weeks 14–17
Training & Go-Live

Live and in your team's hands

Training materials prepared and delivered — agents and admins
Go-live readiness, communications plan, and cutover preparation
Go-live with early-life support
Handover pack delivered, project formally closed
🚀 Live, stable, and handed over to your team
Governance & Control

Nothing moves without your sign-off

Complex projects fail when scope drifts and decisions get made without the right people in the room. This plan is structured so you stay in control at every stage — not just at go-live.

1
After Discovery & Design — Week 4

Build spec sign-off

Before a single line of configuration is written, you review and formally approve the design document. What's in scope, what's out, how integrations will work, and what the finished platform will do. No ambiguity going into build.

2
After Build — Week 9

Build review sign-off

The full build is reviewed against the agreed spec before UAT begins. You confirm the platform matches what was designed. Issues are resolved here — not discovered by your team during testing.

3
After UAT — Week 13

Go-live readiness sign-off

Your team tests the platform end-to-end. Every issue is logged, triaged, and resolved. You formally confirm the solution is ready before training begins — nothing goes live that hasn't been approved by your stakeholders.

4
After Training — Week 17

Project closure sign-off

Training is delivered, the handover pack is in your hands, and the project is formally closed with a documented record of everything built and every decision made. You own it completely from day one.

Not sure which plan fits?

Complex requirements deserve a proper conversation.

Tell us about your organisation — your current setup, your integrations, and what you need Halo to do. We'll scope the right plan and give you a clear picture of timeline and effort before you commit to anything.

Talk to Allied ESM →