Back to library
StripeStripe

Product Launch Messaging Framework

Growth & Marketing

What it tests

Ability to translate product capabilities into sharp customer-facing positioning, copy hierarchy, and launch narrative

Format

  1. 1Candidate receives a one-pager: fictional product feature, target persona, competitive context, and three customer pain points
  2. 2They produce a messaging framework: positioning statement, tagline options (3), hero headline, three value props with supporting proof points
  3. 3They write the homepage hero section (headline + subhead + CTA) and one email announcement subject line + preview text
  4. 4Debrief call: interviewer challenges word choices, asks for alternatives, pushes on what was cut and why

What to look for

  • Is the positioning statement differentiated, or does it sound like every SaaS homepage?
  • Do value props speak to outcomes (time saved, revenue unlocked) or features (API, dashboard)?
  • Under challenge: can they defend copy choices with reasoning, or do they cave immediately?
  • Is there a consistent voice and hierarchy from framework down to copy execution?

Adaptation guide

Use your actual upcoming feature or product as the brief. This doubles as real positioning work — the best candidate submissions often inform final launch copy.

Full description

Format:

  1. Candidate receives a one-pager: fictional product feature, target persona, competitive context, and three customer pain points
  2. They produce a messaging framework: positioning statement, tagline options (3), hero headline, three value props with supporting proof points
  3. They write the homepage hero section (headline + subhead + CTA) and one email announcement subject line + preview text
  4. Debrief call: interviewer challenges word choices, asks for alternatives, pushes on what was cut and why

Time: 90 minutes

What to look for:

  • Is the positioning statement differentiated, or does it sound like every SaaS homepage?
  • Do value props speak to outcomes (time saved, revenue unlocked) or features (API, dashboard)?
  • Under challenge: can they defend copy choices with reasoning, or do they cave immediately?
  • Is there a consistent voice and hierarchy from framework down to copy execution?

Adaptation: Use your actual upcoming feature or product as the brief. This doubles as real positioning work — the best candidate submissions often inform final launch copy.