Project Context
At NotionFlow, a B2B SaaS company with 18,000 paying workspaces, your team has analyzed six months of product usage and billing data and recommends changing the pricing model before the next quarterly launch. The data shows that the current flat-rate plan underprices high-usage customers and suppresses expansion revenue, but the executive team, Sales, and Customer Success are worried about customer backlash if the rationale is not communicated clearly.
You are the program manager coordinating a cross-functional rollout with a team of 10 people: 3 product managers, 2 data analysts, 3 engineers, 1 finance manager, and 1 marketing lead. The CEO wants a recommendation and communication plan ready in 3 weeks so the company can decide whether to launch the pricing change at the start of next quarter.
Key Stakeholders
The CFO wants a decision backed by clear revenue impact and confidence in the assumptions. The VP of Sales is concerned that enterprise deals in flight could stall if pricing changes are announced too early. The Head of Customer Success wants simple messaging that account managers can use with non-technical customers. The CEO expects a concise executive narrative, not a technical deep dive.
Constraints
- Timeline: 15 business days
- Budget: $40,000 for customer research and enablement materials
- Data dependency: billing and usage data from the last 2 quarters, with 8% of accounts missing complete feature-level telemetry
- Team capacity: engineers can support only 20 hours total because they are preparing another launch
- Decision deadline: executive review on Day 15
Complications
- Sales has already verbally quoted renewal pricing to 12 large customers under the current model.
- One analyst believes the revenue uplift estimate is overstated because SMB churn risk was not fully modeled.
- The CEO has asked for a recommendation that can be explained in under 10 minutes to a non-technical board audience.
Deliverables
- Create a 3-week execution plan to validate the recommendation and prepare the executive readout.
- Define how you would explain the data-driven decision to non-technical stakeholders with clear trade-offs.
- Propose a launch recommendation, including whether to phase the pricing change or delay it.
- Identify the top risks, owners, and mitigation steps before the Day 15 decision.
- Define success criteria for both the decision meeting and the first 30 days after rollout.
