TL;DR: Most IGA programmes govern only 13% to 15% of the application estate, leaving the rest to manual handling, and StackBob estimates that a 1,000-person organisation can absorb $12.9M in five-year costs, with 91.7% tied to the governance gap rather than platform spend. The real issue is not licence cost, but the operational, audit, and productivity drag created when access sits outside lifecycle control.
Editorial analysis by NHI Mgmt Group, based on content published by StackBob: “What Is IGA Coverage Gap Costing You Over Five Years?”.
Key questions
Q: What breaks when IGA does not cover the full application estate?
A: When IGA does not cover the full application estate, joiner, mover, leaver processes fall back to manual handling, access reviews become inconsistent, and audit evidence fragments across local owners and ticket queues.
Q: Why do ungoverned applications create both compliance and productivity costs?
A: Because the same missing control causes two different failures.
Q: How should organisations decide which apps to bring under IGA first?
A: Start with the applications that create the highest manual workload, the most access delays, or the most audit exceptions.
Practitioner guidance
- Map governed versus ungoverned application coverage Build a current-state inventory that shows which applications participate in automated joiner-mover-leaver, certification, and revocation flows, and which still rely on tickets or app-owner handling.
- Quantify manual fulfilment hours by application Measure helpdesk and IAM labour spent on requests for applications outside lifecycle control, then express it as recurring annual operating cost rather than one-off implementation work.
- Prioritise high-friction applications for governance extension Target the systems that generate the most access delays, audit exceptions, and manual provisioning effort, especially legacy apps and SaaS without SCIM support.
Bottom line: The article argues that the biggest IGA cost is not software licensing but the manual work created by applications that never enter governance.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Coverage, not licence count, is the real economic unit in IGA. The article shows that platform spend is only a small fraction of programme cost when the application estate remains mostly outside governance. The important question is how much of the estate can actually participate in lifecycle control, certification, and revocation. Practitioners should evaluate IGA as an enterprise coverage problem, not a procurement line item.
A few things that frame the scale:
- Nearly 60% of IT leaders cite restrictive cost and complexity as a weakness of legacy identity governance, according to the 2025 State of Identity Governance Report.
A question worth separating out:
Q: When does IGA investment become a cost-reduction decision rather than a control decision?
A: When the ungoverned portion of the estate is large enough that manual work, audit remediation, and delayed access outweigh the incremental cost of extending governance. At that point, the business case is no longer only about risk reduction. It is about removing recurring operating expense from identity operations.
👉 Read our full editorial: IGA governance gaps cost more than the platform itself