Agent Value Ledger

Every agent must earn its place in the accounts

We start from the financial statements, not the technology, and hold each AI agent to the line it is meant to move, at its full cost.

The four pillars

How every agent is judged

The same four financial pillars appear in every engagement, on every industry page and in every board report.

01

Revenue growth

Conversion, pricing, retention and new services that AI makes possible, counted as gross profit, not headline revenue.

  • Revenue growth
  • Conversion improvement
  • Customer retention
  • Gross profit contribution
02

Operating cost efficiency

Hours, handoffs and rework removed from core processes, net of the full cost of running and supervising AI.

  • Cost per transaction
  • Process operating costs
  • Productivity gains
  • Verified expense reductions
03

Capital productivity

Cash released from inventory, receivables and work in progress, and better returns on the assets already owned.

  • Working capital
  • Inventory efficiency
  • Receivables
  • Asset utilisation
04

Risk reduction

Fewer losses, errors, incidents and compliance failures, counted only when there is evidence to show it.

  • Expected operating losses
  • Error and remediation costs
  • Compliance-related exposure
  • Control effectiveness
Four categories

Revenue | Operating costs | Capital | Risk

For each category: the baselines that matter, where AI can help, what the organisation needs, where value comes from, what it costs, how it is measured and attributed, and the oversight it needs.

Revenue

Financial baselines
Revenue by segment and channel, conversion rates, average price and discount, retention and churn, gross margin.
Potential AI use cases
Faster quotes and credit decisions, lead qualification, next-best-action prompts, pricing support, proactive service and retention.
Required capabilities
A clear growth strategy, joined-up customer data, consistent customer processes, and sales and service teams ready to work with AI.
Sources of value
Gross profit from extra conversion, better price realisation and retained customers. Counted as gross profit, not revenue.
Implementation and recurring costs
Integration with customer systems, data preparation, model usage, sales enablement and oversight of customer-facing outputs.
Key performance measures
Conversion, time to quote or decision, retention, revenue per customer or adviser, price realisation.
Measurement and attribution
Controlled roll-out or matched comparison groups wherever possible; otherwise before-and-after against a stated baseline, with other changes noted.
Risks and human oversight
Mis-selling, unfair or biased treatment, brand damage and inaccurate commitments. Customer-facing actions need clear limits and human review above thresholds.
Try the method

An adjustable ledger scenario

Hypothetical illustration. Change the assumptions to explore the method. The results are not a forecast, a quote or a client result.

The method

Five steps from the accounts to the agent

  1. 01

    Read the accounts

    We start with the annual report, management accounts and segment results, and compare them with listed peers. Where does the business trail its sector, and which lines carry the most weight?

  2. 02

    Map the value levers

    For each line that matters, we trace the operating drivers behind it and the decisions inside those drivers. Only then do we ask where an agent could move the number.

  3. 03

    Build a case for every agent

    Each proposed agent gets a one-page case: the line it moves, today's baseline, the expected effect, the full cost of running it, a named owner and the conditions under which it is switched off.

  4. 04

    Decide and sequence

    Cases are ranked as a portfolio, by value, time to evidence and risk, and each agent is placed on the delegation map: act, recommend, or inform only.

  5. 05

    Measure and assure

    After deployment, results are measured against the baseline with evidence an auditor would accept, and reported to the board as a quarterly ledger. Agents that do not earn their place are stopped.

Estimated versus realised

Two numbers, never confused

Before deployment, the ledger holds an estimate built from stated assumptions. After deployment, it holds realised results measured against the baseline. Both are reported, side by side, and only realised results are claimed.

Estimated

Business case

Built from the baseline and stated assumptions before an agent is approved. Used to decide and prioritise.

Realised

Measured result

Measured against the same baseline after deployment, with evidence an auditor would accept. Reported quarterly to the board.

Our discipline

Rules we hold to

Capacity is not a saving

Freed hours count only when they are redeployed to revenue work or replace hiring that would otherwise happen.

Count the full cost

Model usage, integration, data work, human oversight, validation and assurance all go on the ledger.

No baseline, no agent

If a result cannot be measured before deployment, it cannot be claimed after.

Risk benefits wait for evidence

Lower losses or fewer incidents are counted only once there is enough history to show them.

Roles kept separate

Our advisory work is independent. Where we also lead delivery, or use technology from a company in which we hold an interest, we say so in writing and never assure our own work.

Start with the accounts

Send us your latest annual report. We will show you where agents could move the numbers, and where they should not.

Start a conversation