Project status
The system is being rebuilt as one platform: customer sign-up, the client portal, menus and preps, and the team's daily tools. It is built stage by stage on a test copy loaded with real data, with review, testing, and feedback shaping each stage. The current app keeps running unchanged throughout.
and your data
client portal
workspace
automations
and enhancements
What is already working, on the test copy
- The new customer sign-up, the piece this project started with: inquiry, agreements, deposit, groceries, and preferences, ending in the portal. Your feedback from our July 13 call is built in. The notes you sent after that are logged item by item; those changes come later.
- The client portal: what a customer sees. Their menus, preferences, household details, and visits. Past menus fill in as the repair below completes.
- Your data, loaded: households, members, preferences, plans, invoices, and 10,593 meal preps for your active clients. The screens above run against these records.
- Prep tracking that keeps its history. Every prep records each step as it happens (menu submitted, menu email sent, approved, FD order placed, report submitted, completed), and its status is read from those steps. So a status can no longer reset on its own: an FD order placed before the Thursday deadline stays visible after the deadline passes.
- The prep page: the team's screen for one prep. It shows where the prep stands and what happens next, and from now on records who did what and when. Steps can be recorded and undone right there.
What we are doing right now
Repairing the menu history. Most dishes on past menus came over from the current app without their details. The full recipe library is intact in the current app, 37,206 recipes including each household's custom versions, so we are pulling it over and re-linking every past menu to its real dishes and ingredients. Anything that cannot be matched with certainty goes to a review list for a person to settle. None of this touches your live app.
This is the foundation for the next stage: once every dish knows its ingredients, the system can check any menu against a household's allergies and preferences.
What comes after
- Menu safety. Every menu is checked against the household's allergies and preferences, and anything flagged goes to a person to review and approve.
- The team's daily views. An Inbox that shows what needs attention, a Week view of upcoming preps, and the client pages. Each person lands on the view that fits their role.
- The items from your lists. Separating a true allergy from a strong preference, compound ingredients, curated shared menus, the payroll export, and messaging from the portal. Plus editing a weekly service in one place, instead of separate popups.
- The routine automations. Menu send, approval reminders, invoices, the chef recap, and reports.
- Look and feel, refined once the behavior is right.
- Review, testing, and feedback. Each stage is reviewed and tested with your team, and enhancements from that feedback are added to the plan.