Packaging deliverability services: audits, fixes, and retainers

After this lesson you can shape deliverability work into three services a small business will actually buy, scope each one at intake, and price them with arithmetic you can say out loud without flinching.

Everything this course taught you sells as one of three products: a diagnosis, a repair, or a watch. The audit finds what is wrong. The fix engagement makes it right. The monitoring retainer notices when it goes wrong again. Every other package I have seen is one of these three wearing a costume, or an open-ended promise that ends with an unhappy client and an argument about the invoice.

The audit: the entry product

The audit is the workflow you already have with a price on it. Fixed scope: one domain, its mail streams, its records and reputation signals, all read from outside. Fixed deliverable: the findings write-up from the previous lesson, every finding translated into the client's money and paired with its fix.

Price it as a diagnostic, not as a discounted teaser for the real work. The client is paying a professional to tell them what is true about their sending, and the write-up should hold its value even if they hand it to someone else to execute. That is the test of a real audit: if the document is worthless without you attached to it, you wrote a sales letter and charged for a report.

The fix engagement: finite by design

The fix engagement is scoped to the audit's plan and nothing else. Never sell "make our email better". You cannot finish it, so you cannot price it, and six months in you will be relitigating what "better" meant.

Completion is defined the same way the problems were found: from outside. Every item on the plan gets verified with the same external checks the audit used, record by record, and when the list reads verified, the engagement is done. Anything you discover mid-fix (and you will; audits see the outside, fixes open the cupboards) becomes a change order: a new scoped item with its own price, agreed before you touch it. Silent expansion is scope creep, and scope creep is how fixed prices quietly become hourly work you forgot to bill.

The retainer: the decay thesis with an invoice attached

This whole course has argued that email setups break silently over time. If you believed the argument, the retainer is its business model. The client buys three concrete things. The check routine runs on schedule against their domain. A monthly report says what was checked, what changed, and what it means in their numbers. And when something breaks, you are the first call, not a stranger they find mid-crisis.

It is the honest version of recurring revenue because the decay is real. You are not inventing busywork to justify the direct debit; you are standing watch over something that genuinely erodes. Which means you must teach the client, before the first invoice, that a report reading "all clear, nothing needed" is the product working. Skip that conversation and the quiet months read as you doing nothing, right up until they cancel in the month before the breakage.

Full disclosure: I sell monitoring software, so discount my enthusiasm for retainers by whatever amount seems fair. The reasoning stands without me. You watched records rot in Part 5; recurring problems justify recurring attention.

On tooling, the honest tradeoff. You can run retainers entirely on the manual routine and free tools, and for your first clients you probably should, because doing the checks by hand is what keeps the skill sharp. The cost is attention, and attention does not scale: somewhere past a handful of clients, the checking hours start crowding out the billable ones. Automated monitoring (Inbox Decay is one option, and yes, that is the bias I just declared) turns the routine into reviewing alerts. Count your hours per client per month and decide with your own numbers.

What moves the price

Five things change the size of the job, and your intake call exists to surface them. Domain count, because each sending domain is its own audit surface. Mail streams, because separated streams multiply what you verify. The number of ESPs and connected tools, because every sender is another set of records and expectations to check. List size, because hygiene work scales with it. And the B2B share, because corporate filters mean per-recipient investigation and appeals that consumer mail never needs.

The questions that pull these out are plain ones. What sends email on your behalf: the ESP, the CRM, the helpdesk, the billing system, anything sales installed? How many domains send mail for the business, including the one marketing set up for that campaign in 2023? Roughly how many addresses, and roughly what share are business inboxes? If the answers never change your quote, you are not scoping. You are guessing with extra steps.

Pricing without pretend numbers

You may notice this lesson quotes no dollar figures, and that is deliberate. Anyone publishing "typical rates" for this work is describing their own market or inventing one. What transfers is the logic.

Price the audit against the cost of the problem, which the audit itself quantifies. The revenue-per-email arithmetic from the findings lesson tells the client what a broken month costs them; a diagnostic priced well under that number is easy to say yes to.

Check that price against your own day rate. You have run the full audit workflow in the labs, so you know your honest hours. Multiply by what a working day must earn for your situation, in your city, at your experience level. Your numbers, nobody's directory.

Price the retainer against the attention the routine actually takes: your hours for the checks and the report, plus margin for the incidents you will absorb. Not against "what monitoring is worth" in the abstract, which is a number nobody can defend.

Value anchors are legitimate as reasoning the client can verify, never as claimed data. If one campaign to their list is worth what they told you at intake, and monitoring catches one silent breakage a year before campaign day, the retainer paid for itself. Show the arithmetic and let them check it.

Where the retainer ends

Decide the boundary before the first incident, because afterwards it is a negotiation. A retainer incident is a fault the routine caught with a bounded, known repair: the DKIM record a host migration dropped, a fresh blocklist listing to investigate and dispute, an SPF include a new tool broke. Restoring the setup the audit already verified is covered.

Building something new is not. An ESP migration, a new sending domain, a dedicated IP decision, rescuing a list after somebody bought addresses: each of those is a fresh engagement with its own scope and price. The line in the agreement can be one sentence. Restoration is included; construction is quoted.

The client to turn away

Sooner or later a prospect will ask for "deliverability help" and mean getting more cold outreach delivered from a rotating stable of domains. Say no, or scope your work strictly to their opt-in mail. Cold email is a structurally different game with its own folklore and its own legal exposure, and a retainer that promises to keep a cold-outreach machine inboxing puts you in a contest against filtering systems built to defeat exactly that. The next-but-one lesson gives you the honest version of that conversation; have it before you take the money, not after the reputation damage is mutual.

Pricing honestly is half the ethics of this trade. The other half is what you promise, and the next lesson is about the guarantees nobody can make and the sentences that protect your name when you refuse to make them.

Terms from this lesson

• retainer - an ongoing paid arrangement covering a recurring routine, reporting, and first response when something breaks.
• scope creep - work silently expanding beyond what was agreed and priced, usually one small favor at a time.
• change order - a new scoped and priced item added to an engagement by agreement, instead of absorbed silently.
• day rate - what a working day of your time must earn; the sanity check behind any fixed price you quote.

Check yourself

1. Why is a fix engagement scoped to the audit's plan instead of sold as "make our email better"?

Clients refuse to pay for anything open-endedA defined list with external verification has a knowable finish line; "better" cannot be completed or pricedThe audit plan is legally binding once deliveredOpen-ended engagements are only a problem for large agencies

2. What makes a monitoring retainer the honest version of recurring revenue?

Recurring billing is always more ethical than one-off feesThe monthly report gives the client something to fileDecay is real: records rot and reputations drift, so recurring attention answers a recurring problem rather than inventing busyworkIt locks the client in before a competitor can

3. Mid-retainer, your routine catches a DKIM failure: the client's new website host dropped the CNAME records during a migration. Retainer incident or new engagement?

New engagement, because the client's own vendor caused itRetainer incident: the routine caught it and the repair restores what the audit already verifiedNeither; DNS is always the client's responsibilityNew engagement, because DKIM work is specialized

Scenario

A prospect emails: "Our newsletters started going to spam. We don't need a whole audit, just a quick fix. What would you charge?" They seem sharp, budget-conscious, and in a hurry.

How do you respond?

Quote a small fixed fee to fix whatever they think is brokenTell them you only work with clients on a monitoring retainerExplain that the audit is the quick fix's insurance: a small fixed-scope diagnostic that finds the actual cause, with a write-up they keep either way, and the fix quoted from its findingsOffer to take a free look first to win the work