The shift this course is about

The tools in this course — PostHog, Hogsend, a Meta pixel — are the easy part. You can install all three in an afternoon. The hard part, and the thing that actually moves the business, is a change in how you operate: you stop treating growth as a thing the marketing person does over there, and you start treating it as a system your whole team builds, measures, and improves — the same way you build, measure, and improve the product itself.

That is what "product-led growth team" means in this course. Not a job title, not a department, not a SaaS category you have to belong to. It's a way of running a startup where the product and its usage data are the engine of growth, and where growth is an engineering discipline — instrumented, measured, iterated — rather than a budget you hand to an agency and hope.

The rest of the course is the concrete version of that idea: measure honestly, keep the users you earn, then grow into an audience you own, and run the whole thing on a cadence. This chapter is the why underneath all of it.

This operating model has a reputation for being a big-company luxury — something you adopt once you have a growth team to staff it. The evidence runs the other way: the smaller the team, the more leverage the model has, because a four-person company can't afford to spend a quarter building things nobody uses or pouring money into ads that don't return. The loop this chapter describes is cheapest exactly when you're small. The most instructive recent case is Lovable — covered at length on Lenny's Podcast — which reached $200M in ARR within a year of launch with a team in the dozens, running precisely this playbook: obsessive instrumentation, activation work before spend, and growth decisions made by the people building the product. So if you're wondering whether you're too small for this — you're not. If anything, you're the ideal size for it.