WorkflowProcurement

Procurement Front Door

Procurement intake in plain words — every request routed the right way to buy, with the clause behind it

Anyone asks in plain words, and every request takes the right way to buy and reaches a purchase order in under two days.

See one case, screen by screen ↓
demo7smedian from asking to a route, on the request network
target1.9daysmedian from request to purchase order
target94%of requests routed right the first time — route not changed later by Procurement
demo$17,600below the supplier’s quote, by keeping an assay validation on an existing agreement
The problem

Why a simple request takes a week to reach a purchase order

Most employees do not know the buying policy, and they should not have to. They know they need a survey tool, a courier for samples or a lab to validate an assay — and often a supplier they already like. So the request arrives as an email with a quote attached, and procurement operations starts the back-and-forth: is there personal data, which cost centre, when is it needed, is this even a purchase?

Then someone has to check the catalogue, every agreement and rate card, the licence register and the supplier master before deciding the route — catalogue, existing contract, new supplier, quotes or a sourcing event, a statement of work, or another process altogether. When that check is skipped, a new supplier is onboarded for work an agreement already covers, and 15 to 25 working days of set-up land on a request that could have gone out in two.

estimated4–8daysfrom request to purchase order by hand
demo15–25working daysto set up a new supplier, under the buying policy in the working solution
typical55–60%less manual effort per request, published by a top-five drug maker
Where a request’s days go, before the purchase orderestimated
By hand6 days
With the solution1.9 days
  • Back-and-forth for missing details1 → 0.1 d
  • Working out the right way to buy1 → 0.1 d
  • Checking catalogue, agreements and licences1 → 0.1 d
  • Filling in and re-keying the forms1 → 0.2 d
  • Waiting on approvers2 → 1.4 d

Estimated split for a typical services request that an existing agreement covers, by hand and with the solution. Days are working days.

How it works

How a request moves

Six specialist agents ask, classify, match, route, pre-fill and track every request; the procurement operations lead decides the exceptions.

What comes in
Requests inPortal, chat, email · plain words, quotes attached
Agents at work
Intake guideonly the questions that matter
Then
Request classifier
Supplier & contract matcher
Then
Policy routerroute + clause
Then
Form pre-fillerwhat comes next
Then
Request trackernudges late approvers
A person decides
Procurement operations leaddecides exceptions; approvers sign in order
What comes out
Right way to buy
Purchase order
Live tracker for the requester
One case, step by step

Two requests, from plain words to a purchase order

