Sourcing and RFQ AI Agent

What this agent does

Proposes the shortlist, never chooses from it

A requirement lands, and what the business needs is written apart from what the last supplier gave it.

A requirement is inherited, and the lines traceable to the incumbent contract are marked as inherited.

Reason

A shortlist is drawn, and each name carries the reason it is on the list rather than a rank.

A shortlist repeats the last one, and the repetition is reported as a finding rather than as agreement.

A request is drafted, and a question no supplier could answer from its own records is pulled before it goes.

Decide

A quote returns on its own basis, and the adjustments that make it comparable are shown one by one.

A candidate leaves the list, and the reason and the person who removed it are held against the requirement.

Out

A supplier declines to bid, and the decline is captured and asked about rather than left as silence.

Execute write actions only inside the approval boundaries agreed during implementation.

→ Product statement

Separation, candidate proposal, drafting and normalisation belong to the agent. Choosing belongs to a named buyer, who awards the work and owns it there.

Example workflow

One requirement, brief to issue

AgentHuman

1Requirement receivedA buying request, a renewal date, a specification or the contract that is expiring

2Need separated from incumbentWhat the business needs, what the last supplier happened to provide, and which lines came from which

3Candidates proposed with reasonsEach name, why it is on the list, and which names the last shortlist carried

4Controls appliedAnswerability checks, repetition checks, coverage checks and shortlist confidence

No human action required

Stages 1 to 4 run unaided, and nothing goes to a supplier at any of them — the agent is proposing, and the buyer lane opens at the shortlist gate.

5DecisionSplits at the shortlist gate

Shortlist moves off the last one

Goes to the named buyer to issue.

Anything that repeats it

Adds a category-manager read first.

Buyer review

The shortlist is held with the requirement, the reason per name and the names it did not carry.

Issue · Add candidate · Send to category review

Issued — by the named buyer▼

6Sourcing and supplier records updatedOnly where write access and records policy allow it

7Outcome evaluatedShortlist turnover, response comparability, buyer corrections and what review found

Corrections

Each buyer correction is counted in the evaluation.

What should not run autonomously

Human approval stays in control

Outside the boundary — human approval required8 items

Choosing which supplier gets the work.

Dropping a candidate off the shortlist.

Awarding, or committing spend to a supplier.

Ruling that two quotes are equivalent.

Automation boundaryAgent acts unaided

✓Separate the requirement from the specification the incumbent wrote.

✓Propose each candidate with the reason it is on the shortlist.

✓Draft the request each candidate is asked to answer.

✓Show every adjustment made to compare two quotes on one basis.

Nothing is awarded except by a named buyer, working inside the boundaries agreed.

Judging whether a market test is needed at all.

Telling a supplier why it was not asked.

Settling what the business actually requires.

Changes to the source list or shortlist rules.

Example output

One shortlist and its request, annotated

A component desk names distribution paths per candidate and a supplier agent orders against approved sources; this is the requirement-to-shortlist step for any category, where the question is why these names.

Sourcing output · single requirementIllustrative example

Requirement

Recorded as

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 requirementFrom the request that raised it

03Evidence

Where the evidence is used

Where a shortlist went out short of a name that should have been on it, the buyer reopens the requirement, the omission is recorded against it, and the case joins the suite.

01Approved path

A shortlist is a set of choices

Nobody made those choices in one sitting: the requirement narrowed the field, the source list narrowed it again, and the last shortlist did most of the narrowing before anyone sat down.

02Human review

What was checked, and not found

No law examined tells a private company who to invite to quote. Public-sector procurement rules are real, and this page is not about them. Nothing consulted obliges a market test, a floor on how many candidates are asked, a published notice, or a stated reason for leaving a supplier off a list, and nothing sets a period for keeping the reasons. So the discipline here is a control the company chooses to run, and what it is run against is habit rather than a rule.

04Build an evidence trail

The shortlist, the requirement it answers and the buyer who chose stay together.

Integrations

Typical integrations

Five system groups connect to the same agent. Which of them are in scope is decided in discovery.

Sourcing platformsCoupa Sourcing · Jaggaer · Keelvar
Ariba and RFx event records

