Negotiating with AWS: How Enterprise Teams Cut Cloud Costs Before They Compound

AWS is one of the most under-negotiated enterprise vendors in the market.

That sounds surprising. AWS is often one of the largest technology suppliers in an enterprise portfolio, with annual spend measured in millions, or tens of millions. Yet many organizations approach AWS as if the only available levers are architectural optimization, Savings Plans, and Reserved Instances.

Those tools matter. They are not the whole negotiation.

AWS spend grows organically through consumption rather than seats. New accounts appear. Workloads move into production. Data volumes increase. Development environments multiply. Business units adopt services independently. By the time finance sees the full picture, the organization may already have a substantial AWS run rate, and limited visibility into the commitments supporting it.

That is precisely when a large cloud bill becomes a negotiation opportunity.

The goal is not simply to obtain a larger headline discount. It is to build a commercial structure that aligns with actual consumption, protects flexibility, reduces commitment risk, and preserves leverage for the next renewal.

Why AWS negotiations work differently from SaaS negotiations

Seat-based SaaS contracts usually have a visible commercial unit: users, licenses, modules, or transactions. AWS is different. The bill is a portfolio of variable consumption lines.

AWS pricing can include:

  • On-Demand usage
  • Savings Plans
  • Reserved Instances
  • Data transfer and egress
  • Storage and requests
  • Managed database consumption
  • Support fees
  • AWS Marketplace purchases
  • Promotional credits
  • Migration funding
  • Enterprise-level private pricing

That creates two common mistakes.

First, teams benchmark the wrong number. They compare the total invoice to public list price without normalizing usage, regions, service mix, pricing model, and credits.

Second, teams negotiate the wrong commitment. They accept a spend target based on an optimistic cloud roadmap rather than a defensible forecast of eligible consumption.

In a seat-based negotiation, unused licenses are visible. In AWS, unused commitment can be buried inside a complicated consumption model and discovered only after the organization has already signed.

The AWS commercial landscape: what can actually be negotiated?

On-Demand pricing

On-Demand is the most flexible AWS pricing model, but generally the least economical for stable workloads. It is also the baseline against which many other discounts are presented.

On-Demand pricing is useful as a reference point, not as a complete benchmark. The real question is:

What effective rate is the enterprise paying for its actual service mix after all discounts, credits, commitments, and exclusions?

Savings Plans

Savings Plans provide discounted rates in exchange for a one- or three-year commitment to a consistent level of eligible compute spend.

Depending on the type, they may apply across services such as:

  • Amazon EC2
  • AWS Fargate
  • AWS Lambda
  • Selected database workloads

The tradeoff is flexibility versus discount depth. A Compute Savings Plan can provide broader portability across eligible compute, while an EC2 Instance Savings Plan may offer stronger economics with more constrained coverage.

AWS provides public documentation on how Savings Plans work, but the discount is not automatically a substitute for enterprise negotiation. Savings Plans typically do not address:

  • Data transfer out
  • AWS Support fees
  • Most Marketplace software fees
  • Broader enterprise commitment risk
  • Contractual protections around future services

Review the official AWS Savings Plans documentation before modeling a proposal.

Reserved Instances

Reserved Instances can reduce the cost of predictable EC2 and database usage, usually in exchange for a defined configuration and term.

They can be attractive when workloads are stable. They can also create avoidable lock-in when a business is changing instance families, regions, operating systems, or deployment patterns.

The right question is not “What is the maximum discount?” It is:

How much of this workload can the business confidently call stable for the full commitment term?

AWS explains the mechanics of Reserved Instances here. Your negotiation should go further by testing whether the commitment is operationally realistic.

EDPs and Private Pricing Agreements

Large AWS customers may negotiate an Enterprise Discount Program, often referred to in current market discussions as a Private Pricing Agreement or PPA.

The basic structure is straightforward:

  1. The customer commits to a minimum level of eligible AWS consumption.
  2. AWS provides a negotiated discount across defined eligible usage.
  3. The agreement runs for a set term, commonly one to five years.
  4. The customer must manage its usage carefully to avoid falling short.

AWS does not publish a universal public discount schedule for EDPs or PPAs. Rates depend on factors such as:

  • Annual committed spend
  • Total term value
  • Current run rate
  • Forecast growth
  • Service mix
  • Region and account structure
  • Competitive alternatives
  • Migration or modernization plans
  • AWS Marketplace participation
  • Timing and internal AWS priorities

Industry-observed ranges are directional rather than official. As a rough negotiating reference, enterprise proposals may fall into bands such as:

Annual commitment Directional observed discount range*
$1M–$5M 5%–8%
$5M–$10M 8%–12%
$10M–$25M 10%–15%
$25M–$50M 14%–19%
$50M+ 17%–23%

*These are market observations, not AWS-published tiers or guaranteed outcomes. A discount is meaningful only when you understand exactly which services, charges, accounts, and commitment calculations it covers.

Do not negotiate on the headline percentage alone. Ask AWS to define:

  • Eligible services
  • Excluded services
  • Treatment of new AWS services
  • Treatment of Marketplace spend
  • Treatment of support charges
  • Credit application order
  • Account and region portability
  • Ramp mechanics
  • Shortfall consequences
  • True-up and true-forward provisions
  • Renewal and repricing rights

Flat-design illustration showing enterprise cloud spend benchmarking with normalized rates, usage bars, and a benchmark line

The growth commitment trap

The most dangerous AWS commitment is not necessarily the one with the lowest discount. It is the one based on a forecast that the business cannot reliably achieve.

AWS teams may present a larger commitment as a way to unlock better economics. The logic can be compelling:

  • The business is migrating workloads.
  • AI and analytics usage will grow.
  • New regions are planned.
  • More business units will consolidate onto AWS.
  • A modernization program will increase consumption.

Some of those assumptions may be correct. The problem is that a forecast is not the same as committed usage.

If actual consumption falls below the commitment, several outcomes are possible depending on the agreement:

  • The customer receives less economic value than expected.
  • Unused commitment may expire.
  • The customer may need to accelerate migrations or shift workloads.
  • Finance may face a true-up or shortfall obligation.
  • The customer may have less leverage at renewal because it appears to have underperformed against its promise.

