One page, one story
Five good fragments don't add up to an offer. Integrate, read it aloud, and only then go pitch it.
Your job: catch the gaps between your five Ps before a prospect does.
Check my 5P offer Read `offer://current` and `business_model://current`. Assemble my 5P Matrix on one page and run the four integration checks. For any check that fails, name the gap and propose the smallest revision — shrink the Promise before expanding the Product. Then write the aloud-read spine. claude mcp add --transport http leanspark https://leanspark.ai/mcp Connect first →
What you get back
Assembles your five Ps onto one page, runs the four integration checks — Promise-solves-Problem, Product-delivers-Promise, Proof-credible-at-stage, Price-anchored-to-value — scores each, and renders the aloud-read spine so you can hear whether it's one story or five fragments.
A one-page 5P Matrix with each check passed or flagged, the specific gap named, and the smallest revision that closes it. When all four pass, you're ready to build the demo on top of it.
You have drafts of all five Ps. The last step is pulling them onto a single page and running the checks that separate a strong offer from five good-looking fragments that don’t add up. The full offer, on paper, before any code or demo gets built: Problem (80–120 words), Promise (30–60), Proof (50–100), Product (50–100), Price (20–40). If it doesn’t fit on one page, the offer isn’t tight enough.
Four integration checks, in order:
- Does Promise solve Problem? Read them side by side. If the Problem is about feeling like the bottleneck and the Promise is about reporting improvements, they don’t hook together, and the prospect won’t feel the offer was written for them.
- Does Product deliver Promise? Walk the causal chain honestly: “If I sold this tomorrow, could I deliver the Promise in the timeframe it names?” If not, shrink the Promise or expand the Product. Don’t pretend the chain works when it doesn’t.
- Is Proof credible at your stage? If you can’t say your Proof out loud without a pang of “that’s a stretch,” tighten the Promise until existing Proof covers it, or find stronger Proof.
- Does Price anchor to the value? $500 against a $40k problem makes prospects wonder what’s wrong with it; $30k against $40k leaves less than a 2x win and stalls the decision. The Price should feel like obvious-win arithmetic, not a negotiation.
The aloud-read. Read the whole page in order: “You [Problem]. We [Promise]. Here’s why [Proof]. We deliver this by [Product]. The exchange is [Price].” That’s the spine of a pitch. If it tells one coherent story aloud, you’re ready. If there’s a gap anywhere, you’ll feel it in your own voice.
Everything from here is delivery. The one-page offer you just integrated is exactly what How to Sell Before You Build (No. 5 in this series) turns into a four-act pitch, a smallest-viable demo, and a set of real commitments. The demo isn’t a product tour; it’s a tour of these five Ps, made visual. Design here, sell there.