CRM Strategy, Salesforce

You Don’t Have a Salesforce Problem. You Have a Strategy Problem.

Published

March 20, 2026

Read Time

5 min read

The Most Misdiagnosed Problem in B2B Operations

Salesforce is the most powerful CRM platform on the market. It’s also the most commonly blamed for problems it didn’t create.
I’ve spent 15 years in CRM and systems architecture — including time as a Director of Systems inside a fast-growing startup — and I can tell you that the vast majority of Salesforce “failures” I’ve encountered were never Salesforce failures at all.
They were strategy failures. Process failures. Governance failures. Salesforce just happened to be the system that made them impossible to ignore.

Salesforce doesn't create dysfunction. It amplifies what's already there.

What a Strategy Failure Looks Like Inside a CRM

It usually doesn't announce itself as a strategy problem. It shows up as a series of smaller frustrations that compound over time:
  • Leadership doesn't trust the pipeline numbers — so they build their own tracking in a spreadsheet
  • Sales reps don't log activities consistently — so forecasting is always a negotiation, not a data exercise
  • Marketing and Sales disagree on what constitutes a qualified lead — so MQL-to-SQL conversion rates are meaningless
  • Customer Success doesn't have visibility into what was sold — so onboarding starts from scratch every time
  • Every new admin makes changes without documentation — so nobody fully understands what the system is doing or why
None of these are bugs. They're reflections of strategic ambiguity that was never resolved before anyone logged into a sandbox.

The Implementation Trap

Here's how most Salesforce implementations actually happen at growth-stage companies:
A decision gets made — often at the executive level — to move to Salesforce or to overhaul the existing instance. A partner is brought in, or an admin is hired. Requirements are gathered, usually through a series of interviews with individual stakeholders. The system gets configured. Go-live happens. Six months later, adoption is lower than expected and the data quality is already degrading.
What went wrong?
The implementation was built around the process each team thought they had — not the process the organization needed to operate as a unified GTM motion. Marketing described their handoff to Sales. Sales described their pipeline stages. But nobody got all of those teams in a room to reconcile their different versions of reality into a single, agreed-upon architecture.
Salesforce was configured around the ambiguity. And Salesforce, being an incredibly powerful system, enforced that ambiguity at scale.

Strategy Has to Come Before Configuration

The best Salesforce implementations I've been part of shared one defining characteristic: the hard strategic decisions were made before anyone touched the system.
Before the first workflow was built, someone had answered:
  • What does each stage of our pipeline mean — precisely, in writing, with clear entry and exit criteria?
  • Who owns each stage, and what are they responsible for doing within it?
  • What data is required at each stage, and who is accountable for its accuracy?
  • How do we define a qualified opportunity, and who makes that call?
  • What does success look like at the end of each quarter, and how will we measure it?
These aren't Salesforce questions. They're business questions. But they determine everything about how Salesforce gets configured — and whether it will actually work.
If your strategy is ambiguous, your implementation will be too.

The Operator's Perspective

Having sat on the inside of a fast-growing company as a Director of Systems, I know what it feels like to be handed a Salesforce instance and told to make it work — without the strategic clarity needed to build it properly.
You do your best. You make judgment calls. You configure around the loudest voices in the room. And then you spend the next two years maintaining a system that reflects those judgment calls, not the actual needs of the business.
It's not a failure of technical skill. It's a failure of organizational process. The systems team was asked to build before the business was ready to be built on.

What Fixing It Actually Requires

If your Salesforce instance isn't delivering the value it should, the fix almost certainly isn't a reconfiguration project. It's a strategy alignment project that leads into a reconfiguration project. That means getting the right people in the room — across Sales, Marketing, Customer Success, Finance, and Operations — and doing the unglamorous work of agreeing on definitions, ownership, and process before anyone opens a setup menu.
It means documenting the customer journey end to end, identifying where handoffs break down, and building consensus around what the system needs to enforce — not just reflect.
It's harder than a technical project. It requires organizational will that a systems team alone cannot provide. It needs executive sponsorship and cross-functional accountability.
But it's the only thing that actually works.

The Right Question

Before your next Salesforce project — whether it's a new implementation, a cleanup, or a full overhaul — ask yourself this:
Is our strategy clear enough to build a system around?
If the honest answer is no, start there. The platform will still be there when you're ready.

CRM Strategy, Salesforce

Share

Related Articles

Ready to talk about what's underneath?'

If this sounds familiar, I'd love to hear where you're at. No pitch — just a conversation with someone who's been in your seat.
Get in touch