A strong AWS negotiation separates three numbers:

  1. Current run rate: what the company is consuming today.
  2. Committed base: what the company can defend with high confidence.
  3. Strategic upside: what may happen if planned migrations and growth materialize.

Only the first two should form the foundation of a hard commitment. Strategic upside should be rewarded through ramps, expansion rights, reopener clauses, or incremental discounts, not automatically converted into a fixed liability.

Committed spend, true-ups, and unused commitment liability

Before signing, model the agreement month by month.

At a minimum, calculate:

  • Expected AWS usage by service
  • Eligible versus excluded spend
  • Existing Savings Plans and Reserved Instances
  • Marketplace spend
  • Credits and expiration dates
  • Support fees
  • Migration-related costs
  • Seasonality
  • Business-unit allocations
  • Downside and upside scenarios

Then test three cases:

Base case

The organization follows its current migration and growth plan.

Downside case

Migration is delayed, a major workload remains on-premises, or optimization reduces consumption.

Upside case

AI, data, or application workloads grow faster than expected.

The agreement should not be economically attractive only in the upside case.

Ask for mechanisms that reduce unused commitment liability, including:

  • A lower first-year commitment
  • Annual ramps rather than a flat commitment
  • Carry-forward rights
  • Reallocation across accounts and regions
  • Broader eligible-service coverage
  • The ability to apply certain Marketplace purchases
  • A formal review if consumption falls materially
  • No automatic conversion of a shortfall into a new long-term commitment
  • Clear treatment of credits when calculating commitment attainment

Flat-design illustration of the enterprise cloud growth commitment trap, with usage falling below a commitment threshold

Use AWS Marketplace, credits, and MAP as negotiation levers

AWS Marketplace can be commercially important in two ways.

First, Marketplace may be part of the broader enterprise cloud commitment. If your organization already purchases significant third-party software through AWS Marketplace, ask whether that spend can contribute to commitment attainment. Do not assume it qualifies. Get the treatment documented.

Second, Marketplace can provide a procurement path for third-party software, including negotiated private offers. AWS explains the mechanics of Marketplace private offers.

Credits are another lever, but they should never be treated as equivalent to a permanent price reduction.

Separate:

  • AWS promotional credits
  • Migration credits
  • Marketplace-related credits
  • Partner-funded incentives
  • MAP funding
  • Service-specific discounts
  • Contractual PPA discounts

For migration programs, AWS’s Migration Acceleration Program terms should be reviewed carefully. MAP may support migration and modernization activities through funding or credits, but eligibility, included services, timing, and exclusions matter. For example, credits may not cover all data transfer costs or third-party software charges.

Negotiate the value of credits as part of the total economic package, while keeping the underlying price and commitment structure transparent.

Data egress: negotiate it before you need it

Data egress is often treated as an unavoidable technical cost. In a negotiation, it is also a portability and concentration-risk issue.

Your AWS analysis should distinguish between:

  • Routine operational egress
  • Cross-region replication
  • Internet delivery
  • Data movement during migration
  • Exit-related data transfer

The EU Data Act is changing the discussion. The European Commission states that switching charges, including switching-related data egress, must be eliminated from 12 January 2027, with a transitional cost-based approach before then. The official European Commission explanation of the Data Act provides the relevant context.

That does not mean all ordinary AWS outbound data transfer becomes free. Day-to-day operational egress remains a separate commercial issue.

For a multinational enterprise, negotiate:

  • A clear definition of switching-related egress
  • Data export assistance
  • Migration support obligations
  • Advance notice requirements
  • Portability of data and metadata
  • Treatment of egress outside the EU
  • No contractual language that defeats applicable regulatory rights

Support fees are negotiable too

AWS Enterprise Support is generally calculated as a percentage of monthly AWS charges, subject to minimum fees and tiered rates. At large spend levels, even a modest reduction in the effective support rate can produce meaningful savings.

Ask AWS to clarify:

  • The exact fee base
  • Whether credits reduce the support calculation
  • Whether Marketplace charges are included
  • Whether support fees increase automatically as usage grows
  • Minimum monthly charges
  • Enterprise Support versus other support tiers
  • Technical Account Manager coverage
  • Service-level commitments
  • Response-time remedies

Do not accept support as an automatic percentage of every dollar on the invoice without testing the calculation. Support is a distinct commercial line and should be benchmarked separately. Review AWS’s current Support pricing directly, then negotiate the enterprise-specific application.

How to benchmark AWS spend properly

You cannot benchmark AWS effectively by asking whether you received “20% off list price.”

That number may exclude the services where your spend is concentrated. It may also combine different pricing mechanisms and obscure the cost of commitment risk.

A useful AWS benchmark normalizes:

  • Service and SKU
  • Region
  • Usage volume
  • Instance family
  • Operating system
  • Pricing model
  • On-Demand equivalent
  • Effective unit rate
  • Discount off On-Demand
  • Savings Plan or Reserved Instance coverage
  • PPA/EDP discount
  • Credits
  • Support fees
  • Data transfer
  • Marketplace charges
  • Term length and commitment

Track at least three measures:

Effective discount rate

The total discount against the relevant On-Demand baseline.

Effective unit rate

The actual price paid per unit of compute, storage, request, transfer, or database capacity.

Net economic rate

The cost after credits, funding, support, and commitment liabilities are included.

This is where Right Price Benchmarking™ adds value. Benchmarking should reveal not just whether the discount looks attractive, but whether the total structure is commercially fair.

The AWS negotiation playbook

1. Start early

Begin at least six to nine months before a major renewal, PPA, or commitment decision. AWS has more flexibility when the customer has time to create alternatives and does not appear trapped by an expiration date.

2. Build an internal fact base

Bring together:

  • CIO or CTO
  • CFO or finance leader
  • Procurement
  • Cloud economics or FinOps
  • Enterprise architecture
  • Legal
  • Business-unit owners

Agree on the target architecture, migration timetable, acceptable commitment, walk-away position, and priority terms before engaging AWS.

3. Build competitive pressure

