Choosing What to Say No to as You Grow
- 6 hours ago
- 5 min read
Most founders begin a startup with a strong instinct to say yes to almost everything, partly because the early months reward generosity and openness and partly because saying yes feels like the kind of behavior that successful founders are supposed to exhibit.
The instinct is reasonable in the first year, when the company is small enough that opportunities are rare, and almost any new conversation, partnership, or feature request is worth at least examining. The instinct becomes a problem in the second year, when the company has begun to find its shape and the volume of opportunities has grown beyond what the team can absorb, and the founder who keeps saying yes finds that the company is drifting in twelve directions at once with no coherent path through any of them.
This piece is about how to develop the discipline of saying no as the company grows, including the filter that helps you decide and the kinds of opportunities that look attractive but tend to be costly in ways founders do not see until later.
Why yes is the default
The instinct to say yes has two roots.
The first is that founders are often optimistic by temperament, since the work of starting a company favors people who can see possibility in situations that look uncertain to others, and that same optimism makes new opportunities look more promising than they usually turn out to be.
The second is that saying no feels like closing doors, while saying yes feels like keeping them open, and most founders prefer the felt sensation of optionality to the felt sensation of constraint, even when the optionality is illusory and the constraint is what would actually move the company forward.
The trouble is that every yes is a quiet no to something else, since the time, attention, and money required to pursue an opportunity always come from somewhere, and the somewhere is almost always the core work of the company. Founders who say yes to too much do not feel like they are saying no to anything, but the core work slows down, the existing customers receive less attention, and the team starts to feel pulled in directions they cannot explain. The cost of yes is rarely visible at the moment of the yes, which is why the discipline of saying no has to be developed deliberately rather than discovered through pain.
The filter that helps
The filter that helps the most is to ask, of any new opportunity, whether it moves the single most important thing the company is trying to learn or build in the next quarter. The filter assumes that you have already chosen one such thing, which is itself an act of saying no to the other candidates, and the filter then uses that one thing as a reference point for every subsequent decision.
If a partnership opportunity does not move the most important thing, the answer is no, even if the partnership looks impressive on a slide.
If a feature request from a customer does not move the most important thing, the answer is no, even if the customer is pleasant and well intentioned.
If a speaking invitation, a press opportunity, or a podcast appearance does not move the most important thing, the answer is no, even though saying no to attention feels uncomfortable in a culture that treats visibility as a sign of progress.
The filter does not always lead to the easy answer, but it leads to a coherent answer, and coherence is what the company needs as it grows, because incoherent companies do many things at a level of quality that satisfies no one.
The kinds of yes that look attractive but cost too much
There are a few specific kinds of yes that founders tend to say too often, and they are worth naming directly because they are easy to mistake for growth.
The first is the meeting that is interesting but not useful, which is the kind of conversation that leaves you energized at the moment but does not move any decision forward, and is often dressed up as networking or learning. These meetings accumulate quickly and produce a sense of motion without producing actual progress, and the founder who saves an afternoon a week by declining them tends to make better decisions in the rest of the week.
The second is the feature requested by a single loud customer, since the request is often accompanied by enough urgency to feel important, but the feature itself usually serves only that customer and rarely produces value for the wider user base. Founders who say yes to too many of these requests end up with products shaped by the loudest few rather than by the typical many, and the products tend to lose their original clarity over time.
The third is the partnership that promises distribution but requires real engineering work, since partnerships at the early stage almost always cost more than the founder expects, and the distribution rarely materializes at the volume that justified the cost. Most early partnerships are best entered into only when the partner has more to gain than the founder does, because partnerships entered into from a position of need tend to consume resources without producing the expected outcomes.
The fourth is the new product line that emerges from a single conversation, since the founder is sometimes presented with the idea of building an adjacent product after one promising customer interaction, and the temptation to add a second product before the first is fully working is one of the more reliable ways to slow the company down.
"The founder who saves an afternoon a week by declining them tends to make better decisions in the rest of the week"
What to do with the yeses you regret
Founders who realize, after the fact, that they said yes to something they should have said no to often feel obligated to follow through to the end, which is a kind, but expensive, instinct. A better practice is to acknowledge the misjudgment to the other party as soon as you notice it and to renegotiate the commitment to something smaller, because the cost of carrying a poorly fitting commitment for several months is almost always larger than the cost of having a brief uncomfortable conversation to reset the scope.
Most counterparties respond well to honest renegotiation, and the founders who learn to have those conversations early tend to end up with fewer commitments they regret, which makes the subsequent yeses easier to honor.
A closing thought
Saying no as a startup grows is one of the underrated leadership moves of the second year, and it is rarely dramatic when it goes well, since it usually shows up as a quiet pattern of declined meetings, declined feature requests, and declined partnerships that leaves the company with more space to do its actual work. The founders who learn to say no early tend to build companies that feel intentional from the inside, while the founders who keep saying yes tend to build companies that feel busy without feeling productive. Pick the one thing that matters most this quarter, hold the filter strictly, and let the courage to disappoint a few people in the short term protect the work that will serve many more people in the long run.
Comments