Supplier and market dataRegistries · directories
Trade bodies and market listings

Spend and contract historyERP spend lines · contract register
Prior quotes and awards recorded

Agent

Sourcing and request preparation

Reads the requirement
Proposes candidates
Holds for the buyer

Requests and responsesEmail · supplier portals · EDI
Quotes returned and declines to bid

Observability & evaluationOpenTelemetry · Langfuse
Supported monitoring/evaluation sources

Integration availability depends on the client's existing systems and API access.

Agent controls

Six riddles between the model and the shortlist

Six riddles in a stack, the last the finest. What falls through is drawn in the map below.

L6 · Outermost — last line of defenceInward → L1 · closest to the model

L6Rollback / safe modeNarrow the agent to listing sources when evaluation or production signals degrade.Roll back

L5Version monitoringTrack model, prompt and sourcing rules, and note the version each shortlist was drawn under.Track

L4TraceabilityRecord each shortlist, the requirement under it, the reason held per name and every read.Record

L3Buyer releaseHold the shortlist for a named buyer; the hold governs release, not whether the names are the right ones.Gate

L2Sourcing guardrailsTest each shortlist against the separated requirement, and refuse a list drawn from the incumbent specification.Restrict

L1Repetition thresholdsRoute a shortlist that repeats the last one to a category read before it reaches the buyer.Require review

Model coreShortlist drawn — the requirement, the names, the reason for each and the confidence

L1 – L2Test whether a shortlist may stand

L3Leaves the choosing to a named buyer

L4 – L5Keep the shortlist and the requirement behind it

L6Returns to the source list when signals degrade

How Nestack evaluates it

Evaluate the whole selection — not only the shortlist that comes out.

Coverage runs the whole depth of the workflow, and every layer is cut by slice.

Surface — the shortlist a supplier reads

Depth of coverage ▼

E1Final-output evaluationDid the shortlist record the requirement it was actually drawn against?

E2Step-level evaluationDid the agent read the right requirement, the right sources and the live source list?

E3Tool evaluationDid it read and write the correct requirement and the correct candidate?

E4Confidence calibrationDo low-confidence shortlists actually attract more buyer corrections?

E5Slice evaluationHow does performance change across specific requirement types?

E6Business outcomeHow many shortlists needed a correction before the buyer would issue?

Floor — the market a shortlist actually tested

Failure modes

Where each failure originates in the agent

Seven failure modes, each pinned to the stage where it first shows.

Agent lifecycleDirection of processing →

01 · Retrieval1 mode

OG-03

Stale source list read

The source list read is not the one now approved.

Stage gathersThe need, the sources, the names and the dates

02 · Reasoning2 modes

OG-04

Shortlist repeats the last one

The names are the names that were asked last time.

OG-06

Retired requirement read as live

An old specification is worked as the current one.

Stage proposesThe requirement, the candidates and the reasons

03 · Tool / write2 modes

OG-02

Thin shortlist passed forward

A list moves on without the category read.

OG-05

Quote bound to the wrong requirement

The response is filed against another requirement.

Stage writesOnly where write access and approval policy allow it

04 · Output1 mode

OG-01

Issued with the reasons unrecorded

The record shows the names but not why each is there.

Stage returnsThe shortlist a supplier reads and answers

05 · Change / Version1 mode

OG-07

Silent source-list drift

The approved list narrows while stored shortlists keep the old one.

Stage tracksModel, prompt, source rules and list dates

Sev-1 · a shortlist issued with no reasons Sev-2 · a repeated list reaches the market Sev-3 · sources degrade, shortlist held back

See the complete Procurement failure-mode catalogue →

Affected slices

Renewals carry the repeated shortlists

A requirement-level coverage figure can read clean while renewals of expiring contracts carry most of the shortlists that repeat the last one. Nestack reports the repeat rate by requirement type, not only in total.

Slice performance — reported separately, not only in aggregateIllustrative example

Slice	Failure rate	Lift	Status
Renewals of expiring contracts	9.5%	3.7×	Review
Incumbent-written requirements	6.8%	2.6×	Review
Single-source technical builds	4.2%	1.6×	Watch
Open specification requirements	2.2%	0.9×	Normal

