AGX in production

Proven controls for measurable recovery.

These are not autonomous agents guessing what to do. They are governed operational controls that survived the AGX Control Optimization and Falsification Loop. The agent is the bounded operational surface that executes inside the proven gate.

AGX Agent

Billing Readiness Agent

AGX tested the Billing Readiness Agent before production, promoted only the guardrails that recovered leakage without flooding finance with rework, and kept invoice authority with the finance team.

Delivery-to-Cash / Revenue Operations Billing Readiness Agent 10,000 training cases 2,000 held-out validation cases Shadow-tested guardrails Finance approval preserved
The trade-off

Strict billing checks can catch leakage but drown finance in manual rework. Loose rules move faster but let revenue escape.

The guardrail

AGX shadow-tested candidate policies and promoted the combination that maximized recovery while preserving finance authority and speed limits.

Agent surface

The agent prepares evidence, pauses risky cases, and routes questions to owners. It cannot release invoices, change terms, book revenue, or bypass approval.

$5.68M baseline identified revenue leakage
$2.16M recoverable leakage validated in historical replay
38% reduction in eligible-case leakage
100% promoted controls tied to source evidence
0 invoices released without mandatory finance approval

The Problem: The Trade-Off Between Leakage and Rework

Revenue operations teams face a binary choice with automated billing: catch every discrepancy and drown finance teams in manual rework and delayed cash flow, or loosen the rules and accept revenue leakage.

Deploying a raw AI agent to fix billing errors usually results in the former. The agent aggressively flags minor issues, halting invoice releases and creating unmanageable cycle-time delays. AGX was used to deploy an autonomous billing agent that aggressively recovers leakage, but strictly adheres to finance policies and operational speed limits.

The Solution: Shadow-Tested Agent Guardrails

Instead of deploying an untested AI agent into production, AGX was used to build, test, and enforce strict operational guardrails for the Billing Readiness Agent.

Before the agent ever touched a live invoice, AGX shadow-tested candidate policies against 10,000 historical delivery-to-billing records and 2,000 held-out validation cases. The system automatically rejected guardrails that caused excessive manual rework or unacceptable cycle-time delays. It promoted the exact combination of checks that maximized revenue recovery while preserving finance authority.

How It Works

The Billing Readiness Agent operates inside a strict, multi-step policy gate. It executes a defined sequence of checks before an invoice can be marked ready.

Delivery Evidence Check verifies that completed work has the required worklogs, milestone proofs, and delivery evidence.

Contract-Rate Reconciliation compares billed rates against contracted terms to catch stale rate-card underbilling.

Scope Recovery Check identifies completed out-of-scope work that lacks approved recovery evidence.

Automated Packet Generation pauses the workflow when a discrepancy is found, compiles the evidence, drafts specific questions for the account owner, and routes the case for human review.

Strict Boundaries: What the Agent Cannot Do

Autonomy requires strict limits. The Billing Readiness Agent is designed to prepare and flag, never to execute financial transactions.

It cannot release, send, or finalize invoices.

It cannot change contract terms, alter invoice amounts, or approve discounts.

It cannot book revenue or recognize income.

It cannot bypass, waive, or override mandatory finance approvals.

Promoted guardrail

Shadow-Tested Billing Readiness Guardrail

An invoice cannot be marked ready when delivery evidence, contract-rate terms, scope recovery, or approval evidence fails the tested policy gate.

Trigger
Missing delivery evidence, stale rate-card underbilling, unresolved out-of-scope work, or missing mandatory approval evidence.
Effect
Pause the workflow, prepare the review packet, draft owner questions, and route the case for human review.
Boundary
The agent prepares and flags; it never releases invoices, changes terms, books revenue, or bypasses finance approval.
Rejected guardrail example

Overbroad Discrepancy Halt

A raw rule that stops too many minor invoice discrepancies would recover some leakage but create unacceptable finance rework and cash-flow delay.

Trigger
Any small mismatch between delivery, contract, or invoice records.
Effect
Halt invoice readiness too often and overload finance with manual review.
Boundary
AGX rejected this path because recovery cannot come at the cost of breaking the billing workflow.
Falsification proof What AGX tested, rejected, and promoted
World

AGX shadow-tested candidate policies against 10,000 historical delivery-to-billing records and 2,000 held-out validation cases before the agent touched a live invoice.

Mechanism