A patient-advocacy lead needs a survey tool, and a scientist needs an assay validated by a lab she named herself. Here is what happens at Northwind Bio’s front door, screen by screen, in the working solution.

  1. 01Morning

    Every open request on its buying route

    Priya Raman · Procurement operations lead

    Priya opens the request network: 209 open requests on five buying routes, 38 purchase orders issued today, 96% routed without a buyer. Four requests are waiting on her, the oldest for 17 h 40 m. Each station shows how many requests sit there and how many are late.

    “Not a purchase → HCP engagement, grants, travel · 5 today”

  2. 02Asked

    Plain words in, only the questions that matter back

    Sam Patel · Patient Advocacy

    Sam writes: “We need a survey tool for our patient advisory panel — about 40 seats, roughly $18,000 a year. We liked Pollen Survey.” The intake guide reads it as a software subscription and asks two questions with answer chips. The request builds itself on the right as he answers — category, value, named supplier, personal data, need-by date, cost centre 4410.

    “Will the tool hold names, emails or health information of panel members?”

  3. 033.5 seconds later

    A licence already covers it

    The agents

    The classifier puts it in the $10,000–$100,000 band. The matcher finds 312 unassigned seats on the company’s Fieldnote Research Cloud licence, and notes that Pollen Survey is not a supplier. The policy router applies the channel order and finds Fieldnote already security-assessed. The answer: use the Fieldnote licence — seats ready tomorrow, no cost to Sam’s budget, no PO needed.

    “Pollen Survey as a new supplier needs an IT security assessment, a privacy review and three quotes — typically 4 to 6 weeks.”

  4. 04One click

    The clause behind the route

    Sam Patel · Patient Advocacy

    Every reason carries a citation. Sam clicks one and sees the exact passage of buying policy GP-PRC-001, version 6.2, approved by the CFO. He sends the request; his tracker shows the seat request going to the Fieldnote administrator.

    §7.5: “Unused seats on an enterprise licence are used before a new tool is bought.”

  5. 05Needs you

    A requester-named supplier comes to a person

    Priya Raman · Procurement operations lead

    REQ-24117: Dr. Maya Chen needs the sTRX-7 ligand-binding assay validated on VLT-302 serum samples, 12 weeks, starting by Nov 3 — and Kestrel Bioanalytics quoted $182,400. The intake guide read the quote and asked two questions: coded patient samples, and cost centre 3120. The agents are 88% sure of the route, and because Maya named another supplier, it waits for Priya.

    “Needs your decision. Maya named a new supplier, and an existing agreement covers the same work — the route needs your decision.”

  6. 06Seven tests

    Each policy test, with its passage

    Policy router

    Is it a purchase — yes, a research service. Catalogue item — none. Existing contract — Larkspur MSA-0418, rate card item BA-14. Competition above $100,000 — the agreement was competitively sourced under RFP-2025-031. Coded samples leaving Northwind — covered by the agreement’s data-transfer schedule. Kestrel is not a supplier, so onboarding and a sole-source justification would be needed.

  7. 07Side by side

    Two routes, and she confirms one

    Priya Raman · Procurement operations lead

    Larkspur: start Oct 27, $164,800, a statement of work under MSA-0418, about 2 days to a PO — and Larkspur ran sTRX-7 for VLT-201 last year. Kestrel: start about Nov 24, $182,400, due diligence and a sole-source form, 15–25 working days to a PO. Priya confirms the Larkspur agreement, and the approval chain is built from delegation of authority FIN-DOA-004.

    Dr. Henrik Lund, budget owner → Grace Whitfield, VP R&D Operations (DoA $150k–$500k) → Omar Haddad, Procurement sign-off above $100k.

  8. 08Drafted

    The work order and the note to Maya, ready

    Form pre-filler

    Work order SOW-0418-031 under MSA-0418: rate card item BA-14, coded VLT-302 serum transferred under Schedule 4, milestones at weeks 2, 3–9 and 12, acceptance against ICH M10 signed by the Northwind study bioanalyst, $164,800 fixed. A plain-words note tells Maya why Larkspur, and that it is $17,600 below the Kestrel quote.

    Drafts only — a person posts the requisition, and agreed prices are never changed.

  9. 09Tracked

    Like following a delivery

    Dr. Maya Chen · Translational Sciences

    Maya sees the request the way she would follow a parcel: asked, route chosen, contract matched, release drafted, approval, purchase order expected before Nov 3. The request tracker nudges approvers with the request and its reasons attached, and records every step on the request’s activity trail.

Who it’s for

Built for everyone who asks to buy — and everyone who decides.

The same front door, seen by the requesters, the procurement operations lead and the category manager — what their week looked like, and what it looks like now.

PR
Priya RamanProcurement operations lead
Decides routes
Before
Reads every request to work out the route, and chases requesters for the details the route depends on.
Now
Sees only the exceptions — low confidence, split purchases, requester-named suppliers — each with the tests, the options and the clauses side by side.
SP
Sam PatelPatient Advocacy
Requester
Before
Asks for the tool he liked and learns weeks later it needs a security assessment, a privacy review and three quotes.
Now
Describes the need, answers two questions and is told in seconds that a company licence covers it — seats ready tomorrow.
MC
Dr. Maya ChenTranslational Sciences
Requester
Before
Sends a quote and waits, without knowing where the request is or why.
Now
Gets a note saying which lab, why, and when it starts — and follows every step on her tracker.
OH
Omar HaddadCategory manager, research services
Sourcing events
Before
Finds out about an uncompeted purchase above $100,000 late, when a new supplier is already being set up.
Now
Signs off above $100,000 with the agreement, its sourcing event and the rate card line already cited; sole-source justifications come to him pre-filled.
Built on the engine

6 agents. Each with one job, and hard limits.

Six specialist agents ask, classify, match, route, pre-fill and track every request; the procurement operations lead decides the exceptions.

Intake guide

Talks with the requester in plain words, reads attached quotes and SOW drafts, and asks only the questions the route depends on — personal or patient data, need-by date, cost centre, named supplier, whether a person works under Northwind direction.

  • At most three questions
  • Plain words — no policy numbers in questions
  • Never promises a supplier or a price
Request classifier

Sets the category, the value band and whether it is a purchase at all — goods, software, services, or a payment to a person that belongs in another process.

  • A confidence on every label
  • Below the auto-confirm line, the request goes to procurement operations
