The software estate your catalogue will never find.
A global technology company. Mature enterprise architecture governance. Every software procurement decision routed through the intelligence layer. Someone asks a routine question, and the system returns nothing because the tool isn't there.
The company was real, the governance was serious, and the question was simple: what alternatives do we have for DocuSign across the estate? The intelligence layer came back empty. DocuSign was not in the catalogue at all.
Not because the system failed. The system worked exactly as designed. DocuSign simply is not the kind of software that gets discovered.
Why SaaS doesn't get caught
DocuSign has no on-premises installation. There is no endpoint to scan. You navigate to a URL, authenticate, and use the product. The SAM tool never touches it. The discovery agent never catches it. As far as the catalogue is concerned, the tool does not exist.
This is not a DocuSign-specific problem. DocuSign is just the one someone happened to ask about. The same structural blind spot applies to Slack, Figma, Miro, Notion, and Salesforce, and the entire SaaS layer that accumulated across the estate over the past decade. Tools that arrived on a corporate card rather than through procurement. Subscriptions that finance knows about but IT does not. Applications that marketing uses daily but enterprise architecture has never seen.
Three pictures of the same estate, none of them complete
Most enterprises carry three separate views of their software. SAM tools discover what is installed via endpoint scanning. Procurement systems record what went through a formal approval process. Finance captures what hit a subscription line or corporate card. None of these three pictures overlaps fully with the others. None tells you what the software actually does.
You think you know what software you own. You know what you installed. Those are not the same thing.
The gap compounds with time. Enterprise teams adopt SaaS tools quickly, often outside the formal procurement cycle. By the time the catalogue team hears about a product, it may have been in active use by hundreds of people for years, spread across multiple cost centres, under payment arrangements nobody has a complete view of.
Every decision made against a partial picture
Here is where the real cost sits. Every governance decision, whether to buy a tool, renew a contract, consolidate a category, or retire a product, gets evaluated against the catalogue. If the catalogue is missing an entire class of tools, every single decision gets made with incomplete information.
Someone requests a new contract management tool. You search the estate. Nothing found. The procurement cycle begins. Months later, you discover that several hundred people have been paying for DocuSign for years. That outcome is not a procurement failure. It is a catalogue failure. And it is common.
We have a request to purchase DocuSign for the contracts team. Nothing came up in our catalogue search. Can we proceed?
DocuSign is already active in your estate. Finance records show 340 licensed seats across three business units, acquired via corporate card spend over the last four years (annual outlay approximately £180,000). Raising a new contract would create a fourth parallel agreement. Recommend consolidating existing seats under a single enterprise agreement before any new purchase is approved.
The answer isn't a better scanner
An improved endpoint scanner still will not find tools accessed through a browser. The problem is not the quality of the discovery mechanism. It is architectural. A catalogue built primarily around installation scanning has a structural blind spot for the way modern software is consumed, and that blind spot does not close by scanning more frequently or more thoroughly.
The answer is a catalogue designed to be complete, not just discoverable. That means drawing in SaaS spend data from finance systems, contract data from procurement, and usage signals from the applications themselves. Completeness treated as a design requirement rather than a goal the team works towards eventually.
This is the premise behind how Samplify is built. Feature-level intelligence across the full estate, SaaS included, with context drawn from wherever the data lives. So when someone asks what alternatives exist for a given tool, the answer reflects the estate as it actually is, not as the scanner last saw it.
You think you know what software you own. You know what you installed. Those are not the same thing.
The question worth asking before the next request lands
Pick any three SaaS tools your team relies on daily. Slack. Salesforce. Figma. Ask your SAM platform for the renewal status, seat count, and feature summary for each. See what comes back.
If the answers are incomplete, or if any of those tools simply do not appear, the catalogue gap is real in your estate. The question is whether a duplicate purchase or a missed consolidation has to happen before it becomes a priority.
If your catalogue cannot answer what you own today, the conversation is worth starting now.
The 30-day proof
Run Samplify on your stack, your questions, your inbound flow.
Start your 30-day proof →