Skip to content
TrendPost feature card: thirty squares for thirty build in public post ideas, the last three filled in copper.

Build in Public Post Ideas for Weeks You Shipped Nothing

A week with nothing shipped still gives you plenty to post when you build in public. Share a number that moved, a decision you made, a mistake, how you work, or what you learned from a customer. The strongest posts react to something your niche is discussing that day, with your own experience added.

Some weeks you ship. Other weeks go to a bug that will not reproduce, three sales calls that went nowhere, and a refactor nobody will ever see. Those weeks feel like there is nothing to post about. There is plenty. You just have to post the work instead of the release.

Here are 30 build in public post ideas, grouped by what you need to have done that week. Each one works as a single tweet or a short thread on X (Twitter), and most need nothing more than an honest look at your own week. If you have ever wondered what to tweet as a founder on a slow week, start here.

What numbers can you share?

  1. One metric, this week versus last. Signups, trials, revenue, churn. Say which way it went and your best guess why.
  2. A number that went down. Founders share wins all the time. A drop with an honest explanation stands out.
  3. Your real conversion rate at one step. Visitor to signup, or trial to paid. Most people have never seen anyone else's.
  4. What a single customer is worth to you, and how long they took to pay back what it cost to win them.
  5. Your cost to run the product per month. Hosting, APIs, tools. Founders love comparing these.
  6. Time spent this week, by category. Building, selling, support, admin. The split is usually a surprise.

Which decisions are worth posting?

  1. A feature you decided not to build, and the reason.
  2. A price change you are weighing. Post both options and ask.
  3. A tool you switched away from. What it cost you and what you moved to.
  4. A customer you turned down, or would turn down, and why they were not a fit.
  5. The one thing you are prioritizing next month, and the three things it pushed out.
  6. A decision you reversed. What you thought then and what changed your mind.

How do you post about mistakes?

  1. The bug that ate your week. What broke, how long it took to find, and the one-line fix.
  2. Something you built that nobody used. How you found out.
  3. An assumption a customer proved wrong.
  4. A launch that went quietly. What you would do differently.
  5. Advice you followed that did not work for you. Name the advice, not the person.

What can you show about how you work?

  1. Your actual stack, including the boring parts.
  2. Your weekly routine as a solo founder. When you build, when you sell, when you stop.
  3. A screenshot of your to-do list, with one item you keep putting off.
  4. A before-and-after of a page, an email or an onboarding step you rewrote.
  5. The question you ask every new customer, and the most common answer.
  6. How you handle support with no team.

What can you share from customer conversations?

  1. A paraphrased support message that changed your roadmap, with permission or with details removed.
  2. Why your last customer bought. In their words, if they agreed to be quoted.
  3. Why your last cancellation left.
  4. A feature request you get every week and still have not built.

How do you react to your niche?

  1. Your take on a story founders are discussing today. A pricing change from a big tool, a platform policy shift, a funding round in your space. Add what it means for a product your size.
  2. A thread you disagree with. Link it, say where you land, and back it with your own experience.
  3. A question someone asked in a founder community that you can answer from your own numbers.

Why do reactions to your niche carry the most weight?

The first 27 ideas come from your own week. They are good, and they run out. After a few months of building in public you have posted your stack, your routine and your worst bug. The list gets thin.

The last three never run out, because your niche talks about something new every day. The best build in public examples tend to work this way: a founder adds their own numbers or experience to something the community is already arguing about. They also reach further. A post about your own metric reaches people who already follow you. A post adding your experience to a conversation founders are already having reaches people who are searching for that conversation right now.

The catch is timing. A take on a story is worth most while the story is still growing, and much less once everyone has posted about it. Finding that story means checking several founder communities every morning and telling the rising threads from the ones that already peaked. Our guide to finding trending topics to post on X walks through that routine.

TrendPost runs the routine for you. Every morning it checks your niche's sources, measures which stories are still gaining attention, and shows 3–5 of them with the source link, the numbers and the age. Then it drafts posts in your voice, sized for X (Twitter) or LinkedIn. You add the part only you can add: what it looked like from inside your own week.

Common questions

6 answered
01What should I tweet as a founder?
Tweet what only you can see from inside your company: a number that moved, a decision and its reason, a mistake, a customer insight, or your take on a story your niche is discussing today. Specific beats polished. One real figure or trade-off per tweet gives other founders something to reply to.
02What should I post when I have not shipped anything?
Post the work behind the shipping. Decisions you weighed, numbers that moved, a bug that ate your week, a customer conversation, a feature you cut. Building in public is about showing how the product gets made, and most of that work happens in weeks where nothing visible goes out.
03How often should I post when building in public?
Often enough that people remember what you are building, and never so often that you post filler. For most solo founders that means a few posts a week on X (Twitter). A steady rhythm with something real in each post beats a burst of daily posts followed by a month of silence.
04Is it safe to share revenue numbers publicly?
It is a personal call. Many founders share revenue because it builds trust and invites useful advice. Others share ratios or growth rates instead of raw figures. Never share a customer name, a private conversation or a number someone else gave you in confidence without asking them first.
05What makes a build in public post get replies?
Something specific another founder can react to. A real number, a real trade-off or an honest question gives people something to answer. A vague update like "making progress this week" gives them nothing to say back, however consistent the posting schedule is.
06How do I find what my niche is talking about today?
Check where founders talk candidly: subreddits like r/SaaS and r/indiehackers, Hacker News, and the newsletters in your space. TrendPost does this every morning, shows 3–5 rising topics with the source link, numbers and age, then drafts posts sized for X or LinkedIn in your voice.

Keep reading

Stop hunting for topics. Get them delivered with proof.

Start free trial →

7 days free · No card needed

Questions first? Message on WhatsApp