State the bets a category plan is making — about the market, the supplier, the specification — date each one, give it an owner, and leave every revision to a named category manager.
A plan is set, and each assumption it stands on is written out beside it with an owner and a date.
02
An assumption moves, and the plans resting on it are marked stale rather than left reading as current.
Reason
03
A plan is inherited, and any bet in it with no living owner is raised as an orphan instead of carried on.
04
A lever is listed, and a plan that lists consolidation, re-specification and demand work alike says so.
05
A market signal arrives, and it is put against the assumption it bears on the day that signal lands.
Decide
06
A saving is claimed, and the baseline behind the claim is shown, or the claim does not travel onward.
07
A plan is copied out of another category, and the assumptions that did not travel with it are named.
Out
08
A bet is put under test, and what the plan would become if that bet failed is set out alongside it.
09
Execute write actions only inside the approval boundaries agreed during implementation.
→Product statement
Assumption capture, staleness marking and signal watch belong to the agent. The strategy, the lever, the spend and any claim that a market has changed belong to a named category manager.
Example workflow
One category plan, bets to review
AgentHuman
1Plan and category receivedCategory plan, spend cut, supplier list, contract register or the last review pack
2Assumptions lifted outThe market, supply, specification and demand bets the plan rests on, each with an owner and a date
3Standing testedThe assumption, the signal against it, whether it still holds and confidence
4Controls appliedAssumption-coverage checks, signal-age checks, owner checks and confidence threshold
No human action required
Stages 1 to 4 run unaided, and no plan is revised at any of them — the agent is testing, and the category manager lane opens at the confidence gate.
5DecisionSplits at the confidence gate
Assumption still holding
Goes to the category manager to accept.
Anything stale or unowned
Adds a procurement lead read first.
Category manager review
The plan is held with its assumptions, the signals against them and the confidence.
Accept · Amend · Send to category review
Accepted — by the category manager▼
6Plan and category records updatedOnly where write access and records policy allow it
7Outcome evaluatedAssumption coverage, staleness caught, manager amendments and what review found
Amendments
Each amendment made in review is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Setting the strategy a category is bought under.
Choosing which lever a category is taken to.
Committing spend against a plan.
Declaring that a market has changed.
Automation boundaryAgent acts unaided
✓Write each assumption down with an owner and a date.
✓Mark a plan stale when the assumption beneath it stops holding.
✓Watch the market signals beneath a standing plan.
✓Show what the plan would look like if one of its stated bets failed.
Nothing revises a category plan except a named category manager, inside the agreed boundaries.
Judging whether a category can be planned at all.
Telling a board that a plan is still sound.
Deciding which supplier a category consolidates on.
Changes to the plan, the levers or the assumptions.
Example output
One category assumption, annotated
This serves a procurement team who may have to explain years later why a category was bought the way it was; below is one assumption exactly as the agent leaves it.
Assumption output · single category planIllustrative example
Category
Assumption as written
Stated as
Standing
Confidence
Held for
Packaging, regional plan
The regional supply base stays competitive
Written as a fact, not a bet
Signal dated 3 August 2026
Held unaccepted
The category manager, by name
As receivedTaken from the plan as written and the signals as they arrived — nothing on this side is judged by the agent.
Why this is a betWhether this bet holds is a judgement the category manager makes.
ActionAcceptAmendSend to category review
What the score decidesBelow the configured threshold an assumption gets a lead read before the manager sees it.
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 category planFrom the plan that carries it
03Assumptions
Where the bet is tested
The classification deciding what a category even contains is the spend analysis agent; this one starts after that line is drawn, and its subject is the assumption a plan rests on.
01Approved path
A plan is a set of bets
Say a market will stay competitive and you have made a prediction; write it into a plan as a fact and nobody goes back to test it.
02Human review
What was checked, and not found
No category plan reviewed states its own expiry, and none carries a mechanism for withdrawal, so a plan whose premise has gone is reported as still in force rather than quietly retired.
04Build an evidence trail
The plan, the assumption under it and the manager who set it stay together.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Category and spend dataSpend cubes · category hierarchies Category spend and volumes
Market and price dataIndex series · price feeds Input cost and capacity moves
Supplier and contract dataSupplier master · contract register Terms, expiries and dependencies
Agent
Category management and planning
Reads the plan Tests the bets Holds for the manager
Planning and reportingCoupa · Ariba · Ivalua · Jaggaer Category plans and review calendars
A category-level assumption figure can read clean while inherited category plans carry most of the amending. Nestack reports the amendment rate by slice, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Inherited category plans
7.9%
3.7×
Review
Single-source categories
5.6%
2.6×
Review
Volatile input markets
3.5%
1.6×
Watch
Established stable categories
1.5%
0.7×
Normal
Bar: amendment-rate lift vs. established-category baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
What a dead assumption costs
The loop ends when the assumption nobody stated is a standing case. That suite is what the next plan published is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Amendment rate rises on inherited category plans.
02Diagnose
The category plan built on a supply assumption that stopped being true two quarters ago, still being executed because no plan carries an expiry, is worked backwards until one cause stands.
03Improve
The change goes out numbered, and the category plans behind it travel attached.
04Verify
A single red category case is enough to stop the release.
05Learn
It is retained permanently, and the planning rules travel alongside it.
Learn → DetectThe return edge. The next plan is measured 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, assumption logic, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Category-assumption discovery and boundary setting.
02Spend, market and contract source review.
03Assumption-to-signal and category-coverage mapping.
04Plan ingestion and assumption extraction.
05Assumption logic and owner binding.
06Confidence scoring and review routing.
07Category manager review workflow.
08Market-signal integration.
09Assumption and coverage cases.
10Guardrails and revision controls.
11Plan-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 category, one cycleProductionProduction planning workflowAdvancedMultiple categories / regions
Introduced at Pilot
Assumption capture to your plans✓✓✓
Category manager acceptance✓✓✓
Category-structure baseline✓✓✓
Introduced at Production
Reporting by category owner—✓✓
Category review workflow in your systems—✓✓
Approved write-back—✓✓
Market-signal integration—✓✓
Introduced at Advanced
Cross-region assumption sets——✓
Multi-category plan packs——✓
Large plan portfolios——✓
Multi-category assumption controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, workflow complexity, plan volume, 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 live categories and the plans each is bought under→Assumption capture and register versioningWeek 1
02Representative category plans and review packs→Signal binding, staleness logic and the assumption baselineWeek 2
03Your planning calendar and the managers it names→Assumption mapping, owner binding and the automation boundaryWeek 1
04Access to relevant APIs, feeds or exports→Spend, market and contract source assessment, then integration setupWeek 2
05Plans you would not want interrogated→Assumption cases and the drift evaluationWeek 4
06What no category plan may promise→Confidence scoring, review routing, guardrails and release controlsWeek 3
07A named category manager who accepts the register→Release to the category manager, 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
Bands are sized to the work behind each one, so a week carries two rather than one being stretched.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Category discovery, assumption mapping and the automation boundaryW2Spend, market and contract integration and the assumption baselineW3Staleness logic, confidence scoring and release controlsW4Evaluation suite, assumption cases and failure-mode testingW5Planning integration, pilot registers and targeted correctionsW6One planning cycle run under the category manager, then Agent Care handover
Reading the bandEach bar covers only the weeks its own work is named for, and week five is shared by design.
At the end of W6When the category record validates, Agent Care picks the agent up.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Procurement AI agent
Build a category management agent around the bets your last plan never wrote down.
Show us one category plan in flight and the assumptions under it. If a bet in that plan has gone untested for over a cycle, then the plan is costing you the lever nobody looked at. We will map the assumptions, set the automation boundary and name what stays with the manager.
