# The community thread should already contain the problem > A plain essay on five Quo/OpenPhone early-growth moves: Reddit alerting, adjacent problem posts, requested-feature updates, review-worthy support moments, and persona data before horizontal scale. - Canonical HTML: https://growth.iangoh.com/blog/the-community-thread-should-already-contain-the-problem/ - Published: 2026-06-07 - Updated: 2026-06-07T02:03:15Z - Categories: community-led growth, first customers, customer research - Niches: SaaS, B2B software, AI products, developer tools, local services ## On this page - Join the thread after the pain appears - Teach the adjacent question before naming the product - Let beta users feel the product moving under their hands - Ask for reviews after the customer has felt the team - Collect enough persona data before the product gets too horizontal ## Start with these related tactics - [Reddit alerts join existing buying conversations](/growth-ideas/reddit-alerts-join-existing-buying-conversations/): Set alerts for industry and competitor terms, then join relevant Reddit threads that already contain the problem instead of starting with a self-promotional post. - [Adjacent-topic posts before product mention](/growth-ideas/adjacent-topic-posts-before-product-mention/): Write useful posts around the buyer’s adjacent questions before mentioning the product, so the founder becomes part of the problem space rather than a drive-by vendor. - [Requested-feature update loop to beta users](/growth-ideas/requested-feature-update-loop-to-beta-users/): Send early users frequent progress updates and ship the features they asked for, so beta participation starts to feel like ownership. A good community thread already contains the problem. That is the quiet difference between community growth and community spam. One starts with a room that has already shown pain. The other starts with a founder hoping the room will stop what it is doing and care. Quo’s first-customer story is useful because it shows how many of the best moves happened around the product, not inside a campaign dashboard. ## Join the thread after the pain appears [Reddit alerts join existing buying conversations](/growth-ideas/reddit-alerts-join-existing-buying-conversations/) is the simplest version. Quo tracked industry and competitor terms so it could join threads that were already about the pain. That is a much better starting point than trying to make every subreddit accept a pitch. This is how I would think about market entry too. You do not want the biggest room first. You want the room where the pain is already being argued about. ## Teach the adjacent question before naming the product [Adjacent-topic posts before product mention](/growth-ideas/adjacent-topic-posts-before-product-mention/) turns dull category education into distribution. Quo wrote around business-phone questions founders were already asking. The product sat nearby, but the post did not need to begin as a product pitch. That is useful for AI tools and developer products too. The buyer often needs language for the problem before they need a vendor list. ## Let beta users feel the product moving under their hands [Requested-feature update loop to beta users](/growth-ideas/requested-feature-update-loop-to-beta-users/) is a word-of-mouth move disguised as product operations. Frequent updates and shipped requests give early users a reason to believe the team is listening. More importantly, they give those users a story to tell. The founder trap is sending updates that only celebrate the company. The stronger update says: you asked, we changed this, here is what works better now. ## Ask for reviews after the customer has felt the team [Delight moments convert into store reviews](/growth-ideas/delight-moments-convert-into-store-reviews/) is the review version of good timing. Quo connects fast product updates, timely personal support, and small gestures with strong App Store reviews. The review ask worked because something had just happened that was worth reviewing. In consumer platforms, creator tools, and local-service products, this timing matters. A review request sent after relief lands differently from a review request sent after a calendar delay. ## Collect enough persona data before the product gets too horizontal [Signup persona fields before horizontal scale](/growth-ideas/signup-persona-fields-before-horizontal-scale/) is the research move Quo wished it had done earlier. A horizontal product can collect lots of signups and still not know which segment has the real pull. A few lightweight fields can make every cohort easier to read. The trick is restraint. Ask for the data that changes your next decision. Anything else is just friction wearing a lab coat. This batch fits founder-led SaaS, AI workflow products, developer tools, and local-service software where trust comes from useful presence before it comes from scale. If you want help turning community signal into a growth system that does not feel spammy, the advisory CTA is here: [work with Ian Goh](https://iangoh.com/advisory). ## Related GrowthDex tactics - [Reddit alerts join existing buying conversations](/growth-ideas/reddit-alerts-join-existing-buying-conversations/) - Reddit, Communities, Social Listening - [Adjacent-topic posts before product mention](/growth-ideas/adjacent-topic-posts-before-product-mention/) - Content, Reddit, Communities - [Requested-feature update loop to beta users](/growth-ideas/requested-feature-update-loop-to-beta-users/) - Lifecycle, Product, Word of Mouth - [Delight moments convert into store reviews](/growth-ideas/delight-moments-convert-into-store-reviews/) - Reviews, Support, Word of Mouth - [Signup persona fields before horizontal scale](/growth-ideas/signup-persona-fields-before-horizontal-scale/) - Onboarding, Research, Analytics ## Essay chronology - [Newer essay: The GitHub release page should finish the upgrade decision](/blog/the-github-release-page-should-finish-the-upgrade-decision/) - brand trust, retention, SEO - [Older essay: The price change is a research instrument](/blog/the-price-change-is-a-research-instrument/) - first customers, pricing, operator-led growth ## Keep reading - [The first customers should leave fingerprints on the product](/blog/the-first-customers-should-leave-fingerprints-on-the-product/) - first customers, community-led growth, product-led growth - [The price change is a research instrument](/blog/the-price-change-is-a-research-instrument/) - first customers, pricing, operator-led growth - [The Show HN thread should finish the first technical conversation](/blog/the-show-hn-thread-should-finish-the-first-technical-conversation/) - community-led growth, brand trust, launches ## 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 - [Quo (formerly OpenPhone): How we got our first 1,000 customers](https://www.quo.com/blog/first-1000-customers/) · [GrowthDex source hub](/sources/quo-formerly-openphone-how-we-got-our-first-1-000-customers-quo-com/) - [OpenPhone RSS mirror: How we got our first 1,000 customers](https://openphone31.rssing.com/chan-79484123/article15.html) · [GrowthDex source hub](/sources/openphone-rss-mirror-how-we-got-our-first-1-000-customers-openphone31-rs/) - [Product Hunt: Initially failed PH launch turned around to get us 850+ paid subscribers](https://www.producthunt.com/stories/initially-failed-ph-launch-turned-around-to-get-us-850-paid-subscribers) · [GrowthDex source hub](/sources/product-hunt-initially-failed-ph-launch-turned-around-to-get-us-850-paid/) ## Editing notes - Kept one plain claim: the best community entry point is a thread where the problem already exists. - Used concrete Quo mechanics such as Reddit alerts, adjacent posts, beta updates, review timing, and signup persona fields. - Added operator perspective on market-entry rooms and review timing without pretending Ian ran these specific tactics. - Removed generic community-growth language and made each section point to a founder decision. ## Advisory If you want help turning this into a growth system, Ian Goh offers advisory at https://iangoh.com/advisory.