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 Difference Between Gartner & The Negotiator Guru

​Gartner, at its core, is a market intelligence firm. It uses a wide-angle lens to give you a big-picture view of market and industry trends. You can use their data as general negotiation guidance and add their toolkits to your own.

​There is absolutely value in this broad-stroke model but it can be limiting when it comes to looking for data and resources that more specifically mirror the size and needs of your organization.

​In this article, I want to outline the similarities and differences between a simple market intelligence firm approach and a niche service provider approach. There are many reasons you might want to research best practices from a 30,000-foot view as well as dive deeper at a 5,000-foot view.

Many of my clients will use both Gartner’s and The Negotiator Guru’s (TNG) services to achieve the best results for their companies.

The graphic below gives a basic overview of the similarities and differences between our companies and we’ll break each one down in this article.

‍

Picture

​There Are Some Similarities Between Gartner & The Negotiator Guru

​Both Gartner and TNG provide information on market and industry trends as well as general guidance on IT Cost Optimization. We have each developed our own toolkits to strategically approach each client’s needs. We overlap when it comes to providing general guidance to CIO’s.

Our companies also both provide rate benchmark data although, as you’ll read below, we go about this in different ways. Gartner has quite a bit of data they provide in aggregated terms which is useful but, without isolating the information by industry or annual spend or similar categories, it can be difficult for CIOs and their supporting functions to narrow down actionable intelligence that is defensible and realistic.

​​There Are Many Differences Between Gartner & The Negotiator Guru

​The keyword I would use to describe the services Gartner and TNG have in common is ‘general.’ Gartner is a great resource for general information across a wide array of topics but rarely provides niche depth that our customers are longing to consume.

In contrast, TNG has a deep and disciplined focus within the IT Software vertical which enables our team to share actionable insights that are localized, specific, and highly relevant to our clients. In fact, it was our early clients that helped shaped this disciplined focus as they made their niche needs clearly known to our team. Due to our outstanding client family, TNG has been on a journey to fill our clients’ market intelligence needs for specific supplier relationships. This has organically driven our firm to be the worldwide leader in Salesforce Contract Negotiation Advisory Services which typically is 80% of our work portfolio at any given time.

With the average cost of a Gartner subscription being $30,000 per seat, plus additional consulting costs in order to receive personalized advisory services, it’s worth your while to be informed on what they can and cannot help you achieve.

Because we provide specialized data and consulting services, we’re able to dig deeper into our clients’ businesses and tailor our process to better achieve the results they’re looking for.

The following are a few of the specific areas The Negotiator Guru differs from Gartner in terms of what services and results we can offer our clients.

Right Size

​While Gartner has a wealth of industry data and information, it can be nearly impossible for a client to look at the data and isolate a specific instance to best compare themselves to their peers. This leaves clients feeling informed but uncomfortable about how this information is applicable, and more importantly defensible, within their environment.

In certain circumstances, Gartner will provide “best in class” rates for a specific digital capability or service portfolio. One would argue that this provides directionally correct price targets to use as a market intelligence within their supplier negotiation. We generally agree, however, it’s important to note that your software sales executive (or worse yet your internal colleagues) will very quickly share with you that you don’t fit the profile of those rates for XYZ reason. We know this because we’ve been in these conversations on countless occasions.

In the rare case that you obtain “best in class” rate information for your specific topic of interest, you are still missing a critical piece of knowledge which we call our “Right Size” guidance. Using conservative figures, there is a 15-20% value-capture opportunity just by applying Right Size practices to your research and internal analysis before entering into any IT contract negotiation

Our supplier-specific expertise is one of the biggest contributors to this Right Sizing approach.

Within our Discovery Phase, we take an inventory of your current products and licenses and match them against your actual business needs. Almost always, we find that our clients are over licensed and have shelfware within their environment. This is an example of Right Sizing.

From a Right Pricing standpoint, not only do we understand “best in class” rates, we localize price targets based on industry, client size, and contract value. This enables our clients to feel 100% confident about the market intelligence as we’re benchmarking their rates against that of their likesize industry peers.

To expand upon this difference, we’ll use our expertise in Salesforce as an example.

