The Reality of Salesforce Business Process Design
If you’re coming into a Salesforce implementation without a firm grip on your processes, it’s natural to wonder:
Can the consultant just figure this out for me?
Some people say it outright.
Others let it leak out slowly:
- “Well you’re the expert…”
- “Haven’t you done this before?”
Here’s the truth, Salesforce Business Process Design cannot be outsourced.
Not fully. Not cleanly. Not successfully.
You can get help. You can get structure. You can get guidance.
But if you expect someone from outside your business to design how your business should operate you are setting yourself up for heartache.
The Short Answer
No. Salesforce consultants cannot design your business processes for you.
Even industry-specific firms and “off-the-shelf” solutions still require:
- Your definitions
- Your tradeoffs
- Your understanding of how your business actually works
Without that, there is no version of Salesforce Business Process Design that leads to success.
Why Salesforce Business Process Design Fails Without You
A few things keep this myth alive:
- Sales Process
Consultants don’t always push back hard enough. Deals move forward even when this gap is obvious. - Over-Reliance on Experience
Customers assume “they’ve done this before” = “they can do it for us.”
That’s not how it works. - Scoping Fantasy
Scopes are treated like contracts carved in stone.
In reality?
It’s more like gathering 65% of what’s needed from someone giving you 38% of their attention.
And then pretending that’s enough.
5 Reasons Salesforce Consultants Can’t Design Your Business Processes
1. Consultants Don’t Work Inside Your Business
What it is
Consultants are external.
Even if they’ve worked with companies like yours, they don’t feel your pressure, understand your quirks, or know your internal tradeoffs.
What’s actually happening
Customers confuse experience with similar companies with ability to define our business.
Experience helps refine.
It does not replace your input.
It’s the final coat of paint.
Not the entire paint job.
What this looks like in real life
A software company comes in saying:
“We’ve seen Salesforce work before.”
They know what dashboards looked like, what metrics were tracked, and have surface-level familiarity.
But under the hood?
They don’t know how those metrics were calculated, what rules drove them, and what exceptions existed.
They lean on the consultant’s word (and likely the consultant’s word alone).
Then the build comes back and nothing behaves the way they expect.
Now you’ve got confusion, rework, and intensely circular conversations.
Why it matters
You always end up needing to define it anyway.
The only question is Do you do it upfront or in the middle of an engagement you’re already paying for?
2. You End Up With a Summary of Other People’s Processes
What it is
My partner calls this “Salesforce by Chris”. Salesforce by Chris.”
Customers who can’t be definitive end up with what he likes, what he’s seen work before, and what other companies signed off on.
What’s actually happening
There’s a silent agreement:
- Customer doesn’t fully define things
- Consultant doesn’t push too hard
Everyone avoids friction.
Everyone crosses their fingers really hard and hope it works.
What this looks like in real life
Metrics get defined by the consultant:
- Pipeline stages
- Conversion logic
- Forecast rules
But small differences in your business change everything:
- Sales cycle timing
- Qualification criteria
- Deal structure
Now reports don’t match reality and the rebuild starts.
Why it matters
Inside the consulting firm you start to hear “This customer doesn’t know what they want”.
Customers start to say “This consultant doesn’t get our business”.
Both are frustrated.
Both are right.
3. It Masks What You Don’t Know About Your Own Business
What it is
Salesforce Business Process Design forces definition.
That can be uncomfortable.
What’s actually happening
Leaders get asked:
- How should this page look?
- What should this calculation be?
- When should this automation fire?
And sometimes they just don’t know.
They don’t know.
Instead of saying that, they pass it off.
What this looks like in real life
A traveling executive constantly on the road, juggling priorities, and pulled into design sessions.
They’re asked for specifics.
They don’t want to slow things down, look incompetent, or create friction.
So they say “you guys are the experts you handle it”.\
The system gets built.
Users hate it.
Adoption stalls.
Now the leader has to step back in and define everything anyway. Just later with exponentially more pressure.
Why it matters
When Salesforce goes live, you become the change management leader.
You cannot lead something you don’t understand.
4. You Will End Up in a Continuous Build Cycle
What it is
Instead of a clean implementation you wind up in a continuous loop of build, adjust, rebuild, and repeat.
What’s actually happening
The relationship only works when:
- Customer defines
- Consultant builds
If the customer steps back that structure collapses.
What this looks like in real life
Weeks 1–4:
- Initial build goes up
Weeks 5–8:
- “This isn’t quite right”
- “Can we tweak this?”
Weeks 9–12:
- Full redesign of:
- Stages
- Automations
- Reporting
Examples:
- Pipeline definitions rebuilt 3 times
- Lead routing logic rewritten twice
- Dashboards constantly reworked
Why it matters
You’re paying for licenses and consulting and getting an endless series of meetings with no discernible progress towards your goal.
5. You Will Not Get Business Results
What it is
This is where it hits.
You didn’t buy Salesforce to watch people build things.
You bought it for results.
What’s actually happening
You step back.
You let “the experts” run.
And slowly the system becomes something you can’t use.
What this looks like in real life (my story)
We hired a PPC firm.
I decided to “get out of the way”.
I didn’t want to micromanage, interfere, or be “that irritating client:.
Here’s what happened:
- Our money became “data fuel”
→ Their goal: collect data
→ My goal: generate pipeline - It took 4 months to align to our actual business
→ We didn’t need traffic
→ We needed qualified buyers - Financial strategy mismatch
→ I wanted to double down on what worked
→ They followed a generic model for industries far less competitive than mine. - Spend went to the wrong places
→ Platforms that didn’t fit
→ Low-quality clicks - Messaging didn’t differentiate
→ Their goal: safe, generic copy
→ My goal: differentiated copy that drove business
The Results were brutal
$35,000 spent
~6,000 clicks
3 customers
I don’t blame them. I blame myself.
I got out of the way when I shouldn’t have and our organization paid the price.
Why it matters
Consultants don’t own your outcome.
You do.
If you remove yourself from Salesforce Business Process Design you’re accepting someone else’s vision for the pressure, responsibility, and long term ownership that can only exist with you.
The Pattern Behind It
The core issue is simple:
Misalignment of responsibility.
- Customers expect consultants to define
- Consultants expect customers to define
No one fully owns it.
So the system becomes reactive, misaligned, and frustrating.
The Common Mistake
This is not a technology problem.
It’s a role clarity problem.
- Customer defines outcomes
- Consultant executes
When that flips?
Everything breaks.
What Good Salesforce Business Process Design Looks Like Instead
You don’t need perfection.
You need engagement.
That means clear definitions from your end or a willingness to say “I don’t know give me x amount of time to figure it out” when you don’t.
Also participate in testing, iteration, and feedback or you’ll find yourself saying Salesforce is a terrible fit.
Closing Thought
This was written with very specific people in mind.
Good people.
Smart people.
People who tried to do the right thing by getting out of the way.
You expose yourself and your business to some core truths.
- Consultants don’t work inside your business
- You become a summary of other companies
- You still have to own adoption
- The build will take forever
- Results become incredibly hard to achieve
Salesforce Business Process Design is not optional.
It’s your responsibility.
If you’ve taken your hands off the wheel and things aren’t working, let’s fix that.
We can help you get back in control.