# X for Indie Hackers: A Playbook for Growing on X in 2026

Source: https://trygrowx.app/x-for/indie-hackers (updated 2026-11-10)

Indie hackers grow on X by sharing the real numbers and decisions behind a small product, replying to other makers and to the people who have the problem they solve, and turning those conversations into their first customers. One honest post a day plus fifteen minutes of replies is enough to start. The audience you build becomes your launch list, your beta testers and, often, your best source of ideas for the next product.

## Why X suits indie hackers

Solo makers have no marketing budget and very little time. X rewards the two things they have plenty of: progress worth reporting and opinions earned by shipping. The maker community on X follows journeys, so a product with 14 customers is a story worth following, and the people cheering you on are often the same people who buy, share and give feedback.

The trap is that it is easy to build an audience made only of other indie hackers. They are great for support and feedback, and most of them will never buy a tool for dentists. The playbook below balances both groups: makers for momentum, buyers for revenue.

## What to post: five content pillars

| Pillar                    | What it looks like                                                                           | Why it works for indie hackers                                               |
| ------------------------- | -------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------- |
| **The scoreboard**        | MRR, signups, churn, traffic, with the time period and starting point                        | Makers follow along for the numbers, and honest small figures are relatable  |
| **Decisions and pricing** | Why you raised prices, killed a feature, picked a stack or said no to a big customer         | Other founders face the same calls and reply with their own experience       |
| **Distribution notes**    | What happened when you posted on a directory, ran a cold email test or wrote an SEO article  | Everyone is stuck on distribution, so tested channels get saved and shared   |
| **Ship log**              | A screenshot or short clip of what you shipped this week, and the customer request behind it | Shows momentum and gives potential buyers a reason to try the product        |
| **The buyer's problem**   | Posts written for your customers about the problem your product solves, in their language    | Keeps your audience from being only makers, and attracts people who will pay |

