The lesson
Show the internal adoption system that made the product useful, not only the product that was bought.
The page opens with the title, a Babbel product and market snapshot, and three proof points: “10 million subscriptions sold,” “#1 selling language learning app,” and “14 languages offered.” The story then moves from “Becoming a data-driven company” to the analytics team’s ad hoc request problem and a named quote from Jakob Willisch. It explains Babbel’s Amplitude rollout, then uses “Data access alone is not enough” to list workshops, weekly meetings, Slack support, bug documentation and data protocols before showing how the Product Performance team uses Amplitude in “Putting out better content, more quickly” and “An improved way of working.”
Don't copy Babbel's language-learning category, Product Performance team, or internal enablement details. Keep the structure of business context, analytics bottleneck, self-service rollout, adoption infrastructure, team workflow and named customer quotes.
Tell us what you want to make. We’ll talk through how to put these ideas to work for your brand.