Azure and Google Cloud do not need to replace AWS entirely to create leverage. A credible alternative may include:

  • A workload migration
  • A regional deployment
  • A data and analytics platform
  • A disaster recovery environment
  • A new AI workload
  • A dual-cloud architecture
  • A competitive benchmark

The objective is not to threaten a migration the company cannot execute. It is to demonstrate that AWS is competing for future workload allocation.

4. Use timing deliberately

AWS’s fiscal calendar, quarter-end priorities, renewal windows, migration milestones, and internal account planning cycles can affect responsiveness.

Do not wait until AWS presents its final proposal. Establish your economic requirements early, then create a structured process with multiple proposal rounds.

5. Negotiate the complete package

Ask for more than a discount:

  • Better PPA or EDP economics
  • A defensible ramp
  • Carry-forward rights
  • Broader eligible spend
  • Marketplace treatment
  • Credits and MAP funding
  • Reduced support fees
  • Egress protections
  • New-service coverage
  • Renewal caps
  • Exit and portability language
  • Governance and reporting rights

AWS contract traps to review

Before signing, specifically test for:

  • Auto-renewal: Does the agreement renew automatically, and how much notice is required to prevent it?
  • Term escalators: Can the commitment or support fee increase during the term?
  • Service-level carve-outs: Are critical services excluded from meaningful remedies?
  • True-forward language: Can a shortfall or added usage create a higher future commitment?
  • Repricing risk: Can AWS reprice new services or move them outside the negotiated discount?
  • Credit expiration: Do credits expire before planned workloads go live?
  • Account restrictions: Can spend move between accounts, regions, and subsidiaries?
  • Marketplace exclusions: Does Marketplace spend count toward the commitment?
  • Support calculation: Are support fees calculated on gross or discounted usage?
  • Change-in-control language: What happens after a merger, divestiture, or acquisition?
  • Exit costs: What data, assistance, and egress obligations apply when workloads move?

Flat-design illustration of an enterprise cloud contract risk review showing auto-renewal, escalators, true-forward, carve-outs, and an exit path

Key takeaways for CIOs, CFOs, and procurement teams

  • AWS is not simply a usage bill. It is a portfolio of pricing models, commitments, credits, support charges, and contractual risks.
  • The largest discount is not always the best deal if it requires an unrealistic commitment.
  • EDPs and PPAs should be negotiated around eligible spend, flexibility, shortfall protection, and future-service treatment, not just the headline percentage.
  • Savings Plans and Reserved Instances optimize specific workloads. They do not replace enterprise-level negotiation.
  • Marketplace, MAP, credits, support fees, and egress can materially change the total economics.
  • Benchmark effective unit rates and net cost, not just “discount off list.”
  • Competitive pressure from Azure and Google Cloud is useful only when it is credible.
  • Contract language determines whether savings survive after the signature.

Frequently asked questions

How much discount can an enterprise get from AWS?

There is no universal public AWS discount table. Directional market ranges may vary from single digits for smaller commitments to the high teens or low twenties for very large, well-structured commitments. The actual result depends on spend, term, service mix, growth, competition, and negotiation timing.

Should we commit to all projected AWS growth?

Usually not. Separate current run rate, defensible committed spend, and strategic upside. Use ramps, expansion rights, and review mechanisms to capture upside without turning an uncertain forecast into a fixed liability.

Do Savings Plans replace an AWS EDP or PPA?

No. Savings Plans address eligible compute consumption. An EDP or PPA may provide broader enterprise pricing, but its scope and exclusions must be negotiated. The two mechanisms can coexist.

Can AWS Marketplace spend count toward an enterprise commitment?

Sometimes, depending on the agreement and eligible products. Never rely on a verbal assurance. Require the treatment of Marketplace spend to be stated clearly in the commercial documents.

Is AWS egress now free?

Not generally. Ordinary operational egress remains a cost category. Switching-related charges are subject to evolving regulatory requirements, including the EU Data Act, and AWS has separate policies and eligibility conditions for migration-related transfers.

When should we begin an AWS negotiation?

For a major renewal or enterprise commitment, begin six to nine months ahead where possible. Earlier preparation creates room for benchmarking, competitive pressure, internal alignment, and contract review.

Negotiate AWS before the commitment becomes the constraint

AWS spend compounds quietly. A small pricing gap across thousands of usage lines becomes a major financial issue when consumption grows every month.

The answer is not to avoid cloud commitments altogether. It is to make commitments that reflect reality, reward growth without overpaying for it, and preserve options when the roadmap changes.

The Negotiator Guru is an impartial negotiation firm. We do not accept vendor referral fees, and we operate discreetly as an extension of your team. We have delivered $1.05 billion in total cost impact globally, with average savings of 37% per deal. If we cannot identify at least 10% savings, we do not take the deal.

For a pending AWS negotiation, we can help with:

AWS may control the pricing model. Your team can still control the negotiation.

More resources

From Fortune 500 giants to fast-growing innovators, TNG has helped clients save 20% – 40%+ on enterprise software contracts — even when they thought it was impossible

The truth about Salesforce Enterprise License Agreements (SELA)...is it right for you?

We’ve found that the average savings potential for a company switching from a Salesforce Enterprise License Agreement (SELA) to a standard Salesforce Subscription Agreement is 41.3%. ​

Yet many large enterprises still honor their SELA agreements simply “because we’ve always had one.” Subsequently, these companies have a difficult time benchmarking the value they’re extracting from a SELA vs any other contracting method. ​

While Salesforce will present these agreements in a way that may seem extremely advantageous to the customer, the truth is they’re rarely a good fit.In this article we are going to explain:

  • What is a SELA Agreement?
  • How SELA’s looked in the early days of Salesforce
  • How present day SELA’s have changed
  • Why SELA Agreements are a bad idea for most companies
    • Problem 1: SELA caps are built off of your current needs
    • Problem 2: SELA agreements are manipulated by Salesforce’s changing product line
    • Problem 3: You are paying 41.3% more than you should be with a SELA Agreement
  • When SELA’s work
  • When SELA’s don’t work
  • Why “you don’t have to manage it” rarely justifies a SELA
  • What to do if you have a SELA

