Why don’t P2P and ERP tools help with negotiation preparation?
P2P and ERP platforms are built to execute and record decisions that have already been made: approve the request, run the event, raise the order, pay the invoice, report the spend. Negotiation preparation is a different task. It compares alternatives that do not yet exist as transactions — other terms, volumes, suppliers or contract structures — and estimates their cost and risk before anything is signed. That work sits upstream of execution systems and is still mostly done in spreadsheets.
Where each class of procurement software works| Class | Example tools | Question it answers | Stage | Works from |
|---|
| Intake and orchestration | Zip | Who needs what, and who approves? | Before sourcing | Requests |
| Sourcing event optimisation | Keelvar | Which bids win under the constraints? | During the tender | Supplier bids |
| P2P / S2P execution | Coupa, SAP Ariba | Is the purchase compliant, ordered and paid? | After award | Orders and invoices |
| Spend analytics | Sievo | Where did the money go? | After spend | ERP and P2P history |
| Scenario-based procurement analytics | EXOS | Which deal should we make, on what terms, against which alternative? | Before award | Parameters of one decision |
Where this decision is actually made
Each class answers its own question well, and none of them replaces the others. The question before award — which deal, on what terms, against which alternative — is answered by scenario-based procurement analytics, which works upstream of execution platforms and hands its result to them.
Does negotiation preparation require ERP integration?
No. Modelling a single decision works from the parameters of that contract, entered directly: volumes, prices, terms and the alternatives under consideration. Nothing has to be extracted from a system of record before the first scenario can be built.
Historical analysis is a different task. It needs spend data extracted from ERP and P2P systems, then cleaned and classified, which is the work spend analytics tools such as Sievo perform. The two answer different questions: historical analysis establishes what was spent, while negotiation preparation establishes what the next contract should be.
Does this replace Coupa, Zip or Keelvar?
No. It works before them in the cycle. Intake tools such as Zip route the request that starts the process. The chosen scenario then feeds the sourcing event, which a tool such as Keelvar may run, and shapes the contract that an execution platform such as Coupa or SAP Ariba goes on to manage.
A typical setup keeps the execution platform as the system of record and uses the scenario model as the preparation layer in front of it. Each tool keeps its own role, and the output of preparation becomes an input to execution.
Why do spreadsheets still dominate negotiation preparation?
Because the alternatives do not exist as data in any system until someone models them. A proposed volume commitment, a different payment term or a second supplier is a hypothesis, and execution tools have no place to store hypotheses — they hold transactions: requests, bids, orders and invoices.
Each negotiation also turns on a different set of variables, so generic reports built on historical records do not fit the question being asked. A spreadsheet accepts arbitrary variables and arbitrary structure, which is why preparation work still ends up there.