Software Audits from Oracle, SAP, Microsoft, and Salesforce: What You Should Know

Getting an audit notification from your software provider can be nerve-wracking, but after reading this you’ll realize this is less likely due to something you’ve done wrong and more likely a tactic to throw you off-course.
If you’ve never been through an audit before, you don’t know what to expect, what to do, or how to make sure it’s over as quickly as possible with minimal expense to your organization.
In this article, we’re going to make all this crystal clear by outlining the audit processes of large enterprise software providers like Oracle, Salesforce, SAP, and Microsoft. There are a few key things you need to take into account that apply to all of these providers: ● Use your contract as your best weapon to defeat audits. Take action if there is any sort of grey space in terms of what is allowed by the supplier.
- Use your contract as your best weapon to defeat audits. Take action if there is any sort of grey space in terms of what is allowed by the supplier.
- You’ll do best if you bring in outside assistance. An expert who has experience guiding businesses through software audits will be a huge help throughout the process.
- You need to control all the information that is shared with the supplier in your own format and spreadsheets.
- The more you are proactively sharing information with suppliers, the less basis they have to bring up an audit.
- Audits are brought forth to customers for many commercial reasons. The more proactive you (the customer) are with sharing information, addressing audit risks in meetings, and creating a paper trail, the less likely your supplier is to audit you.
What is a Software Audit and How Did Your Company Get Selected for One?
A software audit is both a technical and contractual review of your organization’s use of a specific software platform within your IT environment. Most large enterprise software companies like Oracle and SAP have separate departments that focus purely on license compliance audits. These teams look and feel like a shared service organization inside of a large software company. They work with a customer’s account management team to take an aligned, yet separate and distinct, position on behalf of their software company. We will discuss the similarities and differences between these different teams later in the article.
One common similarity across all of these suppliers is that the audits will compare your usage and processes to any specifications, standards, or contractual agreements in place.
Why your company? Why did you get singled out for an audit?
There are three primary operational/contractual triggers for a software audit:
- If there is any sort of consumption-based pricing in your contract;
- If you have any sort of restricted-use license in which you are only allowed to use a license for certain functionality; or,
- If you have recently acquired or divested a company.
While not mutually exclusive, you’ll also find the timing of these audits is very suspect and robotic in nature. The two primary timing triggers are:
- Anytime a large software company needs to identify “unearned revenue” to meet quarterly revenue targets; and,
- A pending contract renewal.
These large enterprise software companies know that it’s very common for their customers to be out of compliance due to the sheer size and scope of their operations. This is augmented by the fact they know anytime there is employee turnover within a customer’s IT organization (especially their “software asset management” department) the company is susceptible to additional compliance risk as a result of lost tribal knowledge of the environment, past internal audits, etc.
Taking all of this into consideration makes it relatively easy to understand why a company like Oracle can confidently predict net new revenue from their existing client base.
In addition to market pressure for additional revenue, a customer’s upcoming contract renewal also serves as an all too common trigger. The general rule of thumb we tell clients is anytime you have a contract renewal coming up nine to twelve months, your supplier is likely to introduce an audit. Your supplier will use this as an opportunity to distract you and gain the upper hand in an anticipated contract negotiation that hasn’t even started.
Suppliers do this because it automatically puts you in a defensive position. Naturally, you will be forced to concentrate on defeating the audit instead of allocating that same time to figuring out what you need for the upcoming contract renewal. They want to gain as much leverage and understanding of your business as possible before going into a renewal negotiation.
The audit is merely a tactic large software providers use to 1) seek out unearned revenue for their company to meet revenue targets and 2) gain the upper hand in your contract renewal negotiations in the hopes of minimizing any revenue loss from your account.
The fact of the matter is that it’s very common for customers to be unintentionally out of compliance. Knowing this, it’s important you know what to do in order to defend your company from what is potentially a very costly situation.
Here’s an example to help illustrate this tactic
By way of an audit, an ERP provider could discover you are misusing the license, giving the supplier reason to charge you a larger fee. Often, sales revenue targets for these audits are about 30% of your annual maintenance/subscription costs.
Let’s say you are spending $1M on core licenses, the audit will likely lead to around $300k in costs on top of that. If you can defeat the audit and keep your core license costs at $1M, then you will be happy and reward yourself for fending off the extra charges. In reality, the supplier didn’t expect the $300k in the first place, the audit was just a way to distract you from putting time and effort into your upcoming renewal negotiation.
It’s a win-win situation for them - if they win the audit, they put the money towards their sales revenue to meet their quota; if they don't, they’ve distracted you from being prepared to save money on your upcoming contract negotiation.
As a sales rep, finding new business is much harder than auditing an existing customer. Suppliers will target big companies because they don’t have perfect internal controls and mistakes are likely to happen.
What to Do When You Get an Audit from Oracle
When Oracle conducts an audit, they engage their License Management Services (LMS) team to run the process.
The audit process often involves installing software code within your secure environment. It is a listener software that will hit your mainframe servers and figure out how many other systems are connected.
This is important because, historically for this on-premise software, you are licensed based on the interconnectedness of both physical and virtual server environments. Your supplier wants to know how much “value” you are getting from their platform so the software they install provides a report of how many systems are interconnected. In a nutshell, the software delivers a report that illustrates when your technical architecture is in non-compliance. This automatically gives Oracle the upper-hand as it forces the customer to validate the information.
The best tactic to defeat this process is to never allow the software in your environment to begin with.
You have the right to refuse listening software within your Oracle contract.
Unless your contract explicitly calls out installing software, tell Oracle that installing software does not comply with your IT security protocols.
Look to determine if you have audit language specified in your contract. The older the contract you have with Oracle, the more likely you have the right to refuse the audit, or to at least not allow the listener software to be installed within your environment.
If this is the case, tell Oracle that instead of installing the software, you will run the audit yourself using their tools and spreadsheets with no software included. This means you are in control of what information is being shared with Oracle. Controlling the information is incredibly important in any audit, especially when suppliers are involved.
What to do when Salesforce Conducts an Audit
Salesforce audits customers when there is a restricted-use license available. When this happens you need to think critically about negotiating with Salesforce.
Salesforce is Software as a Service (SaaS) in the cloud which means they have more ability to freely monitor your utilization of licenses within your environment and can freely audit for misuse.
When you have a Restricted Use License (RUL), you have permission to use the product for a specific business purpose leveraging a certain number of standard and custom objects. Standard objects are modules within the Salesforce platform, such as contacts, accounts, or prospects. A custom object is something that was built by a Salesforce developer specifically for your company.
The license limitations in an RUL are a contractual limitation, not a technical one. A contractual limitation means there is legal language on your Order Form specifying how the license may use a predetermined number of standard/custom objects even though there is a set quantity limitation, technically there is no way to shut off access to other custom objects for that user.
This license is often in place for a subset of users who only need limited access to your tool. For example, an employee who is only viewing the data and not editing it. If this group starts editing objects, it becomes in and of itself a compliance issue.
Salesforce makes it easy for the end-user to accidentally do this without realizing they are in breach of the license. They will use this opportunity to accuse you of using the license incorrectly and request that your organization upgrade these licenses to full users and will seek compensation since the inception of the misuse. Contractually, Salesforce has the right to charge you full retail price for those non-compliant users.
Another time when Salesforce audits come into play is when a client is on a SELA Agreement (Salesforce Enterprise License Agreement).
How do you get around Salesforce RUL audit problems?
The best thing you can do is to establish quarterly check-ins with your account team at Salesforce. Use these meetings to stay on the same page with your account team and create a paper trail that shows how your users are engaging with the platform.
If you are accused of breaching restricted use, but have established quarterly check-ins with a paper trail, you can respond to Salesforce by saying “We met with your team and they didn’t bring anything up during our meeting so why should we believe you now?” Without quarterly check-ins and a paper trail, you get into a he-said-she-said argument.
Often times, the employee in breach of license may have accessed the wrong objects once or twice throughout the life of an account. Salesforce will create an argument that the license has been systematically misused for a long period of time.
We treat this event like a litigation. If you don’t have a paper trail of record, then you have no legal foundation for a defense. When comparing the perspective outcome of the party that has records and the other that does not, the person with records almost always wins in court.
Keep careful documentation about your interactions with Salesforce, and have open conversations about audit and license use risk. This will build a strong foundation and reduce the risk of an audit.
How to Handle an Audit from SAP
An audit by SAP is very similar to an audit by Oracle in that, historically, their licensing model is primarily “consumption-based.” This means your price is based on your company’s revenue, profit, services used, how many suppliers you have, or any number of a series of variables.
This model falls under the concept of Value-Based Pricing and is a subjective assessment of value captured from the utilization of the software.
SAP will use many of the same tactics as Oracle which we’ve outlined above. One thing to specifically note about SAP is that they very frequently introduce audits during merger & acquisition (M&A) announcements. When supporting clients with M&A IT Sourcing, we commonly tell our clients to “get ready for the ‘ransom letter.’” These aren’t our words but rather those of our clients who received notifications from suppliers such as SAP immediately after announcing a large acquisition to the market.
Want to know if you’re susceptible to these ‘ransom letters?’ Take a look at your contract and keep an eye out for any language within your contract that indicates they will “readdress the terms of the contract if you the customer acquires or divests entities during the term of the contract.” If you have this language within your contract you will more than likely receive a similar notification within 1 month of publicly notifying your M&A intent.
In order to defeat an SAP audit, take the same approach we would take with Oracle and then protect yourself moving forward by changing your pricing model to a fixed baseline model that is attached to the reasonably certain variables in your company such as the number of employees.
What to Do When Microsoft Audits You
Microsoft’s audits vary depending on the products and services within your contract. Similar to Salesforce, Microsoft will commonly focus on those licenses that have restricted use. A very common audit for those clients with perpetual Microsoft Office licenses is the 1-to-1 validation of windows desktop licenses to computers within a customer’s environment. Similarly, for those clients with an active Office 365 subscription, Microsoft will look closely at the utilization of subscriptions that are inherently limited in their intended use. This is augmented by a deep analysis of computers and users in your ecosystem to ensure the capabilities being used are properly licensed.
If you are paying for any physical or virtualized servers from Microsoft within an SCE agreement, you will commonly be audited to ensure your consumption metrics are within your contracted allocation.
Frequently with Microsoft, you are leasing the utilization of servers either on-premise or in the cloud. Generally speaking, if you have a physical piece of hardware from Microsoft on-premise, they will almost certainly conduct an audit at renewal time to monitor utilization as part of their “optimization analysis.” In a nutshell, they will try to move you from an on-premise environment to the cloud.
Conceptually this is fine but they will use that audit as leverage to do a lift and shift into Microsoft Azure.
Microsoft Azure is a very attractive product for the sales team because they are heavily incentivized to get your company into the cloud. The market is looking at how Microsoft’s cloud growth is going year after year and as a result, the company wants to increase its usage.
Essentially, Microsoft will audit to try and sell you on Azure. This isn’t necessarily a bad move to make but knowing key motivators will keep you ahead of the game and alleviate any potentially detrimental surprises.
What Happens Next?
If you’ve been audited by any of your enterprise software providers, we recommend bringing in outside help to guide you through the process. Leveraging their experience and expertise will go a long way to mitigate both short and long term risk that can easily rise into the millions.
Don’t solely believe what your account executive is telling you, oftentimes they don’t have all the information needed and they are heavily incentivized by their employers.
Your outside expert will be able to comb through your contracts, identify risks/opportunities, and drive both cost savings and containment. With the proper assistance, you’ll be able to confidently stand your ground and mitigate risks before they are realized.
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