What is a SELA Agreement?

A SELA Agreement is a Salesforce Enterprise License Agreement.

​What is the difference between a Salesforce Enterprise License Agreement (SELA) and a Salesforce Subscription agreement?

​A Salesforce Enterprise License Agreement (SELA) agreement is different from a Salesforce Subscription Agreement in one key way. A SELA is meant to provide “Unlimited Access” to the platform, while a standard Salesforce Subscription Agreement includes set prices for a set number of products.

Yet while SELA began as an “Unlimited Access” promise, that is not quite what SELA agreements look like today.

To understand SELA’s and why your company probably doesn’t need one, it’s helpful to understand the history of SELA’s and how they may have looked when your company originally signed one.

How SELA’s looked in the early days of Salesforce

​In the early days of Salesforce, there was a massive focus on market penetration. Like any typical SaaS company, all they cared about was volume.

In the early days of Salesforce, the CRM market was extremely fragmented with small players and disparate homegrown solutions. Arguably, at the beginning, the largest competitor to Salesforce was Microsoft Excel. As a result, Salesforce hit the market precisely at the right time and acquired new customers relatively easily.

But given that Salesforce was in such a high-growth mode, they wanted to leverage their existing client base to grow organically both internally and externally at the client organization. In other words, they wanted to pursue any strategy that enabled new endpoints whenever, and wherever, possible.

Under this premise, they created the first SELA which conceptually provided unlimited access to the platform. This would ensure that Salesforce could land and expand as fast as possible within a new account without any barriers, paperwork, governance, or red tape.

​The MO of an early SELA deal summarized would be:

Your contract with Salesforce is $10M per year over a 5 year contract term. It is a $50M relationship, and you can use the entire Salesforce platform however you see fit, no restrictions. Use our support as you need it. Our goal is to help you grow.

This unlimited access approach was the foundation for Salesforce’s growth by 100x in the early years. By signing one of these deals, and then expanding into a large enterprise organization, they were able to show massive growth rates on all of the SaaS growth metrics such as users, retention, growth rate, turnover rate, etc.

Because they were signing customers onto SELA’s, their growth metrics went through the roof which gave all of the signals for additional funding, press, and market share.

The goal of SELA in the early days was simple. Achieve as much penetration as possible into the corporate world.

How present day SELA’s have changed

While SELA’s once provided “Unlimited Access” to the platform, that isn’t always the case today. Present day SELA agreements look quite different.

Today’s SELA Agreements are full of floors and caps on the quantity of specific product sets that you can use. While old agreements were “Unlimited”, the new agreements come with added restrictions, usage ceilings, and massive financial growth commitments.

When your organization grows/declines past the commercially allowed threshold within your specific SELA, there will be significant financial consequences. Subsequently, without the proper legal terms and conditions protecting you from changes within your business, you are setting yourself up for significant financial and legal risk.

​Why a SELA is a bad idea for most companies

A floor/cap on your product usage initially may not sound like a large risk for your company, especially if you are comfortably within the allowed threshold at the time of contract execution.  That being said, there are 3 major problems that commonly arise from this scenario. Here we are going to dive into the three fundamental problems:

Problem 1: SELA caps are built based on your current needs

A SELA agreement will often be on a 3-5 year term, and the caps are negotiated based on the needs of your organization at the signing of the contract. This may not sound like a major risk, but for high volatility (growth and/or decline) companies, or anyone in an active M&A industry, this can be a major issue.

When you break the caps of your SELA Agreement, it’s not as simple as “buying extra licenses” to make up the gap. Instead, it will trigger an entire sales event with Salesforce that is going to have them coming back to you for more money.

Additionally, you may only trigger your cap in one single product category (Ex. Pardot), but if you break your SELA caps in that space, they can use that as grounds to raise prices across the board.

These caps are dangerous because as soon as you break one, it puts the power of the contract back into Salesforce’s hands.

Problem 2: SELA Agreements are manipulated by Salesforce’s changing product line

The second problem with a modern day SELA is the ever-changing product line from Salesforce.

Salesforce is a master of releasing and repackaging products. They are constantly rolling out new products into the market, as well as repackaging existing products, while retiring old products.

While innovation at Salesforce is great, the new products and services that are organically (or inorganically) created are rarely contemplated as part of your organization’s SELA. If your organization wants to use those new products and/or services, they will likely need to be paid for separately as an additional expense.

Additionally, some products may “retire” or become a “carveout” of an existing product. Continued usage of these products may actually trigger a contractual breach of your SELA.

This sounds ridiculous, but Salesforce does it all of the time, and it’s very expensive for the client. Naturally, most Salesforce clients are not aware of these inherent risks until they’re sent an invoice for this incremental out of compliance usage.

Here is a recent practical example of how they pull this off...

Repackaging Example: Sales & Service Cloud

Up until recently, Sales Cloud & Service Cloud were two separate products from Salesforce.

Sales Cloud was for Sales Reps while Service Cloud was for service department technicians. These two products came at two different price points. Sales Cloud was cheaper, and Service Cloud was more expensive.

Eventually, Salesforce decided to roll these into “Sales and Service Cloud” as a single commercial product even though they technically operate as separate infrastructures (clouds). This provided Salesforce a commercial opportunity to financially uplift those existing clients that had both products (Sales and Service Cloud), historically with two different price points, now as a single price point that matched the more expensive line item as part of Customer 360. The logic being that both clouds are integrated harmoniously whereas the entire client organization is able to review all of its omnichannel touchpoints with their customers. This “additional value” was largely the basis for this product and price convergence.

The targeted outcome is typically around a 30% revenue boost within the existing customer base. This revenue boost was predicated by a simple repackaging of services.

Problem 3: You are likely paying 41.3% more than you should be with SELA

​We renegotiate a lot of SELA deals at The Negotiator Guru (TNG), and on average, we identify a 41.3% cost reduction opportunity when switching to a standard Salesforce Subscription Agreement.

The reason behind this is that most SELA’s are priced extremely high (on a price per unit, per month basis) and commit the client to much higher usage (products & quantities) than is actually being used, creating conceptual shelfware.

