Saying no is one of those skills nobody teaches you in services work. Saying yes is celebrated. The signed contract is the metric. The pipeline is the dashboard. Walking away from a deal feels like leaving money on the table — and in the moment, it usually is.
But the math of saying yes to the wrong work is bad. Bad-fit projects don't end on the day they end. They cost the studio for the next six months in distraction, in late nights, in the slow erosion of the team's belief that the work is worth doing. We've felt all of that. We've learned to say no.
Here are the kinds of work we've politely turned down — and the questions that get us there.
The "you'll get exposure" pitch.
Free or sub-cost work in exchange for some future credit. The exposure is rarely as advertised. We've found that the kind of clients who lead with this pitch are also the kind that will treat the work casually and the team disrespectfully. We say no kindly, and refer the project to a junior shop that genuinely needs portfolio work.
The "we already know what we want" brief.
A client who arrives with a fully fleshed-out solution and just wants someone to build it. We don't reject these on principle — sometimes the brief really is solid. But if the discovery call doesn't surface a single new question, we get cautious. The work usually shows up six weeks later as a "could you also..." trail, because the original brief had skipped the diagnosis.
The "lowest bidder" job.
Work that's been bid out to several shops and the deciding factor is price. Our quotes are honest, not competitive. If price is the lever, we'll lose, and that's fine — the relationship would have been a strain anyway, with the client always quietly suspecting they overpaid.
The misaligned values.
This is the rarest no, and the most important. We've turned down a small handful of projects because the underlying business model was something we wouldn't be proud to ship for — predatory lending, shady supplements, opaque pyramid schemes. The brief might be technically sound, the budget might be real, the work might be doable. We still walk away. The team has to feel good on Monday morning about what they're building.
The questions we ask ourselves.
Three questions, in order. Will this client respect our process? Is the budget honest? Will we be proud of this work in two years? If we get a clean yes on all three, we move forward. If we get a soft maybe on one, we slow down. If we get a no on any, we say no.
Saying no is hard. It still is, even after a year of doing it. But every time we've said no for the right reason, the time we saved went straight back into doing the existing client work better. The math has held up.