Work & projects · v0.1.0
Strategy Narrative Deck
A nine-slide narrative deck for a strategy or investment story: proof, constraint, pivot, the platform, a reference, the moat, the roadmap, and the ask. The arc consultants and founders use to walk a room from problem to decision.
investor deck board deck pitch deck strategy narrative pivot story the ask slide workshop deck operator to platform pitch
Open template ↗
Download .html
Paste the prompt into Claude (or any agent that can fetch URLs) with your content — you get back a finished, self-contained HTML file. Manifest ↗
Live preview — the example content ships with the template and is replaced by your content.
What an agent may change — and what content you should have ready. Everything outside these slots is fixed by design.
Slots
| Slot | Type | Req. | Example |
|---|---|---|---|
doc-title |
text | yes | Anchor Logistics — Investment Overview |
cover-tag |
text | yes | Freight Matching Infrastructure · Investment Overview |
cover-title |
html | yes | From regional broker <em>to matching infrastructure.</em> |
cover-sub |
text | yes | Anchor Logistics has proven the brokerage model on one corridor. Now we're building the platform that lets other brokers run on it. |
cover-footer |
text | no | Confidential · for discussion purposes only |
proof-kicker |
text | yes | Proof of concept · Pacific Northwest corridor |
proof-title |
html | yes | We built a brokerage that works. |
proof-sub |
text | yes | Freight matched between shippers and carriers on a single corridor, with our own dispatch team running the full loop end to end. |
proof-pull |
html | yes | Proven at real volume on one corridor — not a hypothesis. |
constraint-kicker |
text | yes | The constraint |
constraint-title |
html | yes | Geography, not the model, is the ceiling. |
constraint-sub |
text | yes | Standing up our own dispatch desk corridor by corridor is slow and doesn't compound. Every new lane is a fresh operations problem we have to solve ourselves. |
constraint-pull |
html | yes | That's the ceiling on growth — not carrier supply or shipper demand. |
pivot-kicker |
text | yes | The pivot |
pivot-title |
html | yes | We proved brokers want this. <em>We can't run every lane ourselves.</em> |
pivot-sub |
text | yes | So we're changing what we build. Instead of running every corridor, we build the platform underneath it — and make it available to brokers who already have the lanes we don't. |
solution-kicker |
text | yes | The platform |
solution-title |
html | yes | Four services, built once, sold many times. |
solution-pull |
html | yes | Any broker plugging in gets a ready-made matching engine — without building any of this themselves. |
proofpoint-kicker |
text | yes | Live today, not hypothetical |
proofpoint-title |
html | yes | Regional brokers plug in matching they don't have to build. |
proofpoint-sub |
text | yes | Each broker brings the shipper and carrier relationships; we bring the matching and settlement infrastructure underneath. |
moat-kicker |
text | yes | Why this is defensible |
moat-title |
html | yes | Complexity is the moat, not the obstacle. |
moat-close |
html | yes | That's exactly what this investment funds. |
roadmap-kicker |
text | yes | Already in motion |
roadmap-title |
html | yes | This isn't a plan on a slide. |
roadmap-sub |
text | yes | We've scoped a costed, sequenced build plan to turn this into the platform described here. |
ask-kicker |
text | yes | The ask |
ask-title |
html | yes | Investment in the platform, <em>not the corridor.</em> |
ask-body |
html | yes | <p>We're raising [investment amount – TBD] to fund the technology build itself...</p> |
Repeat: presenter (1–3×)
Names on the cover slide.
| Slot | Type | Req. | Example |
|---|---|---|---|
presenter-name |
text | yes | Maya Torres |
presenter-role |
text | yes | CEO & Co-founder |
Repeat: step (3–6×)
One node per step in the proof-of-concept process chain.
| Slot | Type | Req. | Example |
|---|---|---|---|
step-name |
text | yes | Source |
step-detail |
text | yes | Shipper accounts, direct and via load boards |
Repeat: module (2–4×)
One tile per component of the platform being sold.
| Slot | Type | Req. | Example |
|---|---|---|---|
module-name |
text | yes | Carrier matching |
module-detail |
text | yes | Real-time matching engine, tuned on our own dispatch data. |
Repeat: reference (1–3×)
One card per live partner or customer used as proof the platform works for someone else.
| Slot | Type | Req. | Example |
|---|---|---|---|
reference-name |
text | yes | Harbor & Slate Logistics |
reference-detail |
html | yes | Mid-Atlantic broker, live since July 2026 across four lanes. |
Repeat: reason (2–4×)
One tile per reason the business is defensible / hard to copy.
| Slot | Type | Req. | Example |
|---|---|---|---|
reason-name |
text | yes | Lane variation |
reason-detail |
text | yes | Every corridor has different carrier density, seasonality, and rate volatility. |
Repeat: milestone (2–6×)
One row per roadmap milestone, in chronological order.
| Slot | Type | Req. | Example |
|---|---|---|---|
milestone-time |
text | yes | Oct 2026 |
milestone-name |
text | yes | Platform review |
milestone-detail |
text | yes | Domain-by-domain review of the current stack, live now. |
Repeat: signee (1–3×)
Names on the closing / ask slide.
| Slot | Type | Req. | Example |
|---|---|---|---|
signee-name |
text | yes | Maya Torres |
signee-role |
text | yes | CEO & Co-founder, Anchor Logistics |
The authoritative fill instructions from manifest.json — the only place a template may instruct an agent (why).
This is a full-bleed presentation, not a printable document — nine fixed slides in a fixed order (cover, proof, constraint, pivot, platform, reference, moat, roadmap, ask). Do not add, remove, or reorder slides; do not change the two dark slides (pivot, ask) back to light. Kickers are short, all-caps category labels (2–5 words) — do not write full sentences there. Titles are short and declarative; where the manifest shows <em>, that is the turn of the argument (the pivot's cost, the ask's boundary) and should stay emphasised, not the whole title. Every slide makes exactly one point — if the user's content doesn't cleanly split into these nine beats, compress rather than inventing a tenth slide. For every repeat, remove the data-example rows (they are preview-only filler) and duplicate the prototype once per real item, respecting min/max. The proof chain (step) should read as a short process, 3–6 nodes, one or two words each. The platform grid (module) is what the user is selling as reusable infrastructure — keep each tile to one sentence of detail. The roadmap (milestone) must be chronological with real or clearly bracketed dates. The ask slide's amount should be the actual figure if the user gave one, or an explicit bracketed placeholder like '[amount – TBD]' if not — never invent a number. Keep the register consistent throughout: confident and specific, no hype adjectives, one hard number per slide where possible. Never shrink fonts, change the CSS, or alter slide dimensions to fit more text — tighten the wording instead.
v0.1.0latest
2026-08-17
Initial release: nine-slide proof → constraint → pivot → platform → reference → moat → roadmap → ask narrative arc.
Published versions are immutable: /t/strategy-narrative-deck@{version}/ never changes once live. /t/strategy-narrative-deck/ always points at the latest.