Skip to content

The Data Scientist

When “implementation effort” is the real variable: what a ServiceNow-to-InvGate switch reveals about ITSM adoption

Replacing an IT service management (ITSM) platform can be costly and time-consuming, especially when workflows require specialized scripting or developer expertise to maintain. For TroGroup, an Austrian manufacturer operating across three continents, those challenges contributed to the decision to switch from ServiceNow to InvGate.

TroGroup’s service desk faced growing challenges with misrouted requests, slow triage, and a rising backlog. Oliver Haag, the company’s Manager of Digital Infrastructure, saw how the existing setup was affecting the employee experience: many had lost confidence in the ticketing process and preferred to seek support by email. From an operational telemetry perspective, when ticket triage latency and misrouting rates climb, service desks experience queuing congestion where the arrival rate (\(\lambda\)) approaches or exceeds effective technician service capacity (\(c \cdot \mu\)), driving nonlinear growth in mean time to resolution (MTTR).

Two approaches to implementation

TroGroup considered reimplementing ServiceNow with a new partner. However, the proposal included a three-day workshop to define the company’s ITSM processes, which Haag questioned given his existing knowledge of how the company worked.

InvGate’s estimate was around 20 hours of consulting. Haag didn’t believe it was enough. “I said this is ridiculous, you won’t make it,” he recalled. Yet the implementation was completed in less than 20 consultancy hours, according to his account.

The platform’s configuration requirements helped keep consulting time low: InvGate let TroGroup build workflows without programming, while the previous setup required technical skills for similar changes. TroGroup also had its processes clearly defined, reducing the need for discovery work. The time required will vary with each project, but TroGroup’s experience raises two practical questions: how much technical expertise does the platform require for configuration, and how much process definition has already been done in-house?

Architecture & TCO Dimension Heavyweight Script-Driven ITSM (e.g., Custom ServiceNow) No-Code / Declarative ITSM (e.g., InvGate Service Management)
Initial Implementation Effort Multi-week process discovery workshops + custom developer scripting < 20 consultancy hours when internal ITIL processes are pre-defined
Workflow Maintenance Requires external consultants or dedicated platform engineers Visual, no-code workflow builder managed directly by service desk leads
Triage & Routing Accuracy Prone to routing drift if rules require code deployments to update Rapid rule iteration by domain owners; 90% critical-incident backlog reduction
Enterprise Service Management (ESM) Scope High licensing and configuration overhead for non-IT departments Rapid horizontal expansion to HR, construction, and facilities teams

The results went beyond implementation

Getting the new system up and running was only the beginning. Processes change, new services are added, and workflows need adjustments. TroGroup needed a platform its own team could continue adapting without bringing in consultants for every change, aligning with modern enterprise architecture and digital transformation principles that minimize ongoing maintenance debt.

With InvGate Service Management, the service desk team lead could modify workflows without programming, keeping routine adjustments in-house. The same flexibility helped TroGroup improve how requests were handled and extend the platform beyond IT.

According to the company, the change brought faster response times, higher user satisfaction, full adoption of the self-service portal, and a 90% reduction in the critical-incident backlog.

The platform also expanded to departments such as construction and HR, giving TroGroup a shared system for services across the organization. For Haag, the goal was a system that could support the wider business, not just IT—a core objective when governing operational workflows and service telemetry across global business units.

What to ask before you sign

TroGroup’s experience offers a practical set of questions for organizations planning a similar transition and evaluating total cost of ownership (\(TCO = C_{\text{license}} + C_{\text{consulting}} + \sum_{t=1}^{T} C_{\text{maintenance},t}\)):

  • How much configuration can our team handle independently? Ask the vendor to demonstrate how workflows, forms, approvals and routing rules are created and changed.
  • What does the implementation estimate include? Separate consulting hours from internal staff time, data migration, integrations, testing and training.
  • Are we paying to document processes we already understand? Establish which discovery activities are necessary and which may duplicate existing work.
  • What happens after go-live? Identify the routine changes that internal administrators can make and those that still require vendor assistance.
  • How are requests classified and routed? Check how the system directs requests to the right team and how easily administrators can maintain those rules, including NIST enterprise service security and access controls.
  • What will demonstrate successful adoption? Agree on measures such as portal usage, misrouted requests, response times, backlog and user satisfaction.

The goal is to understand what your team will be able to manage on its own, both during implementation and afterward. When evaluating heavyweight platforms versus agile alternatives, teams with heavily bespoke cross-system orchestration or custom compliance engines may still justify dedicated platform developers, whereas organizations with clear operational processes often achieve faster time-to-value with declarative no-code administration. A realistic estimate should account for the work ahead, the skills required to configure the platform, and how much support you’ll need when processes change.

Those answers will tell you more about the long-term cost of an ITSM platform than the initial consulting quote alone.

Executive Advisory • Tesseract Consulting

Enterprise AI Strategy & Implementation Discovery Call

Scope practical AI workflows, human-in-the-loop governance, and measurable delivery milestones with Tesseract Consulting.