# SaaS Management Platform Market > Size of the SaaS management platform market plus hard data on SaaS spend per employee, app counts, shadow IT and the waste that funds these tools. Source: https://saas-marketing.net/guides/saas-management-platform-market/ Topic: SaaS Market and Industry Data Type: guide Published: 2026-09-11 Last updated: 2026-09-11 Publisher: SaaS Marketing (saas-marketing.net) License: CC BY 4.0. Quote or republish with attribution and a link to https://saas-marketing.net/guides/saas-management-platform-market/ ## Short answer The SaaS management platform market is a low single digit billion dollar software category growing in the high teens to mid twenties annually, with vendors including Zylo, Productiv, Torii, Zluri, Vertice and Spendflo. Its size is set by measured waste. Published vendor research consistently finds companies run hundreds of applications, spend several thousand dollars per employee per year on software, and leave roughly a third to a half of purchased licences unused. ## Key takeaways - SMP vendors sell against measured waste, so the category ceiling tracks reported unused licence rates more than it tracks IT budget growth. - Zylo's published index work has put annual SaaS spend near 4,800 dollars per employee, with large enterprises running hundreds of distinct applications. - Roughly a third to a half of purchased SaaS licences go unused or barely used in the average enterprise estate, depending on whose methodology you accept. - Shadow IT is not a rounding error: expense card and SSO discovery routinely surfaces two to three times the apps IT thought existed. - Buyers justify SMP spend with a savings multiple, usually needing five to ten dollars back for every dollar of platform fee. - The category is being absorbed into procurement and ITAM suites, which caps standalone vendor pricing power over the next few years. --- Two things belong on the same page here. The size of the SaaS management platform category, and the spend data that creates it. Analysts who size this market from the top down get wildly different answers because they disagree about what counts as a vendor. Size it from the waste instead and the number becomes defensible. ## How big is the SaaS management platform market The standalone category sits in the low single digit billions of dollars, growing somewhere in the high teens to mid twenties percent a year. That is a range, not a point estimate, and anyone quoting you three decimal places is selling something. The spread comes from category definition. A narrow definition covers discovery, usage telemetry and licence optimisation: Zylo, Productiv, Torii, Zluri. A wide one folds in procurement and negotiation platforms like Vertice and Spendflo, plus the SaaS modules inside ITAM incumbents such as Flexera and ServiceNow. The wide definition is roughly double the narrow one. This is the same definitional problem that makes [SaaS market forecasts](/research/saas-market-forecasts-reconciled/) disagree by a factor of two, and it is worth reading how those reconcile before you quote any single number in a board deck. Our position: size this one bottom up. Waste is measurable, the addressable estate is countable, and the willingness to pay is a fraction of documented savings. That makes it one of the few software categories where [bottom up sizing](/comparisons/top-down-vs-bottom-up-market-sizing/) beats the analyst top down number by a comfortable margin. **$4,830** Reported annual SaaS spend per employee in large organisations ## Who the vendors are and where they came from Six names cover most live deals, and they arrived from three different directions. The origin matters because it determines the buyer. Zylo and Productiv sell to IT and finance jointly. Vertice and Spendflo sell to finance almost exclusively, and often to a CFO who has never asked IT for an app inventory. Torii and Zluri tend to land with IT operations. That split is the single best predictor of which deal you will win, and it is the same pattern you see across the wider [enterprise SaaS market](/guides/enterprise-saas-market/), where the budget holder determines the roadmap more than the technology does. Adjacency pressure is real. ITAM incumbents have shipped SaaS modules, identity providers have shipped app discovery, and finance platforms have shipped vendor management. A standalone SMP needs a reason to exist beyond a dashboard. Most have picked one: Productiv picked depth of usage telemetry, Vertice picked negotiated outcomes, Torii picked automation. ## What companies actually spend on software Zylo's published index work has put annual SaaS spend near 4,830 dollars per employee. That figure comes from a customer base of large organisations that already suspected they were overspending, so treat it as a ceiling rather than an average. Per employee spend does not scale linearly. It dips in the 200 to 500 headcount band as companies consolidate, then climbs again above 1,000 as departments start buying independently. The dip is real and short lived. | Company size | Typical distinct applications | Rough annual SaaS spend per employee | | --- | --- | --- | | Under 50 employees | 25 to 60 | $2,000 to $3,500 | | 50 to 200 | 60 to 120 | $3,000 to $4,500 | | 200 to 1,000 | 120 to 250 | $3,500 to $5,000 | | 1,000 to 5,000 | 250 to 400 | $4,000 to $5,500 | | Over 5,000 | 350 to 600+ | $4,500 to $6,500 | Source for the ranges: aggregated practitioner reports and published vendor indices, saas-marketing.net estimate. The app counts vary more than the spend because discovery method changes the answer. Count contracts and you get one number. Count anything with a corporate email login and you get triple. Two vendors can both be honest and report app counts that differ by 3x. One counts applications with a signed agreement. The other counts every domain that appeared in an SSO log or an expense feed once in twelve months. Neither is wrong. They answer different questions. ## The unused licence data that funds the whole category This is the number that sells SMPs. Published vendor research from Zylo and Productiv has reported that somewhere between 40 and 55 percent of purchased licences are unused or meaningfully underused. That range is wide because the definition of "used" moves. A licence that saw one login in a quarter is technically used. Productiv's contribution to this argument has been to measure feature level engagement instead, which drops the "genuinely used" figure further. If your definition is weekly active use of a core feature, the dormant share climbs. Even conservative internal audits run by finance teams with no tooling usually surface 20 to 30 percent dormant seats. That is the floor. Below 20 percent, either your estate is unusually well managed or your audit was too shallow. Dormant seats cluster in three places: departed employees who were never deprovisioned, seats bought in a volume tier to hit a discount threshold, and tools bought for a project that ended. The third category is the hardest to reclaim because someone still defends it. ## Shadow IT and duplicate applications Shadow IT did not die with single sign on. It moved. Free tiers, personal card purchases, and the 2024 to 2026 wave of AI tools bought by individual teams all sit outside identity provider visibility by design. Companies that run expense feed discovery alongside SSO discovery routinely find two to three times as many applications as IT had on its inventory. The gap is not evenly distributed. Design, marketing and data teams generate the most unsanctioned purchases, because their tooling changes fastest and their budget authority is often local. Duplication is the more expensive problem. A 1,500 person company will typically be paying for two project management tools, three video tools, two design tools and four note taking products at once. Some of that is legitimate, because Figma and Canva are not competitors in practice. Much of it is not. The security exposure from that sprawl is what pulls the [SaaS security market](/guides/saas-security-market/) into the same buying conversation, and it is increasingly why a CISO signs off on an SMP purchase that finance initiated. Marketing stacks are usually the worst offenders. The tool count inside a single marketing org can exceed thirty, which is one reason the [marketing SaaS market](/guides/marketing-saas-market/) has such a long tail of small vendors with real revenue. ## The ROI math buyers actually run Buyers do not underwrite these purchases on efficiency language. They run a savings multiple. **The SMP business case, as buyers build it** The first year is always the best year. Dormant licences get reclaimed once. Year two savings come from renewal negotiation and from preventing new sprawl, both of which are smaller and harder. Vendors know this, which is why multi year contracts are pushed hard at renewal. An SMP produces a list. A list is not a saving. The programmes that fail are the ones where nobody owns the reclaim workflow, so the dashboard shows 400,000 dollars of identified waste for eighteen months and finance eventually cancels the tool. Assign a named owner with authority to switch things off, or do not buy. ## Why the waste number sets the market ceiling Here is the argument in one line. An SMP can capture a slice of documented waste, and nothing more. If global SaaS spend is in the hundreds of billions and the dormant share is roughly 40 percent, the waste pool is enormous. But buyers only pay a fraction of realised savings, typically 10 to 20 percent of year one recovery, and only the segment of companies large enough to have a real sprawl problem will ever buy. That is roughly organisations above 500 employees, plus fast growing mid market firms with runaway app counts. Run that arithmetic and you get a category in the low billions with a credible path to high single digit billions as mid market adoption deepens. It is a good market. It is not a category defining one, and the growth rate depends on whether procurement suites absorb it first. This is the same structural question that separates [horizontal and vertical SaaS](/comparisons/horizontal-saas-vs-vertical-saas-marketing/) outcomes: horizontal utilities get absorbed, vertical depth survives. For anyone modelling the category properly, the practical path is to build the estimate from published usage data rather than analyst headline figures, then sanity check it against the broader [SaaS market size and growth](/saas-market/) picture. The [research tools](/tools/saas-market-research-tools/) worth using here are the ones that expose methodology, not the ones that hand you a single number. ## What to do next If you are sizing this market for a deck, build bottom up from app counts and dormant licence rates, state your definition of "used" on the same slide, and give a range. If you are buying, count your estate first with two independent sources, because the discovery number is the whole business case. And if you are marketing one of these platforms, publish your methodology with your waste figures. In a category where every vendor quotes a different number, the one that shows its working becomes the citation everybody else uses. For the operational detail on running one of these programmes, start with the [SaaS management platforms](/guides/saas-management-platforms/) guide. ## Frequently asked questions ### How big is the SaaS management platform market? Analyst estimates put the standalone SaaS management platform category in the low single digit billions of dollars, growing in the high teens to mid twenties percent range annually. The spread between estimates is wide because definitions differ. Some counts include procurement and spend management vendors like Vertice and Spendflo, others restrict the category to discovery and licence optimisation tools. ### How much does the average company spend on SaaS per employee? Zylo's SaaS Management Index work has reported figures in the region of 4,800 dollars per employee per year across its customer base. That number skews high because Zylo's customers are large organisations that already suspect they overspend. Smaller companies typically land lower, but per employee spend rises sharply once headcount passes about 500. ### How many SaaS applications does a typical company use? Published vendor research puts small companies in the 30 to 80 application range, mid market firms in the low hundreds, and large enterprises at several hundred distinct applications. Discovery methodology drives most of the variance. Counting anything with a login produces a much larger number than counting anything with a contract. ### What percentage of SaaS licences go unused? Vendor studies from Zylo and Productiv have reported unused or underused licence rates in the 40 to 55 percent range, depending on whether a licence counts as used after one login or after regular weekly activity. Even conservative internal audits usually find 20 to 30 percent of seats dormant, which is where most SMP business cases start. ### Is shadow IT still a real problem in 2026? Yes, and SSO adoption has not solved it. Free tiers, personal credit card purchases and AI tools bought by individual teams sit outside identity provider visibility. Companies that run expense feed discovery alongside SSO discovery typically find two to three times as many applications as IT had on its inventory. ### Do SaaS management platforms actually pay for themselves? Usually in year one, if the estate is over about 150 applications. Below that, a finance analyst with a spreadsheet and a renewal calendar captures most of the savings. Buyers typically underwrite a five to ten times savings multiple on platform fee, and the first year is always the biggest because dormant licences get reclaimed once. ### What is the difference between SaaS management and SaaS spend management? SaaS management platforms discover applications, track usage and optimise licences. SaaS spend management and procurement platforms focus on negotiation, renewal workflow and purchasing influence. The two are converging fast, with Vertice and Spendflo coming from the buying side and Zylo and Productiv from the usage side.