The Question
Have you ever had to give refunds to customers?
If so, what was the reasoning behind it?
Salesforce Consulting Refund: The Short Answer
Yes. While we are typically very good with customers, there are times when the relationship simply doesn’t work out.
Since Cloud Trailz was founded, we have worked with more than 300 companies in various capacities. Across those 300+ customer relationships, there are four situations that stand out where we believed it was best to refund the customer and allow them to seek help elsewhere.
A lot of consulting companies like to pretend every engagement is a success story. That simply isn’t reality.
Projects involve people. People have expectations. Businesses change. Needs evolve. Sometimes what looked like a good fit in the beginning turns out not to be one.
The goal isn’t to avoid every mistake.
The goal is to recognize when continuing the relationship would create less value than ending it.
Why This Happens
Many people like to pretend consulting relationships always work out, they do not.
The reality is that no business functions that way.
The world would be a better place (or at least the Salesforce ecosystem would) if there was more honesty around things like this.
The truth is that customers and consultants can both have good intentions, work hard, communicate frequently, and still ultimately conclude that continuing the relationship is not the best decision.
Over the course of 300+ customer relationships, we have only reached that conclusion four times.
What follows is a chronological history of those situations and what we learned from each one.
1. We Charged For Effort Instead Of Outcomes (Winter 2021)
What It Is
This was the first time we had to face the music and refund a customer.
This was a nonprofit organization based in Atlanta. Like many nonprofits, they didn’t have unlimited funds to invest in a Salesforce project that wasn’t delivering results.
At the time, Cloud Trailz was operating under a very different business model than we use today.
Projects were billed hourly, ownership of customer outcomes was less defined, and the mentality was much closer to “sign the project and figure it out as you go” from a previous regime.
As you can imagine, that approach created problems.
What Happened?
The customer invested roughly $10,000 into the project.
Hours were billed, work was performed, meetings happened.
Unfortunately, none of that changed the most important fact. The customer didn’t have a working solution.
There was effort.
There was activity.
There was work.
There simply wasn’t enough progress toward an outcome that materially improved the customer’s situation.
Eventually we had to ask ourselves a difficult question. Is this customer actually better off because of the money they spent with us?
The answer was no.
Why It Matters
This refund fundamentally changed how we think about consulting.
The customer had paid for work, without receiving meaningful value.
We ultimately refunded the project because keeping the money felt wrong.
More importantly, it forced us to begin moving toward the fixed-focused model that Cloud Trailz operates under today.
2. Managed Services Became A Brainstorming Session (Fall 2023)
What It Is
This was one of our earliest managed services customers.
It was a very small company. essentially a one-person operation.
The owner was ambitious, energetic, and constantly generating new ideas.
The challenge was that Salesforce became less of a business platform and more of an idea factory.
What Happened?
The customer subscribed to managed services.
What followed wasn’t really a managed services relationship.
Instead, the ticketing system became a stream of consciousness.
Ideas, concepts, features seen online, random thoughts, new opportunities, new directions, new experiments.
Rather than helping the customer prioritize and improve an existing process, we increasingly found ourselves functioning as a daily brainstorming partner.
The goal became keeping us busy rather than creating measurable value.
Why It Matters
Eventually we realized that the customer needed something different than managed services.
We refunded both our services and the Salesforce license they purchased for our access.
The decision wasn’t made because anyone was angry.
It was made because both organizations were moving in different directions.
Looking back, this situation taught us that managed services requires priorities.
Without priorities, every idea appears equally important.
Nothing good comes from that.
3. The Customer Needed A Different Product Than They Bought (Winter 2023)
What It Is
This company came to us as the COVID pandemic wound down.
Many businesses were moving quickly.
Many consulting firms were moving quickly.
We were no exception.
The customer had purchased Sales Cloud.
At first glance, the engagement appeared reasonable.
What Happened?
We loaded data.
We configured portions of the system.
We conducted platform reviews with company leadership.
On the surface, everything seemed normal.
Then the conversations started changing.
Instead of discussing standard sales process concerns, discussions began focusing on:
- Product bundles
- Complex discounting structures
- Packaged pricing
- Large inventory considerations
- Product relationships spanning numerous offerings.
The deeper we went, the clearer it became that this wasn’t really a Sales Cloud problem.
The customer’s needs aligned much more closely with CPQ.
It took three to four platform reviews to fully recognize the mismatch.
That wasn’t ideal, but it was reality.
The important thing was recognizing it before the engagement went much further.
Why It Matters
By the time we identified the issue, meaningful work had already been completed.
Data had been loaded, configuration had started, and meetings had occurred.
Even so, we issued a full refund.
Why?
Because the customer was standing at the beginning of a very important journey.
They needed a partner with deep CPQ expertise, and that was not us.
Eventually they rescoped the engagement and moved to a firm better aligned with their needs.
That was the right outcome for all involved.
4. We Wanted A Platform. They Wanted Custom Code. (Spring 2026)
What It Is
After the first three refunds, nearly three years passed without another one.
Then it happened.
This organization had a highly customized web solution that was performing many functions Experience Cloud could handle out of the box.
From our perspective, migrating toward Experience Cloud made a great deal of sense.
From their perspective, the custom solution from a previous firm was ultimately what they wanted to stay with.
What Happened?
The engagement lasted approximately three months.
During that time we completed several worthwhile initiatives and improvements.
However, there was always an elephant in the room.
The custom application.
We had been clear from the beginning that custom-code support was outside our scope.
The challenge is that consultants and customers often hear that statement differently.
We know exactly what it means.
Customers often don’t.
As the engagement progressed, it became increasingly clear that the long-term expectation involved digging into custom code and extending the existing solution.
Technically we could have found people to do it, but that’s not the point. We don’t exist to continually place band-aid after band-aid on something someone else built.
Why It Matters
Experience Cloud offered several advantages:
- Better scalability
- Native user management
- Event management capabilities
- Reduced dependence on a single developer
- Greater long-term maintaintability
Had the organization wanted to move in that direction, they likely would have been a fantastic long-term fit.
The issue wasn’t technical.
It was emotional and financial.
They were invested in the custom platform they had already built and we respected that.
But we weren’t interested in becoming a long-term custom application support company.
So we refunded them and wished them well.
The Pattern Behind Every Salesforce Consulting Refund
Looking back across all four situations, a pattern emerges.
None of these refunds happened because someone was a bad person.
None happened because we suddenly decided we didn’t want the work.
Every Salesforce Consulting Refund started with a fit problem.
Service model mismatch, managed services mismatch, product mismatch, and solutions mismatch.
Different situations.
Same root cause.
What We Learned From These Refunds
The most important thing about these four situations is that they made us better and reinforced the same lesson.
The sooner you identify a fit problem, the better it is for everyone involved.
That’s one of the reasons we’ve only issued four refunds across more than 300 customer relationships.
Over time we’ve become much better at identifying fit before work begins.
Closing Thought
If you’ve read this far, you may be wondering whether publishing something like this is a good idea.
Absolutely.
Pretending every consulting engagement works perfectly isn’t honest.
Across more than 300 companies, we’ve had four situations where giving the customer their money back was the right thing to do.
Not because we enjoy refunds.
Not because mistakes don’t hurt.
But because sometimes continuing the relationship creates less value than ending it.
If you’re evaluating Salesforce consultants and wondering how a company behaves when things don’t go according to plan, hopefully this gives you some insight into how we think.
And if you’re frustrated with Salesforce, unsure about your current partner, or simply looking for a team that will tell you the truth (even when it’s uncomfortable), we’d be happy to talk.
We can’t promise every engagement will be perfect.
But we can promise we’ll be honest about what we believe is best for your business.