Application Onboarding: The Manual Problem Nobody Budgets For

Application onboarding is one of those things that sounds completely straightforward until you actually do it. "We just need to connect the app to the platform." Sure. And Frodo just needed to take a little walk.

The identity industry has been trying to solve this problem for over 30 years. Platforms have gotten more sophisticated. Investments have gotten bigger. And yet most enterprises still can't tell you with confidence who has access to what across their full application landscape. Not because they haven't tried. Because the problem is genuinely hard, and the approach hasn't kept up with the scale.

The technical challenges are real, but at least they're visible. A broken connector gives you an error message, something concrete to diagnose and fix. The part that actually kills programs is less obvious. It’s all the manual work and coordination, the human dependencies that stay invisible on a project plan until something just stops moving.

The Math No One Wants to Do

Enterprises don't operate with a handful of applications. They operate with hundreds. Sometimes thousands. And each application doesn't just need to connect to one platform.

It needs to connect to several. Each one a separate integration effort, with its own requirements, its own timeline, and its own set of manual steps that someone has to work through by hand.

Onboarding a single application across multiple platforms can run anywhere from 150 to 400 hours of manual effort per platform. That's not a typo.

Every discovery task, every entitlement mapping, every validation, every provisioning workflow has to be built, tested, and handed off manually. One application at a time. By a team with a limited number of hours in the week.

The result is exactly what you'd expect: fragmented investments and partial deployments. Every application effectively becomes three or more projects, and the backlog keeps growing faster than anyone can work through it.

The Spreadsheet Nobody Wants to Talk About

Most IAM teams have some version of it.

A tracker. A master list. A document that started as a clean onboarding plan and slowly became a color-coded monument to everything that hasn't happened yet.

Yellow means waiting on the app owner. Orange means waiting on IT. Red means it has been red for so long that nobody remembers what the original blocker was. And somewhere near the bottom, there are applications that haven't moved in so long they might as well be part of the document's furniture.

The tracker is a symptom, not the cause. It exists because application onboarding is still a manual, person-dependent process with no real automation underneath it.

Someone has to update it. Someone has to chase the status. Someone has to notice when it stops moving. That's not a workflow. That's a wish list with conditional formatting.

The Human Side of Manual Work

Here's the part that compounds all of it: every manual step in the onboarding process depends on a human being available and engaged at exactly the right moment. 

1. Provide documentation.
2. Validate entitlement mappings.
3. Review connector configurations. 
4. Confirm ownership. 

Each one of those sounds small. Each one is a potential stall point.

Every application has an owner, in theory. In practice, some have an owner who has no idea they're the owner. Some have three owners, all of whom think someone else is responsible.

Some have an owner who left the company and the application has been running on its own recognizance ever since. And the person listed as owner in your platform? They found out when you emailed them.

This is the part of onboarding that no vendor demo covers. The fellowship doesn't just form because you put names on a slide.

The manual coordination work has to happen across every application, every platform, every time. And until it's structured, it falls on whoever is willing to keep chasing.

The Real Takeaway

Thirty years of investment in Identity platforms and the onboarding backlog is still growing. That's not a knock on the technology. It's a sign that the manual effort wrapped around the technology has never really been solved.

The organizations making real progress aren't just the ones with the best connectors or the biggest budgets. They're the ones who figured out that you can't scale a manual process by working harder. At some point the process itself has to change.

The eight-month "in progress" item on the onboarding tracker almost never got stuck on a technical problem. It got stuck on the manual work around it. And that, more than anything else, is the problem worth solving.