The standard agency sales playbook treats every inbound lead as a deal to be closed. Objections become walls to break through. Pricing is whatever the lead will tolerate. Scope expands to absorb whatever the prospect mentions. The proposal goes out within a week, the contract gets signed, the work begins, and three months in everyone is unhappy.
We've inverted that. About one in four discovery calls ends with a polite no from our side. Not because we don't need the revenue — we do. Because the engagements where the math doesn't work end the same way every time, and we'd rather not run that play.
What we say no to
- 01Budgets we know won't carry the scope. If the work needs $80k and the budget is $25k, the engagement either fails on quality or doubles in cost mid-project. Both are worse than not starting.
- 02Timelines that imply the team will burn out. Two-week MVPs of complex products. Hard launch dates with no slack. Reasonable timelines exist; impossible ones produce work nobody wants to ship.
- 03Goals we don't share. If the prospect wants pixel-perfect designs of a product they haven't validated, we'd ship beautiful work that doesn't move a number. We'd rather not.
- 04Buyers who can't decide. Two stakeholders disagree on the brief in the first call. We'll point this out and suggest they align internally before talking to any agency, including us.
What happens after we say no
Three outcomes, in rough order of frequency.
Most commonly, the prospect goes elsewhere. They find an agency that says yes to the original brief. Sometimes that works for them. Sometimes — and we hear about this through the back-channel often enough that it's a pattern — it doesn't, and six to nine months later they email us again with a different project that does fit.
The second outcome: the prospect rewrites the brief. They take our reasons for declining seriously and come back in a few weeks with a smaller scope, a longer timeline, or a clearer goal. Roughly a third of our re-engagement conversions started this way.
The third outcome, and the most surprising: they refer us. Even when we say no, we send three written recommendations the prospect can act on without us. People remember that. The discovery call becomes a small piece of free consulting that doesn't end in an invoice. About a fifth of our inbound leads in a typical month come from a previous prospect we declined.
The discovery call is a recommendation engine, not a sales pitch. People who can't hire you can still send you the next three people who can.
Why this works at small scale
The reason most agencies can't say no is the same reason most agencies can't measure outcomes: their cost structure demands a constant rate of new project starts. Junior teams need work to do, senior teams need utilisation targets, and overhead is fixed. When the pipeline dries up for a month, the next bad-fit deal becomes the saving deal. The cycle continues.
A small senior studio has a different cost structure. Three to five engagements a year, each fully scoped and resourced, covers operating cost with enough margin to skip the wrong ones. Saying no isn't a luxury; it's the operating model that makes the work consistently good.
The version that doesn't work
Two failure modes. First, saying no without offering anything useful. 'Not a fit, good luck' is worse than saying yes — the prospect leaves the call with nothing, and you're not memorable. The recommendation version of the no is the version that pays off later.
Second, saying no when you should have asked harder questions. Some prospects look bad on paper and turn out to be exceptional clients once the brief is clarified. The discovery call's job is to find that out. Reflexive no is no better than reflexive yes.
Curious how we'd actually qualify your project? The discovery call is the cheapest way to find out, and if we're not the right team for it you'll leave with three written recommendations from somebody who isn't trying to sell you anything.