Company Context

NotionFlow is a collaborative productivity SaaS platform used by 25M monthly active users, with a strong freemium funnel and paid team subscriptions driving revenue. The company has healthy retention among established teams, but new-user activation has stalled as competitors offer simpler onboarding and faster time-to-value.

Problem

The product team has built an AI-guided workspace setup feature called QuickStart. In user tests, QuickStart helps new users create a first project 35% faster and improves day-7 activation from 42% to 51%. However, existing power users rate it poorly because it adds UI prominence to onboarding flows they do not need, creates some navigation clutter, and may divert engineering attention from workflow improvements they have requested.

Current usage mix is 30% new users and 70% existing users. Existing users generate 82% of subscription revenue today, but most future growth depends on improving new-user conversion from free to paid. Engineering can only support one major launch this quarter: either QuickStart, or a set of workflow enhancements for existing users.

Deliverables

1. Define how you would evaluate whether NotionFlow should launch QuickStart broadly, selectively, or not at all.
2. Identify the most important user segments and explain whose needs should matter most in this decision.
3. Propose a product strategy, including any rollout, targeting, or packaging approach that balances new-user gains with existing-user risk.
4. Define success metrics, guardrails, and decision thresholds for launch.
5. Explain the key trade-offs you would make and what additional research or experiments you would run before full rollout.

Constraints

• One-quarter delivery window; no capacity for two parallel major launches
• Only 4 engineers and 1 designer available
• Must avoid a measurable decline in paid-team retention
• AI feature inference cost cannot exceed $0.08 per activated user
• Full redesign of navigation is out of scope for this quarter