If you're staring at an idea right now, trying to decide whether to actually build it, here's the thing nobody tells you: that decision isn't the hard part. Avoiding it is.

Most founders don't decide not to build. They just keep researching. Keep talking to "a few more people." Keep tweaking the pitch deck for an idea that doesn't have a product yet. The build-or-don't decision gets replaced by an infinite runway of activity that feels like progress and isn't a decision at all.

I get why. A decision is binary and final-feeling. Research is safe. You can research forever and never be wrong, because you never committed to anything that could be checked.

The tell: you're gathering evidence you don't intend to act on

Here's how you know you're avoiding the decision instead of making it: ask yourself what result would make you stop. Not slow down — stop. If there's no number, no answer, no single piece of evidence that would actually kill the idea for you, you're not evaluating it. You're building a case for a verdict you already reached.

"You're not evaluating it. You're building a case for a verdict you already reached."

Founders spend four months validating an idea they were always going to build regardless of what the validation said. The research wasn't a decision-making tool. It was a delay with better PR.

"The research wasn't a decision-making tool. It was a delay with better PR."

What the decision actually requires

The build-or-don't decision needs exactly three things, and most founders skip straight past them to "let me just build an MVP and see."

Who pays, specifically — not "the market," a person you could put a name to. What they'd stop doing, or stop paying for, to pay you instead. And the number that would make you walk away, decided before you're three months and a chunk of your savings into finding out.

Skip any of the three and you haven't made the decision. You've deferred it to a future version of yourself who'll have a lot more sunk into being right.

Why "just build it and find out" isn't a decision either

There's a popular counter-argument: just ship something small and let the market tell you. Fair, for the shape of the product. But it's a different question. "What should we build" and "should we build" aren't the same decision, and the second one is the one people dodge by rushing to the first.

Building something small still costs you months. It's not free just because it's fast. If you'd have built the small thing regardless of what it told you, the market didn't decide anything — you did before you started, and the build was theatre.

"If you'd have built the small thing regardless of what it told you, the market didn't decide anything — you did before you started, and the build was theatre."

The decision, made honestly

If you can't name who pays, can't describe what they'd stop doing to pay you instead, and haven't decided in advance what would make you walk away, you haven't reached a build-or-don't decision yet. You've reached a build-eventually-probably decision, and those don't get made. They get outlasted by whoever's patience runs out first — usually the bank account.

Name the three things. Then decide. The decision is fast once you actually have what it needs. It's the avoiding that takes months.

Want more like this? Rick writes about the go/no-go decision, founder counterintuitions, and the business of building ventures worth building.

All writing