Part 1: Nobody in the Room Is Neutral
Around this time of year, a particular kind of meeting starts appearing in calendars. The Salesforce renewal is coming up. The finance director wants to know why the number has gone up again, and somebody has been asked to pull together a view on what the business should be buying next year. Around the table sit the people you would expect. There is the account executive from Salesforce, and perhaps the partner who built the system. There is the admin or platform lead, the senior leader who championed the original purchase, and someone from finance holding the contract. Everyone is capable and everyone is well-meaning. Within forty minutes the conversation has moved from “is Salesforce worth what we pay for it?” to “what should we add next?”, and nobody in the room can quite say when that happened.
I became an accidental Salesforce admin at a drinks company in 2012, went independent in 2014, and since then I’ve worked with thousands of users on projects in more than a dozen countries. I’m also a Trailhead Academy Certified Instructor. Most of my career has been spent in the space between the people who make decisions about Salesforce and the people who have to live with those decisions every day. In that space you learn to notice something the meeting room rarely notices about itself: everyone around the table is giving advice, and almost none of that advice is neutral.
I want to be careful here, because this isn’t an argument about bad people. I work alongside partners, account teams and admins, and the vast majority of them are good at what they do and genuinely want their customers to succeed. The problem isn’t anyone’s character. It’s that every person in that meeting is rewarded for something, and when you lay those rewards side by side, they almost all point in the same direction.
Start with the account executive. Their job is to grow the account, and their targets reflect that. There’s nothing hidden or sinister about it; it’s what the role is for. But it means that a renewal conversation is, from their side, also an expansion conversation. This year the expansion has a very clear shape. There are new AI editions, there’s Claudeforce putting Salesforce inside Claude, and there’s a steady stream of announcements suggesting that the organisations who move first will pull ahead. An account executive who walks out of a renewal having sold you nothing new has, by the measures their employer uses, had a quiet meeting.
The implementation partner is rewarded differently but leans the same way. A partner’s business is built on projects, and projects are built on things that need building. If they look at your organisation and the honest diagnosis is “your people don’t know what they already have, and two days of showing them would solve most of this”, that’s a perfectly good piece of advice. It just isn’t a project. It’s very hard to staff, scope and invoice for something that small, so problems tend to get described in a way that has a build at the end of them. Again, this isn’t dishonesty. When your business model is construction, everything you look at starts to resemble a building site.
Then there’s your own technical team, and this is the part organisations least like to hear. Admins, developers and architects build their careers on what they know, and the ecosystem rewards them for knowing what’s new. Certifications, community recognition, conference talks and job adverts all point towards the latest capability. Nobody adds a line to their LinkedIn profile saying they spent a month making sure the sales team understood the features they’ve had since go-live. The standard capabilities of the platform feel solved to the people who build on it. The new things are where the interest is, where the learning is and, frankly, where the next job is. So when the business asks its technical team what it should do next, the answer is shaped by what that team finds worth doing.
The senior leader who championed the original purchase has a quieter interest, but it’s real. Their reputation is tied to Salesforce being a success. Buying the next thing signals momentum. It says the investment is maturing and the platform is growing with the business. Standing up in that meeting and saying “we’ve been paying for capability for three years that most of our people have never been shown” feels uncomfortably close to admitting that the original decision didn’t land. It’s far easier to move forward than to look back.
And finance, the one person you might expect to push hardest against spending, is usually negotiating with only half the information. Finance can see the price. It can see the uplift, the discount and the term. What it can’t see is use. So it negotiates hard on the number and treats a few percent off as a win, without anyone being able to say whether the thing being bought is being used at all.
There’s one more voice in the room that rarely gets named, and that’s the advice that arrives free. The discovery workshop at no cost, the complimentary readiness assessment, the pre-sales session where a solution engineer shows you what’s possible with your own data. These sessions are often genuinely useful, and I’m not suggesting anyone turn them down. But advice that arrives free is usually being paid for somewhere else, typically later, in the shape of a purchase. Businesses often treat these sessions as independent guidance because no invoice came with them. They’re the opening of a sale, done well.
Put all of this together and a pattern emerges. Every piece of advice takes the shape of the person giving it. Ask someone who sells products and you’ll get a product. Ask someone who runs projects and you’ll get a project. Ask someone whose career is built on new capability and you’ll get new capability. None of them are wrong, exactly. Each of them is answering the question from where they stand.
The problem is the person who isn’t in the room. The sales rep who uses Salesforce for six hours a day. The service agent who has found three different ways to do the same job because nobody showed her the fourth, much simpler one. The manager who still asks for updates by message because he doesn’t trust the dashboard. They’re the people who decide whether Salesforce is worth it, because worth is created or lost in how the system gets used, not in what the contract contains. They’re almost never invited to the meeting where that question is answered. And even if they were, nobody around the table is rewarded for representing them.
That’s why “is Salesforce worth it?” so rarely gets a straight answer. It gets a forward-looking one instead: it will be worth it, once we add the next thing. The question about value quietly turns into a question about purchase, because every adviser present is better equipped, and better rewarded, to answer the second one.
The obvious response is that the business should simply push back. It should ask harder questions, challenge the recommendations and refuse to buy what it doesn’t need. In theory, yes. In practice, most businesses can’t, and the reason isn’t a lack of nerve. It’s that they no longer know enough about their own system to tell the difference between what they need and what they’re being offered. That gap, and how it opens up, is where we’re going next.
Part 2: You Hired the Knowledge. You Never Kept It.
In the first part of this series I looked at the meeting where a business decides whether Salesforce is worth what it pays, and at how almost everyone advising it is rewarded for recommending more. The natural response is that the business should push back. In this part I want to look at why it usually can’t, and it comes down to one decision most organisations made years ago without realising they were making it.
When a business buys Salesforce, it buys a platform it doesn’t understand. That’s entirely reasonable. Nobody expects a sales director, a head of service or an operations manager to know how the platform is configured, what each feature does, or how the pieces fit together. So the business does the sensible thing and hires specialists. Partners, contractors and consultants come in, design the system, build it and hand it over. Later, when something needs changing, the business hires specialists again. This is a perfectly normal way to run things, and for the build itself it’s often the right one.
But something else happens along the way that nobody puts in the project plan. The business outsources its knowledge of its own system. Every time a specialist arrives, solves a problem and leaves, they take with them the understanding of why things were built the way they were, what the platform could have done instead, and what already exists that nobody is using. The system stays. The understanding of it walks out of the door with each contract.
Over time this creates a very specific kind of dependency. Think about taking your car to a garage when you know nothing about engines. The mechanic tells you it needs a new part. You have no way of knowing whether that’s true, whether a cheaper repair would do, or whether the problem could have been sorted by something already in the glovebox. You aren’t being cheated, necessarily, but you’ve lost the ability to judge. Every recommendation has to be taken on trust, because you no longer have the knowledge to question it.
That is where many businesses now stand with Salesforce. When someone recommends a new feature, a new build or a new edition, the business can’t judge it. It doesn’t know what Salesforce does as standard, so it can’t tell whether the thing being proposed is necessary or whether the capability has been sitting in the system for years.
And very often it has. This is the part that surprises leaders most when they see it. A manager asks for a custom report to be emailed to him every Monday, not knowing the platform can already send reports on a schedule. A team asks for a new screen so they can see their deals by stage, when a standard board view does exactly that. Someone requests a bespoke reminder process for follow-ups that tasks with due dates already handle perfectly well. These requests come in as “can we build…?”, because people can’t ask for something they don’t know exists. Whoever picks up the request, internal or external, then has a choice: point out that the business already has it, or build it. Building is more interesting, more visible, and sometimes more billable. So, one reasonable request at a time, businesses pay to rebuild what they already own.
There’s a second reason the standard capabilities stay invisible, and it’s subtler. Specialists suffer from what psychologists call the curse of knowledge. Once you know something well, it becomes very hard to remember what it was like not to know it. To an experienced consultant, standard features are so basic they feel barely worth mentioning. Of course you’ve got scheduled reports. Of course there’s a board view. Of course your team knows about the mobile app. They assume the business knows, because to them it’s obvious. So the conversation skips straight past the foundations to the interesting work, and the business never finds out how much was already in the box.
This connects to something that happens at almost every go-live. When the system is first rolled out, people are shown their part of it. They learn the screens they need for the process that was designed, usually in a session that walks through a few key steps. That’s understandable when time is short, but it means each user ends up knowing a narrow path through a very large system. Everything outside that path is effectively invisible to them. Years later, those same people are still walking the same narrow path, the system around them has grown with every release, and nobody has ever gone back and said: here’s what else you have, and here’s how it could make your day easier.
Meanwhile, each new round of specialist help deepens the dependency. The business hires someone to answer a question it could have answered itself, if it had kept even a basic understanding of what Salesforce does as standard. That specialist leaves, the knowledge leaves with them, and the next time a question comes up the business has to hire again. It becomes a permanent customer of its own system, paying repeatedly for knowledge it once had access to and never kept.
I want to be fair to the specialists here, because most of them would happily share what they know. The problem is that nobody asks them to, and nobody on the business side is in a position to receive it. Handover usually means documentation about how something was built, written for the next technical person. It rarely means anyone sitting with the business and explaining, in working language, what the platform can now do for them. The knowledge is passed from one technical person to another, and the business sits outside that loop entirely.
This is why the renewal meeting from the first part goes the way it does. The business isn’t weak or careless. It’s simply negotiating about a system it has gradually stopped understanding, surrounded by advisers who do understand it and who are rewarded for recommending more. Without its own knowledge, the business has no counterweight. It can question the price, but it can’t question the content.
The answer isn’t for every business to become a Salesforce expert. That would be unrealistic and, honestly, not a good use of a sales director’s time. The answer is for the business to keep a minimum of knowledge inside its own walls. Somebody who knows what’s in the box. Somebody who can hear “you need this new feature” and ask, calmly, “what do we already have that does something similar?” Somebody whose job is to understand how the system is used, rather than how it was built.
That might sound like a modest ambition. In practice, it’s one of the most valuable things a business can have when it’s deciding where its Salesforce money goes. It means going back to the core of the platform, reviewing what was switched on years ago and never explained, and reintroducing people to capability they’ve been paying for all along. It’s not glamorous work, which is exactly why it so rarely gets done.
Which brings us to the obvious next question, and the hardest one. If the business needs someone on its side, someone whose interest is use rather than more, where does it find them? Because the usual route to getting independent advice turns out to have exactly the same problem as everything else in this story.
Part 3: How to Find Someone Who’s on Your Side
Over the first two parts of this series I’ve made an uncomfortable argument. When a business decides whether Salesforce is worth it, almost everyone advising it is rewarded for recommending more. And because the business hired out its knowledge of its own system long ago, it can no longer tell what it needs from what it’s being offered. The conclusion seems obvious: the business needs someone on its side, someone whose interest is how the system is used rather than how much more gets bought. What’s much less obvious is how to find that person, and that’s what this final part is about.
The usual instinct is to commission an independent review. A business that suspects it’s overpaying, or underusing what it has, brings in a large consultancy to analyse the platform and recommend a way forward. I understand the instinct, and some of these reviews are excellent. But many of them run into the same problem we’ve been talking about all along. A large agency’s business model rewards programmes of work. So the analysis comes back thorough, well presented and full of change impacts, capability heat maps and a multi-phase roadmap, and the roadmap happens to need that same agency to deliver it. The finding that would often be most valuable, “you need less than you think, and your people need to be shown what they already have”, rarely survives a slide deck that also has to justify a substantial fee.
So the question isn’t just who you hire. It’s how you set things up so that the advice you receive isn’t quietly shaped by what the adviser earns next. Here are the approaches I’ve seen work.
The first, and the most important, is to separate the diagnosis from the delivery. When you buy a house, you don’t ask the builder who wants the renovation contract to do your survey. You ask a surveyor, precisely because they have nothing to gain from what they find. Salesforce reviews deserve the same discipline. Write it into the brief that whoever carries out the review won’t deliver what comes out of it, or at the very least that the delivery will be scoped and tendered separately. Pay for the diagnosis as a short, fixed-fee piece of work. The moment the person diagnosing your system knows they won’t be paid to fix it, the shape of the advice changes.
The second is to ask the question that reveals how someone thinks. When you’re speaking to a potential adviser, ask them: “What would you tell us if the honest answer was that we don’t need anything new?” Then ask them to tell you about the last time they advised a client not to buy or build something. Good advisers have these stories ready, because it happens to them regularly. They’ll tell you about the feature a client already owned, the project they talked someone out of, the edition upgrade that wasn’t needed. If the answer goes vague, or turns into a description of how they’d help you get more value from new capability, you’ve learned something important.
The third is to watch where they want to start. Ask any potential adviser who they want to speak to first. If the answer is the admin, the steering group and a look through the setup menu, they’re planning to review the build. That has its place, but it won’t tell you whether the system is worth what you pay. The right person will ask to sit beside your people while they do real work, and to speak to the managers who rely on what comes out of the system. If I sat beside five people doing the same job, would they all use Salesforce the same way? Someone who wants to find that out is reviewing use. Someone who doesn’t is reviewing configuration.
The fourth is to judge them by the shape of what they hand back. A useful review, in my experience, has a very particular look. The first thing it gives you is a plain-language list of what you already own and aren’t using, sorted by what your people could start using within the next month without anything being built. The second is a list of what you’re paying for that you could stop. Only after that does it get to the gaps that genuinely need new work. If the first page of the report you receive is a transformation roadmap, be wary. Good advice in this space is measured in what gets rediscovered and what gets removed, not in how much gets added.
The fifth is to look at background, not just badges. Certifications tell you someone knows the platform. They don’t tell you whether that person can explain a feature to a field engineer at seven in the morning, or understand why a sales team quietly stopped using a process. The people best placed to tell you whether your Salesforce is worth it are usually the ones who’ve spent real time with users: people who have taught, supported, or done the job themselves. They are translators between system language and working language, and that’s precisely the skill this work needs.
The sixth is the one that lasts longest, and it’s to grow someone on the inside. An external review is a moment. What a business really needs is a permanent counterweight, and that person is often already in the organisation. It might be the operations coordinator everyone goes to when they’re stuck, or the sales manager who quietly worked out how to get far more from the system than her peers. They don’t need to be technical. They need to be curious, trusted by their colleagues and given the time to do it properly. Give them protected hours to learn what the platform does as standard and what each release adds. Make sure someone explains those releases to them in business terms, not technical ones. And most importantly, give them a formal seat in every buying decision, with one standing question they’re entitled to ask before anything new is purchased or renewed: “What do we already have that does this?”
That question, asked consistently, changes the dynamics of the meeting I described at the very start of this series. It doesn’t make anyone in the room an opponent. The account executive, the partner and the technical team can all still bring their ideas, and some of those ideas will be exactly right. But for the first time, somebody at the table is rewarded for representing use. Somebody can weigh the new against the existing. Somebody can say, without embarrassment, “before we add that, let’s make sure people are using what we’ve got.”
If you take one practical thing from this series, make it this. Before your next renewal or your next purchase, decide who in that room speaks for the people who use the system every day, and how they’ll be heard. If the honest answer is nobody, that’s the first gap to close, and it costs far less than anything on the proposal in front of you.
So, is Salesforce worth it? It depends who you ask, and how they’re paid. Most businesses have spent years asking people who are rewarded for more. It might be time to ask someone who isn’t.
Be the first to comment