You can collect 500 waitlist emails and still have $0 in the bank.
Signups feel like progress. Follower counts feel like momentum. A big launch day feels like the finish line. None of those are revenue.
If you are wondering how to get your first 10 paying customers, the answer is usually not “wait until Product Hunt.” It is a quieter loop: talk to people who already feel the pain, sell a small paid pilot, help them win fast, then ask for one intro. Launch day can amplify that later. It does not replace it.
This is for solo founders and indie hackers who want cash in the account before the applause.
Why waiting for a launch stalls revenue
Launch day is a distribution spike. It is not a business model.
When you treat launch as the moment money starts, three things go wrong:
1. You delay real conversations until the product feels “ready for strangers.”
2. You optimize for public numbers (upvotes, comments, traffic) instead of closed loops (problem → payment → win).
3. You learn objections too late — after the spike, when nobody is listening.
Founders who get to 10 paying users early learn what the product is. Founders who wait for launch often learn what the homepage copy should have said — after the traffic is gone.
You do not need a launch to sell. You need a narrow customer, a clear offer, and the willingness to do unscalable work for the first ten.
Define one narrow ICP before you send a single message
“Anyone who needs productivity software” is not an ICP. It is a reason your DMs get ignored.
Write one sentence you can use as a filter:
[Role] at [company type / stage] who [specific painful workflow] and currently [ugly workaround], and who would pay if [measurable outcome] happened in [timeframe].
Examples that are narrow enough to work:
Freelance bookkeepers who reconcile 3+ client QBO files weekly in spreadsheets and would pay for a 20-minute weekly close.
Solo SaaS founders with 50–300 MRR who publish on Indie Hackers and want a weekly content system, not a full agency.
Agency owners under 10 people who lose deals because proposals take three days.
Rules for the sentence:
One role, not three.
One painful workflow, not “growth.”
One outcome you can prove in a week.
A buyer who can pay without a committee.
If you cannot name 20 people who match it from memory or LinkedIn, the ICP is still too vague.
Build a list of 40–50 real people (help first)
You are not building a blast list. You are building a short list of humans you can actually help.
Aim for 40–50 names. That is enough for a two-week outreach sprint without feeling like spam.
Where to find them
Niche communities. Slack groups, Discords, Indie Hackers threads, small Facebook groups, Circle communities. Look for people describing the problem in their own words — not people asking “any tools for X?”
LinkedIn. Search the job title + a problem keyword. Read their recent posts. Comment usefully once before you DM.
Reddit and forum problem threads. Sort by New in relevant subs. Reply in public with a concrete tip (no link dump). If they engage, follow up privately.
Warm network. Former coworkers, customers from a past job, people who already trust you. Ask: “Who do you know that does [ICP sentence]?”
Capture fields that matter
Use a simple sheet:
Name | Where found | ICP fit (1–3) | Pain quote | Last helpful touch | Next step | Status |
|---|
Do not add people who only “might be interested someday.” Fit score 1 gets archived, not messaged.
Help first means: answer their question, share a checklist, intro them to someone useful — before you pitch. That is how outreach stops feeling gross.
Outreach that is not spam
Spam is volume without context. Good outreach is short, specific, and easy to ignore.
Structure that works
1. One line that proves you read something real about them
2. One sentence on the problem you think they have (framed as a question)
3. One small offer of help (not a 30-minute demo)
4. Easy out
Copyable templates (edit hard)
Community / comment follow-up
Saw your note about [exact pain]. We kept hitting that when [similar situation]. Curious — are you still doing [workaround], or did you find something that stuck? Happy to share the 4-step checklist we use if useful. No pitch required.
LinkedIn / cold DM
Hi [Name] — noticed you [specific detail: post, role, project]. I work with [ICP] on [outcome in timeframe]. Not sure if this is even a priority — if it is, I can send a 1-page pilot outline. If not, all good.
Warm intro request
Quick ask: do you know anyone who [ICP sentence]? I’m running a small paid pilot this month and only want people who already feel that pain. One name is enough.
What to avoid
“I’d love to hop on a quick call” as the first ask
Long product paragraphs
Fake personalization (“Loved your profile!”)
Following up three times in 48 hours
Cadence: one message, one follow-up 4–6 days later if they opened or replied partially, then stop. Silence is data.
Sell a small paid pilot instead of an endless free trial
Free trials feel safe. They also train people to never decide.
For customers 1–10, sell a paid pilot or concierge setup:
Fixed price ($49–$499 depending on your market — pick something that hurts a little but is easy to approve)
Fixed window (7 or 14 days)
One promised outcome
You do more of the setup than productized SaaS usually allows
Frame it like this:
“Instead of a free trial where you figure it out alone, we run a 7-day paid pilot. You pay $X. I set it up with you. Success = [one metric]. If we miss it, I’ll [refund / extend / credit] — your call which path feels fair.”
Why this works early:
Payment filters curiosity from seriousness
You learn onboarding friction with people who care
You can still be generous without being free forever
If someone wants free forever, thank them and offer a waitlist for a later public launch. Do not renegotiate your first ten into unpaid consulting with no end date.
When you eventually launch publicly — including through places like Aura++ daily launches — you will already know the offer that converts. That is the point of doing this early.
White-glove onboarding for customers 1–10
Your first ten customers should feel slightly spoiled. That is not a scaling bug. It is research.
In the first 48 hours
Book a 20–30 minute setup call (or async Loom + checklist if they hate calls)
Import or enter their real data yourself when possible
Remove optional settings from the path
Agree on one measurable win in 7 days
A measurable win is not “explored the dashboard.” Examples:
First report generated and shared with a client
First invoice sent
First weekly workflow completed without the spreadsheet
First teammate invited and active
Write the win in the same words they used on the sales chat. Then send a day-3 check-in:
Quick pulse — did [win] happen yet, or are we stuck on [likely blocker]? I can jump in for 15 minutes today if useful.
Your job is not to protect the product’s self-serve story. Your job is to create a screenshot of success you can point to later.
Ask for one intro after a win
Do this when they have felt the win — not on the welcome email.
Script:
Glad [win] landed. Two asks, both optional: (1) would you mind a 2-sentence quote I can share with similar [role]? (2) is there one person in your circle who has the same [pain] and might want the same pilot?
One intro beats ten cold DMs. People introduce people who made them look smart — so make the win obvious and low-drama.
If they say yes, draft the forwardable blurb for them:
“Hey — I’ve been using [product] for [outcome]. Founder is running a small paid pilot for [ICP]. Thought of you because of [reason]. Want an intro?”
Make intro-asking a habit after every win, not a desperate move when the pipeline is empty.
Metrics that matter (ignore vanity)
Track a weekly funnel that matches the work you actually do:
Stage | Definition | Weekly target (example) |
|---|---|---|
Conversations | Real back-and-forth about the problem | 10 |
Pilot offers | You sent a clear paid pilot | 5 |
Paid | Money received | 2 |
Activation | Agreed 7-day win hit | 1–2 |
Referral | Intro or quote given | 1 |
Vanity to ignore for this phase: waitlist size, Twitter impressions, “interested” emoji reactions, pageviews without a conversation.
If conversations are high and paid is zero, your offer or ICP is wrong. If paid is fine and activation is zero, onboarding is the product bug. Fix the broken stage — do not post more launch teasers.
When you do launch later, use something like the launch-day comment playbook to convert public attention. That playbook works better when you already have paying users and proof.
Weekly checklist you can copy
Monday — list hygiene
☐ Confirm ICP sentence still fits (rewrite if last week’s chats drifted)
☐ Add 10 new fit-score 2–3 names
☐ Archive fit-score 1s without guilt
Tuesday–Wednesday — outreach
☐ Send 8–10 personalized first touches
☐ Follow up on open threads from last week (max one bump)
☐ Log every pain quote verbatim
Thursday — offers
☐ Send 2–4 paid pilot outlines
☐ Price stays fixed; scope can flex slightly
☐ No new free trials for this cohort
Friday — onboarding + asks
☐ White-glove setup for anyone who paid
☐ Confirm each active pilot’s 7-day win
☐ Ask for one intro from anyone who already won
☐ Update funnel counts: conversations → pilots → paid → activation → referral
First 10 teach the product; launch amplifies what already works
Your first ten paying customers are not a vanity milestone. They are the curriculum.
They tell you which ICP was real, which outreach landed, which objections were polite stalls, and which onboarding steps people skip. Launch day is optional amplification for a machine that already turns conversations into paid wins.
If you are still waiting for a perfect homepage and a big day on the calendar, skip both for two weeks. Build the list. Send the messages. Sell the pilot. Create the win. Ask for the intro.
Ten times. Then launch — if you still want to.
