Startup template
Product launch OKR template
Launch the new product to all customers with 30% adopting it in the first month.
A launch is not finished when the release ships. It is finished when customers use what you built. This template keeps the team accountable for both: a readiness checklist before launch, and adoption measured 30 days after.
The beta milestone with ten customers is the safety net. It catches broken onboarding, missing documentation and pricing confusion while there is still time to fix them.
When to use this template
- You are releasing a new product, plan or major feature to existing customers.
- Past launches shipped on time but adoption was never measured.
- Product, marketing and support each have their own launch plan and need one shared view.
The goal tree
Everything below is created for you when you use the template, ready to edit. Each part is tagged with its logframe level, so the goal sits alongside a donor results framework without being rewritten.
Objective
OutcomeLaunch the new product to all customers with 30% adopting it in the first month
Plan the release, test it, launch it, and measure real adoption.
Key result 1
ActivityLaunch readiness checklist complete: 100%
Key result 2
OutcomeCustomers adopting in month 1: 30%
Key result 3
OutputBeta customers rating the launch 4/5 or higher: 80%
Milestones
Activity- Day 14 · Scope frozen
- Day 45 · Beta with 10 customers
- Day 75 · Public launch
- Day 105 · 30-day adoption review
First actions
Activity- Write the launch plan
- Recruit beta customers
- Prepare help docs
- Announce by email and in-app
Logframe levels: Impact is the long-term change, Outcome is what changes for the people or organisation you serve, Output is what you deliver, and Activity is the work that produces it.
Example KPIs to track alongside it
These indicators are not part of the template. Add the ones that fit as extra key results or as KPIs you watch.
| Indicator | Definition | Level |
|---|---|---|
| Feature activation | Customers who complete the feature's core action at least once. | Outcome |
| Repeat use at day 30 | Customers who used the feature in the week before day 30, out of those who tried it. | Outcome |
| Launch-related support tickets | Tickets tagged to the launch per 100 adopting customers. | Output |
| Announcement open and click rate | Opens and clicks on the launch email and in-app message. | Activity |
How to adapt it
- Define adoption by a meaningful action, not a click. For a reporting feature, that might be one report generated and shared.
- If the launch targets a segment rather than all customers, set the adoption percentage against that segment only.
- Add a revenue key result for paid add-ons, for example upgrades in the first 60 days.
- Push the adoption review to 60 days for features used monthly rather than weekly.
Frequently asked questions
Is a readiness checklist a real key result?
It is a delivery measure, close to an activity in logframe terms. Keep it while the launch is being prepared, and judge success on the adoption key result.
What is a good adoption rate in month one?
It varies by feature. 30% is a reasonable target for a feature most customers need. Niche features may succeed at 10%.
How many beta customers do we need?
Ten is enough to surface the main usability issues. Choose a mix of your largest, newest and most demanding customers.
Use this template
Start with this goal already set up
The objective, 3 key results, 4 milestones and 4 first actions are created in your workspace. Change the numbers, assign owners and run weekly check-ins.