As raised and validated by leading consulting and intelligence firms, TNG has the most comprehensive  database of Salesforce rates in the world. This capability allows our team to quickly and easily perform a price benchmarking exercise for our clients. In many instances, we’ll inform prospective clients that their rates are within an acceptable margin of their “Right Price” benchmark and that the only real opportunity (if any) is to pursue “Right Sizing” inside of their environment. At TNG, our culture and client centric values direct our work and guide us to only accept prospective clients where we know with certainty there is a strong potential to drive huge impact.

Picture

​Being able to combine Right Price and Right Size analysis will have a significant impact on the effectiveness of your supplier negotiation strategies. ​

Contract Language Risks

​As a result of our deep supplier-specific expertise, our team on average analyzes 5 - 15 software contracts per day. As a result, we know what’s “normal” with all of the large enterprise software platforms and any common risks that are inserted unbeknownst to our clients. By doing this every single day, our team is easily able to identify commonly-used, ambiguous language that always favors the supplier.

Large software companies know their customers rarely spend time analyzing terms and conditions within their contracts. Furthermore, the widely accepted principle of Software-as-a-Service (SaaS) leads clients to believe the terms are standard and unchangeable.

Unfortunately, this simply isn’t true. As part of our Contract Execution Phase, we conduct a deep dive assessment of our client’s supplier contract as part of our standard service (another major difference from Gartner). To put the impact of this added service into context, our team identifies a unique contractual risk within SaaS contracts alone 33% of the time. If the contract we are analyzing is not a SaaS contract, contractual risks are identified, on average, 85% of the time. Knowing what to look for in each supplier’s contract language helps our clients avoid common pitfalls and supplier-centric renegotiation strategies.

Sales Playbook Coaching

​Another key difference between taking a general approach on market intelligence (Gartner) vs. a software specific deep niche (TNG) is the ability to learn and leverage the sales playbook(s) for these large enterprise suppliers. It may not surprise you that within the most successful software sales organizations are repeatable and prescriptive sales playbooks that guide the near robotic actions of their sales representatives.

As a result of learning these sales playbooks we are literally able to tell our clients the moves their suppliers are going to take next. This intelligence allows us to be one step ahead within the negotiation process while leveraging the interests of both parties.

While the art of negotiation is an art and not a science, arming yourself with this intelligence allows you to deploy counterintelligence strategies inside of your organization (to counteract common supplier tactics such as divide and conquer) while also proactively preparing counterpoints to their foreseeable arguments. As a result, our clients commonly tell us that they were the most prepared they have ever been before, during, and after a negotiation.

Advisory and Execution Services

​We don’t just tell you what is possible. We help you achieve it.

The biggest criticism most companies have of typical market intelligence and/or management consulting firms is that they’ll tell you what “best in class” looks like but will leave you to figure out how to achieve it within your organization. If they do offer advisory services that help you implement their “best in class” then it will be for additional fees that eat away at the cost savings potential, etc.

We’re a full, beginning-to-end provider who will help you all the way through to the execution of the contract..

At TNG, we not only share a “best in class” picture but also create a realistic future state localized for your business. We help you implement that future state while also limiting risks to your organization long after our engagement ends. This is all part of our standard duty of care for our clients.  

4-Step Negotiation Process

​Our proprietary 4-step negotiation process allows us to deliver a clear and consistent service to our clients. In the interest of brevity we won’t go into detail of what each step entails, however, please know that within the Discovery and Strategy steps you will walk away with a forward looking roadmap as part of the overall engagement. If even offered, this would be an extra advisory fee from Gartner and/or any other market intelligence and/or management consulting firm.

The graphic below quickly outlines our negotiation process:

Picture

Compensation & Fees

​Our compensation for these services is also entirely different from Gartner’s method.

As mentioned above, Gartner’s average subscription rate is $30,000 per person plus any additional consulting fees.

With this package, you have access to their standard publications, toolkits, and potentially a limited number of “analyst calls” which are quick conversations with the author of the publications. Any additional advisory assistance, if even possible, comes as an upcharge. Even with this additional cost, you will be on your own from an execution standpoint.

Picture

​We charge either an Advisory Fee based on annual contract value or we offer a Pay Per Performance option with a simple baseline calculation.

We don’t charge based on a subscription service to our articles, we provide all this information for free.

Our rates contain no hidden charges or surprise upsells. On top of that, we’ll help you execute the strategies we develop with you.

We’re incredibly transparent with how we price our services and our clients never question the value they achieved from engaging with TNG.

