A
Tremor Symptom Self-Tracker
3.95
Derivation Chain
Step 1
AI Parkinson's disease diagnostic technology expansion
→
Step 2
Demand for early symptom self-monitoring
Problem
Parkinson's disease takes an average of 1-3 years to diagnose, and most patients fail to recognize early symptoms (micro-tremors, motor slowness, handwriting changes) or dismiss them as normal aging. Among adults over 50 who experience hand tremors, it takes an average of 8-14 months before visiting a neurologist, during which no symptom data is recorded, leaving doctors with no meaningful information at the first consultation.
Solution
Uses smartphone accelerometer sensors to measure hand tremor frequency (4-6Hz is the suspected Parkinson's range), tracks handwriting changes (touchscreen writing analysis), and records gait patterns through a daily 30-second test. Visualizes weekly/monthly trend reports and sends 'neurology visit recommended' alerts when suspicious patterns are detected. Data can be exported as PDF for submission to doctors at the first visit.
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 (79%)
Data Availability
24.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 (50/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
Frontend [medium]
Backend [low]
AI/ML [low]