Not that kind of engagement farm

Grow an audience. Don't game one.

A field guide for people who built something real and now need it to be found — by the people it's for, in the places they already trust.

Sourced participation rules for the venues builders actually use, thirteen cases of contribution-led growth, the weeds to avoid, five worked path portfolios, and a method you can run yourself. Evidence has dates. Judgment has labels.

No service behind this page. Nothing to sign up for.
Read it, use it, correct it.

THE FIELDVENUESCONVERSATION
FIG. 01 — AN AUDIENCE PATHneed → venue → contribution → conversation
What this is

A product launch is an event. Distribution is a system.

Most builders are told to post more, copy a viral format, or be everywhere. This guide starts from a different question: where does your audience already look for help, and what could you contribute there that deserves attention — under that place's actual rules?

A useful product fails to find an audience when one link is missing. Most launches break at link 03 — the place. That is where this guide spends most of its pages.

It is

A field guide

Sourced rules, real cases, worked examples, and a method. Every factual item carries a link, a checked date, and an evidence label. Read it in an evening; use it for a season.

It is not

A service or a score

Nobody here researches your paths, posts for you, or ranks you. There is no fit score, no lead list, no account. The Soil Tester is a toy and says so.

It can be

Corrected

Rules change. If you moderate a venue cited here and the record is wrong or stale, tell us. Corrections are dated and kept.

Start here

Six parts. Read in any order.

How builders describe it

The felt problem is an empty room.

Verbatim, linked, from public threads. Forty-four of these were collected; six are enough to recognise yourself. Reddit links may need a cached copy.

“But when I share it here I get crickets.”

Hacker News · first-person account

“I've built an app and now I don't know how to get users and validate my idea.”

Hacker News · first-person account

“every community has its own unwritten rules.”

r/indiehackers · participant observation

“sell without coming off spammy.”

r/startups · first-person framing

“getting attention is harder than building the actual product itself.”

r/SaaS · participant observation

“mutual help, not turning every subreddit into a low quality ad board.”

r/SideProject · a community's side of it

Collected 2026-08-26. Language evidence, not outcome evidence: these tell you how the problem feels and what words people use, not what works. For what worked, see the cases.

The farm pledge

Grow recognition without manufacturing it.

The name's a joke with a thesis. Engagement farms manufacture activity. This is the field guide to the other thing — finding the ground where something real can grow, and knowing when to leave a place alone.

  • No bots, engagement pods, paid vote coordination, or fake personas.
  • No auto-posted comments, mass DMs, or scraped “ready to buy” people.
  • No generated voice presented as spontaneous human experience.
  • No hidden affiliation when your product or client is relevant.
  • No guaranteed users, virality, ranking, or revenue — from anyone.
  • No claim on this site without a source and a date.
  • No pressure to enter a place that is conditional, unclear, or closed.
The goal is not to look popular. It is to contribute something useful, learn whether the fit is real, and leave the place better than a lead list would.
Fewer guesses. Better contributions.

Know the soil before you plant a link.

Start with the rules of the places you were about to post in. Then borrow a worked portfolio and fill in the worksheet for your own product.

Nothing posts for you. Nothing guarantees growth. Not here stays on the table.