Stop Overpaying for Salesforce: A Practical Guide for CFOs and Business Leaders

Where your Salesforce money actually goes

When you see the Salesforce invoice, you see a single number. Behind that number, there are usually four cost drivers:

Licenses and editions

Extra products and add‑ons

Implementation and ongoing change work

Complexity: how hard and slow it is to change anything

Most discussions focus on negotiating a discount on the first line. That's useful, but if you don't address the other three, you usually just slow the cost increase instead of changing the curve. As a business leader, you don't need to know every technical detail – but you do need a simple view of where the waste sits.

Step 1 – Ask for one simple report: who actually uses Salesforce?

You don't need admin access for this. Ask your Salesforce owner or IT team for a very simple report:

• All active users
• Their role or department
• Their license type
• Their last login date

Then look at it with your business brain, not as a technical person:

• Who hasn't logged in for 30, 60, 90+ days?
• Are there former employees still listed as active?
• Are there people whose job clearly changed, but they still have a full Salesforce license?

In almost every company, this basic check reveals a group of users who are technically "active" but not really using the system. That's your first, low‑risk saving opportunity.

You don't switch anything off immediately, but you start a structured conversation: "Do these people still need this level of access, or can we reduce or remove it before renewal?"

Salesforce sells bundles – most teams use a fraction

One thing I've seen again and again: Salesforce is sold as "feature bundles," but most companies use a small slice of what they're paying for. Especially with add‑ons and extra licenses, it's very common that less than 10% of the available features are used in real life.

This doesn't mean Salesforce is bad. It means the commercial packaging and the real needs of your team are often misaligned. A bundle looks attractive in a sales presentation, but once the project is live, people go back to the 3–5 features that actually help them do their job. The rest quietly becomes paid shelfware.

As a CFO, CIO, Head of Sales, or founder, you don't need to understand every feature in the bundle. You just need to keep asking a simple question: "Which specific parts of this add‑on or license are we actually using today?" If the answer is vague, that's a red flag. It usually means you're paying for a lot of theoretical value, not real value.

A very practical exercise here is to pick one expensive add‑on or license type and ask your teams:

• What do you do with it in your day‑to‑day work?
• What would break if we didn't have it next quarter?
• Could we cover the same need with features we already own?
• And most importantly, How about if we can only pay for what we are using and for the full bundle.

Step 2 – Match license level to role, not habit

The second source of waste is giving everyone the "standard" or most convenient license, instead of the one that matches their role.

As a leader, you can guide this without going into system menus. Start from roles:

• Who truly lives in Salesforce every day to drive revenue?
• Who just needs to check information occasionally?
• Who only needs reports and dashboards?

The goal is not to make anyone's life harder. The goal is to pay for the right level of capability per role.

In practice, this often means:

• Frontline sales and service teams keep full licenses.
• Some support functions and management roles can move to lighter, cheaper access.
• Occasional users might not need a license at all if the process can be designed differently.

You don't need to design the solution yourself, but you can set the expectation: "By next renewal, I want every license category to have a clear business justification."

Step 3 – Audit the "extras" that quietly renew

Salesforce is rarely alone. Around it, most companies collect:

• AppExchange apps
• Integration tools
• Reporting or analytics tools
• Side products that were once "urgent"

These tools often renew automatically and sit in different cost centers. As a result, nobody looks at them as one picture.

As a CFO, CIO, or founder, you can ask for a one‑page overview:

• All recurring tools connected to or built around Salesforce
• Annual cost per tool
• A clear statement: which team uses it and what for

You're not looking for perfection. You're looking for things where nobody can confidently say "we still need this." Those are the candidates to remove or replace.

The rule I like to use: if no team can explain, in simple language, why a tool is essential, it shouldn't quietly renew.

Step 4 – Recognize that complexity is also a cost

There is a hidden cost that doesn't show up as a separate line item: complexity.

You feel it as:

• Long delays for simple changes
• Dependence on external consultants for every small adjustment
• Risk and anxiety around releases ("don't touch that, something might break")

Complexity means you pay more for every future change and every new idea. It also means your teams are slower, which is a cost even if it doesn't appear in the Salesforce bill.

As a leader, you don't need to design the architecture, but you can set a direction:

"I want a simpler Salesforce setup that our internal team can manage confidently."

"I want us to remove old, unused processes and customizations instead of piling new ones on top."

Often, a cost‑reduction project is the best moment to also reduce complexity, because you're already questioning what you really need.

Step 5 – Don't start the conversation 4 weeks before renewal

One of the most expensive habits I've seen is starting to think about Salesforce only when the renewal email lands in the inbox. By then, your options are limited: you can ask for a discount, but you can't fundamentally change what you're paying for.

A better rhythm looks like this:

• 6 months before renewal: basic usage and license analysis
• 3–4 months before renewal: decisions on which licenses and add‑ons you really need
• 1–2 months before renewal: negotiation, backed by facts

This doesn't have to become a huge project. But putting Salesforce on a simple, predictable review cycle gives you control instead of surprises.

A realistic, pragmatic plan for the next 90 days

If you want something concrete to start with, here is a 90‑day plan you can drive as a business leader:

Month 1

Ask for the user and last‑login report.

Identify obvious inactive or low‑usage accounts.

Decide which ones should be reviewed or removed.

Month 2

Ask for a license‑by‑role view.

Challenge mismatches where the license looks much heavier than the role.

Set a target for what you want your license landscape to look like at renewal.

Month 3

Get a list of all recurring Salesforce‑related tools and add‑ons.

Agree with your team which ones are clearly essential, which are candidates for removal, and which need deeper review.

Align this with your renewal timeline.

You don't have to reach 100% optimization in one round. Even getting the basics right can already free up budget and reduce surprises.

How I can support you

My background is not as a salesperson for any particular tool, but as someone who sat inside companies and had to make these systems work within real budgets and real constraints. I've seen Salesforce used very well, and I've seen it become a slow, expensive burden.

If you want an outside view that speaks both the language of technology and the language of finance and sales, I can help you review your current setup, show you where the hidden costs are, and outline a realistic plan to reduce spend without disrupting the business.