SCRIPTS FOR COMMERCIAL COURAGE
Five outreach scripts for indie hackers who hate outreach
Good outreach is not aggressive. It is specific, relevant, and easy to answer. Use these scripts as structures, then replace every bracket with a real observation.
1. The permission-based demo
Use this when you can identify a strong fit but do not yet know whether the problem is urgent. The message earns permission for a small demonstration instead of forcing a link and feature list into the first contact.
Hey [name] — saw [specific trigger]. I’m working on [product] for [buyer type] who need to [outcome] without [current pain]. I recorded a 60-second example using a situation like yours. Worth sending?
2. The blunt first-impression request
Use this when the product is live and you need clarity evidence. Make the test small, tell the person what kind of feedback is useful, and remove the pressure to be polite.
I built [product] for [buyer]. Could you look at the homepage for 30 seconds and tell me: what do you think it does, who is it for, and where do you hesitate? “I don’t get it” is more useful than encouragement. [link]
3. The problem interview without theater
Do not ask people what features they want. Ask about the last real occurrence of the problem, the workaround, the cost, and what triggered action. Past behavior is more useful than hypothetical enthusiasm.
I’m researching how [buyer] handle [specific job]. When did this last happen for you? What did you do instead, and what was annoying or expensive about that workaround? I’m not asking you to design the product.
4. The paid pilot ask
Use this when a prospect clearly has the problem and you can deliver the outcome manually if necessary. A paid pilot tests urgency and willingness to commit better than another round of compliments.
Based on what you said about [problem], I can help you reach [specific outcome] over [short period]. I’ll handle [scope], and we’ll measure [success signal]. The pilot is [price]. If it does not sound urgent enough to pay for now, that is useful for me to know.
5. The useful follow-up
A follow-up should add relevance, reduce friction, or acknowledge timing. Do not send “just bumping this.” Set an expected response date before you send, then use one or two useful follow-ups before closing the loop.
Following up because [new relevant observation / concise clarification]. The smallest useful next step is [answer one question / watch 60 seconds / try one workflow]. If this is not a priority right now, reply “later” and I’ll close the loop.
How to send without becoming spammy
Set a small daily target and inspect the replies before increasing volume. Eight thoughtful messages teach more than two hundred generic ones. Stop when the segment is wrong, the relevance is weak, or the channel rules prohibit solicitation.
- Use a real reason for contacting this person.
- Make one claim and one ask.
- Never fabricate familiarity or results.
- Respect opt-outs and community rules.
- Save exact objections; they are product and copy inputs.
Adapt the structure to the channel
Email can carry a concise observation and permission-based next step. LinkedIn needs the same relevance with less setup. Reddit and communities require the useful answer before any product mention. X or short social messages work best when the visible trigger is recent and the ask is tiny.
Do not paste the same message everywhere. Keep the buyer, problem, and ask stable while adapting the social context and local rules.
- Email → specific subject, one observation, one claim, one ask.
- LinkedIn → use the visible trigger; avoid the fake networking preamble.
- Reddit → answer publicly, disclose your connection, link only when permitted.
- X → reference the actual post or launch; do not force a demo into the first reply.
- Slack or Discord → contribute inside the community norm before requesting attention.
Rewrite the message that sounds personalized but is not
Weak: “Love what you’re building. We help innovative founders unlock growth with AI. Want to jump on a call?” The compliment is unverifiable, the buyer is generic, the outcome is abstract, and the ask is expensive.
Better: “Saw you launched the client portal last week and are still collecting revision notes by email. I built a small approval log for web agencies that need one decision trail without moving clients into project software. I can send a 45-second example using a mock website revision—worth it?” The relevance can be checked, the problem is concrete, and the recipient can answer with one word.
Use a bounded follow-up cadence
Set the expected response window before sending. Follow up once with new relevance or a smaller next step, and optionally once more to close the loop. Do not turn silence into an automated sequence that continues after the person has declined or the channel discourages solicitation.
FOLLOW-UP PLAN Initial message: [date] Reason this person qualifies: [trigger] Expected response date: [date] Follow-up 1 adds: [example / clarification / smaller ask] Close-the-loop date: [date] Stop immediately if: [decline / opt-out / rule / poor fit]
Frequently asked questions
How personalized should cold outreach be?
Personalize for relevance, not biography. Mention the observable trigger or workflow that makes the problem plausible. A precise reason for contacting the person matters more than a paragraph proving you researched their hobbies.
How many times should I follow up?
For early founder outreach, one useful follow-up and one respectful close-the-loop message are usually enough. Channel rules, an explicit decline, or an opt-out always override the cadence.
Should I include the product link in the first message?
Only when the link is the smallest useful next step and the channel permits it. Permission to send a short example often creates a cleaner first interaction and tells you whether the problem itself earned attention.