Pitching a new product idea—or a feature you know your team should build—is tricky. It’s easy to ramble. Easy to throw in all the context. And way too easy to leave the reader thinking: cool idea, but why now?
This template keeps you focused. It helps you structure a crisp, confident pitch that speaks to real value—not vague potential. Use it when you’re proposing something new to your team, your PM lead, or your execs. It works for moonshots and marginal gains.
And if your org loves async pitches? Even better. This format reads clean and fast.
The template
Title
Make it specific and value-oriented
E.g. “Add self-serve cancellation to reduce churn by 15%”
Problem
What’s the pain point, bottleneck, or missed opportunity?
Our current cancellation process requires users to email support. This creates frustration, adds operational cost, and delays feedback on why users are churning.
Context
Brief background—what’s changed, or why now?
Over the last 3 months, support tickets related to cancellation increased by 22%. Our NPS feedback often mentions the lack of control around leaving. Competitors offer self-serve flows as standard.
Proposed solution
What are you suggesting, and what would it roughly involve?
Build a self-serve cancellation flow in the billing settings. Users choose a reason, complete a short offboarding flow, and receive an exit email. This would be a 2–3 sprint effort, primarily front-end heavy.
Impact
Why does this matter? What would success look like?
- Reduce support load by ~30 tickets/week
- Collect better churn reason data
- Improve customer sentiment on exit
- Potential to retain 5–10% of users through targeted save offers
Risks & unknowns
What might go wrong? What don’t we know yet?
- Some edge cases around legacy billing systems
- Unclear how many users would complete the feedback flow
- Risk of highlighting the cancellation option too prominently
Next steps
What are you asking for? Is this a pitch, or are you ready to move?
If there’s support for this direction, I’ll partner with Design to sketch out a V1 and work with Eng to size it. Open to feedback on approach or alternatives.
Tips and tricks for making this work
Be specific, but not rigid.
This isn’t a spec—it’s a proposal. You’re starting a conversation, not issuing an order.
Anchor to outcomes, not effort.
Don’t pitch features as “cool.” Pitch them as useful. Tie everything back to user value, business goals, or team priorities. If your impact section feels thin, your idea might still be half-baked.
Don’t bury the lede.
Make your title punchy and the problem painfully clear. A vague pitch rarely gets real traction.
Keep the tone neutral, not defensive.
You’re not proving yourself right—you’re offering a thoughtful way forward.
Ask for what you want.
Close with a nudge. Should they approve it? Help shape it? Suggest another direction?
When to use this
- Proposing a new feature or experiment
- Arguing for a roadmap shift
- Framing a user pain point as a product opportunity
- Async pitching to leadership or cross-functional peers
If you’re in a fast-paced team or work mostly async, this format can cut through the noise—fast. No fluff. No overkill. Just a clean, thought-through pitch that respects everyone’s time and your idea’s potential.