The plan is twenty minutes. The eleventh plan is a Sunday.
Software for nutrition coaches usually solves the wrong end of the problem: it counts food a client has already eaten. The expensive part of the week is upstream of that — writing eleven plans that respect eleven sets of calories, preferences, allergies and schedules, and then reading eleven diaries to work out what to change.
The week you actually have
Eleven clients on plans, two of them vegetarian, one with a nut allergy, all of them due a review this week.
Every plan is a constraint problem
A target, a set of macros, a list of things they will not eat, a budget, and a week that has three evenings out in it. Solving that by hand is the job, eleven times.
Diaries are unreadable at volume
What you need is the pattern across a fortnight. What you get is a list of entries, and finding the pattern means reading all of them.
Restrictions must never be forgotten
A preference that goes missing is annoying. An allergy that goes missing is a serious incident, and it is one edit away in any system where the constraint is not part of the record.
What this changes
Three specifics, rather than a feature list
Plans drafted against the profile, not a template
Calories and macros for that client, with their restrictions and preferences applied, written as meals rather than as a spreadsheet of numbers.
Restrictions live on the client
Allergies and exclusions are part of the client record rather than a note in a message thread, so they are applied to every draft rather than to the ones you remember.
Progress, as a line rather than a list
Weight, measurements and check-ins over time, charted — and read, so a plateau is something the operator raises rather than something you spot late.
What is actually generated
A first draft: a week of meals that hits the client’s targets, avoids what they cannot or will not eat, and looks like food rather than like a macro calculator’s output. It is written from their profile, their history, and what they said at the last check-in.
It is a draft in the strict sense — it exists in the product, labelled as AI-drafted, and it does not reach the client until you assign it. Coaches change something on most of them, which is the point: the twenty minutes you would have spent typing goes into the two decisions that matter.
Allergies, and why they are a field
The reason restrictions are stored on the client record rather than kept in your head or in a thread is that everything downstream reads from the record. A draft plan, a substitution, a shopping list and a reminder all apply the same constraint, and none of them depends on somebody remembering to reapply it.
A constraint that lives in a message is a constraint that is one busy Tuesday from being missed.
Where the coaching stays yours
No plan is assigned automatically, no message is sent to a client without your approval, and nothing here gives clinical advice. If a client’s situation needs a dietitian, that is a referral you make; the software’s job is the repetitive middle, not the judgement at either end.
The rest of the coaching business
Enquiries, follow-ups, packages, renewals and invoices sit in the same product as the plans — so a client whose block ends in a fortnight is a renewal the operator has already drafted rather than a lapse you notice a month later.
The client sees their own portal: their plan, their check-ins, their progress and their invoices, in a browser, without an app.
Questions people ask about this
How does it handle allergies and intolerances?
They are fields on the client record, and every draft applies them. That is a deliberate structural choice rather than a feature: a restriction kept in a chat thread is one that eventually gets missed.
Does it calculate calories and macros itself?
It works from the targets on the client’s profile, which you set. It will draft meals that hit them; it will not decide what somebody’s target should be, because that is the coaching.
Is the food database exhaustive?
Plans are written as meals and portions in your words rather than pulled from a food-database lookup, which is more flexible and less precise. If your practice depends on gram-accurate database entries, this will not replace that tool.
Where does a client’s health data live?
In your workspace, isolated per workspace at the database level, visible to you and to that client. It is not used to train anything, and the privacy policy sets out exactly what is processed and by whom.
Last reviewed on . Something out of date or wrong? Tell us and it gets fixed.
À lire ensuite
Give it one client and read the first draft.
Add a client, fill in their goals and restrictions, and NeoAI writes the opening training week and the meals to match. You edit it before anybody sees it.