Supplier & contract matcher

Searches, in order, the catalogue, agreements and rate cards, enterprise licences with unused seats and the supplier master — including near-name duplicates.

  • Cites the record or passage for every match
  • A near-name match is never assumed to be the same company
Policy router

Runs the policy tests — purchase or not, channel order, thresholds and competition, split purchases, after-the-fact, services and SOW, contingent worker, privacy and security — and builds the approval chain from the delegation of authority.

  • Every test cites a clause
  • Exceptions always go to a person
  • A requester never approves their own request
Form pre-filler

Drafts what comes next: a work order under an agreement, supplier set-up, a sourcing event, a privacy or security review, a sole-source justification, and the note to the requester.

  • Drafts only — a person posts the requisition
  • No changes to agreed prices
Request tracker

Keeps the requester’s tracker live, nudges late approvers and reviewers with the request and its reasons attached, and records each step.

  • One nudge per working day
Procurement operations lead

Decides each exception. The agents propose; a named person decides.

Ask in plain words

Ask about any request, rule or approver

Procurement can ask in plain words about a request, a threshold, an approver or a supplier — or tell it what to change. Every answer cites the policy, the agreement or the record behind it.

Why is REQ-24117 going to the Larkspur agreement?

Maya asked for Kestrel Bioanalytics, but the Larkspur agreement covers the same work: rate card item BA-14 validates a ligand-binding assay with up to three analytes for $164,800, and Larkspur ran sTRX-7 for VLT-201 last year. The agreement was competed, so no new sourcing event is needed, and its Schedule 4 covers the coded samples. It is 88% sure because Maya named another supplier — so it waits for you.

Who approves $164,800?

The delegation of authority sets the approver by value: up to $25,000 the cost-centre manager, $25,001–$150,000 a director, $150,001–$500,000 a vice president, $500,001–$2M a senior vice president. Above $100,000 Procurement signs too, and no one approves their own request. So REQ-24117 goes to Grace Whitfield and Omar Haddad after Dr. Henrik Lund.

Show possible split purchases this month

One pair. Sam Patel asked for part 2 of the patient video series from Lumen Story Studio ($54,000) five days after part 1 ($54,000). Together they are $108,000, above the $100,000 line, and the policy adds requests to the same supplier within 30 days. Sam said it is the same series split across two quarters, so I recommend one sourcing event.

Add a rule: software under $5,000 with no company data skips the security review

Done. Software under $5,000 that stores no Northwind or personal data goes straight to approval, without the IT security assessment; everything else still follows §7.5. Over the last 90 days this would have applied to 47 requests. The rule is on in Settings and recorded in the audit trail; it reaches the agents after Jonas Weber approves it.

Every screen

The working solution, as it ships.

13 screens from the working solution, on its sample data. Pick one to see it large.

The request networkEvery open request on its buying route, station by station, with what is waiting on procurement operations and what arrived today.
The front doorAn employee describes the need in plain words; the intake guide asks only what the route depends on, and the request builds as they answer.
The route, with its reasonsThe agents’ steps in view, the best way to buy with when, cost and paperwork, and the reasons cited to the policy.
The clause behind itAny citation opens the exact passage of the buying policy, highlighted.
A request that needs a decisionThe conversation, the attachment, the agents’ trace and every policy test with its passage.
Routes side by sideThe recommended route and the alternative, with start date, price, steps and days to a purchase order.
The approval chainApprovers in order from the delegation of authority, with Procurement added above $100,000, and the structured request with a confidence on each field.
Prepared for youThe work order under the agreement and the note to the requester, drafted and cited, ready to post.
The activity trailWho asked, what each agent did and who chose the route, with the time of each step.
Every requestEach request with its route, value, where it is now and how long it has waited — filter by route, needs you, late, on track or done.
The dashboardRequests through the front door, days to a purchase order, routed right the first time, where requests went and the clauses the agents cited.
Your rulesQuote and sourcing thresholds, the auto-confirm line, the split-purchase window and who decides each exception.
What the requester seesA live tracker for every request, from asked to purchase order.
Governance

Built for controlled spend: cited, approved, on the record.

