.png)
Frameworks, core principles and top case studies for SaaS pricing, learnt and refined over 28+ years of SaaS-monetization experience.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
How Are SaaS Management Platforms Priced for Enterprise Procurement
Enterprise buyers rarely procure a SaaS management platform because they need another dashboard. They buy one because hundreds of software contracts have become hard to govern: employees join and leave, business units buy their own tools, renewal dates sit in scattered systems, and licence counts drift away from actual use. The procurement problem is therefore unusually recursive. A company buys software to control its software spend, yet the platform doing the controlling can itself introduce opaque tiers, true-ups, add-ons and renewal exposure.
The market in 2026 makes that tension visible. BetterCloud says its price reflects licence count, connected applications, modules and add-ons. Torii ties licensing directly to employee count and true-ups. Josys uses organisation size, users and governance requirements. Cledara exposes application-count thresholds. Zylo and CloudEagle show clear packages but keep the billable unit and rate behind a sales conversation. Those are materially different ways to turn the same broad job - discovering, governing and optimising SaaS - into an invoice.
Monetizely's position is that enterprise SaaS management should be priced primarily on an annual band of active employees or managed identities. Core discovery, integrations and spend visibility should sit inside that price, while genuinely separate modules may carry fixed fees. Buyers should resist contracts in which app count, total SaaS spend, realised savings or loosely defined scope becomes a second uncapped meter.
Active employee count gives buyers the cleanest primary meter
The pricing question becomes clearer when we use Monetizely's 5-Step Pricing Framework. The framework starts with Goals & Segments, because a procurement-led enterprise has different needs from a small IT team. Those choices determine Positioning & Packaging, meaning which capabilities belong together and which deserve separate tiers. The third step, Pricing Metric, asks what unit should make the bill rise as customer value rises. Rate-Setting, or Price Points, determines how much the vendor charges per unit or package. Operationalization then governs what happens in the real contract and billing process: measurement, discounts, true-ups, renewal rules and sales execution. The sequence matters here because a seemingly reasonable metric can become a poor enterprise contract when packaging or billing rules multiply its effects. The broader discipline behind that approach also runs through Monetizely's work on software monetisation, including Monetizing Agentic AI. The five steps and their sequence are described by Monetizely as of 13 August 2026.
Three of the clearest public examples point towards a human-count meter. BetterCloud says, on its current pricing page accessed 13 August 2026, that price reflects licence count alongside connected apps, modules and add-ons. Torii explicitly states that licensing is tied to total employees, falling back to users when an organisation has not configured its employee definition. Josys says its automated identity-governance pricing is customised using organisation size, number of users and governance requirements.
That pattern makes economic sense for an enterprise SMP. More employees usually mean more identities to discover, accounts to reconcile, licences to analyse and joiner-mover-leaver events to govern. The metric is also independently auditable against the HR system or identity provider. Torii goes so far as to warn that failing to define employees correctly can cause billing to default to the larger user population.
Application count is weaker as the primary measure. Cledara's current published packages make the limitation concrete: Basic covers up to 20 software applications and Premium up to 75. Yet one application might be a low-cost niche tool while another might represent millions of pounds of enterprise spend and thousands of users. App count tracks administrative breadth, but it does not consistently track either workload or value.
The vendor landscape shows how far commercial structures already diverge.
| Vendor | Published charging logic as of 13 Aug 2026 | Dominant pricing metric | What enterprise procurement should infer |
|---|---|---|---|
| BetterCloud | Price reflects licence count, connected apps, selected modules and add-ons; volume and term discounts may apply. | Licence count, with secondary scope variables | The human-count base is sensible, but four price inputs can make expansion harder to forecast. |
| Torii | Licensing is tied to employees; users become the fallback when employee parameters are undefined. | Employees | Strong primary meter, but its definition and true-up mechanics become central contract terms. |
| Josys | Pricing uses organisation size, number of users and governance requirements; standard SaaS Management is quote-based. | Users / organisation size | Human scale is visible, although “governance requirements” introduces another negotiated variable. |
| Cledara | Published packages cap managed applications at 20 and 75; optional Spend Optimization and IT Management modules are each £1,500 a year. | Managed applications in published tiers | Transparent thresholds help budgeting, but app growth can trigger package pressure unrelated to employee growth. |
| Zylo | Core, Premium and Enterprise packages are public; Enterprise adds multi-business-unit, M&A and sandbox capabilities, but the page directs buyers to request a quote. | Not publicly disclosed | The package is visible while the unit economics remain hidden until sales engagement. |
| CloudEagle.ai | SaaS Management, SaaS Procurement, Identity Governance, Security and AI Governance are separate modules; its public pricing page routes buyers to a personalised demo rather than publishing a unit rate. | Not publicly disclosed | Buyers can see the module boundaries but cannot forecast marginal expansion from the public page alone. |
The pattern matters more than any one vendor. Employee count is the strongest primary meter in this category, but only when app discovery and ordinary integrations do not become an uncontrolled second meter.
Packaging is where enterprise SMP quotes begin to diverge even before a rate is discussed. BetterCloud combines User Automation, Spend Optimization and Workspace Management for Google in its broader platform while also allowing individual modules. Zylo moves pricing benchmarks, IAM actions, ITSM automation and cost allocation into Premium, then reserves multi-business-unit and M&A support for Enterprise. CloudEagle visibly separates SaaS Management from SaaS Procurement, Identity Governance and Security. Those structures were current on 13 August 2026.
For procurement, feature separation becomes important when the buyer needs several jobs at once. A platform purchased to discover unused licences may later need procurement workflows, benchmarking, onboarding automation or governance. A low starting quote can therefore be less informative than the price of the package the enterprise will need in year three.
Monetizely's framework makes the failure modes easier to diagnose. Packaging, pricing metric and operationalization have to work together rather than merely look reasonable in isolation.
| Vendor | Packaging diagnosis | Pricing-metric diagnosis | Operationalization diagnosis |
|---|---|---|---|
| BetterCloud | Modular entry lowers the barrier to adoption, but connected capabilities can expand the paid scope. | Licence count has a sound base; connected apps and add-ons can create multiple scaling axes. | Custom quotes and term discounts mean the order form needs to state the marginal rate for every expansion path. |
| Torii | The core billing model remains easier to understand than a heavily modular structure. | Employee count is the strongest public metric in the group. | The weakness appears at true-up: additions to an annual allocation can be billed monthly at the non-discounted employee price. |
| Josys | A broad SaaS Management package reduces visible feature fragmentation. | User count is sensible, while “governance requirements” makes part of the metric less objective. | Quote-only rate-setting reduces external price transparency. |
| Cledara | App caps and separately priced modules make upgrade triggers unusually visible. | App count is simple to measure but weakly connected to the economic value of each application. | The model is transparent enough to model, although step changes and add-ons can accumulate. |
| Zylo | Core, Premium and Enterprise create a clear maturity ladder. | No public charging unit means the buyer cannot test how cost scales before obtaining a quote. | Request-a-quote pricing makes three-year marginal economics a negotiation task rather than published product behaviour. |
| CloudEagle.ai | Distinct management, procurement, governance and security modules map well to separate buying needs. | The public page does not disclose the billable unit. | Buyers need sales engagement before they can model incremental cost across modules. |
Our view is not that modules are inherently poor packaging. A procurement advisory service or deep identity-governance capability can justify a separate fee because the work, buyers and cost structure differ from basic SaaS discovery. Problems begin when capabilities required to produce the promised core outcome are split across packages solely to create upgrade pressure.
The same reasoning rules out percentage-of-savings as the primary software meter. A platform that helps remove £2 million of redundant spend should certainly demonstrate that value. Charging a recurring percentage of the saving, however, means the supplier captures more precisely when the customer's software estate becomes leaner. For a persistent system of record, an auditable employee base plus fixed module fees gives procurement cleaner incentives.
Enterprise buyers often spend most of a negotiation on the opening discount. Operationalization deserves at least as much attention.
Torii provides a useful platform-specific example. Its current support documentation says an annual customer with 250 employees that rises to 290 before the next monthly cycle is true-upped for the additional 40 employees at the non-discounted employee price. The same documentation warns that an incorrectly configured employee definition can default billing to all users instead.
Cledara provides a different form of conditional pricing. Its pricing page, accessed 13 August 2026, states that customers seeking its free Get Started package must pay for 10 applications through Cledara virtual cards in the first month; failing the condition produces a £100 monthly charge.
The wider SaaS portfolio shows why an SMP buyer should care so much about renewal mechanics. The platforms being managed can reprice materially at renewal, which makes accurate contract records, notice periods and scenario modelling part of the SMP's economic value.
| Named pricing event | Documented figure | Procurement lesson |
|---|---|---|
| Torii annual true-up, current 13 Aug 2026 | Example rises from 250 to 290 employees; the additional 40 are billed at the non-discounted employee rate. | A discounted annual commitment can still contain a higher marginal rate. |
| Cledara package condition, current 13 Aug 2026 | Failure to meet its stated virtual-card condition produces a £100/month charge. | Commercial conditions outside the headline subscription can alter effective price. |
| GitLab Premium, effective 3 Apr 2023 | List price rose from $19 to $29 per user per month, a 52.6% increase; existing customers received a temporary $24 transition price. | Renewal pricing can overwhelm the value of a previously negotiated seat discount. |
| Salesforce Enterprise and Unlimited, effective 1 Aug 2025 | List prices for specified Sales Cloud, Service Cloud, Field Service and industry editions rose by an average of 6%. | A moderate percentage becomes material when applied to a large installed base. |
| Slack Business+, announced Jun 2025 | Annual-equivalent Business+ pricing rose from $12.50 to $15 per user per month, a 20% increase, alongside additional AI and Salesforce capabilities. | New bundled value can still raise the baseline for customers whose usage has not changed. |
| Microsoft 365, effective 1 Jul 2026 | Microsoft 365 E3 with Teams rose from $36 to $39 per user per month, while F1 rose from $2.25 to $3, or 33%. | Portfolio-level repricing can create very different exposure by employee population and SKU mix. |
These are not equivalent controversies, nor do they need to be. For procurement, the common point is simpler: the next invoice can move because the rate changed, the billable population changed, the package changed or the billing rule changed. A useful SMP contract should reduce those sources of surprise in its own pricing rather than reproduce them.
Procurement teams frequently benchmark a vendor's Year One annual contract value and stop there. That approach misses how different meters respond to growth.
Consider an enterprise beginning with 5,000 active employees and 500 managed applications. Headcount grows 8% a year while the app estate grows 12%. By holding the first-year software cost at $180,000 across three different structures, we can isolate how the chosen meter changes later spend.
The exercise does not prove that one commercial offer will always be cheaper. It shows something more useful: the meter determines which part of the enterprise's future becomes the vendor's expansion engine.
App counts can grow without proportional increases in business value. Headcount can also jump after an acquisition, but procurement can verify it against an authoritative system and negotiate bands for expected changes. A fixed fee produces the greatest budget stability, although it gives the supplier little automatic participation in customer growth and will often be recovered through renewal increases.
Our preferred architecture therefore keeps active employees or managed identities as the primary meter, then uses fixed module fees for materially separate products. The contract should turn normal employee growth into agreed bands rather than a stream of monthly surprises.
Rate-setting comes after that choice. A buyer saving 20% on the unit rate but accepting two uncontrolled secondary metrics has not necessarily negotiated a lower three-year cost.
A strong order form converts variable demand into bounded exposure
The enterprise negotiation should begin with a billing schedule, not with a discount request. Every scenario that can change the invoice should be written down before the buyer compares headline prices.
The negotiation checklist we would use is:
A long checklist may look more demanding than asking for “25% off”. In practice, it does the opposite. Once the buyer controls the unit definitions and expansion rules, discounts become comparable because the denominator has stopped moving.
The strongest order forms also distinguish discovery from paid management. An SMP should be encouraged to find more shadow applications. Charging materially more simply because its discovery engine succeeded would create the wrong incentive. Unlimited discovery is therefore a sensible part of core enterprise packaging even when premium direct integrations or workflow modules remain separately priced.
Enterprise procurement should standardise the buying architecture before negotiating the vendor
The SaaS management category is mature enough that buyers no longer need to accept “custom pricing” as a complete commercial explanation. BetterCloud already discloses its pricing inputs, Torii discloses its employee-based mechanics in unusual detail, Josys identifies users and governance requirements, and Cledara publishes application thresholds and module fees. Zylo and CloudEagle show the other end of the spectrum, where packaging is public but unit economics remain quote-led.
None of those vendors should be allowed to define the comparison unit for the buyer. Procurement should create its own demand curve first: employee population, growth, application estate, required modules, acquisition scenario and target term. Every shortlisted supplier then prices exactly that curve.
Monetizely's position for 2026 is clear: the best enterprise SMP agreement uses active employees or managed identities as its primary meter, annual growth bands rather than punitive monthly true-ups, unlimited ordinary discovery, and fixed prices for genuinely separate modules. The supplier should earn expansion when the customer's managed population grows, not because its own product discovered more apps or because procurement successfully reduced SaaS waste.
Four actions follow from that position:
Choose the platform's institutional job before choosing the platform. Decide whether the company primarily needs an IT governance system of record, a finance-led spend-control layer or an outsourced procurement capability. Paying one vendor for all three without making that decision first creates package bloat rather than integration value.
Make every finalist price the same three-year operating scenario. Commercial evaluation should use a common employee curve, app curve and module roadmap rather than each vendor's preferred quote format. A lower Year One ACV should not win if its chosen meter produces materially higher expansion later.
Treat portability as part of pricing power. Contract records, usage history, renewal data, application inventory and entitlement data should be exportable in usable formats. An SMP becomes harder to reprice or replace when the buyer's own software inventory is trapped inside it.
Measure the platform on controlled spend, not vendor-attributed “savings”. Finance should track avoided renewals, reclaimed licences and prevented overbuying independently, but software fees should remain separate from those figures. Procurement needs the supplier motivated to reveal waste even when doing so shrinks the underlying SaaS estate.
Assumptions
The three-year TCO exhibit models a 5,000-employee organisation with 8% annual employee growth and 500 managed applications growing 12% annually. The employee, application and fixed-module rates are modelling inputs rather than vendor quotes; the table excludes implementation, taxes, foreign-exchange effects and negotiated volume discounts. All vendor pricing descriptions reflect public sources accessed on 13 August 2026 unless an earlier effective date is stated.
Footnotes
https://www.amazon.com/Monetizing-Agentic-AI-Handbook-Transformation/dp/B0H7Z13VKJ/
https://www.getmonetizely.com/blogs/how-do-companies-decide-on-their-pricing-model
https://www.bettercloud.com/pricing/
https://support.toriihq.com/hc/en-us/articles/22291596956955-Subscription-Management
https://www.josys.com/pricing
https://www.cledara.com/pricing
https://zylo.com/pricing
https://www.cloudeagle.ai/pricing
https://www.microsoft.com/en-us/licensing/news/2026-M365-Packaging-Pricing-Updates
https://www.salesforce.com/news/stories/pricing-update-2025/
https://about.gitlab.com/blog/gitlab-premium-update/
https://slack.com/blog/news/june-2025-pricing-and-packaging-announcement