How to Create a Salesforce Roadmap
In previous articles, we shared with you how the Salesforce machine operates. We shared with you how it structures its organization and the tactics it uses to maximize its revenue from your company.In this article, we are going to dive into your single most important weapon against Salesforce in your negotiation . . . Your Salesforce Roadmap.
What is a Salesforce Roadmap?
Simply put, a Salesforce Roadmap is nothing more than a table outlining:
- What you are going to buy
- When you are going to buy it
This sounds simple, yet most companies don’t go into a negotiation with Salesforce clear on these two points. As a result, Salesforce hijacks the conversation and creates a roadmap for them.
What you are going to buy
This question isn’t always as simple as it sounds.
Do you need Enterprise or Unlimited?
Do you even need premium support? Or would that money be better spent on a 3rd party consulting firm?
Have you run a utilization report to see how many of your licenses are actually being used?
Is marketing actually using that instance of Pardot you purchased three years ago?
The “what you are going to buy” conversation isn’t always easy. One company we worked with ran a utilization report to find that only 63% of their licenses had even been logged into in the past year. This means they were paying for 37% more licenses than they actually needed!
Another customer realized that a large portion of his organization could get by through downgrading to a lower license level. They were only using basic features that didn’t require them to be at the Unlimited License.
It’s easy to think you know exactly what you need going into a negotiation, but sometimes you need to do a bit more digging into understanding how each department actually utilizes the tool.
When you are going to buy it
Another common tactic Salesforce uses is to tell you that you cannot roll out licenses over the course of a three-year contract. Your rep will tell you that you need to buy them all up front now if you want to get a discount.
This ironically always works out in Salesforce’s favor as the added revenue from those dormant licenses makes up for the discount one rates. The truth is you can negotiate to roll out licenses at set periods of time throughout your negotiation.
In order to do this though, you need a clear roadmap and to create confidence with Salesforce that this is what you actually need and when you need it.
Why Is Building a Salesforce Roadmap So Important?
Before we dive into how to create this roadmap, let’s first dive into explaining why this roadmap is so important.
A roadmap is your best defense against divide and conquer
Remember the divide and conquer tactics we described in our guide on negotiating with Salesforce? We shared with you how Salesforce will make contact with multiple individuals and decision-makers throughout your organization.
Its goal with divide and conquer is to create conflicting stories which develop chaos in terms of what you actually need.
Creating your own Salesforce Roadmap helps you prevent against that.
When you create a roadmap and get buy-in from all your key stakeholders on that same roadmap, you create alignment within your organization. In addition to the roadmap, we are also going to give your internal stakeholders key talking points on what to say if Salesforce approaches them. It’s also important to know that timing is everything with regards to these key messages.
As a result of being aligned on talking points and what your organization actually needs, your organization begins to speak from one voice. Instead of having Salesforce gather conflicting stories from each department, they suddenly are left dumbfounded when they receive the same story from all contacts within the organization.
Flip-flopping your wants in the negotiation focuses the discussion on the wrong things
Whenever you don’t have your roadmap aligned, you spend your time in the negotiation with your rep going back and forth on how many licenses you need or what add-ons you do or don’t want.
Every time you go to your rep with a revision on your renewal because you and your team changed your mind, you are wasting a valuable chance to negotiate a key term or reduce your rates.
Without a roadmap, you will end up flip-flopping on what you want during the negotiation and spend your time focused on what licenses you are even going to buy instead of the price point or the terms. The entire negotiation gets focused on just figuring out what you need instead of getting you the best rates.
Your roadmap creates that clarity and alignment and lets you spend your time focused on getting you the best deal.
A lack of alignment undermines the key contact of the negotiation
Imagine for a moment that you are a Salesforce rep. You go into conversation with the Salesforce Admin who is your main point of contact in the negotiation. The Salesforce Admin request a 20% license count increase but is not interested in adding any new products or expanding their Salesforce footprint into any new departments.
Then two days later, your sales management team comes back from a basketball game with the CEO of your client organization. They tell you “we just met with the CEO, he wants to roll Salesforce out to his entire marketing department as well.”
As a Sales rep, you immediately jump to the conclusion that your Salesforce Admin is not the authority or decision-maker on this account. All respect you had for this Salesforce Admin’s decision-making ability has gone out the window.
As a result, that Sales rep treats the Salesforce Admin differently in the negotiation. He starts going around them and maximizing his divide and conquer tactics because he knows the Salesforce Admin is not in charge.
This is what happens when your organization is not aligned.
It undermines the individual who is the face of the negotiation. It doesn’t matter if it is a Salesforce Admin, CIO, or CFO.
Alignment and a roadmap gives power to the negotiator
Let us imagine another scenario for a moment here. Imagine that you are a Salesforce rep. You go into a conversation with your Salesforce Admin who is your main point of contact. The Salesforce Admin tells you they want to increase sales cloud licenses by 20% and consider a demo of Pardot in their marketing department.
Then two days later, your sales management team comes back from a basketball game with the client CEO. They tell you “we just met with the CEO, he wants to grow his licenses by 20% and is considering expanding Pardot into their marketing department.”
As a Sales Rep, you just heard consistency.
You heard that your Salesforce Admin is aligned with the CEO.
You heard that your Salesforce Admin is actually in charge of this negotiation.
When you have organizational alignment on your roadmap, it gives power to whoever is running your Salesforce Negotiation. It doesn’t matter of it is the Director of IT, CIO, or CFO. Whenever you have that alignment of stories, it gives that person in the negotiating seat power to drive the negotiation on their own.
When to Create your Salesforce Roadmap
We typically recommend companies start building their roadmap six to nine months prior to their negotiation. You are going to want at least three months to handle the actual negotiation with Salesforce so a six month runway gives you an additional three months to get that internal alignment.
Each organization is different, but that internal alignment won’t happen overnight. Give yourself some time to meet with all key stakeholders and achieve that internal alignment.
Three Steps to Creating your Salesforce Roadmap
A Salesforce Roadmap is not complicated. It is a simple table of “what you need” and “when you need it” over the next three to five years.
Even though most Salesforce renewals are only three years, it is helpful to plan five years in advance so you can think of a bigger picture of what may be coming down the line. This helps you in creating an aligned story for Salesforce at your renewal.
Step 1) Create a rough draft alone
If you are reading this, chances are you are the one who is driving the Salesforce negotiation. You have extensive knowledge of Salesforce and can probably fill out 80% of the roadmap on your own.
The key in this step is to document all of your ideas for the roadmap on paper.
You don’t want to go to your key stakeholders with a blank slate and build the roadmap from scratch together. That is not a good use of their time, and it is going to create too much debate.
By crystallizing your thoughts about Salesforce into a rough draft of the roadmap, you can share that document with others. It becomes a starting point for the entire roadmap discussion.
Step 2) Take the rough draft to key stakeholders for feedback
This rough draft of the roadmap is purely for internal use. Once you have this rough draft complete you are going to present this document, typically in the form of a PowerPoint presentation, to your key stakeholders within the organization.
This may be your CEO, CFO, CIO, COO, VP of Sales, Director of IT, Salesforce Admin, Sales Management Team, etc.
You are going to take this roadmap to them and say “This is what I believe our 3-5 year Salesforce roadmap looks like...what feedback do you have?”
As you go into these meetings you may find yourself saying, “I have an idea here but I don’t know exactly what X department needs.” This roadmap and these conversations are meant to help you refine the roadmap and clarify those needs with each department in the organization.
What is great about this step of the process is that this allows your team to have internal dialogues about what you need with Salesforce. Without doing this internal roadmap, these contacts would not be brought into the conversation until a contact from Salesforce had reached out to them.
Instead of letting Salesforce guide these conversations, you are getting in front of them and taking charge. This helps you own and drive the conversation.
Step 3) Gather all feedback and refine your roadmap
Once you have gathered alignment from each of your key stakeholders on the roadmap, you are going to want to take some time to sit down and refine that roadmap into a final polished version.
At this point, you are almost ready for entering the negotiation. But before that we need to build a communication strategy and negotiation plan.
Lastly, it's also important to realize that a Salesforce Roadmap is essential for SELA Agreements (Salesforce Enterprise License agreements). Read our guide for more details on how to renegotiate your SELA Agreement.

