# Channel SOP — Indie Hackers and founder communities

**Use when:** founders/builders are the ICP or credible peers can provide relevant learning, introductions, or early adoption.

**Avoid when:** the actual buyer is elsewhere and founder applause is being mistaken for demand.

## Post formula

1. State the specific problem or decision—not a victory headline.
2. Show evidence: customer wording, experiment, before/after, number with honest denominator, or failure.
3. Explain what changed and the tradeoff.
4. Ask one question peers can answer from experience.
5. Mention/link the project only when needed for context.

Useful formats: teardown, build/decision log, failed experiment, first-customer lesson, transparent launch follow-up, or request for a very specific introduction.

## Cadence

- participate in existing discussions before publishing;
- one substantial evidence-led post per week at most;
- follow up thoughtfully on comments;
- convert relevant interest into a real customer conversation, use, or introduction.

## Measure

Primary: qualified ICP conversations, introductions, activation, or payment. Peer comments/upvotes are diagnostic and are not validation unless those peers match the buyer.

Continue topics that create useful relationships and target-user evidence. Change audience/channel if only other makers engage. Never fabricate revenue, customer counts, or “building in public” drama.