An offer, not a product
A product is what you build. An offer is what someone buys. Design the second one first.
Your job: hear the difference between your product pitch and your offer pitch.
Rewrite my pitch as an offer Read `business_model://current`. Write my idea two ways — a product pitch (features) and an offer pitch (a specific, committed transformation for my segment) — then judge the offer version against my interview evidence: would a prospect nod, or politely say "that's interesting"? claude mcp add --transport http leanspark https://leanspark.ai/mcp Connect first →
What you get back
Writes your idea both ways — the product pitch (features and capabilities) and the offer pitch (a specific, committed transformation in your segment's words) — then runs the nod test on the offer version against your interview evidence, line by line.
Both pitches side by side and a nod-test read: which lines a real prospect would nod at, and which are still feature-land. The offer version seeds the five Ps you're about to draft.
You’ve done the interviews. You know the problem is real, you can hear your segment’s voice in your sleep, and every instinct says it’s time to design the product. Here’s the most common failure mode at exactly this moment: founders design a product when they should be designing an offer.
A product is what you build. An offer is what someone buys. They’re not the same thing, and the difference decides whether anything you build next gets bought.
Consider a CRM that automates follow-up with cold leads. The product pitch: “AI-powered CRM with sentiment-aware follow-up sequences, integrations with 47 tools, and advanced pipeline analytics.” The offer pitch: “Stop losing deals to late or forgotten follow-up. Double your close rate on stale pipeline in 90 days, or don’t pay us.” Same underlying system. One is a feature list. The other is a committed transformation.
Why features don’t move purchases. A purchase happens when Push + Pull > Inertia + Friction. Features contribute to Pull, but only weakly, because features are attributes of the new way, not outcomes for the buyer. Prospects don’t reach for a better feature list. They reach for a better situation. The offer has to describe the situation, not the system.
The offer you’re about to design has five parts, the 5P Matrix: Problem, Promise, Proof, Product, Price. Notice that Product is the fourth P, not the first. That’s deliberate. Most founders start with Product and try to retrofit the rest around it. It rarely lands. Start with the segment’s real problem and design backwards from there.
The good news: the hard work is already done. Your interviews hold the transformation in the segment’s own words. Designing the offer isn’t inventing from scratch. It’s translating specific evidence into a five-part specification the prospect will recognize when you show it to them.
A useful check as you draft each P: read it aloud and ask, “Would a prospect from my segment nod at this, or politely say ‘that’s interesting’?” A nod means the offer speaks their language. “That’s interesting” means you’re still in feature-land, and the prospect is being polite. Revise.