Build in Public When Nothing Shipped: What to Post This Week
Nothing shipped this week? Here are 8 concrete things solo founders and indie hackers can post to keep building in public without a product update.
Building in public works best when you show up consistently — but some weeks the commit log is empty, the roadmap feels stalled, and you have nothing obvious to announce. That silence doesn't mean you have nothing worth sharing. The whole point of build in public isn't a product demo reel; it's a transparent record of the work. This week's work might be research, a dead end, a customer conversation, or a decision you almost got wrong. All of that is postable, and in practice it often resonates more than a polished release note. This guide gives you a concrete list of what to post when nothing shipped, with worked examples and honest trade-offs for each type.
Why "Nothing Shipped" Is the Wrong Frame
The assumption buried in the question is that build in public = shipping updates. That framing puts you in a bind every slow week. It also misrepresents what the most-followed founders actually post.
Look at any long-running build-in-public account and you'll find a mix: product updates make up maybe a third of posts, while the rest is thinking out loud, problems, questions, behind-the-scenes process, and lessons from failure. The product updates get likes; the messy-middle posts get replies and shares.
The more useful frame is: build in public = documented thinking. You're not a changelog bot. You're a person making decisions in public, and decisions happen even in weeks when no code gets merged.
This reframe also solves the consistency problem. If posting depends on shipping, you post erratically. If posting is about documenting your week's thinking, you always have material.
Eight Things You Can Post When Nothing Shipped
1. A Decision You Made (and Almost Got Wrong)
Every slow week still contains decisions: which feature to prioritize next, whether to raise prices, which customer segment to focus on, what to cut from scope. Walk through one of them publicly.
Worked example:
"Spent most of this week deciding whether to build a CSV import or a Zapier integration first. I almost picked Zapier because it feels more 'startup-y.' But three customer interviews this month all mentioned CSV. Going with CSV. Here's why that matters for how I think about my roadmap..."
This post does several things at once: it shows your reasoning process, it signals you talk to customers, and it invites people who've faced the same decision to reply.
Trade-off: Be careful with decisions that involve named competitors, specific customers (without permission), or future pricing. Posting prematurely about pricing or partnerships can box you in. When in doubt, describe the type of decision without the sensitive details.
2. A Dead End or Abandoned Approach
Things you tried and dropped are chronically underposted. Founders worry it makes them look incompetent. In practice, it usually makes them look honest — which is rarer and more valuable.
Worked example:
"I spent two days building a custom onboarding flow with branching logic. By day three I realized it was solving a problem I'd imagined, not one my users had reported. Deleted the whole thing. The simpler linear flow is staying. Here's what I learned about when to trust your assumptions..."
Trade-off: Don't publicly criticize a specific tool or service you abandoned — that creates unnecessary friction and can come across as a vendor complaint rather than a learning post. Keep the focus on your own decision-making, not on what failed you.
3. A Customer Conversation (Anonymized)
User research weeks often look like "nothing shipped" because the output isn't visible code. But a good customer call is rich content.
Worked example:
"Talked to a user today who's been on the free plan for four months. I expected her to say the paid tier was too expensive. What she actually said was she didn't understand what she'd get. That's a copy problem, not a pricing problem. Fixing the upgrade page this week."
A few rules of thumb: anonymize by default (no names, no company names unless the person explicitly says you can use their name), describe the insight not the person, and get the customer's permission if you're quoting directly. How much detail is appropriate depends on your relationship with that user and what they shared — use your judgment.
Trade-off: Oversharing customer frustrations can read as venting or as a loyalty breach. Focus on what the conversation taught you, not on what the customer said wrong or what your product got wrong in a way that implicates them.
4. A Number That Surprised You
You don't need a launch to share a metric. Weekly active users, email open rate, churn, support ticket volume — any number that made you rethink something is worth a post.
Worked example:
"Support tickets this week: 11. Nine of them were the same question about how to export data. I don't have a user problem. I have a documentation problem. Writing a proper export guide this weekend."
Trade-off: Be intentional about which numbers you share publicly. Revenue figures, in particular, can affect negotiations with potential customers, partners, or investors. There's no universal rule here — some founders share MRR openly as a trust-building move; others keep it private. Know your reason either way. And if a number is early enough to be misleading out of context, add that context or don't post it yet.
5. A Question You're Genuinely Stuck On
Asking your audience for input is underused by solo founders. You have a built-in advisory group if you ask it the right questions.
Worked example:
"Genuine question for anyone running a SaaS with a free plan: how did you decide when to remove the free tier? I'm at a point where free users are roughly 40% of my support load and 0% of my revenue. I've heard arguments both ways and I'm genuinely undecided."
This kind of post works because it's specific, it respects people's experience, and it generates replies that are actually useful to you.
Trade-off: Don't ask questions you've already decided the answer to, and don't ask questions so vague they can't be answered helpfully ("What do you think about pricing?" is not a question). The post should reflect genuine uncertainty, not performed engagement.
6. A "What I Learned This Week" Recap
If none of the above categories fit, a short weekly learning recap is a reliable fallback. It's not glamorous, but it compounds well.
A weekly learning recap can be structured in four consistent parts.
Describe an experiment or action you took, even if the result was inconclusive.
Name the insight — from a customer, a metric, a tool, or your own reasoning.
What you stopped doing or cut from scope, and why.
One concrete next step. Keeps you accountable and gives you a natural follow-up post.
Step 1 of 4
One thing I tried
Describe an experiment or action you took, even if the result was inconclusive.
Worked example:
"Week 34 recap. Tried: A/B testing two subject lines on my newsletter. Learned: the boring descriptive subject line outperformed the clever one. Dropping: my habit of writing clever subject lines. Next: apply the same logic to my landing page headline."
Trade-off: Recaps can get repetitive if the structure never varies. After a few months, consider mixing in longer-form posts so the format doesn't become wallpaper.
7. A Behind-the-Scenes Process Post
How you work is interesting to other solo founders even if the output isn't ready. Tools, workflows, decision frameworks, and scheduling habits all count.
Worked example:
"My Monday morning routine as a solo founder: 20 minutes reading last week's support tickets before touching any code. It's the fastest way I've found to stay calibrated on what actually matters versus what I think matters."
Trade-off: Process posts can veer into productivity theater if they're not grounded in a real outcome or problem. Anchor the process to a specific result — "this habit helped me catch X" — or it reads as filler.
8. A Reframe of an Old Post or Past Assumption
If you've been building in public for a while, you have a backlog of posts containing assumptions you no longer hold. Revisiting one of them publicly is honest, useful, and genuinely interesting to longtime followers.
Worked example:
"Six months ago I posted that I'd never charge more than $29/month because my users are indie hackers. I've now changed my mind. Here's what shifted: [three customer conversations, one competitor analysis, one pricing experiment]. The new plan goes up to $79."
Trade-off: Don't do this constantly — it can make your thinking look unstable if you're reversing course every other week. Reserve public reframes for genuinely significant shifts, not minor updates.
How to Choose Which Type to Post
Not every post type fits every platform. Here's a rough matching guide:
Different post types suit different platforms based on depth and format constraints.
| Post type | |||
|---|---|---|---|
| Decision walkthrough | partial | yes | yes |
| Dead end / abandoned work | yes | partial | yes |
| Customer conversation | yes | yes | partial |
| Surprising metric | yes | yes | partial |
| Stuck question | yes | partial | no |
| Weekly recap | partial | yes | yes |
| Process post | partial | yes | yes |
| Reframe of old assumption | partial | yes | yes |
A stuck question works well on X or Threads where replies are fast; it falls flat in a blog post with no mechanism for quick back-and-forth. A decision walkthrough or a reframe of an old assumption has enough depth to anchor a newsletter or LinkedIn post, but can also be condensed into a thread. Match format to platform.
The Consistency Problem: What to Do When You Still Can't Think of Anything
Blank-page paralysis is real. Here are three practical ways to break it.
Keep a running "post ideas" note. Every time you hit a decision, a friction point, or a surprising result during the week, drop one line into a note. By the end of the week you have raw material even if nothing shipped. The note doesn't need to be polished — just "considered dropping free plan, decided not to because..." is enough to build a post from.
Set a low bar for "interesting." You are not writing for a general audience. You are writing for people who are also building something. What's mundane to you — how you handle a support queue alone, how you decide which bug to fix first — is specific and therefore useful to them.
Review what you've already posted. Go back three to six months. Find a claim you made that you now have more data on, or a prediction you made that turned out wrong. Write the follow-up. This requires almost no new thinking and produces one of the highest-engagement post types in any build-in-public community.
One Practical Note on Drafting
Solo founders face a real time constraint: the week that produces nothing to ship is usually also the week where every hour is already spent on something. Drafting posts when you're stretched thin is where content habits break down.
If drafting is the bottleneck, The Bason is worth a look. You feed it your ideas or rough notes, and it drafts blog posts on a schedule as well as channel-specific versions for X, Threads, and LinkedIn, which you review and edit before anything goes out. It doesn't remove your judgment from the process — you still decide what's worth posting and what isn't — but it removes the blank-page friction on weeks when you're already running low on hours.
Conclusion
Build in public doesn't require a shipped feature to justify a post. The most durable build-in-public presences are built on documented thinking, not just release notes. Decisions, dead ends, customer insights, surprising metrics, and honest questions are all legitimate content — and in practice they drive more conversation than a polished changelog entry.
The practical takeaway: keep a running note during the week, pick one idea from the eight types above, and post it. Consistency matters more than finding the "best" post type. Start with the decision you almost got wrong this week — that's usually the most honest and the easiest to write.
Comments
Loading comments…
