Sports & Fitness AI agent · Nutrition
Nutrition-Guidance AI Agent
Answer general nutrition questions from a configured library, suppress the topics that must not be answered at all, and route individualised or clinical questions to a named dietitian.
- Typical delivery
- 4–6 weeks
- Deployment
- Your stack
- Named dietitian
- General only
- After launch
- Agent Care
What this agent does
Gives information, not a prescription
In
- 01
Ingesting the configured nutrition library, the club's referral list and whatever the member has logged.
- 02
Normalising each logged entry against the food database, and carrying it forward with its source.
Reason
- 03
Screening each question for eating-disorder, clinical and doping topics first.
- 04
Drafting general information, meal ideas and macro ranges from the approved library.
- 05
Checking the member's configured state against the dietetics licensure rule set held for that state.
Decide
- 06
Suppressing out-of-scope topics rather than answering them more carefully.
- 07
Holding anything individual or product-specific for the named dietitian.
Out
- 08
Retaining the suggestion, the profile it was drawn against, the referral offered and the edits made.
- 09
Execute write actions only inside the approval boundaries agreed during implementation.
Product statement
The agent supplies general information; the named dietitian decides anything individual, and the operator answers for what is said.
Example workflow
One question, intake to referral
- 1Member question receivedMember app, kiosk, coach hand-off or a logged food entry
- 2Context assembledLogged entries, the configured state, flags on the member record and the referral list
- 3Suggestion draftedGeneral information, meal ideas, scope notes and confidence
- 4Controls appliedTopic screening, scope checks, state licensure rules, supplement suppression and confidence threshold
No human action required
Stages 1 to 4 run unaided, and nothing individual leaves at any of them — the agent answers generally, and the dietitian's lane opens at the gate.
Goes to the club dietitian to release.
Adds a scope review first.
Dietitian review
The suggestion is held with the profile it was drawn against and the confidence.
Release · Edit · Refer to a professional
Released — sent to the member
- 6Member app updatedOnly where write access and approval policy allow it
- 7Outcome evaluatedEdit distance, referral outcomes, suppression hits and post-release corrections
Edits
Every dietitian edit is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required
8 items
- Medical nutrition therapy for a disease or condition.
- Recommending a supplement product to a tested athlete.
- Engaging a member flagged for disordered-eating risk.
- Setting an individual calorie target or rate of loss.
Automation boundary
Agent acts unaided
- ✓Answer general, population-level nutrition questions.
- ✓Suggest meals and recipes from the club's approved recipe set.
- ✓Return what the member logged and what the food database holds.
- ✓Offer the club's configured referral into a qualified.
Any write happens inside the boundaries agreed at implementation, never ahead of review.
- Nutrition for pregnancy, postpartum or under-18 members.
- Reading a blood result, a scan or a clinician's letter.
- Adapting a plan where the state requires prior sign-off.
- Changes to scope, referral thresholds or the state rules.
Example output
One suggestion, annotated
Everything the agent suggests is attached to the profile it was drawn against.
Nutrition-guidance output · single member
Illustrative example- Member
- General member
- Suggested line
- A higher-protein breakfast from the club's approved recipe set
- Basis
- Recipe card
- Drawn from
- Configured library
- Confidence
- 91%
- Scope
- General information only
As received
Taken from the configured library and what the member logged — nothing on this side is composed by the agent.
Sources used
- Approved recipe set
- Member's logged entries
- Club referral list
Why this stays general
It describes food in general, not this member's requirement — the line the dietitian weighs.
What the score decides
Below the configured threshold the suggestion picks up a scope review before it.
Action
ReleaseEditRefer to a professionalValue
Where AI adds value
The same four claims, placed at the point in the workflow where each one applies.
Where the value lands
Value 01 – 04
Every question
From the member
Answer from the library
Draw on the configured library and the club's approved recipe set, and on nothing else.
General information, named so
Routine questions about food and macronutrients arrive already answered.
Send the rest to a person
Screened topics and low-confidence suggestions are held, so the dietitian's time goes where the risk sits.
Build an evidence trail
The suggestion, the profile it was drawn against and the referral stay on file.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Member management
- Mindbody
- Glofox
- ABC Fitness
- Xplor
Nutrition and food data
- Configured club library
- Food-composition databases
Member apps
- Club app
- member portal
- Logged food and activity
Agent
Nutrition guidance
- Reads the profile
- Answers generally
- Holds for the dietitian
Referral and clinical
- Dietitian rota
- referral list
- Practice-management systems
Observability & evaluation
- OpenTelemetry
- Langfuse
- Supported monitoring/evaluation sources
Integration availability depends on the client's existing systems and API access.
Agent controls
Six layers between the model and the member
Controls stack inward. What the stack does not catch is set out in the map below.
L6 · Outermost — last line of defence
Inward → L1 · closest to the model
- L1 – L2
- Test whether a suggestion may stand
- L3
- Puts the release in a dietitian's hands
- L4 – L5
- Keep what was suggested and what it was drawn from
- L6
- Narrows to logging-only when signals degrade
How Nestack evaluates it
Evaluate the workflow — a correct answer in the wrong context is still a failure.
Coverage runs the whole depth of the workflow, and every layer is cut by slice.
Surface — what the member reads
- E1Final-output evaluationDid the suggestion stay inside the library and general framing?
- E2Step-level evaluationDid the agent use the right profile, flags, library and state rule set?
- E3Tool evaluationDid it read the correct member record and write the correct field?
- E4Confidence calibrationDo low-confidence suggestions actually attract more dietitian edits?
- E5Slice evaluationHow does performance change across specific member profiles?
- E6Business outcomeHow many suggestions needed a dietitian edit or a correction after release?
Floor — the outcome the operator answers for
Failure modes
Where each failure originates in the agent
Seven failure modes, placed at the stage each one originates.
Agent lifecycle
Direction of processing →
01 · Retrieval
1 mode
- NU-03
Stale referral destination
A helpline on the referral list has since been disconnected.
Stage gathers
Library, recipe set, member flags and the referral list
02 · Reasoning
2 modes
- NU-04
Context-blind correct answer
Standard weight-control guidance is returned to a member at risk.
- NU-06
General information individualised
A population-level range is restated as this member's target.
Stage proposes
General information, meal ideas and confidence
03 · Tool / write
2 modes
- NU-02
Suppressed topic answered
A screened question is answered instead of being held.
- NU-05
Product named to a tested athlete
A named supplement reaches a member subject to testing.
Stage writes
Only where write access and approval policy allow it
04 · Output
1 mode
- NU-01
Scope line crossed
The reply reads as advice for this member's body and goals.
Stage returns
The suggestion the dietitian releases and
05 · Change / Version
1 mode
- NU-07
Silent scope regression
A model or library change widens what the agent will answer.
Stage tracks
Model, prompt, library and state rule set
- Sev-1 · a suppressed topic is answered
- Sev-2 · individual advice reaches a member
- Sev-3 · source degrades, suggestion routes to review
Affected slices
Overall accuracy can hide one member cohort
Aggregate suggestion quality can look acceptable while a small number of member cohorts absorb nearly all of the missed referrals. Nestack measures the referral-miss rate by slice, not only in total.
Slice performance — reported separately, not only in aggregate
Illustrative example| Slice | Failure rate | Lift | Lift vs. threshold | Status |
|---|---|---|---|---|
| Disordered-eating flags | 6.3% | 3.6× | Review | |
| Tested athletes, supplements | 4.2% | 2.4× | Review | |
| Exclusive-scope states | 3.0% | 1.7× | Watch | |
| General members, no flags | 1.4% | 0.8× | Normal |
Bar: referral-miss-rate lift vs. the general-member baseline · scale 0–4.0× · tick marks the 2.0× review threshold
2 of 4 slices over threshold
Evidence-linked improvement
No cycle closes without a new test
An apology does not close a cycle; a case the next release must pass does. That suite is what the next suggestion leaving the agent is measured against.
Improvement cycle · five stages
Switchback — the path turns at Improve and returns at Learn
- 01
Detect
Referral-miss rate rises in a member cohort.
- 02
Diagnose
Pull the suggestion and the profile it was drawn against, then read until one cause survives.
- 03
Improve
The correction is versioned, with the suggestions that motivated it attached.
- 04
Verify
A failing case holds the release until it passes.
- 05
Learn
The case is added permanently, and the referral thresholds move with it.
Learn → Detect
The return edge. The next detection is measured against a suite that just grew.
Typical build scope
Twelve workstreams across six weeks
The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, sources, guidance workflow, evaluation, integration, then production validation and handover.
Workstream
Week 1Week 2Week 3Week 4Week 5Week 6
- 01Nutrition workflow discovery and scope definition.Week 1
- 02Member-system and food-data source.Week 1, Week 2
- 03Library, referral-list and state rule-set mapping.Week 1, Week 2
- 04Member-record ingestion and entry.Week 2
- 05Guidance logic and library binding.Week 2, Week 3
- 06Confidence scoring and screened-topic routing.Week 3
- 07Dietitian review workflow.Week 3, Week 4
- 08Member-app and club-system integration.Week 5
- 09Referral-threshold cases.Week 4, Week 5
- 10Guardrails and scope controls.Week 4
- 11Suggestion-trail instrumentation.Week 5, Week 6
- 12Deployment, documentation and Agent Care handover.Week 6
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallel
Final scope and sequence confirmed in discovery
Engagement tiers
What each tier includes
Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.
| Capability✓ in scope · — not at this tier | PilotOne club, one library | ProductionProduction member systems | AdvancedMultiple brands / sites |
|---|---|---|---|
| Introduced at Pilot | |||
| General information from your library | ✓ | ✓ | ✓ |
| Dietitian release | ✓ | ✓ | ✓ |
| Suggestion-quality baseline | ✓ | ✓ | ✓ |
| Introduced at Production | |||
| Reporting by member profile | — | ✓ | ✓ |
| Release workflow in your systems | — | ✓ | ✓ |
| Approved write-back | — | ✓ | ✓ |
| Member-app integration | — | ✓ | ✓ |
| Introduced at Advanced | |||
| Multiple state rule sets | — | — | ✓ |
| Multi-stage clinical review | — | — | ✓ |
| High member volume | — | — | ✓ |
| Multi-brand programme controls | — | — | ✓ |
| Build price | From $5,000 | From $8,000 | Custom quote |
- Final build price
- Confirmed after discovery based on integrations, workflow complexity, member volume, approval controls and deployment requirements.
- Separate from build
- Build pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.
What we need from you
What you bring, and what we build with it
Each input maps to a piece of build scope and a week in the delivery timeline.
You bring
We build with it
01Your nutrition library and approved recipe set
→Library ingestion and source mapping
Week 102Representative member questions
→Guidance baseline, scope extraction and library binding
Week 203Your referral list and the professionals on it
→Referral-list verification and scope-boundary definition
Week 104Access to relevant APIs, feeds or exports
→Member-system and food-data assessment, then integration setup
Week 205Suggestions that should have been a referral
→Referral cases and the evaluation suite
Week 406Where general information has to stop
→Confidence scoring, topic screening, guardrails and scope controls
Week 307Named dietitians to review suggestions
→Dietitian review workflow, then pilot and production validation
Weeks 5–6
Nothing else is required
Deployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
Each band covers the weeks the work really takes, so week 5 carries evaluation and launch together.
Phase
W1
W2
W3
W4
W5
W6
- DiscoveryW1
- BuildW2 – W3
- EvaluateW4 – W5
- Pilot & LaunchW5 – W6
Week focus
W1Nutrition workflow discovery, scope mapping and the state rule set
W2Source integration and the guidance baseline
W3Guidance workflow, screening logic and release controls
W4Evaluation suite, suppressed-topic checks and failure-mode testing
W5Member-app integration, a pilot cohort and targeted corrections
W6A cohort of members supported under a dietitian, then handover
- Reading the band
- Each bar sits only on the weeks its work is named in. The fifth week genuinely carries two kinds of work.
- At the end of W6
- Validation finishes on live members and Agent Care assumes monitoring.
- Duration
- Six-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Sports & Fitness AI agent
Build a nutrition agent that stays on the general side of the line.
Show us your library, your referral list and the states you operate in. A dietitian you name signs anything individual, and the workflow is built around that signature.
- Typical delivery
- 4–6 weeks
- Deployment
- Your club systems
- Dietitian release
- General only
- After launch
- Agent Care available
Nestack Agents · Nutrition guidance
AGT-SF-04 · Agent Care available after launch