forsvn-labs Write social and community marketing
Produce ready-to-post work that fits the community, actor, and audience. Verify current platform rules and format limits when they affect the result.
Establish channel fit
Determine:
- actor: founder, company, employee, customer, or community participant;
- audience and community purpose;
- useful idea, product change, evidence, or question;
- affiliation and disclosure requirements;
- native format and realistic CTA;
- strongest skeptical response.
Recommend not posting when the community-product fit is weak. Never manufacture engagement, votes, controversy, vulnerability, authority, or customer advocacy.
Apply the channel
Product Hunt
Classify the product with a concrete, differentiated tagline. Explain the problem, mechanism, why now, and invitation for feedback. Make gallery assets tell a progressive product story. Prepare honest answers on audience, alternatives, pricing, privacy, and roadmap. Measure qualified activation and objections, not rank alone.
Check the specific community's current rules and norms. Lead with a useful observation, artifact, result, or honest question. State affiliation plainly. Make the post valuable without the click. Prefer one well-matched community over cross-posting the same pitch.
X
Put the claim, observation, or product change in the opening line. Compress wording, not meaning. Use a thread only when sequence creates cumulative value. Make media carry evidence. Write replies that advance the idea rather than repeat it.
Open on a concrete professional tension, result, or lesson. Prefer lived specificity and real tradeoffs over inspiration. Keep line breaks readable without theatrical fragmentation. Use founder voice for conviction and learning; company voice for product truth and proof.
Deliver
Return the final native post or listing first. Include only the useful supporting pieces:
- alternate hook or title when it tests a genuinely different angle;
- honest disclosure line;
- media or gallery brief;
- reply bank for likely questions and objections;
- sequence timing when multiple posts have distinct roles;
- measurement and a decision date.
Keep publishing and account actions behind explicit approval. If the host cannot guarantee that boundary, stop with the ready-to-post package.