Comparison
Evolinq vs Pactum
Pactum's agents negotiate commercial terms with suppliers autonomously and at a scale no buying team could reach. Evolinq's agents execute the orders that follow. Both are autonomous negotiating and communicating software; one settles what you pay, the other settles whether you get it.
What Pactum does well
Pactum made an unreachable population addressable. Walmart's tail was around 20% of a supplier base exceeding 100,000, sitting on standardised terms nobody had ever negotiated. Pactum's agents engage each supplier in an asynchronous text negotiation inside a pre-configured mandate, trading concessions across price, payment terms, rebates, discounts and allowances until a deal lands in the acceptable range.
The results are quantified and independently reported: Harvard Business Review documented agreements closed with 68% of suppliers approached, with each side gaining something it valued. Pactum reports around 3% average gain alongside payment terms extended by an average of 35 days, and 83% of suppliers describing the system as easy to use. It raised a $54M Series C in June 2025 and has extended from tail spend into recurring direct materials price-list negotiation.
Where the boundary sits
Pactum publishes its own use-case catalogue. It covers working capital and payment terms, rebates, discounts, allowances, contract renewals, spot buying, tactical sourcing, quote negotiation, retail price revisions and freight lanes. There is no use case for delivery date confirmation, order acknowledgement, expediting, supply assurance or shortage management.
One naming detail causes genuine confusion and is worth stating clearly: Pactum's Post-Sourcing Negotiation Agent means after the sourcing event, not after the purchase order. It captures commercial value left on the table once an RFQ closes. It does not touch order execution.
What flows back to the buyer's systems is agreed commercial terms into contract and P2P repositories — not order status, confirmed dates, or promise data against a PO line.
How Evolinq differs
Evolinq operates on the order, not the agreement. Once a price and terms exist and the PO is issued, Evolinq chases the acknowledgement, captures the committed date, detects the slip, flags the discrepancy, and keeps the ERP honest about what the supplier actually said.
Pactum makes the terms better. Evolinq makes the delivery certain. A buying team can want both, and neither substitutes for the other.
Pactum vs Evolinq
| Pactum | Evolinq | |
|---|---|---|
| Position | Before and around the PO — commercial negotiation | After the PO — execution |
| Variables | Price, payment terms, rebates, discounts, allowances | Dates, quantities, revisions, discrepancies |
| Writes back | Agreed terms to contract and P2P repositories | Confirmed dates and quantities to the ERP |
| Supplier interaction | Emailed invitation into a hosted negotiation interface | Reply in the supplier's own inbox, no destination |
| Overlap | Effectively none | Effectively none |
When the alternative is the better choice
- If the goal is extracting commercial value from a supplier base too large to negotiate with by hand — payment terms, rebates, tail-spend pricing — that is Pactum's category and Evolinq has no negotiation capability at all.
- Evolinq never discusses price.
Frequently asked questions
Pactum has a Post-Sourcing agent — does that cover PO execution?
No. "Post-sourcing" means after the sourcing event, capturing commercial value once an RFQ has closed. It is still a negotiation about terms, not an execution agent working an open order line.
Can Evolinq and Pactum run together?
Yes, and the sequence is natural: Pactum settles the commercial terms, the purchase order is issued against them, and Evolinq runs the follow-up until the line is confirmed and delivered.