Confidential Clients: Why We Do It
For those of you wondering why we keep all of our clients confidential, our Founder and Senior Partner Dan Kelly provided a few key insights as part of a recent interview. We hope you appreciate learning why this is such an important guiding principle for TNG.
Moderator: Keeping your clients confidential is a pretty bold and respectable move… Why does TNG do it?
Dan: It’s a great question and one that comes up often during initial conversations with our prospective customers. We find that customers are more curious as to the reasoning versus questioning the legitimacy.
We treat each engagement with a customer as if it were a legal proceeding. We find that our ideal customers really appreciate how sensitive we treat our collaboration with their company and their most senior stakeholders/leaders.
From a logistical standpoint, some customers reach out to us when they are trying to commercially mediate what appears to be a potential legal situation with an external vendor. 95% of the time, we can handle the situation via commercial negotiation. If the situation does require any sort of legal support or litigation, our team is ready to quickly support and collaborate with our customer’s legal team based on our strict confidentiality and document handling standards.
Moderator: Did your background in the FBI contribute to your decision on this approach?
Dan: {Laughing} Yes, I think it probably did. There were two things that I was taught immediately upon entering my FBI career: 1) Before you make any questionable decision, think about how the outcome of your decision would look on CNN the next morning and 2) Classified information is best protected on a compartmented, need-to-know basis.
While our entire team doesn’t come from an Intelligence Community background, everyone is provided training on the importance of confidentiality and the proper procedures for protecting client confidential materials. I can confidently say, without a doubt, that our customer data and processes are more secure than most multinational law firms.
Moderator: When you have prospective clients looking to speak with references, aren’t you afraid of losing potential business if you’re not willing to share your client portfolio?
Dan: You know the business owner in me honestly thinks about this a lot. From an actual data standpoint, we know that if a prospective customer chooses not to work with us, it’s primarily due to cost and not caused from the lack of reference calls.
Another fact that we’ve proven over the years is that 3 out of 4 clients request repeat or ongoing support, so any lost opportunity from this topic is naturally superseded with our repeat customer business. That’s how I would prefer it anyway, as taking on a new customer brings its own inherent risks… it’s a two-way street.
Moderator: How do you make clients feel comfortable working with you if they aren’t able to speak with references?
Dan: My answer on this is simple: Everyone has friends. Do you honestly think any salesperson, no matter what industry, is going to refer you to a client that has had a sub-optimal experience? I am a Strategic Sourcing Expert, and so is the rest of the Service Delivery Team. When we worked for large companies, we often were told to ask for references. However, whenever we received reference contact information, we rarely called them to validate. This reference gathering process is an old school purchasing process for process sake, and we find our best customers find more trust in the fact that we were ranked as the 2nd fastest growing company in Minnesota by Inc Magazine.
Moderator: What are some other benefits that might not be apparently obvious of keeping clients confidential?
Dan: Excellent question... This is a passionate topic of mine of which I could honestly discuss for an hour. In the interest of brevity, a few of the top benefits include:
Ease of Contracting – No Publication
Most of our clients are very large multinational organizations. The Marketing and Legal departments inside of these companies are naturally very protective and risk adverse (for good reason) of their name brand, logo, etc. Since our customer contracts don’t include any language regarding “publication,” it eliminates unnecessary administrative burden, and legal review cycles, on both sides of the transaction.
TNG Client Protection
Most of our clients request that TNG be a covert silent advisor in the background (instead of an overt legal agent of the company). This means that the supplier in which our customer is negotiating with should never have knowledge of our involvement. By keeping all clients confidential, we eliminate any risk of the supplier later discovering our involvement.
Deter Sales Snooping
Without going into too much detail here, just know that large software companies have an incredible amount of financial resources. They employ individuals to be assigned, or even sit in, your organization to learn everything there is to know about your company in the interest of upselling their products and services. This also includes learning as much as they can about what companies are using external advisors to benchmark rates, processes, etc.

