Simply Health

The practice was running with three accumulated frictions:

• Hundreds of patients in a single document, with significant time lost finding the right one before each consultation.
• Manual onboarding for every patient. A repetitive task done every time a new patient came in.
• Menus drafted by hand, with no recipe or food database behind them.

Non-negotiable client requirement: stay inside the Google ecosystem.

Three architectural decisions shaped the project:

• External shared database + one document per patient. Recipes and foods (with macros, portion ranges and types) live in a single Sheets file. Each patient has their own document that pulls from that base. Updating a recipe ripples through every patient with no data duplication.
• Everything in one place. Stay inside the Google ecosystem.
• Patient follow-up. A single document to track each patient's progress, outstanding payments and most recent menu.

Phase 1. Structuring the recipe database Recipes lived as free text: "100g of sirloin OR tenderloin + 250ml of gazpacho". An extraction prompt and an Apps Script pipeline were designed to convert free text into structured JSON in batches (ingredients, quantities, units, option splits). Manual review only on the borderline cases the system flagged.

Phase 2. Weekly menu generator Engine that combines: the patient's target kcal (from their personal calculator) × distribution per intake × food exclusions × recipe base. Scales each ingredient's quantity respecting the racionMin / racionMax ranges set by the nutritionist. The full menu is written, formatted, into the patient's template.

Phase 3. Practice management system

• Automatic onboarding from a Google Form: folder creation + template copy + linking.
• Manual onboarding from the sheet (for in-person patients who don't fill in the form).
• Tiered pricing system managed from the PRECIOS tab.
• Dashboard tracking payments and sessions.

Operational recipe base: +500 structured recipes, queryable and usable by the menu engine.

Patient onboarding: from a multi-minute manual task to fully automatic after a form submission (or one click from the sheet for manual entries).

Full weekly menu generated in a single run, adjusted to the target calories within acceptable deviation ranges.

Self-managed pricing and bundles: the nutritionist updates rates without a developer in the loop.

Two-document architecture: changing a recipe or a food updates every patient without duplicating data or opening 50 files.