AI Product One-Pager Template: A Single-Page Format for Quick Approvals
TL;DR
The 10-page PRD is for the team. The one-pager is for the exec. AI product one-pagers fit on a single screen, take 90 seconds to read, and either get a yes or a clarifying question — never a maybe. This template covers the six-section structure, the AI-specific lines that earn approval, and the discipline of cutting the doc until it actually fits one page.
Six Sections, One Page
1. The headline (1 sentence)
The whole proposal in one line. "Add AI summarization to long threads to cut time-to-action 30%." Forces clarity.
2. Problem (3-4 sentences)
Specific user, specific pain, evidence. One quote, one stat, one anecdote.
3. Proposed solution (3-4 sentences)
What it is, scope, what it's explicitly not. Mockup if available; otherwise word-only.
4. AI approach (3-4 sentences)
Model choice, prompt approach, eval methodology, cost expectation. The differentiator section.
5. Phased plan (4 lines)
Prototype, beta, GA. Dates and kill criteria for each.
6. The ask (2-3 sentences)
What you want, by when. Specific resources, specific decision deadline.
The AI-Specific Lines That Earn Approval
Capability claim with evidence
"Models can do this reliably (verified in 50-case eval, 87% accept)." Specific. Bounded. Tested.
Cost-at-scale projection
"~$0.008/request × 100K requests/month = $800 incremental cost." Hand-waving here loses execs.
Eval and rollback plan
"Eval gates at each phase; instant rollback via feature flag." Reassures execs that risk is bounded.
Why now
"Inference cost halved this quarter; this becomes viable now where it wasn't." Anchors timing.
The Discipline of Cutting
A one-pager that doesn't fit on one page isn't a one-pager — it's a PRD lying about its size. The discipline of cutting forces you to know which sentences earn their space. The first draft is always too long; the third or fourth is the right one.
Cut every adjective
Adjectives don't carry information; nouns and verbs do. Hunt them down.
Cut throat-clearing
"In today's fast-moving AI landscape..." — kill these. Get to the point in sentence one.
Cut redundancy ruthlessly
If you say it twice, you don't trust the first time. Trust it. Cut the second.
Cut hedges
"We believe", "possibly", "may." Hedges signal weakness. State or cut.
Cut exposition
Don't teach concepts execs already know. Reference, don't explain.
Get One-Pagers Reviewed Live
The AI PM Masterclass walks through real one-pagers with cuts and rewrites in real time — taught by a Salesforce Sr. Director PM.
When to Use a One-Pager vs. a Full PRD
Use one-pager for
Exec approval, kickoff alignment, executive previews. Anything where the audience is senior and time-poor.
Use full PRD for
Engineering implementation, eval design, edge case handling. Anything where the audience needs to ship the work.
Use both together
One-pager links to the full PRD. Execs read the one-pager; team reads the PRD. Same project, different audiences, different docs.
Update the one-pager as scope evolves
Treat the one-pager as the 'current snapshot' — keep it fresh as the project evolves. The full PRD captures detail; the one-pager captures direction.
One-Pager Mistakes
Writing 1.5 pages
Either it fits or it doesn't. 1.5 pages says you didn't do the work to cut. Iterate until it fits.
No specific ask
"Looking forward to feedback" is not an ask. Specific resource, specific deadline, specific decision required.
Hand-waving on AI capability
"LLMs can do this" without evidence reads as naïve. Reference an eval, a prototype, or a comparable shipped feature.
Burying the ask
The ask should be the last section, prominent. Execs scan top-to-bottom; the ask should be unmissable.
No why now
Without timing context, every proposal looks the same. Why now is what makes execs prioritize this over the other 20 things.