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

Why is it that companies are sometimes resistant to engaging with a cost savings firm like The Negotiator Guru (TNG)?  ​Furthermore, why is it that a company refuses to engage with an advisory firm (like TNG) after they know there is a guaranteed ROI? Is there any rational reason for this or is it purely an emotional response?We at TNG find ourselves asking these questions far too often…

We know humans can be complicated (😊), but we wanted to dig deeper into what sometimes appears to be irrational behavior that negates shareholder value creation opportunities.  As a result, we conducted ethnographic research on the cause of this behavior with the intent of identifying key trends, by persona. Here are a few of the key insights we discovered:

• IT Leadership (CIO, VP of IT, etc.) fears they will hurt the relationship with the software publisher/service provider leading to service degradation.  
• ​Purchasing/Procurement/Sourcing representatives have huge egos and thrive on taking credit internally. Furthermore, they are worried about their job security if someone else can achieve a greater result.  
• CFOs think they only way to achieve such savings is by changing vendors (ex: Salesforce to Microsoft) or by cutting products/services.  
• Business leadership think it will take too much time to achieve the prospective savings which will negate the realized ROI.
• Executives at publicly traded companies are generally risk adverse and think it’s safer to use a big 4 consulting firm (that’s already “in the system”) even though they will likely cost more and achieve much less (since they’re a generalist vs. specialist).

We’ve heard different variations of these key objections for years. What makes us most proud is that some of this feedback came from a few of our past clientele who decided to overcome their natural resistance as they knew what was best for their organization.  Per the recommendation of these past customer respondents, we've outlined what they experienced (vs. initial perceived resistance):

• Vendor Relationship – While it may be slightly uncomfortable at the beginning (depending on how much Right Sizing and/or Right Pricing opportunities TNG identifies), the vendor relationship and service quality improves at the conclusion of the TNG engagement. The vendor is engaged with the customer in a strategic manner and the customer can now feel confident they are only paying for what they need at a fair price.  
• Procurement Job Security – TNG acts like a force multiplier for existing Procurement teams. As such, TNG simply seeks to enable high impact results vs. seek credit.  
• Vendor/Product Change – Vendor changes are extremely rare. TNG simply identifies how internal stakeholders use the respective software platform (via their proprietary persona analysis) and identifies cost savings opportunities without sacrificing functionality/service quality.  
• Time/Cost to Achieve – Internal business stakeholders are rarely involved in the process after the Discovery phase is complete.  
• Niche vs. Generalist – The speed and consistency in which TNG can delivery results is a direct result of their focus and dedication focusing on their core competency, such as Salesforce.

Interestingly, our analysis identified the following key insights regarding business leaders' intention for engaging an outside advisory firm (summarized for brevity):

• IT Leadership sometimes feel uncomfortable being the “tough voice,” so they hire a 3rd party who brings the credentials to speak from an authoritative position.  
• C-Suite Executives simply want to motivate (prove to) their Procurement/Business Teams that the “great deal on the table” is not so great after all.  
• Procurement leadership wants to be armed with accurate price benchmarking or contract term knowledge. They recognize they can’t be experts in everything and value niche expertise from specialists vs. generalists.  
• Board members want to do anything possible to reinforce their fiduciary duty to their shareholders…this includes identifying, and executing on, every available cost savings opportunity.  
• Contract negotiators want to understand the software publisher’s sales playbook and internal incentive process…not just general market intelligence.  

We hope that you find these key insights helpful as you contemplate and reflect on your own personal resistance to engaging an outside advisory firm. TNG prides itself to make every engagement as risk-free as possible for our clients. Furthermore, TNG will only accept a client if we know there is a major impact opportunity…if not, we will simply give you some free advice.  Ready to explore joining the TNG family?  Contact us today to set-up a client intake assessment where we identify your cost savings opportunity for free!

What is Commerce Cloud

The Salesforce Commerce Cloud is one of the fastest growing segments within the Salesforce ecosystem of products and services. The Commerce Cloud provides an enterprise grade e-commerce solution that which is a direct competitor to e-commerce heavyweights including, but not limited to; Shopify, Magento (Adobe), SAP, Oracle, just to name a few.  

Since about 2018, Salesforce has highlighted the e-commerce cloud as a strategic growth channel for its existing customers. In other words, Salesforce has focused on deploying their “land and expand” sales strategies to deploy the e-commerce platform amongst its Sales and Service Cloud customers. There are clearly significant customer experience opportunities that can be enabled when e-commerce is connected directly to your CRM.  Ironically, the TNG team is engaged by both new and existing Salesforce customers to assist with commercial negotiations related to the on-ramp and off-ramp of Commerce Cloud. Our clients seem to either love or hate the Salesforce Commerce Cloud depending on their specific use case. No matter where you land on the love/hate spectrum, it’s important to understand key negotiation opportunities/risks that are specific to the Salesforce Commerce Cloud.  

