Keep or Kill: Fix It or Fold It, But Decide Fast

Every operator I have worked with has had a version of the same conversation: something in the business is not working and they know it, but they have not made the call to fix it or fold it. The product, the hire, the partnership, the market, the entire company. Something is wrong and the decision to address it is sitting on the desk unsigned.

The framework I use is called Keep or Kill. The name is deliberate. The point is that there are only two choices, and the worst thing you can do is stay in the middle.

Here is the sequence.

First, set a timeline up front. Before you launch anything, before you hire anyone, before you enter a market, decide in advance how long you will give it before you evaluate honestly. Ninety days, six months, a year. Whatever fits the venture. The timeline is your commitment to yourself that you will look at the data on a specific date and make a call, rather than drifting indefinitely on hope.

Second, test with friends-and-family customers. Can the people who already know you and already trust you see value in what you are building? If your warmest, most forgiving audience does not buy, the product has a problem. Not a marketing problem. A product problem.

Third, test with net-new customers. Can a stranger who has no relationship with you see enough value to pay? If friends and family buy but strangers do not, the product may work but the market may not. If strangers buy too, you have something real.

If both tests fail within your timeline, kill it. Not after another six months of hoping. Not after one more pivot. Kill it, learn from it, and move.

I knew a business was done at eight months and held it until month eighteen. I did not grind the business into the ground. I ground myself into the ground. The money I lost was recoverable. The time and energy I spent were not. If I had run Keep or Kill at month eight, I would have saved myself ten months of pain and come out the other side with more of myself intact.

The variant on the kill side is worth noting. Before you shut it down entirely, ask whether there is a sell-small or acquihire option. Can someone else use what you built? Can the team land somewhere that values them? The kill does not have to be a bonfire. It can be a clean handoff. But the decision to stop has to come first.

The teaching underneath this framework is that operators are wired to build and persist. Those are the same instincts that made you successful in the first place. But those instincts do not know when to stop. Keep or Kill is the circuit breaker. Set the timeline. Run the tests. Make the call.

What in your business have you known was dead for months but have not killed yet?

~b