What founders can post on X, with 14 full examples

People follow founders to watch someone make decisions with real stakes. Not to be taught, not to be sold to. The moment a founder account starts posting frameworks and quotes it becomes indistinguishable from the ten thousand others, and the moment it starts posting what happened in the business this week it becomes the only one of its kind.

That gives you a filter for every post: does this reveal a decision, a number or a conversation that only I had access to? If yes, post it. If it could have been written by anyone with a business degree, it is filler, however well it reads.

• A decision with the road not taken

  Copy

  We picked annual-only pricing for the first 100 customers. Monthly would have given us more signups and less cash. Cash buys time. Time is what we were short on.

  Why it works:

  Stating the alternative shows you considered it. Founders who chose monthly will tell you why, which is the conversation you want.

• A number with its context

  Copy

  MRR this month: $4,120. Same number as June. Difference: June was 61 customers, now it is 44. Fewer people paying more. Not sure yet if that is good.

  Why it works:

  A flat headline number with a moving story underneath. Admitting you are not sure invites people to argue it out for you.

• What you spent and what it bought

  Copy

  Spent $1,800 on a designer for the landing page. Conversion went from one visitor in a hundred to one in forty. Best money this year, and I argued against spending it for a month.

  Why it works:

  Price, outcome and a small confession. The confession is what makes it a post rather than a receipt.

• The metric you stopped tracking

  Copy

  Stopped looking at signups. Started looking at how many people come back on day 3. Signups made me feel good. Day 3 tells me if the product works.

  Why it works:

  A change in what you measure is a change in how you think. Other founders will reply with the number they watch.

Your customers hand you posts every week in support emails and calls. Quote them (without names unless they agree), say what you did about it, and stop. These posts also quietly tell potential customers that you listen, which no feature list can do.

• A customer sentence, quoted

  Copy

  A customer told me today: "I use it, but I would not miss it." That is the most useful review I have had all year. Building something people would miss is the whole job.

  Why it works:

  A hard sentence, taken seriously instead of defensively. The last line is the lesson, but the quote does the work.

• A churned customer

  Copy

  Lost a customer this week. Asked why. "Your tool is great, I just stopped doing the thing it helps with." Can't fix that with a feature. Can fix who I sell to.

  Why it works:

  Churn posts are rare because they sting. That is why they get read, and the conclusion shows you learned the right lesson.

• A competitor's move

  Copy

  Our biggest competitor dropped prices today. Not matching. We sell to people who already tried the cheap option. Ask me again in six months whether that was brave or dumb.

  Why it works:

  A live decision under pressure, with a date to check back. People bookmark posts with a deadline in them.

• What they asked for versus what you built

  Copy

  Twelve people asked for a mobile app. Built a better email digest instead. Eleven of the twelve use it daily. People ask for the shape they know.

  When:

  You solved a request with something other than what was requested.

  Why it works:

  A product lesson told as a story, with a quotable last line that is earned by the numbers above it.

• A hiring lesson

  Copy

  First hire: a senior engineer I could barely afford. Would do it again. The three months of runway it cost bought a year of not rewriting things.

  Why it works:

  Hiring posts usually avoid money. Naming the cost in runway makes this one useful to a founder facing the same choice.

• Raising prices

  Copy

  Doubled the price for new customers on Monday. Signups down by about a third. Revenue from new signups up. The people who left were the ones who emailed support most.

  Why it works:

  A pricing change with both sides of the result and an observation that is slightly uncomfortable. Pricing posts always get replies.

• Saying no to money

  Copy

  Turned down a $30k contract today because it needed a feature only they would use. Writing it here so I remember how much it hurt and why it was right.

  Why it works:

  Posting a decision as a note to yourself is honest and makes readers feel they are watching, not being taught.

Lesson posts are where founder accounts go wrong, because the lesson arrives without the event that produced it. Keep the event attached. A lesson with a cost next to it reads as experience; a lesson on its own reads as a poster.

• A mistake with the cost attached

  Copy

  Spent four months on an integration nobody asked for because a famous founder said integrations are moats. Moats are for companies with castles. I had a tent.

  Why it works:

  The cost is four months, the cause is borrowed advice, and the last line is funny because it is true.

• Advice to last year's self

  Copy

  Last year I would have told you to build faster. This year: talk to five customers before you touch the editor. Every single week. The code was never the bottleneck.

  Why it works:

  A reversal of your own advice is more credible than advice. It also shows growth without claiming it.

• A question for other founders

  Copy

  Founders who went from solo to a team of three: what did you stop doing, and what did you regret stopping?

  Why it works:

  Narrow audience, concrete moment, two-part answer. The replies become a resource people save. More shapes like this are in question posts that get replies.

1. 01On Friday, list every decision you made this week that took more than a minute. There will be more than you think.
2. 02Next to each, write the number or the sentence that forced it. No number and no sentence means it is not a post yet.
3. 03Pick the two that you would be slightly nervous to post. Nerves usually mean there is a real opinion inside.
4. 04Write each one as what happened, then what it cost or taught, then stop. Cut any line that explains the lesson a second time.
5. 05Schedule one for Monday and one for Thursday. Spend the saved time replying to other founders; the reply examples for founders show what to say.

If the week produced nothing you can share, say so in one line, or skip the post and reply instead. The guide to growing on X as a founder covers how to balance posting and replying when you also have a company to run.

The accounts worth following are the ones you could not have written yourself. Keep posting the decision, the number and the sentence, and the opinions will take care of themselves.