Audited a $602 MRR meal-planner SaaS — the real product is a clinical dataset he didn't k

Audited a health-vertical SaaS this week. Backend dev, no nutrition background, $602 MRR in 60 days on $89/mo costs. The operator thinks he sells a meal planner. He's actually running a clinical dataset business with a meal planner glued to the front. Sharing the dissection because the actual lesson is not what the operator thinks it is.

What he built

His dad got diagnosed Type 2 diabetes. The doctor handed over a generic 8-page PDF from 2019. He's a backend dev, so he built the thing on weekends.

• 86 paid users at $7/mo → $602 MRR by day 60
• $89/mo fixed cost (OpenAI). Vercel hobby + Supabase free, $0 hosting
• 23% trial-to-paid (was 18% before he added an "ADA 2025 guidelines" banner)
• 4% monthly churn, ~85% gross margin
• 80 hours of build, spread across 8 weekends
• One r/diabetes post → 200 trial signups → 67 paid

The stack is boring: Next.js + Supabase + Stripe + OpenAI + Resend. Nothing on that list is an edge.

The training-grade lesson

Most people read this case and think "AI health is hot, ship a meal planner." That's the wrong takeaway.

The product isn't the meal plan. The product is the glycemic response dataset the meal plan extracts while users think they're getting recipes. Every $7 subscriber logs 30+ glucose readings a week, tagged to a meal, an HbA1c band, an age, a carb target. That's a cohort Levels Health spent over $300M trying to build with hardware CGMs. He's building it through self-report and a Stripe account.

Map this to our world. We obsess over content depth, EMD, DA, internal links, AI-overview survival. None of it is a moat in 2026 — GPT clones a review page in an afternoon. What most niche site builders never build is the proprietary data layer underneath: which products our readers actually keep vs. return, what they report back six months later, which use-case they had before they clicked the affiliate link out. The SERP can't see any of that. A scraper can't either.

A review page is content anyone can copy. A dataset of what your readers actually keep is a moat that compounds.

Try this yourself this week

Pick your strongest niche site or review page and ask:

1. What structured data am I collecting from visitors that no other site in my vertical has?
2. If I emailed my best 100 readers tomorrow, what specific outcome could I ask them to report back?
3. What small free tool — calculator, fit-checker, comparison quiz — could I ship that captures one structured input per visitor, not just an email?

If your answer to #1 is "Google Analytics," you don't have a moat. You have what every other affiliate in your niche already has, anonymized and aggregated.

Bottom line

The operator thinks his next move is a Spanish version, a white-label deal, or doubling the price. None of that is the moat. The moat is two years of meal × biomarker × outcome data no one can backfill.

For us, the equivalent is straightforward: stop trying to out-publish the AI-content factories. Build the small data layer underneath your site that they can't replicate. They'll out-write us. They can't out-collect.

Want the next one?

I dissect one of these every weekday — micro-SaaS, niche-site, and AI-product cases pulled apart for the actual lesson, not the surface story. Full dissections with the steal-the-playbook bits I cut for length here. Check my profile if you want the longer version. WA members can lock in the founding rate on the way in.

What kind of business do you want me to dissect next?