3. Feature-by-Feature Scrutiny (The Idea as Described)
Categories:
- Table stakes (TS): customers expect it. It earns nothing, but its absence costs you.
- Differentiator (D): a real reason to choose you over the alternatives.
- Distraction (X): built but unlikely to move revenue or retention.
- Liability (L): creates support, cost, legal or trust risk.
Some elements sit in two buckets. The primary bucket comes first.
3.1 Classification table
| # | Element of the idea | Category | Reasoning |
|---|---|---|---|
| 1 | Unique ping URL per job | TS | Every rival has it: Healthchecks, Cronitor, Dead Man's Snitch, Better Stack, Sentry, Laravel Forge. It's a weekend build. Keep it as the fallback for scripts in the MSP product. |
| 2 | Schedules and grace periods (cron expressions, "expect every 24h, allow 2h late") | TS | Expected. Get time zones and daylight-saving changes right, or you'll send false alarms twice a year. |
| 3 | Email alerts | TS | Expected. The cheapest channel and the one MSPs use to feed their help desk. |
| 4 | Slack alerts | TS | Expected. For MSPs, Microsoft Teams matters as much or more (assumption; verify in calls). |
| 5 | SMS alerts | L / TS | Customers ask for it, but it's a fraud target. SMS pumping cost Healthchecks.io ~$1,800 over two days in May 2026. If you ship it, cap messages per account, allow-list countries and meter it. Not in v1. |
| 6 | "Scheduled jobs" as the scope | X as the headline | Generic scope puts you against six rivals and three free tiers. The job type matters less than who is accountable for it. |
| 7 | "Backups" as the scope | D (for MSPs) | Backups are the job where a silent failure is most expensive, and where someone else (the MSP) is accountable. This element is the wedge, buried at the end of the original description. |
| 8 | Reliability and trust as the moat (catalog note) | D, earned slowly | Correct, but it's a moat you have to build month by month. Until you have a public track record, reliability is table stakes and a risk, not an advantage. |
3.2 Scoreboard
| Category | Count | Elements |
|---|---|---|
| Table stakes | 4 | Ping URL, schedules and grace periods, email alerts, Slack alerts |
| Differentiator | 2 | Backups as the scope (for MSPs), reliability (once earned) |
| Distraction | 1 | Generic "scheduled jobs" as the headline |
| Liability | 1 | SMS alerts without fraud controls |
About 25% of what's described is a reason to buy, and only once it's aimed at MSPs. Everything else is a feature every rival already has.
3.3 "Building to avoid selling": explicit call-outs
- Cloning Healthchecks with AI. It feels like progress. It creates a product nobody needs to switch to.
- Integrations for everything. Kubernetes agents, Laravel packages, Terraform providers, GitHub Actions. Each is fun, each is permanent maintenance, and none brings an MSP.
- Status pages and uptime checks. A way to stay busy in a crowded adjacent market.
- 235 backup-vendor APIs. Backup Radar's moat, built over years. Email templates cover most products on day one.
3.4 What a disciplined v1 looks like
Keep: per-client email intake with 8 backup-product templates, a "teach it" rule screen, ping URLs, a multi-client backup board, alerts to email, Teams and Slack, email-to-ticket into any PSA, a daily digest, and a monthly white-label client report. Next: restore-test log with quarterly reminders, evidence export. Defer: native PSA APIs, backup-vendor APIs, SMS. Cut: generic developer marketing, free plan, Kubernetes and Laravel packages, uptime checks, status pages.