Implement IT Service Management

Service Desk Launch

A live, ITIL-aligned service desk your team actually uses — in weeks, not quarters.

Stand up a production service desk on Jira Service Management, ONES.com or HaloITSM in six to eight weeks, with your workflows, SLAs and portal configured and your team trained.

Duration

6–8 weeks

Pricing

on request

Deliverables

8 included

The figure above covers this initial engagement. Where discovery shows the work needs more, we continue on an optional time-and-materials basis.

What's included

  • Platform selection support and licence sizing
  • Request catalogue and portal design
  • Incident, request, change and problem workflow configuration
  • SLA and escalation policy setup
  • Two integrations with your existing systems
  • Knowledge base structure and seeding
  • Administrator and agent training
  • Two weeks of hypercare after go-live

Who it's for

  • Organisations moving off email, spreadsheets or a legacy helpdesk
  • Teams consolidating several departmental desks onto one platform
  • IT functions formalising service management for the first time

A service desk implementation fails for predictable reasons: the request catalogue mirrors the org chart instead of how people ask for help, SLAs are set to numbers nobody can meet, and training happens the week after go-live rather than the week before.

Service Desk Launch is scoped to avoid all three.

How it runs

Weeks 1–2 — Design. We agree the request catalogue with the people who will answer the tickets, not just the people who own the budget. We define workflows, approval paths and SLA targets against what your data says is achievable.

Weeks 3–5 — Build. We configure the platform, set up the customer portal, wire up two integrations with your existing systems, and structure the knowledge base so it is useful on day one rather than a year in.

Weeks 6–8 — Enablement and go-live. Administrator and agent training, a supervised pilot with a limited audience, then full launch with two weeks of hypercare while your team settles in.

Platform choice

We are an Atlassian partner and implement Jira Service Management most often, but this package is deliberately platform-flexible. Where data residency, licence economics or feature fit point elsewhere, we implement ONES.com or HaloITSM instead. If you are not sure which is right, start with the ITSM Health Check.

How scope expands

The starting price covers two integrations and one service desk project — enough to get a working desk live and learn how your organisation actually uses it. Additional integrations, further business units, or asset management scope are handled on an optional time-and-materials basis, described and agreed with you before the work begins.

Interested in Service Desk Launch?

Tell us about your environment and we will confirm the starting scope and price before any commitment. If a different package fits better, or if you need something else entirely, we will say so.