When to Say No to a Client: Lessons in Building a Sustainable Business
Back in 2011, when we started McCullough Web Services, we said yes to almost everything. A client needed a quick fix on a WordPress site someone else built? Sure. Someone wanted enterprise-level functionality on a budget? We’d figure it out. A prospect couldn’t articulate what they wanted but needed it “soon”? Let’s give it a shot.
We thought that flexibility made us a good business. What we didn’t realize was that every wrong “yes” meant we were missing out on being able to do our best work.
That was a long time ago. For years now, we’ve only said yes to the right clients, and it’s made all the difference. Our intake process is smooth, our project workflow is dialed in, and our designers and developers have worked with us for the better part of a decade. Here’s what that experience has taught us, and why these decisions have made us stronger.
The Real Cost of the Wrong Client or Project
When we say yes to the wrong project, the price tag extends beyond a difficult client relationship. Here’s what those wrong fits actually cost:
Time drain. Projects outside our core expertise take twice as long as they should. A WordPress maintenance project that “should be easy” can consume 15 hours of debugging someone else’s code, time that could go toward building a new site from scratch, which is where we shine.
Opportunity cost. Every hour spent on a misaligned project is an hour we can’t spend on ideal clients. We’ve had to turn away great projects because we were tied up fixing problems we shouldn’t have taken on in the first place.
Team morale. Nothing burns out a team faster than constantly fighting fires on projects that don’t align with their skills. When our developers spend their days reverse-engineering sloppy code instead of building elegant solutions, their passion wanes.
Reputation risk. Work outside our sweet spot rarely represents our best work. That mediocre outcome still has our name on it, sitting alongside the excellent work we do when everything aligns.
Red Flags We’ve Learned to Recognize
Over the years, we’ve identified patterns that signal a project isn’t right for us:
Budget misalignment. When someone wants custom development at budget prices, it’s not just about money. It’s about mismatched expectations. They often don’t understand the value of what they’re asking for, which means they won’t be satisfied no matter what we deliver.
Unrealistic timelines. “I need a complete website redesign in two weeks” isn’t an ambitious goal. It’s a sign the client doesn’t understand the process and will likely be frustrated throughout.
Poor communication during sales. If a prospect takes three days to respond to simple questions before signing, that pattern rarely improves after the contract is signed.
Agency fatigue. When someone tells us they’ve worked with three different web designers in the past year, we listen to what they’re really saying. Sometimes the problem wasn’t the agencies.
Values misalignment. We work with businesses we respect and believe in. Life’s too short to build websites for companies whose practices make us uncomfortable, regardless of the budget.
None of these alone necessarily disqualify a prospect. But they are all things we consider when determining fit.
When the Project Doesn’t Fit Our Model
Some projects aren’t wrong because of the client. They’re wrong because of the work itself.
As we explained in our post about why we build websites from the ground up, taking over someone else’s work rarely goes well. Here’s why we decline projects that involve fixing or maintaining sites built by other developers:
Almost nobody likes cleaning up someone else’s mess. Our developers want to build, create, and solve new problems. Asking our team to spend its days untangling someone else’s shortcuts and patches is a recipe for burnout.
It always takes longer than expected. A “quick fix” quoted for two hours can turn into eight once we discover undocumented workarounds, plugin conflicts, etc. The client is frustrated because it’s taking longer and costing more than expected. Our developers are frustrated because they’re stuck in someone else’s technical debt.
We can’t deliver our best work. When we’re constrained by someone else’s architecture and decisions, we can’t implement solutions the way we know they should be built. The end result has our name on it, but it isn’t really our work. It’s a compromise, and compromises rarely wow anyone.
The liability is unclear. When something breaks, is it because of what we just changed, or how it was built originally? We end up responsible for problems we didn’t create, with a client who doesn’t understand why fixing one thing revealed ten other issues.
We’ve also learned to decline projects that ask us to work against our methodology. If someone wants us to skip the discovery phases we consider essential, or use a platform we don’t specialize in, the project is set up to fail from the start.
This isn’t about being inflexible. It’s about knowing where we can deliver exceptional value and being honest when we can’t.
The Art of Saying No Gracefully
Turning down work doesn’t have to burn bridges. Done well, it can strengthen our professional reputation.
Here’s our approach:
Be prompt. We don’t string prospects along. If we know it’s not a fit, we tell them quickly so they can find the right solution.
Be honest, but kind. “This isn’t the type of project we specialize in” is better than being vague. Most people appreciate straight talk.
Offer alternatives. We keep a list of agencies and freelancers we trust for different types of work. A referral helps everyone: the prospect gets what they need, the referred professional gets a lead, and we demonstrate our investment in their success even when we can’t help directly. If you’re a web professional who specializes in work we don’t do, like taking over existing sites or working with platforms we don’t use, we’d love to have you on our referral list. Contact us and let us know what makes you the right fit for projects we need to pass along.
Leave the door open. “This particular project isn’t a good fit, but we’d love to talk if you have other needs in the future” acknowledges that circumstances change. Sometimes the prospect who wasn’t right this year becomes our ideal client next year. We don’t assume one “no” means “no forever.”
How Saying No Has Strengthened Our Business
Becoming more selective hasn’t limited our growth. It’s fueled it.
Better client relationships. When every project aligns with our strengths and values, clients are more satisfied. We do better work, communication flows smoothly, and people refer us to others like them. When our clients call, we’re genuinely glad to talk with them. That feeling matters, and it shapes every relationship we build.
More focused expertise. Instead of being generalists who are pretty good at many things, we’ve become specialists who excel at specific things. That expertise is valuable and allows us to charge appropriately for the value we deliver.
Sustainable workload. We’re no longer constantly putting out fires or working nights and weekends to salvage difficult projects. Our team has the time and energy to do thoughtful work.
Higher quality portfolio. Every project we take on now showcases work we’re proud of. Our portfolio attracts more of the right clients, creating a positive feedback loop.
Room for the work that matters. By saying no to misaligned paid work, we’ve created space for passion projects with local nonprofits.
The Confidence to Choose
Learning to say no isn’t about being difficult or exclusive. It’s about having the confidence to know our value and the wisdom to protect it.
Back in 2011, that confidence didn’t come naturally. We worried that saying no meant missing our only opportunity.
But here’s what we’ve learned: the market rewards focus and expertise more than it rewards being everything to everyone. The clients who are right for us want to work with specialists who know exactly what they’re good at and deliver it exceptionally well.
Today, when we say no, it’s because we respect both the prospect and ourselves enough to be honest about fit. We know the project they need exists, and that someone else is better positioned to deliver it. And we know that keeping our capacity open for work we excel at serves everyone better in the long run.