Validate Product-Market Fit at Launch

Company Context

NotionFlow is a Series B B2B SaaS company with 25,000 paying teams using its workflow and documentation platform. The company is launching a new AI meeting assistant that automatically summarizes calls, extracts action items, and pushes follow-ups into team workspaces. Competitors already offer meeting transcription, so leadership believes differentiation must come from workflow integration rather than raw AI quality alone.

Problem

The CEO wants to know how you would ensure this launch has strong product-market fit before scaling go-to-market spend. Early beta results are mixed: 62% of invited users tried the feature once, but only 18% used it weekly after four weeks. Qualitative feedback shows some users love automatic action-item capture, while others say setup feels confusing and summaries are "nice to have" rather than essential.

You are the PM responsible for launch readiness. You need to determine whether the product solves a real, frequent problem for a clear user segment, what the MVP should include, and what evidence would justify a broader rollout.

Deliverables

1. Define the target user segment(s) and the core job-to-be-done for the launch.
2. Explain how you would assess product-market fit before and immediately after launch.
3. Recommend the MVP scope and which features you would prioritize or cut.
4. Define launch success criteria, including leading and lagging indicators.
5. Identify the most important trade-offs and risks in the launch decision.

Constraints

• MVP must launch within 10 weeks.
• Engineering capacity is limited to 1 product squad (6 engineers, 1 designer, 1 data analyst).
• Sales is pushing for a broad launch across all paid plans, but support can only handle a controlled rollout.
• The AI stack has non-trivial inference costs, so the company cannot subsidize heavy usage indefinitely.