DEV Community

Hive80-lab
Hive80-lab

Posted on

The Outage Email That Turned a $900 Contract Into a $2,400 Contract

Free sample: the first-30-minutes incident runbook — grab it here — no email needed.

A two-person MSP in our orbit had a Tuesday outage: DNS blipped, three clients lost mail for 40 minutes. The tech did one unusual thing — he sent a plain-text email to all three clients before they noticed, with three lines: what broke, what we did, what happens next. All three stayed. Two of them called back within a week asking what else "covered" they were missing.

Why that email works

  • It flips the power frame: the vendor reports first, so the client never gets to feel blind.
  • It converts an incident (cost center) into evidence of a system (value).
  • It creates a paper trail the client reads at renewal time — every future upsell references your own comms, not your pricing.

The template (steal it)

Enter fullscreen mode Exit fullscreen mode

Notice what it does NOT contain: apologies longer than one clause, jargon beyond one noun, and any sentence that ends with "we'll discuss billing."

The money move

At the next quarterly review, hand the client a one-page "coverage map" — the named runbooks, the paging windows, the 15-minute update cadence — and price the tiers explicitly. Businesses happily pay 2-3x for certainty, but certainty has to be visible in writing. The outage email above is the first proof artifact; the coverage map is the quote.

Steal the kit

Send one honest outage email this week, even if it's for a 5-minute blip. The renewal conversation changes.

The full coverage-map + client-comms kit ships in the Ops Mega Bundle (lifetime updates). Free versions of several scripts live in our GitHub repo. Send one honest outage email this week — even for a 5-minute blip — and watch the renewal conversation change.

Top comments (0)