What Running a Growth Agency Taught Me About Product Teams
When I started running a growth agency, I thought my job would be simple.
Get more users, lower CAC, scale what works.
What I didn't expect was that most growth problems had nothing to do with ads and everything to do with how product teams think, decide, and measure.
After working with multiple product-led companies, mostly apps and fintechs, I realized something uncomfortable: the fastest-growing teams don't just execute better. They are clearer about what actually matters.
1. Product Teams Don't Lose Because of Bad Ideas
They lose because feedback arrives too late.
From the outside, many product teams look busy:
- features shipping
- flows being redesigned
- long discussions around UX details
From the growth side, the issue is usually obvious:
- no single metric tied to the change
- no expected direction or magnitude of impact
- no deadline to decide if it worked
If after 7 to 14 days you cannot say "this moved (or did not) X", it was not an experiment. It was just activity.
Running an agency forces this discipline, because someone external is paying and asking what changed.
2. "More Data" Is Rarely the Problem
Fragmentation is.
Most teams already run multiple tools:
- GA4
- MMPs
- product analytics like PostHog
- ad platforms
- dashboards layered on top of all of it
Yet basic questions remain unanswered:
- which behaviors actually predict conversion
- where users stall before reaching value
- what separates users who pay from those who don't
The issue is not tooling. It is that no one owns the responsibility of connecting signals across tools into a single story.
Agencies are forced to do this by default. Product teams often are not.
3. The Best Product Teams Are Metrics-Led
The strongest teams I've worked with share one trait: they argue about metrics before they argue about solutions.
They are explicit about:
- what value means in their product
- which metric represents that value
- what should move if a change works
They still build features. They still refine flows. But every decision is anchored to a measurable outcome. Taste and intuition are still part of the process, but they are treated as hypotheses to validate, not conclusions to defend.
Growth is not something they "hand off" later. It is already embedded in how priorities are chosen.
4. What Agencies See That Product Teams Often Miss
Running a growth agency gives you distance. That distance creates pattern recognition.
You start to notice when:
- teams overbuild without learning
- roadmaps expand while understanding stays flat
- marketing is blamed for unclear product value
Most growth problems are not acquisition problems. They are product-clarity problems that only show up once traffic increases.
When ads stop scaling, it is usually because the product signal was never strong enough.
5. The One Question I'd Force Every Product Team to Answer
Every single week:
"Could we explain in one sentence why users grow or convert?"
If the answer changes depending on who you ask, that is the real bottleneck.
No roadmap fixes that.
Running a growth agency didn't teach me how to scale ads. It taught me how exposed product teams become when growth forces clarity.
Growth is not a channel. It is what happens when product decisions are tied to reality.
Originally published by Valentin Morales, Martech Director, on Medium.
https://medium.com/@valentin42401/what-running-a-growth-agency-taught-me-about-product-teams-3cbfdef4fd1e