Every route cites its clauseEach policy test on a request links to the passage behind it — the buying policy, the delegation of authority, the agreement, the rate card or the supplier record — and opens at that passage.
Exceptions go to a personA route is confirmed automatically only when the agents are at least 90% sure and no exception applies. Low confidence, split purchases and requester-named suppliers wait for the procurement operations lead.
Segregation of duties, built inThe approval chain is built from the delegation of authority, Procurement signs above $100,000, and no one approves a request they raised or a request for a supplier they manage.
Drafts, never postingsThe agents draft the work order, supplier set-up and reviews; a person posts the requisition. Agreement terms and agreed prices are never changed.
Rule changes are approved firstA new rule added in plain words reaches the agents only after its approver signs it off, and a change to a threshold goes to the CFO as a new policy version.
Every step on the recordWho asked, what the agents did, which route was chosen and by whom — each request keeps its activity trail with the time of every step.
Configuration

Your buying policy, not ours

The thresholds and approvers come from your buying policy and delegation of authority — and each one is a setting.

SettingDefaultChoose from
One quote below$10,000$5,000 · $10,000 · $15,000 · $25,000
Sourcing event above$100,000$50,000 · $100,000 · $150,000 · $250,000
Confirm a route automatically90% confidence85 · 90 · 95% confidence
Add together requests to the same supplierWithin 30 daysWithin 30 · 60 · 90 days
Existing contracts and licences before new suppliersOnPart of the policy — cannot be turned off here
Who decides routing exceptionsPriya RamanPriya Raman · Omar Haddad
Who approves sole-source justificationsOmar HaddadOmar Haddad · Priya Raman
Nudge approvers after1 working day4 hours · 1 working day · 2 working days
Connections

Works with the systems you already run

Buying policy and delegation of authoritythe clauses every route cites
Contracts and rate cardsmaster agreements, schedules and rate card lines
Supplier master and purchase historywho is a supplier, and what they delivered before
Catalogues and licence registerpunch-out items and unused enterprise seats
Your ERPrequisitions out, PO numbers back to the tracker
Intranet, company chat and the procurement mailboxwhere requests come in, attachments and all
What it changes

The difference, in numbers.

Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.

target
1.9days
median from request to purchase order
By hand4–8 days
With agents1.9 days
target
94%
of requests routed right the first time
route unchanged by procurement
typical
55–60%
less manual effort per request, published by a top-five drug maker
By handall of it
With agents40–45%

“demo” = seen in the working solution, on its sample company data · “target” = the design goal, measured in the live solution (dashboard, last 30 days) · “estimated” = our estimate · “typical” = published figures (procurement-intake case study, top-five drug maker, 2024 — 55–60% less manual effort per request). People, companies and products named on this page are fictional — characters and sample data in the working solution.

Questions

What procurement teams ask us.

What is a procurement front door?

One place where any employee asks to buy something in their own words, instead of picking a form or a buying channel. Procurement Front Door classifies the request, asks only the questions the route depends on, finds the right way to buy — catalogue, existing contract or licence, new supplier, quotes or a sourcing event, a statement of work, or another process — and tracks it to the purchase order.

How does it decide the right way to buy?

The policy router runs your buying policy’s tests in order: is it a purchase, the channel order, value thresholds and competition, split purchases, services and statements of work, contingent workers, privacy and security. Each test cites the clause behind it, and the approval chain comes from your delegation of authority.

Does it stop people onboarding new suppliers for work an agreement already covers?

It checks the catalogue, agreements and rate cards, and licences with unused seats before a new supplier, as the channel order requires. When a requester names a supplier anyway, the request comes to procurement operations with both routes side by side — start date, price, steps and days to a purchase order.

Does it catch split purchases?

Yes. Requests from the same cost centre to the same supplier within the window you set — 30 days by default — are added together when the thresholds are applied, and a possible split comes to procurement operations as an exception.

Do people stay in control?

Yes. A route is confirmed automatically only above the confidence you set and when no exception applies; everything else waits for the procurement operations lead. The agents draft forms but never post a requisition, approvers sign in the order the delegation of authority sets, and no one approves their own request.

What about fees to doctors, grants and travel?

They are not purchases. The front door recognises them and hands them to the HCP engagement, grants or travel process with the details already filled in, so the requester does not have to start again.

How long does it take to go live?

The Agentic Solution Engine builds and deploys it from your requirements — your buying policy, delegation of authority, agreements, catalogue and a sample of past requests — and it goes live once every quality gate has passed. We will walk you through it on your own requests first.

See it on
your requests.

We’ll run Procurement Front Door on a sample of your own past requests and your buying policy.