Nutrition practitioner software
Publish the plan. Let Lumo run inside it.
Lumo is built for clinics where the practitioner owns the client relationship. The practitioner creates and publishes the care plan; Lumo uses that plan to generate meals, answer routine questions, and surface exceptions.
What Lumo is built to support
Lumo is not a general chat layer. It is a practitioner-led workflow: invite client, publish care plan, maintain rolling meals, support check-ins, and monitor alerts.
Practitioners define the goals summary, calorie target, macro targets, planner notes, and operating boundaries for AI support.
Clients accept a clinic invite, add profile fields, and capture taste and cooking preferences.
Lumo maintains a rolling meal buffer, handles swaps, and tracks eaten, skipped, or modified meals.
Practitioners review alert categories instead of approving every generated meal.
Daily support stays grounded in practitioner judgment.
Meals can auto-publish when they stay inside the harness. Non-compliant or unstable outputs become regeneration work or practitioner alerts instead of routine client support.
Bring the plan into daily life.
Join the waitlist for clinic-first nutrition software that reduces routine workload without replacing practitioner judgment.
Join waitlist