History of SF Commerce Cloud

Salesforce acquired Demandware on June 1st, 2016 for $2.8 Billion USD. Some say that Salesforce was “forced” into the acquisition based on a synergistic customer portfolio (with Demandware), a lackluster homegrown solution filled with development challenges, and a competitor landscape (including Oracle, Adobe, etc.) who were making significant strides in the space.

In our opinion, Salesforce acquired Demandware primarily to purchase a pre-existing retail customer base that can be cross-sold Salesforce native functionality like Sales and Service Cloud. Salesforce had historically been lacking both North American and European retail customer penetration so this allowed an easy on-ramp.  Fast forward to 2021 and Salesforce is still lagging (compared to their normal market penetration) in retail customer acquisition globally. Furthermore, we have seen many legacy Demandware customers transition away from the Salesforce Commerce Cloud and migrate over to easier-to-use platforms like Shopify. Having the e-commerce competitive landscape in mind is important when exploring/negotiation a commercial relationship with Salesforce either as a new or existing customer.

Why these negotiations are different

Salesforce typically organizes their sales team by industry, region, and product line (cloud). Their sales team incentives are consistently changing but are largely established by industry and product line. Furthermore, customer pricing is influenced based on industry, annual contract value, and customer revenue.

To be most effective at any commercial negotiation it’s important to have as much data as possible. This includes identifying the supplier’s interests and best-in-class rates on a product-by-product basis based on your unique footprint. We call this our Right Price Benchmarking service which is included as part of our Full Negotiation Service or also offered as a standalone product for those that just want the data.  

Salesforce, and for that matter all e-commerce solution providers, are fully aware that switching costs from one e-commerce platform to another is an undesirable expense. They know that once they get you onto their platform that you will need to be really upset to create a reason to leave.  

The fact of the matter is that plenty of customers do leave Salesforce’s Commerce Cloud for one or multiple reasons. Our research, and real client experiences, have identified one consistent trend amongst those looking to leave: Out of control run costs.  

No matter whether you’re a new or existing customer to Salesforce it’s important to be as prepared as possible when engaging Salesforce. Take a look at the section below for some key insights specifically related to negotiating a Salesforce Commerce Cloud contract.

Key Insights/Tips

Now that you understand the history and key motivations related to Salesforce’s Commerce Cloud you should be able to apply the below key insights most effectively.  

• Salesforce is heavily focused on capture net new retail customers. Your Salesforce sales team is heavily incentivized to find and convert customers on existing e-commerce platforms.
• If you are a current Salesforce customer and exploring the Commerce Cloud, be focused on “lift and shift” credits from Salesforce that help mitigate any change costs. Depending on your situation, you can negotiate credits to be applied immediately, over the contract term, via discounts on other products, etc.  ​
  • It’s very important you conduct a thorough assessment of your options and the overall total cost of ownership impact of your potential options. For example, a one-time credit on the Commerce Cloud license fees may produce far lass benefit to your organization than a % discount on your existing license footprint with Salesforce.
• It’s important to understand who has decision-making authority inside of Salesforce. It largely depends on what you’re asking for, the overall relationship impact, and the attractiveness of you the customer. The only way to successful navigate the Salesforce ecosystem is to hire a firm that deals with Salesforce everyday and has ex-Salesforce employees (excuse the shameful TNG plug).  
• Literally 90% of current Salesforce customers that engage TNG are paying for more digital capability than they need. Those same customers are also overpaying for licenses that that they don’t even need. It’s very important you conduct a Right Sizing assessment to ensure you’re only procuring what you need.  
  • Specific to Commerce Cloud, this includes forecasting your Gross Merchandise Value (GMV) projections for each contract year.  
• Similar to the above point, our research empirically proved that 100% of our customers (no matter new or existing Salesforce customers) have committed to higher revenue targets than needed in the interest of “getting the best deal” without TNG support;  
  • This creates a material risk to the Salesforce customer when they don’t hit those targets.  
• Generally speaking, a longer contract term will drive a lower GMV price point;
• ​Even if you feel very confident in your GMV projections, focus on usage and price-point flexibility within your Commerce Cloud contract to eliminate surprises and capture cost savings if revenue actuals exceed projections.  
  • Note: If you are in an industry that is undergoing significant industry consolidation (M&A activity) then you should provide yourself the flexibility to acquire and/or divest mid-contract with Salesforce.

