ParkiDose Timing Bot

3.70

Derivation Chain

Step 1 Proliferation of AI Parkinson's diagnostic technology

→

Step 2 Growing demand for Parkinson's patient medication management

→

Step 3 Medication timing optimization chatbot

Problem

For Parkinson's disease patients, even a 30-minute deviation in taking key medications like levodopa can trigger 'on-off phenomena' (sudden loss of drug efficacy). However, the optimal dosing time varies daily depending on meal times, protein intake, and drug interactions. 72% of patients report difficulty managing medication timing, and symptom flare-ups from poor timing lead to 2–4 emergency room visits per year (about $75–$225 per visit).

Solution

Patients input their prescribed medications, meal patterns, and activity schedule, and the system automatically calculates an optimal daily medication schedule based on a drug interaction database, then sends reminders via KakaoTalk/app push notifications. When meal times change, the schedule is readjusted in real time. An 'on-off' symptom logging feature provides medication efficacy data to the patient's physician.

Target: Parkinson's disease patients (age 60+) and their primary caregivers (spouse or adult children, ages 40–60)

Revenue Model: Premium Subscription: basic reminders free; meal-linked auto-adjustment + symptom logging + physician Report at $3.70/month. Family sharing plan at $5.20/month.

Ecosystem Role: Consumer

MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty

3.0/5

U Urgency

5.0/5

M Market

3.0/5

R Realizability

4.0/5

V Validation

3.0/5

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 (68%)

Tech Complexity

29.3/40

Data Availability

18.3/25

MVP Timeline

20.0/20

API Bonus

0.0/15

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 (53/100)

Competition

8.0/20

Market Demand

6.2/20

Timing

14.0/20

Revenue Signals

7.5/15

Pick-Axe Fit

10.5/15

Solo Buildability

7.0/10

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]

Dashboard