At TNG, we leverage a proprietary Right Size, Right Price approach to drive efficient and long lasting savings for our clients.

We first understand what your organization actually needs and build a roadmap to support you based on your specific global business. Instead of buying everything through a SELA Agreement, we leverage our Right Size framework to ensure you’re leveraging the appropriate products and services at the Right Price.

We are able to easily identify Right Price information based on our industry leading price benchmarking database that is minimally rationalized based on your Annual Contract Value, Industry, and Company Size. We say “minimally” because there are other factors that determine product pricing such as product mix, your roadmap, Salesforce quarterly interests, etc.

Then, we leverage our unmatched expertise negotiating with Salesforce either as a covert silent advisor, or an overt legal agent, to extract maximum value for you at the lowest possible cost.

Those two simple components alone have generated our SELA Agreement customers 41.3% in savings.

We’ve worked with Fortune 100 companies paying $25M+ per year to Salesforce whose actual contract value should have only been $10M.

The savings potential is real and worth the time to renegotiate.

​When a SELA is a good idea

Most of this article is spent sharing why SELA’s are a bad idea for most clients. That being said, there are a few select cases where they may be temporarily beneficial to a client.

Every year, we speak with hundreds of Salesforce Customers. Since the inception of TNG in 2015, we have only had one customer where a SELA was actually a good fit for their needs.

While we always keep our clients confidential, this specific company was a high-growth IT firm with rapid-growth aspirations (500x), large amounts of equity funding, minimal IT resources, and a technical architecture that required Salesforce to act as the backbone for their outreach strategy. They were in a very unique situation.

Here are the required conditions to even consider a SELA:

  • High-Growth Environment of 10x-500x per year;
  • High-amounts of capital investment;
  • A large volume of customers with varying interaction levels across multiple channels; or,
  • A clear architectural roadmap from a digital capability and functionality perspective.

When a SELA is a bad idea

99% of the time, a modern day SELA Agreement is a bad idea. In almost all cases, it just doesn’t make sense.

Here are (only some of) the conditions where a SELA does not work:

  • You signed a SELA 4+ years ago;
  • Your company has predictable needs in both products and quantities;
  • Your company is spending less than $10.75M/year on Salesforce;
  • You have less than 5,000 API connections per day;
  • Your IT department’s strategy is to leverage native (vs. custom) functionality wherever possible;
  • You have less than 3,500 Sales and/or Service Cloud licenses; or,
  • You’re not sure where your business is going in the next 3-5 years. ​

Why “you don’t have to manage it” rarely justifies a SELA

Yet, even with everything we shared, many companies still sign up for new, or keep renewing their existing, SELAs. Perhaps that’s because they haven’t read this article!

The most common reason we hear from our clients on why they have a SELA is that “We don’t have to manage it. There are no order forms, compliance, or governance. We just signed the deal and originally, didn’t have to worry about it.”

While that is great in theory, you can achieve nearly the same benefits with a standard Salesforce Subscription Agreement by negotiating specific terms and conditions into your Order Forms. We will share two of these terms below for your awareness and utilization:

M&A Language

Request language be added to your Order Forms that protects you in the event of an extraordinary corporate event like Merger and Acquisition (M&A) Activity. Adding in the appropriate language for M&A activity can provide huge benefits to your organization. Specifically, ensuring that an acquisition or divestiture can be brought in or taken out of your environment without commercial recourse will proactively avoid painful legal headaches and financial synergy slippage.

Product Swap Language

​As we discussed, Salesforce likes to change up their product line to create disruption in the marketplace and in your contract. Introducing product swap language that enables you to swap products and services freely as long as you maintain the same annual contract value provides a huge value that is similar to that of a SELA.

FAQ’s

What happens if I exceed the caps on a product in my SELA Agreement?

Salesforce will use this overage as leverage against you in your upcoming negotiation. They will either charge you an overage fee or push a net new product on you in exchange for waving your overage fee. This net new product helps them achieve additional revenue, new products, and a larger footprint inside of your organization.

When you exceed the caps on a product in your SELA Agreement you are naturally placing yourself in a vulnerable position with Salesforce.

Many organizations who have an active SELA Agreement with Salesforce don’t have an internal software asset management (SAM) team. As such, these organizations won’t know they have exceeded their cap limit until Salesforce informs them. Even with an active SAM team inside multinational organizations it can be very easy to exceed your caps.

In general, 6 months prior to your contract renewal, Salesforce will conduct an audit on your account to look for any overages. If your organization is not already aware of these overages you’re naturally going to be on your heels trying to fact check information internally. Either way, Salesforce will use these overages as leverage against you in the upcoming renewal negotiation.

There are two scenarios that commonly play out within this situation:

First, if you notice you have exceeded the cap limit, you can take corrective action to decrease your quantities of specific products so that you are back in compliance. Your organization will technically be obligated to pay overage fees for the time those overages were occurring within your environment. The standard language within Salesforce agreements indicates you will be liable to pay the “published retail rate.” In other words, the rate that Salesforce publicly publishes on their website without your organization’s discount.

Second, if Salesforce notices that you have exceeded the cap limit, then you will be hit with a heavy overage fee in a similar manner as discussed above.  However, Salesforce will likely use this opportunity to push new products within your environment in exchange for some of the overage fee. The net outcome, if not properly negotiated, will be a higher total cost of ownership over the term of your new contract than paying the overage fee by itself.

It’s important we state this again: Standard Salesforce MSA and SELA Agreements (aka all agreements) include  a standard clause that any license overage will be charged at the then current retail price. That means instead of paying for additional seats at your discounted rate, they will charge you the retail price for the product that is currently listed on their website.

This is a very dangerous situation as the retail price can often be 2 -3x your standard rate.

We recommend negotiating specific contractual language that limits your financial liability to that of your organization’s reduced rate vs. retail.

How do you approach negotiating an existing SELA Agreement?

When renegotiating a SELA Agreement, we leverage our best-in-class and proprietary  approach that we always use when Negotiating with Salesforce.

Mastering Your Salesforce Spend: Why Ditching the SELA Can Save You Millions

