We turned down a client last year. It was the best decision we've made in a long time.
It's a strange thing to say out loud in a service business. Software companies say yes to projects the way restaurants seat walk-ins — every yes is a sale, every no is money on the table. But the projects that nearly sank us weren't the ones that were hard. They were the ones where we ignored the signs.
The signs
This particular project checked every box in the beginning. Good budget. A real problem to solve. A founder with energy. And then the first red flag: the scope was a moving target, and every meeting added requirements we'd "just agreed to."
The second red flag: decisions were made by a committee we never met, and they kept changing the person in charge. Our point of contact changed three times in a month.
The third red flag — the one that finally did it — was when we were asked to commit to a fixed deadline for a project that kept growing. We knew that deadline would be impossible, and we knew we'd be blamed for it anyway.
The decision
We sat down and had the conversation every agency dreads. We told them, honestly, that we didn't think we were the right fit — and why. We gave them their deposit back.
It felt like losing money. In the short term, it was.
What happened next
A few months later, we saw the project go to another vendor. Then we saw it stall. Then we saw it go to a third. By then, it wasn't our problem — and the lesson had paid for itself twice over.
The founder eventually called to say we'd been right.
The rule we live by now
We ask three questions before we take any project: Is the problem real? Is the decision-maker reachable? And can we be proud of the result? If the answer to any of them is no, we pass — politely and early.
Saying no is how we say yes to the projects we actually do well. And those are the ones worth having.