A raw AI billing agent would flag too many minor issues, halt invoice releases, and create cycle-time delays that finance cannot absorb.

Control

The agent should pause invoice readiness only when delivery evidence, contract-rate terms, scope recovery, or approval evidence fails the tested policy gate.

Result

AGX identified $5.68M of baseline revenue leakage and validated $2.16M of recoverable leakage in historical replay, with a 38% reduction in eligible-case leakage.

Boundary

The agent prepares and flags. It cannot release, send, or finalize invoices; change contract terms; alter invoice amounts; approve discounts; book revenue; or bypass mandatory finance approvals.

Composed control The Billing Readiness Agent operates inside a strict, multi-step policy gate.

The agent executes a defined sequence of checks before an invoice can be marked ready. AGX promoted the exact combination that recovered leakage without creating unacceptable rework or cycle-time delay.

  • Delivery Evidence Check

    Confirms completed work has the worklog, milestone, and delivery proof needed for billing review.

  • Contract-Rate Reconciliation

    Compares billed rates against contract terms before the invoice candidate is treated as ready.

  • Scope Recovery Check

    Finds completed out-of-scope work that lacks approved recovery evidence.

  • Automated Packet Generation

    Compiles the evidence, drafts specific questions for the account owner, and routes the packet for human review.

The agent can prepare and flag. It cannot execute financial transactions.

Control record How the gate is built and operated
  1. Delivery Evidence Check

    Verifies that completed work has the required worklogs, milestone proofs, and delivery evidence before an invoice can be marked ready.

  2. Contract-Rate Reconciliation

    Compares billed rates against contracted terms to catch stale rate-card underbilling and rate mismatches.

  3. Scope Recovery Check

    Identifies completed out-of-scope work that lacks approved recovery evidence.

  4. Automated Packet Generation

    When a discrepancy is found, the agent pauses the workflow, compiles source evidence, drafts owner questions, and routes the case for human review.

  5. Finance Approval Boundary

    The agent can prepare and flag. Finance still decides whether the invoice can be released.

Authority and audit What the agent can do and what stays protected
Agent work

What the agent can apply

  • Delivery Evidence Check verifies that completed work has the required worklogs, milestone proofs, and delivery evidence.
  • Contract-Rate Reconciliation compares billed rates against contracted terms to catch stale rate-card underbilling.
  • Scope Recovery Check identifies completed out-of-scope work that lacks approved recovery evidence.
  • Automated Packet Generation pauses risky cases, compiles evidence, drafts owner questions, and routes the packet for human review.
Protected authority

What stays protected

  • Cannot release, send, or finalize invoices
  • Cannot change contract terms, alter invoice amounts, or approve discounts
  • Cannot book revenue or recognize income
  • Cannot bypass, waive, or override mandatory finance approvals
Control record

Every run leaves a usable control record.

10,000 historical delivery-to-billing records 2,000 held-out validation cases $5.68M baseline identified revenue leakage $2.16M recoverable leakage validated in historical replay 38% eligible-case leakage reduction 100% promoted controls tied to source evidence 0 invoices released without mandatory finance approval
AGX Agent

Vendor Cost Drift Agent

AGX continuously monitors delivery-cost and forecast-lock workflows, generates safety policies for margin drift, shadow-tests them against historical data, and enforces bounded review workflows while keeping finance and delivery authority intact.

Finance & Delivery Operations / Margin Management Vendor Cost Drift Agent 12,000 training cases 2,500 held-out validation cases Shadow-tested guardrails Forecast ownership preserved
Operational gaps

Margin leakage appears when staffing mix drifts, contractor costs rise, offshore delivery mix erodes, bench time accumulates, or fixed-fee work absorbs unplanned rework.

Shadow-tested guardrail

AGX tested candidate policies against history and rejected rules that created false positives, immaterial review burden, or forecast-lock delays.

Agent surface

The agent prepares cost-driver evidence, routes material drift to the right owner, and waits for clearance. It cannot update forecasts, approve contractors, or change staffing.

$30.75M baseline eligible margin leakage identified
$6.77M margin recovery validated in replay
22% validation-set leakage reduction
1,868 eligible cases routed before forecast lock
0 forecast updates or staffing changes made by the agent

The Operational Reality

Vendor cost drift does not usually come from one obvious failure. It happens in the operational gaps: staffing plans drift from reality, contractor usage rises quietly, offshore mix erodes, bench time accumulates, and fixed-fee work absorbs rework that no one clears before forecast lock.

