What to post on X when you have nothing to say

The composer is empty because you are looking for an idea, and ideas are rare. What is not rare is material: things that already happened today. A post is one piece of material plus one observation about it. Once you stop waiting for an idea and start scanning the day for material, the problem goes away. The prompts below are a scan.

A useful rule: if it took you more than a second to decide, someone else is deciding it right now. That is your reader. Tell them what you picked and why, in the words you would use to a friend.

• A decision you made today

  Copy

  Killed the free plan this morning. 14 months of "we'll convert them later". We converted 9. Trial with a card from now on. Will report back in 30 days.

  Why it works:

  A decision with the number that forced it and a promise to follow up. People reply with their own free-plan stories.

• A message you sent to a customer

  Copy

  Told a customer today that we won't build the thing they asked for. Hardest email I've written this month. Also the right one. Saying no to one person is how you keep saying yes to the rest.

  Why it works:

  Everyone who has a product has sent this email. The last line is quotable without being a motivational poster.

• A number you checked

  Copy

  Checked where last week's signups came from. 61% replies on other people's posts 22% my own posts 17% everything else I spend most of my time on the 22%.

  Why it works:

  Real numbers, a ratio, a small confession. The post teaches something without claiming to be a lesson.

• A tool that annoyed you

  Copy

  Spent 40 minutes today fighting a date picker. Not building one. Not using a library. Fighting the one I chose last year because it saves 12kb. 12kb. Forty minutes.

  When:

  You lost time to something small.

  Why it works:

  Specific, self-mocking and relatable to anyone who has optimised the wrong thing.

• Something you changed your mind about

  Copy

  A year ago I'd have said "post every day or don't bother". Now: post when you have something, reply every day. The replies grew the account. The daily posts mostly trained me to write.

  Why it works:

  A before and after of your own opinion is honest and invites people to share their own reversals.

• Advice you ignored and regret

  Copy

  "Talk to users before you build it." Heard it a hundred times. Built the thing anyway. Three months. The first user call took 25 minutes and would have saved all three.

  Why it works:

  The regret is specific and the cost is quantified. The reader feels the lesson instead of being told it.

• A small rule you follow

  Copy

  Rule I stick to: no new feature ships without a sentence on the changelog a customer could understand. If I can't write the sentence, the feature isn't done.

  Why it works:

  Rules are easy to adopt and easy to argue with, so they get both saves and replies.

• The thing you keep explaining

  Copy

  Explained to the third person this week why we don't do yearly plans at launch. You can't refund your way out of a bad first year. Monthly keeps you honest. Writing it here so I can link it next time.

  When:

  You answered the same question twice recently.

  Why it works:

  If you keep explaining it in private, people are searching for it in public. Posting it saves you time and shows expertise.

• What you are working on, as a question

  Copy

  Rewriting our onboarding email. Current first line: "Welcome to the team!" We are not a team. They bought a tool. What would you open with?

  Why it works:

  You show the work, admit the flaw and ask a question with a one-line answer. This shape gets replies reliably.

• The thing you shipped, however small

  Copy

  Shipped: you can now paste an image into the composer instead of clicking upload. Took two hours. Three people asked for it. Should have done it in March.

  When:

  You are tempted not to post because the change feels too small.

  Why it works:

  Small ships with a small confession read as momentum. Nobody expects a launch every day.

• What you are reading or watching, with a take

  Copy

  Reading old Paul Graham essays again. The thing nobody mentions: half of them are about writing, not startups. Maybe that's why the founders who read them write well.

  Why it works:

  A familiar reference plus an observation that is actually yours. The take is the post, the reference is the hook.

• What you are avoiding

  Copy

  Things I did today instead of recording the demo video: Refactored the settings page Rewrote the pricing FAQ Changed the favicon The video takes 20 minutes. Tomorrow. Probably.

  Why it works:

  Procrastination lists are funny because they are true, and people reply with their own.

1. 01Pick the prompt that matches the day. Do not browse all twelve; the first one that makes you think of something is the one.
2. 02Write the material first, plainly: what happened, with the number or the name or the time.
3. 03Add one observation: what it cost, what you would do differently, what it taught you, what you want to know.
4. 04Cut the first sentence if it is a warm-up. Most posts start one line too early.
5. 05Break it into short lines with a blank line between thoughts. On X, white space is punctuation.
6. 06Post it, then spend the next twenty minutes replying to other people. The replies are where the post gets its first readers.

If you want a stock of these for bad days, write three when a good day gives you material and schedule them. The guide on how often to post on X covers how to keep a queue without it turning into filler. If your first line is not pulling people in, post hooks for builders shows the openings that do.

The difference between the two columns is one word: today. A post that could have been written by anyone on any day is filler. A post that could only have been written by you, today, is content, even when it is small.