Cold Email Templates for Freelance Developers (5 Templates + Real Examples)
By Zhaosheng Lin, independent developer behind FreelanceMail
Quick answer
A freelance developer's cold email works when it opens with one technical detail you checked yourself on the prospect's site or product (a PageSpeed result, a bug you hit, two tools they sync by hand) and offers one small, concrete fix. Below: a 10-minute research checklist, 5 templates (store performance, SaaS bugs and features, startup MVPs, integrations, mobile), and three real generated emails for real companies, including one where the site couldn't be read, with what to fix before sending.
What Makes a Developer's Cold Email Different
Most cold email templates are written for marketers and agencies. A developer has an advantage they don't: you can check things. You can run a page through PageSpeed Insights, see which platform a store runs on, try the signup flow, or read the API docs. A cold email built on something you checked is hard to dismiss as spam.
So every template below has the same shape:
- One technical observation you verified yourself.
- One sentence on why it matters to their business, in plain language. The person reading may not be technical.
- One relevant past project, with a link.
- A small ask: "Want me to send the three fixes?" is easier to say yes to than "Can we book a call?"
Research Checklist: 10 Minutes Before You Write
Pick the checks that match the service you're selling. You need one solid observation, not ten.
- Speed: run the homepage and one product or pricing page through PageSpeed Insights on mobile. Note the score and the top two suggestions. Screenshot it, because results change between runs.
- Platform and tools: check the page source or a lookup tool (BuiltWith, Wappalyzer) for the platform (Shopify, WordPress, Webflow) and the apps they've installed.
- Stack: read their job postings. Engineering roles usually list languages, frameworks and infrastructure.
- The product itself: sign up for the free trial or go through checkout up to payment. Write down anything broken, slow or confusing.
- Integrations and API: look at their integrations page and API docs. What do customers keep asking for that isn't there? Their changelog, community forum or public roadmap often says.
- Health: check their status page and public GitHub issues for repeated problems.
- Basics: test the site on your phone. Look for broken links, missing alt text and forms that don't submit.
Write down where each observation came from. If they reply "where did you see that?", you want an exact answer.
Template 1: Store Performance and Theme Fixes
Best for: Shopify, WooCommerce and front-end developers pitching online stores.
Subject: [Company]'s [product page / homepage] on mobile
Hi [Name],
I ran [Company]'s [page] through PageSpeed Insights on mobile this morning and it scored [score]. The two biggest suggestions were [issue 1, e.g. very large hero images] and [issue 2, e.g. several apps loading scripts on every page].
On a store, that's the page shoppers wait on before they can add to cart. I'm a freelance [Shopify] developer and these are usually contained fixes in the theme.
Want me to send the screenshot and the two changes I'd make first?
[Your name]
[Link to a similar store you worked on]
Follow-up (3–4 days later):
Hi [Name],
One concrete example from [Company]'s site: [specific asset, e.g. the homepage banner is a [size] image served at full size on phones]. [What you'd do, e.g. serving it in a modern format at the right size for each screen] would make it much lighter.
Happy to send the full list if it's useful.
[Your name]
Before sending: only use numbers you measured, say how you measured them, and keep the screenshot. Don't promise a specific speed or sales improvement.
Template 2: SaaS Bugs and Features the Team Has No Time For
Best for: back-end and full-stack developers pitching small software companies.
Subject: [Specific feature or bug] in [Product]
Hi [Name],
I tried [Product] [this week / on the free trial] and [specific observation, e.g. the CSV export stopped at 10,000 rows, or your forum has a long thread asking for a [tool] integration].
I'm a freelance [full-stack] developer and I help small teams ship this kind of work without hiring: [type of work, e.g. new API endpoints, integrations, admin tools]. I recently [one real past project, one line].
Is this on your list, or already handled?
[Your name]
Before sending: reproduce the bug twice and note the steps, browser and date. If it's a feature request, link to the public thread where customers ask for it.
Template 3: Startup MVP or Extra Hands
Best for: full-stack developers pitching early-stage startups.
Subject: [Company]'s [open role / recent launch]
Hi [Name],
I saw [specific trigger, e.g. you're hiring a senior full-stack engineer / you just launched [feature]].
While you look for the right full-time person, I could take on [specific part of the work] as a freelancer. I work in [their stack, from the job post] and recently [one real past project, one line, with link].
Would it help if I suggested a small first piece I could ship in [realistic time]?
[Your name]
Before sending: use the stack from their job post, not your favorite stack. Founders read a lot of these, so keep it short.
Template 4: Integrations and Automation
Best for: back-end developers and automation specialists.
Subject: [Tool A] and [Tool B] at [Company]
Hi [Name],
I noticed [Company] uses [Tool A] and [Tool B] ([where you saw it, e.g. your job post for an operations coordinator mentions both]). Are you moving data between them by hand?
If so, that's the kind of integration I build. [One real example, e.g. for a [type of business], I connected [system] to [system] so [what happens automatically]].
Want me to sketch how it could work for you?
[Your name]
Follow-up:
Hi [Name],
Here's a rough sketch of a [Tool A] to [Tool B] connection for [Company]:
1. [Tool A] sends an update when [event].
2. The data is checked and reformatted.
3. [Tool B] creates or updates the record.
4. Anything that fails gets flagged to [Slack / email] so nothing is lost silently.
Happy to scope it properly if it's useful.
[Your name]
Template 5: Mobile App
Best for: React Native, Flutter, Swift and Kotlin developers.
Subject: [Company] on mobile
Hi [Name],
I use [Company]'s [web app] and [specific observation, e.g. on my phone the dashboard needs sideways scrolling and the date picker is hard to tap / you don't have an app yet, but your reviews mention wanting one].
I'm a freelance mobile developer working in [React Native / Flutter]. I recently built [real app example, with App Store or Play link].
Would a short list of what a first version could include be useful?
[Your name]
Before sending: test on a real phone and take screenshots. Keep the proposed first version small; a long mobile project is a hard first yes.
Real Examples: Unedited Emails for Real Companies
On November 12, 2026 I ran FreelanceMail on three real company websites with three developer service descriptions. The tool reads the prospect's homepage and about page plus a few signals from the page code, then writes a first email and two follow-ups. Below are the first emails, copied exactly as generated, and what I'd change before sending.
Shopify developer → deathwishcoffee.com
Service entered: "I am a freelance Shopify developer. I fix slow, buggy Shopify themes, build custom sections and set up apps so store owners can sell without fighting their site."
Subject: Are your product images fully described?
Hi there,
Death Wish Coffee's holiday lineup, from the Gingerdead blend to the Peppermint Mocha bark, sits right on your homepage. Eight of the 47 images on that page have no alt text, which leaves screen readers and search engines guessing what they show.
I'm a freelance Shopify developer. I fix slow, buggy themes, build custom sections, and set up apps so store owners can sell without fighting their site. Adding alt text and cleaning up image setup in a theme like yours is a small, contained fix.
Want me to list the images missing alt text?
The first follow-up added that the homepage HTML is about 659 KB.
Before sending: I checked the alt-text claim in a browser the same day: 8 visible images on the homepage had empty or missing alt text, so it holds. But an empty alt is correct for purely decorative images, so list which of the eight are products or banners with text before you call it a problem. The 659 KB figure is the size of the HTML file, not a speed test. If speed is your angle, run PageSpeed Insights and quote that instead. Then find the e-commerce or web lead's name.
Full-stack developer → transistor.fm
Service entered: "I am a freelance full-stack developer. I help small software companies ship features and integrations their team has no time for, like new API endpoints, Zapier-style integrations and admin tools."
Subject: Who builds integrations for a five-person team?
Hi there,
Transistor's About page says a team of five serves over 40,000 podcasts. That's a lot of product surface for a team that size.
I'm a freelance full-stack developer. I help small software companies ship the features and integrations their team has no time for, like new API endpoints, Zapier-style integrations, and admin tools.
Most small teams have a short list of these that keeps getting pushed to next sprint.
Would a 15-minute call this week be useful?
Before sending: the facts are right; the about page says "a small (but mighty) team of five people" and "over 40,000 podcasts." But team size is an observation about the company, not about a problem you can fix. Spend ten minutes in their docs, changelog or community to find one integration customers ask for, and lead with that. Replace the call with a smaller ask, like the tool's own follow-up: "Want to pick one request and scope it together?" A company this small may prefer to build things themselves, so expect a no and keep it friendly.
When the site can't be read: drybar.com
Service entered: "I am a freelance full-stack developer. I build online booking, customer portals and internal tools, and connect the tools a business already uses so staff stop copying data by hand."
Drybar's site blocked automated visits, so the tool had nothing to read and showed a notice saying so. The first email:
Subject: Is copy-paste eating your team's week?
Hi there,
How many hours a week does your team spend copying the same customer details from one system into another? With several locations, that work multiplies fast, and mistakes creep in.
I'm a freelance full-stack developer. I build online booking, customer portals, and internal tools, and I connect the software your business already uses so information moves on its own.
Would a 15-minute call this week make sense?
Before sending: don't. It's a reasonable email about nobody in particular. It doesn't mention Drybar once, and it assumes a problem you haven't seen. Go back to the research checklist, find one real detail (how their online booking works, which booking software their locations use), and paste it into the prospect details so the next draft has something real to work from.
What the three show
The useful drafts start from a real detail. The tool finds it faster than you would, but you still need to check it, decide whether it's a problem you can actually solve, and find a real name. When the site can't be read, you get a generic email, and a generic email isn't worth sending.
General Tips for Developer Outreach
- Send from your own address, ideally on your own domain, not a no-reply or bulk-mail address.
- Keep subject lines short and specific so they aren't cut off on a phone.
- No attachments in the first email. Link to an audit, a short screen recording or a portfolio page.
- Send each email individually. Small numbers of researched emails, not a bulk campaign from the same address your clients use.
- Follow up once or twice with something new, then stop. See follow-up templates.
- Keep notes on what you sent. If replies are low, the observation is usually the weak part, not the wording.
For situations these templates don't cover, such as replying to a job post or reaching back out to a past client, see freelance cold email templates by situation.
Draft the First Version From Their Website
The research is the slow part. FreelanceMail does a first pass: paste a prospect's website and describe your development service, and it reads their homepage and about page plus a few signals from the page code (platform, installed tools, missing alt text), then writes a first email and two follow-ups like the examples above. It doesn't run speed tests or try their product, so those checks are still yours. You can try one on the homepage without signing up.
Frequently asked questions
What should a freelance developer write in a cold email?
Lead with one technical detail you actually checked on their site or product, explain in one sentence why it matters to their business, mention one relevant past project with a link, and ask a small question. Skip the full résumé and the list of every language you know.
How do I find out what technology a company uses?
Look at their job postings (they usually list the stack), run the site through a technology lookup tool such as BuiltWith or the Wappalyzer browser extension, check the page source for platform clues like Shopify or WordPress, and read their integrations page, API docs and public GitHub if they have one.
Should a developer include performance numbers in a cold email?
Only numbers you measured on their site, such as a PageSpeed Insights score or a page weight, and say how you measured them. Don't quote industry statistics about conversions or promise a result you haven't delivered before. The prospect cares about their own site.
Should I attach files to a cold email?
Not in the first email. Attachments can trigger spam filters and look like a mass mailing. Link to a short audit, a Loom video or a portfolio page instead.
Write the first draft from their website
Paste a prospect's website and FreelanceMail reads their homepage and about page, then writes a first email plus two follow-ups for your service. One free try, no sign-up.
Try it on a prospect's site