A
GLP-1 Clinic Booking Optimizer
3.65
Derivation Chain
Step 1
Expansion of oral GLP-1 obesity therapeutics
→
Step 2
Patient surge at obesity clinics causing appointment/waitlist chaos
→
Step 3
Clinic appointment & revisit auto-scheduling SaaS
Problem
As oral GLP-1 therapies become mainstream, obesity/diabetes clinics are experiencing a surge in new patients. Small clinics (1-3 doctors) manage appointments and re-prescription schedules manually separate from their EHR, wasting 5-8 hours per week. No-show rates of 15-20% cause monthly revenue losses of 2-4 million won (~$1,500-$3,000).
Solution
Provides automated re-appointment scheduling aligned with GLP-1 prescription cycles (4-week/8-week), no-show prediction-based overbooking optimization, and KakaoTalk automated reminders to improve clinic operational efficiency.
NUMR-V Scores
NUMR-V Scoring System
| N Novelty | 1-5 | How uncommon the service is in market context. |
| U Urgency | 1-5 | How urgently users need this problem solved now. |
| M Market | 1-5 | Market size and growth potential from proxy indicators. |
| R Realizability | 1-5 | Buildability for a small team with realistic constraints. |
| V Validation | 1-5 | Validation signal quality from competition and demand data. |
SaaS N=.15 U=.20 M=.15 R=.30 V=.20
Senior N=.25 U=.25 M=.05 R=.30 V=.15
Feasibility (69%)
Data Availability
19.4/25
Feasibility Breakdown
| Tech Complexity | / 40 | Difficulty of core implementation stack. |
| Data Availability | / 25 | Practical availability and cost of required data. |
| MVP Timeline | / 20 | Expected time to ship a usable MVP. |
| API Bonus | / 15 | Bonus for viable public API leverage. |
Market Validation (54/100)
Validation Breakdown
| Competition | / 20 | Signal quality from competitor landscape. |
| Market Demand | / 20 | Demand proxies from search and mention patterns. |
| Timing | / 20 | Fit with current shifts in tech, behavior, and regulation. |
| Revenue Signals | / 15 | Reference evidence for monetization viability. |
| Pick-Axe Fit | / 15 | How well the concept serves participants in a trend. |
| Solo Buildability | / 10 | Practicality for lean-team implementation. |
Technical Requirements
Backend [medium]
Frontend [medium]
Infrastructure [low]