The entry point to the Senders Deliverability Dept. tier is a focused diagnostic session. Everything else follows from what we learn there. This is part of the Q1 intensive — it's how the dedicated Deliverability Engineer gets full context on your situation before the heavier work starts.

The Diagnostic Session

This is a working session, not a sales call. You get 1–2 hours with the Deliverability Engineer, who reviews your authentication setup, analyzes your sender reputation across major mailbox providers, examines your sending behavior patterns, assesses the tools you're currently using, and identifies the core issues affecting your deliverability.

The diagnostic often surfaces one or two high-impact problems that can be fixed immediately. Sometimes it's a DNS record that was misconfigured months ago and nobody noticed because it still technically resolves. Sometimes it's a volume pattern that's too aggressive relative to your domain's sending history, triggering filters. Sometimes it's a configuration gap between how your ESP is set up and what's actually happening in your infrastructure. Sometimes it's reputation damage from a previous campaign that's still affecting what mailbox providers do with your mail. When the engineer sees these, you walk through the fix together in real time.

Here's what a real-world diagnostic looks like. A B2B SaaS company comes in saying their transactional email is getting delayed. The engineer pulls their reputation data and sees that their email is fine technically, but also that they started cold outreach two months ago from the same domain. The cold outreach has a 2% complaint rate (which they assumed was normal for cold email).

The engineer points out that they're building reputation debt faster than they can pay it down, and the complaints from cold outreach are affecting how the mailbox provider treats everything from that domain. The company hadn't realized these two streams were competing for the same reputation. That's the kind of connection that changes everything.

After the session, you leave with:

• A clear diagnosis of what's happening and why
• Immediate fixes applied in real time (where applicable)
• Clarity on whether this is a small remediation or the start of a larger program
• A plan for how the rest of the Q1 intensive will be structured

The Rest of Q1: Intensive Work

The Q1 intensive runs for the full quarter and covers what the diagnostic surfaced. Depending on what you need, that might include:

• A full deliverability audit across all your domains and sending systems
• Crisis response (DNS fixes, reputation recovery, blacklist remediation) if there's an active issue
• Setup of all ongoing testing and monitoring across up to 10 domains and 10 sending systems
• Backup and fallback domain setup and warming
• Infrastructure buildout: domain architecture design, subdomain strategy, sending stream segmentation
• Rebuilding reputation after a complaint spike — monitoring closely, adjusting volume, managing complaints
• Implementing a segmented sending architecture so cold outreach doesn't tank your marketing reputation
• Overhauling list hygiene practices and re-engagement strategy
• Systematically fixing authentication and DNS gaps
• Warming a new IP for high-volume sending

The engineer provides strategic guidance and validation checkpoints. You execute changes on systems you own (your ESP, your DNS, your tools). The engineer executes directly on Senders-managed infrastructure. Everyone validates together that changes are actually working.

After Q1

Past Day 91, the engagement continues at the ongoing rate ($1,200/month, $3,600/quarter). You keep the same Deliverability Engineer, the full monitoring suite, and the operational rhythm — quarterly check-ins on strategy, weekly visibility into reputation metrics, ad-hoc Slack coordination for incidents and questions.

Some companies don't need to continue past Q1 — the intensive resolved the problem, the infrastructure is solid, the monitoring is set up, and the internal team can take it from there. Others continue indefinitely because email remains a business-critical operation and ongoing engineering attention is worth the rate.

There's no minimum commitment past Q1. You can stop at the end of any quarter.

What's Built In Versus Optional

Built in to the Deliverability Dept. tier from day one:

• Dedicated Deliverability Engineer
• Full monitoring suite (up to 10 domains, 10 sending systems)
• Ad-hoc seed list testing
• Proactive alerting and dedicated incident response
• 1 sender at 600 emails/day on Managed Email Infrastructure
• Dedicated Slack channel and ad-hoc meetings

What's not built in (and priced separately):

• Additional senders or volume beyond 600/day — priced per the Sender & Volume Pricing Schedule
• Verified email data credits — priced per the data module

How to Get Started

You schedule the diagnostic, come prepared with access to your email infrastructure (ESP dashboard access, DNS records, recent campaign data, sending logs), and the engineer digs in. Many companies bring their whole team to the session so everyone understands what's being reviewed and why it matters. Sessions can be recorded so the team can reference the explanation later.

Before committing to the full Q1 engagement, you'll know what the engineer found, why it matters, what the fix path looks like, and how the rest of the quarter will be spent. No surprises, no vague proposals.

The diagnostic is the cleanest way to evaluate whether the Deliverability Dept. tier is the right level for your situation.