9. Assumptions and Open Inputs
The idea came from row D8 of the 30 Sept 2026 micro-SaaS idea catalog as a one-line concept. Team, location, hours per week available, pricing, stage and traction were not supplied. Here's what was assumed, and how the verdict changes if each assumption is wrong.
9.1 Assumptions made
| Input | Assumption used | If actually different… |
|---|---|---|
| Target customer | Indian dental clinics, 2–6 chairs, one city | A founder with deep access to another market (e.g. Indonesia, or US dental through a practice-management reseller) could change the wedge. It wouldn't change the "reminders are bundled" problem. |
| Location | India-based founder, able to visit clinics in one city | Without in-person access, the pilot and trade-partner channel get much harder. Multiply the odds by ~0.6. |
| Hours per week available | Two columns: ~15 hrs/week and full-time | Below ~10 hrs/week, the day-45 test won't finish on time. |
| Pricing | ₹1,499 / ₹2,999 / ₹5,999 a month; blended | If clinics only pay ₹999, every rung needs ~2.6× more clinics, and $10k+ is out of reach. |
| Stage | Idea. No code, no users, no revenue. | Any paying clinics change this from judgment to evidence. |
| Clinic value | A 2–6 chair clinic has ~500 appointments a month, a ~20% no-show rate, and ~₹800 average value per appointment | Then a 5-point drop is ~25 appointments ≈ ₹20,000 a month. All three numbers are unverified; the pilot baseline replaces them. |
| Reminder effect | ~25% relative reduction in no-shows (meta-analysis, ~21% → ~15%) | Indian clinics may differ. WhatsApp two-way may do better than SMS; unverified. |
| Message cost | Utility | Reported by third parties, not read on Meta's own rate card. If service replies are billed from the first message, cost rises but margin stays above 80%. |
| Churn | 4% monthly after month 6 | At 6%, $20k is out of reach and $5k needs ~20 new clinics a month. |
| Competitors | Indian EMRs offer one-way reminders; two-way WhatsApp confirmations are not yet standard | The most important unverified assumption. If they already offer it, stop at week 1. |
| Onboarding route | You can onboard clinics' own numbers on the Cloud API directly (Tech Provider / embedded signup) at low cost | If you need a partner with a monthly per-clinic fee, the margin may disappear. Day-14 checkpoint. |
9.2 Inputs that would change the verdict most (please supply)
- Hours per week available, and for how many months.
- Your city, and whether you can visit clinics in person.
- Dental access: a dentist in the family, a dental-supply or lab contact, or a clinic you already serve.
- WhatsApp Cloud API experience: have you built templates, webhooks and embedded signup before?
- What Practo Ray, Eka Care, HealthPlix and DocPulse charge for, and whether they do two-way WhatsApp (you can check this in an afternoon of demo calls).
- Any other market you have real access to (Indonesia, Gulf, Brazil). Access matters more than market choice here.
9.3 Definitions used throughout
- Tier A / Tier B: as in docs/README.md.
- No-show rate: booked appointments where the patient didn't arrive and didn't cancel in advance, divided by booked appointments.
- Relative reduction: (baseline − current) ÷ baseline. 20% → 15% is a 25% relative reduction.
- Slot refill rate: freed slots (cancellations) filled from the waitlist, divided by freed slots.
- Utility / marketing / service message: Meta's WhatsApp message categories. Utility is transactional (e.g. an appointment reminder); marketing is promotional; service is a free-form reply inside the 24-hour window.
- All odds are judgment estimates, not computed statistics.