Run the breeding calendar, the ration record and the component and culling numbers behind them — the herd manager decides, and the veterinarian's prescription and feed directive stay untouched.
A pregnancy check runs, and the agent posts the result against the cow, the service sire and the breeding date.
02
A ration is mixed, and the agent reconciles the batch sheet against the ration the nutritionist approved.
Reason
03
A sire list lands, and the agent screens both parents for the CDCB haplotype codes before a mating is proposed.
04
A genetic report spans April 2025, and the agent re-expresses both sides on the base CDCB moved that month.
05
A test day closes, and the agent trends components against the Net Merit weights as revised in 2025.
Decide
06
An official SCC sample posts, and the agent counts how many of the last five sit above the PMO limit.
07
A VFD is on file, and the agent tracks its expiry and the durations FDA's February 2026 guidance asks sponsors to add.
Out
08
A cull list is drawn, and the agent reconciles genomic merit against the pregnancy inventory behind it.
09
Execute write actions only inside the approval boundaries agreed during implementation.
→Product statement
The agent models and schedules; the herd manager decides, and a veterinarian prescribes, signs the feed directive and diagnoses.
Example workflow
One breeding group, record to approval
AgentHuman
1Herd record receivedParlour data, pregnancy check, test-day file or feed batch sheet
2Context assembledPregnancy inventory, the ration on file, component history and the prescribed protocol, each with its source
3Recommendation draftedBreeding list, ration note, component trend and confidence
4Controls appliedLabel-interval checks, haplotype screens, index-revision checks and confidence threshold
No human action required
Stages 1 to 4 run unaided, and nothing is bred, mixed or shipped at any of them — the agent is modelling, and the manager's lane opens at the confidence gate.
5DecisionBranches at the confidence threshold
High confidence
Goes to the herd manager to approve.
Low confidence
Adds a nutritionist or breeding-adviser read first.
Manager approval
The recommendation is held with its source records, its flags and the confidence.
Approve · Edit · Send to the adviser
Approved — released to the pen▼
6Herd software updatedOnly where write access and approval policy allow it
7Outcome evaluatedManager edits, conception outcomes, component movement and corrections after the group was bred
Edits
Every manager edit is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Designing or altering a synchronisation protocol.
Prescribing or ordering a reproductive hormone.
Issuing, extending or amending a feed directive.
Diagnosing mastitis or any other disease.
Automation boundaryAgent acts unaided
✓Build the breeding calendar and the eligible cow list for the herd manager.
✓Track the ration on file against what was mixed.
✓Trend components, cell counts and feed efficiency.
✓Flag what the herd manager should weigh, and hold the decision for review.
Any write happens inside the boundaries agreed at implementation, never ahead of approval.
Clearing milk or a cull cow after a withdrawal.
Approving the ration before it is fed.
Adding or changing a medicated article.
Changes to protocol, ration or approval rules.
Example output
One breeding recommendation, annotated
Everything the agent proposes is attached to the record it was drawn from.
Herd-production output · single animalIllustrative example
Animal
Recommendation
Days in milk
Source of record
Confidence
Attribution
Second-lactation cow
Eligible for the next timed-AI group on the protocol as it was prescribed
92 DIM
Pregnancy check on file
89%
Herd manager and named veterinarian
As receivedTaken from the pregnancy check and the breeding log — nothing on this side is written by the agent.
Source records usedPregnancy-check resultBreeding and service logPrescribed protocol
Why this animalShe is eligible on the protocol as prescribed — the call the manager makes.
ActionApproveEditSend to the adviser
What the score decidesBelow the configured threshold the recommendation picks up a second read.
Value
Where AI adds value
The same four claims, placed at the point in the workflow where each one applies.
Where the value landsValue 01 – 04
Every animalFrom the herd record
03Modelling
Model from the record
Draw on the herd records and the protocol, ration and index rules configured for the operation.
01Approved path
A protocol is a prescription
Routine breeding lists and ration checks arrive already worked.
02Human review
Send the manager to the decisions
Label conflicts, carrier matings and rising cell counts are marked and handed on — production is modelled here, disease is not.
04Build an evidence trail
The decision, the record it was drawn from and the herd manager who approved it stay on the animal.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
A herd-level pregnancy rate can look acceptable while a few pen cohorts absorb most of the rework sitting behind it. Nestack reports the manager-edit rate by slice, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
First-lactation breeding groups
5.7%
3.8×
Review
Fresh pens on a new ration
3.1%
2.1×
Review
Purchased replacement heifers
2.4%
1.6×
Watch
Established mid-lactation pens
1.5%
1.0×
Normal
Bar: manager-edit-rate lift vs. the established-pen baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
Every cycle ends with a new case
A cycle is closed when the wrong breeding call is a case the next release must survive. That suite is what the next group bred is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Manager-edit rate rises in a pen slice.
02Diagnose
The heifer that was bred to the wrong bull is walked back through the sire file until the cause narrows to one.
03Improve
The change leaves with a version on it and the groups that found it attached.
04Verify
The release stays shut while any touched protocol case is still red.
05Learn
It is held permanently, and the ration rules shift with it.
Learn → DetectThe return edge. The next group is worked against a suite one case longer.
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, production workflow, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Production-workflow discovery and decision boundary scoping.
02Herd, milk and genetics source assessment.
03Protocol, ration and genetic-index rule mapping work.
04Herd-record ingestion and normalisation.
05Modelling logic and record binding.
06Confidence scoring and decision routing.
07Herd manager approval workflow.
08Herd-software and feed-system integration.
09Breeding and ration cases.
10Guardrails and approval controls.
11Animal-trail instrumentation.
12Deployment, documentation and Agent Care handover.
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallelFinal 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 tierPilotOne site, one speciesProductionProduction herd systemsAdvancedMultiple sites / species
Introduced at Pilot
Modelling to your records and rules✓✓✓
Manager approval✓✓✓
Decision-accuracy baseline✓✓✓
Introduced at Production
Reporting by pen—✓✓
Approval workflow in your systems—✓✓
Approved write-back—✓✓
Herd-software integration—✓✓
Introduced at Advanced
Multi-site ration and label rules——✓
Multi-stage production approvals——✓
High animal count——✓
Multi-site production controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, workflow complexity, herd size, approval controls and deployment requirements.
Separate from buildBuild 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 bringWe build with it
01Your herd records and pen structure→Herd-record ingestion and mappingWeek 1
02Representative breeding and ration history→Modelling baseline, rule extraction and record bindingWeek 2
03Your protocol, ration and index rule sources→Protocol, ration and index rule mappingWeek 1
04Access to relevant APIs, feeds or exports→Herd, milk and genetics assessment, then integration setupWeek 2
05Decisions you would not want acted on→Protocol cases and failure-mode testingWeek 4
06What no protocol change may skip→Confidence scoring, decision routing, guardrails and approval controlsWeek 3
07Named herd managers to review recommendations→Manager approval workflow, then pilot and production validationWeeks 5–6
Nothing else is requiredDeployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
The phases are drawn to the weeks they occupy, and week 5 genuinely runs two things at once.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Production workflow discovery, rule mapping and the automation boundaryW2Herd, milk and genetics integration and the modelling baselineW3Production workflow, confidence logic and manager-approval controlsW4Evaluation suite, label and carrier checks and failure-mode testingW5Feed-system integration, pilot pens and targeted correctionsW6One breeding cycle run under the herd manager, then Agent Care handover
Reading the bandA bar covers the weeks its work is named in, and nothing else. The week 5 overlap is real, not padding.
At the end of W6The last checks clear on live groups and Agent Care picks up monitoring.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Agriculture AI agent
Build a herd production agent around your records and your advisers.
Show us your herd records, your ration on file and who signs off. Not another opinion on the protocol. A calendar built to the label your veterinarian prescribed, and a call that stays with your manager.
