Hire an email deliverability consultant in three situations:
- Replies fall on several sending domains at once.
- The same failure returns after every fix.
- Your invoices and support emails start landing in spam.
Fix it yourself when the trouble sits in one mailbox or one domain and you can name the cause. Common causes are a missing SPF, DKIM or DMARC record, an inbox that skipped warmup, or an unverified list.
A deliverability consultant works out why your mail is not reaching the inbox. Then they tell you, in order, what to change. Freelancers usually sell it by the hour, vendors as a defined review, and outbound agencies fold it into the campaigns they run.
One disclosure first: my agency does not sell deliverability as a stand-alone product, so this guide comes from the operator side. It covers what to check yourself, what is worth paying someone to find, and what a report must contain before it earns its invoice.
What does a deliverability consultant check?
The job is diagnosis across the whole sending system. A real consultant checks authentication records, domain and IP reputation, list quality, warmup history and the volume each inbox sends. Then they tell you which of those broke first.
Mailbox providers set the floor everyone builds on. Gmail requires every sender to use SPF (a DNS record listing the servers allowed to send for your domain) or DKIM (a signature proving the message was not altered), and Postmaster Tools, Google's free dashboard for senders, should show spam rates under 0.3%. Senders above 5,000 messages a day must also publish DMARC. For marketing and subscribed mail, they must offer one-click unsubscribe (Google sender guidelines).
Google's recommended target is lower: a spam rate under 0.1% (Google bulk sender guidance).
Two standards sit underneath those rules:
- DMARC. It checks that the domain in the visible From line matches a domain that passed SPF or DKIM. It also lets the domain owner publish a policy of none, quarantine or reject (RFC 7489).
- One-click unsubscribe. It needs three things: a List-Unsubscribe header with an HTTPS link, a List-Unsubscribe-Post header reading "List-Unsubscribe=One-Click", and a DKIM signature that covers both headers (RFC 8058).
Why is multi-domain cold outbound a different problem?
A newsletter goes out from one domain. Serious cold outbound goes out from many. For cold email, my rule is 10 to 20 sending domains and 20 to 40 inboxes, more for a bigger company. At that size, "is my email OK?" is no longer one question.
The provider ceiling is real. Google's Workspace sending limits cap each user at 2,000 messages a day (1,500 for mail merge, 500 for trial accounts). Hit a limit and that user can't send new messages for up to 24 hours. We keep each inbox far below that ceiling and spread the volume across many inboxes.
Scale makes this concrete. One UAE tech startup we worked with sent about 1,250 emails a day from 50 email accounts and booked 684 demos in 4 months. That is roughly 25 sends per account per day. Nobody spots a broken DKIM key on account 37 by opening a dashboard once a week. You need a setup that tells you which domain, which inbox and which day.
To book 30 to 35 B2B sales calls a month, you have to reach at least 10,000 people every month. Across that many sends, one silent inbox or one dead domain hides inside the totals. Here is one month, 17 April to 17 May 2023, from a UK software development and IT consulting client of ours, split by channel:
| Channel | Positive replies | Meetings booked | Sales |
|---|---|---|---|
| 62 | 18 | 3 | |
| Cold email | 41 | 13 | 2 |
Together those two channels closed 5 contracts that month. If the sending layer behind the email column had slipped into spam, the 13 email meetings would have dried up, and the monthly total would have read as a slow month, not a sending fault.
So my team puts each client's sending on its own dedicated IPs, with different IPs behind different domains of the same client, and a client can run on 10 to 20 IPs. We handle the domains, SPF, DKIM, DMARC, warmup and monitoring inside the campaign. The goal is isolation: trouble on one domain should stay on that domain.
When should you hire one instead of fixing it yourself?
Work through a ladder in this order: the mailbox, the domain, the list, then the sending pattern. Rewriting the email is the tempting first move. Don't. Climb the ladder first.
| What you see | Usual cause | Fix yourself or hire |
|---|---|---|
| A new inbox lands in spam from its first sends | No warmup, or volume raised too early | Fix yourself: pause it and warm it up |
| Gmail bounces mail with a 5.7.26 error, its code for unauthenticated mail | Missing authentication, per Google's sender guidelines | Fix yourself if you have DNS access |
| Replies die on one domain while the others still get answers | That domain's reputation, sometimes a blocklist | Fix yourself: rest the domain and check listings |
| Replies fall on every domain in the same week, with no list change | A shared cause in setup, sending pattern or repeated content | Hire |
| Invoices or support mail start reaching spam | Cold mail going out from the main company domain | Move cold mail off that domain today yourself; hire if replies stay down |
| Each fix holds for two weeks, then the problem returns | A root cause nobody has found | Hire |
A single blocklisted domain is a recovery job with its own steps, the kind you handle by working through a blacklisted domain recovery before you spend money.
The decision rule is short:
- Fix it yourself if you can point at one mailbox or one domain.
- Pay someone if the problem spans several domains, mailboxes or campaigns and you cannot isolate it in an afternoon.
If one email draft is weak, rewrite the draft and keep your money.
What should you fix before paying anyone?
Copy will not rescue weak sending or a poor list. Broken sending does not come back as a reply explaining itself. It comes back as silence, and silence looks exactly like weak copy. None of the basics below requires an expert, and you can check all of them in one sitting:
- Keep cold mail off your main company domain. Use separate domains that point at a real website.
- Set SPF, DKIM and DMARC on each sending domain before sending any volume.
- Let every new inbox warm up for a minimum of 10 to 14 days ahead of the first prospecting email. If you are unsure about timing, check how long a new email domain needs to warm up.
- Run every address through verification, and aim for bounces under 0.5%.
- Raise volume only after warmup ends.
- Put the last 30 days of sends per inbox per day into one sheet. If one inbox carries most of the volume, start your search there.
- Check whether the same text goes to everyone with no variants. Identical sends at volume are an easy pattern for filters to catch. Google says Gmail uses machine learning, powered by user feedback, to spot spam patterns in large data sets.
If all seven pass and results still fall, you have a real reason to hire.
What should a real deliverability audit include?
Hand over these before the consultant starts:
- every sending domain and the inboxes on each one
- DNS access, or a person who can change records the same day
- access to the sending tool and its logs
- daily sends per inbox for the last 30 to 60 days
- the templates and sequences sent in that period
- bounce and complaint history, plus any Postmaster Tools data
- where each list came from and how it was verified
- any blocklist alerts or placement tests already run
Then judge the report. Every finding should answer four questions: what the root cause is, what the exact fix is, who owns it, and what has to happen before it.
The report should also say whether you have a one-domain problem or a fleet-wide one. Those need different fixes. A report with 40 generic best practices and no order is a checklist dump. You could have downloaded it for free.
Check the DMARC plan line by line. Google says to put DKIM and SPF in place at least 48 hours before DMARC. It then says to run policy none for a week, which carries no risk of rejection, and only then quarantine a small share of mail. That share is 10% for a small organization and 1% for a large one (Google DMARC rollout).
Microsoft describes the same climb from none through quarantine to reject, raising the share of affected mail in steps of 25, 50, 75 and 100 (Microsoft Learn). If the report jumps a fresh domain straight to reject, ask why.
Deliverability is one part of the funnel. The wider review of list, copy and offer belongs in a full outbound audit.
How much does an email deliverability consultant cost?
| Option | Published price, at the time of writing | What the price usually buys |
|---|---|---|
| Freelance specialist | Upwork gives $15 to $40 an hour as the general range, $60 to $400 per project for authentication setup, and $300 to $1,000 for ongoing monitoring. At least one listed profile charges $500 an hour (Upwork) | Setup and narrow fixes |
| Consultant or vendor service | One email verification vendor lists an authentication review, a full audit, and DMARC and BIMI implementation, priced on request | A diagnosis and a fix plan |
| Outbound agency | My team's monthly fee starts from USD 3,000 (about EUR 2,500) and covers all campaign work including sending management; tools, domains and mailboxes are paid separately | Sending run day to day, with lists, copy and replies |
| Monitoring or validation tool | A vendor subscription; price varies by vendor and sending volume | Alerts and data |
| In-house | A share of an operations person's time; the real cost depends on salary and time spent | Ongoing ownership, if that person knows the work |
Upwork's figures are marketplace data with no stated method. Treat them as a rough floor.
Each pricing model fits a different job:
- Hourly suits a narrow, known task.
- A project price suits a defined audit.
- A retainer suits sending that needs watching every week.
Before comparing any two quotes, ask one question: does the provider only audit, or does it also make the fixes? A cheap audit that becomes a PDF nobody implements costs more than it looks.
Consultant, freelancer, agency, tool or in-house?
| Option | Speed to start | Depth | Your coordination load | Best fit |
|---|---|---|---|---|
| Freelancer | Fast | One task | High: you brief, check and own the result | One domain, a known setup job |
| Consultant | Medium | Deep diagnosis | Medium: your team implements | Many domains and an unexplained drop |
| Agency | Slower, because it builds the program | Deep and ongoing | Low | Multi-channel outbound run for you |
| Tool | Same day | Data only | High: someone must read it and act | A healthy setup that needs watching |
| In-house | Slow to hire | Grows over time | Medium | Large, constant sending volume |
A freelancer is enough for a narrow job, which is the usual tradeoff when hiring a cold email freelancer or an agency.
My agency sits in the third row, the cold email agency model, and none of what we sell is a stand-alone deliverability audit. If all you need is a DKIM fix, a freelancer will do it faster and cheaper.
Why fix deliverability before adding volume?
If your results depend on more sends but your sending is unstable, extra volume changes nothing. I raise volume last. A hundred thousand more emails this month on shaky foundations just means more mail in spam. If your sending does not work at small numbers, it will never work at big numbers.
The stakes rise because in our campaigns email follows a LinkedIn touch. A sequence needs at least 5 to 6 touches, and several of them are emails. If they land in spam, a good LinkedIn conversation loses the follow-up that would have turned it into a call.
Fix the sending first. Then scale: add inboxes to the channel that already works.
Before you pay anyone, build the sheet of sends per inbox per day for last month. If nobody on your team can produce it, that is the first thing to hire for.
Seeing replies fall on several domains and unsure whether to fix it or hire? Book a call and bring last month's sends per inbox. I will say whether it looks like a job for a consultant.
Questions founders ask before hiring
How long until deliverability consulting shows results?
Diagnosis is fast and recovery is slower. One vendor lists its authentication review at about 1 to 2 weeks with up to 2 meetings. Any new domain or inbox the consultant recommends still needs its warmup before it carries volume. A damaged domain recovers only as fast as mailbox providers re-trust it, and no consultant controls that.
Which email service has the best deliverability for B2B sending?
No provider fixes a weak sender. Placement follows your authentication, reputation and list, and each mailbox provider filters in its own way (how placement differs by mailbox provider). Be careful with open-rate comparisons. Google says it does not track open rates, and low open rates are not necessarily an accurate sign of deliverability (Google sender guidelines). Judge by replies.
Does the Gmail bulk sender rule apply to B2B cold email?
Only partly. Google exempts mail that lands in Google Workspace inboxes from its sender guidelines, so company addresses hosted on Workspace sit outside them (Google bulk sender guidance). Personal Gmail addresses on your list still count, all mail from one primary domain counts together, and once a domain counts as a bulk sender, Google says that status does not expire.
Who should read DMARC reports after the consultant leaves?
One named person. Google recommends a dedicated group or mailbox for DMARC reports, because a domain can receive hundreds or even thousands of them a day (Google DMARC setup). Without an owner, those reports go unread, and the next authentication failure only shows up when replies drop. Name that person before the consultant's last call.