When MSPs Walk Away From A Sale

When MSPs Walk Away from a Sale

Most MSP owners feel pressure to say yes to any revenue opportunity, especially when it comes from existing clients. But not every sale is a good idea for your MSP.

Executive Summary

This article explains when a mature MSP should walk away from a sale or client engagement, even if the work is technically possible. It focuses on fit, complexity, profitability, and long-term operational impact — not beginner sales tactics or pricing tricks.

• Understand why custom and one-off work quietly erode process and margins.

• See how complexity in service offerings impacts your MSP’s operations.

• Get permission and language to say “no” when a deal is a bad fit.

• Use a simple checklist to decide when to walk away from a sale.

If you have ever thought, “This deal doesn’t feel right, but I’m afraid to say no,” this article is written for you.

Author: Ian Richardson, Founder, Fox & Crow Group Inspired by Thursday Process with guest Michael Crean, VP, Sonic WallLast updated: December 14, 2025

Questions This Post Answers

When should an MSP walk away from a sale or client engagement, even if the work is technically possible?

How do you know if a prospect is a bad fit for an MSP?

Why do custom MSP projects and one-off services lose money?

Is it okay for an MSP to say no to work it can technically deliver?

How do experienced MSPs decide which sales to walk away from?

What is the real operational cost of custom work in an MSP?

When a Sale Is a Bad Idea for Your MSP

Saying no to money is tough to do.

Most MSP owners and leaders pride themselves on solving problems and closing business. Walking away from an opportunity can feel wrong, especially when you know your team could technically do the work.

The pressure is even higher when the request comes from a current client. Fear and anxiety set in:

• Fear that the client will leave your MSP.

• Fear that a competitor will say “yes” when you say “no”.

• Fear that turning down revenue will slow growth or hurt reputation.

So the MSP says yes to work that is custom, outside the core stack, or a one-off exception to the standard agreement. On the surface, it looks like extra revenue. Underneath, it is usually a drag on the business.

Over time, diluting your service offerings with special cases and “just this once” projects becomes more than a distraction. It quietly erodes the performance and profitability of your MSP.

Why Mature MSPs Walk Away From Certain Deals

Michael Crean of Sonic Wall shared this wisdom with me:

“Just because you can do [a product or service offering] doesn’t mean you can do it well.”

For a mature MSP, that’s the crux of the decision.

The question is not, “Can we do this?” The real question is, “Can we do this well, repeatedly, inside our standards, without hurting the rest of the business?”

How Complexity Breaks MSP Process

Whenever you add a new variable to your service offering — an unfamiliar product, a one-off integration, a custom support model — you introduce complexity. Complexity always increases overhead.

Mature MSPs fight complexity with process.

Process tells your team, “Do this task in this way.” It’s what turns your tech stack and standards into a consistent client experience.

At its core, process exists to simplify the complexity of your MSP’s offer. It does that by dictating how you deliver the work.

So what happens when you add variables for a single MSP sale?

• The process no longer functions as designed.

• Your team has to create exceptions, workarounds, and “shadow” procedures.

• Tickets take longer, projects slip, and escalations increase.

When you add enough of these one-off variables, your process breaks.

Deliverables and outcomes stop going as planned. Your best people spend time firefighting instead of improving the business.

The Real Cost of Custom Work in an MSP

This isn’t a new idea.

Peter Drucker detailed a version of it in his essay “Managing for Business Effectiveness.”

I’m heavily paraphrasing, but Drucker essentially reveals that the true cost of an organization’s products or services is directly related to the number of transactions required to deliver that offer — things like quotes, service calls, project changes, manufacturing runs, tickets, and meetings.

Custom MSP work requires more of everything:

• More quoting and re-quoting.

• More scoping and re-scoping.

• More tickets, escalations, and status meetings.

• More back-and-forth with the client as you “figure it out together.”

Standardized offers, built on a defined stack and support model, need fewer inputs and fewer customer interactions.

The work is familiar.

The path is clear.

Those increased inputs on custom work translate directly into increased costs. That leads to my favorite MSP math problem:

*When complexity goes up, costs go up. *

When costs go up and price doesn’t follow, profitability goes down.

MSP Walk-Away Checklist: When to Say “No” to a Sale

Walking away from a sale is not about being difficult.

Walking away from an MSP deal that is a bad fit is about protecting your standards, your team, and your best-fit clients.

Here is a simple checklist you can use when you are not sure whether to say yes or no.

If several of these are true, you should strongly consider walking away from the sale:

• The prospect refuses to adopt your standard stack or security baseline.

• They insist on one-off tools, legacy systems, or custom integrations your team doesn’t already support.

