Finding your first customers on Indie Hackers

Builders in the open

Indie Hackers is where bootstrappers build in public and ask for help in the open. Founders post about what they are building, what is not working, and what they need. For a freelancer or a small agency, that openness is the opportunity. The founders who need a service are not hiding behind a hiring form. They are writing, in public, about the exact problem you solve.

The threads to look for are easy to recognise once you know the shapes. Feedback requests: a founder posts a product and asks what is wrong with it. Growth questions: how do I get users, nothing is converting, my launch flopped. Launch posts: a product goes live and the founder is suddenly facing every problem at once. Each of those is a person who may need design, copy, engineering, marketing, or operations help, and who is already talking about it in public.

Reply as a helper, not a vendor

The mistake most people make on Indie Hackers is replying like a vendor. They see a founder struggling and respond with a pitch for their services. Founders there have seen that reply a hundred times, and they ignore it. The reply that works is the helpful one: a specific observation about their product, a question that clarifies the real problem, a suggestion they can use whether or not they hire you.

That distinction matters more on Indie Hackers than almost anywhere else, because the community is built on builders helping builders. A founder who gets a genuinely useful reply remembers who gave it. A founder who gets a pitch remembers that too, and not fondly. If your reply helps, the founder will check your profile, and the conversation starts on its own. If it does not help, no pitch would have saved it. The same answer-first approach is covered in our guide to writing a manual outreach reply that does not sound like spam.

The daily habit for first customers

Finding your first customers on Indie Hackers is a daily habit, not a campaign. Spend a short block each day reading new posts from founders in your area. Reply to the ones where you can genuinely help, and skip the rest. Keep track of the threads you replied to, and check back on them. Founders often reply days later, and the freelancer who follows up on the thread is the one who gets the conversation. That is also what Avrel's community directory is for: it tracks the rooms where founders actually ask for help, so you spend your time replying instead of scrolling.

Read the rules before posting on any community, including Indie Hackers. The same answer-first discipline applies everywhere buyers ask for help, and our guide to finding freelance clients on Reddit without getting banned covers it for Reddit. Answer first, pitch never, and never send a cold pitch to someone who only asked a question.

One more honest note: your first customers from Indie Hackers will probably be small. Early-stage founders have small budgets and big problems. That is fine. Small first customers who love the work become testimonials, referrals, and repeat work, and they teach you exactly what your market needs. The founders building in public today are the companies hiring properly tomorrow.

The short version

Your first customers on Indie Hackers are already posting about their problems in public. Find the feedback requests, growth questions, and launch posts in your area, reply as a helper rather than a vendor, and follow up on the threads. Do that daily and the builders in the open become your first clients.

Start finding founders asking for help