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

A 3-Step Process to Reduce Your IT Spend 25% Or More

​In the latest meeting with your company’s executives, the ultimate goal was the same as ever - increase revenue, decrease spend.

Do more, with less.
‍
Your directive is to find a 10% cost savings in the next year and you are looking for some quick, streamlined ways to achieve that goal.

Have you taken a good look at your current contract situation? Where can you find savings in the software and products you’re already paying for?​​In this article, I’m going to share how you can create a system to manage and optimize your current (and future) IT contracts. By taking these steps, you'll achieve the best cost savings (often upwards of 25%) for your company.​

​How do you manage & optimize your current IT contracts?

To optimize your IT spending, you need to get organized. Tons of contracts are flying around and you have to know where you’re starting from today to be able to optimize for the future.

You have multiple contracts with each supplier you work with. Each product you buy from them throughout the year has its own legal commitments: Master Service Agreements (MSA), Statements of Work (SOW), order forms, etc.

Each supplier has a number of IT contracts they use with their clients.

Any of these types of contractual documents probably have different commercial language.

And they all add up to time and money obligations for you.

The worst part? Almost none of these contracts will be co-termed. Regardless of the company they’re with, each contract will have a different term period. Some of them will be for six months, a year, eighteen months, what have you.

This creates mass chaos and it’s all by design.

In order to get out of that chaos, you need to get above it - get a bird’s eye view of the landscape of your IT contracts. This can be a very arduous process but the payoff is huge. Take the time to align each of the contracts so you can properly optimize around them.

Step 1: Create an Asset Inventory List

If you don’t have a contract management system - and most companies don’t, even the biggest ones out there - you need to create an Asset Inventory List.

Basically, list out all your suppliers and all the IT contracts. You need to be clear on what contracts you have with a specific supplier.

You can do this with a fancy Excel spreadsheet like the one I’ve created below. You can download this template for your own use.

Picture

​Essentially, this list will have the vendor name, contract type, contract term, and price. Consultant groups charge millions for this fancy spreadsheet but you can create one yourself from my free template.

‍Through this process, you’ll identify 2 things:

  1. How much you’re spending every year.
  2. How many IT contracts you have with each supplier.

With this information, you can tackle the next step. You now know what contracts are coming up for renewal and when. You know the negotiation period and can bring in extra help in advance to work through that process. And finally, you can now work on co-terming all the order forms and SOWs.

hese adjustments create more administrative ease versus the chaotic burden they’re designed to be.

Once you’ve got a survey on your IT contract landscape, you can move on to Step 2.

Step 2: Analyze Each Supplier Against a Right Size/Right Price Matrix

Start with the suppliers that are your biggest spend items. These will most likely be your ERP provider, your Microsoft Office contract, and your CRM software. Do an internal assessment of these suppliers and determine:

  • How much you’re spending;
  • When you’re going to renew; and,
  • What you’re planning to do in the future.

This will help you determine that you are, in fact, only paying for the items that you need versus those that you don’t. All too often companies are paying for products that they aren’t even using because they don’t have a handle on their contracts.

The second thing you’ll be able to keep an eye out for is whether you’re paying for the right license types or not. Challenge your company to look at ways you can downgrade your subscriptions.

The third piece of knowledge you’ll gain from this process is figuring out which business capabilities each supplier is supporting. You’ll be able to see which suppliers are overlapping functionalities.

This overlap is common in decentralized organizations. Each business stakeholder wants to use the software they’re familiar with even though three other companies provide the same capabilities. Your corporation is likely spending way too much on overlapping suppliers that provide the same digital capability.

Paying for software you’re not using is called shelfware. Don’t make the mistake of paying for shelfware.

You need to start this internal assessment process six months before your next contract renewal. If you don’t, you’re going to be playing catch up to these large suppliers because they know more about you than you do.

Step 3: Preparing for negotiation

Create your negotiation team

Your negotiation team should consist of 3 different roles: a business stakeholder, an IT stakeholder, and a negotiator. Sometimes this last role is procurement and sometimes it involves an outside advisor.​

​Gather benchmark data

In addition to your negotiation team, you’ll need some hard-to-find information. One of the biggest pieces of leverage you can get is benchmark data. This data gives you the prices other firms are paying for the same service. There’s no way your company can know what other businesses are paying unless you bring in an external advisor like The Negotiator Guru.​

Create an opportunity analysis

You can analyze your rates against the benchmark to find out how competitive your prices are compared to your industry peers. Similarly, you can analyze your supplier performance metrics, Service Level Agreements, governance process (etc.) against benchmark data to find out how well your suppliers are performing.

And finally, you can analyze your Innovation Quadrant against the benchmark.

How is the supplier driving new ideas, new concepts, process improvements, etc? How are they incentivized to drive cost savings for YOUR company through their relationship with you?

For example:

If you’re using a company like Accenture to run your help desk, there should be a clause in the contract for a 10% target cost savings over the contract term for the services they provide. They do this through process improvements and through automation.

