Running Deathplanswitch as a service, Security Tools

Deathplanswitch Agency Implementation, Selling Client Continuity Protection

Learn how to position and deliver Deathplanswitch as a retainer service for agencies managing client infrastructure. This course covers setting up self-hosted instances for clients, configuring escalation workflows, packaging continuity protection as a recurring revenue product, and handling the sensitive conversations around succession planning with your client base.

Open the decision record for Deathplanswitch

What does running Deathplanswitch for clients commit you to?

Published figures for this service. Blank fields are not published.

Monthly tool cost
Deathplanswitch is open-source (MIT-licensed) and has no published paid plan; the only published cost basis is the agency's own hosting, SMTP, and scheduler infrastructure. Hosting, SMTP, and labor costs must be supplied by the agency, not modeled here.
Time to first value
Not published
Payback
Not modeled, client price, labor cost, hosting/SMTP costs, and expected client volume are not supplied
Guided implementation
8 hours

Is Deathplanswitch worth running as a client service?

The evidence supports building a managed continuity service around a free, self-hosted tool that covers weekly check-ins, staged escalation, next-of-kin verification, and false-alarm notices for solo developers. What remains unknown is whether agencies can sustain it economically, since there is no hosted version, no multi-client dashboard, no pricing data, and no published effort figures.

An agency-fit judgement for reselling this service. It is separate from the tool description on the decision record.

Before you start

What has to be in place before the first client engagement.

Tools and subscriptions

  • PHP 8.1 or newer hosting environment
  • SMTP account for outbound check-in and notification email
  • Cron or any external scheduler capable of requesting a web address every 15 minutes
  • Hosting environment independent of the client's protected sites
  • Place to record next-of-kin and designated contact details (no database is included)

People and inputs

  • Server administration capability to deploy and keep a self-hosted PHP app running
  • Process for verifying the staged escalation timeline (reminders at 24 and 48 hours, next-of-kin inquiry, contact notifications)
  • Process for reviewing and updating pre-written contact messages with the client
  • Monitoring routine for scheduler requests and SMTP delivery so escalations fire correctly

Included with the course

6 working documents for delivering this service.

  • Client Continuity Audit Worksheetworksheet
  • Deathplanswitch Setup and Configuration SOPsop
  • Pre-Written Escalation Message Templates by Roletemplate
  • Monthly Check-In Verification Checklistchecklist
  • Client Onboarding Guide for Continuity Protectionguide
  • Retainer Pricing and Packaging Worksheetworksheet

Listed by name. These documents are not yet published as individual downloads.