ServicesThree pillars, one system

OutboundPipeline from cold↗ABMNamed accounts, warm market↗RevOpsData, routing, reporting↗

OUTBOUND

Pipeline you can plan around

Low volume, high intent, inboxes that actually land.

GTM BrainFOR OUTBOUND

It gets sharper with every reply it reads.

← All skillsOPERATIONS

Deliverability Audit

Which inboxes should rest, why, and how big the capacity gap is.

›[deliverability-audit]Leave your work email and Claude writes your version of this skill from your domain, against your ICP, your offers and your market. We send it over when it is built.PERSONALISED INSTANTLY · NO CALL REQUIRED

EXAMPLE RUN

[deliverability-audit] full fleetReading warmup and health per inboxProposing inboxes for rest against the ruleSizing the gap between capacity and committed volume9 inboxes proposed for rest. Capacity gap of 2 days a week.

THE SHORT VERSION

Deliverability degrades quietly. By the time reply rates visibly fall the damage is weeks old and takes longer than that to undo.

YOU GIVE ITYour sending fleet.

YOU GET BACKA read on sender health, a rest proposal with the reasoning, and the size of the capacity shortfall.

Why rest rather than push through

A degraded inbox does not just deliver its own mail badly. Sustained poor engagement on a sending domain affects the domain, and recovering a domain takes considerably longer than resting an inbox.

So the fleet is managed by resting inboxes before they cause domain-level harm, accepting a short-term capacity loss to avoid a long-term one. That trade is uncomfortable exactly when volume commitments are tight, which is when it matters most.

The capacity gap is the uncomfortable number

Resting inboxes means sending less. Reporting the rest proposal without the resulting shortfall lets a team accept the proposal and then quietly miss its volume for a fortnight without connecting the two. The gap is stated in the same output.

Read and decide, not execute

This is the canonical rule set and the on-demand look. Actually resting an inbox, tagging it and detaching it from its campaign so that sending genuinely stops, is a separate execution skill. Keeping the read separate from the action means you can look without committing.