A freelance developer gets hired when a company has a specific, costly problem and an email names it in the first line. "I build apps" names nothing. "Your booking app is rated 2.4 stars and the reviews are about login" does. The four templates below each start from a different problem a business already has: a broken app, a spreadsheet that runs a process, two tools that do not talk to each other, and a customer-facing app that is slowing a team down. Pick one, put your own facts in it, and send it to a person who can sign the invoice.
The examples follow Anil Rao, a freelance developer in Austin who builds web apps and integrations for companies with 20 to 200 employees. Everything is invented, including the names and prices. The reader on the other end is a business buyer: an operations manager, a product owner, a founder or a head of IT. Consumers are not your market here.
Who to write to, and how to find them
Operations managers and department heads feel the pain of manual work and have budget for a fix that costs less than another hire. Founders and product leads at small software companies feel the pain of a slow or broken product. Both are findable by title and company size. Two signals make the first line honest and specific. An app with a low rating and recent reviews describing the same fault is something you can see in the store listing. A job post for an "operations coordinator" whose duties are copying data between systems tells you where hours are being lost.
Keep the first batch small. Forty well-chosen people with a real observation each will teach you more than four hundred with the same line, and your own Gmail inbox can carry that comfortably. How to send from it is in how to send cold emails from Gmail.
Template one: the rescue note
Use it when you can see a live product with a visible fault. It is the most concrete of the four and works best for founders and product owners.
Subject: Login issue in the Harbor Booking app
Hi {{first_name}},
Looking at the Harbor Booking reviews on the App Store, five of the last eight mention that logging in fails after the latest update. I fix that kind of regression for a living: I would trace it, patch it and tell you what caused it, usually within a week.
Would a 15-minute call be useful? I can look at the build before we talk.
Anil Rao, Rao Software, 100 Example Street, Austin, TX 78701. If you would rather I did not write again, reply "no thanks" and I will not.
It works because the reviews are public and the fault is specific. Check the review count before you send, and change the sentence if the count is wrong. Never invent a fault.
Template two: the spreadsheet replacement
Use it for operations managers at companies where a shared spreadsheet runs scheduling, inventory or quoting.
Subject: The scheduling spreadsheet at your shop
Hi {{first_name}},
Your careers page is hiring a dispatch coordinator, and the duties include keeping the weekly schedule in a spreadsheet. I build small internal tools that replace that kind of sheet: the same fields, but with a login for each person, no overwritten cells, and a text to the technician when the job changes.
A typical build is three to five weeks. Could I show you a sample from a similar company next week?
Anil Rao, Rao Software, 100 Example Street, Austin, TX 78701. Reply "no thanks" and I will not write again.
The first line comes from a public job post, so it is true and the reader recognizes it. The offer is concrete: what it replaces, what is different and how long it takes.
Template three: the integration offer
Use it when you know the company runs two tools that should share data, such as a CRM and an invoicing program, or a store and a warehouse system.
Subject: Orders from your store into the warehouse system
Hi {{first_name}},
I noticed you sell through Shopify and ship from a third-party warehouse. If someone on your team is copying orders from one to the other, I can connect them so orders move across on their own, with a daily check that flags anything that failed. Most of these take under two weeks.
If that is not a problem for you, ignore this. If it is, I would like to hear how it works today.
Anil Rao, Rao Software, 100 Example Street, Austin, TX 78701. Reply "no thanks" and I will remove you.
The last paragraph of the email gives the reader an honest way out and an easy way in. It also asks a question that is simple to answer by reply.
Template four: the field team app
Use it for companies with people in the field, such as inspectors, installers or delivery drivers, who still use paper forms or text messages to report work.
Subject: Inspection forms on a phone
Hi {{first_name}},
Your inspectors are still filling out paper forms, from what I could see on your service page. I build phone apps for field teams: the form opens on the inspector's phone, photos attach to it, and the report is in the office before the truck leaves the site.
I priced a recent one for a similar company at $14,000 for a first version. Would a quick call to check whether that scale fits yours be useful?
Anil Rao, Rao Software, 100 Example Street, Austin, TX 78701. If you would rather not hear from me, reply "no thanks."
A price in the first email filters. Some buyers will leave, and that is saving you a call. The people who stay have a budget that matches.
Which one to send
| If you can see | Send | To |
|---|---|---|
| A live app with a repeated complaint | The rescue note | Founder or product owner |
| A job post about manual data work | The spreadsheet replacement | Operations manager |
| Two named tools in use | The integration offer | Operations or e-commerce lead |
| Paper forms or text-message reporting | The field team app | Head of operations |
For the subject line, keep it as plain as the examples. Cold email subject lines that get opened has more, and cold email call to action examples covers what to ask for at the end. If you are growing from a solo freelancer into a studio, cold email templates for software development agencies is written for that stage.
What a first batch can earn
Suppose Anil's average project is $18,000. That is an assumption, so use your own. He sends 60 emails in a week and treats the rates below as guesses to test, not facts. One email in 12 gets a reply, which is 5 replies (60 / 12). Half of the replies become a call, which is 2.5 calls. One call in 4 becomes a project, which is 0.625 projects (2.5 / 4). At $18,000 a project, a batch of 60 is worth about $11,250 (0.625 x $18,000), or $187.50 an email ($11,250 / 60). That is a reason to write each email carefully, and the first real batch will replace the guesses with numbers.
The legal basics for a US sender
Each template ends with a street address and a "no thanks" line because the FTC's CAN-SPAM compliance guide for business (ftc.gov, page dated August 2023 and edited January 2024, read 2026-11-15) asks for both: a valid physical postal address, and a clear way to opt out that you honor within 10 business days. The guide is plain that "the law makes no exception for business-to-business email," and its list also covers accurate headers, a subject line that matches the body and a clear sign that the message is an ad. If you pay someone to send for you, the guide says you cannot contract away your own responsibility. It puts the penalty at up to $53,088 for each email in violation. The rescue note carries one more risk of its own, because it states a fact about someone's product: keep a screenshot of the reviews you counted. The full US rule and other countries are in is cold email legal.
If you would rather spend the week building, Rocketship's AI salesperson can send first emails like these for you: it finds operations managers and founders by title and company size, writes from your own Gmail, follows up and answers replies. You bring the offer and take the discovery call. Plans start at $12 a month on the pricing page, each with a 7-day trial, card required.