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

Where should Wix ask builders to pay?

Wix is a self serve platform that lets people build and publish websites online. Answer this product management case and get it graded line by line against a weighted rubric.

The situation

At Wix, the GM for self serve website creation has asked you, a PM on growth and monetization, to recommend how and when users should encounter the upgrade prompt during the website building journey. Wix already attracts people who want to create a site without talking to sales, but leadership believes the current path from building to paying may be weaker than it should be. Some teammates want to ask for payment earlier, arguing that it will qualify intent and increase revenue faster. Others worry that an early paywall will interrupt momentum, reduce site creation, and make users feel they are being charged before they have seen enough value. This has become urgent because the team needs a clear go to market recommendation for the builder flow this quarter, but you are not being asked to redesign the product or invent a new pricing model from scratch. The hard part is deciding whether the main lever is price, timing, sequence, or some combination, and how to test a change without hurting trust or long term adoption.

What to produce

Write a 1 to 2 page recommendation memo, about 700 to 900 words.

Your answer must

Constraints

Format

Use five sections: user and problem, options, recommendation, experiment plan, risks and mitigations.

How Wix actually played it

A teardown of why the author paid Wix $34 a month despite being able to build a site another way. The core point is that asking for payment after the user has invested hours in building makes the upgrade feel natural.

  • Time the paywall after the user has invested effort
  • Let users see their own work before charging
  • Pricing sequence can matter as much as price level

Built from Wix: The pricing playbook that works (even when your product doesn't) by Kristen Berman (Product Teardowns, Irrational Labs).

Related case studies

Keep practising