This ensures they are actively working toward providing your company with cost savings to make your business more efficient.

Create a Roadmap of Initiatives

This roadmap has the intent of prioritizing your initiatives to ensure you’re targeting the greatest impact that will take you the least amount of time.  Of course, not all initiatives will be easy to achieve but taking a systematic approach to what you work on first is paramount to your success.

To assist with this approach, we suggest categorizing your initiatives so that you can easily sort and isolate the opportunities in front of you. Categories you might consider using include “Quick Win, Strategic Sourcing, and Business Transformational.” Naturally, the progression of cost savings usually increases in scope and impact as you move from Quick Win opportunities to that of Business Transformation.

After you perform your opportunity analysis, get your benchmarks, and create your roadmap of initiatives, you can then pull together a Heat Map. This entails creating a visual graph that clearly identifies the sequencing opportunities.

Here is an example of one of these Heat Maps:

Picture

Being proactive with IT contracts can save 25% annually

A stellar negotiation team together with your benchmark data and forward-looking road map will give you a clear direction during the renegotiation process.

‍Centralizing, and subsequently renegotiating, your contracts with this approach generates on an average 25% P/L cost savings for your company (industry agnostic).

A decentralized company can cost you extra money

If a company has multiple business units and/or sites that are responsible for their own procurement you will undoubtedly have an unstructured supply base. The downstream effects of this situation is that you will have overlap in your supply base, duplicative digital capabilities, and a rats nest of contracts causing incredible inefficiencies and unleveraged spend.  

For example, if one branch is using DocuSign for e-signatures and another is using Panda, this is a digital capability overlap that can easily be eliminated.

After your company streamlines your digital capabilities, your company should be able to easily consolidate spend, processes, and contracts. Once you remove the redundancy and get everyone on the same software, you can also negotiate a single contract for your company that drives immediate cost savings and long-term cost avoidance.

IT Contracts create both opportunity and risk in Merger & Acquisition transactions

When combining companies, it’s important to do both a top-down and bottoms-up approach to identifying synergy opportunities within your IT spend.

Top-down approaches involve a lot of financial synergy assumptions based on similar transactions within your industry. These approaches largely identify duplicative roles, processes, etc. and identify a financial target for savings. This approach naturally takes a high-level approach but doesn’t consider the unique needs of your business. To accurately forecast synergy opportunities it should not be the only synergy view to consider.

Bottoms-up approaches, on the other hand, allow you to co-create opportunities with your l business stakeholders that consider business risk, culture, and ease to achieve.

I’ll provide more insight on how to properly prepare for a merger in a future article.

Wrapping It All Up

Follow these steps to properly optimize your current contracts:

  1. Identify your current state situation.
  2. Identify your high-spend suppliers.
  3. Gather benchmark data to see how your contracts stack up.
  4. Run an Opportunity Analysis to determine overlap and shelfware.
  5. Create a negotiation team.
  6. Optimize each contract as its renewal period approaches.

5 Tips for Negotiating a Salesforce Extension

In this article we will discuss how to successfully extend your current Salesforce contract in order to create additional time to successfully prepare and negotiate your renewal agreement.  For more detail, read our guide on negotiating with Salesforce.

​An extension is commonly needed whenever our clients engage us too late (i.e. too close to their contract renewal) and we need time to successfully complete the Discovery and Strategy Phases of our proprietary 4-Step Negotiation Plan.  

​Tip #1: Be Confident

We find that most of our clients have either rarely or never requested a contract extension with either Salesforce or any other IT Supplier. As such, this very basic concept becomes daunting for the average IT or Procurement leader as they don’t have either the experience, or past playbook, to execute with natural confidence. This sentiment is augmented by the fact that Salesforce will automatically inform you that they never allow extensions. If you’ve read our previous articles, then you’ll know this is yet another canned answer out of their sales playbook. Please know that extensions are granted all the time as long as you know how to ask for them…as such, they are considered the exception vs. the rule.  

Tip #2: Focus on the Facts

Share only what is necessary with Salesforce without going into too much detail. You don’t want to expend all of your negotiation equity during this process or you’ll end up hurting yourself down the road. Keep in mind that Salesforce will try and obtain as much information as possible during this stage so they can decide 1) whether or not to grant the extension and 2) to determine how prepared you are as an organization.  

‍Tip #3: Establish the Why

Like any human scenario, it’s always easier to influence people if they understand the intent and context behind any request. This scenario is no different as you’ll want to answer in a way that is authentic to your organization but intentionally vague in material content. Typical responses we find most effective are the following:  

  • Active interest in exploring new digital capabilities and need time to make internal decisions;
  • Internally restructuring the Salesforce relationship accountability;
  • Aligning multiple stakeholders within your organization to accurately capture the wants and needs over the next 5 years;
  • In the process of obtaining end user feedback and need some additional time to finalize, analyze, and make decisions, etc.  

