Built for the Center of Excellence.

You set the strategy, write the policies and decide the ways of working. Digital workers run them on every request, in every region, from the day you decide.

  • 1,000,000+requisition checks since March 2026
  • 99%agreement with a customer's own reviewers before it acted alone
  • 122,000+requisitions a year absorbed with no added headcount
  • <1 dayfrom request to purchase order

Set the rules for every digital worker

Say it once, in plain language. Every digital worker runs it from that day.

  • Built from the policies and category strategies you already have
  • Tested against your own reviewers in observer mode before it acts
  • Yours to edit, version and widen, with no code and no ticket
Illustration: the Center of Excellence asks the policy assistant to lower the three-quote threshold to $25,000 for all indirect categories in the US and to start Europe in observer mode. The assistant confirms rule v5 is live in the US from now and that Europe will run it in observer mode for two weeks before it switches on

Then digital workers run every request end to end

Pactum's AI agents take every request from intake to purchase order, following your rules.

  • Every request checked against policy the moment it is raised
  • Sourced and negotiated the way your category strategy says
  • Written back to Coupa or SAP Ariba with the decision trail
<1 minto check a request against every policy you have
Illustration: a $27,500 facilities repair requisition in Dallas is checked by the alignment agent. The supplier record, cost center and budget pass, the amount is above the $25,000 three-quote threshold in rule v5, and the tactical sourcing agent has sent an RFQ to four approved suppliers

Replace your BPO with digital workers

Save the outsourcing fees. Your Center of Excellence governs requisition review through sourcing and negotiation, run by digital workers, with no added headcount.

  • Routine requisition review replaced outright, at any volume
  • Quotes and negotiations run on every request in scope
  • Observer mode alongside your current provider, so the numbers decide the renewal
1,000,000+requisition checks since March 2026
Illustration: the Tactical Sourcing Agent running a queue of RFQs at once, with counts of requests in market, awarded this week and waiting on a buyer

Digital workers for the Center of Excellence

One rulebook gives every one of them its rules. Your Center of Excellence decides which run, where, and how far.

  • Intake Agent

    Turns a request in plain words, in Teams or your P2P, into a clean, correctly coded requisition and hands it on.

  • Alignment Agent

    Turns your policies and strategy into one rulebook, checks every request against it and gives every digital worker its rules.

  • Single-Source Negotiation Agent

    Negotiates every single-source requisition before the PO exists, for better price, payment terms and working capital.

  • Tactical Sourcing Agent

    Runs the RFQ, drives the competition and negotiates the final terms on buys your team never had time to run.

  • Advanced Sourcing Agent

    Runs the multi-round events your buyers used to carry alone, built on your category strategy.

  • Post-Sourcing Negotiation Agent

    Takes the bids from your closed RFx and negotiates a final offer with every shortlisted supplier before you award.

“Days of manual reviews became minutes. Faster decisions, better compliance, and real efficiency gains.”
Rob Baillie · Head of Procurement · SUEZ UK

Frequently asked questions from procurement Centers of Excellence

Who maintains the rules, the Center of Excellence or Pactum?

The Center of Excellence maintains the rules. Your team writes and edits them in plain language, tests a new version against live requests with no effect, and switches it on. Pactum helps with the first rules and then steps back.

What resource does a Center of Excellence need to run AI agents?

A Center of Excellence runs AI agents with a small team who own the rulebook alongside their existing role. They write and test rules, read each rule's performance and decide when a workspace moves from observer mode to action. The routine checking the center did by hand is replaced outright, so the time comes from there.

Does Pactum fit our AI governance model?

Pactum is built for a governed rollout. Every rule runs in observer mode first, is tested against your own reviewers' decisions and reports its agreement rate before it acts. Every check and decision is recorded, every rule is versioned, and Pactum is SOC 2 Type 2 compliant and ISO/IEC 27001:2022 certified. See the Pactum Trust Center.

How often do procurement policies change, and what happens when they do?

Procurement policies change more often than an organization can retrain its buyers. When a threshold, a supplier list or a category rule changes, the center edits the rule once, tests the new version and switches it on. Every request from that moment is checked against it, with no retraining cycle between the decision and the behavior.

Can we start inside the center and roll out at our own pace?

Yes. Most centers start with a centralized rollout, inside the center and on a few categories or one region, rather than putting a new tool in front of several hundred buyers on day one. A rule applies wherever you point it, so widening the scope is a change to where the rule applies, not a new project, and the center keeps revising thresholds as it sees the results.

What does observer mode show us before anything is switched on?

Observer mode runs a rule on live requests with no effect and reports how often it agreed with your own reviewers, what it would have caught, and where it would have raised a false alarm. The center reads those numbers per rule and decides when a workspace moves from observing to advising to acting, which is how one procurement operations team put it: "you can do the observer mode by specific policies".

How is this different from uploading the policy PDF to Copilot?

A policy in Copilot answers a question when someone asks. A rule in Pactum checks every request whether anyone asks or not. The AI agent reads the request in Coupa or SAP Ariba, applies each written rule the same way on every request, sends the reason and the fix back to the requester and records the decision.

Can thresholds and approved suppliers live in Pactum rather than in Coupa or SAP Ariba?

Yes. Thresholds, approved suppliers and category rules live in the Pactum rulebook, and the master data stays in your P2P. A rule reads the request in Coupa or SAP Ariba and the result goes back to the record. For Coupa the write-back and the logged decision trail are documented, and SAP Ariba is supported as a named approver step. See integrations.

How does a Center of Excellence enforce policy without retraining everyone?

A Center of Excellence enforces policy by turning it into rules that AI agents apply on every request. The center decides the rule once and it runs everywhere from that day. A requester learns the rule when a request comes back with the reason and the fix, in the same conversation. Read how a Center of Excellence scales procurement without adding headcount.

Which spend does Pactum work on?

Pactum works on indirect spend: the goods and services a company buys to run itself, such as IT, facilities, MRO and professional services. AI agents run each request end to end, from intake and the policy check to sourcing, negotiation and the purchase order, inside Coupa or SAP Ariba where each agent is live. That includes the requests outside your catalog and contracts, where no price was agreed in advance.

See your own policy run on a real request.

Bring one rule and one requisition from your queue, and we'll run the demo on them.