SaaS sprawl drives up IT support tickets and onboarding friction. Learn how in-app guidance and smarter governance reduce the load without slowing teams
Level 1 support tickets rarely spike all at once. They grow gradually, one small question at a time: how to find a report in the CRM, which HR portal to use, why a Copilot feature behaves differently than expected, or which purchasing screen is the correct one after a system update. In many organisations, SaaS sprawl -- the steady accumulation of overlapping tools and disconnected workflows -- turns these small questions into a constant stream of support requests.
For CIOs and IT leaders, this constant flow of small questions is not harmless. It consumes valuable support capacity, slows response times, and makes each new rollout harder than it needs to be. When organisations discuss the SaaS sprawl problem, the conversation usually centres on cost and security. But its day-to-day impact on IT support and onboarding is often overlooked.
This article explores SaaS sprawl from an operational perspective. It is intended for CIOs, IT Directors, Heads of IT Operations, and Application Owners who want to reduce repetitive support questions across tools such as Salesforce, Workday, Microsoft 365, Copilot, ERP and HR systems, and other specialised applications. We look at why SaaS sprawl increases support demand, how in-app guidance helps users complete tasks correctly, and how organisations can simplify their software landscape without slowing innovation.
On paper, your application landscape may look controlled: one main CRM, one HR system, one collaboration suite, perhaps one ERP. In reality, each of these core platforms is surrounded by many additional tools -- plug-ins, specialised SaaS products, AI assistants, team-specific apps, and older systems that are still in use.
This growing mix of tools creates complexity that is often felt first by IT support teams. Employees must navigate multiple interfaces, different logins, and overlapping features, making everyday tasks harder than they should be.
Common signs of SaaS sprawl include:
All of this increases the mental effort required to complete everyday tasks. When processes are complex, rarely used, or spread across multiple tools -- such as expense approvals, HR updates, or multi-step sales workflows -- employees often turn to the service desk for help. Over time, SaaS sprawl increases reliance on support teams simply because it becomes harder for users to know where to go and what to do.
Onboarding magnifies the problem. New starters are often hit with multiple logins, an overstuffed day-one training deck, and no meaningful in-app help. They learn by trial, error, and tickets. By the time you have a full cohort of new joiners every month, IT support has effectively become the substitute for a digital adoption strategy.
Ticket deflection is usually framed as a knowledge-base problem: if only the documentation were better, users would stop asking basic questions. In a SaaS-heavy environment, that thinking falls short. Nobody wants to read a wiki page to figure out how to raise a simple purchase request or book leave. They want the system to show them, in context, on the screen they are looking at.
This is where a Digital Adoption Platform (DAP) changes the equation. Rather than treating training as something that happens before go-live, a DAP like Lemon Learning adds a thin layer of in-app support across your strategic tools: Salesforce, Workday, Microsoft 365 and Copilot, ERP, HRIS, internal portals, and even legacy desktop apps. That support can take several forms:
As Pierre-Alexandre Mass, a transition CIO, put it: "You can run the most interesting project in the world, but if there is no support for users, adoption will be very limited. So you need tools that let people build skills on these new tools easily and intuitively." (CIO Pioneers podcast)
For IT operations, the strategic move is to connect this adoption layer directly to your ticket patterns. Instead of guessing which guides to build, start by mining your ITSM data:
1. Identify your top SaaS-related ticket types.
Look for patterns like "How do I book leave?", "Where do I update my bank details?", "How do I convert a lead in Salesforce?", "Why won't this invoice post?", or "How do I get Copilot in Teams?". These are the questions your service desk sees every week.
2. Map each ticket type to a real workflow.
Work through the actual click path in the relevant system. Where do people get stuck? Is the logic unclear, the labels confusing, the steps too long, or the error messages cryptic?
3. Turn those workflows into in-app guidance.
Use your DAP to build short, focused guides and tooltips that answer the question on the screen. Keep them concise: one clear outcome, minimal branching, completed in roughly 60 to 90 seconds of interaction.
4. Instrument everything.
Tag each guide by application, workflow, and ticket category. Lemon Learning's insights let you see how often guides are used, who uses them, and where users drop off.
Once in-app guidance is live, both users and support teams see immediate benefits. Employees receive clear, contextual help directly inside tools such as Workday, Salesforce, or Microsoft Copilot, helping them complete tasks correctly the first time. Support teams can link directly to this guidance instead of repeatedly explaining the same steps. Over time, simple requests decrease, leaving fewer but more meaningful support tickets -- and reducing the everyday friction that SaaS sprawl creates.
To manage SaaS sprawl effectively, organisations need a simple and repeatable approach. The objective is not to eliminate every extra tool, but to gradually reduce unnecessary complexity without slowing down teams or blocking useful innovation.
Step 1: Establish a joint view across IT operations, apps, and support.
Bring together representatives from IT operations, the service desk, and key application owners (Salesforce, Workday/HRIS, Microsoft 365/Copilot, ERP). Agree on a single report that combines SaaS ticket volumes by application and category, average handling time, and -- where available -- in-app guide usage.
Step 2: Pick a small number of "fix first" journeys.
Prioritise workflows that generate the most tickets, involve multiple tools, or are critical to business outcomes. Good candidates include: onboarding a new hire across HRIS, Microsoft 365, and identity; raising and approving a purchase request; creating and progressing a Salesforce opportunity; and using Copilot safely in Outlook and Teams.
Step 3: Design both the workflow and the guidance.
Sometimes tickets reveal a training gap; sometimes they expose a bad process. Use what you find to simplify screens, remove unnecessary steps, or standardise tools before writing more help content. Only then add in-app guidance that reflects the streamlined reality. This introduction to digital adoption is useful for aligning everyone on principles before you dive into content creation.
Step 4: Launch quietly, measure loudly.
Deploy guides to a subset of users or business units first. After a few weeks, compare ticket volumes, handling times, and error rates between guided and non-guided groups. If you have a SaaS management platform in place, also check whether overlapping tools for that journey are still being used.
Step 5: Iterate and expand.
Treat each wave as an experiment. Where guides work and tickets fall, scale the pattern to other regions or teams. Where they fail, look again at the process or configuration rather than simply adding more instructions.
Over time, you can present a clear story to stakeholders: targeted in-app guidance on your highest-volume workflows reduces repetitive Level 1 tickets, cuts average handling time, and narrows the number of overlapping tools in those journeys. That is a compelling argument when you need continued investment in both a DAP and SaaS rationalisation.
SaaS sprawl and rising support tickets are closely linked. It is difficult to reduce one without addressing the other. When employees have to navigate too many tools and unclear processes, questions and errors naturally increase. Combining SaaS governance with a digital adoption layer helps solve this problem in a practical way. Instead of relying only on training or documentation, organisations can guide users directly inside the tools they use every day -- making it easier to follow the right process at the right moment.
For CIOs and IT leaders balancing daily operations with long-term transformation, this approach helps reduce unnecessary support demand without limiting what teams can achieve. It allows organisations to overcome SaaS sprawl while keeping productivity and innovation moving forward.
SaaS sprawl creates overlapping tools, inconsistent processes, and fragmented user experiences. People get confused about which tool or path to use and log tickets for help. Each extra application adds configuration quirks and edge cases that surface as "how do I…?" requests.
Traditional knowledge bases help, but they require users to leave their workflow, search, and interpret instructions. In practice, many people prefer to ask the service desk. In-app guidance meets them where they are, on the screen, and is far more effective for routine workflows.
Begin by cleaning and standardising categories for the top applications: Salesforce, Workday/HRIS, Microsoft 365, ERP, and your service portal. Even a rough mapping of the most common question types is enough to identify candidate workflows for in-app guidance.
It depends on scale and focus, but many organisations see meaningful reductions on targeted workflows within one or two quarters -- especially where guides replace repeated "how do I?" tickets. The key is to prioritise, instrument, and iterate instead of trying to cover everything at once.
In the short term, it shifts effort from answering the same questions repeatedly to designing better workflows and guidance. Over time, you can handle growth without linear increases in headcount and free experienced staff to focus on true incidents and higher-value work instead of basic navigation problems.
SaaS sprawl creates overlapping tools, inconsistent processes, and fragmented user experiences. Employees struggle to know which tool or workflow to use, which drives up support tickets, increases onboarding friction, and raises security and cost risks.
Start with a full SaaS audit to map every application in use, then categorise tools by business value and usage. Consolidate overlapping apps, reassign or cancel unused licences, and put a governance process in place to control future purchases.
In-app guidance meets employees on the screen they are already using, walking them through tasks step by step. This reduces the need to contact the service desk for routine questions and improves first-time completion rates across key workflows.
Learn how to get ISO 27001 certified step by step, from defining your ISMS scope to passing the audit and maintaining certification long term.
Learn how to implement corporate data governance step by step — from defining goals and assigning roles to choosing tools and overcoming common...
Learn how to align your IT strategy with business objectives using 5 proven levers, practical governance frameworks, and performance metrics that turn