Every founder I work with knows how to ask "what should we fund?" Few know how to ask "what should we kill?"
That's the question that determines whether the next eighteen months of the company compound or just get busier. And almost nobody asks it until the board forces it.
The bias makes sense. Founding a company is an additive act. You build the product, build the team, build the customer base, build the brand. Killing things doesn't feel like progress. It feels like retreat. And the team that owns the initiative you're about to kill has spent twelve months telling you — and convincing themselves — that it's six weeks from breakthrough.
But starvation by addition kills more companies than bad bets. The founder who can't kill anything ends up running fourteen half-funded initiatives instead of four well-funded ones. The team spreads thin. The decision quality on each initiative drops because nobody has the bandwidth to actually think about it. The flywheels never start spinning because no single thing got enough fuel for long enough.
This is the capital allocation question every founder gets wrong: not "where should we deploy?" but "what should we stop deploying to?"
The build/buy/kill triage
The cleanest way to force this conversation is to put every active initiative on the table and ask one of three questions about it.
Build means we are committing to this. We are giving it the people, the budget, the timeline, and the air cover to actually work. We accept that other things will get less in order for this to get more.
Buy means we believe in the outcome but not in our ability — or our willingness — to build it ourselves. We acquire the capability, partner for it, or contract it. We free our team to focus on what only we can do.
Kill means the strategic intent has changed, the math has changed, or the world has changed, and continuing to fund this is choosing to be wrong on purpose. We stop. We move the people and the dollars to something that can actually compound.
Every active initiative should fit one of those three answers. The ones that don't — the "we're still figuring it out" ones, the "let's give it another quarter" ones, the "the team would be upset if we cut it" ones — those are the ones bleeding the company quietly.
A Series B SaaS founder I worked with had nineteen active initiatives across product, GTM, and operations. We ran the triage in a half-day session. Eight were genuine builds. Three made sense as buys. Six got killed in the room. Two needed more thinking. The six killed initiatives weren't bad ideas — most were good ideas. They were just losing to better ideas in a finite-capital environment.
Six months later the team was hitting numbers it had been missing for three quarters. The constraint was never the strategy. The constraint was the willingness to subtract.
Sunk-cost momentum versus strategic patience
The hardest part of this conversation is distinguishing two situations that feel identical and have opposite right answers.
The first is sunk-cost momentum. You've invested two years and several million dollars in an initiative. The metrics are stuck. The team is tired. The market hasn't responded. Every conversation about it sounds like "we're so close" — but "close" hasn't moved in nine months. Sunk-cost momentum is the gravitational pull of past investment, and it will keep you funding a dead initiative until the company can't afford to be in it anymore.
The second is strategic patience. You've invested two years and several million dollars in an initiative. The metrics are slow but moving in the right direction. The team has a clear thesis on what comes next. The market has given you signal, even if it's quiet. Strategic patience is the willingness to fund the long arc of something that's actually working, even when the short arc looks unimpressive.
These two situations feel the same from the inside. The team telling you about them sounds the same. The founder's gut tells them the same thing. The difference is in the underlying data, and you have to be willing to look at it without the team in the room.
A useful test: if you were starting today, with the current team and current capital, would you start this initiative? If the answer is no — not "not in the same way" but flatly no — you're in sunk-cost territory, no matter how much momentum the team feels. Strategic patience is reserved for the things you'd still start today, knowing what you know now.
The four-quadrant frame
Put strategic value on one axis. Put current return on the other. Plot every initiative.
High strategic value, high current return. Double down. These are the engines of the business. Most founders don't fund these enough because they're already "working" and don't feel like they need attention. Wrong. These are exactly where additional capital compounds fastest.
High strategic value, low current return. This is where the build-versus-kill judgment actually happens. Strategic patience lives here, but so does sunk-cost momentum. The right call depends on whether the underlying data shows a thesis that's still alive. Be honest. If you wouldn't start this today, kill it. If you would, fund it like you mean it.
Low strategic value, high current return. These are the cash cows. Run them, harvest them, but don't let them set the agenda. Many founders quietly let the cash cow define the company's identity, which is how you end up three years later with a profitable business that has no future.
Low strategic value, low current return. Kill. There is no version of this conversation where you should be funding initiatives in this quadrant. The fact that you are means either the strategic intent isn't clear, the data isn't visible, or someone on the team has political capital invested in keeping the initiative alive. Fix the root cause, then make the call.
The point of the quadrant isn't the visual. It's the forced ranking. You can't put every initiative in the top-right quadrant. The act of placing them surfaces the choices you've been avoiding.
The conversation that actually matters
Here's the thing nobody tells founders about capital allocation: the hard work isn't the analysis. The hard work is the conversation with the team running the initiative you're about to kill.
That person has spent twelve or eighteen months pouring effort into this. They built the team around it. They told their friends and family this was the thing. They believe in it. They are not wrong to believe in it — they are doing exactly what you hired them to do.
Killing the initiative is not a referendum on their judgment or their effort. It's a recognition that the company is finite-capital, the world changed, and the math no longer supports continuing. The way you have that conversation determines whether you keep the talent and move them to something better, or whether they leave and take their context with them.
The founders I see do this well treat the kill decision as a leadership moment, not a budget decision. They name the call early, frame it in terms of what the company needs to focus on now, and move the talent to the initiatives that can actually compound. The teams respect the call. The companies move faster.
The founders I see do this poorly let the initiative limp along for another two quarters until everyone has quit or the runway runs out. The decision is the same — it just costs four times as much by the time it's made.
What to do this week
Pull up your current portfolio of active initiatives. Anything that's consuming people-time or budget counts. Put each one in the four-quadrant frame, honestly. For everything in the bottom half, ask the "would I start this today?" question.
You'll have one or two answers that surprise you. Sit with those for forty-eight hours, then make the call. The cost of waiting another quarter is almost always higher than the cost of being wrong about the call.
If you're staring at a portfolio of initiatives and you're not sure which ones are strategic patience and which ones are sunk-cost momentum, that's worth twenty minutes. Book a free alignment call and we'll work through it together. You leave with one specific strategic recommendation, regardless of whether we work together.