Saying no is the hardest skill I’ve learned as a freelancer. And the most important one.
For years, I said yes to everything. Every project, every request, every “can you just quickly...”. Because when you’re freelancing, every opportunity feels precious. What if this is the one that leads to the next big thing? What if I can’t afford to pass?
What I didn’t realise was that every yes to the wrong project was a no to the right one.
The red flags
I’ve learned to recognise the signs. A client who wants to skip the discovery conversation and jump straight to design. Someone who describes their ideal outcome as “I’ll know it when I see it.” A budget that doesn’t match the expectations. Or simply — that quiet instinct that says this isn’t going to work.
These aren’t bad people. They’re just not the right fit. And recognising that early protects both of us.
What saying no actually means
Saying no isn’t about being exclusive or difficult. It’s about being honest. If I take a project I’m not right for, the client gets mediocre work and I get frustrated. Nobody wins.
But when I say no to the wrong project, I’m keeping space open for the right one. The one where the client values what I bring, where the work will be meaningful, where both of us will be proud of the result.
How I say it
I try to be direct and kind. I’ll explain why I don’t think we’re the right match. Sometimes I’ll suggest someone who might be better suited. And I always mean it — a recommendation isn’t a rejection, it’s a redirect.
What I’ve noticed is that most people respect honesty. They’d rather hear “this isn’t my strength” than discover it halfway through a project.
Saying no is a skill that protects everyone involved. It protects the client from getting the wrong designer. And it protects the work from being done without care.