Recent workLive in production

From policy PDFs to policy decisions

A rules first agent that tells up to 10,000 people who approves what, with the exact policy clause attached.

Visual for from policy pdfs to policy decisionsA large listed manufacturer with revenue above US$1 billion
Problem statement

What the client was up against

The procurement rulebook spanned 70+ SOPs, a delegation of authority matrix per vertical and a capex policy, about 340 files in all. Requesters and approvers searched by hand and many questions ended with a few process experts. An earlier document chatbot pilot was dropped over running cost.

Our approach

How we approached it

  1. Changed the design question from reading documents on every query to governing decisions
  2. Extracted policies once into reviewed, versioned decision tables
  3. Let the AI model interpret the question and explain the answer
  4. Kept documents as proof, with a citation to the exact clause
Solution we created

What we built

A Cortex policy agent that answers who approves what, which thresholds and quote rules apply and when a committee must sign off. It runs in the client's own Azure environment with its own model keys and a full audit trail.

Agents in the system

The multi agent team behind it

SourcesSAP ERP, Microsoft Azure, SharePoint policy library
Question agentWorks out amount, category, unit and policy version
Rules engineApplies versioned decision tables
Explanation agentWrites the answer in plain language
Citation agentLinks every answer to the exact clause
People decideReview, approve and act
Question agentWorks out amount, category, unit and policy version
Rules engineApplies versioned decision tables
Explanation agentWrites the answer in plain language
Citation agentLinks every answer to the exact clause
SAP ERPMicrosoft AzureSharePoint policy library
What it was built to change

The outcome it is designed for

Clear, cited policy answers for up to 10,000 people, far fewer questions landing with a few process experts and a lower running cost than a document chatbot.

This is live work without published results yet. We show the problem and the build, not numbers we have not measured.

Client names, detailed case studies, demos and references can be shared on request.

Looking for a similar solution?

Tell us your version of this problem. We will walk you through what we built and what a first pilot would look like for you.

Let's talk