Before a channel, there is a conversation

Early growth advice often begins with channels: content, partnerships, outbound, communities, paid ads. Those can all matter. But a founder who has not spent time listening to the people the product is for will struggle to make any channel work.

The first job is to understand the situation around the problem. What were people trying to do? What made it difficult? What did they try before? What changed when the problem became urgent?

Those answers shape product, positioning and distribution at the same time.

Ask about the last time it happened

The most useful questions are grounded in specific past behaviour:

  • Tell me about the last time you had to do this.
  • What happened right before it became a problem?
  • What did you use instead?
  • Who else was involved in the decision?
  • What was frustrating enough to make you look for another way?

These questions are better than \u201cWould you use this?\u201d because people do not have to predict their future behaviour. They can describe what already happened.

The Nielsen Norman Group\u2019s guide to user interviews is useful here: interviews work when they uncover needs, context and current behaviour rather than trying to validate a solution someone has not experienced.

Listen for language you did not invent

Founders often describe a product with the vocabulary of the product team. Customers describe it with the vocabulary of their work.

The difference matters. A founder might call something \u201cworkflow intelligence.\u201d A customer might say, \u201cI keep losing the next step after calls.\u201d The second sentence is a far more useful starting point for a landing page, a demo, or an outreach message because it contains the lived problem.

Collect the phrases that repeat. Do not force them into a polished narrative too quickly. The rough language tells you what people recognise immediately.

Make a small promise to a real group

Listening should lead to a narrower first promise, not a vague claim that the product is for everyone.

For example, instead of saying \u201can AI workspace for modern teams,\u201d describe the first job for the first group that has the problem: \u201cturn client calls into reviewed follow-ups for a small sales team.\u201d That is specific enough for someone to self-identify and specific enough for a founder to test.

The promise can grow later. In the beginning, clarity is more valuable than breadth.

Turn every conversation into a next action

Direct customer contact becomes growth work when it changes something tangible. After each conversation, capture:

  • the exact problem described;
  • the current workaround;
  • the words worth reusing;
  • the objection or risk that came up;
  • one change to test in product, messaging or onboarding.

This prevents \u201ctalking to users\u201d from becoming a performance. The goal is not to collect compliments. It is to make the next product or growth decision less speculative.

Keep listening after the first traction

Founder-led growth does not end when a channel starts working. The messages that bring someone in may not be the reasons they stay. New customer segments may hear the product differently. A strong loop keeps the founder close enough to spot that change.

The best early growth systems are built from that feedback: real problems, real language, a useful promise, and a way to learn again after the product reaches another person.