7. What's Missing: The Gap Between Built and Paid, Renewed, Referred
Assumption: nothing is built yet. So these are gaps between the idea and a business.
7.1 Gaps to pay
| Gap | Why it blocks payment | Fix |
|---|---|---|
| No defined buyer | "Anyone with a cron job" means competing with free tiers | Pick one: small MSPs (1–20 staff, 5–80 clients) in the US, UK, Canada and Australia. |
| No pricing | Undefined | Solo $39/mo (≤10 clients), Team $99/mo (≤30), Growth $199/mo (≤80), then $2.50 per extra client. Annual at 10× monthly. 14-day trial, no free plan, no setup fee, month to month. |
| No reason to switch | Developers already have Healthchecks and friends | For MSPs: "stop reading 100 backup emails every morning, and hand every client a monthly backup report". |
| No proof it works | MSPs won't trust a new monitor with clients' backups on a website's word | Concierge phase case studies, a public status page from day one, an honest incident history. |
| No trust signals | You'll see client names, hostnames and backup setups | Security page: what you store (job metadata only), what you delete (emails after parsing), where data lives, two-factor login, a data-processing agreement. |
7.2 Gaps to renew
| Gap | Fix |
|---|---|
| "Set and forget" means invisible | A daily digest and a monthly client report. The product shows up every day even when nothing fails. |
| False alarms | Unknown wording = warning, never success. Template-change detection. Maintenance windows. Alert grouping. |
| Missed failures | Two inbound providers, an external watchdog, retry and dead-letter queues, and a "silence is suspicious" rule for every job. |
| No switching cost | 13 months of backup history per client, restore-test logs, and report archives. Leaving means losing the evidence trail. |
| Seasonal or one-off use | The restore-test log with quarterly reminders gives a reason to log in every quarter, not just when something breaks. |
7.3 Gaps to refer
| Gap | Fix |
|---|---|
| Nothing shareable | The client report footer: "Backup monitoring by [name]". Every MSP's clients see it every month, and some clients are other MSPs' prospects. |
| No peer proof | Short "caught it" stories with the MSP's permission: which backup, how long it had been failing, how fast it was fixed. |
| No referral economics | One month free for the referrer and the new MSP, for each paying referral. |
| No community presence | One useful post or guide a week in MSP spaces. Answer backup-monitoring questions helpfully, not with links. |
7.4 Non-product gaps
Distribution
- Missing entirely from the idea. "Word of mouth among developers" worked for Healthchecks over 11 years, helped by an open-source version. It's too slow for a 24-month target.
- Channels that work for MSP tools: peer referral, MSP communities (r/msp, peer groups, Discords), search by backup product ("Veeam backup failure alert for multiple clients"), and partner listings with PSA or backup vendors later.
- Channels that burn money: broad paid ads, MSP trade-show booths before $5k MRR, cold email to thousands of MSPs.
Positioning
- Current: "heartbeat monitoring for scheduled jobs and backups". Accurate, generic, and identical to six rivals.
- Better: "Every client's backups on one screen. Know the moment one fails, and hand every client the monthly proof."
Sales motion
- Product-led with a founder call. 14-day trial, self-serve setup, and a 20-minute setup call offered to every MSP in the first year.
- No sales team, no demos for MSPs under 30 clients after month 6. Video walkthroughs instead.
Reliability and operations (the real moat)
| Area | Minimum |
|---|---|
| Inbound email | Two providers with fail-over MX records. Store raw email briefly, parse, then delete. |
| Alerting | Queue with retries, and a dead-letter alarm. |
| Watching the watcher | An external heartbeat on your own scheduler and alert sender, on a different provider. |
| Database | A hot standby and daily off-site backups, with a restore test every quarter (practise what you sell). |
| Status and incidents | A public status page and a written post-mortem for every incident. |
| Time | Correct time-zone and daylight-saving handling for every client. |
Compliance and legal
| Area | Requirement |
|---|---|
| Data protection | GDPR / UK GDPR data-processing agreement for MSPs. Hostnames, job names and email headers can be personal data. Keep EU data in the EU. |
| Data minimisation | Store job name, status, time, size and product. Never backup contents, file lists or credentials. |
| Claims | "Evidence of backup status", never "your backups are safe", "compliant" or "insurance-approved". |
| Liability | Terms that cap liability at fees paid. You notify; you don't guarantee. |
| SMS (later) | Country allow-lists, per-account caps, and metering, to prevent SMS pumping fraud. |
Team
- Not provided. At minimum you need one developer who can run a reliable service, and one person with MSP access. That can be the same person if they've worked at an MSP.
Metrics and instrumentation
- Activation: first client connected and first backup email classified within 24 hours of signup.
- Classification rate (target ≥98% automatic), alert latency (target <5 minutes), false-alarm rate.
- Weekly active MSPs, client reports sent per month, restore tests logged per quarter.
- Trial-to-paid, month-3 retention, monthly logo churn, share of trials from referral and search.