Why we say no
(sometimes)
Turning down work sounds noble until you have payroll. We do it anyway, and the reasons are more practical than principled.
Every so often we end a first call by recommending someone else.
People are surprised by this. Agencies are supposed to be yes machines. The whole business model, as commonly practiced, is to say yes quickly, figure it out later, and let the change orders absorb the difference. Declining revenue on purpose looks either saintly or stupid, depending on your accounting.
It’s neither. It’s math, just with a longer time horizon.
The math of a bad yes
Here’s what a bad yes actually costs. A project that isn’t a fit doesn’t fail loudly on day one. It fails slowly, over months, in a specific and predictable sequence: the work takes longer because nobody’s excited about it, the client senses the flatness and starts managing us harder, the extra management makes the work worse, and eventually both sides are counting the days until the contract ends. Nobody gets a portfolio piece. Nobody gets a referral. Both teams spent half a year producing something everyone involved would rather not discuss.
A no in the first meeting costs one slightly awkward phone call. Compare receipts.
What makes us decline
So what makes us decline? Three things, mostly.
Fit
Fit is the big one. Sometimes the project needs a specialty that isn’t ours, and pretending otherwise would mean learning on your dime while a genuinely great shop sits across town. Other times the mismatch is chemistry: we work embedded, close to your team, with real candor flowing both directions, and if a prospective client wants a silent vendor who executes orders and stays out of sight, they’re describing a fine relationship that we would be terrible at. Better to say so before anyone signs anything.
Capacity
Capacity is the second, and it’s the least glamorous. We’re deliberately not huge. The people you meet are the people who do the work, which means our hours are real and finite, and every yes spends them. Taking your project while we’re full doesn’t get you our best work. It gets you our leftovers, delivered late, by people quietly resenting the schedule. You deserve the version of us that had room for you. If that version doesn’t exist right now, we’ll tell you when it will.
Shouldn’t
The third reason is the uncomfortable one: sometimes we think the project shouldn’t happen. Not can’t. Shouldn’t. The rebrand that’s really an attempt to avoid a harder conversation about the product. The app nobody’s customers asked for. We’ll always explain our reasoning, and we’ve been talked out of it more than once by a client who understood their business better than our first impression did. But we won’t take money to build something we believe won’t work. That’s not a service. That’s a very expensive form of politeness.
There’s a version of this essay where saying no becomes a humble brag, the agency equivalent of a nightclub with a velvet rope. That’s not the energy. We’re not curating an aura of exclusivity, and plenty of our favorite projects arrived looking modest. The no isn’t about the size of the brief or the prestige of the logo. It’s about whether we can honestly picture doing work we’d be proud of, for a team we’d enjoy the trenches with, on a timeline that lets both happen.
When we can’t picture it, saying so is the only respectful move available. A no respects your time, your budget, and your actual goal, which was never “hire us.” It was to get the thing built well. Sometimes the fastest route to that runs through a different shop, and we’d rather be the people who pointed you there than the people who wasted your quarter proving they should have.
The no is what makes our yes worth anything.
When we take the project, you know it’s because we looked at it honestly and wanted it. Not the contract. The problem.
