# The first customers usually come from the conversation already happening > Why problem-thread replies, founder-story context, visible product proof, manual walkthroughs, and a free-channel reachability test beat another launch-shaped fantasy. - Canonical HTML: https://growth.iangoh.com/blog/the-first-customers-usually-come-from-the-conversation-already-happening/ - Published: 2026-05-30 - Updated: 2026-05-30T16:05:00Z - Categories: community-led growth, founder-led sales, brand trust - Niches: SaaS, AI products, developer tools, creator tools, B2B software ## On this page - Start where the complaint already exists - The founder story often carries better than the feature list - Proof should show up before the form - Manual work is often the shortest route to the real objection - Distribution deserves a pre-build test, not a post-build excuse - Where this cluster is strongest ## Start with these related tactics - [Problem-thread reply before funnel build](/growth-ideas/problem-thread-reply-before-funnel-build/): Reply where the complaint is already live before you build a broader funnel, because the thread already contains pain, timing, and the language a buyer uses when the problem is real. - [Founder story before product pitch in community replies](/growth-ideas/founder-story-before-product-pitch-in-community-replies/): In community conversations, lead with why you built the thing and the buyer problem you saw before you list features or ask for the signup. - [Show the tool before asking for email](/growth-ideas/show-the-tool-before-asking-for-email/): Let strangers see what the product does before you ask for their email, because early trust is easier to earn with proof than with a gated promise. A lot of founders still think the hard part is making enough noise. Usually it is not. The hard part is being present in the exact conversation where the pain is already live, then looking credible enough that someone gives you ten minutes instead of another polite like. That is why first-customer advice feels messier than launch advice. Launch advice can be templated. First-customer work usually means replying in small rooms, showing rough proof, and doing inconvenient manual things while the product still learns what job it is really being hired for. ## Start where the complaint already exists [Problem-thread reply before funnel build](/growth-ideas/problem-thread-reply-before-funnel-build/) is the cleanest correction in this batch. If someone is already describing the problem in a Reddit thread, a forum post, or a niche community, the founder does not need to manufacture intent. The intent is already in the room. That fits naturally beside [early reply window before thread crowds](/growth-ideas/early-reply-window-before-thread-crowds/) and [permission-based founder DM after public help](/growth-ideas/permission-based-founder-dm-after-public-help/). First be useful in public. Then earn the right to continue the conversation. ## The founder story often carries better than the feature list [Founder story before product pitch in community replies](/growth-ideas/founder-story-before-product-pitch-in-community-replies/) works because buyers in community rooms are deciding two things at once. Does this problem sound familiar, and does this person sound close enough to the problem to be worth hearing out. That is different from a launch page. In a thread, the polished feature stack often loses to a plainer sentence about why the founder built the thing. It is close to [builder-written launch content](/growth-ideas/builder-written-launch-content/), except the room is smaller and the trust test is harsher. ## Proof should show up before the form [Show the tool before asking for email](/growth-ideas/show-the-tool-before-asking-for-email/) is easy to say and still regularly ignored. Founders gate the product behind a waitlist because they want to preserve optionality. The stranger sees it differently. They are being asked to trust a blank space. That is why I still like [single-screen waitlist with post-signup micro-survey](/growth-ideas/single-screen-waitlist-with-post-signup-micro-survey/) only when the page already makes the outcome visible. If the product is hard to show, use a short demo, a worked example, or one honest before-and-after. Do not ask the buyer to imagine the whole thing for you. ## Manual work is often the shortest route to the real objection [Manual SaaS walkthrough before automation](/growth-ideas/manual-saas-walkthrough-before-automation/) is what a lot of founders know is right and still avoid. It feels unscalable, which is true. It is also a faster teacher than another week of hiding inside product polish. This belongs beside [two-minute personal demo after warm interest](/growth-ideas/two-minute-personal-demo-after-warm-interest/) and [manual empty-state concierge onboarding](/growth-ideas/manual-empty-state-concierge-onboarding/). Early traction is often a done-with-you service wearing a software costume for a while. That is not fraud. That is the founder finding the edges of the job. ## Distribution deserves a pre-build test, not a post-build excuse [Free-channel reachability test before second build](/growth-ideas/free-channel-reachability-test-before-second-build/) is the hardest rule here because it ruins a lot of fun ideas. But it is good discipline. Before the next build cycle, can you name the communities, search terms, or public rooms where a few thousand plausible buyers can actually be reached without money. That is where [customer-source interviews before the channel bet](/growth-ideas/customer-source-interviews-before-channel-bet/) gets more useful. One tactic asks where current buyers already look. The other asks whether that route is reachable enough to deserve another product bet. ## Where this cluster is strongest This cluster is strongest for SaaS, AI products, developer tools, creator tools, and B2B software where the first customer often arrives through a narrow conversation before any scalable loop exists. It is especially useful for founders who keep mistaking launch surfaces for demand surfaces. If I were tightening one this week, I would ask five blunt questions. Which live thread already contains the complaint. Does the founder story explain why this product exists in one plain sentence. Can a stranger see the tool before the form. What part of the onboarding can be done manually this week. Can the next five thousand plausible buyers be reached without pretending ads will save the idea. If you want help turning community conversations, founder-led proof, and early demand capture into a cleaner growth system, the advisory CTA is here: [work with Ian Goh](https://iangoh.com/advisory). ## Related GrowthDex tactics - [Problem-thread reply before funnel build](/growth-ideas/problem-thread-reply-before-funnel-build/) - Reddit, Communities, Founder-led - [Founder story before product pitch in community replies](/growth-ideas/founder-story-before-product-pitch-in-community-replies/) - Reddit, Communities, Positioning - [Show the tool before asking for email](/growth-ideas/show-the-tool-before-asking-for-email/) - Website, Demo, Acquisition - [Manual SaaS walkthrough before automation](/growth-ideas/manual-saas-walkthrough-before-automation/) - Founder-led, Calls, Customer Development - [Free-channel reachability test before second build](/growth-ideas/free-channel-reachability-test-before-second-build/) - Research, Distribution, SEO ## Essay chronology - [Newer essay: The Product Hunt page should keep working after launch day](/blog/the-product-hunt-page-should-keep-working-after-launch-day/) - Product Hunt, launches, SEO - [Older essay: The answer should travel before the queue grows](/blog/the-answer-should-travel-before-the-queue-grows/) - support-led growth, brand trust, SEO ## Keep reading - [The waitlist should act like a working queue](/blog/the-waitlist-should-act-like-a-working-queue/) - community-led growth, waitlists, founder-led sales - [The feedback loop breaks when the middle stays hidden](/blog/the-feedback-loop-breaks-when-the-middle-stays-hidden/) - product-led growth, community-led growth, brand trust - [The first customers should leave tracks for the next ones](/blog/the-first-customers-should-leave-tracks-for-the-next-ones/) - early-stage growth, founder-led sales, brand trust ## Continue through the blog - [SaaS](/blog/#path-saas) - 3 essays in this path - [AI products](/blog/#path-ai-products) - 3 essays in this path - [developer tools](/blog/#path-developer-tools) - 3 essays in this path ## Sources - [Reddit /r/SaaS: How I was acquiring customers backwards](https://www.reddit.com/r/SaaS/comments/1srlwig/how_i_was_acquiring_customers_backwards/) · [GrowthDex source hub](/sources/reddit-r-saas-how-i-was-acquiring-customers-backwards-reddit-com/) - [Reddit /r/SaaS: How we got 412 waitlist signups for an AI sales tool without spending on ads](https://www.reddit.com/r/SaaS/comments/1s1c71w/how_we_got_412_waitlist_signups_for_an_ai_sales/) · [GrowthDex source hub](/sources/reddit-r-saas-how-we-got-412-waitlist-signups-for-an-ai-sales-tool-witho/) - [Reddit /r/SaaS: I launched a SaaS and learned more in 90 days than in 4 years of reading startup books](https://www.reddit.com/r/SaaS/comments/1saa0zx/i_launched_a_saas_and_learned_more_in_90_days/) · [GrowthDex source hub](/sources/reddit-r-saas-i-launched-a-saas-and-learned-more-in-90-days-than-in-4-ye/) - [Reddit /r/founder: How are you getting users after launching?](https://www.reddit.com/r/founder/comments/1t0kzrc/how_are_you_getting_users_after_launching/) · [GrowthDex source hub](/sources/reddit-r-founder-how-are-you-getting-users-after-launching-reddit-com/) - [Reddit /r/SaaS: Launched 4 SaaS in 18 months. All solved real problems. Only 1 made money.](https://www.reddit.com/r/SaaS/comments/1qxit3q/launched_4_saas_in_18_months_all_solved_real/) · [GrowthDex source hub](/sources/reddit-r-saas-launched-4-saas-in-18-months-all-solved-real-problems-only/) ## Editing notes - Kept the essay on one claim: first customers usually come from live conversations, not launch theater. - Used ordinary objects like threads, forms, demos, calls, and communities instead of abstract growth language. - Cut generic startup mythology and kept the argument tied to what founders actually did in public rooms. - Ended with five operating questions so the piece stays practical after the reader leaves the page. ## Advisory If you want help turning this into a growth system, Ian Goh offers advisory at https://iangoh.com/advisory.