Traditional solutions force a choice: deploy autonomous AI agents that risk changing forecasts or commercial assumptions without approval, or rely on humans to manually write and enforce variance rules that are too slow to scale.

The Vendor Cost Drift Agent eliminates this trade-off. It acts as a continuous policy engine that extracts failure patterns from execution traces, drafts candidate guardrails, validates them through historical replay, and enforces margin-readiness review at runtime while keeping human authority intact.

How the Vendor Cost Drift Agent Works

Pattern Extraction & Policy Generation: AGX analyzes historical delivery-cost and forecast-lock traces to identify exactly where margin leaks. It does not guess; it extracts recurring failure patterns such as staffing mix drift, contractor substitution, bench leakage, and fixed-fee rework, then drafts candidate safety policies to stop them.

Historical Shadow-Testing: before any policy goes live, AGX tests it against 12,000 historical training cases and 2,500 held-out validation cases. It rejects policies that create excessive false positives, immaterial owner review, or unmanageable forecast-lock delays.

Bounded Execution & Evidence Preparation: once deployed, the agent operates strictly inside approved boundaries. When a project triggers a policy, the agent confirms staffing and cost evidence, compares actuals against the approved plan, identifies unresolved drift, and compiles the cost driver, exceptions, and owner questions into a single finance and delivery review packet.

Hard System Boundaries: What the Agent Cannot Do

Trust is built on strict limitations. The Vendor Cost Drift Agent is a bounded operational surface. It prepares, requests, routes, and waits. It never silently takes authority.

No forecast updates: the agent cannot update forecasts, change forecast-ready status, or alter forecast assumptions by itself.

No staffing changes: the agent cannot change staffing plans, approve role substitutions, or assign people.

No spend authority: the agent cannot approve contractors, commit vendor spend, or alter commercial terms.

Finance and delivery approval preserved: every flagged item requires explicit owner clearance before the workflow moves forward.

Validated Results: Proven in Replay

AGX validated the Vendor Cost Drift Agent through historical replay before deployment.

$30.75M baseline eligible margin leakage was identified in historical data.

$6.77M of margin recovery was validated in replay.

The promoted control gate reduced validation-set leakage by 22%.

1,868 eligible cases were routed before forecast lock.

The agent made 0 forecast updates or staffing changes on its own.

The Compounding Asset

The system learns from the controls it rejects. If a candidate margin rule floods forecast owners with immaterial variances, that failure is recorded in the Falsified Hypothesis Ledger.

The next policy search is narrowed so AGX does not keep proposing controls with the same operational penalty. Knowing exactly what failed ensures the system only scales what actually works.

Promoted guardrail

Vendor Cost Drift Margin-Readiness Gate

Before forecast lock, a project with material staffing, vendor-cost, contractor, bench, or fixed-fee drift must clear a margin-readiness gate before forecast-ready status is accepted.

Trigger
Senior mix above plan, offshore mix below plan, unplanned contractor usage, bench leakage, fixed-fee rework, or unexplained vendor-cost variance.
Effect
Pause forecast readiness, prepare the margin review packet, draft owner questions, and route the case for finance or delivery clearance.
Boundary
The agent prepares and routes; it never updates forecasts, approves spend, changes staffing, or bypasses owner approval.
Rejected guardrail example

Overbroad Variance Halt

A raw rule that blocks every variance would catch some drift but flood forecast owners with immaterial reviews and delay forecast lock.

Trigger
Any mismatch between plan, actual staffing, vendor cost, utilization, or forecast records.
Effect
Halt forecast readiness too often and overload finance and delivery owners with manual review.
Boundary
AGX rejected this path because margin protection cannot come at the cost of breaking the forecast workflow.
Falsification proof What AGX tested, rejected, and promoted
World

AGX shadow-tested candidate policies against 12,000 historical delivery-cost cases and 2,500 held-out validation cases containing planned hours, actual hours, staffing mix, offshore mix, contractor usage, bench time, rework, forecast variance, and margin leakage.

Mechanism

A raw AI agent would flag every variance, overwhelm forecast owners, and slow forecast lock. A weak rule would miss real margin erosion until it shows up too late.

Control

Before forecast lock, any project with material staffing, vendor-cost, contractor, bench, or fixed-fee drift must clear a margin-readiness gate: explain the cost driver, attach evidence, and obtain owner clearance before forecast-ready status is accepted.

