Platform BuildOwn Product

MealCircle: A Retention-First Nutrition Coaching SaaS

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

Overview

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

  • 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. Each practice is a separate covered entity, so a cross-tenant leak would be a breach regardless of cause.
  • Google Cloud, built to HIPAA requirements: Cloud SQL for PostgreSQL with Cloud KMS encryption at rest, Cloud Audit Logs enabled before the first user, Secret Manager for every credential, TLS everywhere, and a BAA in place with the cloud provider and every service that can see patient data.
  • Stripe subscription billing on a per-practice flat rate with usage-based add-ons, with subscription state reconciled from webhooks.
  • An EHR integration path designed around FHIR R4 rather than per-vendor connectors, so a practice's EHR can be connected when it exposes FHIR.

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.

Key Results

Shipped and operated end-to-end by one engineer
Retention signals surface drifting clients to coaches between sessions
Tenant isolation enforced in the database, not only in application code
Auth, billing and infrastructure on managed services so operations stay small

Frequently Asked Questions

Is MealCircle a client project?

No. MealCircle is my own product. I designed, built and operate it as the sole engineer.

Who is it for?

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.

How is each practice's data isolated?

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.

What does it run on?

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.

Services Delivered

  • Product design and full-stack build, solo
  • Patient mobile app and coach web app
  • Adherence and retention-signal data model
  • Multi-tenant PostgreSQL with row-level security
  • Google Cloud infrastructure built to HIPAA requirements (Cloud SQL, Cloud KMS, Cloud Audit Logs, Secret Manager)
  • Stripe subscription billing: per-practice flat rate with usage add-ons
  • EHR integration path designed around FHIR R4

Build this for your organization

I architect systems like this for healthcare operators and SaaS founders. Let's talk about your specific stack and requirements.

Book a Call

Need this built for
your clinical operation?