15 X Post Ideas for Indie Hackers to Grow Your Audience

You shipped something on Tuesday. On Wednesday a customer's card failed and you spent an hour in support. On Thursday you have nothing to post except the same 'just shipped a feature' line you posted last week.

Most indie hackers on X end up posting three things: a launch, a milestone and a link to the product. Those posts are real, but the same three on repeat stop reaching the people you want. Your revenue also sits next to customer names and invoices you can't show, so it feels safer to post nothing.

This page gives you 15 post ideas taken from work you already do: revenue reports, failed ad tests, billing fixes, support questions, launch days and pricing emails. Each idea has a template with brackets for your details and a real post that shows the idea working.

All 15 ideas at a glance

Why X works for indie hackers

X is where builders read about builders. The people who reply to indie hacker posts are usually other founders, developers and marketers, and some of them are the affiliates, partners and buyers you want. A new account usually gets seen through replies under larger accounts in the same niche, so reply first and post second.

Most of your posts should teach something any builder could use. About one in three can be a product update. Posts that admit a failure often do better than posts about a win, so keep a few honest numbers in the mix.

  • Text post: Free accounts can post 280 characters. Premium posts can run to 25,000 characters, which fits a monthly number and the reason behind it. Use it for revenue updates, decisions and prompts that people answer in the replies.
  • Thread: A thread can hold up to 50 posts. Use it for bug postmortems, launch-day recaps and step-by-step fixes, where each post should still make sense when someone screenshots it alone.
  • Short vertical video: A 9:16 video can run up to 140 seconds on a standard account. The feed plays video without sound, so put the words on screen. Use it for screen recordings of a fix, a page roast or a support answer.
  • Image post with a checked screenshot: A chart or dashboard image gives a number its context. Check the exported file for customer details before you post. Use it for MRR charts and launch-day signup graphs.

15 X content ideas for indie hackers

Revenue and the numbers behind it

These posts show what you earn and what it took to get there. Other builders get a benchmark, and your reader gets a reason to check the next update.

Text post with a chart image

1. A monthly revenue update that separates MRR from revenue

Why it works: Builders question whether a revenue number is real, and the replies to a bare figure are usually that question. A post that puts MRR and revenue on separate lines, with the hours you spend each day, answers those questions before they are asked. The number also gives your niche something to compare against.

Template[Month] update for [product]: $[MRR] MRR, $[revenue] revenue, [N] paying customers. MRR and revenue are different. The gap this month came from [reason, e.g. annual plans paid up front]. I spent [N] hours a day on it, mostly on [support, bug fixes or sales].
The post splits revenue from MRR in its first lines, then says how many hours a day the founder works and on what.X

Thread

2. The plateau math: why my MRR stayed flat for [N] months

Why it works: A founder stuck at a few hundred dollars a month reads the arithmetic before any advice. Flat months shown as exact new and lost customers make the reader check their own numbers, which is why they reply. Each stall in the thread can become its own post later.

TemplateMy MRR sat between $[low] and $[high] for [N] months. Each month I gained [N] customers and lost [N]. Here is the math: [one line showing the gap]. The one change that moved it: [change, with the number before and after].
It opens with three flat months as exact customer counts, then turns each stall into a lever.X

Text post

3. What a failed ad test cost in dollars and paying users

Why it works: Indie hackers buy ads often and most of them are not sure what they should have tested first. A test with the exact spend and the paying-user count tells the reader what to skip. Failure posts like this often get more replies than a launch announcement.

TemplateI spent $[amount] on [channel] over [N] weeks. Result: [N] visits, [N] signups, [N] paying users. If I ran it again I would test [one change] first, and I won't spend another dollar until [condition].

Text post

4. Where my paying customers came from, with the share from X

Why it works: A follower count does not show where paying customers come from. A split by channel shows whether X is doing the work, and readers who run a product will ask how you tracked each signup. Showing the method makes the number worth more.