Combining a Broad Overview Approach with a Specialized, Niche Consulting Firm is a Winning Equation

One of the questions we hear frequently is whether someone can/should work with both Gartner AND The Negotiator Guru.

The answer is yes!

Gartner provides a lot of good, general information. TNG helps you zoom in on the information that is most relevant to your organization so you can determine which key findings are critical for driving cost savings/avoidance while lowering your contractual risk.

Gartner is a market intelligence research firm that has a very limited advisory component separate from their articles. They do not generally provide execution services.

TNG provides information without a subscription fee and our advisory and execution services are provided in the same package.

Bringing in TNG to help you pinpoint your specific needs, value capture opportunities, and execution strategies will provide immediate and long-term intrinsic value for your organization. Remember, TNG will only accept you as a client if there is clear and distinct net positive impact potential… well, we can’t speak for the other guys.

Quid Pro Quo: Salesforce & Salesforce Consulting Partners

We commonly get asked the following questions in varying forms:  ​

  • Is The Negotiator Guru (TNG) a Salesforce Partner? Are you on the AppExchange?  
  • What are the differences between TNG and a Salesforce Partner?  
  • Why can’t my Salesforce Partner advise me on the best possible rates/products for my Salesforce environment?

Before we get into the specific answers to the above questions, let us share a brilliant unsolicited quote from one of our recent multinational clients regarding the motivational differences between TNG and a Salesforce Partner:

Expecting a registered Salesforce Partner listed on the AppExchange to give you completely impartial advice on Salesforce pricing is like expecting a court room prosecutor to share their notes with the defense before every trial.

Why, you might ask?

The answer is simple: All Salesforce Consulting Partners have an unavoidable conflict of interest with their clients. Why? Because of the inherent need for these “Partners” to make both their client and Salesforce happy.  

In this article we’re going to cover this conflict of interest and why TNG is different.  

Salesforce Partners Always Have Two Clients (and one isn’t you)

Salesforce Partners have two customers:  

  1. You the client; and,  
  2. ​Your Salesforce account management team (hereby collectively referred to as “Salesforce”)

The fact of the matter is that your Salesforce Partner is, by design, incentivized to keep both its client and Salesforce happy. The difficult truth is that you, the customer, are the least important of the two clients. Yes indeed, more often than not, your Salesforce Partner has a greater long-term interest in keeping Salesforce happy. Yes, we know this sounds horrible, but we hope you appreciate our directness here.

Let’s dig into two key, but interrelated, reasons:  

‍1. Business Relationships

Your Salesforce Partner focuses heavily on keeping a strong business relationship with Salesforce. Why? Because Salesforce is their single most effective sales channel to acquire new business. When Salesforce identifies a new or existing client that needs custom development work, they have the entire Salesforce Partner community to consider when providing a recommendation to their customer. Naturally, those Salesforce Partners that are “supportive” to their sales process will be referred more and more business.  

‍2.  Money

‍More referrals = more business = more money.  

Back in the 18th century Edmund Burke once said “…never bite the hands that feed you.”

Presenting this differently, if you were a Salesforce Account Executive and you had a Salesforce Partner repeatedly suggest changes to an account that materially decreased your sales compensation revenue, would you continue using that Partner when you have others options available?

To be clear; we are not saying that all Salesforce Account Executives are unethical in how they conduct business. However, we are stating that there is an inherent fundamental conflict of interest for the Salesforce Partner who commercially needs to appease both parties.  

The unfortunate situation is that while a Salesforce Partner may know a customer is being sold more products and/or services than they actually need, they rarely speak up for the reasons above. We’ve even been told there is an informal blacklist inside of Salesforce that keeps track of these Partners that raise cost avoidance opportunities during the sales process.  

We don’t like writing about this topic but we know every customer wants the truth.  

‍Why TNG is different

Quite simply we are only focused on keeping you, the client, happy. When the firm was founded we only included a “pay for performance” compensation option to ensure our incentives were aligned with the client. Over the years, we added an “advisory fixed fee” option purely based on repeated client requests.  

‍TNG’s Right Size & Right Price Process

Part of our secret sauce is a deep focus and understanding on 1) how Salesforce works, 2) you as a customer, and 3) best practices on how to quickly drive savings in your environment. While strategic negotiation is an art, our Right Size & Right Price process is more of a science based on its repeatability across all industries.  

