When to Hire an Email Deliverability Consultant, and When It Is the List

Hire an email deliverability consultant when your messages are being rejected, deferred or rate-limited and the SMTP response names a specific technical fault. Those faults have correct answers, and someone who works on them daily will find them faster than you will. Do not hire one when your messages arrive and nothing happens. Silence is not a deliverability problem, and a retainer will not turn it into one that can be fixed.

The disclosure first. We build Keaz Signals, which sells buying signals and contacts for ecommerce outreach. We are not a deliverability consultancy, we do not sell consulting hours, and we have no plans to. So we are an interested party in the question of what a consultant is for, and the honest way to handle that is to draw the boundary carefully and then say which side of it we sell on.

What follows is an argument about scope rather than a verdict on anyone's work. Good deliverability consultants exist, they are worth their fee for the problems inside their remit, and the failure we see most often is not incompetence on their side. It is an agency buying the engagement for a symptom that was never theirs to fix. The useful question is not whether consultants are good. It is which of your problems is one.

Your SMTP error code answers the hiring question before anyone quotes you. Google publishes the full list of Gmail codes, and they split into two families that mean different things: one describes something wrong with how you send, the other is a judgement about whom you sent to. Telling them apart takes ten minutes and costs nothing (retrieved 21 September 2026).

Configuration faults look like this, and they are what a consultant is for:

• 550 5.7.25 — the sending IP has no PTR record, or forward DNS does not reference it.
• 550 5.7.26 — the sender is unauthenticated; DKIM and SPF both did not pass.
• 550 5.7.27, 5.7.29, 5.7.30 and 5.7.40 — SPF, TLS, DKIM and DMARC, each missing or failing.
• 421 5.7.32 — the From: header is not aligned with the authenticated SPF or DKIM domain.

Each has a right answer an outsider can verify in an afternoon, and none is a matter of opinion. If this is your error, go and buy the hours. The second family is the subject of the rest of this piece.

A consultant can be held to a published standard, and that is what makes the engagement worth scoping tightly. Google's sender guidelines set out the requirements plainly: SPF or DKIM for all senders, SPF and DKIM and DMARC above 5,000 messages a day, valid forward and reverse DNS, a TLS connection, RFC 5322 formatting, From: alignment, one-click unsubscribe, and a spam rate kept below 0.30% (retrieved 21 September 2026). Ask for that list, audited, with evidence. It is a finite job with an end state.

What nobody can sell you is access. The same document says so directly:

Google and Gmail don't accept allowlist requests from email providers. We can't guarantee messages sent by email providers will pass Gmail's spam filters.

There is no list to be added to and no relationship to be leaned on. The guidelines do mention deliverability mitigations, and they attach a condition rather than a price: senders who fail to follow best practices may not be considered for them. Compliance is the entry ticket, not the lever. Anyone implying they have a back channel is selling something that the receiving side has published a denial of.

A small agency may have nothing for a consultant to read, which is the practical problem nobody warns you about before the first invoice. Postmaster Tools is the primary evidence a consultant works from, and Google states that data might be missing if the total number of messages for a given day is too low, to protect users' privacy (retrieved 21 September 2026). Data also only covers messages sent to personal Gmail accounts.

An agency sending a few hundred well-targeted messages a week to store owners can therefore be in the worst position of all: something is clearly not working, and the dashboard that would say what is blank. A consultant in that situation can audit your configuration, which is real work, and then has no reputation or spam-rate series to reason about. That is not a failure on their part. It is the instrument's floor.

Two things follow. Ask whether your volumes populate the dashboards before you sign, because it decides whether half the engagement is possible. And treat an empty dashboard as missing evidence rather than as a clean bill of health. We take the reading of those dashboards apart in Reading Google Postmaster Tools for a Cold Email Domain.

The second family of error codes names the problem outright. Google's list includes 550 5.7.1, "This message is likely unsolicited email", and the 4.7.28 and 5.7.28 responses, which describe an unusual rate of unsolicited email from your IP, domain or netblock (retrieved 21 September 2026). The operative word is unsolicited. That is not a statement about your DNS.

