Loading source
Pulling the file list, source metadata, and syntax-aware rendering for this listing.
Source from repo
Creates B2B sales collateral including pitch decks, one-pagers, objection handling docs, demo scripts, and sales playbooks.
Files
Skill
Size
Entrypoint
Format
Open file
Syntax-highlighted preview of this file as included in the skill package.
references/one-pager-templates.md
1# One-Pager Templates2Templates for different one-pager use cases, with layout guidance and copy prompts.4## Product Overview One-Pager6The default one-pager. Introduces your product to someone who knows nothing about you.8### Structure10```12[Logo] [Tagline]13HEADLINE: One sentence describing what you do and who it's for.15THE PROBLEM172-3 sentences describing the pain your buyer faces.18THE SOLUTION202-3 sentences describing how your product solves it.21WHY [YOUR PRODUCT]23• Differentiator 1 — One sentence explaining the benefit24• Differentiator 2 — One sentence explaining the benefit25• Differentiator 3 — One sentence explaining the benefit26PROOF28"Customer quote with specific result." — Name, Title, Company29[Optional: 2-3 metric callouts: "X% improvement", "Y hours saved"]30[CTA Button/Link] [Contact: [email protected]]32```33### Copy Prompts35- Headline: "What do you do, in one sentence, that makes someone say 'tell me more'?"37- Problem: "What is your buyer struggling with before they find you?"38- Differentiators: "If you could only tell them 3 things, what would make them choose you?"39---41## Use-Case Specific One-Pager43Tailored to a specific workflow, vertical, or problem. More targeted than the product overview.45### Structure47```49[Logo] [Use Case: e.g., "For Sales Teams"]50HEADLINE: How [your product] helps [persona] [achieve outcome].52THE CHALLENGE54When [persona] needs to [task], they face [specific pain].55This leads to [consequence]: [time wasted / money lost / risk].56HOW IT WORKS581. [Step 1] — What happens and why it matters592. [Step 2] — What happens and why it matters603. [Step 3] — What happens and why it matters61RESULTS63• [Metric 1]: Before → After64• [Metric 2]: Before → After65• [Metric 3]: Before → After66CUSTOMER SPOTLIGHT68"Quote about this specific use case." — Name, Title, Company69[CTA: "See it in action" or "Start a pilot"] [Contact info]71```72### When to Use74- Different buyer personas need different one-pagers76- Industry-specific versions (healthcare, fintech, e-commerce)77- Use-case versions (reporting, onboarding, security)78---80## Post-Meeting Leave-Behind82Designed to reinforce a conversation that already happened. Summarizes what you discussed and proposes next steps.84### Structure86```88[Logo] [Date of Meeting]89MEETING RECAP: [Company Name]91WHAT WE DISCUSSED93• [Pain point 1 they mentioned]94• [Pain point 2 they mentioned]95• [Goal they're trying to achieve]96HOW [YOUR PRODUCT] HELPS98• [Solution to pain 1] — [Specific capability or workflow]99• [Solution to pain 2] — [Specific capability or workflow]100• [How you help them reach their goal]101RELEVANT PROOF103"Quote from a similar customer." — Name, Title, Company104[1-2 metrics from a similar customer]105PROPOSED NEXT STEPS1071. [Next step with date]1082. [Follow-up action]1093. [Decision timeline]110[Your name] | [Your title] | [Email] | [Phone]112```113### Tips115- Send within 24 hours of the meeting117- Reference specific things they said (shows you listened)118- Keep proposed next steps concrete and time-bound119- This is the asset your champion forwards to their boss120---122## Champion Enablement One-Pager124Designed specifically for your internal champion to share with their team and leadership. Written to make them look smart.126### Structure128```130[Logo]131WHY WE'RE EVALUATING [YOUR PRODUCT]133THE SITUATION135[2-3 sentences about the internal challenge, written as if the champion136is explaining it to their team. Use "we" and "our" language.]137WHAT [YOUR PRODUCT] DOES139[1-2 sentences. Plain language, no jargon.]140WHY THIS SOLUTION142• [Reason 1] — How it solves our specific problem143• [Reason 2] — How it compares to what we do today144• [Reason 3] — How it compares to alternatives we evaluated145EXPECTED IMPACT147• [Metric]: Current state → Expected state148• [Metric]: Current state → Expected state149• [Time to value]: Live within [X weeks]150WHO ELSE USES IT152[2-3 recognizable company names in their industry]153"Relevant customer quote." — Name, Title, Company154NEXT STEPS156• [What we're doing next]157• [What we need from the team]158• [Decision timeline]159Questions? Talk to [Champion name] or [Your name at email].161```162### Why This Works164- Written in the champion's voice, not yours166- Answers the questions their boss will ask167- Includes peer proof from companies they respect168- Clear ask and timeline to drive internal momentum169---171## Layout Guidance173### Visual Hierarchy1751. **Headline** — Largest text, top of page, immediately communicates value1772. **Section headers** — Bold, clear, act as scannable anchors1783. **Body text** — Short sentences, bullet points preferred over paragraphs1794. **Proof elements** — Metrics and quotes should visually stand out (larger font, color, or callout box)1805. **CTA** — Prominent placement, bottom of page or bottom-right181### Whitespace183- Margins: at least 0.75" on all sides185- Space between sections: enough to visually separate (don't cram)186- If it feels crowded, cut content. Never shrink font below 9pt.187### Font Sizing189| Element | Suggested Size |191|---------|---------------|192| Headline | 18-24pt |193| Section headers | 12-14pt bold |194| Body text | 10-11pt |195| Fine print / footer | 8-9pt |196### Color198- Use brand colors for headers and accents200- Keep body text dark (black or near-black) on white201- Limit accent colors to 1-2 for visual consistency202- Use color to draw attention to metrics and CTAs203### File Format205- **PDF** for email attachments and leave-behinds207- **Google Slides / PowerPoint** for editable versions reps can customize208- Always include both — reps will customize, prospects want clean PDFs209