Posting on Peerpitch is how you build in public. Every update you share does three things at once: it maintains your daily streak, it earns Peerpoints, and it puts your work in front of an audience of builders who are genuinely rooting for you. Over time, consistent posting compounds — the builders who followed Ishaan Kapoor's journey before his launch already knew his work when he was ready to ship. That warm audience is built one post at a time, starting today.
Creating a post
To post, click + Post in the top bar of the feed at /home. The composer opens with a text field and a post type selector. Write your update, pick the type that fits, and hit Publish. That's it — your post is live.
Click + Post
Find the + Post button in the top bar of the feed. It's always visible when you're logged in.
Choose a post type
Select the hashtag that best fits what you're sharing. The post type signals to your readers how to engage — a #ask invites answers, a #show invites reactions to what you built.
Write your update
Keep it honest and specific. The most-reacted posts on Peerpitch aren't polished — they're real. Yuki Tanaka's #ask — "Solo founders — how do you decide what NOT to build? My backlog has 200 ideas." — earned 145 reactions because it named a feeling everyone recognizes.
Publish
Hit Publish. Your post appears in the All feed instantly and counts toward your streak for today.
Post types
Every post on Peerpitch carries a hashtag that tells readers what kind of content to expect. Use the type that honestly matches what you're sharing.
| Post type | Use it when you want to… | Example |
|---|---|---|
| #show | Share something you've built or shipped | "Launched a screenshot API — one endpoint, give it a URL, get back a clean screenshot." |
| #update | Log daily progress on your project | "Quietly shipped an uptime monitor last week. No big launch, just put it live." |
| #discuss | Share an opinion or spark a conversation | "Unpopular opinion: most 'build in public' growth is just other builders watching each other." |
| #ask | Put a question to the community | "Solo founders — how do you decide what NOT to build?" |
| #note | Drop a short observation or bookmark | "Distribution beats product more often than founders want to admit." |
| #learning | Share something you learned today | "Charge money before you think you're ready. Free users tell you what's nice to have. Paying users tell you what's necessary." |
| #stuck | Ask for help with a specific blocker | "Spent two days debugging a race condition that was just me not awaiting a promise." |
Tips by post type
#show — Ship it, then show it
Use #show right after you've shipped something — a feature, a product, a side tool. Don't wait until it's perfect. Linh Nguyen launched a screenshot API with #show and earned 85 reactions from other builders who'd suffered through unreliable alternatives. Show the thing, explain what it does, and link to it.
#update — Make your process visible
#update is your daily work log made public. Be specific about what you actually did — not "worked on the product" but "shipped the first working version of the summarizer." Kwame Mensah's #update — "Quietly shipped an uptime monitor last week. No big launch, just put it live." — earned 181 reactions precisely because it was understated and real. Specificity wins.
#discuss — Lead with your honest take
#discuss posts that perform best have a clear point of view. Don't hedge. Mathis Moreau's "The 'overnight success' you're jealous of has a graveyard of dead projects behind it you never saw" earned 104 reactions because it named a hard truth without softening it. Write the thing you actually believe.
#ask — Be specific about what you need
A good #ask is narrow enough to get a useful answer. Yuki Tanaka's question — "How do solo founders decide what NOT to build?" — worked because it had a specific audience (solo founders) and a specific pain (prioritization). Vague questions get polite non-answers. Focused questions start real conversations.
#note — Short is fine
#note is the lowest-stakes post type. A single observation, a link worth sharing, a sentence that crystallized something for you today. There's no minimum length requirement. Notes are a great way to post on days when you don't have a big update — and they count toward your streak just as much as anything else.
#learning — Teach what you just figured out
The best #learning posts feel like someone handing you the answer to a problem you haven't hit yet. Nour Saleh's learning — "Free users tell you what's nice to have. Paying users tell you what's necessary" — earned 21 reactions because it was specific, earned from experience, and immediately useful. Write your learning as if you're leaving a note for yourself six months ago.
#stuck — Name the exact problem
When you're blocked, post it. Describe the specific problem, what you've already tried, and what you think might be causing it. Aisha Khan's #stuck post — "Spent two days debugging a race condition that was just me not awaiting a promise" — helped other builders who'd hit the same wall. Your blocker today is someone else's tutorial tomorrow.
Reactions and comments
Every post can receive reactions (a thumbs-up from the community) and comments (threaded replies). Reactions are a lightweight signal of resonance — a nod from a fellow builder who saw themselves in your post. Comments are where the real conversation happens.
To react, click the reaction icon on any post. To comment, click the post to expand the thread and type your reply. Both actions are visible to the original author and notify them.
Every post you publish — regardless of type or length — counts toward your daily streak and earns Peerpoints. A single #note at the end of a long day is worth the same streak credit as a detailed #update. Consistency matters more than length. See the Streaks page for how streaks work and the Peerpoints page for the full points breakdown.