| Date | Name | Role | Version | Comments |
|---|---|---|---|---|
| @January 23, 2023 | John Doe | Founder | 0.1 | Initial draft |
| Name | Project Role | Contact for |
|---|---|---|
| John Doe | Project lead | Clarifications on user flow, product design & strategy. |
| Isaac Hobb | Tech | Anything front end, back end or data engineering |
| Emma Crosby | Marketing & Admissions | Anything around email drips for admissions |
| Justice Hill | Onboarding & Experience | Anything around email drips for activation |
Why is it important? Faster buy-in and a common language around what exactly the product does across all internal teams. The elevator pitch should cover the core value proposition, what problem the product solves, mention relevant metrics, and address possible customer pain points.
Few elevator pitch examples here.
What are you hoping to achieve with this product/feature?
How will you know once you've gotten there?
What limitations will you need to consider when building this product? Limitations from a metric POV or could be another form of constraint.
What assumptions are you making about your audience?
Who is this feature for? What segment? etc. Be as detailed as possible, provide quantitative data on how many users this product/feature affect as well.
Summary of the high level of pain, followed by the specific pain points below.