TemplateOf my [N] paying customers, [N] came from [channel], [N] from [channel] and [N] from X. I have [N] followers on X. I tagged each signup by [method, e.g. a question on the signup form].
It sets the follower count against the share of customers from X in two short sentences, then leaves the comparison to the reader.X

Build log and fixes

Shipping and fixing are the events a solo builder has most often. These posts show the work and the fix, so another builder can use them on their own product.

Short vertical video or text post

5. The billing fix that took one setting

Why it works: A customer who cannot pay is a bigger story than a new feature. Business buyers often need a company name or tax ID on the receipt, and their accountant will reject a receipt without it. Showing the exact setting makes the fix easy for another founder to copy.

TemplateA [type of customer] could not pay for [product] for [N] days. Their accountant kept rejecting the invoice because [missing field]. The fix was one setting: [setting]. It took [N] minutes.
The blocker was the invoice rather than the product, and the post names the detail that was missing from it.X

Thread

6. Bug postmortem with the timeline and the email you sent

Why it works: When a bug blocks paying users, existing customers want to know what happened and whether they lost anything. A thread with timestamps shows how you handle trouble, and that is what a buyer checks before paying for a small tool.

TemplateOn [day] at [time], [N] users could not [action] for [N] hours. Here is what broke: [cause]. Here is what I changed: [fix]. Here is the email I sent to the [N] affected accounts: [paste the first two lines].

Text post

7. The feature I killed after [N] customers asked for it

Why it works: Solo founders get feature requests in the support inbox, and many of them come from one customer. A post about a feature you chose not to build shows the reasoning. It also invites readers who run products to say what they would cut, which starts the replies.

Template[N] customers asked for [feature] this month. I asked the [N] who asked for it what they would do without it. [N] said [answer]. I am not building it. Instead I am doing [change].

Short vertical video with a screen recording

8. A support question I answered in the app instead of by email

Why it works: Support email takes the hours a solo founder doesn't have. A screen recording of one question answered inside the product shows a fix and a saved hour in under a minute. The question also uses the words customers really type, which your reader can reuse on their own site.

Template[N] people emailed me this week asking [question, in their words]. I added [screen or setting] so they can see the answer in the app. Here is the screen before and after. Find it at [location in the product].

Teardowns and how-tos

These posts teach one skill that another builder can use this week, such as a landing page fix or a failed-payment email. Your product is the worked example, not the pitch.

Short vertical video with on-screen captions

9. A 60-second landing page roast

Why it works: Founders watch to see what would change on their own page, and most of the people watching run a site that looks similar. A roast works when the founder has agreed to be shown. The replies then turn into a queue of new pages to review.

TemplateI roasted [N] landing pages for [type of founder] this week. This one is [product], shown with permission. The first fix: [specific change to the headline, photo or price]. Drop your page in the replies and I'll pick one for next week.
The post lists four fixes as a numbered list, each one a copy or photo change a reader can make on their own page.X

Thread, with each email in its own post

10. The three emails I send when a card fails

Why it works: Failed card payments happen to most subscription products, and most builders write the recovery emails from scratch. Posting the actual wording gives other builders something to copy, and a thread like this gets bookmarked. The reader can change the words to fit their own product.

TemplateA card failed on [N] accounts last month. Here are the [N] emails I now send. Email 1, sent [hours] after the failure: [subject and first line]. Email 2, sent on [day]: [subject and first line]. Email 3, sent on [day]: [subject and first line].

Image post with the signup chart

11. The day-after signup numbers from a launch

Why it works: Most launch posts stop on launch day. Showing the second day and what caused its signups gives builders a plan for their own launch. A single chart with a clear cause is easy to save and reuse.

Template[Product] launch day: [N] signups. The day after: [N] signups. The jump came from [source, e.g. a newsletter send]. If you launch next week, write the day-after email before launch day and test that it lands on [onboarding step].
One chart shows the second day, and one line gives the cause of the spike.X