• They push back on your standard processes (ticketing, SLAs, communication channels) and want special treatment.

• They want “enterprise” outcomes on a bargain budget and resist appropriate pricing.

• The engagement would be a one-time exception, not a repeatable service you plan to sell again.

• Your team already feels uneasy about the client’s behavior, expectations, or communication style.

• You cannot clearly see how this work fits your long-term vision for your MSP.

If you read that list and feel a knot in your stomach, trust that signal. Your intuition is often your experience trying to protect your business.

If you or your reps have difficulty saying no to bad fit MSP clients, some coaching may help.

Free No Paywall MSP Bad Fit Client Checklist

Download the Fox & Crow When to Walk Away Checklist right here.

No paywall.

100% Free.

Keep it on your desk and refer to in when you're trying to decide "is this MSP client a bad fit?"

Permission to Say “No” as an MSP Owner

This is where many MSP leaders get stuck. They know a deal doesn’t feel right, but they hesitate because saying no is uncomfortable.

It’s easy to tell yourself:

• “We’ll just do it this once.”

• “We can make it fit our process later.”

• “We’ll raise prices next time.”

In reality, each of those exceptions trains your team and your clients that standards are optional. It also teaches your sales function that any deal that closes is a good one.

In a mature MSP, walking away from a sale is not a failure. It’s a sign of operational judgment.

You’re not just protecting this month’s margin. You’re protecting:

• Your service standards.

• Your team’s morale and focus.

• Your ability to deliver consistently for your best-fit clients.

Learn how MSPs are using the MSP Sales Process to grow their businesses with the right clients in this case study!

Final Thoughts on MSP Service Offerings

By pursuing that extra “sale” that doesn’t fit, you’ve decreased the operating efficacy of your business. You would have been better off walking away from the sale — and in many cases, your client would have been better off too.

Adhering to standards improves your customer’s experience working with your company. Your team knows what “good” looks like. Your offers are clear. Your delivery is repeatable.

In the end, it’s far better to take Michael’s advice:

"Stop trying to be everything to everyone. Be what you said you wanted to be, and … be amazing at that and stop being distracted.”

If you're struggling to select core MSP offers or define your standards, I'm happy to help.

I talk offers in my newsletter

I'm always happy to chat with people around offer selection and standardization. My calendar is here.

References: Peter Drucker, Harvard Business Review, "Managing for Business Effectiveness". May–June, 1963.

FAQ: Walking Away from MSP Sales

When should an MSP walk away from a sale?

An MSP should walk away from a sale when the prospect refuses to adopt your standard stack, demands one-off custom work, underinvests relative to the risk, or insists on exceptions that will break your processes and drain your team.

What are red flags that a prospect is a bad fit for an MSP?

Red flags that a prospect is a bad fit for an MSP include ignoring security best practices, demanding special treatment, pushing for unrealistic response times, bargaining heavily on price, and showing disrespect toward your team or your expertise.

Why do custom MSP projects and one-off services lose money?

Custom MSP projects and one-off services lose money because they create extra quotes, meetings, tickets, and escalations, and those additional transactions increase cost and complexity without a matching increase in price.

Is it okay for an MSP to say no to work it can technically do?

It is okay for an MSP to say no to work it can technically do when the engagement does not fit the MSP’s standards, stack, or strategy, because saying no to misaligned work protects margins, morale, and the quality of service for your best clients.

How do experienced MSPs decide which sales to walk away from?

Experienced MSPs decide which sales to walk away from by using clear criteria such as fit with the standard stack, fit with the support model, realistic budget and expectations, alignment with long-term strategy, and whether the work can become a repeatable offer.

People Also Ask

Will my MSP lose business if I start saying no to prospects?

Your MSP will lose some prospects if you start saying no, but saying no to bad-fit prospects frees capacity and focus for better-fit clients and usually leads to healthier growth and fewer painful engagements.

How early can you spot a bad MSP client?

You can spot a bad MSP client as early as the discovery and proposal phases, especially when prospects resist your standards, push hard on price, or expect special treatment before they even sign.

How do MSP service offerings affect profitability?

MSP service offerings affect profitability by either increasing or reducing complexity: simpler, standardized offerings usually increase profitability by reducing tickets, rework, and exceptions, while complex, custom-heavy offerings drive higher cost and operational drag.

What should I do if I already said yes to bad-fit MSP work?

If you already said yes to bad-fit MSP work, you should acknowledge the impact on your team and margins, then decide whether to reset expectations, re-scope and re-price, or exit the engagement and use that experience to tighten your qualification and walk-away criteria for the future.