Shape the buying request whatever form it arrives in, ask only the questions this one needs, route it to the reviews it actually requires, and leave every approval to a named procurement lead.
A request arrives as an email, a form, a ticket or a corridor conversation, and it is taken in as it stands.
02
A request is read for what it is actually asking, before anyone decides which reviews apply.
Reason
03
A request is asked one question at a time, each one chosen because of the answer before it.
04
A request needing legal, security and data-protection reads has them opened together, not in turn.
05
A route is drawn where one review truly blocks another, and the dependency is stated rather than assumed.
Decide
06
A request that is really several requests is split, and each part goes to the people it needs.
07
A request that duplicates one already in flight for another team is joined to it, not started again.
Out
08
A request stalls, and the review it waits on and the person who owns that review are both named.
09
Execute write actions only inside the approval boundaries agreed during implementation.
→Product statement
Intake, shaping and routing belong to the agent. Approval belongs to a named procurement lead, who clears the request and owns the decision from there.
Example workflow
One request, arrival to clearance
AgentHuman
1Request receivedAn email, an intake form, a ticket, a chat message or a line on a spreadsheet
2Request read and shapedWhat is being bought, for whom, against which contract and by when the requester needs it
3Reviews identified and sequencedWhich reviews apply, which may run together and which one waits on another
4Controls appliedCompleteness checks, duplicate checks, threshold checks and routing confidence
No human action required
Stages 1 to 4 run unaided, and nothing is approved at any of them — the agent is routing, and the procurement lane opens at the routing gate.
5DecisionSplits at the routing gate
Route is unambiguous
Goes to the procurement lead to clear.
Anything unclear
Adds a category read first.
Procurement review
The request is held with the answers given, the reviews opened and who each one waits on.
Clear · Reroute · Send to category review
Cleared — by the procurement lead▼
6Workflow and purchasing records updatedOnly where write access and records policy allow it
7Outcome evaluatedRouting accuracy, review coverage, lead corrections and what the read found
Corrections
Each procurement-lead correction is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Approving a buying request of any size.
Waiving a review a request has triggered.
Ruling that a threshold has not been crossed.
Closing a request as unnecessary.
Automation boundaryAgent acts unaided
✓Take the request in whatever shape it arrived.
✓Ask only the questions this particular request needs.
✓Open the reviews the request requires and run them in parallel.
✓Show where the request is waiting and which person must act next.
Nothing is approved except by a named procurement lead, inside the boundaries agreed.
Deciding which team owns a shared purchase.
Telling a requester that no review applies.
Choosing which supplier a request goes to.
Changes to routing rules or review thresholds.
Example output
One buying request, annotated
Our operations workflow agent orchestrates business processes across systems; this one shapes a human request before any process starts, and below is one request as the agent leaves it.
Intake output · single requestIllustrative example
Request
Recorded as
Requester
Evidence of record
Confidence
Held for
Software for one team
Arrived as an email thread
Shaped, not approved
Intake record, 3 August 2026
Held uncleared
The procurement lead, by name
As receivedRead off the request as it arrived and the answers the requester gave, and it claims nothing past those.
What the record holdsThe request as sentThe answers givenThe reviews opened
Why no clearance hereClearing a request is a judgement a named procurement lead owns.
ActionClearRerouteSend to category review
What the score decidesBelow the configured threshold the request collects a category read before the lead 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 requestFrom wherever it arrived
03Evidence
Where the evidence is used
Where a request was routed wrongly and the buy has already happened, the lead reopens it with its intake trail attached, the missed review is run late, and the case joins the suite.
01Approved path
The request arrives shapeless
Somebody wants something and does not know whether it needs legal, security, data protection or a new supplier — and the form assumes they do.
02Human review
What was checked, and not found
No rule consulted requires a buying request to be routed any particular way: intake design is policy a company writes for itself, so which reviews a request triggers and the order they run in are choices rather than requirements. What is measured here is your own policy and whether a request met it.
04Build an evidence trail
The request, the route it took and the person who owns it stay together.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Intake channelsEmail · web forms · chat apps Service desk and ticketing queues
Workflow and approvalsServiceNow · Jira · Asana Approval steps and task queues
Purchasing systemsSAP Ariba · Coupa · Jaggaer Requisitions and the approved catalogues
Agent
Intake and orchestration
Takes the request Shapes and routes Holds for the lead
Reviews and reviewersLegal · security · data protection Finance and the category owners
A type-level routing figure can read clean while first-time request types carry most of the routes that had to be redone. Nestack reports the reroute rate by request type, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
First-time request types
9.0%
3.7×
Review
Multi-review requests
6.4%
2.6×
Review
Cross-team shared buys
4.0%
1.6×
Watch
Catalogue re-orders
1.7%
0.7×
Normal
Bar: reroute-rate lift vs. catalogue-re-order baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
What a request routed to nobody costs
A cycle ends when the request routed to nobody is a standing case. That suite is what the next intake cleared is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Reroute rate rises on first-time request types.
02Diagnose
The buying request that came in as a message to somebody who left, and sat there, is worked backwards until one cause is left standing.
03Improve
Changes leave numbered, and the requests that forced them are filed underneath.
04Verify
One request case still failing is enough to stop the release.
05Learn
One case joins the suite, one line joins the routing rules.
Learn → DetectThe return edge. The next request 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, intake and routing logic, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Intake discovery and automation-boundary definition.
02Email, workflow and purchasing sources.
03Request shaping and question-dependency route mapping.
04Request capture and channel normalisation.
05Question sequencing and review binding.
06Confidence scoring and review routing.
07Procurement review workflow.
08Workflow and purchasing integration.
09Routing and completeness cases.
10Guardrails and routing controls.
11Request-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 team, one request typeProductionProduction intake workflowAdvancedMultiple teams / entities
Introduced at Pilot
Request shaping to your rules✓✓✓
Named procurement-lead clearance✓✓✓
Request-population baseline✓✓✓
Introduced at Production
Reporting by request type—✓✓
Routing review workflow in your systems—✓✓
Approved write-back—✓✓
Workflow-and-form integration—✓✓
Introduced at Advanced
Multi-review orchestration——✓
Cross-team request packs——✓
Large request volumes——✓
Multi-team routing controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, workflow complexity, request 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 request channels and the shapes they arrive in→Request capture and channel mappingWeek 1
02Representative requests from a recent buying period→Channel capture, question logic and the routing baselineWeek 2
03Your review owners and the teams they sit in→Review mapping, question logic and the automation boundaryWeek 1
04Access to relevant APIs, feeds or exports→Channel, workflow and purchasing source assessment, then integration setupWeek 2
05Requests you would not want traced→Routing cases and failure-mode testingWeek 4
06What no intake form may settle→Confidence scoring, review routing, guardrails and release controlsWeek 3
07A named procurement lead who clears the request→Release to the procurement lead, 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
Read the bands as measurements, not decoration. Two share week five because that is how they run.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Intake discovery, review mapping and the automation boundaryW2Channel and workflow integration and the request baselineW3Question sequencing, routing logic and release controlsW4Evaluation suite, routing cases and failure-mode testingW5Purchasing integration, pilot requests and targeted correctionsW6One intake month run under the procurement lead, then Agent Care handover
Reading the bandEach bar covers only the weeks its own work is named for, and two bands genuinely share week five.
At the end of W6When the routing record validates, Agent Care takes the agent on.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Procurement AI agent
Build an intake agent around the buying request your last form never fitted.
Show us one buying request that reached the right desk late and the form it was asked to fill in first. Send it as it arrived, and we will show you the questions it should have been asked and the reviews it should have opened. A request nobody chased comes back as a finding.
