# How to Win Indie Hackers as Paying Clients

> Indie hackers are solo founders who watch every dollar and decide alone. Here is how to find the ones worth pitching, what they will actually pay for, and how to email them without sounding like a template.

Indie hackers are tricky clients to land. They are builders, so their first instinct is to do the work themselves. They have small budgets, they hate sales calls, and many of them run their business from a laptop with no office and no listed phone number. Yet plenty of them do pay for help, and when they find someone good, they stick around and recommend that person in public.

The trick is understanding how they think before you write a single email.

## How indie hackers actually run

An indie hacker is usually one founder, sometimes two, running a small software product, a newsletter, a template shop or a micro SaaS. There is no procurement process. There is no marketing manager. The person who reads your email is the person who owns the bank account.

That sounds easy, but it cuts both ways:

- **Time is the scarce resource.** They juggle building, support, marketing and billing. Anything that saves hours without needing management gets attention.
- **Money is tracked closely.** Many share revenue publicly. They know exactly what a monthly fee does to their margin.
- **They can smell fluff.** They write landing pages and cold emails themselves. Generic copy gets deleted fast.
- **They value shipping.** A freelancer who delivers a finished thing in a week beats an agency with a long discovery phase.

## What they really buy

They rarely buy "marketing strategy" or retainers with vague outcomes. They buy specific, bounded work that they cannot do well or do not want to do:

- Landing page redesigns and conversion copy
- Demo videos, product screenshots and launch graphics
- SEO content and programmatic pages
- Design polish on an app built by a developer with no design eye
- Bookkeeping, sales tax and incorporation help once revenue gets real
- Customer support coverage or onboarding emails
- One-off dev work: integrations, migrations, performance fixes

Price it as a fixed package with a clear deliverable. "Landing page rewrite, delivered in 7 days" lands better than an hourly rate. If you do video work, the advice in [getting clients as a video editor](https://getclient.pro/blog/get-clients-for-a-video-editor) carries over well, since demo videos are a common need.

## Timing: when they are ready to spend

Indie hackers do not follow retail seasons. Their buying moments are tied to their own product cycle:

- **Right before a launch.** A planned Product Hunt launch or a major version means they suddenly need visuals, copy and a polished page.
- **Right after traction.** When revenue crosses a level where their time is worth more than the task, they start outsourcing.
- **End of year and tax season.** Bookkeeping and accounting offers fit here.
- **After a quiet stretch.** Flat growth makes founders open to someone fixing their onboarding or SEO.

So watch for signals: an "upcoming" listing, a new pricing page, a public revenue milestone. Those are better triggers than any calendar date.

## Where to find them (and where Google Maps fits)

Be honest with yourself here: many indie hackers have no Google Maps listing at all. Google Maps still helps for the ones who registered a small company with an address, and for small software studios that behave like indie hackers. Try searches like:

- "software company" or "SaaS company" in tech-heavy cities
- "app developer" and "web application developer"
- "software studio" or "digital product studio"
- "coworking space" (useful to identify hubs, then look at tenants)

Use bulk keywords across several cities at once, then filter hard. The [Google Maps scraper guide](https://getclient.pro/resources/google-maps-scraper-guide) covers how to set up those searches.

For this audience, another source usually fits better. GetClient can pull leads from **TrustMRR**, where founders show verified revenue. Revenue data is especially useful: it tells you who can afford a package before you write a word.

## What makes a good prospect

Score each lead before you add it to a campaign. A strong indie hacker prospect usually has:

| Signal | Why it matters |
|---|---|
| Real revenue, even modest | They can pay and they care about growth |
| A weak spot you can see | A dated landing page, no demo video, thin docs |
| An active product | Recent changelog or launch, so someone is home |
| A findable founder name | You can write to a person, not "hello@" |
| A fit with your offer | Your service fixes the visible weak spot |

Skip products that look abandoned and founders with obvious agency backgrounds in your exact skill. Verify emails before sending, since small domains often have dead or catch-all addresses.

## A sample cold email

Keep it short, specific and about their product. Here is a starting point for someone offering landing page rewrites:

> Subject: quick idea for {{params.name}}
>
> Hi {{params.firstname}},
>
> I spent a few minutes on {{params.website}}. The product looks solid, but the hero section explains features before it explains the problem it solves, so a first-time visitor has to work to get it.
>
> I rewrite landing pages for solo founders as a fixed package: new hero, benefits, pricing section copy, delivered in 7 days.
>
> Want me to send a rough rewrite of just the hero so you can judge it? No call needed.
>
> [Your name]

Note the offer to do the work async and the absence of a call request. Indie hackers often prefer that. Replace the observation with one you actually made about their site; a fake observation is worse than none. For more on structure, see the [cold email](https://getclient.pro/learn/cold-email) guide.

## A sensible follow-up

Two or three follow-ups over about two weeks is a reasonable rule of thumb for busy founders. Branching helps you avoid sending the same note to everyone:

- Showing beats asking.
- **Day 10:** a brief close-out: "I'll stop here. If a launch is coming up, I'm happy to help then."

If you are unsure which account type to use, read [Gmail vs SMTP for cold email](https://getclient.pro/blog/gmail-vs-smtp-for-cold-email). Every email should include an unsubscribe link, and you should check the email rules that apply where you and your prospects are.

Test one variable at a time, such as offering a free sample versus a portfolio link. The guide on how to [A/B test cold emails](https://getclient.pro/blog/ab-test-cold-emails) explains how. New accounts get 100 free credits with no card, and you can see plans on the [pricing page](https://getclient.pro/pricing).

## Frequently asked questions

### Do indie hackers respond to cold email at all?

Many do, if the email is specific to their product and asks for little. They tend to ignore generic pitches and long requests for calls. Offering a small, concrete sample of your work is often the easiest way to get a reply.

### How much should I charge indie hackers?

Price fixed packages tied to a clear result rather than open retainers. Look at their public revenue if they share it and keep your package a sensible fraction of what the work could return. Start smaller to earn trust, then offer ongoing work once they see results.

### Should I pitch on Twitter or communities instead of email?

Public communities work for building a reputation, but direct pitches there often look like spam. Email lets you be specific and private. Many freelancers use both: visible helpful posts in communities, and short personal emails to founders who fit their offer.

### What if the founder has no email on their site?

Check the product's support or contact page, their changelog, and public maker profiles. Run any address you find through email verification before sending, because small product domains often have unused or catch-all inboxes.

Source: https://getclient.pro/industries/indie-hackers