Taming SaaS sprawl with a digital adoption layer

If you run IT or transformation in a mid-sized or large organisation, you don’t need another definition of SaaS sprawl, since you live it. Finance discovers three different whiteboarding tools on the card statement. Marketing is paying for two automation platforms. Somewhere in HR, a team has bought its own “lightweight HRIS” on top of Workday. Meanwhile, your official backbone tools such as Salesforce, Microsoft 365 with Copilot, Workday, your ERP and HRIS, still aren’t being used the way you designed.

SaaS sprawl is usually treated as a procurement or security headache. In reality, it is an adoption problem. People reach for new tools when the sanctioned stack feels too hard, too slow, or too rigid for the work in front of them. If your response is only to centralise buying and tighten controls, you will push experimentation into the shadows while usage of your strategic platforms remains patchy.

This article argues for a different approach: pairing SaaS management with a digital adoption layer that makes it easier to do the right thing in the tools you already pay for. We will look at what SaaS sprawl really costs, how to design an adoption layer across core platforms like Microsoft 365, Copilot, Salesforce, Workday, ERP and HRIS, and how to measure progress in terms that matter to the board: support load, risk, and ROI.

Why SaaS sprawl is an adoption symptom, not just a spend problem

Most CIOs now accept that SaaS sprawl is structural, not accidental. Surveys from SaaS management vendors such as Torii and Zylo show that large enterprises typically run hundreds and sometimes thousands of apps, with a significant share operating outside formal IT oversight. Torii’s 2026 benchmark report, summarised in this CIO Dive analysis, puts the average large enterprise at more than 2,000 applications, with only a small fraction fully sanctioned.

It is tempting to see this purely as waste and risk. There is certainly plenty of both. Zylo, whose platform is positioned as a “financial system of record for SaaS”, highlights how overlapping tools, idle licences, and unmanaged renewals quietly drain budgets, as described on their product overview. Security teams rightly worry about data in unvetted tools and accounts that are never properly deprovisioned.

But if you stop there, you are looking at the symptom, not the cause. SaaS sprawl accelerates when:

• Core platforms are hard to use. If it takes ten clicks and a PDF job aid to raise a purchase request in your ERP, someone will find a workaround.
• Change lands faster than enablement. New Salesforce objects, fresh Copilot capabilities, or updated HR processes arrive without in‑app guidance, so people cling to familiar side tools.
• Local teams are under pressure. Marketing, HR, or Operations leaders buy point solutions to hit their own targets when central roadmaps feel slow or abstract.

Shadow IT and shadow AI behave the same way. Employees do not wake up wanting to bypass policy; they are trying to get work done in an environment where sanctioned paths are often the hardest.

From a CIO perspective, that means you cannot rationalise your way out of SaaS sprawl with contract work alone. You also have to change the lived experience of your official stack so that, in practice, it becomes easier to use the tools you want than to keep spawning new ones.

Designing a digital adoption layer to absorb SaaS sprawl

SaaS management platforms give you the inventory and financial lens you need: they tell you what is out there, what it costs, and where licences are under‑used. What they cannot do is make Salesforce easier for sales managers, Workday less opaque for line managers, or Copilot safer for knowledge workers. That is the role of a digital adoption layer.

A Digital Adoption Platform (DAP) such as Lemon Learning overlays your existing applications with in‑app guidance: step‑by‑step walkthroughs, field‑level tips, contextual announcements, and an embedded help centre or AI assistant that answers “how do I do this?” in the flow of work. Instead of sending users to PDFs or intranet wikis, you express the “golden path” for key workflows directly on the live screen.

To use that layer against SaaS sprawl, you need to design it deliberately around three questions:

1. Which workflows matter enough to standardise?
Start from the journeys that justify your biggest SaaS investments: opportunity management and forecasting in Salesforce; self‑service HR in Workday or your HRIS; purchase requests and approvals in your ERP or purchasing system; everyday productivity in Microsoft 365 and Copilot. For each, document the happy path and the most painful failure modes—tickets, errors, rework, or shadow tools.

