Experienced founders still start with an idea. They are not more patient, or more virtuous, or less in love with their products than you are. The difference is smaller and stranger than that.
They start in the same place. They just organize the work around a different center.
The Outcome-First Spine
The product-first founder organizes everything around the solution. The experienced founder organizes everything around the customer's outcome. That's the entire shift. Everything else in this chapter follows from it.
Here's what the work looks like when the outcome is the spine instead of the product:
I know it has more steps. Don't let that fool you into thinking it's more work. It's the same work, reordered, plus a few questions at the front that the product-first spine skips entirely — and skipping them is exactly what costs founders their runway.
Notice where the customer shows up. Not at step four, when there's finally a demo. At step two. The customer's wanting is the second thing you think about, right after "what do we believe." The product, meanwhile, has gone quiet. There's no "build the demo" step near the top. Building happens (it shows up around delivery, step nine), but it has moved from the beginning of the story to the middle, after you understand what you're building toward and for whom.
The Question That Changes Everything
The experienced founder is not asking the product-first founder's question. This is the heart of it, so I'll put both questions side by side.
The product-first founder asks: "Do they have the problem my solution solves?"
The experienced founder asks: "Do they already want this outcome badly enough to change behavior, spend money, risk time, or use their political and social capital?"
These point you at completely different evidence. The first question is satisfied by a customer nodding and saying "yes, that's a real pain." The second is satisfied only by a customer *doing* something — switching, paying, committing, sticking their neck out. The first collects opinions. The second collects behavior.
Dev, predictably, perked up at this, because behavior over opinion is his entire religion. "So the outcome-first spine is the one that actually has an evidence standard. The product-first spine collects 'this is great.' This one collects 'I'll act.'" Yes. That's exactly it. The reorder isn't softer than the product-first approach. It's harder, because it refuses to count a compliment as data.
The Spine on a Real Beach
Watch the spine run on a real beach.
Marisol's outcome (step 2): tutors want a full, predictable schedule and to never have an awkward money conversation. Her customer (step 3): independent tutors who are already turning away students or chasing late payments — people the wanting is live for, today. The roadblock (step 4): they're juggling texts, a paper calendar, and Venmo, and things fall through the cracks. The alternatives (step 5): a messy spreadsheet, a free calendar app, and a lot of mental load they've learned to tolerate.
Only now, step six and beyond, does the product re-enter. The offer: we'll give you a week that fills itself and money that arrives without you asking. The message: not "a scheduling and payments app," but "stop chasing students and stop chasing money." The commitment: will a tutor who's never met you actually sign up? The delivery: does it work well enough to be worth the switch?
Same product Marisol already built. Completely different starting point, and therefore completely different content, and therefore, for the first time, strangers who lean in. She didn't need a new product. She needed to enter through the outcome instead of the app.
Marisol redraws her plan. It takes her an afternoon. The strange part, she tells me, is how little of it is new: she'd done versions of almost every step. She'd just done them in the wrong order, starting from the app and working outward, so the customer's wanting was the last thing she examined instead of the first.
"It's the same pieces," she says. "I just had the spine backwards."