Dev has a whiteboard. On it, in his neat engineer's hand, is the plan. It is a good plan. It is the plan almost every founder draws, usually without realizing they're drawing it, because it feels less like a choice and more like the way things obviously go.
Dev's Plan
Here is Dev's plan. I've seen it on a hundred whiteboards. You have it too, somewhere, even if you've never written it down.
Look at how reasonable this is. Build something. Show it. Get feedback. Improve it. Find more people. Sell it. It maps almost perfectly onto what startup advice sounds like it's telling you to do. It is logical, it is active, and every single step produces something visible — a demo, a pilot, a new feature, a lead list. It feels like progress at every stage.
I call this the product-first spine, because every step bends around the product. The product is the spine; everything else hangs off it. The customer enters the story late, at step four, when there's finally something to try, and again at step seven, when it's time to sell. For the first three steps the customer is essentially absent. The founder is talking to the product, about the product, for the product.
The Hidden Assumption
This spine has one assumption holding it up. The whole structure depends on it. And almost no founder ever says it out loud, which is why it never gets tested.
The assumption is this: If the solution is good enough, people with the problem will want it.
Read it again, because it's Dev's entire operating system, and probably some of yours. If I build something good enough, and put it in front of people who have the problem, they will want it. It feels less like an assumption and more like a law of nature. Good solution plus real problem equals demand. How could it not?
Here's how it could not.
People run into problems all day long. Hundreds of them. Almost none of those problems cause anyone to search for a solution, adopt a tool, change a habit, or spend money. You have problems right now you will do absolutely nothing about. The existence of a problem, even a real, genuine, you-correctly-identified-it problem, does not create demand. A problem is not a wanting.
What creates action is wanting an outcome badly enough. The problem only matters when it's standing between the customer and an outcome they actively want — when it's the roadblock to the beach. A "good solution to a real problem" can sit on the shelf forever if no one wanted the beach on the other side of that problem badly enough to move.
This is the trapdoor under the product-first spine. It assumes the wanting is already there, waiting, and just needs to be unlocked by a good enough product. Sometimes that's true. Often it isn't. And the spine gives you no way to find out, because it never asks the question. It starts at "I have a solution" and races toward "sell it," and the wanting — the one thing the whole business depends on — is simply assumed.
Dev's Pushback
Dev pushed back on this, hard, which is what Dev does and what I want you to do too.
"This sounds like you're telling me the product doesn't matter. That's absurd. A bad product won't sell no matter how you talk about the outcome."
He's right, and I told him so. The product matters. A genuinely bad product will fail. But notice what he did: he heard "the product isn't where you start" as "the product doesn't matter," and those are different claims. Of course the plane has to actually fly. But a flight that flies perfectly to a destination no one wanted is still an empty plane. Product quality is necessary. It is not sufficient. And the product-first spine treats it as if it were both.
Dev's monitoring tool was, by his own high standards, excellent. It worked. It was fast. The product was not the problem. The problem was that he had spent eleven months perfecting a flight and roughly zero hours confirming that engineering leads wanted the destination — uninterrupted sleep after a deploy — badly enough to rip out the tool they already had. The spine never made him check. It just told him to refine and ship.
That's the danger of a logical-feeling plan with a hidden assumption. It keeps you productive, busy, and shipping, right up until you run out of money, without ever surfacing the question that would have saved you.
Dev looks at his whiteboard for a long time. The plan is still good. He's just seen, for the first time, the thing it quietly assumes — the load-bearing belief he never wrote down because he never knew it was a belief.
He picks up a marker and writes one line under the seven steps: "Do they want the destination?" Then he stares at it, because he realizes he does not actually know.