DealInSec Open App

Cold Email Templates for Web developers

Three short first emails for web development, a follow-up that adds something new, subject lines, and the public signs that a business may need you. Free to copy, no sign-up.

Free to copy3 emails + a follow-upWorks in any country

Web development is harder to sell by cold email than design, because the problems stay invisible to most owners until something breaks. A founder rarely knows their WordPress plugins are years behind or that the checkout throws an error on Safari. That gives you an opening, as long as you translate the technical finding into a result they can see: lost orders, a form that silently drops enquiries, a browser warning that the site isn't secure. Lead with one finding, explain what it means in a sentence, and offer to show them. Skip the stack talk and the list of languages you know. Developers who win work this way usually write to businesses that already sell or take bookings online, since that is where a bug has a cost.

Who buys web development

Online shops on WooCommerce or Shopify

Checkout bugs, slow product pages and app conflicts cost them orders directly, so they budget for fixes.

SaaS startups after a seed round

They often need a contractor to ship features faster than a small team can hire.

Design agencies that don't write code

Many need a dependable developer to build what their designers mock up, and they send repeat work.

Membership sites and online course businesses

Login, payment and content-access plugins break in ways that lock out paying members.

Businesses with custom booking or quote forms

Hand-built forms tend to break quietly after a hosting or plugin update, and enquiries vanish.

Signs a business may need web development

Each one is public and takes about a minute to check. Mention the one you actually found; it is what makes the email worth answering.

The browser shows a 'not secure' warning or mixed content

Load the site in Chrome, look at the padlock, then open the console and look for mixed-content warnings.

The checkout or contact form throws an error

Add an item to the basket, or fill the form, up to the final step without submitting, and watch for errors.

The CMS or plugins are visibly out of date

View the page source and search for 'ver=' or the generator tag, or run the site through Wappalyzer or BuiltWith.

Product or service pages are slow on mobile

Run PageSpeed Insights on an inner page, not just the homepage, and note the slowest element.

They're advertising for a developer

Check their careers page, LinkedIn jobs or startup job boards for a front-end or full-stack role that's been open for weeks.

Three first emails for web development

Replace everything in {curly brackets}. Send each one by hand, to one person, about one thing you noticed.

1. The bug you found

You hit a real error on their site and can describe exactly where it happens.

Subject: an error on your checkout page

Hi {First name}, I was browsing {Company}'s shop, and when I added {the product} to the basket on Safari, the checkout page {what happened}. I didn't place an order, but I'd guess some customers hit the same wall. I'm a web developer and I fix WooCommerce and Shopify problems like this one. I can write up the steps to reproduce it, so whoever looks after your site can check. Want me to send those steps? If you already know about it, there's no need to reply. {Your name}
2. The free outside-only tech check

Their site looks neglected under the surface and you can explain three issues plainly.

Subject: three things from a quick tech check

Hi {First name}, I build and maintain websites for small online businesses. I ran a quick, outside-only look at {Company}'s site, nothing that touches your server, and found three things worth knowing about, including {the most important finding}. I've written them up in plain English, with how urgent each one is. It's half a page and yours to keep, whether we ever work together or not. Should I send it to you or to whoever manages the site? If this isn't useful right now, just say and I'll drop it. {Your name}
3. The funding round and the open role

They raised money or launched, and a developer job has been open for a while.

Subject: contract dev while you hire?

Hi {First name}, I saw {Company} announced {their funding or launch} recently. Congratulations. Your careers page lists a senior front-end role, and those often take a while to fill. I'm a contract developer working in {their stack}, and I usually help teams in that gap: a defined feature or a backlog of fixes, handed over cleanly when the hire starts. Would a short-term contractor help while you recruit? If you'd rather wait for the permanent hire, that makes sense and I won't chase. {Your name}

The follow-up

Send it once, four to seven days later, and only if it adds something. If there's still no reply, stop.

Follow-up

Subject: re: the checkout error

Hi {First name}, A quick addition to my note last week: I checked again today and {what you found on the second check}. I've put the steps below in case they help whoever handles your site. {the steps} No reply needed. I won't email about this again. {Your name}

Subject lines

  • an error on your checkout page
  • {Company} checkout on safari
  • three things from a quick tech check
  • contract dev while you hire?
  • your site's security warning
  • the contact form on {Company}
  • plugin updates on your shop

Mistakes to avoid

  • Leading with your stack. 'React, Node, Laravel' means nothing to a shop owner. Lead with the order they might be losing.
  • Running scans that hammer their server or poke at login pages. Stick to what any visitor can see, or you'll look like an attacker.
  • Describing a bug vaguely. 'Your site has issues' gets ignored; 'checkout fails on Safari at the delivery step' gets forwarded to the person who can say yes.
  • Pitching a rebuild when they need a fix. A small paid fix is often how you become someone's developer for years.
Find businesses that show these signs

Describe the clients you want and where. DealInSec's Client Radar researches real companies that fit, checks each one's own website, shows what it found with sources, and drafts a first email for you to read, edit and send yourself. Free plan, no card.

Find web development clients free →

Cold emails for web development: questions

Is it okay to test someone's site before emailing them?

Browsing as a normal visitor is fine: loading pages, adding to a basket, reading the page source, using public lookup tools. Don't submit forms with fake data, try passwords, or point aggressive security scanners at a site you don't own. Apart from being rude, it can break computer misuse laws in plenty of countries. If a finding needs deeper testing, ask permission first.

Who should I email at a small online business?

At a shop with fewer than ten people, the founder usually decides on website spend, even if someone else uploads the products. At a funded startup, it's the CTO or head of engineering, and the founder only if there's no technical lead. Check the team page and LinkedIn. Avoid generic info@ addresses for technical findings; they rarely reach someone who understands them.

Should I include my GitHub or portfolio link?

One link at most, and only to something close to their problem: a shop you fixed, a booking system you built. A GitHub profile means little to a non-technical owner, so save it for the technical lead at a startup. Too many links in a first cold email can also make it look like bulk mail to spam filters.

Find clients. Win deals. Get paid.

For freelancers, consultants and small agencies, wherever you bill from: find clients with Client Radar and two AI helpers (Nibo and Mika), then a quotation, an agreement signed online, the invoice and payment follow-up for each client, in your own currency, free on every plan with no monthly cap. No card, in every country. Paid plans (from ₹299/month, bought in India) add more AI client research and drafts.

Get started free →