Growth Hacking Community: How to Find and Use a Good One

A growth hacking community is a group of marketers, founders and product people who trade experiment results: what they tested, on which channel, against what baseline, and what happened. A good one shares failures as readily as wins and shows the numbers behind a claim. A weak one trades "secret hacks" and funnels members toward a course.

This guide covers what these communities are actually for, where they tend to live, how to tell a working one from a funnel, and how to post an experiment so that people with real experience bother to reply.

What a growth hacking community is actually for

The term "growth hacker" was coined by Sean Ellis in his 2010 post "Find a Growth Hacker for Your Startup", describing a person whose every decision is judged by its effect on growth. Andrew Chen's 2012 essay "Growth Hacker is the new VP Marketing" popularised it. In both, the idea was a working method — fast, measured experiments across product, onboarding and acquisition — not a list of tricks.

That origin tells you what a useful community trades. The raw material is the experiment write-up: context, hypothesis, channel, metric, baseline, result. A tactic without that context is close to useless, because the same change behaves differently for a consumer app, a B2B tool and a cross-border store. The value of a room full of practitioners is that someone has probably run something similar in a context close to yours, and can tell you where it broke.

In their book "Hacking Growth", Sean Ellis and Morgan Brown describe a high-tempo testing process in which ideas are scored and run in short cycles. Communities that work well are an extension of that loop: they widen the pool of ideas and, more importantly, the pool of results you can compare against before you spend a sprint on something.

Where growth hacking communities live

The label covers several formats that behave differently.

Public forums and subreddits. Open spaces such as r/GrowthHacking. Low barrier and searchable, which makes them good for seeing what people are trying. The trade-off is volume: promotional posts and recycled listicles compete with real write-ups, and moderation quality decides which wins.

Founder communities. Places such as Indie Hackers, where people building small products post milestones and post-mortems. Growth discussion is mixed in with product and revenue talk, which gives useful context — you can often see the whole business behind a tactic.

Invite-only chat groups. Slack, Discord, Telegram or WeChat groups, usually small and screened. Candour is higher because posts are not public, but knowledge disappears into the scroll. The screening criteria decide who you meet: a group filtered by role produces different conversations than one filtered by industry.

Operator networks. Mixed groups where growth marketers sit alongside media buyers, sellers and service providers. Useful when your growth problem is tied to a channel or a market, for example paid acquisition in a new region. See our guide to media buyer communities for how to judge the paid-media side of these rooms.

Local meetups. Short, in-person, uneven. What you hear in a room is often more candid than anything posted online; what you take home depends on whether you follow up.

Most practitioners end up using two or three of these, each for a different question.

How to tell a real growth hacking community from a hack-list funnel

Read a week or two of posts before contributing. The pattern shows quickly.

Signals of a working community:

• Posts include a denominator — sample size, time window, baseline — not just a result.
• Failed tests are shared and discussed without embarrassment. A community that only posts wins is either selective or not testing.
• Replies ask clarifying questions about context ("what was the traffic source?", "was that new users only?") rather than answering with slogans.
• Members name the channel, market and product type, so you can judge whether a result transfers to your case.
• Moderators remove promotional posts and the removal is visible.

Signals of a funnel dressed up as a community:

• Headlines about a "secret" or "one weird" growth hack, with the details behind a DM or a sign-up form.
• Screenshots of dashboards with no time range, no baseline and no explanation of what was measured.
• A course, template pack or paid tier mentioned in most threads by the same few accounts.
• Tactics that quietly break platform rules, presented as clever rather than risky.
• Questions from newcomers answered with links to a product rather than an explanation.

None of these alone is conclusive. A community with some promotional noise can still be the best place for your question. The ratio is what matters.

How to share an experiment so people answer

Experienced members answer posts they can evaluate quickly. The most reliable way to get a useful reply is to write your experiment in the same shape a good team would log it internally:

1. Context. Product type, market, stage, main acquisition channel. Two sentences is enough.
2. Hypothesis. What you expected to change and why.
3. Change. Exactly what was different between control and variant.
4. Metric and baseline. The number you were watching and where it started.
5. Result and duration. What moved, over how long, with roughly how much traffic.
6. Your question. Specific: "is this sample large enough to trust?" or "has anyone seen the same effect hold after the first two weeks?"

Scoring ideas before running them helps too. Sean Ellis's ICE framework — Impact, Confidence, Ease — is widely used for this, and posting your ICE reasoning invites people to challenge the "Confidence" part, which is usually where outside experience helps most.

Leave out anything that identifies your accounts, your customers or your suppliers. A result is still useful with the brand removed.

Hacks that cost more than they bring

Part of the appeal of the word "hack" is the suggestion of a shortcut. Some shortcuts are fine: a better onboarding email, a referral prompt at the right moment, a faster landing page. Others carry costs that do not show up in the week-one numbers:

• Fake or incentivised reviews, which marketplaces and app stores treat as policy violations.
• Automated mass outreach on social platforms, which tends to end in restricted or suspended accounts.
• Scraping personal data for cold campaigns, which runs into privacy law in many markets.
• Engagement pods and bought followers, which inflate vanity metrics and distort every test you run afterwards.

A community that treats these as normal will also be a community where results are hard to trust. When a tactic sounds too cheap for what it claims to do, ask in the thread what the downside was. People who ran it usually know.

The short version

A growth hacking community is worth your time if it trades experiment results with context — baselines, sample sizes, failures — rather than tactics without context. Read before you post, share experiments in a structured way, and treat any single result as a lead to test, not a conclusion. If your growth work sits close to cross-border sales and paid traffic, TrafficTalking is one operator network where those conversations happen.

FAQ

Is growth hacking still a useful idea?

The label has faded from job titles, but the method it described — fast, measured experiments across the whole funnel — is now standard practice in product and marketing teams. Communities using the term are useful when they keep that experimental core.

Are paid growth hacking communities better than free ones?

Not by default. A fee filters for commitment, but it can also attract people whose main business is selling to members. Judge a paid group by a sample of its discussions, not by its price or member count.

What should I post first in a growth hacking community?

A small, structured experiment of your own, including a result that did not work. It shows how you think, gives others something concrete to respond to, and tends to get better replies than a general request for advice.