Most “build in public” threads are performance. Screenshots of MRR charts, vague gratitude posts, zero specifics. That gets likes, not customers. Here’s what actually works.

Share the thing that helps a stranger

Your MRR number helps you, not your audience. A post that explains how you fixed a real bug, priced a feature, or lost a customer teaches something. That’s what gets saved, quoted, and remembered.

Rule: if the post could be written by a bot skimming your Stripe dashboard, skip it.

What to share

• Decisions and the reasoning, not just outcomes. “We killed our free tier because support cost more than conversions” beats “free tier is dead.”
• Specific numbers when they help someone else’s decision. Conversion rate on a pricing test. Time to first response on support tickets. Churn by cohort.
• Mistakes, named plainly. “I built the wrong thing for three months because I never talked to a user” is worth more than any launch thread.

What to keep private

• Revenue, until you’re ready to defend every follow-up question about it publicly. Once you post MRR, every future post gets read against that number.
• Anything about a specific customer they didn’t agree to have shared, even anonymized. Someone will recognize themselves.
• Salary and anything that becomes a negotiating chip against you later. Competitors and future hires read these threads too.
• Problems you haven’t solved yet, if naming them tips off a competitor before you’ve shipped the fix.

The signup math

Building in public drives signups through one mechanism: trust built by specificity, compounded over time. A single viral thread gets you a spike that churns fast. A year of honest, specific posts gets you people who already believe you before they land on your pricing page.

If you’re optimizing for one thread to blow up, you’re optimizing for the wrong metric. Optimize for “would a stranger trust this person’s judgment after reading ten of these.”

A format that works

1. State the problem in one sentence.
2. Show what you tried that didn’t work.
3. Show what worked and why.
4. Stop. No “let me know what you think!” No forced CTA.

The CTA is your bio link. People who want more will find it. Begging for engagement is the theater part — cut it.

The tell

If you’re checking analytics every ten minutes after a post, you’re building for the applause, not the audience. Write the post you’d want to read if you were three years behind where you are now. That’s the only metric that scales.

The long game

Nobody remembers your best single thread a year later. They remember whether you were right, consistently, over dozens of posts. That reputation is what turns a stranger into a signup without you ever pitching them directly — build for that, and the applause becomes a side effect instead of the point.

---