7 Most Common Mistakes to Avoid When Negotiating Your Salesforce Agreement
We commonly get the question: “What are the most common mistakes and/or things to avoid when negotiating a Salesforce Agreement?” So much actually that we thought it made sense to write a short article for all to consume.
A Customer Relationship Management (CRM) platform is commonly within the top 5 expenses within every CIO’s annual budget. The day-to-day operations of business serve as a natural distraction for all of us and, if you don’t negotiate contracts all day long, it’s near impossible to know all the information you need in order to successful prepare and execute a negotiation strategy. Negotiating a Salesforce contract is tricky and can be extremely complex. Don’t underestimate the time, effort, or expertise you’ll need, or you’ll quickly lose control of the entire deal.
Here are the 7 most common mistakes we find CIOs and IT Management Teams make when negotiating their Salesforce agreement:
1. Failing to prepare
While this may not come as a surprise, the single most common mistake is failing to allocate enough time, resources, and expertise to properly prepare for the negotiation.
Ask yourself this: Would you ever go to a car dealership and take the first car they offer without first doing your research on price, warranty, etc.?
As a CIO or IT management team, you should not make assumptions or rush through the process of finding and/or negotiating your CRM platform. No matter whether you are searching for a new CRM platform or simply renewing your existing agreement, make sure you take time to understand the business and digital capabilities you are looking to acquire and/or augment. Take time to conduct interviews across the organization and create a business canvas of those needs to create a simple viewpoint of the wants and needs of the entire organization.
We advise our clients to start 6 months prior to any anticipated contract execution date.
2. Failure to look at the bigger picture
We find CIOs, IT Management Teams, and Salesforce administrators are great at thinking about the relatively short-term needs of their organization but commonly forget to keep the big picture in mind. As with any strategic supplier relationship, you need to think about how the pricing, requirements, and relationship with Salesforce will look over the next 3-5 years. Instead of looking at the short term, think strategically about your organization's goals and the relationship you want to build. You need to approach your CRM vendor with a long term mindset. Look at how their services will be beneficial to your organizations in terms of growth and transformation. Make sure you prepare a compelling forward-looking strategy that is deliberate in identifying how the Salesforce relationship will benefit your business. It’s equally as important to understand how Salesforce views its relationship with you. Only after both sides understand the current state of each organization can it build a plan forward.
3. Focusing too much on price
Our clients are almost always surprised when we say this statement. While price is ultimately very important in any commercial agreement, it’s equally as important to validate that you have the proper products and services for your organization.
“Right Size for the Right Price” – Dan Kelly, The Negotiator Guru
If you’re a new customer, make sure you’re not overbuying at the start…remember, adoption always proves to be slower than you will anticipate when introducing a new CRM platform.
Subsequently, it’s all too common for the sales team to overweight your 1st year agreement as they are solely focused on capturing as much revenue as possible from your account.
If you’re an existing customer, conduct an internal audit of your products and services that are currently part of your Salesforce ecosystem. Make sure not only these products and services are being used (the easy part) but also that they’re being used appropriately. Very often we’ll find opportunities for our clients to downgrade while still achieving the same business functionality required.
4. Not considering all your options
It’s important to keep a pulse on the marketplace…there are multiple CRM platforms out there and while Salesforce is the industry leader they may not be the best fit for you.
Subsequently, if you are a current Salesforce user then it’s equally as important to conduct a deep dive assessment on how other peers in your industry are using Salesforce. A properly run CRM platform should not only optimize the sales process but also drive efficiencies in back office operations, etc. If you identify (and you most likely will) new areas where Salesforce can assist your business, carefully bring this up as an opportunity during the negotiation process. Again, we urge the word “carefully.”
5. Not developing Executive Level relationships
As written in previous articles, Salesforce has set-up its very own incredibly effective sales machine. While we won’t reiterate the previously written articles it’s important to call out that most Salesforce customers underestimate the importance of developing and engaging VP level and higher relationships at Salesforce. Only these levels have decision making authority on your account. If these individuals are on your side, and understand your story, you’ll be far more successful in your negotiation.
6. Failure to create a strategic internal communication plan (as part of your negotiation strategy)
Almost everyone fails at developing a bulletproof internal communication plan. While the saying “speak from one voice” is widely used and understood in negotiations, it’s not enough to simply rely on human beings to say exactly the same thing at the same time. Instead, we advise our clients to develop a communication plan that provides key talking points for different levels of the organization. These talking points all align to the same objective but are developing in a way that reinforce message authenticity for that specific stakeholder.
7. Neglecting to include your C-Level Executives in the negotiation
Related to the previous point, we find that the majority of organizations we advise have historically tried to limit and/or eliminate any C-Level interaction with Salesforce. This is naturally understandable (based on common thinking) but actually a serious mistake.
Salesforce takes great pride in, and places great importance on, developing relationships directly with their customer’s executive team.
We advise clients not to fight this point but leverage it. We admit that we used to get this point wrong ourselves. We used to ensure the C-Suite knew not to say anything and only redirect messages to a single point of contact. The big problem with this is that the c-suite really likes to talk! Instead of fighting this natural instinct (and skillset) we advise our clients to leverage it by creating a C-Suite communication and engagement plan that empowers the negotiation plan.