2. Where are users defecting to side tools today?
Combine SaaS discovery data from tools like Zylo or Torii with adoption analytics. If people export Salesforce data to spreadsheets to “fix” reports, or use Notion and Miro instead of your official collaboration standards, treat that as design input. The goal is not to lecture teams for improvising; it is to understand what your core stack is failing to do for them today.

3. How can in‑app guidance make sanctioned tools the path of least resistance?
This is where a DAP becomes tangible. Instead of training sellers in a classroom and hoping they remember, you attach concise, role‑specific guides to your Salesforce layouts. Instead of a 20‑page document on raising a compliant PO, you provide a 90‑second walkthrough on the ERP screen that highlights which fields matter, how to pick the right cost centre, and what happens downstream. In Microsoft 365, you wrap priority Copilot scenarios with short guides that show how to use AI safely and productively in Outlook, Teams, and Word.

External resources can help benchmark your approach. PDQ’s pragmatic guide at this article on SaaS sprawl rightly emphasises ownership, approval rules, and a “system of record” policy. A digital adoption layer adds the missing human piece: it shows people, in context, what those decisions mean on screen.

Handled well, the result is a thin, reusable guidance fabric across your sanctioned stack. Rather than every team bolting its own tours or wikis onto favourite tools, you run one adoption layer across Salesforce, Microsoft 365, Copilot, Workday, ERP, HRIS, and internal portals. That consistency is how you gradually reclaim messy usage without freezing innovation.

Making SaaS governance measurable and defensible

In a flat‑budget world, you will not get sustained support for SaaS rationalisation or a DAP unless you can show concrete movement on cost, risk, and productivity. That demands a simple, disciplined scorecard.

Start by combining three data sources:

• SaaS inventory and spend. Your SaaS management platform or finance system should tell you what you are paying for, by category and vendor.
• Application and support telemetry. Ticket data, error logs, and high‑level usage stats from your core platforms—Salesforce, Microsoft 365, Workday, ERP, HRIS.
• Digital adoption analytics. From your DAP, you should see which guides and tooltips are used, where users drop off, and what they search for when stuck. Lemon Learning’s own guidance on metrics at this metrics article offers a useful blueprint.

Then pick a handful of scenarios where SaaS sprawl and adoption problems intersect. For example:

• Salesforce vs side CRMs and spreadsheets. Measure guide usage on core opportunity workflows, related ticket volume, and the number of off‑platform tools used for pipeline tracking.
• Workday or HRIS vs local HR tools. Track completion of in‑app onboarding and self‑service guides, HR ticket volume by category, and the number of unofficial HR spreadsheets or portals in use.
• Microsoft 365 and Copilot vs external productivity apps. Monitor adoption of guided Copilot scenarios, support tickets, and spend on overlapping note‑taking, meeting, or document tools.

For each scenario, define a few directional targets: fewer redundant tools, lower Level 1 tickets, better completion rates, cleaner data. Use your DAP to iterate. If a workflow shows stubbornly high errors or external tool usage despite strong guide engagement, the problem is probably process or configuration, not just training.

Over time, this lets you tell a credible story in the language your board expects. Instead of “we reduced SaaS sprawl”, you can say: “By redesigning our purchasing journey, deploying in‑app guidance, and retiring three overlapping tools, we cut related tickets by 30%, reduced SaaS spend in that category by 18%, and improved first‑time‑right POs by 20%.” Those are numbers finance and operations leaders can recognise.

In summary, SaaS sprawl is not going away. But you can decide whether it remains an unmanaged by‑product of local problem‑solving or becomes raw material for a better, more governed digital workplace. Pairing SaaS management with a digital adoption layer—one that sits across Salesforce, Microsoft 365, Copilot, Workday, ERP, HRIS, and your internal portals—is how you shift from chasing invoices to actively shaping how work gets done. Done well, you will see fewer tickets, calmer rollouts, and a stack that your people actually use, not just one you pay for.

FAQ