A warm introduction is a short, personal note from a happy early customer to someone they already know who has the same job. Ask early customers after a clear win, make it easy to forward, prepare a two-sentence blurb plus one link, track every ask in a simple sheet, and keep the cadence to one or two asks per week so you do not burn trust. This is peer-to-peer distribution, not a referral link program and not cold outreach.
When do warm introductions beat another launch board?
Warm introductions work when you already have a handful of people who got a real result, and when your buyers listen to peers more than to a directory listing. They fail when nobody has a clear win yet, when your buyers sit behind enterprise procurement, or when the product still breaks every week.
Think of this as borrowing trust, not buying traffic. One careful intro from a customer who already got value can open a conversation that a cold DM or another launch listing rarely will. The cost is reputation, so treat every ask like it might be the last one that customer is willing to make.
Choose warm customer introductions when:
You have at least three people who finished a real job in the product and would say so without a script.
Your ICP is reachable through their network (other founders, other ops leads, other agency owners), not only through paid ads or a giant enterprise RFP.
You can follow up the same day if someone introduces you. An unanswered intro is worse than no intro.
Skip or pause when:
Nobody has a clear win yet. Asking for intros before the product works turns customers into unpaid salespeople for a broken demo.
Buyers need procurement, security review, and a six-month cycle. A peer email will not shortcut that. Use it later for a champion inside an account, not as your main top-of-funnel.
The product still fails weekly. Fix reliability first. An intro that lands on an outage teaches the new person to ghost you.
If you are still hunting your first few paid users, start with direct outreach and onboarding, not intros. Aura++ covers how to get your first 10 paying customers without a launch day. Warm intros sit after that stage: you already have early customers who trust you.
What is a warm intro vs a referral link vs an affiliate ask?
Keep the three paths separate in your head and in your customer emails.
Path | Who does the work | What the recipient sees | Best when |
|---|---|---|---|
Warm introduction | Your customer writes a short personal note to one named peer | A trusted person saying "I use X for Y; wanting to intro you to the founder" | You have 5-40 happy users and a narrow ICP |
Referral link | Your customer shares a link (often with a reward) to anyone | A link or code; the relationship may be thin | You want volume and already have a simple loop |
Affiliate | A partner promotes you for commission | Content, coupons, or tracked links from someone who may not be a user | Retention and economics support partner payouts |
A referral loop with triggers, pasteable asks, and a sheet is a different playbook. MakerHunt covers how to build a simple referral loop under 100 users. This post is only about asking one happy customer to introduce you to one peer. Do not mix a cash affiliate pitch into a warm-intro email.
Who should you ask first?
Ask people who already showed goodwill and results. Avoid silent free users and anyone still stuck.
Good first asks: customers who replied to you, renewed, expanded seats, finished the core job more than once, or said something like "this saved me X hours."
Second tier: active free users who talk to you, ship work in the product, and match your ICP. Still ask after a win, not after signup.
Skip for now: people who never activated, people with open bugs that block them, anyone in a billing fight, and anyone who only signed up for a free credit.
Write a short list of five to ten names. Next to each name, note the win you can point at and one peer type they might know ("other weekly content ops leads", "other agency PMs"). Specific peer types beat "anyone who might like this."
The running example (made-up)
Peerwick is an illustrative, made-up product, and every number about it below is made up too. Treat names and numbers as fiction.
The setup: a solo founder builds Peerwick, a tool that turns weekly content briefs into a shared calendar with approvals for small content teams (roughly 2-8 people). There are 14 paying customers and about 25 free users who still open the app. Three paying customers already said the weekly approval flow cut their Slack chase time. The founder wants warm introductions to more content ops leads, not another generic launch-board blast.
When should you ask for the intro?
Timing matters as much as the wording.
After a clear win (first successful job, first weekly cycle that ran clean, first renewal). Point at that win in one sentence.
Not at signup. New users do not know if you are worth their reputation.
Not during an outage, a data scare, or a billing fight. Wait until the relationship is calm again.
Not in a group channel blast. One-to-one email or DM is the default.
For Peerwick (made-up), the founder waits until a customer finishes two clean weekly cycles, then asks within a day of a thank-you reply.
How do you write the ask?
Keep your note short. Make the "no" easy. Ask for one peer type, not a broadcast.
You to customer (requesting the intro) - illustrative Peerwick ask:
Subject: quick intro ask (easy no)
Hi Maya,
Glad the weekly approval flow finally cut the Slack chase for your team.
Would you be open to introducing me to one other person who runs weekly content ops (another in-house lead or agency PM)? I can send a two-sentence blurb you can paste, plus a link. Totally fine if now is a bad time or you do not have anyone in mind.
Thanks either way,
Alex
Treat Maya, Alex, and the numbers as fiction.
Rules for the ask:
One peer type. "Someone else who runs weekly content ops" beats "anyone who might like Peerwick."
Offer an easy no. People say yes more often when declining is safe.
Do the work for them. Promise the pasteable blurb in the same thread.
Do not attach a reward in the first ask at this size. Skip paid intro bounties until trust and product proof are boringly solid.
What should you prepare for the customer?
Send three pieces they can forward without rewriting your whole pitch.
A 2-3 sentence blurb in their voice, not yours. Fact first: what they use it for, one result, one honest limitation.
One link (homepage or a short Loom). Not five links.
One limitation line so they do not oversell ("works best for teams under ~10; not a full DAM yet").
Forwardable blurb (illustrative Peerwick, fiction): "I use Peerwick to turn our weekly content briefs into a shared calendar with approvals. It cut the Slack chase for our 5-person content team. Limitation: it is built for small teams, not a full asset library. Happy to intro you to Alex (founder) if useful."
Also prepare your own calendar: if they introduce you today, you reply within a few hours. Keep a short "who I help" line ready so you do not invent a new pitch under pressure. If you need a proof point later, a thin case note with one buyer is enough; IndieHunt's guide on how to write a customer case study when you only have three buyers is the companion for that, not a substitute for the intro itself.
What do you do after the intro lands?
The introducer lent you their reputation. Protect it.
Reply within a few hours (same business day). Thank them, restate the job you help with in one sentence, and propose one soft next step (15-minute call or a short async Loom), not a pitch dump.
Thank the introducer privately in a separate note. Do not BCC the whole chain forever.
Run a short discovery if they agree to talk: their current workflow, what they already tried, what "good" looks like. Keep demos short. If the chat turns into a sales call, stay disciplined; save the full demo playbook for later.
One soft next step. Trial, second call, or "not now" with permission to check back. Do not add them to a drip without consent.
How do you track warm intro asks?
A simple sheet beats memory. Columns: who you asked, who they introduced, who was introduced, date asked, date intro sent, outcome (replied / call / trial / paid / no), notes.
Asked | Introducer | Introduced | Date | Outcome | Notes |
|---|---|---|---|---|---|
Maya (paying) | Maya | Jordan (agency PM) | 2026-10-06 | call | fiction row: 15-min call booked |
Sam (paying) | Sam | Riley (in-house content lead) | 2026-10-08 | replied | fiction row: wants async Loom first |
Priya (paying) | - | - | 2026-10-09 | no | fiction row: no peer in mind; stop asking |
Those three rows are made up for Peerwick. Copy the columns; do not copy the names as real data.
Review the sheet weekly. If "no" or silence repeats for the same customer, stop asking them.
What cadence keeps trust intact?
One to two asks per week max across your whole customer base early on. Quality over volume.
One ask per customer until they volunteer another name or you have a new, separate win to point at months later.
Stop asking a customer after a clear no, after two unanswered asks, or if their tone cools. Their goodwill is finite.
Warm introductions are a trust spend. Spend slowly. If two asks in a week both convert into calls, pause new asks and work the pipeline. Filling the calendar with intros you cannot follow up on is how the channel dies.
What traps burn the channel?
Mass "please share" blasts to your whole list. That is not a warm intro.
LinkedIn connection-request spam that name-drops a customer without their OK.
Paid intro bounties too early. Skip cash for intros at this size; it can feel like buying their reputation before the product has earned it.
Asking unhappy or stuck users. They will either refuse or introduce you poorly.
Pitching the introducer's whole company Slack. Ask for one peer, not a channel dump.
Slow replies after the intro. Ghosting the new person makes your customer look bad.
Turning every intro into a feature dump. Lead with their job and one next step. Save the full tour for people who asked for it.
A 14-day plan to run your first warm intro sprint
Day | Focus | Done when |
|---|---|---|
1 | List happy customers | 5-10 names with a clear win and peer type noted |
2 | Write the ask + blurb | Short ask email and 2-3 sentence forwardable blurb drafted |
3 | Build the tracker | Sheet with columns for ask, intro, outcome |
4 | Pick first two asks | Calendared; not during an outage or billing issue |
5 | Send ask #1 | Personal note out; easy no included |
6 | Send ask #2 | Second note out; same standard |
7 | Follow up gently if needed | One bump max after 3-4 days; then stop |
8-9 | Deliver blurbs for yeses | Blurb + one link sent same day as yes |
10-11 | Reply to new intros fast | Same-day thank-you + soft next step |
12 | Thank introducers privately | Separate note; no endless BCC chain |
13 | Update the sheet | Outcomes logged; stop list updated |
14 | Review | Decide next week's 1-2 asks or pause |
Sample warm intro email the customer can send (illustrative)
Below is a made-up Peerwick forward. Treat names as fiction.
Subject: intro: Alex <> Jordan (weekly content ops)
"Jordan - meeting Alex, founder of Peerwick. I use it to turn weekly content briefs into a shared calendar with approvals; it cut Slack chase for our small team. Limitation: best for teams under ~10, not a full DAM. Thought of you because you run weekly content ops at the agency. No pressure either way. Alex is on this thread."
Your reply on that thread (same day): thank both, one sentence on the job you help with, one soft next step, then move to a smaller thread if they want a call.
FAQ
What if they say no?
Thank them and stop. A clear no is a gift. Do not re-ask next week with a new angle. Put them on a "do not ask" note in your sheet. You can still serve them as a customer; intros are optional.
Is this the same as referrals?
No. A referral link is a shareable path, often with a reward, aimed at anyone. A warm introduction is a personal note to one peer. You can run both later, but do not collapse them into one email. Use the MakerHunt referral-loop guide when you want the link-based system.
How many intros before it feels weird?
If you are asking the same person repeatedly, it already feels weird. One thoughtful ask after a win is normal. A second ask months later after a new win can be fine. Weekly asks to the same customer are not.
Should I offer a discount for intros?
At 5-40 customers, usually no. Discounts and cash bounties can make the ask feel transactional and can pressure people to introduce you before they are ready. Make the ask easy and reputation-safe instead. Revisit incentives only when the product proof and retention are boringly strong.
Pick five happy customers this week, write one forwardable blurb, and ask customers for intros with two careful notes. When you want early-stage founders who care about new AI and SaaS tools to find you, launch your early-stage product on EarlyHunt.