​Negotiating with Salesforce is more of an art than a science. It’s important that you understand all of the facts before negotiating with Salesforce. Please feel free to contact us for some additional helpful tips as you start to explore the Salesforce Commerce Cloud.  (And yes, we’re happy to help even if you’re in the 19th hour of negotiations 😊)

The Salesforce implementation phase can make or break a SaaS platform’s adoption rate and effective use for months and years to come.​

Resistance to change is to be expected, but companies need their employees to go all-in on understanding the tech, establishing new processes, and eliminating workarounds and legacy behaviors.​

Salesforce implementation costs vary widely depending on the size of the implementation partner (if you choose one), your total Salesforce spend, and how many custom features and processes are required. Implementation costs also vary based on whether you are migrating from an existing platform(s) or starting fresh. If you plan to implement an off-the-shelf instance with few customizations, average costs range from 10-30% of your total annual spend. On the other hand, a large company with extensive customization could pay as much as 50% of their annual spend. Integrating multiple disparate systems after a merger or acquisition can drive the price even higher.

​Start with Your Salesforce Roadmap

We recommend our clients begin building out a Salesforce roadmap six to nine months before negotiations. This process helps document necessary functionality, gain buy-in from internal stakeholders, and control the direction of negotiations from the beginning.

The Salesforce roadmap can also serve as a guide during the implementation process. It represents the project’s top priorities in terms of users, functionalities, and expectations; it sets the stage for a successful rollout.​

What if we are an existing company migrating to Salesforce from one or more platforms?

If you are implementing Salesforce to replace existing technology (“lift-and-shift”), the roadmap is more defined at the outset. Many processes are already in place, users have certain expectations about how their work should be done, and stakeholders know what outcomes to expect from these efforts.

A successful implementation should do more than replicate existing processes. Users should expect to adapt processes and habits to fit the new platform and achieve the desired outcomes more efficiently. (If not, why did we switch platforms at all?)​

“Lift-and-shift” implementations almost always cost the most, take the longest, and have the most risks involved. Implementation partners must be experts on Salesforce and any legacy platforms.

What if we are a new company or startup with no CRM?

New companies are challenged to build a roadmap with more limited information. Depending on the age and history of the company, it can take weeks or months to really understand what it needs from a technological standpoint. Strategies fluctuate; in many startups, marketing and IT departments do not exist as standalone functions yet.

These companies must define critical needs quickly, but they have one cost-saving advantage—they can build out business processes based on existing Salesforce functionality. There are no “bad habits” to accommodate that require custom development.

Regardless of whether you are implementing Salesforce for the first time or as a replacement, there are five important ways to keep implementation costs down.

5 Steps to Reducing Salesforce Implementation Costs

         1. Build your Salesforce Roadmap

Your Salesforce roadmap contains two basic pieces of information: what you plan to buy and when you plan to buy it. It is your guide for negotiating and will become your guide for implementation as well.

In many organizations, one individual serves as the Salesforce “project manager” leading this effort. This person could have any role in the organization, from Salesforce admin to CIO, but is the primary point of contact for the Salesforce rep. This does not stop the rep from reaching out to the C-Suite and VP-level leaders to build better relationships.​

The roadmap helps project managers achieve the internal alignment necessary to fend off Salesforce reps who contact multiple organizational stakeholders in hopes of influencing buying decisions. It empowers the Salesforce project manager and stakeholders to present a united front regarding what to buy right now, keeping negotiations focused on costs and business value rather than product.

         2. Your Introductory Rates Matter

Your initial negotiations with Salesforce will determine your rates forever. The rate you start with will be the benchmark for all future negotiations, a boon for sales reps who will jump at the chance to sell seats and modules you do not need yet.

Without a clear roadmap that identifies the types of platforms your company needs (Sales Cloud, Marketing Cloud, industry-specific clouds, etc.), the sales rep will take the opportunity to build a roadmap for you that best serves their sales and revenue objectives. To drive first-year revenue as high as possible, it will likely include many features and benefits you need, along with quite a few that you do not.

Features and benefits that are not business-critical as defined in the roadmap inflate your base price, affecting future negotiations. They will also inflate third-party implementation costs, regardless of whether you plan to use all the functionality at the time of implementation or not. Unnecessary features still take time and resources to implement, potentially deterring those resources from more important projects. Many Salesforce implementation firms bill by the hour, so every hour they spend on non-critical functionality is money wasted.

         3. Avoid Buying “Shelfware”

