Business Model Architect

Business Model Canvas — Appointment Reminder Concept

Stage: Concept validation. The five interviews are founder-reported and not independently verified. No customer commitments, willingness-to-pay evidence, costs, retention, or regulatory review were supplied. This is a hypothesis map, not a forecast.

Value creation and delivery

Revenue-model comparison

Option A — monthly clinic subscription: predictable fee per clinic or tier. Test whether value and costs vary with clinic size. Monthly contribution = collected subscription revenue − variable delivery/support costs.

Option B — per confirmed appointment: aligns payment with a measurable event but creates attribution, dispute, seasonality, and revenue variability questions. Contribution = eligible confirmed events × agreed fee − variable messaging, payment, support, and integration costs.

Do not set a price or forecast revenue until buyer interviews, cost estimates, event definitions, and willingness-to-pay tests provide evidence. Avoid counting a reminder as preventing a missed appointment unless a suitable comparison supports that claim.

Channels and capabilities

Potential discovery channels to test include founder-led clinic interviews, professional networks, and referral partners. Required capabilities may include consent-aware messaging, reliable scheduling data, delivery monitoring, support, security controls, and clear opt-out handling. These are design questions, not confirmed integrations.

Risks and assumptions

• Clinics may value reduced manual work, fewer missed visits, or both; rank value with buyers rather than assuming.
• Appointment and patient information may be sensitive. Obtain qualified privacy, security, contractual, and jurisdictional review before handling real data.
• Integration effort, message costs, deliverability, staff adoption, and support burden are unknown.
• A per-event model needs a mutually accepted event definition, audit trail, and dispute process.

Six-week validation plan

1. Week 1: interview 8–10 additional decision-makers using neutral questions; document segment and evidence source.

Week 2: map the current reminder workflow and collect consented, de-identified baseline measures where appropriate.
3.

Week 3: prototype both pricing explanations; ask buyers to compare tradeoffs without presenting an unsupported “right” price.
4. Week 4: estimate variable delivery, support, setup, and integration costs with technical owners.
5. Week 5: obtain privacy/security and contract review before any pilot involving real patient data.
6.

Week 6: run a limited, consent-based pilot only if approved; predefine outcomes, comparison, opt-out, and stop conditions.

Decision gate: advance only if buyers confirm a meaningful job, the delivery model is feasible, economics can be tested, and qualified reviewers approve the data and contract approach.