The nutrition-coaching SaaS I built solo and run: a patient mobile app, a coach web app, and alerts when a client drifts between sessions.
Outcome
Own product, in production
Compliance
Built to HIPAA requirements
Integration
API-First
Delivery
Founder-led
MealCircle is my own product, not a client engagement. I designed, built and operate it as the sole engineer, and it is the system I point to when someone asks whether I have shipped healthcare software end-to-end myself.
What it is
A retention-first clinical nutrition SaaS for dietitians and nutrition practices. Coaches lose clients between sessions because nothing keeps the client connected to their care plan between appointments. MealCircle is that layer: meal logging and progress tracking in a mobile app for patients, and a web app for coaches with the client's adherence trend, messaging, and alerts when someone is falling off.
Why retention-first changes the data model
Most nutrition apps model meals. MealCircle models adherence: each log entry is a data point on the relationship between what the coach recommended and what the client actually did. That is what lets the platform score adherence over time and surface drifting clients to the coach before the next session, rather than after a no-show.
Architecture
What it proves for a client build
The same patterns I use on client platforms were exercised here under my own name: tenant isolation, audit logging, managed infrastructure that keeps operations small enough for one engineer, and billing built early instead of "later". The technical write-ups are in the MealCircle articles under insights.
No. MealCircle is my own product. I designed, built and operate it as the sole engineer.
Dietitians and nutrition practices. Patients log meals and progress in a mobile app; coaches use a web app with each client's adherence trend, messaging, and alerts when someone is falling off.
It has been multi-tenant from the first migration: every table carries the practice identifier, and PostgreSQL row-level security enforces isolation in the database, not just in application code.
Google Cloud, built to HIPAA requirements: Cloud SQL for PostgreSQL with Cloud KMS encryption at rest, Cloud Audit Logs and Secret Manager, with Stripe for subscription billing.
I architect systems like this for healthcare operators and SaaS founders. Let's talk about your specific stack and requirements.
Book a Call