Picture

The Right Size process

‍ focuses on identifying consumption based savings opportunities within your organization.  

Our three most commonly identified opportunities within this process are:

  1. “shelfware” elimination
  2. license optimization
  3. governance enhancement.  On average, we identify 24% savings opportunity within this process alone.

The Right Price process purely focuses on your product and service price points within your specific Salesforce contract. The vast majority of our clients reach out to us for this service alone. Specifically, they want to know how their prices compare to their peers and if they’re getting a “good deal.”  

We have the largest database of Salesforce rates in the world and can quite easily identify if there is a price optimization opportunity within your various SKUs. Unlike other large market intelligence firms, we are able to isolate your realistic “should cost” price points based on your industry, annual revenue, and annual contract value. The others simply will share a “best in class” rate which is ambiguous and often self-serving.  

On average, we identify a 22% savings opportunity here but your specific opportunity could be as high as 305% (yes, this was a real client).  

Fit-for-Purpose Engagement Style

The Founder of TNG, Dan Kelly, feels strongly about providing our clients options on how they engage our firm depending on each individual client’s needs. Some clients want a “negotiation-as-a-service” approach while others simply want the output of our Right Price process to identify target price benchmarks to use within their own negotiations. We welcome you to start a conversation with our firm to determine how we can most effectively and efficiently support you.  

‍Summary ​

To recap, here are the basic points of what we’ve covered in this article:  

  • Your Salesforce Partner has motivation to keep both you and Salesforce happy;
  • They aren’t able to easily share cost savings opportunities with you in fear of losing future opportunities with other Salesforce customers;  
  • The Negotiator Guru is only focused on driving cost savings for you by negotiating with Salesforce, the client;  
  • We have a proprietary negotiation process that includes both the art of negotiation and the science of opportunity creation inside of your Salesforce organization,  
  • On average, we save clients 20-50% on their Salesforce annual expenses through our Right Size and Right Price process; and,  
  • On SELA Agreements (Salesforce Enterprise License Agreement), we typically generate a 41.3% savings for our clients.
  • We only accept clients within our full negotiation service where we know we can make a huge impact.  ​

What to Look Out for When Negotiating with ERP Providers like Oracle & SAP

Do you know how to protect yourself and stay in the driver’s seat during contract negotiations so that you won’t be held ransom by your ERP provider?

In this article, we’re going to outline the top things you need to take into consideration when negotiating contracts with Oracle, SAP, and any other ERP system.

We’re going to share with you the key terms to clarify in your contracts to avoid extra costs and substantial frustrations down the road.

What to Look for in an ERP

While no company has a crystal ball to know exactly what the future will look like, you do need to identify how you’d like your business to function over the next 10 years.

Why 10 years?

Typical business roadmaps project as far as 3-5 years in the future. Most ERP systems relationships last a minimum of 10 years. You need to know how your business will function in order to know what you’d even need an ERP for and what it would need to do.

You need to be risk-averse in your contract negotiation in order to cover your bases for what could happen.

Once you have your future vision in place, you’ll look at the supplier landscape. Compare what each of the top ERP systems providers offers and how it’ll meet your needs outlined above. Create a Supplier Decision Matrix and stack each contender against it to determine which is the best for your corporation.

Once you know which ERP software is right for your corporation, you’ll need to dig deep to really figure out the total ownership cost. This is the tricky part and is best handled through careful contract negotiation, financial analysis, and service management.

Key Things to Consider When Negotiating an ERP Software Contract

The contract is the most important factor when determining the total cost of ownership of the ERP and there are generally only two triggers for renegotiation once a contract is in place.

These triggers are: mergers & acquisition activity and contract renewals.

Providers know that you don’t read ERP contracts every day. They design contracts in complex and ambiguous ways, which leads to more revenue for them - and more fees for you.

Each of the following points needs to be specifically addressed and outlined in your contract to prevent your ERP from holding you ransom at various times over the course of your relationship.​

Pay Attention to Intellectual Property Ownership

Many ERP contracts will state that any systems or processes developed while using the ERP are now Intellectual Property (IP) owned by the ERP provider.

We worked with a customer recently in the manufacturing industry. They had developed a process for creating their materials more efficiently going through the production line. According to their contract with their ERP provider, it shows that any process that you develop using the ERP software can be considered ERP owned IP. As such, we needed to carefully negotiate the situation with the ERP provider so as to not cannibalize the newly found process improvement which led to millions in positive P&L impact (new revenue and cost savings).

