One governed front door for every plant, function and entity.
A plant engineer writes
Gearbox on line 3 has failed. Need a replacement this week.
Proconomy runs
Extracted
Classified
An engineer describes a failed gearbox and Proconomy returns a categorised, costed, routed request.
Approved request
Selected by rule, not by whoever opened the inbox
Value, category, entity and risk select the buying route, so nothing depends on who opened the inbox.
Reads category, entity, plant, cost centre, value band and required date out of free text, and shows its working for correction.
Asks the requester for the drawing, quantity or date the category requires, then resumes the moment it arrives.
Applies your approval matrix across entities, sends the reminders and escalates an overdue decision to the named alternate.
Read from the text
Every value stays editable by the buyer
Category requirements
Chased from the requester, not from your buyer
Seven stages from the plant floor to your ERP. One of them waits for a person.
A plant engineer writes what the line needs, in their own words.
Category, entity, cost centre and value band are read out of the text.
The drawing reference and delivery date are requested from the requester.
Catalogue, contract, sourcing or onboarding — and the rule that fired is stored.
Nothing above your threshold is auto-approved and the checkpoint cannot be configured away.
The approved outcome is written back to the system of record you already have.
Original text, extracted data, applied rule, approvals and outcome, as one record.
A need is described
The request is classified
What is missing is collected
Policy selects the route
A named person decides
The ERP is updated
The history stays linked
Routing agent
Each agent carries an enumerated permitted-action set and a value ceiling you configure per entity.
Consequential decisions return to the people your policy names, and no configuration removes them.
Reconstructable
Retrievable per transaction, without reading a mailbox
Every action is attributed to an actor and the permission that allowed it, retrievable per transaction.
Intake failure never appears as a budget line. It appears as these.
The categories nobody had a spare week for go to renewal untested, at the incumbent’s price.
When the route depends on who opened the inbox, policy is advisory — and nobody can say by how much.
The buyers holding the thresholds are the routing engine. Their notice period is your recovery window.
Mailboxes evidence the purchase. They rarely evidence the rule that permitted it.
Proconomy connects to the systems you already run. The ERP stays the system of record.
The complaint that reaches the executive is rarely the one that costs the most.
Top painI am asked what proportion of our spend followed policy, and I can give an opinion rather than a number.
What changesEvery request stores the rule that routed it, so policy adherence becomes a number you report.
Top painI have written the policy three times. It is still applied differently at every plant, and I find that out at audit.
What changesPolicy is executed rather than circulated, and entity differences are configured once.
Top painMost of my week goes on working out what people actually asked for, then chasing the half of it they did not send.
What changesRequests arrive classified, complete and routed. The chasing happens before a buyer sees them.
Top painI approve things whose justification sits in an email thread I was never on, and I approve them late because nobody told me they were waiting.
What changesThe request, the rule and the justification arrive together, with a reminder before it is late.
Top painI can prove what was bought. I cannot prove why it was allowed to be bought that way, and that is the question being asked.
What changesRequest, extracted data, rule, approvals and transaction stay linked as one record.
Do we have to fix our category structure first?
No. Start with the structure your buyers already use. Classification is corrected in the flow of work rather than in a cleansing project.
Does this replace our ERP?
No. The ERP stays the system of record and receives the approved outcome. Nothing is migrated out of it.
Who needs to be in the first session?
One person who can settle a rules question without convening a committee, and someone who knows how your ERP is actually used. Two people is usually enough.
What if we are a single plant?
Then coordination is probably still manageable by hand, and we will say so on the first call rather than after a pilot.
One of your own requests, including the part that usually goes wrong. You will see where the agents act, where the platform stops, and what it leaves on the record.
Someone from client success replies, not a sales sequence. If we are not a fit we will say so on the first call.
Not ready to talk to anyone?
Fair enough. Both of these work without giving us your email.
Bring one workflow. We will run it.No slides. You will see where it stops for a person.
