How Software Vendors Structure Pricing - And What Buyers Should Look For
Enterprise software pricing can be surprisingly difficult to understand.
Two vendors may appear to offer similar products yet price them in completely different ways.
One charges per user.
Another charges by usage.
Another bundles features into tiers.
Another combines a platform fee with consumption charges.
And once enterprise negotiations begin, the published price may bear little resemblance to the final commercial agreement.
For buyers, understanding the pricing model matters just as much as understanding the price.
Because the way a vendor charges determines how your costs may change as your organisation grows, usage increases and the contract renews.
Why Software Pricing Is So Complicated
Software vendors are trying to solve several problems at the same time.
They want pricing that:
- Reflects the value customers receive
- Grows as customers grow
- Produces predictable recurring revenue
- Is easy enough to sell
- Protects margins
- Supports different customer sizes
Those objectives do not always align.
That is why enterprise software pricing often evolves into combinations of:
- User licences
- Platform fees
- Usage charges
- Product modules
- Feature tiers
- Minimum commitments
- Volume discounts
The headline number is only the beginning.
Per-User Pricing
One of the most familiar models is per-user or per-seat pricing.
The customer pays based on the number of people licensed to use the platform.
For example:
100 users × $100 per user per month.
This model is easy to understand and relatively predictable.
But it can become expensive as an organisation grows.
What Buyers Should Look For
Ask:
- Do all users need a full licence?
- Are there different user types?
- Can licences be reassigned?
- Is there a minimum seat commitment?
- Can unused seats be reduced at renewal?
- What happens if headcount falls?
A large discount on unused licences is still wasted spend.
Usage-Based Pricing
Usage-based pricing charges according to consumption.
Depending on the product, that may mean:
- API calls
- Data volume
- Transactions
- Compute
- Storage
- Messages
- AI tokens or credits
This can initially look attractive because cost follows usage.
But predictability becomes harder.
What Buyers Should Look For
Understand:
- How usage is measured
- What happens when limits are exceeded
- Whether overage rates are higher
- Whether unused consumption rolls over
- Whether usage can be monitored in real time
- Whether spending can be capped
The key question is not:
What does one unit cost?
It is:
How many units are we realistically likely to consume?
Tiered Pricing
Many software companies bundle capabilities into tiers such as:
- Standard
- Professional
- Enterprise
Higher tiers unlock additional functionality.
This makes products easier to package and sell.
But buyers can sometimes end up upgrading an entire organisation to access one important feature.
What Buyers Should Look For
Identify exactly which capabilities force you into the higher tier.
Ask:
Which features in this package are we actually buying the tier for?
Sometimes the expensive part of the agreement is not the software you need.
It is everything bundled around it.
Module-Based Pricing
Large enterprise platforms often sell multiple modules separately.
For example:
- Core platform
- Analytics
- Security
- AI
- Workflow automation
- Reporting
- Customer service
The initial purchase may cover only part of the broader platform.
Over time, additional modules can significantly increase spend.
What Buyers Should Look For
Before signing, understand:
- Which functionality is included
- Which capabilities require additional modules
- Whether modules are bundled at renewal
- How cross-product discounts work
- Whether removing one module affects pricing on others
The initial contract should not be reviewed in isolation from likely future needs.
Platform Fees
Some enterprise vendors charge a base platform fee before user or consumption costs are added.
The commercial structure might therefore look like:
Platform fee
- users
- modules
- usage
This can make comparisons difficult.
A competitor without a platform fee may appear more expensive per user while still being cheaper overall.
Buyer's Insight
Compare total expected spend, not individual unit prices.
Minimum Commitments
Usage-based vendors often ask customers to commit to a minimum amount of consumption.
This gives the vendor predictable revenue.
For the buyer, however, it creates risk.
If the organisation consumes less than expected, it may still pay for the full commitment.
What Buyers Should Ask
- How was the commitment calculated?
- What happens to unused capacity?
- Can consumption be carried forward?
- Can the commitment be reduced at renewal?
- Can usage be shared across teams or products?
Do not confuse a discounted commitment with guaranteed savings.
The discount only has value if you use what you bought.
Volume Discounts
Enterprise vendors often reduce unit pricing as commitment increases.
For example:
More users may produce a lower price per user.
Higher consumption commitments may produce cheaper unit rates.
Longer contracts may create additional discounts.
This can be beneficial.
But it can also encourage buyers to commit to more than they need.
The Buyer's Question
Instead of asking:
How much more discount can we get?
Ask:
What commitment are we making to earn that discount?
A 25% discount attached to 40% excess capacity is not necessarily a good deal.
Multi-Year Pricing
Vendors often offer better commercial terms for multi-year agreements.
From the vendor's perspective, longer contracts provide:
- Revenue predictability
- Lower renewal risk
- Stronger customer retention
For buyers, multi-year agreements can provide:
- Price certainty
- Better discounts
- Reduced procurement effort
But they also reduce flexibility.
Before accepting a longer term, buyers should understand:
- Price increases
- Exit rights
- Product commitments
- Usage assumptions
- Future business requirements
The longer the contract, the more important those assumptions become.
AI Is Making Pricing Harder
AI products are creating new pricing structures.
Buyers increasingly encounter combinations of:
- User subscriptions
- Tokens
- Credits
- Compute
- API calls
- AI actions
- Automated tasks
The challenge is that usage may be difficult to forecast before deployment.
A pilot may consume very little.
Enterprise adoption may consume significantly more.
Buyer's Insight
When evaluating AI pricing, model multiple usage scenarios.
Do not rely only on pilot consumption.
Ask what costs look like at:
- Current usage
- 2× usage
- 5× usage
- Enterprise-wide adoption
The commercial model should survive success, not just the pilot.
Why Comparing Discounts Can Be Misleading
Buyers frequently ask:
What discount are other customers getting?
That information can be useful.
But discount percentage alone can be misleading.
Consider two contracts.
Vendor A
List price: $1 million
Discount: 30%
Price: $700,000
Vendor B
List price: $800,000
Discount: 10%
Price: $720,000
Vendor A appears to have provided the better discount.
But that does not necessarily make it the better agreement.
The buyer should also compare:
- Included functionality
- Usage rights
- Implementation
- Support
- Contract length
- Renewal protection
- Future price increases
Discount is one variable.
Commercial structure matters more.
The Questions Buyers Should Ask About Pricing
Before comparing vendor proposals, ask each vendor:
- What exactly drives our price?
- Which variable is most likely to make our costs increase?
- What are we committing to that we may not use?
- Which important capabilities cost extra?
- What happens if usage doubles?
- What happens if usage falls?
- What happens at renewal?
- Which discounts disappear after the initial term?
- Are there overage charges?
- Can unused licences or consumption be reduced?
- What costs are not included in the proposal?
If a pricing model cannot be explained clearly, that itself is worth investigating.
Build A Three-Year Pricing Model
Do not evaluate enterprise software based only on year one.
Model at least three years.
Include:
- Subscription costs
- Expected growth
- Usage changes
- Additional modules
- Implementation
- Support
- Renewal increases
This connects pricing directly to Total Cost of Ownership.
A proposal that looks attractive today may become significantly more expensive once growth and renewal economics are included.
The Buyer's Side Take
The most important question in software pricing is not:
What discount did we get?
It is:
What causes our cost to change?
Understand that and you understand the commercial model.
A good software agreement should make it reasonably clear what happens when:
- Your organisation grows
- Usage increases
- Usage decreases
- You add products
- You remove products
- The contract renews
The strongest buyers do not simply negotiate the price.
They negotiate the mechanics behind the price.
Because in enterprise software, that is often where the real cost is hiding.