Create a Salesforce Roadmap

The first step in controlling your Salesforce spend is to build a roadmap of specific products and services you will need from Salesforce over the next 5 years. Create a list of both your needs and your wants.

With a Salesforce Enterprise License Agreement (SELA), it is very important that you build a 5-year game plan instead of a 1-3 year plan. The reason is that the 5-year roadmap will help you decide if a SELA agreement is right for you. If you are forecasting rapid growth or large M&A activity, then a SELA may make sense, assuming the proper legal terms and conditions are in place. But without either of those two components, a SELA rarely provides the differentiated and intrinsic value one would expect from its large price tag.

In most situations, a SELA Agreement will not make sense for most organizations. Putting together a Salesforce Roadmap will help you see this clearly. When you have a clear roadmap of what products you need, in what quantities, then you can use that as a benchmark on price.

Benchmark Your SELA Spend with Right Price Data

Once you have your roadmap, the next step is to gather Right Price Data for what rates you should be paying for each product on your roadmap.

At The Negotiator Guru, we have the largest database of Salesforce rates as a result of reviewing hundreds of Salesforce contracts for organizations that span literally every industry. We can tell you what you should be paying for each product or service.

While firms out there like Gartner can provide directionally correct information, they are not able to provide prescriptive insights for your specific situation. To access our Right Price Data for your account, contact us at info@thenegotiator.guru.

When you take this Right Price Data and line it up against your roadmap, you can see an estimation of what your Salesforce spend should be in a total cost of ownership view. Now simply take that total number and compare it to the annual spend of your SELA Agreement to see just how much of a savings potential is available for your organization.

Based on our real client data, we find there is typically a 41.3% opportunity available when switching from a SELA to a standard MSA & Order Form contract and pricing structure.

Examples of SELA Negotiation Success

Through our work at The Negotiator Guru, we have helped hundreds of organizations reduce their Salesforce expenses. Our firm is the industry-leading expert in negotiating with Salesforce.

Here are two recent examples of SELA negotiations we have completed with, and for, our clients. All company information has been redacted for client confidentiality.

Negotiating a $75M SELA Agreement down to $32M (57% savings)

One of our clients came to us with a 3-year term on a SELA Agreement valued at $25M per year. This was a total contract value of $75M over a 3-year period.

We worked with the client to create a Salesforce Roadmap and shift the organization over to an MSA & Order form contract and pricing structure. This simple shift produced a material reduction of their annual spend down to $10.7M per year for a 3-year term.

That is over 57% in savings and $43M in cost savings over a 3-year period. This example shows just how much SELA Agreements can be overpriced.

$30.5M in savings by negotiating a SELA Agreement that no longer made sense post-M&A

This particular organization was on a 5-year SELA Agreement. The SELA was designed based on the company footprint at the execution of the SELA Agreement.

There was one major problem—this specific organization was in the telecommunication industry which was experiencing heavy disruption. As a result of this disruption, the company divested several business units for financial and regulatory reasons. When these business units were divested, everyone assumed that their Salesforce contract would adjust accordingly… but that was not the case.

The response that came back from Salesforce was essentially, “It won’t be possible to reduce your spend because you have committed to this agreement for a total of 5 years.”

This meant that the telecom organization was now paying for products and services that were used by companies they divested, and they were committed to continuing to pay for those products for an additional 3.5 years. In total, this would be $36M in wasted expense over a 3.5-year period.

Through negotiations with Salesforce, we were able to reduce that down to a $5.5M breakup fee for a total savings of $30.5M over a 3-year period. This example shows just how important it is to structure in proper M&A language into your SELA and all Salesforce Agreements.

SELA Agreement Logistics and Strategy

What is the typical SELA annual spend?

The typical customer on a SELA agreement is a multinational organization doing over $10B in annual revenue with a total spend of $15M+ per year with Salesforce.

How long does the process take to renegotiate a SELA Agreement?

The process to renegotiate a SELA Agreement typically takes 2.5 months. That being said, to properly prepare for the negotiation, we engage our clients a minimum of 6 months prior to your natural renewal date. Remember, 80% of negotiation is done through thoughtful and intentional planning. In a best-case scenario, you want to plan for your SELA renewal 1 year in advance.

Who is involved in a SELA Agreement negotiation?

On your organization’s side, the following individuals should be involved in your core negotiation team:

  • Head of IT Sourcing
  • IT Leadership in charge of the Salesforce Platform
  • IT Finance Representative
  • CIO (Optional)

From The Negotiator Guru, the following individuals are involved:

  • Lead Negotiator
  • IT Architect
  • Legal Representative

Do I need to switch off a SELA or just negotiate a lower price?

In most cases, it will make sense for you to switch from a SELA Agreement to a standard MSA & Order form agreement with Salesforce. While you do not have to switch, it is often the most advantageous for you as a customer of Salesforce.

There are several material reasons for this, however, the most prominent being that it’s very difficult to proactively measure the value you’re receiving from Salesforce when everything is bundled into an annual fee. This lack of transparency is by design from Salesforce, allowing your account team to do some creative accounting.

When you convert to an MSA & Order Form contract structure, you can compare your specific needs with Salesforce directly with our Right Price Data to understand exactly what you should be paying.

My company’s workflow is seasonal, and a SELA allows us to adjust licenses as needed. How do we accomplish this with a Salesforce Subscription Agreement?

You can achieve the same flexibility of a SELA by adding in Seasonal Worker Licenses within your subscription agreement. These licenses largely produce the same flexibility as they are intended to be used for seasonal contingent workers that increase and decrease throughout the year. Another common use for these licenses would be for college interns or factory workers.

In some cases, Salesforce will tell their customers that this product option does not exist. This is simply not the truth.

Recently, one of our customers did not believe that a “seasonal worker license” actually existed. Through multiple conversations with Salesforce, he was told this simply was not an option. We pulled up a screenshot of another client’s invoice, redacted all of the confidential information, and shared the invoice with “Seasonal Worker License” as a line item. The client was blown away. You can achieve a Seasonal Worker License... you just have to ask... perhaps more than once.

