Hey IH first milestone post for my next bet.
Tide: adaptive nutrition coach for Apple Watch. The thesis is that every nutrition tracker treats the body as static same calorie target whether you slept 4h or 9h. Apple Watch already collects HRV, sleep stages, wrist temp, training load. Almost no nutrition app uses it to adjust anything.
I'm in a 14-day validation phase before writing a single line of Swift. The goal is NOT to ship code. The goal is to either prove people will pay or learn fast that they won't. Day 14 is GO/PIVOT/KILL.
What I've shipped so far (Day 1-3):
Validation hypotheses (need 4 of 5 to GO):
H1: ≥60% of interviews cite ≥2 frustrations with current apps
H2: ≥70% spontaneous positive reaction to the pitch
H3: ≥30% mention WTP $5-7/mo unprompted
H4: 100+ waitlist within $130 spend
H5: ≥5 founder commits at $49
Will post weekly with progress. Brutal feedback always welcome — that's why I'm here.
Smart to force a GO/PIVOT/KILL decision before writing code. I’m in the nutrition tracking space too, and the two complaints I keep hearing are price creep and bad food recognition. That is exactly why I built MetricSync: cheaper than CalAI, more features, better accuracy, and a 3 day free trial so people can test it before committing. Curious whether your interviews are surfacing the same pain points, or if the Apple Watch angle changes the buying trigger.
Most nutrition apps ignore daily body changes, so building a coach that adapts to Apple Watch data is a clever way to solve the static calorie problem. Sticking to a strict 14-day validation phase before writing any Swift code is a smart way to ensure there is real market demand. Have you found that people are more excited about the sleep-syncing or the training load adjustments during your interviews?