Text post

12. The pricing change email and what happened to new signups

Why it works: Pricing questions come up constantly for small SaaS products, and most builders keep their price changes private. The exact email and the signup numbers before and after give a reader a template and a benchmark. Existing customers' replies show how the change was received.

TemplateI moved [product] from $[old price] to $[new price] on [date]. Before: [N] signups a week. Four weeks after: [N] signups a week. Current customers got this email: [first two lines]. [N] of them replied, and one said: [short quote].

Conversation starters

These posts ask other builders to reply. Replies are where new readers find your account, so write each question so a builder can answer it in one line.

Text post

13. Drop your product, your MRR and the one number you check weekly

Why it works: Builders like to see what others are working on, and a list in the replies becomes a directory you can read and reply to. Asking for a number as well as a product gets specific answers, and specific answers are what the next reader wants to see.

TemplateIndie hackers, drop your product, your current MRR and the one number you check every week. I'll reply to the first [N] with one idea each.
A short prompt that asks for product names and lets the replies do the work.X

Text post

14. What I had the month I quit my job

Why it works: Builders and their partners want to know how much runway a side project really gives. A post with the revenue, the followers and the old salary side by side gives the reader a comparison they can make against their own situation.

TemplateWhen I quit my job I had $[revenue] a month from [N] products, [N] followers and a salary of $[salary]. If you are at $[your revenue] right now, here is what I would do next: [one line].
It sets the revenue, the followers and the old salary next to each other, then ends with a plain comparison to the reader.X

Text post

15. A hot take on copycat tools in your niche

Why it works: Cheaper AI-built clones worry many indie hackers. A clear opinion with a question at the end draws replies from people who agree and from people who don't, and both groups read the thread. Asking what each person keeps gives them an easy reply.

TemplateHot take: [N] people in [niche] will clone [type of tool] this year. The part a cheap clone can't copy is [your advantage, e.g. your data or your integrations]. What's the part you'd keep?
It makes one claim about cheaper software and then asks builders what they keep.X

Best practices for X as an indie hacker

How often to post

Start with one original post a day and about an hour of replies to bigger accounts in your niche. Batch the week's posts into one afternoon and schedule them. Cap reply time so the product still gets your best hours. After two weeks, drop the formats that got no replies and do more of the rest.

Tools that help

  • Typefully: Writes and schedules threads and long posts in one place. Free X accounts are limited to 280 characters per post, so the 25,000-character posts on this page need a Premium account.
  • Shotmesh: Covers customer names, emails, card numbers and revenue you did not mean to share before you post a dashboard image. Check the exported file, not the editor preview, because a preview can look clean when the file is not.
  • Sycamore: Adds word-synced captions to vertical videos, which matters for screen recordings and roasts because the feed plays them without sound.

Do

  • Check every revenue screenshot for customer names, emails and card details, and cover them with a solid bar, not a blur.
  • Film dashboard videos on a sample account or a test user, so no real customer shows up in a menu or a tooltip.
  • Ask a customer before you show their name, invoice or feedback. If they say no, quote them without the company name.
  • Put one reason next to each number, such as why MRR and revenue differ this month.
  • Reply to bigger accounts in your niche with a specific answer before you post your own update.

Don't

  • Don't post an invoice or Stripe screenshot without checking the exported file for tax IDs, addresses and emails.
  • Don't put MRR and revenue in one number without a line that says which is which.
  • Don't post a roast or a teardown of someone else's page without the founder's yes.
  • Don't run automated replies. A script that answers every post gets ignored, and the replies that bring readers are the ones you wrote yourself.
  • Don't post a launch and then go quiet for weeks. Use the day after the launch to post the numbers.

More content ideas

More X ideas: Newsletter Writers, Crypto Projects, Freelance Marketers, Game Developers

Edit your videos to go viral