
Organisations & enterprise
Procurement requests that arrive complete — and reach the right approver.
An employee asks for what they need in their own words. The system fills in what is missing and routes the approval according to your procurement policy.
Example · can be built
From a sentence to an approved request.
The employee writes a request
In free language — the way they would write to a colleague.
Missing details are filled in
The system asks only for what is missing, such as quantity, cost centre or the date it is needed.
The approval is routed
By amount and department, following the thresholds and approvers in your procurement policy.
Procurement sees the whole picture
Every open request, its stage and who it is waiting for.

Three views of one request
Each person sees what they need — and nothing more.
What the employee sees
A short conversation instead of a form.
I need a laptop for the new analyst who starts next month.
Which cost centre should this be charged to, and which standard model does the role use?
Finance operations. Standard analyst model.
Request ready. It goes to your department manager for approval.
Illustrative example · sample data
What the approver receives
A complete request, with the reason it reached them.
Approval needed
Your step- Item
- Laptop, standard analyst model
- For
- New analyst, finance operations
- Cost centre
- Finance operations
- Routed
- By amount and department, per policy
Illustrative example · sample data
What the procurement manager sees
Where requests are getting stuck, and with whom.
Open requests
By stage
Laptop — finance operationsWaiting for department manager
ApprovalSafety equipment — plantWaiting for budget owner
StuckSoftware licence — ITApproved · with procurement
OrderingIllustrative example · sample data
Your policy, not ours
The routing rules are yours.
Thresholds, departments, approvers and exceptions are set from your procurement policy — and stay visible, so anyone can see why a request went where it went.
For the IT manager
The solution works with your existing systems and each user's existing permissions, with every connection documented.
For the procurement manager
One place to see every open request, its stage and the person it is waiting for.
For the approver
Requests arrive complete, with the reason they were routed to you.
This example describes a project that can be built with you — not a completed installation.
Start with one process
Which request in your organisation always arrives half-filled?
Start there. We will map how it moves today and propose how it could move instead.