Facebook group founder reply every comment
When selling through niche Facebook groups, treat every comment as a public sales-support thread instead of dropping the post and leaving.
Why this can grow a startup
The operator in r/SaaS said the launch made $5,120 in one month from Facebook groups and that the team replied to everyone, even lightweight comments. That matters because group buyers often judge the founder before they judge the product. Public replies turn a post into a living FAQ, make the founder reachable, and give late readers proof that questions will not disappear after checkout.
Source-backed example
A first-time SaaS founder reported $5,120 in one month from Facebook groups and said the team answered the same questions across groups rather than treating comments as noise.
Source-reported evidence
Source: Reddit r/SaaS: We made $5K in one month on our first SaaS using Facebook groups only
$5,120 in one month from Facebook groups, according to the founder post.
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
When to use it
Use this when Communities, Sales, Support is relevant to facebook groups, founder-led sales, comment replies and you can run a bounded test with a free budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to Communities and Sales, using evidence from Reddit r/SaaS: We made $5K in one month on our first SaaS using Facebook groups only as context—not as a promised result.
- Record a baseline for: Users who resolve the issue and complete the next useful action. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Build creator and community systems around real incentives, trust, and repeat participation.