What Entrepreneurs Can Learn from SPIN Selling
Founders fall in love with what they built, so the moment a prospect or investor takes a call, the instinct is to open with the pitch: the demo, the deck, the vision. That instinct is understandable given how much is riding on every conversation, but it skips the one thing that actually moves a deal — finding out what is true for this specific person before explaining why your thing matters to them.
The whole book, compressed
This edition works through 4 core lessons — take them one at a time, not all at once.
What's different for your conditions
Tap whichever ones sound like you. Nothing here is sent or saved — it's just for your own noticing.
0 of 5 selected
The core lessons, applied to you
Ask before you assume you already know the market
Founders often build the answer before they've confirmed the question, because the idea felt so clear in your own head that it seems obvious it applies to everyone else's. Before describing what you built, get specific about how this person or team handles the task today — the tools, the workarounds, the people involved, and what "good enough" currently looks like for them.
A founder gets fifteen minutes with a target customer and spends twelve of them walking through the product roadmap, only to learn in the last three minutes that the person doesn't actually own the budget or the workflow being pitched. The meeting ends warmly, and nothing happens after it, because no real picture of their situation was ever built.
Before your next customer or investor call, write down three questions about how they currently do this task, and commit to asking all three before you open the deck.
Get specific about the problem before you sell the fix
It's tempting to leap from a vague complaint straight to "here's the feature that solves that," but a fuzzy problem produces a fuzzy sense of urgency. Push the conversation until the other person can state, in concrete terms, exactly where the current approach breaks down and for whom.
A prospect mentions offhand that reporting is "kind of a pain," and the founder immediately jumps to explaining the analytics dashboard, never asking what specifically is painful, how often, or for whom — so the pitch lands as generic rather than as an answer to their actual difficulty.
When you hear a vague complaint, respond with "can you walk me through the last time that happened" before you respond with anything about your product.
Make the real cost of the status quo visible
Once a real problem is named, it is worth spending time on what it is actually costing the person — the time lost, the workarounds piling up, the decisions being made on bad information. This only works when the problem is genuinely already there; the goal is to make an existing cost visible, not to talk someone into worrying about something that isn't actually hurting them.
A founder hears that a team manually reconciles two spreadsheets every week and moves straight into pricing, without ever asking what that reconciliation delays downstream or who has to stay late to finish it — so the eventual proposal reads as a nice-to-have instead of something worth prioritizing.
After naming a problem, ask one specific follow-up about what it affects downstream — a deadline, another team, a decision — before talking about your solution at all.
Let them tell you why fixing it is worth it
The strongest moment in a founder conversation isn't when you explain your value proposition — it's when the other person says out loud, unprompted, why solving this would matter to them. Questions that invite someone to describe the upside in their own words tend to produce commitment that a polished pitch rarely does.
Runway pressure will always push you to skip ahead to the pitch, especially in a short meeting, but a rushed pitch to someone whose situation you don't understand usually costs more time than it saves. Protect the first few minutes of any meaningful call for genuine questions, even when the clock is loud in your head.
Name one thing, honestly
Think of a real deal, hire, or partnership you're trying to move forward right now — what do you still not actually know about the other side's current situation?
Good. Now look back at the "Try this" line under whichever lesson feels most connected to what you just wrote, and treat that as this week's actual assignment — not all 4 at once.
The practices from this edition
0 of 3 selected
Run this for seven days
After naming a problem, ask one specific follow-up about what it affects downstream — a deadline, another team, a decision — before talking about your solution at all.