Cold email deliverability from your own mailbox

A web designer in Sheffield sends thirty well-researched emails to local trades from the Gmail account she has used for years, the same one her invoices and personal correspondence go through. A week later, three replies, and a nagging feeling that more should have landed. She checks a spam folder test and finds half the batch never reached an inbox at all. Nothing about the emails was wrong. The mailbox sending them, and the pattern in which they went out, is what decided whether they arrived. Cold email deliverability from your own mailbox is mostly about that mailbox's reputation, not about writing a better subject line.

What actually decides where an email lands

Receiving mail servers, Gmail and Outlook chief among them, do not judge a message on its content alone. They look at whether the sending domain can prove the email genuinely came from where it claims to, and they look at the sending account's history: how long it has existed, how consistently it has sent mail, how often recipients have replied, deleted without opening, or marked it as spam. A single email with a slightly clumsy line rarely causes a problem. A mailbox that has sent nothing but cold outreach to strangers for the first time this week is a different story, because there is no history to vouch for it.

SPF and DKIM in plain terms

SPF and DKIM are two DNS records, small entries added at your domain registrar, that let a receiving server check a message is authentic. SPF lists which mail servers are allowed to send on your domain's behalf. DKIM attaches a cryptographic signature to each message that proves it was not altered in transit and genuinely came from your domain. Neither is complicated to set up if you use Google Workspace or Microsoft 365 for a custom domain, since both providers walk you through adding the records in their admin panel, and neither costs anything beyond the few minutes it takes. A domain without these records is not automatically binned, but it is treated with more suspicion, and a growing share of mail providers now expect both as a baseline rather than a nice-to-have. Without a custom domain, sending from a plain Gmail or Outlook address, these records are already handled by the provider, which is one reason a personal address behaves reasonably well for the first small batches.

Why pacing matters more than any single setting

The bigger cause of emails landing in spam is not a missing DNS record. It is volume and pattern. A mailbox that has only ever sent a handful of emails a day, then suddenly sends eighty near-identical messages within an hour, looks exactly like the pattern spam filters are built to catch, regardless of whether every SPF and DKIM check passes. The fix is unglamorous: start with a small number of sends a day, perhaps ten to twenty for a brand new domain or a mailbox that has not been used for outreach before, and increase gradually over a few weeks rather than jumping straight to full volume. Genuine personalisation helps here too, not just because it reads better to the recipient, but because dozens of near-identical emails with the same link and the same generic opening are a pattern filters recognise, while emails that each reference something specific about the recipient's own website do not.

Signals that quietly damage a mailbox's reputation

• A brand new domain with no sending history, used for outreach from day one rather than warmed up with normal business email first.
• A sudden jump in daily volume rather than a gradual ramp over several weeks.
• A high proportion of sends with no replies, no opens, and no engagement at all, which providers read as a signal the recipient did not want the email.
• Recipients actively marking messages as spam, which does more damage to a domain's reputation than being ignored.
• Sending the same link or attachment to a large batch of strangers in one sitting, a pattern that looks identical to a mail-merge spam run even when the intent behind it is not.

The email itself still has to earn the reply

Getting a message into the inbox only sets up the next problem, which is getting it read and answered. The observation-plus-offer structure that tends to work for local business outreach, naming one specific, checkable thing about the recipient's website rather than a general pitch, is covered in cold email for web designers: one observation, one offer. Deliverability gets the email to the door. What is actually written decides whether it gets opened.

Patchscout drafts that email for you, personalised and grounded in the real audit of the business's own website, and you send it from your own mailbox, so replies come back to you directly. That also means the mailbox habits above are entirely yours to get right: the sending reputation being built with every email is your own. Starting small and building sending history properly is worth doing before the first real campaign, and the three free searches at app.patchscout.co.uk/signup are enough to see what a first, carefully paced batch could look like.