Figma · Strategy · Entry · 45 to 60 minutes
How should Figma limit its free plan?
Figma is a browser-based design tool where multiple people can create and edit the same design files together. Answer this product management case and get it graded line by line against a weighted rubric.
- Product strategy
- Pricing judgment
- User empathy
- Experiment design
- Metric selection
The situation
You are the PM supporting growth at Figma. The team is reviewing whether the free plan is helping or hurting new user activation. Figma's core value is multiplayer design, but the current free plan allows only two editors in a workspace. Some new teams hit that limit during their first attempt to collaborate, while many others never notice it. Leadership wants a recommendation before the next pricing update. The tension is that the free plan cannot become completely unlimited. It still needs to control cost, reduce abuse, and leave a clear reason for teams to upgrade later. But a limit that blocks a user's first real taste of collaboration may be harming adoption more than it helps monetization. Assume funnel reviews, support tickets, and user feedback suggest wide variation in team size and strong negative reactions when the editor cap interrupts sharing. You need to decide whether the current limit structure is the right one, what alternative would better protect activation, and how to test any change with real users before a public announcement.
What to produce
Write a 1 to 2 page strategy memo.
Your answer must
- State the core product problem and identify the activation moment that the free plan should protect.
- Evaluate at least two free plan designs, including keeping the current editor cap and at least one different way to limit free usage.
- Recommend one approach and explain tradeoffs for new user activation, upgrade incentives, and operational or abuse risk.
- Define 3 to 5 metrics and guardrails, including at least one activation metric and one monetization or misuse metric.
- Describe a test plan that covers target segments, rollout approach, and what evidence would cause you to change course.
Constraints
- Do not redesign paid plans or propose unrelated product features.
- The free plan must remain bounded in some way, fully unlimited free usage is out of scope.
- You need a recommendation that can be tested with real users before any broad announcement, within one quarter.
Format
Use short sections: problem, options, recommendation, metrics, test plan.
How Figma actually played it
Figma's growth product manager explains why the free plan's two-editor cap was removed in exchange for limits on files and pages. The reasoning is that the free plan is a new user's first taste of multiplayer, and any editor cap is arbitrary. The team tested the new plan with thousands of users and shares the reaction. A compact example of trading one limit for another to protect the activation moment.
- Treat the free plan as the activation path, and remove limits that block the core value.
- Swap the limit rather than abandon it: unlimited editors in return for caps on files and pages.
- Reject arbitrary caps (such as simply doubling the limit) when users differ widely.
- Test a plan change with real users before announcing it.
Built from About Figma's new Starter plan by Saba Munir, Figma.
Related case studies
- Figma's AI boundary: make, monetize, or own the recordFigma · Strategy · Senior
- Should Figma bet on prompt to app creation?Figma · AI product · Senior
- How should Figma grow beyond designers?Figma · Strategy · Senior
- How should Figma rally support for a new bet?Figma · Execution · Mid
- How should Figma sequence growth motions?Figma · Go-to-market · Senior
- Plan Figma's upcoming price increaseFigma · Go-to-market · Mid