Result

AGX identified $30.75M of baseline eligible margin leakage, selected the staffing-drift margin-readiness gate, routed 1,868 eligible cases before forecast lock, and validated $6.77M of margin recovery with a 22% leakage reduction.

Boundary

The agent prepares, requests, routes, and waits. It cannot update forecasts, approve contractors, change staffing plans, alter contracts, commit spend, or write to financial systems.

Composed control The Vendor Cost Drift Agent operates inside a strict, multi-step policy gate.

The agent executes a defined sequence of checks before a project can be treated as forecast-ready. AGX promotes only the guardrail mix that protects margin without creating unacceptable forecast-owner burden.

  • Staffing Mix Check

    Detects when senior staffing or offshore delivery mix moves materially away from the approved delivery plan.

  • Contractor Cost Check

    Flags unplanned contractor usage when it changes cost-to-serve before forecast lock.

  • Fixed-Fee Margin Check

    Routes fixed-fee projects with unresolved rework or cost drift for owner clearance.

  • Bench Leakage Reconciliation

    Requires utilization evidence when bench time is distorting project margin.

  • Margin Review Packet

    Combines the cost driver, source evidence, exceptions, and owner questions into one review packet.

The agent can prepare and route a margin review. It cannot update forecasts, approve contractors, change staffing, alter contracts, or write financial records.

Control record How the gate is built and operated
  1. Pattern Extraction & Policy Generation

    AGX analyzes historical delivery-cost and forecast-lock traces to identify where margin leaks: staffing mix drift, contractor substitution, offshore mix loss, bench leakage, and fixed-fee rework.

  2. Historical Shadow-Testing

    AGX tests each candidate guardrail against 12,000 training cases and 2,500 held-out validation cases before it can affect forecast operations.

  3. Guardrail Rejection

    Policies that create excessive false positives, immaterial owner review, or forecast-lock delays are rejected and recorded.

  4. Bounded Execution & Evidence Preparation

    When material drift triggers a policy, the agent compiles staffing, cost, utilization, forecast, and owner evidence into a single review packet.

  5. Owner Clearance Boundary

    The agent can require review and prepare the evidence. Finance and delivery owners still decide whether the forecast, staffing plan, or remediation changes.

Authority and audit What the agent can do and what stays protected
Agent work

What the agent can apply

  • Pattern Extraction & Policy Generation extracts recurring drift patterns and drafts candidate safety policies for margin protection.
  • Historical Shadow-Testing tests each policy against training and validation cases before it reaches live workflow enforcement.
  • Bounded Execution requires review for material staffing, contractor, bench, or fixed-fee drift without making the commercial decision.
  • Evidence Preparation compiles cost drivers, source evidence, exceptions, and owner questions into one margin review packet.
Protected authority

What stays protected

  • No forecast updates by the agent
  • No contractor approvals or spend commitments
  • No staffing-plan changes
  • No contract changes or commercial concessions
  • Finance and delivery owner clearance preserved
Control record

Every run leaves a usable control record.

12,000 historical delivery-cost training cases 2,500 held-out validation cases $30.75M baseline eligible margin leakage identified $6.77M margin recovery validated in replay 22% validation-set leakage reduction 1,868 eligible cases routed before forecast lock 0 forecast updates or staffing changes made by the agent
Compounding asset

The system learns from the controls it rejects.

In both cases, AGX did not just find the rules that worked. It recorded which controls failed, why they failed, and under what conditions the surviving gates actually moved the metric.

Falsified Hypothesis Ledger

If a candidate billing rule increases finance rework by 40%, that failure becomes a reusable constraint. The next search is mathematically narrowed so AGX does not keep proposing controls with the same cycle-time penalty.

Knowing what failed narrows what AGX tries next.
Hard system boundaries

What stays protected when agents operate the gate.

AGX separates the control engine, the operational surface, and human authority. The agent can prepare, request, route, and wait. It cannot silently take authority.

What AGX applies

Control engine responsibilities

  • Evidence quality computation before claims are trusted
  • Revalidation when operating mix drifts
  • Sealed audit chain for situation, recommendation, policy check, owner decision, action, and outcome
What the agent cannot touch

Protected authority

  • No auto-invoicing, revenue recognition, or forecast updates
  • No bypass of finance, delivery, forecast-owner, or approval authority
  • No contract changes, waived approvals, or approved discounts
  • No guessing when policy is missing or ambiguous