Tip #4: Create a Timeline with Milestones

Salesforce will be far more willing to accept an extension request if they understand the timeline in which you plan on making decisions. This in a sense shows a partnership mentality which is both real and healthy. Develop a basic timeline of when you plan on making internal and external decisions that provides a good amount of cushion in favor of your organization.  

‍Tip #5: Keep your Promises

Constant and honest communication is key. All too often we find individuals/companies making the mistake of playing the power client position. In other words, the client exemplifies a lack of empathy or care for the sales process and holds all information back thinking that they are protecting their position. After years of research and proven experience we have repeatedly disproven that hypothesis. Instead, we find providing regular milestone updates to Salesforce (or any IT supplier) shows a level of commitment to the relationship and will pay dividends at the final negotiated deal.   Summary It’s important to recognize that each client scenario offers its unique challenges and opportunity. That being said, the guiding principles laid out above will prove effective no matter your situation. Be confident in your request, focus on the facts of your specific situation, build credibility with Salesforce by providing context into the request, set expectations via timeline with milestones, and deliver on your promises. We use these same effective tactics every day and hope you find them useful in your future endeavors.  

Summary

It’s important to recognize that each client scenario offers its unique challenges and opportunity. That being said, the guiding principles laid out above will prove effective no matter your situation. Be confident in your request, focus on the facts of your specific situation, build credibility with Salesforce by providing context into the request, set expectations via timeline with milestones, and deliver on your promises. We use these same effective tactics every day and hope you find them useful in your future endeavors.  

Key Points to Remember When Negotiating Your Salesforce Master Subscription

Customer Relationship Management (CRM) has become one of the most expensive IT investments for organizations around the world according to the annual “IT Trends Study” conducted by the Society of Information Management. ​

This IT investment growth is being fueled by two primary industry drivers:

  1. Large organizations are both replacing homegrown systems as well as utilizing their CRM platform to further connect their internal and external stakeholders, processes, and communication strategies; and,
  2. Small to medium-sized organizations are rapidly acquiring this technology to make a positive step-change in their customer interactions and client prospecting.

​While there are many Software-as-a-Service (SaaS) CRM platforms to choose from in the marketplace today, Salesforce continues to dominate the space. Subsequently, if you are looking at CRM solutions in the marketplace, you’re likely considering Salesforce as an option.

Why is Salesforce (SFDC) the market leader and what makes it different than the others?

‍While this article is not intended to be a tactical comparison of CRM solutions available today, our vast experience and focus on Salesforce naturally has revealed a few key points:

  • SFDC has been, and continues to be, very strong in outbound and inbound marketing tactics;
  • SFDC arguably was the first mover in defining a SaaS CRM solution that is decoupled from any other large enterprise agreement (ex: Microsoft, Oracle, etc.) making it easier to obtain;
  • SFDC developed a buying channel that is direct to a business end-user vs. going through a channel partner/value added reseller (VAR);
  • SFDC was founded with the intent of truly being a platform where vertical applications could easily connect and integrate (like the Apple App Store); and,
  • SFDC has perfected the sales process inside of organizations in a way that their divide and conquer sales tactics commonly identifies continues growth opportunities across the organization.

Why is negotiating a Salesforce agreement so difficult?

‍The funny thing is that the entire go-to-market model of SFDC makes it very easy to acquire licenses as needed. This is in fact one of the many elements that make negotiating with SFDC difficult. In other words, very often our clients come to us after they have identified SFDC has spread throughout their organization without their knowledge and/or with very little governance. Our clients often describe this situation similar to an “internal virus” (their words, not ours) that spreads organically at a very fast pace. The result of this unmanaged growth can lead to the following (by no means comprehensive):

  • Little to no license asset management leading to “shelfware” (acquisition of more licenses than are being used);
  • Incorrect license purchase creating higher costs than needed;
  • Different monthly subscription fees for the same license type;
  • Lack of an enterprise agreement leading to contractual risk (etc.);
  • No defined growth or utilization strategy; and;
  • A platform that is very difficult to disengage which drastically increases the internal cost of
  • change.

CIOs and IT Procurement leaders often find it difficult to negotiate a more favorable agreement when renewing their SFDC agreement.

‍We find the following to be the primary drivers:

  • Like other very well-known and established software companies, SFDC has developed a sales process that is very difficult to crack if you don’t deal with them every day (like we do); Find out more about this here.
  • The standard SFDC SaaS contract allows for SFDC to introduce price adjustments at any time;
  • If a client is reducing their license count, SFDC’s standard contracts permit higher per unit pricing;
  • SFDC sales leadership and staff are highly motivated to continuously drive revenue growth at existing clients;
    • To be explicitly clear about this, if a client’s contract is renewed with flat revenue, this is a very negative reflection on your account management team;
  • SFDC licenses are constantly changing; and,
  • SFDC account management changes (by design) every 6 – 18 months which naturally negates knowledge continuity, etc.