When to Say No to a Client Project - A Framework for Agency Owners
You get an inbound inquiry. The client has budget. They have a project you could do.
But something feels off. The fit isn't perfect.
The project feels like a distraction. But they have money, so...do you take it?
This post gives you a framework for saying no.
Why Saying No Matters
Every project you take is a project you don't take something else on.
If you're at capacity, a mediocre project crowds out a great client. You're swapping up for down.
Even when you're not at capacity, mediocre projects:
- Consume management time
- Distract from good work
- Damage morale (teams don't like mediocre projects)
- Damage margins (they're harder than expected)
Saying no to mediocre projects is how you say yes to great ones.
The Client Quality Matrix
Evaluate clients on two dimensions:
X-axis: Profit potential (0-10)
- 10 = High margin, fast delivery, repeat business potential
- 5 = Moderate margin, standard delivery
- 0 = Low margin, complex delivery, one-off
Y-axis: Enjoyment/Fit (0-10)
- 10 = Perfect cultural fit, mission alignment, team loves them
- 5 = Neutral, no major issues
- 0 = Bad fit, values misalignment, team dislikes
Plot the client on the matrix:
Top-right (High profit, High fit): TAKE IT. This is your dream client.
Top-left (Low profit, High fit): Consider it. Great fit sometimes justifies lower profit.
Bottom-right (High profit, Low fit): Consider carefully. High profit doesn't make up for bad fit.
Bottom-left (Low profit, Low fit): PASS. Nothing redeems this.
Red Flags
Some clients are warning signs. Watch for:
Red Flag 1: Unclear scope. They can't articulate what they want. You'll spend weeks clarifying.
Red Flag 2: Unrealistic timeline. "We need this in 2 weeks." (But it's complex.)
Red Flag 3: Low budget for the scope. They want a lot for a little.
Red Flag 4: Demanding PM. The client contact is difficult, picky, hard to reach.
Red Flag 5: No decision authority. Your contact can't approve anything. Decisions go to committee.
Red Flag 6: Unclear success metrics. They can't define what success looks like.
Red Flag 7: Misalignment on budget. You bid $30k, they expected $10k. You're starting negotiation from a bad place.
Red Flag 8: Scope creep is inevitable. You can already sense the changes coming.
Any two of these together suggest passing.
The Questions to Ask Before Saying Yes
Before committing to a project, ask:
Do we have capacity? Not just technically, but without stressing other clients/projects?
Can we win? Do we have the expertise? Will we deliver great work?
Is the budget right? Have we bid accurately? Will this be profitable?
Do we like them? Do we want to work with this client for months?
Is this strategic? Does it advance our agency's direction? Or is it a distraction?
Will they be happy? Can we meet their expectations? Or are they setting themselves up for disappointment?
If you answer no to any question, pass.
Saying No Professionally
You don't have to take every project. Say no clearly.
Good: "We appreciate the opportunity, but it's not the right fit for us right now. Here's why: [reason]. We recommend [alternative agency if you have one]."
Bad: "We're too busy." (They hear: call back later)
Bad: "It's outside our expertise." (They hear: too complicated, not confident)
Good reasons to say no:
- We're at capacity and don't want to compromise quality
- This isn't in our core competency
- The timeline is unrealistic for quality delivery
- The fit isn't right for a long-term relationship
- We're focusing on different service offerings
Be specific. Be kind. Leave the door open for future opportunities.
Saying No When You Need the Money
This is hard. You're cash-tight. The project would help.
But taking a bad project to solve a cash problem usually makes things worse:
- Bad projects run over (time, not profit)
- Bad clients pay late
- Bad projects damage morale (your team is unhappy)
- Bad projects lead to more bad work (distracted from good clients)
If you're desperate for cash, the answer is marketing and sales, not taking bad projects.
Build marketing in good times so you don't need bad projects in bad times.
The Exception: Strategic Projects
Sometimes you take a project that's not ideal because it's strategic.
Examples:
- Low profit, high profile client (you want the case study)
- Experimental service you're testing
- Launching into new market (proving capability)
Be intentional about this. It's an investment, not a desperation move.
Mark it clearly: "This is a strategic project. We're pricing it lower to test this service and build the case study."
Don't let strategic projects become a habit. They should be occasional, not normal.
Frequently Asked Questions
What if they're willing to pay premium to have us? Premium helps, but it doesn't cure a bad fit. If the relationship is bad, more money won't help.
Should we counter-offer if it's close but not quite right? Maybe. If the issue is budget, you can propose a smaller scope. If it's timeline, you can propose a longer timeline. But don't compromise on fundamental issues.
What if we're starting out and need all the revenue? Take on projects you can win at first. But be selective. Bad projects hurt more than no projects.
How do we know if we're being too picky? If you're passing on projects that fit your matrix (top-right), you're not picky - you're profitable. If you're passing on everything because "it's not perfect," you're too picky.
What if a mediocre project leads to good clients through referral? Possible, but not certain. Don't make decisions based on hypothetical referrals. Decide on the project itself.
Should we have a formal decision process? Yes, for consistency. Use the matrix. Ask the questions. Document why you passed.
What if the team wants to take a project and you don't? Have the conversation. Maybe they see something you don't. But trust your instincts on bad fits.
The most successful agencies are selective. They say yes to great projects and no to mediocre ones. That selectivity is what makes them great.
Build the confidence to say no. Your clients (and your team) will thank you.