How to Create a Salesforce Roadmap

In previous articles, we shared with you how the Salesforce machine operates. We shared with you how it structures its organization and the tactics it uses to maximize its revenue from your company.In this article, we are going to dive into your single most important weapon against Salesforce in your negotiation . . . Your Salesforce Roadmap.

​What is a Salesforce Roadmap?

Simply put, a Salesforce Roadmap is nothing more than a table outlining:

  • What you are going to buy
  • When you are going to buy it

This sounds simple, yet most companies don’t go into a negotiation with Salesforce clear on these two points. As a result, Salesforce hijacks the conversation and creates a roadmap for them.

What you are going to buy

This question isn’t always as simple as it sounds.

Do you need Enterprise or Unlimited?

Do you even need premium support? Or would that money be better spent on a 3rd party consulting firm?

Have you run a utilization report to see how many of your licenses are actually being used?

​Is marketing actually using that instance of Pardot you purchased three years ago?

The “what you are going to buy” conversation isn’t always easy. One company we worked with ran a utilization report to find that only 63% of their licenses had even been logged into in the past year. This means they were paying for 37% more licenses than they actually needed!

Another customer realized that a large portion of his organization could get by through downgrading to a lower license level. They were only using basic features that didn’t require them to be at the Unlimited License.

It’s easy to think you know exactly what you need going into a negotiation, but sometimes you need to do a bit more digging into understanding how each department actually utilizes the tool.

When you are going to buy it

Another common tactic Salesforce uses is to tell you that you cannot roll out licenses over the course of a three-year contract. Your rep will tell you that you need to buy them all up front now if you want to get a discount.

This ironically always works out in Salesforce’s favor as the added revenue from those dormant licenses makes up for the discount one rates. The truth is you can negotiate to roll out licenses at set periods of time throughout your negotiation.

​In order to do this though, you need a clear roadmap and to create confidence with Salesforce that this is what you actually need and when you need it.

Why Is Building a Salesforce Roadmap So Important?

Before we dive into how to create this roadmap, let’s first dive into explaining why this roadmap is so important.

A roadmap is your best defense against divide and conquer

Remember the divide and conquer tactics we described in our guide on negotiating with Salesforce? We shared with you how Salesforce will make contact with multiple individuals and decision-makers throughout your organization.

Its goal with divide and conquer is to create conflicting stories which develop chaos in terms of what you actually need.

Creating your own Salesforce Roadmap helps you prevent against that.

When you create a roadmap and get buy-in from all your key stakeholders on that same roadmap, you create alignment within your organization. In addition to the roadmap, we are also going to give your internal stakeholders key talking points on what to say if Salesforce approaches them. It’s also important to know that timing is everything with regards to these key messages.

As a result of being aligned on talking points and what your organization actually needs, your organization begins to speak from one voice. Instead of having Salesforce gather conflicting stories from each department, they suddenly are left dumbfounded when they receive the same story from all contacts within the organization.

Flip-flopping your wants in the negotiation focuses the discussion on the wrong things

Whenever you don’t have your roadmap aligned, you spend your time in the negotiation with your rep going back and forth on how many licenses you need or what add-ons you do or don’t want.

Every time you go to your rep with a revision on your renewal because you and your team changed your mind, you are wasting a valuable chance to negotiate a key term or reduce your rates.

Without a roadmap, you will end up flip-flopping on what you want during the negotiation and spend your time focused on what licenses you are even going to buy instead of the price point or the terms. The entire negotiation gets focused on just figuring out what you need instead of getting you the best rates.

Your roadmap creates that clarity and alignment and lets you spend your time focused on getting you the best deal.

A lack of alignment undermines the key contact of the negotiation

Imagine for a moment that you are a Salesforce rep. You go into conversation with the Salesforce Admin who is your main point of contact in the negotiation. The Salesforce Admin request a 20% license count increase but is not interested in adding any new products or expanding their Salesforce footprint into any new departments.

Then two days later, your sales management team comes back from a basketball game with the CEO of your client organization. They tell you “we just met with the CEO, he wants to roll Salesforce out to his entire marketing department as well.”

As a Sales rep, you immediately jump to the conclusion that your Salesforce Admin is not the authority or decision-maker on this account. All respect you had for this Salesforce Admin’s decision-making ability has gone out the window.

As a result, that Sales rep treats the Salesforce Admin differently in the negotiation. He starts going around them and maximizing his divide and conquer tactics because he knows the Salesforce Admin is not in charge.

This is what happens when your organization is not aligned.

It undermines the individual who is the face of the negotiation. It doesn’t matter if it is a Salesforce Admin, CIO, or CFO.

Alignment and a roadmap gives power to the negotiator

Let us imagine another scenario for a moment here. Imagine that you are a Salesforce rep. You go into a conversation with your Salesforce Admin who is your main point of contact. The Salesforce Admin tells you they want to increase sales cloud licenses by 20% and consider a demo of Pardot in their marketing department.

Then two days later, your sales management team comes back from a basketball game with the client CEO. They tell you “we just met with the CEO, he wants to grow his licenses by 20% and is considering expanding Pardot into their marketing department.”

As a Sales Rep, you just heard consistency.
You heard that your Salesforce Admin is aligned with the CEO.
You heard that your Salesforce Admin is actually in charge of this negotiation.

When you have organizational alignment on your roadmap, it gives power to whoever is running your Salesforce Negotiation. It doesn’t matter of it is the Director of IT, CIO, or CFO. Whenever you have that alignment of stories, it gives that person in the negotiating seat power to drive the negotiation on their own.  

When to Create your Salesforce Roadmap

We typically recommend companies start building their roadmap six to nine months prior to their negotiation. You are going to want at least three months to handle the actual negotiation with Salesforce so a six month runway gives you an additional three months to get that internal alignment.

Each organization is different, but that internal alignment won’t happen overnight. Give yourself some time to meet with all key stakeholders and achieve that internal alignment.

Three Steps to Creating your Salesforce Roadmap

A Salesforce Roadmap is not complicated. It is a simple table of “what you need” and “when you need it” over the next three to five years.

