7d • General discussion
Saturday Summary
Hi All,
Just want to share a bit from my learning last week.
I continue to support founders across different SaaS and technology businesses, and one topic came up again:
Can you start acquiring users before you are fully clear on ICP, use case, and value?
My honest answer is yes — but with a big caution.
You can start conversations. You can start testing messaging. You can start learning from the market.
But scaling acquisition too early can create noise.
What I mean is this:
If the ICP is not clear, you may attract the wrong users.If the use case is not clear, your message becomes too broad. If the value is not clear, even interested users may not convert.
So, the real question is not:
“Should I start acquisition?”
The better question is:
“Am I using acquisition to learn, or am I expecting it to scale?”
There is a big difference.
In the early stage, acquisition should help you validate:
- Who is reacting to the problem?
- Which use case creates the strongest urgency?
- What value message gets attention?
- Which segment has the highest willingness to engage?
This connects back to the first part of my G.R.O.W.T.H framework — Groundwork.
Before trying to scale growth, founders need enough clarity on:
- ICP
- Core problem
- Value promise
- Use case priority
- Success metric
Not perfect clarity. But enough clarity to avoid wasting time and budget.
My learning from last week:
You do not need to pause acquisition until everything is perfect. But you should not confuse early acquisition testing with scalable growth.
Curious to hear from others:
Have you seen founders trying to scale acquisition before their ICP or value message was clear?
Would love to hear your thoughts.
0
1 comment
Saturday Summary
powered by
skool.com/plg-product-led-growth-1547
For SaaS founders: sharp PLG thinking, lessons from G.R.O.W.T.H. framework, and office hours on real growth bottlenecks.
Suggested communities
Powered by