Community participation

The strategy is short and most companies cannot execute it: answer the question, including when the answer is not your product.

That is not generosity. The person asking will find out what the right answer is regardless, and the only variable is whether you were the one who told them. A company that recommends a competitor once earns the right to be believed the next twenty times it recommends itself.

The operational shape

Trigger. Someone asks a question your product answers, in a place you do not own.

Reads. Voice and honest limits, from decisions and product. The conversation landscape, from the market map.

Cadence. Opportunistic, deliberately low volume.

Gate. Human-led. The constraint is authorship, not approval — this is the only capability where the requirement is that a person wrote it, not that a person cleared it.

What good looks like

Affiliation is disclosed, in the reply, before the recommendation. Most communities require it. In the ones that do not, being discovered later costs more than the disclosure ever would.

The reply answers the question asked. Not the adjacent question your product is better at. A reply that redirects is a pitch, and readers are extremely good at spotting the pivot.

It is useful to someone who never becomes a customer. That is the test. A reply that is only valuable if it converts is an advertisement placed in a conversation.

The community's norms outrank your policy. Every community has rules about promotion, some written and some not. Learning them takes reading before posting, and skipping that step is how a first reply becomes a last one.

The limits get said out loud. "This is not a good fit if you need X" in a public thread is the single most credibility-building sentence available in this category, and it costs nothing that was ever going to close.

When it goes stale

Standing does not decay. It burns.

This is the only capability here where the asset is reputation in a specific room, and where a single bad act destroys it faster than any amount of good behavior built it. Communities have long memories and searchable archives. One promotional reply in a community that forbids them, one undisclosed recommendation, one argument with a critic — any of these is remembered, screenshot, and referenced years later.

The other two mechanisms are ordinary. Absence — a company that participates only when it has something to sell reads exactly that way. And a changed answer, where an old reply recommending something that has since become wrong stays visible and attributed.

What it feeds

• FAQ pages and knowledge base — the questions people ask in public are the questions everyone has
• Learnings — objections in their rawest form, without a sales conversation shaping them
• Answer-engine citation — community threads rank and get quoted, which is why this outranks its volume

⚑ A note on sequencing. This capability carries the highest authenticity risk of anything in the set and is deliberately scheduled last. The reason is not caution for its own sake: a company that gets this wrong early cannot fix it by getting it right later.