In a contract, you need to be very clear who owns the rights of process improvements as far as when it may directly or indirectly utilize an ERP system.

Your ERP is the backbone of your business. As such, if properly set-up and integrated throughout your organization, it touches most if not all aspects of your business. Naturally, this complicates any opportunity to disentangle from that ERP.

If Oracle, SAP or any other provider wanted to play hardball, they could say any process improvement that utilizes an ERP system could be co-owned or sole-owned by that ERP.  If this is the case, the provider could take that process and then go sell it.

In fact, one of our recent clients had this happen to them based on not properly reading the contract years ago. They needed to retain our expertise and a major law firm to seek litigation with that specific provider.

Make it very clear who owns what when negotiating your own contract. It needs to be clear that the client owns all IP that are developed for the benefit of their company.

Be Smart About Your License Cost Model

Everyone knows ERPs cost a lot. New contracts with smaller providers will often undercut themselves for the first year or two but will see a massive uptick in years 3-8 because the ERP knows it’s incredibly difficult to leave an ERP once you’re integrated into it.

The cost models of ERPs vary depending on the makeup of the customer’s business and what will be the most profitable for the provider.

Some of the pricing models include:

  • Seat-based: Typically the number of humans who log in to the system. These licenses can be either Perpetual or SaaS based.
  • Site-based: Number of physical locations, etc.
  • Consumption Based: Number of processes, inputs, etc., into the tool.
  • Value Based: The newest model within the marketplace and yet the scariest of all. A cost associated with the perceived value of using the platform within your business.

Generally speaking, seat-based pricing is the most cost-effective for companies looking at ERPs, but this depends greatly on what your 5-10 year plan looks like to know which would be the most beneficial to you.

In addition to your unit cost, there could also be annual maintenance expenses. This acts like an annual expense and is generally a percentage of your perpetual license fee/net spend with the ERP.

There are 2 ways to host an ERP system:

  • On-premise: Software that is loaded on the servers you’re in control of.
  • Software as a Service (SaaS): Software is hosted in the cloud by the provider.

Either way, you need to be careful how you license a product because if you don’t have control of consumption and volume-based metrics, it can skyrocket your costs.

Know Your Audit Rights

This is one that gets people in trouble a lot. Generally speaking, Oracle and SAP will not proactively limit access or connectivity to your ERP. This almost always is the responsibility of their customer, based on their unique needs.

As such, these providers will contractually allow themselves unfettered access to your ERP environment with the intent of auditing the usage of their software.

The most common areas of audit risk are:

  • License compliance (Using more seats/volume/etc than you are paying for)
  • Architecture compliance (Too many API connections, etc.)
  • M&A compliance (Acquisitions, divestiture, subsidiary utilization)

Depending on your unique situation, you may be subject to all three (or more) risk areas. It’s important to know there is intentional ambiguity by the software providers in how one could interpret contract language related to permissible use.

Furthermore, we find that clients have no intention of noncompliance within any area but find it most difficult to monitor and govern the area of architecture compliance. A common example of routine noncompliance when a client links their ERP system to both development and production environments.

Similarly, if an ERP is connected (in anyway) to a client’s CRM system it may also trigger a non-compliance event for both architecture and license compliance due to the fact that a client almost always has more active users within a CRM environment. Those CRM users may be somehow benefiting from the ERP and well, we’ll leave it to your imagination based on what you’ve already learned from this article.

Over the last 10 years, large ERP providers like  Oracle and SAP have been focused on audit rights within a client's environment. Specifically, when an ERP is living within a client’s infrastructure (on-premise) it’s technically infeasible for the provider to proactively monitor license compliance.

As such, these providers are inserting audit right language within to client’s contracts (both new and old) providing the legal authority to conduct random audits of a client’s environment. The providers deploy both human and technical based tools. The technical tools include running scripts that “listen” to your environment.

These scripts are developed by the provider themselves and are programmed in a way to identify every single endpoint. The output of the script’s analysis is a single report that identifies ways in which the client is potentially non-compliant. This automatically places the client in a defensive position leading them to try and disprove any sort of non-compliance allegations.

