The Death of Tier-1 Support: Why ERP Consultancies and IT Helpdesks Cannot Defend the Billable Hour

Created on 2026-09-08 — updated on November 14, 2026


The Death of Tier-1 Support: Why ERP Consultancies and IT Helpdesks Cannot Defend the Billable Hour

Reading time: 6 minutes. Author: Hugo S. Nascimento.

Context: I wrote this after auditing an IT helpdesk ticketing log where routine master data fixes in TOTVS and SAP took forty-eight hours to resolve, while external consultancies billed hundred-dollar hourly rates for simple configuration changes. The billable hour model for Tier-1 support is dead.

Executive Summary for Technology Leaders: For decades, global systems integrators and ERP support consultancies — such as Accenture, Stefanini, Sonda, Capgemini, and traditional SAP or TOTVS Application Management Services partners — built recurring revenue on monthly hour packages for Tier-1 tickets. Meanwhile, enterprise ITSM platforms like ServiceNow and Jira Service Management charge per-agent seat licenses plus steep add-ons to route those same tickets across human queues. hsnlabs eliminates Tier-1 ticket queues by deploying headless autonomous agents over the Model Context Protocol and LangGraph — diagnosing and resolving SAP, TOTVS Protheus, and Active Directory exceptions in milliseconds without per-seat SaaS taxes or hourly sustaining retainers.


Diligence Note and Public Sources

The enterprise support structures, ITSM licensing models, and integration protocols analyzed in this article are grounded in public documentation:

  • ServiceNow IT Service Management and Now Assist Licensing Structure: detailing per-fulfiller seat licensing and Pro Plus AI add-on models, available at ServiceNow ITSM Official Portal.
  • SAP Application Management Services and BAPI Integration Standards: official technical documentation for programmatic ERP transactions, available at SAP Help Portal.
  • TOTVS Protheus REST API and Framework Documentation: official technical reference for master data and fiscal routines, available at TOTVS Developer Network.
  • Model Context Protocol Open Specification: open standard for deterministic agent tool execution, available at Model Context Protocol Documentation.

1. The Two Extractive Pillars of Enterprise Support

The enterprise IT sustaining model is built on a misaligned economic incentive: selling expensive human billable hours for trivial, procedural work.

Every month, mid-market and enterprise companies pay multi-thousand-dollar Application Management Services retainers to systems integrators and consulting firms to maintain installations of SAP S/4HANA, Oracle, and TOTVS Protheus.

When an internal accounting clerk encounters an error because a vendor CFOP tax code is missing or an inventory batch failed, what happens?

The clerk files a ticket in ServiceNow or Zendesk. The ticket sits in a queue for twenty-four hours. A junior consultant opens the ERP, cross-references a standard configuration table, enters the missing code, clicks save, and bills two hours on the client's monthly statement.

There is zero intellectual creativity or strategic thinking in that workflow. It is pure mechanical rote work across two massive cost centers:

1. The ERP Sustaining Retainer Illusion

Enterprise leaders are conditioned by traditional integrators — such as Stefanini, Sonda, Accenture, and regional SAP or TOTVS partners — to believe that maintaining an ERP requires a continuous army of external consultants.

When you audit these monthly retainers, over seventy percent of the logged hours do not involve complex system upgrades or custom architecture. They consist of mundane master data maintenance: fixing address formats, updating tax withholding codes, re-routing rejected approval workflows, and reconciling stuck batch jobs.

When an autonomous agent is connected directly to ERP APIs and error logs, it detects the missing master data parameter, validates the entry against the corporate business ontology, and commits the fix in two hundred milliseconds. The entire justification for fifty-thousand-dollar monthly sustaining retainers evaporates.

2. The Internal Helpdesk Triage Queue

The same mechanical waste plagues internal IT service management:

  • Unlocking Active Directory accounts and resetting multi-factor authentication tokens.
  • Provisioning standardized email group memberships and role-based access permissions.
  • Diagnosing recurring VPN handshake failures and local network configuration errors.
  • Parsing application server crash logs to match known error codes.

Helpdesk technicians spend their days acting as manual switches between user chat messages and administrative web consoles. Autonomous agents connected via authenticated Model Context Protocol endpoints execute these routine procedures instantly, eliminating ticket queues and cutting resolution times from days to seconds.


[Agentes] x [a Gente] — Beyond the hype: how Agentic AI multiplies and leverages human labor capacity. Bi-weekly field notes published in Hugo S. Nascimento's LinkedIn newsletter with over 1,600 subscribers. Follow on LinkedIn ↗

2. Executive Comparison: ERP AMS Consultancies vs ITSM Suites vs hsnlabs Agents

When a CIO or CFO audits IT support expenditure, three structural models compete for operational budget:

Operational and Financial Vector Traditional ERP AMS Consultancies - Accenture, Stefanini, Sonda Commercial ITSM and Copilot Add-ons - ServiceNow, Zendesk Headless Self-Healing Agents - hsnlabs
Core Resolution Mechanism Junior analysts reading tickets manually and clicking through SAP or TOTVS screens AI chatbots summarizing tickets so human agents can still execute the fix manually Autonomous protocol-level execution via MCP directly against SAP, TOTVS, Oracle, and Active Directory
Mean Time to Resolution 24 to 72 hours sitting in Tier-1 and Tier-2 triage queues Hours waiting for a human fulfiller to approve and apply the change 200 milliseconds to 5 seconds via deterministic state machines and automated rollback guards
Commercial and Pricing Model Monthly hour retainers or time-and-materials billing; vendor profits when ticket volume grows High per-agent seat licenses plus 30 to 60 percent markups for enterprise AI add-on SKUs Fixed-scope engineering delivery; zero per-seat licensing and up to 85 percent reduction in AMS hours
Cross-System Execution Siloed by practice: SAP squad does not touch TOTVS, Active Directory, or custom databases Restricted to workflows native to the ITSM platform unless expensive custom spokes are purchased Unified Python and Pydantic ontology orchestrating actions across heterogeneous ERPs and legacy DBs
Auditability and Compliance Manual ticket notes often incomplete or closed without documenting root cause Logs the conversation in the ticket, but manual ERP changes remain unverified Cryptographic audit trail of every MCP payload, schema validation, and state transition

3. Shifting from Ticket Triage to Autonomous Self-Healing

The goal of modern enterprise architecture is not to buy expensive AI copilot seats so human technicians can close tickets ten percent faster. The goal is to eliminate the concept of the Tier-1 support ticket entirely.

When autonomous agents built by hsnlabs monitor system telemetry and operational exceptions in real time, they validate business invariants in Pydantic and LangGraph and resolve root causes autonomously before an employee even notices an error.

The billable-hour consulting firm wants systems to break so they can bill hours to fix them. The enterprise needs systems that repair themselves. Deterministic Agentic AI architecture makes that economic alignment possible.



Article originally published on hsnlabs. Author: Hugo S. Nascimento.

Hugo S. Nascimento
Have a project in mind?
Share it with Hugo, CPTO
Start a Conversation