Duolingo is one of the clearest examples of freemium done right. Tens of millions of daily users. A massive free experience. And a subscription business that generates the vast majority of its revenue—without gutting what made the product valuable in the first place.
In this episode of Sub Club, Cem Kansu—former VP of Product at Duolingo—walks through the decisions, trade-offs, and hard calls behind that balance. What stands out isn’t a clever pricing trick or a perfectly tuned paywall. It’s a philosophy: protect the free experience, even when short-term revenue is tempting.
Here are the core lessons every subscription app builder can take from Duolingo’s journey.
Protect the free moat—always
One of the biggest traps in freemium is also the easiest win: take something free, make it paid, and watch revenue spike.
Cem has seen this play out repeatedly—and warns it rarely works long-term.
At Duolingo, the free experience wasn’t just a funnel. It was the product’s moat. Locking too much behind a paywall might boost metrics for six months, maybe a year. But it weakens the growth engine and creates space for competitors to offer what you just took away.
Free value isn’t charity. It’s strategy.
Duolingo’s early success came from doing something incumbents wouldn’t: offering high-quality language learning completely free. Undoing that advantage would have meant undoing the company’s differentiation. So instead of extracting more from free users, the team focused on preserving—and often expanding—the free experience, even when it meant saying no to revenue-positive ideas.
Freemium isn’t a trade-off—it’s the growth engine
At Duolingo, free users were never treated as freeloaders. They were the primary distribution channel.
Word of mouth fueled growth, and word of mouth only worked if the free product delighted people. When free users learned more, progressed faster, and felt respected, they told their friends. That loop compounded.
This is why Duolingo was willing to do something that feels counterintuitive to many subscription teams: move features from paid back to free.
When features like Practice Hub or “Explain my answer” didn’t justify their revenue impact—or became cheaper to run thanks to AI efficiency—the team intentionally took a revenue hit to strengthen the free experience. The short-term numbers dipped. The long-term growth engine got stronger.
That trade-off only makes sense if you believe free users are part of your business, not a cost center.
Monetize with empathy, not extraction
Introducing monetization to a previously free product is as much a cultural shift as a product one.
When Duolingo added ads, the team expected backlash—and they got some. But instead of reacting emotionally to negative reviews, they zoomed out. They measured everything: retention, app closes, review volume per million DAUs, complaint rates across different issues.
What they found was grounding. Ads created noise, but they didn’t meaningfully damage the core experience when done carefully.
The rule was simple: optimize for trust, not ARPU.
Ads only appeared after a lesson—never before, never during. Categories that felt off-brand or unsafe were blocked, even if it cost revenue. Over time, Duolingo went further, partnering directly with advertisers to create custom ad formats that fit the product’s tone and even extended its character-driven world.
The goal wasn’t to squeeze users harder. It was to monetize in ways that felt fair, predictable, and respectful.
A/B test relentlessly—but know when to ignore the data
Duolingo runs hundreds of experiments at any given time. Testing is foundational to how the product evolves.
But Cem is clear: experimentation isn’t the same as outsourcing judgment to dashboards.
Many tests surface uncomfortable trade-offs—revenue up, learning quality down; engagement up, trust eroding slowly. In those moments, the job of product leadership isn’t to follow th