paid marketing

Gustaf Alströmer explains that startups should first find product-market fit by doing hands-on work that does not scale and learning directly from customers. He recommends measuring retention around the product’s core value to judge whether people keep using it. Once retention is strong, startups can improve product conversion and focus on the growth channels that fit their customers and business. For larger teams, A/B testing helps settle product decisions with evidence instead of opinion.

Dan Hockenmaier and Gustaf Alströmer explain how to build growth around product value, sustainable acquisition, and measurable outcomes. They recommend starting with retention, acquisition sources, and the full user funnel, then testing meaningful hypotheses rather than maximizing experiment count. Growth work can live in dedicated teams or across the company, but it needs clear ownership and a shared understanding of the metrics it should move. The speakers also discuss paid marketing, referrals, B2B growth, team organization, and using growth tactics responsibly.

Gustaf Alströmer explains how startups can grow intentionally, while warning that growth work is most useful after finding product-market fit. He recommends measuring a product’s core value through repeat usage and retention, then improving the user funnel through product changes, referrals, paid acquisition, and search optimization. He describes growth teams as cross-functional groups and argues that experimentation helps teams make better product decisions as they scale. The talk also covers when to begin growth work, how to assess channels, and how to use A/B tests.

Ed Baker and Gustaf Alströmer explain how growth teams evolved from viral experiments to cross-functional organizations that use data and experimentation across the company. They describe how product quality, retention, and a clear North Star metric shape growth, including the challenge of balancing riders and drivers in a two-sided marketplace. They also discuss paid acquisition, international expansion, and the operational realities of growing a real-world service. Their examples show how small changes, such as renaming invites to announcements, can have large effects, and why teams should test assumptions rather than trust intuition.