We say no to roughly one in three businesses that reach out.

Not because the businesses are bad. Not because the budgets are wrong. Not because we don't have the capacity.

We say no because the fit isn't there, and taking on work where the fit isn't there is the fastest way to produce results nobody is proud of.

This is uncomfortable to say publicly. Most agencies don't. Saying no to revenue feels counterintuitive when you're building a business. But the agencies that say yes to everything end up doing mediocre work for everyone, and we've made a deliberate choice not to be that.

Here's what actually drives those decisions.

We Say No When the Business Isn't Ready

There is a version of almost every business that is ready to invest in brand and digital work, and a version that isn't.

The version that isn't ready is the one still working out the fundamentals. The offer isn't clear yet. The target client is everyone. The revenue is inconsistent. The founder is still experimenting with what the business actually is.

Investing in brand design and website development at that stage doesn't fix the underlying uncertainty. It wraps it in something that looks polished. The brand becomes a bet on a direction the business hasn't confirmed yet. When the direction shifts, as it often does at that stage, the brand becomes an anchor rather than an asset.

We've made the mistake of taking on these engagements before. The work is hard to execute well because the strategic foundation shifts under it. The client isn't satisfied because the outcome doesn't match the reality of what the business needed. Neither side wins.

So we don't take them on anymore.

We Say No When the Client Wants Execution, Not Partnership

The second category is the client who arrives with a fully formed brief and wants someone to build exactly what they've described.

This client knows what colors they want. They have a wireframe. They have a strong opinion about the navigation structure. They've already decided the positioning. They need an agency to produce the output, not to question the thinking.

We can execute. But the best results we produce come from being involved at the strategic layer, not just the production layer. When that layer is closed off before the engagement starts, the work becomes a production exercise and we're just an expensive version of a cheaper option.

The right client for that brief is a production studio with strong execution and low overhead. That's not what we are, and taking on work that doesn't use what we actually bring leads to frustration in both directions.

> The clients we say no to aren't bad clients. They're just right for a different kind of partner.

We Say No When the Problem Isn't What They Think It Is

This one is the most nuanced, and it's where the most important conversations happen.

Sometimes a business comes to us with a clear problem statement: "our website isn't converting" or "our brand looks inconsistent" or "we need a full redesign." And sometimes, after ten minutes of conversation, it becomes clear that the stated problem isn't the real problem.

The website isn't converting because the messaging is wrong, not the design. The brand looks inconsistent because three different people in the business are making brand decisions without a system. The redesign is being requested because a competitor launched a new site, not because the current one is actually underperforming.

When the stated problem is wrong, solving it produces results that don't address the underlying issue. The new website goes live and still doesn't convert. The redesign looks better but doesn't change the business outcome. And the client wonders why they spent the money.

We try to surface this in the initial conversation. Sometimes we do, and the client is relieved to hear someone name it correctly. Sometimes the client has invested enough in the stated problem that they're not ready to hear that it's the wrong framing.

When that happens, we say no. Not permanently. Just: not yet. Come back when the real problem is clearer and we can actually solve it.

We Say No When the Timeline Is Wrong

Good work takes time. Not infinite time, but more than a week.

When a business comes to us needing a full brand and website in three weeks because they have a conference or a fundraise or a launch deadline, the math doesn't work. Compressing a process that needs space into a timeline that doesn't have any doesn't produce a fast version of good work. It produces rushed work with a deadline attached.

Research by the Nielsen Norman Group consistently finds that the most significant usability problems in digital products come from insufficient discovery and testing time. Rushed timelines skip those stages and the work reflects it.

We'd rather help a business understand what they can realistically achieve in their timeline and do that properly than take on the full scope and produce something we're not proud of under pressure.

We Say No When We're Not the Right Fit for the Industry

There are industries we understand well. Non-technical businesses, professional services, fintech, health, e-commerce. Businesses where brand clarity and digital execution make a measurable difference to how clients find them, evaluate them, and decide to hire them.

There are industries where our expertise doesn't add the most value. Highly technical B2B products where the buyer is an engineer evaluating specifications. Mass-market consumer products where distribution and shelf presence matter more than brand storytelling. Industries with specific regulatory constraints that change what's possible in marketing and brand.

When a business from outside our area of strength approaches us, the honest answer is that they'd be better served by an agency with deeper context in their world. Saying yes to look capable when we'd be learning on their budget isn't fair to them.

What Happens When the Fit Is Right

When we do say yes, it's because something specific lined up.

The business is established and has proof of demand. The founder wants a partner who will push back, not just produce. The problem is real and addressable. The budget and timeline are realistic. The industry is one where we know we can make a meaningful difference.

When all of that is true, the engagement is different. The work is sharper because the brief is better. The results are clearer because the problem was right to begin with. The relationship is easier because both sides knew what they were getting into.

That's what saying no to the wrong fits makes possible. Not every client. The right ones.

Why We're Telling You This

Most agencies don't publish their rejection criteria. It feels like giving away leverage, or admitting limits, or putting off clients who might otherwise have said yes.

We're publishing this because the right clients read something like this and feel relief rather than concern. They've been through the experience of hiring an agency that said yes to everything and delivered work that didn't move anything. They want a partner who is selective enough to know when they're the right fit.

If you read this and thought "this is exactly what I've been looking for," that's the conversation we want to have.

If you read this and thought "they're being too restrictive," that's useful information too. It means we're probably not the right partner for where you are right now.

Either way, you're better off knowing before the discovery call than after a proposal. Start here if you want to find out which side of that line you're on.