Cold email works for freelance developers when each message is about one specific problem you found in the recipient's product, written in a few sentences, with a small and easy next step. Pick a narrow group of businesses, spend fifteen minutes researching each one, send ten good emails a week, and follow up once. What fails is the template sent to five hundred people, because everyone can tell.
The difference between outreach and spam is not the volume. It is whether the email could have been sent to anyone else. If it could, it is spam, even if you sent it to one person.
Choose who to email before what to say
The email gets easier once you know who it is for. A narrow group gives you three advantages: you understand their problems, you can reuse your research, and your one relevant project matches all of them.
Good groups are specific enough that you can list twenty of them in an hour:
- Independent gyms with a booking app that has bad reviews
- Shopify stores in one niche whose site is slow on mobile
- Small SaaS companies whose changelog has not moved in six months
- Local service businesses still taking bookings by phone
Bad groups are "startups" and "small businesses". You cannot research them, and you cannot say anything specific to them.
Fifteen minutes of research per email
For each business, before you write a word:
- Use the product. Sign up, book something, go through checkout on your phone.
- Note one real problem. Something slow, broken, confusing or missing. Be precise: which page, which step, what happened.
- Check it is worth fixing. A problem in the checkout matters. A slightly odd font on the About page does not.
- Find the right person. Founder or owner at a small company. Head of product or engineering at a bigger one. A named person beats "info@".
If you cannot find a real problem in fifteen minutes, skip that business. Writing to them anyway is how outreach turns into spam.
Template one: the observation
Use this when you found a concrete problem.
Subject: Your booking page on mobile
Hi Sara, I tried booking a class on your site from my phone this morning and the time picker goes off the edge of the screen after the second step, so I could not get past it. On a desktop it works fine. That is probably costing you some mobile bookings.
I build booking and payment flows for small businesses, most recently this one: [link]. If it is useful, I can send a short note on what is causing it. No charge for that part.
Muhammet
Short, specific, useful even if they never reply. The offer is small: a note, not a project. That is the easiest thing in the world to say yes to.
Template two: the relevant build
Use this when you have shipped something very close to what they need.
Subject: Stripe subscriptions for [their product]
Hi Tom, I noticed [their product] still takes annual payments by invoice. I recently added Stripe subscriptions, proration and a self-serve billing page to a similar product: [link]. It took about two weeks.
If moving billing online is on your list for this year, I would be happy to send a rough plan and a fixed price. If not, no worries at all.
The proof is the link, and the specific detail (proration, self-serve billing page) shows you understand the work rather than the buzzword.
Template three: the follow-up
Send one follow-up after about a week if you hear nothing. Then stop.
Hi Sara, just bringing this back to the top of your inbox in case it got buried. Happy to send that note on the mobile booking issue if it is useful. If not, I will leave it there.
People are busy, and plenty of replies come from the follow-up. A second or third follow-up does not add much and starts to cost you the reputation you are building.
Subject lines and what to cut
Subject lines should be plain and specific to them: "Your booking page on mobile", "Checkout on [product]", "Question about [feature]". Avoid anything that sounds like marketing, because that is how it gets filtered.
Cut these from the body:
- Your introduction. "My name is X and I am a full-stack developer with Y years of experience" goes last, if anywhere.
- The list of technologies. They care about the problem, not your stack.
- Big claims. "I can double your conversions" is not something you know.
- Attachments. A link to a live project is better and does not trigger spam filters.
- A call booking link in the first email. You are asking for half an hour from a stranger. Ask for a reply instead.
A realistic weekly routine
| Day | What you do | Time |
|---|---|---|
| Monday | Build a list of 10 businesses in your group | 1 hour |
| Tuesday | Research and write 5 emails | 1.5 hours |
| Wednesday | Research and write 5 emails | 1.5 hours |
| Following week | One follow-up to anyone who has not replied | 20 minutes |
Ten researched emails a week is not much volume, and that is fine. It is enough to learn which group responds, which problems people care about, and which template works for you, without sliding into templates nobody reads.
Track every email in a simple sheet: business, date, problem noted, reply, outcome. After a month you will know far more about your market than any course could tell you.
Make sure there is something to click
Every reply starts the same way: the person opens your link and then looks you up. If what they find is a bare GitHub profile or nothing at all, the conversation often ends there.
Before you send the first email, make sure you have one page with your shipped work on it. Developer portfolio website: what to put on it covers what that page needs. And cold email is one channel among several: where freelance developers actually find clients shows how it fits with referrals and communities, which tend to work best in combination.