These guys make huge revenue by running these audits and identifying non-compliance. Architecture based non-compliance is most often the most profitable audit for a provider. In addition to what we’ve already stated, another risk area is when your ERP is connected to other systems outside of your current infrastructure.

In a nutshell, every time you make a connection between your ERP and another outside platform (often done through APIs), the ERP provider may identify this as a missed charge and will charge you retroactively since the connection was initiated. This can easily develop into millions of dollars of new revenue for the ERP providers (with very healthy sales commissions).

Not only with the ERP provider monetize the API connection with an API charge but will also try and push  value-based pricing.

For example, a client is connecting different systems together (using APIs) - this is the backbone of how their systems work. It is going to help them go to market faster.

The ERP provider is arguing the fact that “you are going to get an extra 20% increase in value from the system now vs what we quoted you. As a result, we are going to increase your fee by 20%.”

Value-based pricing is risky because these providers can charge for new API connections, new acquisitions, product launches, and/or the output of the tool and how it can help you run your business. It’s based on potential and not necessarily even realized revenue!

Don’t let a provider run a script inside your environment. If they don’t have access to your information, you’re in control of it and you remain in the driver’s seat.

Have Clear Merger & Acquisition Language

Put specific clauses in the contract that make it very clear what happens if you are acquired or if you acquire someone else.

More often, it is the provider who offers this language. These companies will put in very loose language to say ‘if this happens, we will talk about it’ which leaves a lot of area for ambiguity.

To best prepare yourself for any situation, we recommend you place specific and measures or language in your contract that outlines the cause and effect for the most common situations.

Specifically, you’ll want to identify what happens if you are acquired or if you acquire a separate entity. Within any of these situations it’s important to have clear legal language regarding the rights of your company. From a commercial perspective this means having specific pricing thresholds.

Simply put, If you are acquired, you take the better of two prices. You take the best price of both until you, as the newly combined customer, want to renegotiate.

If you are acquiring a company, it’s important to insert legal language allowing you to renegotiate the contract immediately or rather simply adding the newly acquired entity into your existing contract with only a reasonable increase in fees. From a commercial perspective it’s important that you outline what (if any) additionally fees would be subject to the transaction.

You want to eliminate ambiguity. From a pricing standpoint, you want to make this as clear as possible.

Set Expectations About Subsidiaries

You also want to know the specific parties of the agreement. A common hiccup for companies is that they don’t have subsidiary language in their ERP contracts. A company like Coca-Cola, where each product line acts as its own subsidiary, could be in default of the contract by letting that subsidiary use your system without proper language.

This is something people don’t think about until your provider comes to you and says, ‘Hey, by the way, your other subsidiaries are using this ERP software. Happy you are doing it, but that is not part of your contract so here is a bill for another million dollars.’

Third parties—suppliers, vendors, non-employees—need to be defined in the contract as well. If third parties are allowed to act on your behalf, there shouldn’t be any additional fees for them to use your system.

Be Sure to Outline Price Protection

Another thing you need to consider when negotiating your contract is price protection. Generally speaking, companies don’t write in any sort of price protection year-over-year.

What that means is that over the contract term, your ERP provider could change the price points of your unit costs at any given time.

It is not just about being clear about locking in your price at contract term, it is also putting a cap on the amount of increase that can happen at the next contract renewal, which needs to be aligned to the Consumer Price Index (CPI).

A general rule of thumb is that the increase shouldn't exceed 3-5% at renewal.

Include Clear Terms Around Your Service Level Agreement (SLA)

An ERP is a critical piece of software for any corporation and yet we often don’t negotiate Service Level Agreements (SLAs). If ERP systems go down, it can shut down governments and grids. It is a critical software within companies for good reason.

Make sure that you have the best service level agreements and governance agreements by specifically outlining them in your contract. Including these will ensure that your provider keeps their service at 99.99% performance.

In addition, there needs to be penalties for an ERP provider not meeting or exceeding their Service Levels that you agreed upon in your contract.

Most contracts will put in language about penalties but most companies don’t catch ERP providers when they are starting to fail. There are hundreds of thousands of dollars left out there because no one said “Hey your service was down over the weekend. That creates a $200k payment because it has been down for X hours.”

If a big company hires an IT governance professional to monitor that, that professional will likely be ROI positive. You pay them $130k salary and then get $250k-400k in fees coming back from the ERP provider.