Even though most Salesforce renewals are only three years, it is helpful to plan five years in advance so you can think of a bigger picture of what may be coming down the line. This helps you in creating an aligned story for Salesforce at your renewal.

Step 1) Create a rough draft alone

If you are reading this, chances are you are the one who is driving the Salesforce negotiation. You have extensive knowledge of Salesforce and can probably fill out 80% of the roadmap on your own.

The key in this step is to document all of your ideas for the roadmap on paper.

You don’t want to go to your key stakeholders with a blank slate and build the roadmap from scratch together. That is not a good use of their time, and it is going to create too much debate.

By crystallizing your thoughts about Salesforce into a rough draft of the roadmap, you can share that document with others. It becomes a starting point for the entire roadmap discussion.

Step 2) Take the rough draft to key stakeholders for feedback

This rough draft of the roadmap is purely for internal use. Once you have this rough draft complete you are going to present this document, typically in the form of a PowerPoint presentation, to your key stakeholders within the organization.

This may be your CEO, CFO, CIO, COO, VP of Sales, Director of IT, Salesforce Admin, Sales Management Team, etc.

You are going to take this roadmap to them and say “This is what I believe our 3-5 year Salesforce roadmap looks like...what feedback do you have?”

As you go into these meetings you may find yourself saying, “I have an idea here but I don’t know exactly what X department needs.” This roadmap and these conversations are meant to help you refine the roadmap and clarify those needs with each department in the organization.

What is great about this step of the process is that this allows your team to have internal dialogues about what you need with Salesforce. Without doing this internal roadmap, these contacts would not be brought into the conversation until a contact from Salesforce had reached out to them.

Instead of letting Salesforce guide these conversations, you are getting in front of them and taking charge. This helps you own and drive the conversation.

Step 3) Gather all feedback and refine your roadmap

Once you have gathered alignment from each of your key stakeholders on the roadmap, you are going to want to take some time to sit down and refine that roadmap into a final polished version.

At this point, you are almost ready for entering the negotiation. But before that we need to build a communication strategy and negotiation plan.

Lastly, it's also important to realize that a Salesforce Roadmap is essential for SELA Agreements (Salesforce Enterprise License agreements). Read our guide for more details on how to renegotiate your SELA Agreement.

Confidential Clients: Why We Do It

For those of you wondering why we keep all of our clients confidential, our Founder and Senior Partner Dan Kelly provided a few key insights as part of a recent interview. We hope you appreciate learning why this is such an important guiding principle for TNG.

Moderator: Keeping your clients confidential is a pretty bold and respectable move… Why does TNG do it?

Dan: It’s a great question and one that comes up often during initial conversations with our prospective customers. We find that customers are more curious as to the reasoning versus questioning the legitimacy.

We treat each engagement with a customer as if it were a legal proceeding. We find that our ideal customers really appreciate how sensitive we treat our collaboration with their company and their most senior stakeholders/leaders.

From a logistical standpoint, some customers reach out to us when they are trying to commercially mediate what appears to be a potential legal situation with an external vendor. 95% of the time, we can handle the situation via commercial negotiation. If the situation does require any sort of legal support or litigation, our team is ready to quickly support and collaborate with our customer’s legal team based on our strict confidentiality and document handling standards.

Moderator: Did your background in the FBI contribute to your decision on this approach?

Dan: {Laughing} Yes, I think it probably did. There were two things that I was taught immediately upon entering my FBI career: 1) Before you make any questionable decision, think about how the outcome of your decision would look on CNN the next morning and 2) Classified information is best protected on a compartmented, need-to-know basis.

While our entire team doesn’t come from an Intelligence Community background, everyone is provided training on the importance of confidentiality and the proper procedures for protecting client confidential materials. I can confidently say, without a doubt, that our customer data and processes are more secure than most multinational law firms.

Moderator: When you have prospective clients looking to speak with references, aren’t you afraid of losing potential business if you’re not willing to share your client portfolio?

Dan: You know the business owner in me honestly thinks about this a lot. From an actual data standpoint, we know that if a prospective customer chooses not to work with us, it’s primarily due to cost and not caused from the lack of reference calls.

Another fact that we’ve proven over the years is that 3 out of 4 clients request repeat or ongoing support, so any lost opportunity from this topic is naturally superseded with our repeat customer business. That’s how I would prefer it anyway, as taking on a new customer brings its own inherent risks… it’s a two-way street.

Moderator: How do you make clients feel comfortable working with you if they aren’t able to speak with references?

Dan: My answer on this is simple: Everyone has friends. Do you honestly think any salesperson, no matter what industry, is going to refer you to a client that has had a sub-optimal experience? I am a Strategic Sourcing Expert, and so is the rest of the Service Delivery Team. When we worked for large companies, we often were told to ask for references. However, whenever we received reference contact information, we rarely called them to validate. This reference gathering process is an old school purchasing process for process sake, and we find our best customers find more trust in the fact that we were ranked as the 2nd fastest growing company in Minnesota by Inc Magazine.

Moderator: What are some other benefits that might not be apparently obvious of keeping clients confidential?

Dan: Excellent question... This is a passionate topic of mine of which I could honestly discuss for an hour. In the interest of brevity, a few of the top benefits include:

Ease of Contracting – No Publication

Most of our clients are very large multinational organizations. The Marketing and Legal departments inside of these companies are naturally very protective and risk adverse (for good reason) of their name brand, logo, etc. Since our customer contracts don’t include any language regarding “publication,” it eliminates unnecessary administrative burden, and legal review cycles, on both sides of the transaction.

TNG Client Protection

Most of our clients request that TNG be a covert silent advisor in the background (instead of an overt legal agent of the company). This means that the supplier in which our customer is negotiating with should never have knowledge of our involvement. By keeping all clients confidential, we eliminate any risk of the supplier later discovering our involvement.

Deter Sales Snooping

Without going into too much detail here, just know that large software companies have an incredible amount of financial resources. They employ individuals to be assigned, or even sit in, your organization to learn everything there is to know about your company in the interest of upselling their products and services. This also includes learning as much as they can about what companies are using external advisors to benchmark rates, processes, etc.