Venture Pitch Page
The persuasion narrative of a venture. Its job is not to inform; it is to cause a reader at a named position on the persuasion ladder to commit to the next ask on the ladder. Every section earns its place by moving the reader one rung up.
Primary audience: A reader on the persuasion ladder — a cohort candidate, a partner counterpart, an endorser, or a funder — who has clicked through from the overview page because they recognise themselves in one of the venture's named roles.
Job
The pitch page causes a reader at a named persuasion-ladder position to commit to the next ask appropriate to that position — by stacking ethos, logos, pathos, kairos, and topos in the order needed for that specific commit.
Reader Profile
Role. A specific position on the persuasion ladder: cohort candidate (commits time), venue or partner counterpart (commits a slot or relationship), endorser (commits social proof), funder (commits capital or labour). One pitch page per venture serves all roles by frontloading the shared frame and routing role-specific calls inline.
Moment. Has read the overview, recognises themselves in one of the named roles, has clicked through expecting persuasion. Wants the case made well enough to commit, or made badly enough to walk away without further obligation.
Tension. Wants to back the bet; fears being suckered by narrative without substance, or by substance without stakes.
Direct Action Contract
The page must answer each of the seven on-surface in two sentences or fewer.
- What problem matters now? — Stated as the named pain of one named person (or named segment), not an abstract category.
- What happens if nothing changes? — Stated as the cost-of-nothing-changes; reader feels the gravity before any solution is offered.
- What better future is available? — Stated as the changed state the venture causes, with a named comparable from an adjacent scale where the pattern is already proven.
- Why trust this route? — Stated as ethos: founder pattern proven at adjacent scales, plus the one named pattern this venture inherits and renames.
- What is the first action? — A role-specific commit ask, named verb, named window, named owner. One per role.
- What outcome makes the journey worth joining? — Stated as the artifact the reader will hold at the end of the proof cycle — not a promise of future value, but a concrete deliverable.
- What kill signal keeps the bet honest? — One falsifiable line; cross-link to the proof page where the signal is detailed.
Output — the artifact shape
The pitch page stacks the five rhetorical elements in commit order. Each element is one section.
| Slot | Section | Rhetorical role | Purpose |
|---|---|---|---|
| 1 | Pathos opener — named human or named segment in named pain | Pathos | Set stakes; bypass abstraction |
| 2 | Ethos anchor — founder pattern proven at adjacent scale | Ethos | Earn the right to keep speaking |
| 3 | Logos matrix — the pattern, at the prior scale + at this scale | Logos | Make the bet inspectable |
| 4 | Kairos signal — dated, sourced trigger that says "now, not someday" | Kairos | Frame the window |
| 5 | Topos boundary — what this is NOT, with kill test | Topos | Refuse the wrong category |
| 6 | Three bets matrix — what is being bet, what is the fallback if wrong | Inversion | Show the founder has inverted before pitching |
| 7 | Role-specific commit asks (one per ladder position) | Action | The single move per role |
| 8 | Inline objections — top three the reader is silently holding | Pre-empt | Lower the cost of saying yes |
| 9 | Close — copyable prompt the reader carries into their next conversation | Affordance | The action survives the tab close |
The order is non-negotiable for the lead reader. Logos before pathos teaches; pathos before logos persuades. The pitch page persuades.
Action
Primary action. Take the role-specific commit ask. Named verb, named window, named owner. Different ask per role; one verb per role.
Wrong action. Read the pitch, feel inspired, take no action. Or worse: book a "discussion" without naming what the discussion is for.
Source affordance. The role-specific commit-ask block IS the affordance. Each ask names the reader role first, the verb second, the window third. "For a cohort candidate: confirm attendance for the four-session pilot starting [date] by [date minus 7]" — not "Sign up here."
Outcome Cascade
Right action (the bet pays out)
| Order | Effect |
|---|---|
| 1° Direct | A named opt-in lands and is linked to the reader's role |
| 2° Downstream | The role cohort fills; the proof loop runs against the falsifiable test design |
| 3° System | Evidence accumulates that the role-segmentation thesis works; the founder's persuasion-ladder model gets calibrated |
| 4° Cultural | Readers learn that this venture asks for one specific commit per role, not a generic "interest" — they bring others who match the same role |
| 5° Structural | The venture earns the right to ask for the next-rung commit; the persuasion ladder compounds because each rung's commit was specific enough to deliver on |
Wrong action (the page fails its job)
| Order | Effect |
|---|---|
| 1° Direct | The reader feels inspired; no commit lands; no artifact records the inspiration |
| 2° Downstream | The cohort does not fill; the proof loop does not run; no evidence is produced |
| 3° System | The founder cannot tell whether the pitch was wrong, the role was wrong, or the timing was wrong; future iteration is blind |
| 4° Cultural | Readers train themselves to consume the narrative without committing; the pitch becomes content marketing; readers learn this venture trades persuasion for substance |
| 5° Structural | The venture's persuasion-ladder model decays; future commits become harder because prior reads created no obligation; the venture must rebuild credibility from zero |
Kill Signal
page-to-CTA conversion < 5% for 60 days → pitch is not converting; rewrite the ask or the frame heuristic
Owner: the venture lead. Measurement: site analytics + commit-form submissions tied to page source. Consequence when the signal fires: invert the diagnostic — is the frame wrong (ethos/logos/pathos/kairos/topos misordered), the ask wrong (verb/window/owner missing), or the role wrong (the reader is not actually on the ladder)?
Instrument Flow
Upstream
These instruments feed the pitch.
Adjacent
These instruments strengthen or qualify the pitch.
Downstream
These artifacts consume the pitch's output.
Source Map
| Pitch section | Primary source instrument | Supporting instrument | Downstream consumer |
|---|---|---|---|
| Pathos opener | Idea Capture | ICP | Proof page |
| Ethos anchor | Idea Capture team section | Positioning Statement | One-Page Plan §12 |
| Logos matrix | Idea Capture pattern section | Opportunity Scanner | One-Page Plan §5 |
| Kairos signal | Opportunity Scanner | AI SWOT | One-Page Plan §6 |
| Topos boundary | Positioning Statement | Idea Capture "what it is not" | One-Page Plan §10 |
| Three bets matrix | Idea Capture bets section | Operations Scorecard kill rationale | One-Page Plan §14 |
| Role-specific commits | GTM Strategy | Lead Magnet Strategy | Proof page offers |
| Inline objections | Objection library | Sales playbook | Proof page FAQ |
Procedure
- Name the persuasion ladder. List every reader role the venture serves, in commit order. The order matters: each role's commit unlocks the next role's ask.
- For each role, write the specific commit-ask: verb, window, owner. Three fields. Anything less is not a commit ask.
- Stack the rhetorical elements in commit order: pathos first, ethos second, logos third, kairos fourth, topos fifth. The order is empirical; reorder only with named cause.
- Write the pathos opener around a named human or a named segment in named pain. If you cannot name them, the pathos is abstract and the page is decoration.
- Write the ethos anchor around a pattern proven at an adjacent scale. The pattern is the bet; this venture is the next instance.
- Write the logos matrix as the pattern repeated across scales. Show the structure first; the venture is one row in the matrix.
- Write the kairos signal as a dated, sourced trigger. "AI is reshaping work" is a category, not a signal; "As of [date], [named source] reports [shift]" is a signal.
- Write the topos boundary as what this is NOT — five rejected categories with one sentence each, plus the kill test that defends the rejection.
- Write the three bets matrix: name the three bets, name the fallback for each. The fallback is the evidence the founder has inverted.
- Place the role-specific commit asks inline with the role's rhetorical element. The cohort ask follows the pathos opener; the funder ask follows the kairos signal.
- Anticipate the top three objections silently held by each role. Reply to each in one paragraph. Place inline, not buried at the foot.
- Close with a copyable prompt that the reader carries into their next conversation. The prompt is the first action, not a summary.
Do Not Include
- Generic pathos. "People are struggling" is decoration; "[Named person] cannot do X anymore because Y" is pathos.
- Unsourced kairos. Every dated signal carries a named source or it is rhetoric, not evidence.
- Three or more role-specific commit asks above the fold. Each role gets one; mixing them dilutes all.
- A founder bio above the ethos anchor. Bios are credentials; ethos is pattern. Lead with the pattern.
- A pricing table on the pitch page. Pricing belongs on the proof page; pricing on the pitch page short-circuits the commit ladder.
- Testimonial carousels. Replace with proof-loop outcomes named on the proof page.
- A statement that has no kill test. Every category claim ("this is a third-place protocol, not a wellness app") needs a kill test ("if the member can do this alone with an app, the category claim fails").
- Feature lists. Features belong on the proof page; the pitch page sells the bet, not the artifact.
Scoring Rubric
Score each dimension from 1 to 5.
| Dimension | 1 | 3 | 5 |
|---|---|---|---|
| Rhetorical stack | Random order | Some elements present, order weak | All five elements present in commit order, each earning its place |
| Pathos specificity | Abstract category | Named segment | Named human in named pain |
| Ethos credibility | Bio only | Founder pattern claimed | Pattern proven at adjacent scale, sourced |
| Kairos honesty | "AI is big" | Dated signal | Dated signal + named source + window |
| Commit asks | No verb | Verb but no window | Verb + window + owner per role |
| Inversion shown | No inversion | Wrong-action mentioned | Three bets named with fallbacks; "what it is not" with kill test |
Investor or board standard: no dimension below 4.
CopyablePrompt
For the page builder, before writing the pitch:
I am designing the pitch page for a venture. Before I write any content, I
want to stack the rhetorical elements in commit order so the page causes the
named role to take the named commit ask.
My venture context:
- Persuasion ladder (reader roles in commit order): [...]
- Per role, the specific commit ask (verb / window / owner): [...]
For each rhetorical element, draft the section:
- Pathos opener: name the human or segment, name the pain in present tense, no
abstraction.
- Ethos anchor: name the founder pattern, name the scale where it is proven,
link the source.
- Logos matrix: render the pattern across scales; this venture is the next row.
- Kairos signal: dated, named source, named window; if "AI" or "now" appears
without a date, rewrite.
- Topos boundary: name five rejected categories, one sentence each, plus the
kill test that defends each rejection.
Then write the three bets matrix: three bets, three fallbacks. The fallback is
the evidence the founder has inverted before pitching.
Place each role-specific commit ask inline with the rhetorical element that
serves that role. Anticipate the top three objections per role; reply inline.
Close with a copyable prompt the reader carries into their next conversation.
The prompt is the first action, not a summary.
Questions
- Which rhetorical element is the weakest on the page — and is it weakest because the material is missing, or because the order is wrong?
- For each role on the persuasion ladder, what fraction of pitches result in the named commit? If under one in three, is the ask wrong or is the role wrong?
- Which of the three bets, if wrong, has no graceful fallback — and what does that say about the bet?
- If the kill signal fired tomorrow, would the pitch page survive untouched — or would every section be rewritten?