# Agreeing the number — Radexus

> How to define a metric an AI project can actually be held to.

*Source: https://radexus.com/guides/agreeing-number/*

---

[Guides](https://radexus.com/guides/)  /  For CFOs

# Agreeing the number

How to define a metric an AI project can actually be held to.

- Written for: **For CFOs**
- Length: **12 pages**
- Reading time: **11 min**

In this guide
- [A definition has four parts](#h-0)
- [The exclusions people forget](#h-1)
- [Four questions for the vendor](#h-2)

[Download](https://radexus.com/downloads/radexus-agreeing-number.txt)

The exclusions people forget, the four questions that stop a vendor moving the goalposts later, and a template you can take into the room.

This guide is for the person who will be asked to approve the spend and then, eighteen months later, to say whether it worked. Almost all of the difficulty in that second conversation is created by decisions taken in the first one.

## A definition has four parts

-   **The computation.** Precise enough that two analysts working separately produce the same figure.
-   **The exclusions.** What is deliberately left out, and why. This is where every later dispute originates.
-   **The owner.** A named person whose figure this is, not a department.
-   **The version.** Because it will change, and when it does the change should be a release with a date, not a quiet edit.

The exclusions are where every later dispute originates, which is why they are written down first.

## The exclusions people forget

-   Tender or contract business, which follows different mechanics and swamps a median if left in.
-   Revisions of the same requirement, which inflate volume if counted separately.
-   Items past a staleness threshold, which should be marked dead rather than left open.
-   Volume won centrally and merely billed through a channel, which distorts every channel metric.
-   Intercompany and warranty transactions, which are not commercial events.

## Four questions for the vendor

One. Which single number moves, and who owns it? Two. Is it computable from data we already keep, with no new collection process? Three. What does the contract say happens if the pilot does not clear it? Four. Who reports the result, us or you?

On that last one, insist on your own team. A benefit computed by the vendor is a marketing claim wearing a spreadsheet.

**The test that settles it**If measuring the benefit requires a new data collection process, the benefit will never be measured. Everyone intends to. Nobody does, once the project is live and the team has moved on.

**Take it with you**

Full text, no form, no email capture. Print to PDF or download as plain text.

[Download text](https://radexus.com/downloads/radexus-agreeing-number.txt)Print or save PDF

**Use this on us**

Every question in this guide is one we expect to answer. If we cannot, that is information you should act on.

[Start a discovery](https://radexus.com/start/)

[Back

### All guides

](https://radexus.com/guides/)[Next

### Buying AI without buying a platform

](https://radexus.com/guides/buying-without-platform/)