DataCamp Paywall: 50% Conversion Lift From Deleting a Feature
65% of users bounced on a screen before ever seeing the paywall. I deleted it entirely and lifted conversions by 50%.


Why This
Two-thirds of users never saw our paywall. They bounced on a screen designed to prepare them for it. The screen was doing its job, just not the job we needed. So I proposed deleting it entirely.
Root Cause
Open brief: find paywall opportunities on mobile. No hypothesis, no target metric. Just go look.
I mapped every path a user could take after finishing their first chapter. 70% tapped Start Next Chapter — our main funnel. But that tap did not show the paywall. It showed a pre-paywall screen first: a generic title, a description, and a button.
Of everyone who landed there:
Key Bet
My first instinct was to personalize the pre-paywall. The screen was generic: a title, a description, a button. No context about what the user had just learned or what they would unlock.
Then I stopped and asked a different question: why have a pre-paywall at all?
If we could personalize the content, why not personalize the actual paywall directly? The pre-paywall was an extra step we had invented. Users who reached the paywall converted fine. The problem was the friction getting there.
I proposed killing the screen entirely.
Paywall changes are sensitive territory. Touch the wrong thing and you risk revenue. But the data was too clear to ignore. PM and growth leads aligned once they saw the funnel breakdown.
“The best way to fix a friction point is often to delete it.”
How I Built
Two changes, one sprint.
First, plug the leak. I removed the Home button from the post-chapter screen. That 6% of users who tapped Home and vanished now had to choose between continuing or practicing. Both paths eventually reached the paywall.
Second, eliminate the bottleneck. I removed the pre-paywall screen entirely. Users who tapped Start Next Chapter went straight to the paywall. No intermediary. No warming up. Just a direct path to the decision point.
I kept the Practice option. Practice is core to DataCamp's mobile value proposition. Removing it would have damaged the product experience for a marginal conversion gain.


What Shipped
We ran an A/B test.
The treatment group converted at 7.36% compared to 4.90% for control. A 50% lift in subscription conversions, statistically significant with 95% confidence.
One sprint to build. One month to validate and ship permanently.
This flow is now the default. Every new paywall test starts here.
What I'd Do Differently
This project had the ingredients I thrive on: freedom to explore the data, space to question assumptions, and a fast path from insight to shipped solution.
I wish more projects worked this way. Give me a real problem, access to data, and room to move quickly. I love this stuff.
If I had more time, I would track long-term retention alongside conversion. Did we actually grow subscriptions, or just pull forward purchases that would have happened anyway?
I would also follow up by redesigning the paywall itself. It is crowded, generic, and does not reflect what the user just learned. There is more conversion lift sitting there.
More Case Studies
Explore other projects I've worked on


invoo: From Idea to Multi-Platform Product
Co-founded an invoicing tool for Spanish freelancers. Built web and mobile from scratch in 2 months. 150+ waitlist signups, zero ad spend. Launched May 2026, live with the first cohort.

Deck: The IDE I built because nothing on the market fit
Existing IDEs are either cluttered with dev features I don't use or too heavy on agentic workflow. I wanted something simple: read code files, render Markdown nicely, and run Claude Code in multiple terminals side by side. So I built it. Electron, React, TypeScript, CodeMirror, xterm.js. Actively maintained.


DataCamp Mobile Home: From Content Overload to 7% Course Lift
I bet that users think in actions, not courses. Restructured the entire home screen around learn/practice/review instead of course types. Bounce rate dropped 10%, course engagement rose 7%.
ai-org: scaffolding I clone into every new project
A reusable Claude Code plugin that ships four portable layers into any repo: agents with a point of view, skills with explicit rules, commands that trigger workflows, and product knowledge the AI can actually read. Running in four of my active projects, plus designers at DataCamp using it to ship code they wouldn't have attempted alone.