What 1 Million Organic Downloads Taught Me About Product-Led Growth Before It Had a Name

The insight that changed everything

When we launched Galvanize Test Prep, we were building for a specific, high-stakes user: a student in a Tier 2 or Tier 3 Indian city preparing for the GRE, with limited access to coaching and an enormous amount riding on their score.

That user didn't have money to waste on a mediocre app. And they talked to everyone in their network about what worked. The moment I understood that the product's distribution mechanism *was* the product's quality — that word of mouth was the only acquisition channel that mattered for our audience — everything about how we made decisions changed.

We stopped asking "what can we build?" and started asking "what would make someone pull out their phone in a conversation and say *you need this*?"

What PLG actually looks like in practice

There's a lot of theory about product-led growth. Here's what it looked like for us, concretely:

The first experience had to be undeniably good. Not a watered-down free tier designed to frustrate users into upgrading. We built the free experience to be genuinely useful — because a user who succeeds in the free tier tells people, and a user who hits a wall in the free tier just uninstalls.

Retention was more important than acquisition. We tracked what happened at day 3, day 7, and day 30. The students who came back on day 7 were the ones who recommended us. The ones who churned on day 2 never remembered us. Every product decision ran through this filter: does this improve day-7 retention?

Reviews were a product metric, not a marketing metric. When someone left a negative review, I read it the same day and filed it as a product bug. A 4.6 rating isn't a marketing achievement — it's an engineering achievement. You earn it by fixing things that frustrate people before they leave.

Localization wasn't an afterthought. We had users in 195 countries. The product needed to feel local for a student in Lagos as much as one in Chennai. That meant thinking carefully about content tone, example difficulty, and the assumptions baked into our vocabulary lists.

What this means for the products I work on now

When I work with founders as a fractional CPO today, the first question I ask isn't "what's your acquisition strategy?" It's: "If I were your ideal user and I tried your product right now, what would make me tell the next person I talked to about it?"

Most early-stage teams can't answer that question specifically. They know what their product *does*. They're fuzzy on what it *does for someone* in a way that changes their behavior.

That gap — between the feature list and the felt experience — is where product strategy actually lives. It's the work that looks invisible from the outside and determines almost everything about whether growth happens organically or not.

A million downloads didn't happen because we had a brilliant acquisition funnel. It happened because we stayed obsessed with the moment a student opened the app on a Tuesday night before a test and needed it to work.

That's the only growth strategy I've ever found that compounds.