Figma · Go-to-market · Mid · 45 to 60 minutes

Plan Figma's upcoming price increase

Figma is a collaborative design and product development platform that teams use to create interfaces, prototypes, and shared workflows in the browser. Answer this product management case and get it graded line by line against a weighted rubric.

Pricing strategy
Go-to-market
Customer empathy
Communication
Trade-off analysis

The situation

You are a PM on Figma's monetization and packaging team. The VP of Product and the Head of Revenue Operations need a recommendation for an upcoming price increase on one paid plan area used by design and product teams. They believe the business needs higher revenue per customer to support continued investment, but they are worried about customer backlash, confusion, and churn if the change feels like a pure tax rather than a fair exchange of value. Assume leadership wants a measurable revenue lift this planning cycle, while protecting long term trust and expansion. The hard part is that Figma has a steady stream of product improvements, but not every improvement is obvious to every buyer at the moment a bill changes. Some users care deeply about workflow and collaboration outcomes, while others think in terms of seats, permissions, or specific features. Your job is not just to decide whether to raise prices, but how to package, frame, and time the change so customers understand it and can connect it to value they recognize before they feel the higher bill.

What to produce

Write a 1 to 2 page go-to-market recommendation memo.

Your answer must

State your recommendation on how Figma should introduce the price increase, including packaging, messaging approach, and timing.
Lay out 2 to 3 realistic launch options and compare their trade-offs for revenue, customer trust, and user understanding.
Explain how you would connect the price change to visible customer value, including what kind of value proof customers should see before billing changes.
Define the target audiences for the communication, such as admins, budget owners, and day to day users, and how the message should differ for each.
Specify success metrics and guardrails for the first 1 to 2 quarters after launch, including at least one revenue metric and one customer health metric.

Constraints

You cannot assume a major net new product bet will be ready just for this launch.
You cannot hide the change in confusing billing language or dark patterns.
You should preserve trust with existing customers and avoid avoidable surprise at renewal or invoice time.
Your plan should work with normal product launch and lifecycle marketing channels, not a custom one off sales motion for every account.

Format

Use sections for goal, options, recommendation, rollout and timing, messaging, metrics, and risks.

How Figma actually played it

Unpacks how Figma communicated a price increase, crediting what it did well and what it missed. The author uses behavioral pricing ideas such as framing and timing of new feature launches to show how the same hike could have landed better.

Pair a price increase with visible new value
Frame changes in terms users already care about
Time launches so users notice the value before the new bill

Built from Figma's price hike: How to (and how not to) raise your prices by Kristen Berman (Product Teardowns, Irrational Labs).