a builder's codex
codex · operators · Elena Verna · ins_pricing-iteration-finds-right-model

Treat pricing like a product: assume the first model is wrong and iterate monthly until it fits

By Elena Verna · Growth advisor and former SVP Growth at Miro · 2026-05-05 · essay · The biggest takeaway from my Stripe Sessions keynote

Tier A · TL;DR
Treat pricing like a product: assume the first model is wrong and iterate monthly until it fits

Claim

No team knows the right pricing model in advance. The correct posture is to ship the first plausible model, measure conversion outcomes, and iterate monthly. Lovable changed pricing 10+ times in year one and hit 40%+ paid conversion from freemium.

Mechanism

Pricing is not a policy; it is a hypothesis about how value maps to willingness to pay. Every assumption in the initial model (unit, tier, ceiling, billing period) can be wrong. Teams that treat pricing as a product instrument accordingly: monthly reviews, user surveys, cohort analysis by plan tier. Ungate AI features first to build habit. Add top-ups alongside subscriptions to match actual usage patterns. Targeted downgrade flows surface why users move down, not just that they do. Each pricing experiment gives data that makes the next experiment cheaper to run.

Conditions

Holds when: the product has measurable conversion and retention data and can ship pricing changes on a monthly cadence.

Fails when: enterprise contracts lock pricing for 12+ months, making iterative adjustment impossible without renegotiation. Also fails when cost structure is volatile and pricing experimentation risks margin compression.

Evidence

Verna's prescription from her Stripe Sessions keynote:

Assume you do not know the perfect model in advance.

Her documented example: Lovable's 40%+ paid conversion from freemium after 10+ pricing model changes in year one, including annual plans, credit rollovers, top-ups, removing users as a pricing unit, and targeted downgrade flows.

Signals

Counter-evidence

Frequent pricing changes increase support burden and churn from users who feel misled. Lovable's iteration velocity is viable because it has high organic traffic and a freemium funnel that absorbs early churn without material revenue risk. Established B2B products with contract-heavy pipelines face much higher switching friction from pricing changes.

Open the interactive view → View original source → Markdown source →