Enterprise SaaS Pricing Architecture: Structuring Deals from £20k to £1M+ ACV
Enterprise SaaS requires a fundamentally different pricing approach than self-serve or SMB products. This guide covers how to structure enterprise pricing tiers, negotiate annual contracts with multi-year discounts, navigate procurement processes, and manage complex enterprise MSAs and SOWs.
Enterprise pricing is bespoke, not published. Build ACV tiers by use case, establish negotiation anchors, and use multi-year discounts (10-15% year 2, 15-20% year 3+) to lock in longer commitments. Enterprise deals require MSA and SOW expertise. Discounting has a floor; do not go below 20-30% off list price or you signal weakness.
Enterprise Pricing Is Bespoke, Not Published
Enterprise pricing is never published as a simple list. There is no "Enterprise Plan: £500k per year" on your website. Enterprise pricing is custom, negotiated, and based on value delivered to that specific customer. You might quote Customer A £300k and Customer B £600k for similar use cases, depending on their budget, alternative options, urgency, and negotiating leverage.
This is fundamentally different from SMB pricing, which is published and fixed. The reason is that enterprise procurement is a negotiation, not a transaction. Enterprise buyers have budget constraints, approval processes, and the ability to walk away if your price does not fit their budget. Your job is to find the intersection of your value delivered and their budget.
The starting point for any enterprise negotiation is an anchor. You propose a price based on value delivered, and the buyer responds with their budget or counter-offer. The negotiation moves toward a middle ground. Anchoring high gives you room to negotiate down while hitting your target. Anchoring too high risks losing the deal. Anchoring too low signals weakness and you cannot recover.
Building ACV Tiers and Use Cases
Although pricing is custom, you need internal tiers to guide your sales team. Build tiers by use case: a small enterprise using your product for one team might be tier 1 (£25k to £50k ACV). A mid-size enterprise using it across three departments might be tier 2 (£75k to £150k ACV). A large enterprise with company-wide deployment might be tier 3 (£250k to £500k ACV+).
Each tier should have clear drivers: number of users, number of departments, number of integrations, level of support, customisation required. As you move up tiers, price scales 2-3X, not linearly. A tier 1 customer paying £40k for basic implementation might scale to tier 2 at £120k (3X) when they expand use cases, not to £60k (1.5X). The value delivered scales non-linearly with enterprise size.
Communicate these tiers internally to your sales team so they have anchors. Do not publish them. When a prospect approaches, the sales team estimates which tier they fall into, proposes a number based on that tier, and negotiates from there. This gives consistency while maintaining flexibility.
Multi-Year Discounts and Lock-In
Enterprise deals should be multi-year. Standard is a one-year initial term with renewal options. But you should aggressively incentivise multi-year upfront commitments with discounting. A customer signing a three-year deal should get 10-15% off year 2 and 15-20% off year 3 and beyond.
Example: A customer with list price of £300k per year signs a three-year deal. Year 1 is £300k (no discount, covers your sales effort and implementation). Year 2 is £300k times 0.85 = £255k (15% discount). Year 3 is £300k times 0.80 = £240k (20% discount). Total value over three years is £300k + £255k + £240k = £795k. If paid upfront, that is £795k in year 1 cash. If paid annually, it is £300k in year 1, £255k in year 2, £240k in year 3.
The multi-year discount solves two problems. It gives the customer financial certainty (pricing locked in for three years) and it gives you cash certainty (you know exactly what you will collect from this customer over three years). It also increases switching cost: after the customer has committed three years and is paying you £255k-£300k per year, switching to a competitor becomes less attractive.
Discounting Floor and Negotiation Strategy
Have a discounting floor that you will not breach. Most B2B SaaS companies have a floor of 20-30% off list price. You can offer 20% off year 1 in some situations, but going below that signals that your list price is fake and erodes pricing credibility. If you have a list price of £300k and you are willing to close at £150k (50% off), your real list price is £150k and everyone knows it.
Negotiation strategy should be: start high, negotiate on value, not price. When a prospect says "your price is too high," do not immediately offer a discount. Instead, ask: "What value proposition matters most to your organisation?" If they care about three use cases and you can show that your solution solves all three whereas competitors solve one, justify the premium. If they truly cannot afford you, walk away rather than discount heavily.
If you must discount, use multi-year terms as leverage. "We can move from £300k to £270k (10% off) if you commit to a three-year agreement." This maintains your pricing integrity while accommodating their budget. You also get the benefit of the multi-year lock-in.
The Master Service Agreement and Statements of Work
Enterprise deals have two documents: the Master Service Agreement (MSA) and Statements of Work (SOWs). The MSA is the umbrella contract covering terms, conditions, liability, IP, confidentiality, and other legal/commercial terms. The SOW is the specific statement of what you will deliver, how much it costs, when, and what success looks like.
The MSA is negotiated once and typically carries forward to future SOWs and renewals. Do not reinvent the MSA for every deal. Negotiate it once with the customer, agree on terms, and then use the same MSA for year 2, year 3, and additional SOWs. This dramatically speeds up future renewals.
The SOW is deal-specific and details what you will do, how many seats/users are covered, implementation timeline, training provided, support level, success metrics, and price. The SOW is the contract that moves with each deal and renewal. For a three-year deal, you might have one MSA and three SOWs (one per year, updating users, pricing, and any additions).
Do not try to draft these yourself if you are not experienced. Hire an enterprise contracts attorney to draft templates. The cost (£5,000-£10,000) is trivial compared to the deal sizes and the protection you get from having proper legal documents.
Procurement and Legal Due Diligence
Enterprise procurement is a process. A customer might spend two to three months running procurement and legal diligence before you even begin your sales process. Understand their process: they might require vendor questionnaires, security audits, references, and legal negotiations before approving budget.
Be prepared for this. Have your security documentation ready (SOC 2, penetration test, vulnerability scans). Have a list of reference customers. Have clean corporate documents (articles, insurance, D&O insurance). Do not wait for a customer to request these; proactively provide them during the process. Every day waiting for a document is a day the deal slows down.
Legal negotiations can be lengthy. Customers will want to modify your MSA, add liability caps, require indemnification, and adjust IP terms. Have a lawyer review their requests and recommend positions. Some requests are reasonable (liability caps, indemnification), some are one-sided (requiring you to retain IP they develop), and some are dealbreakers (requiring you to guarantee uptime without penalty provisions).
Know which hills to die on. Do not accept liability above 12 months of fees paid. Do not accept unlimited indemnification. Do accept reasonable security and confidentiality terms. Protect your IP and your liability, but be willing to negotiate on process and timelines.
Expansion and Upsell in Enterprise
Enterprise is not a one-time sale. After the initial contract, there is room to expand. A customer might have started with 500 users and grown to 1,500 users. A customer might have implemented your product in one department and wants to expand to a second department. This expansion is the engine of enterprise NRR and is typically negotiated as a mid-contract expansion or at renewal.
Create a formal process for expansion. At six months into a one-year contract, proactively reach out to ask how the deployment is going and if they want to expand. Propose an expansion SOW: additional users, additional departments, or additional modules. Price it at the same effective per-unit rate, not at a discount. If the customer adds 500 users to their 500-user deployment, that is a straightforward line item addition.
Expansion is lower friction than new sales because the customer already knows your product works. They have already gone through implementation and training. Adding users or departments is additive. Many enterprise deals show 30-50% expansion by year 2, driven by successful initial implementation and growing org adoption.
Real-World Examples and Benchmarks
Salesforce sells enterprise at £500k to £5M+ per year depending on deployment size, modules, and customisation. A global enterprise with 10,000 users across multiple modules might pay £3M per year. A regional mid-market company with 500 users might pay £500k per year. Price scales with value delivered and org size, not linearly.
ServiceNow sells enterprise software with similar logic. Initial deployments for a single department might be £1M per year. Expanded deployments company-wide might be £10M+ per year. Multi-year discounts lock customers in and improve unit economics.
Datadog sells to enterprises at £500k to £2M+ per year depending on infrastructure size, data volume, and module adoption. A bank running 50,000 containers might pay £2M per year. A smaller company running 5,000 containers might pay £200k per year. Price follows infrastructure footprint and complexity.