Aim for roughly half your posts in the first four pillars and half in the last one once you have a product people can use. Before that, lean on the scoreboard and decisions, since that is the story people follow. The [build in public glossary entry](https://trygrowx.app/glossary/build-in-public) covers what to share and what to keep private.

## A realistic weekly rhythm

Most indie hackers also have a job, clients or a family, so the rhythm has to survive a busy week.

- **Every weekday: one post.** Rotate the pillars. Monday ship log, Tuesday a distribution note, Wednesday a buyer's problem post, Thursday a decision, Friday the weekly scoreboard.
- **Every weekday: five to ten replies.** Split them between makers at a similar stage and people in your customer's world. Fifteen minutes is enough.
- **Once a week: one longer piece.** A thread or a long post on a lesson that cost you something: a failed launch, a refund wave, a pricing experiment.
- **Once a month: a monthly update.** Revenue, what shipped, what failed, what is next. Our [build in public update template](https://trygrowx.app/templates/build-in-public-update) gives you a repeatable shape.
- **Weekends: optional.** In our experience a light weekend post about a side project or a reflection does fine, and skipping it costs little.

Consistency over months matters far more than volume in any one week. Read [how to grow on X](https://trygrowx.app/blog/how-to-grow-on-x/) for the wider routine.

## Hooks that work for indie hackers

Indie audiences respond to specific numbers, honest mistakes and decisions with a reason attached. Here are six hooks we wrote for this niche:

1. Day [number] of building [product]: [number] paying customers, $[amount] MRR. Here is what moved the needle.
2. I raised my price from $[old] to $[new]. Churn did [what happened].
3. I spent [number] weekends building [feature] nobody used. The signal I ignored:
4. [Number] launches, [number] flops, [number] products still making money. What the winners had in common:
5. Every distribution channel I tried for [product], ranked by customers per hour spent:
6. Should I [option A] or [option B] for [product]? Here is my reasoning so far.

The first and fourth come from our [numbers hooks](https://trygrowx.app/hooks/numbers), the second and fifth suit [before and after hooks](https://trygrowx.app/hooks/before-after) and [list hooks](https://trygrowx.app/hooks/list), the third is a [mistake hook](https://trygrowx.app/hooks/mistake) and the last is a [question hook](https://trygrowx.app/hooks/question) that invites replies.

## Example posts

A weekly scoreboard post, using the [milestone template](https://trygrowx.app/templates/milestone):

```text
Week 23 of building a booking tool for dog groomers.

MRR: $612 (up $87)
Customers: 31 (3 new, 1 churned)
Shipped: SMS reminders, the most requested feature

The churned customer left because they closed their salon.
The 3 new ones all came from one groomer recommending us in a Facebook group.

Next week: asking every happy customer for an intro.
```

A lesson post, using the [lessons learned template](https://trygrowx.app/templates/lessons-learned):

```text
I launched my second product to zero signups.

What went wrong:
1. I built it in 6 weeks without talking to a single buyer
2. I described features, and buyers search for outcomes
3. I launched on a Friday evening and then went quiet

Product three starts with 10 conversations before any code.
```

A pricing decision post, using the [hot take template](https://trygrowx.app/templates/hot-take):

```text
Unpopular in maker circles: I removed my free plan.

Free users were 80% of support emails and 0% of revenue.
Paid signups went up the month after, and support went way down.

Your free plan should earn its place. Mine did not.
```

Swap in your own numbers and keep every figure true.

## How to find customers and opportunities on X

The people who will pay for a small product usually describe their problem in public before they go looking for a tool. Search for them using phrases like these, with your niche words added:

- "is there a tool that" [task]
- "anyone know an app for" [task]
- "I hate doing" [task] or "I spend hours every week on" [task]
- "alternative to" [big competitor], especially after a price rise
- "looking for recommendations" [category]

Our guide to [X advanced search](https://trygrowx.app/blog/x-advanced-search/) shows how to filter by date, replies and language so you see fresh posts only.

**Who to reply to.** Makers one or two steps ahead of you (they answer questions and their audience is your audience), makers at your stage (you grow together), and people in your customer's industry who post about their work. Leave replies that add a number, a short story or a useful link, and read [how to grow on X with replies](https://trygrowx.app/blog/how-to-grow-on-x-with-replies/) for the method. [Replies](https://trygrowx.app/features/replies) can draft three options in your voice when you are short on time.

**DM etiquette.** Message only people who asked publicly for something you make. Reference their post, answer their question first and offer the product as one option, with no link in the opening message unless they asked for one. One follow-up at most. [Leads](https://trygrowx.app/features/leads) finds those public requests on a schedule and drafts the first message, which you edit and send yourself. Keep within [X's DM limits](https://trygrowx.app/x-specs/dm-limits) and its [automation rules](https://help.x.com/en/rules-and-policies/x-automation): every message should be one you would happily send by hand.

## Common mistakes indie hackers make on X

1. **Writing only for other makers.** A big maker audience can feel like progress while revenue stays flat. Keep the buyer's problem pillar going.
2. **Vanity numbers.** Sharing followers and page views, and leaving out revenue and churn. Readers trust the full picture, small numbers included.
3. **Going quiet after a launch.** Launch day is the start of the story. The weeks after, when you learn why people do or do not stay, are the most useful posts you will write.
4. **Link in every post.** Constant self-promotion trains followers to scroll past. Share the link when someone asks, in replies and in your pinned post.
5. **Copying growth tactics.** Engagement pods, follow-for-follow and bought followers fill your account with people who will never buy. Grow with posts and replies you would be proud of.

## Set up your profile

Your bio should say what you build, who it is for and how it is going. See [indie hacker bio examples](https://trygrowx.app/bios/indie-hacker) and, if you are building a subscription product, [SaaS founder bios](https://trygrowx.app/bios/saas-founder). Draft a few versions with the free [bio generator](https://trygrowx.app/tools/bio-generator), and pin your best scoreboard or launch post so new visitors see the story at a glance. The [X profile limits](https://trygrowx.app/x-specs/profile-limits) page lists the character counts.

## Tools for the routine

Turn today's progress into a post with the free [post generator](https://trygrowx.app/tools/post-generator), test openers in the [hook generator](https://trygrowx.app/tools/hook-generator) and check a draft before you post with the [post checker](https://trygrowx.app/tools/post-checker). For replies under a maker's launch post, try the [reply generator](https://trygrowx.app/tools/reply-generator). If you also want to grow as a developer, see the [developers playbook](https://trygrowx.app/x-for/developers).

## Frequently asked questions

### Should indie hackers share revenue on X?

Share what you are comfortable with. Exact MRR draws the most interest, and ranges or growth rates work well too. Keep customer names private unless they agree, and decide in advance what you will do if numbers fall, since sharing a dip honestly tends to earn trust.

### How do I grow on X with zero followers?

Start with replies. Under posts from makers slightly ahead of you, a thoughtful reply is seen by their audience, which is the fastest way to be noticed early. Post once a day alongside, so people who click through find a reason to follow.

### Is building in public bad if competitors are watching?

In our experience copycats rarely outwork a maker who talks to customers every day. Share outcomes, decisions and lessons, and keep the specific details of your best acquisition channel to yourself if it is easy to copy.

### How many products should I talk about at once?

One main product at a time works best, so followers know what you stand for. Mention side projects occasionally as experiments, and keep your bio and pinned post focused on the one that pays.

### Can I find paying customers on X for a niche B2B tool?

Yes, if your buyers are on X. Search for their problem in their words, reply helpfully, and message only people who asked. If your buyers are not on X, use it for the maker audience and distribution lessons, and find buyers where they already gather.