You almost certainly own something in each of the categories below. None of them is wrong, and we are not asking you to replace them. What none gives leadership is one defensible answer about the whole technology estate.
They discover applications, track spend and report usage. Genuinely useful work.
Almost none of them began as a management platform — the category grew out of procurement tools, spend tools and identity tools that added management later. So the record sits to one side of how people actually work, and nobody has a reason to keep it current. It is accurate the week it is built and stale a month after.
Authentication, access and the joiner-mover-leaver lifecycle. Essential infrastructure—but not a complete answer about technology cost, ownership or value.
Identity only sees what sits behind single sign-on — roughly half of what a company actually runs. Anything bought on a card, bundled inside a larger invoice or standing outside SSO never appears. It knows the door is open. It does not know what the tool costs, who owns it, or whether it should exist.
Intake, approvals, negotiation and vendor benchmarking. They save real money at the contract line.
Most departments hold their own budget and buy their own way, so a large share of spend never reaches procurement at all. What does pass through is governed once, at the moment of purchase, and then nothing watches the three years that follow.
Employee lifecycle, payroll, and provisioning for the applications wired into them.
Not a competitor. HR systems manage the person. The technology estate is a different problem, and the business decisions around it remain elsewhere.
Enterprise IT operations, an application portfolio and audit controls, at real depth.
Built for IT, owned by IT, and in practice siloed there. Twelve-month-plus implementations and six-figure pricing. A finance or operations leader rarely gets a straight answer out of it about what something costs and whether it earns its place.
A standalone inventory decays because nobody is required to touch it. Odau does not sit to one side of the work — procurement requests and access reviews run through it, so the record is maintained as a by-product of decisions people were making anyway. That is the difference between a list and a system of record.
Categories, not vendors — individual products vary and the good ones keep moving. Judge any specific tool against these rows yourself.
Odau records, governs and routes. It does not grant or revoke access, and it does not negotiate or execute a purchase — those stay with the system that owns them and the person accountable for it. Odau is where the request is raised, reviewed and evidenced, and where the outcome is recorded.
Keep the systems that work. Odau gives leadership one governed answer across the technology estate.