Plan loads against harvest and delivery windows, book from an approved carrier and rate list, track in transit and reconcile the invoice — with welfare, food-safety and hours rules held by a person.
Take the loads to move — commodity, quantity, origin and destination, and the window each one has to hit.
02
Read the approved carrier list, the contracted rate table, the equipment available and the appointment calendar.
Reason
03
Match equipment to the commodity — hopper, reefer, live-haul, flatbed — and to what the loading site allows.
04
Plan the run against hours rules, the agricultural exemption's radius and season, permits, weights and route restrictions.
05
Apply the commodity's temperature spec, pre-cooling and record path, or the journey plan a live-haul needs.
Decide
06
Hold any load whose plan leans on an exemption, permit or welfare limit that does not clearly apply on that leg.
07
Hold any carrier that is not on the approved list, or whose authority, insurance or identity does not verify.
Out
08
Tender to an approved carrier at a contracted rate, book the appointment and track the load against it.
09
Reconcile the freight invoice to the rate and the accessorials, and put every difference in front of a person.
→Product statement
The agent plans, books, tracks and reconciles. Carrier approval, any exception to a welfare or safety rule, and every payment stay with a person.
Example workflow
One load, end to end
AgentHuman
1Load requestedThe commodity, the quantity, the origin and destination, and the window it has to hit
2Plan builtEquipment matched to the commodity, then hours and exemption radius, permits, weights and route restrictions
3Requirements attachedThe temperature spec, pre-cooling and the record path, or the live-haul journey plan, density and rest
4Carriers checkedApproved list, contracted rate, and authority and insurance verified at source rather than from the paperwork sent
No human action required
Stages 1 to 4 run before anyone is asked to look — planning, load requirements and carrier checks finish first. A carrier that will not verify, or a plan leaning on an exemption, ends the stretch there and then.
5DecisionSplits on an approved carrier, a clean plan and confidence
Approved carrier, plan clean
Tenders at the contracted rate.
Unverified carrier, or a rule in doubt
Goes to the logistics lead first.
Logistics lead
Reads the plan, the carrier's authority and insurance, the exemption or permit in question and the rate, then approves the carrier or the exception.
Approve carrier · Amend the plan · Reject
Approved — handed back▼
6Tendered, booked and trackedTendered at the contracted rate, the appointment booked and the load tracked against the plan
Every carrier approval and every rule exception is recorded against the load.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Approving a carrier or adding one to the list.
Deciding an hours exemption applies to a leg.
Signing off a permit, route or weight exception.
Accepting a livestock journey outside the welfare limits.
Automation boundaryAgent acts unaided
✓Plan loads against harvest, delivery and appointment windows.
✓Match equipment to the commodity and check hours, weights and the route.
✓Tender to carriers already approved, at rates already contracted.
✓Track the load, collect the records and reconcile the invoice.
Write actions stay inside the boundaries agreed in implementation: approved carriers, contracted rates, and a tender the logistics lead can pull before pickup.
Judging a temperature excursion acceptable.
Releasing payment on a freight invoice or accessorial.
Agreeing a detention, demurrage or damage claim.
Changing rate tables, carrier lists or booking rules.
Example output
One load plan, annotated
Everything the agent proposes is attached to the load, the rate line and the checks it came from.
Freight output · single loadIllustrative example
Load
Lane
Window
Tendered to
Confidence
Temperature
Chilled produce, 20 pallets
Packhouse to a retail DC
Tue 06:00 slot
Approved carrier — verified
92%
Spec set, records due
As receivedThe load, the lane and the window as the order and the appointment calendar hold them.
Evidence usedAuthority and insuranceContracted rate linePre-cool and spec
Why this carrierIt is on your approved list, and its authority and insurance were read at source.
ActionApprove carrierAmend the planReject
What the score decidesConfidence decides how much of the plan a person re-reads, not whether a rule applies.
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 load to moveFrom the order, the harvest plan and the schedule
03Plan & carrier
Apply the rules that govern the run
Use the approved carrier list, the contracted rates, the hours, permit and weight rules, the temperature spec and the welfare limits for that journey.
01Approved path
Settle the plan while it can still change
Equipment, hours, permits and the appointment are worked out before the truck is loaded, not while it is standing at a gate with a crop on it.
02Human review
Put a person on the loads that carry risk
A carrier that will not verify, an exemption that does not fit the leg, a journey that breaks a welfare limit — those reach the logistics lead instead of a carrier.
04Build an evidence trail
Retain the plan, the carrier check, the permit and exemption reasoning, the temperature record, the appointment and the invoice match — on both paths.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Most of the failures sit in a few weeks of the year
A load-exception rate that reads tolerably across a season sits mostly in harvest weeks, in temperature-controlled freight and on carriers nobody has moved with before. Nestack reports performance by slice, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Harvest-peak spot loads
7.0%
3.8×
Review
New and one-off carriers
5.1%
2.8×
Review
Reefer and temperature-controlled
3.5%
1.9×
Watch
Contracted lanes, repeat carrier
1.5%
0.8×
Normal
Bar: load-exception rate lift vs. contracted-lane baseline · scale 0–4.0× · tick marks the 2.0× threshold2 of 4 slices over threshold
Evidence-linked improvement
A load already moving is fixed on the road, not in the loop
A truck under load cannot wait for a root cause. It is re-iced, re-routed or re-booked first — the loop only decides what next week's planning is built on.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
A lane is the unit: exceptions, missed windows and invoice differences counted against it.
02Diagnose
The rate table, the carrier check, the rule set and the tracking feed are read apart until one owns it.
03Improve
Nothing ships until the logistics lead signs the corrected rule, list or rate line, version stamped.
04Verify
Recorded loads from that lane run through again, the ones that failed among them.
05Learn
The load joins the regression set, and the booking runbook is rewritten before the next season.
Learn → DetectThe return edge. A welfare limit, a temperature spec or a carrier list is not the agent's to change — a person signs it before a load runs on it.
Typical build scope
Twelve workstreams across six weeks
The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, rates and rules, planning and tendering, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Workflow discovery and automation-boundary definition.
02Freight-system and carrier-list assessment.
03Hours, permit and welfare rule mapping.
04Commodity-to-equipment matching rules.
05Order, load and appointment ingestion.
06Load planning and delivery-window logic.
07Carrier verification and tendering workflow.
08Temperature spec and live-haul rules.
09Rule-conflict and carrier-verification evaluation.
10Invoice and accessorial reconciliation.
11Tracking, appointment and record integration.
12Observability, deployment 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 lane, one commodityProductionProduction freight integrationAdvancedMulti-site / multi-commodity
Introduced at Pilot
Load planning against windows✓✓✓
Tendering to approved carriers only✓✓✓
Carrier approval left with a person✓✓✓
Baseline evaluation✓✓✓
Introduced at Production
Carrier authority and insurance checks—✓✓
Rule-conflict, permit and weight checks—✓✓
In-transit tracking and appointments—✓✓
Invoice and accessorial reconciliation—✓✓
Observability and evaluation—✓✓
Temperature and live-haul requirements—✓✓
Introduced at Advanced
Multi-site and enterprise controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on lanes and commodities, freight and carrier-data integrations, load volume, rate and accessorial complexity, 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 approved carrier list and contracted rate tables→Freight-system, rate-table and carrier-list assessmentWeek 1
02The rules you work to — hours, permits, weights and welfare→Hours, permit, weight and welfare rule mappingWeek 1
03What each commodity needs from equipment and a site→Commodity-to-equipment and site-constraint rulesWeek 2
04Access to order, appointment and tracking feeds→Order, load and appointment ingestion, then trackingWeek 2
05Loads that went wrong, including the near misses→Evaluation suite, regression cases and failure-mode testingWeek 4
06A year of freight invoices with the disputes attached→Invoice, accessorial and detention reconciliationWeek 5
07A named logistics lead to approve carriers and payments→Carrier-approval workflow, then pilot loads and validationWeeks 5–6
Nothing else is requiredDeployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
Phases are drawn over the weeks they actually occupy. Week 5 carries both the invoice reconciliation and the first supervised loads.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Workflow discovery, the rule set and the automation boundaryW2Rate tables, carrier lists, and order and appointment feedsW3Load planning, window logic and the tendering workflowW4Rule-conflict, permit and carrier-verification testingW5Tracking and invoice integration, then supervised loadsW6Your desk books from live plans, then Agent Care starts
Reading the bandCarrier verification and rule-conflict checks are tested in week 4, before a load is tendered on them in week 5.
At the end of W6Plans have been booked alongside your existing desk and checked against your own invoices, then Agent Care takes over monitoring.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Agriculture AI agent
Build a freight agent around your lanes and your carrier list.
Show us a season of loads, your rate tables and how a carrier gets approved today. We'll replay those loads and show you which plans broke a rule, which carriers would not verify and which invoices you paid twice.
