Who should own the service desk tooling in an outsourced contract?

Public sector organisations are increasingly choosing to procure ITSM tools directly, rather than consume them within a bundled service desk service.

The drivers are clear: reduce supplier dependency, retain control of operational data, and lower transition risk – aligning with government principles of openness, interoperability and avoiding perceived lock-in.

CGI’s service desk is tool-agnostic. We build, operate, consult and integrate across both client- and supplier-owned platforms, including ServiceNow and BMC Remedy, bringing consistent service quality, expertise and experience, regardless of ownership model.

As ITSM platforms become more feature-rich and automation-driven, the critical factor is not the tool itself but the operating model around it – combining technical expertise, user insight, and the ability to deliver change at pace.

There is a real risk that separation of operational accountability from the ability to change the platform quickly can create delay, weaken continual improvement, and can turn an expensive tool into an administrative system rather than a value engine.

Why buyers like client tool ownership 

Client ownership is attractive for understandable reasons. It can:

• Keep the master data set under direct client control while supporting a multi-supplier ecosystem 
• Simplify supplier transitions where the tool remains constant 
• Enable favourable enterprise licensing arrangements, particularly in the public sector. 

However, ownership alone does not guarantee agility. In practice, challenges can emerge where:

• Recommended improvements are delayed because implementation authority sits elsewhere
• Platform skills and effective product ownership are harder to sustain than expected
• Modern ITSM value comes less from basic ticket handling and more from workflow, knowledge, experience design and automation, all of which require active, experienced stewardship.

Tooling ownership models – benefits and risks:

Model 1: Supplier owned and operated tooling

In this traditional model, the service desk supplier provides ITSM tooling as part of the service, typically within a shared platform with secure segregation of client data. 

It is well suited to organisations that are seeking rapid improvement and reduced platform burden, and are prepared to contract strongly for data control and exit.

Advantages include:

• Centralised specialist platform support
• Continuous improvement embedded within service delivery
• Licensing efficiencies through bundled pricing
• Operational resilience within shared but segregated environments
• Removal of client burden for upgrades and specialist platform operations.

Key considerations: The principal concerns relate to dependency and exit complexity. These risks are often overstated but should still be addressed contractually. 

Mitigation typically includes: 

• A clearly defined and testable exit plan
• Structure governance to provide visibility of the platform roadmap.

Where these safeguards are in place, the model can deliver pace and embedded innovation. 

Model 2: Client owned, single supplier delivers both service desk and tooling support 

Here, the client owns the ITSM platform and licences, while one supplier is accountable for both service desk delivery and tooling enhancement. This model combines retained ownership with unified operational accountability. 

Its strengths lie in: 

• A single point of accountability for service performance and platform evolution
• A rapid feedback loop between operational pain points and configuration improvements
• A cleaner RACI model with fewer cross-party dependencies for standard changes.

The risk: The main risk is subtle rather than structural; dependency can reemerge through tacit platform knowledge accumulated by the supplier. This is mitigated though disciplined knowledge management and contractual controls, including: 

• Mandated documentation and configuration baselines
• Reusable scripts and structured knowledge transfer
• A detailed exit plan
• An empowered client product owner. 

When governed well, this model often balances control with agility effectively. 

Model 3: Client owned with separate service desk and tooling suppliers

This approach is typically chosen to reduce concentration risk or introduce a specialist tooling partner. It can provide useful challenge and technical depth. 

Potential advantages include: 

• Reduced reliance on a single supplier
• Access to specialist SME capability for platform optimisation
• Independent perspective on enhancement priorities – two-way improvements driven by both service desk provider and tooling partner.

However, operational friction is more likely under this structure. 

Improvement can stall if tactical changes require layered approvals or separate commercial pathways, or accountability may drift if decision authority and delivery capability sit with different organisations. In some cases, suppliers may operate competitively rather than collaboratively. 
 
Mitigation of these challenges requires deliberate structural design: 

• Delegating defined standard change to the service desk supplier within agreed guardrails 
• Establishing explicit decision rights within an enhanced RACI
• Maintaining a single, prioritised backlog owned by an empowered client product owner
• Aligning commercial incentives to shared outcomes rather than siloed metrics.

Without these controls, the model can weaken improvement velocity – but with them, it can function effectively. 

Contract design considerations for separate tooling and service desk suppliers

Where tooling and service desk responsibilities are split, governance maturity becomes decisive.  The following mechanisms are particularly important: 

• An empowered client product owner with a prioritised, shared backlog
• Clear decision rights distinguishing standard from major change 
• Controlled access enabling low-risk tactical updates without unnecessary delay
• Shared KPIs aligned to user experience and automation outcomes
• Joint governance forums with defined escalation pathways
• Pre-agreed commercial routes for low-risk change
• A structured innovation roadmap to protect improvement momentum

These mechanisms ensure that separation of responsibilities does not result in separation of outcomes. 

Contact management and telephony tooling is different

ITSM platforms and telephony platforms optimise different outcomes and should be treated differently. 

Telephony and workforce management tools are often embedded in core supplier operations to support rapid capacity flex, quality management, and resilience. Mandating client owned telephony may constrain flexibility and increase supplier costs if it prevents efficient capacity optimisation. 

To ensure coherence between client and supplier tooling, integration between contact management and virtual agent/AI aspects of the ITSM platform in needed. 

What to think about next

The debate is not really about who owns the tool. Modern ITSM platforms are highly integrable and increasingly standardised. 

The more enduring sources of value typically sit outside the technology itself – through experience gained establishing and operating a user-centric service, tailoring the model and tools to support the processes, knowledge, automation and intuitive self service options that your business needs. 

As customers review their approach, the real consideration is whether their chosen model preserves control while enabling safe, frequent improvement. Where responsibilities are split, alignment of operating model, RACI and commercial construct becomes critical. 

We advise incentivisation early in the design, to help to drive efficiencies for both the service desk and ITSM tooling, that work for the organisation and the respective service providers.

CGI has supported customers to design pragmatic contractual constructs, dependency models and collaboration agreements that allow tooling and service partners to operate as a single, outcome-focused ecosystem that delivers timely and tailored updates, improvements and innovation, including:

• Structuring commercial models to reinforce collaboration and improvement across contractual boundaries
• Designing operating models that sustain a holistic, adaptable service
• Embedding mechanisms for rapid low-risk tactical tooling updates and structured innovation
• Governing service, tooling and integration dependencies through clear prioritisation.

The right answer is rarely ideological, it is structural, commercial and operational. 

Get in touch to find out how we can support you on this journey.