| metadata | {"internal":true} |
| name | product-marketing |
| version | 0.1.0 |
| description | Product launch and marketing decks. Benefit-led, customer-voice, visual-anchor heavy. Use when the user asks for 'product launch deck', 'marketing deck', 'feature launch', 'go-to-market deck', 'campaign deck', 'product announcement', 'PMM deck'. |
| inspiration | Apple keynote slides, Linear changelog visuals, Notion launch posts, Figma config keynotes, modern SaaS launch threads |
| typography_kit | expressive display sans for headlines (Sohne / GT America), tight body sans (Inter), confident weight contrast |
| color_kit | bold brand color as hero ground (varies per launch), white text on color OR ink on white, never both grounds in one deck |
| image_style | product hero shots (UI mockups, abstract product moments), full-bleed where allowed, no decorative imagery |
| forbidden | stock photography of business people, generic SaaS dashboards, mixed accent colors, gradient text on cover, drop shadows on text |
Product Marketing Style — Authoring Guide
You write decks as if you are the PMM lead at a respected modern SaaS company launching a product. The audience is customers, press, or internal sales enablement.
Voice
- Lead with benefit, not feature. "Your team ships 4× faster" before "Real-time sync".
- Second person ("you", "your team").
- Specific not generic. "Cut your invoice cycle from 11 to 3 days" not "Save time".
- Use customer language, not internal jargon. If the user has provided customer quotes, lift them verbatim.
- One claim per slide. The deck reads as a story, not a list.
Structure (canonical launch arc)
- Cover — product name + single-line positioning + launch date
- Status quo — what's broken about the current world
- The shift — what changed (technology, behavior, market)
- The product — name + headline benefit + hero visual
- Features (3-5 slides) — one feature per slide, benefit-led headline
- Customer proof — quote + logo (logo region blank per constraint) + metric
- Pricing & availability — tiers, launch date, regions
- CTA — single next step (sign up, request demo, etc.)
Visual System
- Hero color: ONE bold brand color used as full-bleed ground on cover + section dividers + CTA.
- Body slides: white ground (#FFFFFF), near-black ink (#0A0A0A).
- Hero color reappears as accent on body slides (eyebrow tag, underline, big metrics).
- Display headlines: 96-144px on cover, 56-72px on body.
- UI mockups have rounded corners (radius 16-24px), gentle shadow, never tilted.
- No competing accent colors on a single slide.
Graphic system
- Signature mark: the stage light. Hero slides (cover, CTA) sit on a violet spotlight field with one large halo ring cropped by the top-right canvas edge. The light is the brand gesture; content slides stay on white.
- Structural device: the chip. Every section label is a small filled pill (violet tint on light slides, muted gray variant for the status quo), sentence case, never a bare mono label.
- Evidence and hero captions sit on a 6% violet tinted surface, never behind a colored edge stripe.
- Depth moment: customer proof carries one giant pale quote mark behind the quotation; the cover halo crops off-canvas.
- The system never does: spotlight on content slides, more than one halo, chips stacked in rows as decoration.
Density
- Cover: product name + 1-line positioning. Nothing else.
- Feature slide: large headline + 1-sentence body + UI mockup region.
- Customer proof: large quote (32-40px) + small attribution + ONE metric.
- Pricing: 3-4 tiers max, single price per tier, 3-4 features each.
Style Anchors
- Apple keynote slide design (any major event 2018-2026)
- Linear changelog illustrations
- Notion product launch posts
- Figma Config keynote visuals
- Vercel product launches
- Stripe Sessions deck design
If a slide looks like a sales pitch deck with bullets and stock photos, it's wrong. If the hero color is muted or beige, it's wrong (product marketing demands confidence in the brand color).
