Build promotional offers from a written plan, test each one against the terms open to competing customers of like grade and quality, and stop what cannot be offered proportionally.
Customer, terms and volume data from the trade, ERP and sales systems, ingested as one set.
02
Field labels and customer hierarchies, normalised, each customer kept with the class it trades in.
Reason
03
The written promotional plan, read as the source every offer has to be generated from.
04
Proportionality on an objective basis — the volume or quantity purchased over a defined period.
05
Competing customers of like grade and quality, identified, so an offer can be tested against them.
Decide
06
Any offer that cannot be made available on proportionally equal terms, stopped rather than scored.
07
Every offer routed to the named trade approver, who decides what is put to a customer.
Out
08
The plan basis, the proportionality test, the approver and the offer, retained together.
09
Write actions executed only inside the approval boundaries agreed during implementation.
→Product statement
The agent generates offers from the plan and tests them; the named approver decides what is offered, and the seller stays responsible even where a distributor administers the programme.
Example workflow
One offer, plan to approved terms
AgentHuman
1Plan and terms receivedThe written promotional plan, customer terms and volumes from the trade systems
2Context assembledCustomer class, competing customers, purchase volume and the terms already offered
3Offer generatedOffer, plan basis and proportionality
4Controls appliedProportionality test against competing customers, notice checks, alternative-terms checks and confidence threshold
No human action required
Stages 1 to 4 run unaided, and nothing is offered at any of them — the offer is held, and the approver's lane opens at the confidence gate.
5DecisionBranches at the confidence threshold
High confidence
Goes to the trade approver to approve.
Low confidence
Adds a compliance read first.
Approver decision
The offer is held with its plan basis, its proportionality test and the confidence.
Approve · Amend · Send to compliance review
Approved — the offer may be made▼
6Trade systems updatedOnly where write access and approval policy allow it
7Outcome evaluatedProportionality outcomes, amendments, notice given and what performance was verified
Amendments
Every approver amendment is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Building an offer around a single named customer.
Deciding that a customer is not a competitor.
Paying an allowance without verified performance.
Setting a shelf price for an individual shopper.
Automation boundaryAgent acts unaided
✓Generate every offer from the written plan already in force.
✓Test each one against the terms open to competing customers.
✓Base proportionality on volume purchased over a set period.
✓Stop what cannot be made available, and hold it for approval.
Any write happens inside the boundaries agreed at implementation, never ahead of approval.
Rewriting the promotional terms the business set.
Ingesting a competitor's non-public price data.
Withholding notice of an offer from a customer.
Changes to the plan basis, thresholds or approvals.
Example output
One offer, annotated
Everything the agent offers is attached to the plan it was generated from.
Offer output · single customerIllustrative example
Customer
What was offered
Basis
Plan it came from
Confidence
Proportionality test
Independent grocer
Display allowance on a promoted chilled line
Volume purchased
The written trade plan
93%
Open to competing customers
As receivedTaken from the written plan and the customer's own purchase record.
Source terms usedWritten promotional planPurchase volume recordCompeting-customer list
Why this one passesThe same terms are open to competing customers of like grade and quality.
ActionApproveAmendSend to compliance review
What the score decidesBelow the configured threshold the offer picks up a compliance read before.
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 offerFrom the written plan
03Generating
Generate from the plan
Draw on the written plan, the customer's purchase volume and the terms already open to the customers who compete with them — never on a shopper's personal data, which some markets now restrict in food.
01Approved path
Proportional, or not at all
Routine offers arrive generated, with their plan basis already attached.
02Human review
Send the approver to the exceptions
If an offer was made and a competing customer says it never saw the terms, the file shows the plan, the test that was run and who approved it — which is the defence on either side of the sale.
04Build an evidence trail
The offer, the terms it was drawn from and the person who approved it stay on the customer file.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Break the offer book down by customer class before you read it: a rate that looks settled across the book can rest on one class that never saw the terms. Nestack reports the amendment rate by class, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Independent and small-format
5.2%
3.6×
Review
Distributor-administered offers
3.2%
2.2×
Review
Bespoke display and demo deals
2.2%
1.5×
Watch
Standard plan-based offers
0.9%
0.6×
Normal
Bar: approver-amendment-rate lift vs. plan-based-offer baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
A cycle closes on a case, not a fix
A cycle closes when the failure is a regression case the next release has to pass. That suite is what the next offer put to a customer is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Amendment rate rises in a customer class.
02Diagnose
If one class is amending more than the rest, the offers, the plan terms behind them and the tests they passed are read together until the cause narrows to one.
03Improve
The change ships against a version, with the offers that exposed it attached.
04Verify
Release is blocked until the affected regression cases pass again.
05Learn
The case joins the permanent suite and the trade playbook.
Learn → DetectThe return edge. The next offer meets 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, offer workflow, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Trade-promotion workflow discovery and boundary definition.
02Trade, ERP and sales-data assessment.
03Plan basis, customer class and proportionality mapping.
04Terms and volume ingestion.
05Offer logic and plan binding.
06Confidence scoring and exception routing.
07Approver decision workflow.
08Trade-system integration.
09Proportionality regression cases.
10Guardrails and approval controls.
11Offer-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 brand, one customer classProductionProduction trade systemsAdvancedMultiple brands / channels
Introduced at Pilot
Offers generated from your plan✓✓✓
Approver decision✓✓✓
Proportionality baseline✓✓✓
Introduced at Production
Reporting by customer class—✓✓
Approval workflow in your systems—✓✓
Approved write-back—✓✓
Trade-system integration—✓✓
Introduced at Advanced
Multi-channel trade terms——✓
Multi-stage trade approvals——✓
High customer counts——✓
Multi-channel offer controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, workflow complexity, customer counts, 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 written promotional plan→Terms and volume ingestion and customer mappingWeek 1
02Representative offers you have made→Offer baseline, plan extraction and proportionality bindingWeek 2
03Your customer classes and who approves terms→Plan basis, customer class and proportionality mappingWeek 1
04Access to relevant APIs, feeds or exports→Trade, ERP and sales-data assessment, then integration setupWeek 2
05Offers you would not want made→Proportionality cases and the evaluation suiteWeek 4
06What no offer may be built customer by customer→Confidence scoring, exception routing, guardrails and approval controlsWeek 3
07Named trade approvers to decide offers→Approver decision 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
Each phase sits on the weeks it actually occupies, and week 5 carries both evaluation and launch work.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Trade-promotion discovery, plan basis and the boundaryW2Source integration and the offer baselineW3Offer workflow, confidence logic and approval controlsW4Evaluation suite, proportionality guardrails and failure-mode testingW5Trade-system integration, pilot customers and targeted correctionsW6One promotion cycle planned under the trade team, then handover
Reading the bandA bar covers only the weeks its work is named in; the fifth carries two kinds at once.
At the end of W6Validation closes on live offers, and Agent Care picks up monitoring.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Food & Beverage AI agent
Build a trade agent that tests proportionality first.
Show us your written plan, your customer classes and the offers you make outside them. Who signs an offer a competing customer cannot be given on proportionally equal terms, and can that person produce the plan, the test and the notice afterwards? We build the boundary around that answer.