Three softer symptoms point the same way. Replies that say the timing is wrong rather than the offer is wrong. Complaints concentrated in one segment while the rest of your sending is calm. And trouble that began when volume rose against the same audience, with nothing else changed — a wider pipe pointed at the same people delivers the same unwanted message faster, which is the argument in A Bulk Email Sender Solves Throughput, Not Timing.

A consultant can reduce the damage from a list problem — slower ramps, fewer messages per domain, retiring what is spent. None of that is a fix, because the input has not changed. This is a point about where each layer's authority ends, not a claim about anyone's compliance.

A consultant is the better purchase than anything we sell whenever the sending itself is broken, and it is cheaper for both of us to say that here. Burned domains, failing authentication, a reputation that fell without a change in audience, a receiving server deferring you — none of that is touched by what we do, and buying from us instead would be paying for the wrong problem.

The rest of where we lose, plainly. We do not export: leads move into campaigns and stay there, which for some teams is a dealbreaker and should be. There are no LinkedIn signals and no LinkedIn sending, and none are planned. We watch Shopify and WooCommerce stores in Europe and North America, and nothing else — no other platform, no other market. Registry, firmographic and hiring triggers are marked planned on our own site, which means they do not exist yet.

We sell no domains, mailboxes, SMTP, warmup pool or sequence engine. Sending runs through Instantly, in your own workspace, on your own domains — so the reputation you build stays yours, and so does the responsibility for it. We are GDPR-conscious by design and will not claim more than that; responsibility for what you send stays with you. The service layer next to the consultant is covered in An Email Deliverability Service Fixes Sending, Not Who You Send To.

We are not going to tell you how often a deliverability consultant solves the problem. We did not measure it, nobody we can cite has measured it in a way that would survive scrutiny, and a number invented for this article would outlive every caveat attached to it. The honest answer is that we do not know, and the useful part of this piece does not depend on knowing.

We are also not going to tell you what a retainer costs, or what inbox placement you should expect after one. Nor will we tell you how much a signal-led list improves deliverability — that is the claim this article comes closest to being able to make, and it is precisely the one we cannot. Testing it would need the same team, same offer, same domains and same week, with one variable changed. We have not run that experiment.

And we make no deliverability or reply-rate promises of any kind, nor will we repeat anyone else's coverage or accuracy figures without their own published, dated source. The refusal is the point rather than an aside: in this category, the claims that cannot be supported are exactly the ones being made loudest.

Wired together, the consultant keeps the sending defensible and the layer above decides who is worth writing to this week. A segment defines the kind of store you sell to. A signal decides which of those stores has a reason to care now. Warmup and pacing sit on the consultant's side of that line — see Email Warmup Ramps Toward Limits Nobody Publishes.

As of September 2026 we watch 4.1 million Shopify and WooCommerce stores, re-scraped weekly, and roughly 41,200 carried a fresh signal in the last seven days. Our own figures; they move, which is why they are dated. The buying signal catalogue lists what we watch for, and the ecommerce leads database is where those stores arrive with contacts attached. Signup includes 1,000 free leads.

• Gmail SMTP errors and codes, Gmail Help — the 5.7.25, 5.7.26, 5.7.27, 5.7.29, 5.7.30, 5.7.40 and 5.7.32 configuration codes, and the 5.7.1, 4.7.28 and 5.7.28 unsolicited-mail codes, retrieved 21 September 2026
• Email sender guidelines, Gmail Help — sender requirements, the 0.30% spam-rate limit, the allowlist statement and the note on deliverability mitigations, retrieved 21 September 2026
• Set up Postmaster Tools, Gmail Help — missing data at low daily volume, and the personal-Gmail scope, retrieved 21 September 2026
• Keaz Signals store coverage and weekly signal counts — our own figures, as of September 2026