How Codecademy grows

Downloaded all checkout page payment errors, stack-ranked them by frequency, rewrote the copy so each failure tells the user what is wrong and what to do (instead of 'Invalid payment method. Please contact your bank.'), with fallbacks: if the card fails, offer PayPal; if PayPal fails, send them back to a card. Merged back into the codebase. Took about 2 days. Rationale: 100% of new revenue passes through checkout, so a 1% lift lifts all revenue 1%.

Cancellation survey routes each reason to a save offer: 'too busy' -> pause the subscription (worked best at Codecademy since people learn to code in bursts); 'too expensive' -> temporary discount (same plan at 50% off for 3 months, then auto-return to full price) or a downgrade to a lower, hidden tier; 'negative experience' -> connect with customer support. On Stripe this needs custom logic in the payment system. Watch the share of users who take the discounts, since save tactics become widely known and get gamed.

Grouped countries into about three willingness-to-pay tiers (Nordics, Western Europe, US and Canada highest; a second tier paying less; a third paying least) and localized price level as well as currency and page content, initially pegging FX rates. Cost: 10 price packages to manage in ads, email, support docs and every future price change. Guest advises squeezing easier tactics out first.