Industry Insights  |  5 min read  |  Audience: Commercial Enterprises

When organizations evaluate identity governance and administration platforms, the conversation is almost always about licensing, implementation, and ongoing maintenance. Rarely does anyone put a number on application onboarding — the process of actually connecting each application to the governance system, defining roles and entitlements, configuring provisioning rules, and validating that everything works.

That’s a significant oversight. Because application onboarding is where most IGA programs spend the majority of their time, their budget, and their organizational goodwill — and almost none of that cost appears on a line item.

Where Does That Number Come From?

The $15,000–$75,000 figure isn’t a licensing fee or a vendor charge. It’s the fully-loaded cost of the onboarding process itself — the people, time, and rework cycles that accumulate every time an organization brings a new application into its identity governance program.

The cost has several components:

Developer time: A skilled SailPoint developer may spend 20–40+ hours on a single application onboarding effort — initial configuration, testing, rework after gaps are identified, and final validation. At enterprise billing rates, that’s a substantial number before any other costs are counted.

Identity team coordination: Program managers, identity architects, and governance analysts spend hours in intake meetings, clarification cycles, and review sessions for every application. Multiply by the number of applications in your portfolio and the cumulative investment is significant.

Application owner time: The business-side cost is often overlooked entirely. Application owners who are unfamiliar with IGA requirements spend hours in meetings, answering follow-up questions, and reviewing configurations — time that comes out of their primary responsibilities.

Rework cycles: Configuration errors caught in testing require developer involvement to correct. Incomplete intake information requires additional rounds of clarification. Each cycle adds days to the timeline and hours to the cost.

Delay costs: Every week an application remains outside the governance framework is a week of unmanaged access, ungoverned entitlements, and compliance exposure. For regulated industries, the cost of delayed governance can exceed the direct onboarding cost.

Why the Number Varies So Widely

The range from $15,000 to $75,000 reflects the significant variation in application complexity, organizational process maturity, and team expertise. A simple application with a standard connector type and well-documented roles might come in at the lower end. A complex, custom-integrated application with poorly documented entitlements, unclear ownership, and a first-time application owner in the process? It can easily exceed the upper end.

What’s consistent across the range is that the majority of the cost is process cost, not technology cost. The IGA platform is already licensed. The infrastructure is already deployed. The expense is in the human effort required to onboard each application — effort that, in most organizations, follows no standard process and produces results of highly variable quality.

Most organizations have never calculated their true per-application onboarding cost. When they do, the number is almost always higher than expected — and it’s almost entirely avoidable.

The Scale Problem

For organizations with modest application portfolios, the onboarding cost is a manageable if frustrating reality. For enterprises with hundreds or thousands of applications — or for organizations undergoing cloud migration, M&A integration, or platform modernization — the cost at scale becomes a program-defining constraint.

Consider the math for an organization onboarding 200 applications at an average cost of $30,000 each: that’s $6 million in process cost before a single user’s access has been governed. At $45,000 per application, it’s $9 million. And that’s assuming each application is onboarded once — changes to application architecture, role structures, and entitlement models require ongoing re-engagement that multiplies the base cost over time.

What Changes When the Process Is Automated

Organizations that have moved from manual, ad-hoc application onboarding to a structured, automated process consistently see improvement in three dimensions:

Speed: Onboarding timelines that previously spanned weeks compress to days. Applications that required multiple rounds of developer involvement are processed through a guided self-service workflow that produces configuration-ready output automatically.

Consistency: Manual onboarding produces highly variable results depending on who’s doing it. Automated, structured onboarding applies the same governance defaults — birthright roles, eligibility checks, approval chains, lifecycle events — to every application, every time.

Cost: When developer involvement is limited to review and validation rather than intake, translation, and configuration, the per-application cost drops dramatically. The fully-loaded cost of an automated onboarding process is a fraction of its manual equivalent.

The business case for automation is straightforward: the savings on a portfolio of 100 applications at even a 50% cost reduction more than justify the investment in a structured onboarding platform. For larger portfolios, the ROI is substantially more compelling.

The Hidden Cost That Doesn’t Show Up Until It’s Too Late

Beyond the direct process cost, there’s a risk cost that rarely appears in budget conversations until an audit, an incident, or a compliance finding makes it impossible to ignore: the cost of applications that are governed inconsistently, incompletely, or not at all.

Every application that is onboarded through an ad-hoc, undocumented process is an application where entitlement definitions may be incomplete, where correlation attributes may be misconfigured, where lifecycle events may not trigger correctly. At scale, those inconsistencies accumulate into a governance posture that doesn’t reflect the access policy the organization believes it has.

Automated, structured onboarding doesn’t just reduce cost. It reduces risk — by ensuring that every application enters the governance framework with the same level of rigor, documentation, and validation, regardless of who managed the intake.