Bar: repeat-rate lift vs. open-specification baseline · scale 0–4.0× · tick marks the 2.0× review threshold 2 of 4 slices over threshold

Evidence-linked improvement

What a repeated shortlist costs

A cycle ends when the shortlist nobody could justify is a standing case. That suite is what the next shortlist issued is measured against.

Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn

01Detect

Repeat rate rises on renewals of expiring contracts.

02Diagnose

The three names on the shortlist that were the three names on the last one are worked backwards until one cause is left standing.

03Improve

The change ships numbered, and the shortlists that forced it ride with it.

04Verify

One shortlist case still failing is enough to hold the release back.

05Learn

It is kept for good, and the sourcing rules are amended in the same commit.

Learn → DetectThe return edge. The next shortlist 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, shortlist and request logic, evaluation, integration, then production validation and handover.

Workstream Week 1Week 2Week 3Week 4Week 5Week 6

01Requirement-separation and automation-boundary work.

02Sourcing, spend and market sources.

03Candidate-to-reason and requirement-coverage mapping.

04Requirement ingestion and normalisation.

05Candidate proposal and reason binding.

06Repetition scoring and review routing.

07Buyer review workflow.

08Sourcing-platform integration.

09Requirement and shortlist cases.

10Guardrails and selection controls.

11Shortlist-trail instrumentation.

12Deployment, documentation and Agent Care handover.

12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallel Final 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 tier PilotOne category, one requirement ProductionProduction sourcing workflow AdvancedMultiple categories / markets

Introduced at Pilot

Shortlists drawn to your requirements✓✓✓

Named buyer selection✓✓✓

Source-list baseline✓✓✓

Introduced at Production

Reporting by requirement—✓✓

Buyer review workflow in your systems—✓✓

Approved write-back—✓✓

Sourcing-platform integration—✓✓

Introduced at Advanced

Multi-source candidate research——✓

Cross-category shortlist packs——✓

Large source libraries——✓

Multi-market shortlist controls——✓

Build price From $5,000 From $8,000 Custom quote

Final build priceConfirmed after discovery based on integrations, workflow complexity, sourcing 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 requirement each starts from → Requirement capture and incumbent separationWeek 1

02Representative requirements and the shortlists they drew → Source binding, candidate logic and the shortlist baselineWeek 2

03Your sourcing calendar and the buyers it names → Requirement mapping, source binding and the automation boundaryWeek 1

04Access to relevant APIs, feeds or exports → Sourcing, spend and market source assessment, then integration setupWeek 2

05Shortlists you would not want defended → Requirement cases and failure-mode testingWeek 4

06What no shortlist may settle → Repetition scoring, review routing, guardrails and release controlsWeek 3

07A named buyer who chooses from the shortlist → Release to the named buyer, then pilot and production validationWeeks 5–6

Nothing else is required Deployment, documentation and Agent Care handover are ours.

Delivery timeline

Four phases across six weeks

The bands here are counted, not spaced to look even; the fifth carries two phases because it does.

Phase W1W2W3W4W5W6

Discovery W1

Build W2 – W3

Evaluate W4 – W5

Pilot & Launch W5 – W6

Week focus W1Requirement discovery, incumbent separation and the automation boundary W2Sourcing and spend integration and the source-list baseline W3Candidate logic, reason binding and release controls W4Evaluation suite, requirement cases and failure-mode testing W5Sourcing-platform integration, pilot requirements and corrections W6One sourcing cycle run under the category buyer, then Agent Care handover

Reading the bandEach bar covers only the weeks its own work is named for, and the fifth week carries two phases.

At the end of W6When the shortlist 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 a sourcing agent around the requirement your last shortlist never questioned.

Show us one category you re-tender and the three names that answered last time. If those three are the three that answered the time before, then the shortlist is a habit rather than a market test. A supplier who declined without being asked why comes back as a finding.

Discuss this agent →

Nestack Agents · Sourcing and RFQAGT-PR-01 · Agent Care available after launch