Land-and-expand is a phrase everyone uses and few structure for on paper. Whether an enterprise agreement is metered by named users, by usage or workflow volume, or licensed unlimited per site determines how naturally — or how painfully — that account expands over the following three years.
The specific numbers in any given deal are never the point. The structural choice underneath them is a repeatable commercial decision, and it's getting more consequential, not less, as AI reshapes how software gets priced industry-wide.
"As agentic AI takes over tasks traditionally performed by humans, the number of active users engaging with software decreases, rendering seat-based monetization on core SaaS software increasingly challenging."
McKinsey's technology practice is explicit that the shift away from per-seat pricing isn't cosmetic — it's a direct consequence of AI changing who, or what, actually uses the software day to day. Companies that have already moved to consumption or outcome-based pricing are seeing meaningfully higher per-customer revenue than legacy per-seat SKUs.
That's exactly the same structural axis behind named-user licensing, usage/workflow-based metering, and site-unlimited enterprise agreements in life sciences software today — the parameter set isn't a historical artifact of how deals used to get done. It's the live design question every vendor is now renegotiating.
Every enterprise software agreement is metered by something. Which structural parameter gets chosen at signature shapes how the account can grow — and how much friction stands between a point-solution win and true enterprise-wide adoption.
Pricing scales with the number of named individuals granted access — simple to understand, easy to forecast, and familiar to procurement teams.
Expansion path: straightforward but linear — growth requires periodically renegotiating headcount, and the model erodes as AI/automation reduces the number of humans who need a seat at all.
Pricing scales with actual system activity — samples processed, workflows run, records ingested — rather than headcount.
Expansion path: naturally aligned to value delivered and resilient to seat-count compression, but requires more sophisticated usage tracking and forecasting on both sides.
A flat fee per site or location grants unlimited internal use — removing the friction of counting users or transactions entirely.
Expansion path: especially effective for multinational organizations rolling the platform out site by site — expansion becomes a geography conversation, not a re-negotiation.
A discounted year-one price that steps up in years two and three signals confidence in expansion — but only if the step-up is sized to match realistic adoption timelines.
Fixed-price versus milestone-billed implementation fees interact directly with a customer's own budget cycle — getting this wrong stalls a signed deal at kickoff.
Which capabilities ship in the base license versus as a paid add-on determines whether expansion revenue is a natural next conversation or a fresh procurement cycle.
Building the next tier's trigger condition into the contract itself — a user threshold, a usage ceiling, a new site — turns expansion into an operational event, not a re-sell.
A framework for choosing the metering model, ramp structure, and expansion triggers that match how your platform actually gets adopted — built on structuring enterprise agreements across multiple deal shapes and customer types in life sciences software.