KoltrixWhen to hire a deliverability consultant, and what to bring
Most email problems are fixable in-house. Here are the signs you need an expert, what a good engagement looks like and the evidence to hand over.
On this page(9 sections)
Sooner or later a founder asks: do we need an email deliverability expert? Receipts are landing in spam, a big customer says your messages never arrive and the person who set up DNS two years ago has left.
Hiring help can save weeks, and it can also waste money on advice you could have had for free. This guide helps you decide whether you need a consultant, what to try first, how to judge one and what to prepare so that an engagement is short and useful. It does not recommend vendors, and it is general information, not legal advice.
Try these first
Many problems that look like a deliverability crisis come from a handful of basics. Rule them out before you spend money.
- Authentication. Check SPF, DKIM and DMARC. A 30-minute review is described in an email authentication audit.
- A single clear cause. Work through the order in authenticated but still in spam: a diagnosis flow.
- Your data. Look at Google Postmaster Tools and your sending provider's dashboard. See the Postmaster Tools guide and deliverability metrics to alert on.
- A blocklist. Check whether your IP or domain is listed. See the blocklist delisting playbook.
- List quality. If you mail old or purchased lists, fix that first. See list hygiene.
- Your provider's support. A good sending provider will look at your account and tell you what they see.
If these steps explain and fix the problem, you do not need a consultant.
Signs you do need one
Consider outside help when:
- The cause stays unclear after you have checked the basics and a real recipient at the affected provider still sees spam.
- A serious problem is hurting revenue, such as receipts, invitations or password resets not arriving, and you lack time to dig.
- You are changing something large, such as moving to a dedicated IP, migrating providers or sending at much higher volume, and a mistake would be expensive.
- You are sending to people at scale, for example a product with millions of messages a month, and reputation decides the business.
- You have been blocked by a major provider and escalations are not working.
- A compliance question arises, with consent and marketing rules across several countries. That is a job for a lawyer, sometimes with a deliverability specialist alongside.
- Nobody on the team has the skills and the learning curve is longer than the problem allows.
If your main issue is volume planning, see planning for email volume spikes and IP warm-up before you decide.
What a consultant can and cannot do
Realistic benefits:
- A fresh pair of eyes on authentication, DNS, sending patterns and content.
- Experience with how large mailbox providers behave, including how to escalate.
- A plan for warm-up, segmentation and monitoring.
- Help interpreting reports and bounces.
- Review of your sending setup, including shared versus dedicated IPs and subdomains.
Limits:
- Nobody can force a mailbox provider to accept your mail. Reputation is earned from recipients' behaviour.
- A consultant cannot fix a list of people who do not want your mail.
- Promises of guaranteed inbox placement are a red flag. Providers do not sell guarantees to consultants.
- They cannot replace your team's ongoing discipline.
How to judge a consultant
Look for signs of substance.
- They ask for data before proposing anything. Good ones want logs, reports and examples first.
- They explain in plain language and show their reasoning.
- They separate what they know from what they are guessing.
- They give references or examples of similar work, and you can speak to someone.
- They define the scope and an end. A short audit with a written report is better than an open-ended retainer to start.
- They are honest about causes that are not technical, such as list quality or content.
- They do not push tools or software that earns them commission without saying so.
Be cautious of anyone who promises quick fixes for a price, offers to "warm up" your domain with fake engagement or suggests buying lists. Those tactics can get you blocked.
Types of engagement
| Type | What it is | Good for |
|---|---|---|
| Audit | A fixed-scope review with a written report | A first step, a clear question |
| Project | A defined piece of work, such as a migration or warm-up | Large changes |
| Retainer | Ongoing monitoring and advice | High-volume senders |
| Incident help | Short-term help with a block or a drop in delivery | Emergencies |
| Training | Teaching your team to run it themselves | Building skills in-house |
For most startups, an audit or a short project is enough.
What to bring
Preparation makes the engagement faster and cheaper. Gather:
- A clear problem statement: what is wrong, since when, which mail, which providers and what changed.
- Examples: full headers of a good and a bad message, with dates.
- Your DNS records: SPF, DKIM, DMARC, MX and any relevant subdomains. See DNS records for email.
- Sending details: providers, domains, IP addresses, volumes and a table of who sends what. See two providers on one domain if you use more than one.
- Reports: Postmaster Tools, DMARC reports, bounce and complaint figures from your provider. See choosing a DMARC monitoring tool.
- Your list story: how addresses are collected, how consent is recorded and how you remove people. See unsubscribe pages.
- Recent changes: new tools, new templates, imports and campaigns.
- Your goals: what a good result looks like, in numbers.
- Access, carefully: read-only where possible. Share only what is needed and use their own accounts.
Remove or redact personal data from examples before sharing, and have a confidentiality agreement.
Questions to ask before you sign
- What will you deliver, and by when?
- What data and access do you need?
- How will we know it worked?
- What is not included?
- How do you handle our customers' data?
- What happens if the problem has a non-technical cause?
- What will it cost, and is it fixed or hourly?
After the engagement
- Write down what was found and what changed.
- Assign owners for monitoring and for each recommendation.
- Set alerts so you learn about problems before customers do.
- Schedule a review in a month and in a quarter.
Key takeaways
- Rule out authentication, blocklists, list quality and provider issues before hiring anyone.
- Bring in help for unclear causes, revenue-critical problems, large changes or major provider blocks.
- Beware promises of guaranteed placement and tactics that fake engagement.
- Start with a fixed-scope audit, and prepare data, DNS records, examples and a clear problem statement.
- Turn the result into owners, alerts and reviews so the problem does not return.
Start with Koltrix
Your domain, one inbox, and an API that sends.
A team inbox where AI sorts and drafts (nothing is sent without your click), plus the transactional API and SMTP relay your product sends with. 7 days free, no card.