Along with keeping an eye on the service levels internally, you need to put the ownership on the ERP provider to send you reports of the performance versus making you have to monitor if it was working correctly. You should put the onus on the ERP provider versus on your employees.

The big providers won’t allow this very often but the smaller ones will. Make it the obligation of the ERP provider to know that there has been a breach in the SLA.

The big ones, like SAP and Oracle, will send automated reports and humans have to look into them to see if there is an issue.

Don’t Forget Cybersecurity and Intrusion Detection

You need to be careful that if you get hacked, you don’t owe your ERP provider or are legally obligated in any other way to pay a hacking fee. This is called indemnification.

In matters of cybersecurity and hacking, your contract should stipulate that the ERP provider should be accountable, if possible. There should be financial and legal obligations, and your ERP software provider should be responsible for any sort of intrusion into the system—especially if it’s located in the cloud.

The concept being that if someone hacks your environment, the source code from the ERP could be opened to the black market for rip off and resell.

People don’t look out for this enough and hackers are getting more sophisticated every day.

Know the Rules About Implementation Partners

Implementation partners are third parties that will help develop custom code on top of the ERP system for your business.

Most of the time, your contract states that any implementation partners have to be registered as “Preferred Providers” for your specific ERP software.

You can’t have just anyone build custom code on top of an ERP system, it has to be an approved vendor.

It is a contractual risk to your company if your contractors are not certified by your ERP provider.

Your E-Commerce System Needs to Play Nice

If your company is in eCommerce, you need to make sure that there is an active and working connection between your ERP provider and your eCommerce provider.

Many ERPs will tell you “Don’t worry, we will make a connection.”

What they won’t tell you is that the connection they make will cost YOU more money. Your contract needs to dictate who is accountable for paying for any connections that are required for your eCommerce platform and your ERP system to play nicely together.

We always make the new piece of software that is connected to the ERP system pay for the API. It is the third party’s cost.

We just had a client that we saved about $500k for this very point!

They have an ERP system and they were working on getting set up with an eCommerce platform.

There was one sentence in the contract that made it ambiguous on who pays for the cost of being able to have different systems to talk to one another.

The ERP software provider was planning to charge it back to the client and the client didn’t even assume that would be their cost.

That basic API connection should not be your cost to maintain and pay for - stipulate in the contract who is responsible (ideally the third party) ahead of time so you aren’t stuck with a huge bill.

Make Sure You Have Coterminous Contracts

Another big thing to look out for is coterminous contracts. In most large companies, each department will have separate contracts with an ERP provider and these contracts won’t align on the same termination date.

If you have multiple business units in a company, the provider will often split out their budget and license fees per business unit.

This is the biggest trick in the book and the largest companies in the world forget to do this step.

It creates massive chaos because you can’t get everyone on the same page. This situation forces the client to align internally at multiple times throughout the year in the interest of representing the entire company. Clients typically lose 10 - 20% when they are in a non-coterminous environment. .

If you you are subject to an non-coterminous environment, then the ERP provider is in the driver’s seat. They will divide and conquer you. This is called a split requirement and they will negotiate with each department individually.

In other words, the ERP software provider negotiates at a business unit level versus an enterprise level. At enterprise level, you have volume and leverage to get better terms which typically drives an additional 10-20% in value.

In Conclusion

Whether you’re negotiating an initial contract or a renewal, make sure you develop and maintain a total cost of ownership view.

First, make sure you understand how your business will be growing over the next 10 years.

Then, dissect the contract so that you better understand the unit cost and connection fees.

In the contract, layout all potential possibilities early as opposed to being forced to react to them as they come along. The more prepared you are, the better you’ll be able to handle surprises, pivots, and conflicts.

Make sure that in the contract, each of the specific points outlined above are detailed with zero ambiguity. Hit all these points as a minimum.

The truth of the situation is that the sales representatives at these ERP providers know you aren’t negotiating an ERP contract everyday. While we’re not saying that every ERP sales representative leverages this face in a malicious manner, it’s important to understand how to protect your company.

As you can see, there is a lot to take into consideration when negotiating contracts with ERP providers. Keeping these points in mind will help you to protect yourself and your company. If you need help implementing any of the above, we have the experience and know-how to protect you from being held ransom now and 10 years down the line. Reach out to us, we’re here to help you with negotiating contracts with your ERP provider.