“Shelfware” is a term that describes software or licenses a company purchases but never uses. Software becomes shelfware in several ways. Perhaps someone saw a “cool” platform at a trade show, bought it, but never adopted or used it. Some companies buy software licenses at a volume discount rather than for an actual number of users. It is an outcome of classic price psychology—if you buy one, you get one more at 50% off. If you do not need two, is the half-off price as valuable as it looks? Rarely.

Salesforce account reps know how appealing a discount is, especially when they know their points of contact must get buy-in from multiple stakeholders. As mentioned above, Salesforce reps are highly motivated to maximize first-year revenue from new clients. They may drive the conversation by offering a bundled selection of platforms at some discounted rate. There is no rhyme or reason behind these discounts. They can be invented on the spot.

New companies are especially susceptible to paying for shelfware. When business processes are still evolving and companies are still working out best practices, it might make sense to license another platform or add a few more user seats in anticipation of future growth. It is certainly easier to do so in a room with an account rep; project managers must be proactive in sticking to the roadmap and focusing on immediate, defined technological needs. Companies must be intentional and specific when negotiating quantities, types of licenses, and the associated costs to keep initial spends reasonable, weed out upselling, and avoid wasting resources implementing unnecessary technologies. At the same time, Salesforce customers should take advantage of free trials, proofs of concept, and demonstrations to explore new technologies before buying.

         4. Require Clarity on Pricing Structures

Bundled pricing leads to shelfware which leads to wasted time and money. Salesforce has several tricks up its sleeve to create highly variable pricing structures across industries and company sizes. Your company’s annual revenue and annual Salesforce spend also influence pricing, but there is no way of knowing to what degree. There are no “best in class” rates; sales reps are trained to rebut these inquiries.

To avoid unnecessary costs, companies must require itemized pricing. Recently, we are seeing more and more deals that boil down to Salesforce offering X, Y, and Z for one discounted fee. This number does not necessarily represent anything; Salesforce uses a value-based pricing model where prices are set based on your perceived value of the solution.

Third-party rate data can help you better understand whether your rates are comparable to similar companies. Some Salesforce consulting firms have price calculators on their websites, but they are generally built on base rates as listed on the Salesforce website. Firms like TNG compile this data based on years of experience negotiating contracts.

         5. Keep it Simple

All SaaS implementation efforts have one thing in common—customizations equal cost.

This simple fact requires stakeholders to think carefully and critically about existing business processes and expected outcomes. The more your business can align processes with Salesforce capabilities out of the box, the lower implementation costs will be.

In many cases, companies fall into the trap of extensive customization. They create technical debt; more custom features require more internal and external resources to support Customization is not necessarily a bad thing, but many small- to mid-sized organizations do not need as much custom development as they believe. A thorough business process analysis in the beginning stages can help avoid costly customizations in the future.

Stakeholders and project managers must also take into consideration the employees working with these systems daily, how changes might impact the workflow, and how human elements of change management factor in. End users must be on board with the change; stakeholders must be sure that customization requests solve a business problem rather than accommodating a user’s (or department’s) preferences.​

Do I need a third-party Salesforce implementation consultant?

Organizations must decide whether they want to launch the platform themselves, add Salesforce’s implementation and customer success services to their deal, or hire a third-party consultancy. All have pros and cons.

A typical Salesforce implementation process includes business process analysis, data transfer from previous systems, custom development (if applicable), user testing and quality assurance, deployment, and ongoing user training and support. It is a heavy lift, even for large organizations.

If you choose to partner with a vendor, it is critical to find the right vendor for your needs. Large vendors may not provide small companies with the level of service or talent necessary to get the job done. While it makes sense for large companies to evaluate the big-name firms, they should prepare for higher costs with no relative increase in quality.

If you already have a consulting partner like Accenture or Deloitte working with your organization, they are strong choices for Salesforce implementation as well—they understand your business and already have strong relationships with stakeholders. Levering these existing relationships can ease the change management process.

Beyond technical proficiency, third-party firms help you manage the human element. They can help secure buy-in, speed up adoption rates and time to proficiency, and help you design workflows that optimize the use of the platform. They also optimize the use of human resources, allowing internal employees to engage with the process as needed without affecting day-to-day responsibilities.

For those who want to partner with a third party, we advocate for mid-sized implementation firms. They are large enough to provide the critical talent necessary for a successful deployment but small enough to prioritize the client-partner relationship and drive mutual success.

You can search Salesforce’s database of implementation specialists here. Brief pricing information is available below.

Conclusion

‍Numerous variables affect Salesforce implementation costs. At TNG, we believe companies need a clearly defined roadmap that aligns stakeholder needs and expectations before ever opening discussions with a Salesforce rep. The roadmap drives the negotiation process which ultimately drives implementation costs and time frames.