---
id: KB-CD-014
url: https://app.codecontract.io/help/credits-and-billing/explaining-the-cost-to-management
idioma: en
categoria: creditos
audiencia: administrador
nivel: intermedio
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-CD-010, KB-CR-013]
citadoPor: [KB-CD-007]
---

# Explaining the cost to management

_The figure does not convince on its own. What convinces is what it is compared against._

**Responde a:** justifying platform spend · return on documentation investment · defending the budget · comparing cost with what it saves

When someone in management asks what this costs, the usual answer is a monthly figure. And a figure on its own, with nothing beside it, always looks expensive: there is no context to judge it against.

## The three comparisons that work

| Comparison | How to calculate it | When it convinces |
| --- | --- | --- |
| Hours recovered | How often it was done by hand × time × hourly cost | Always; the easiest to accept |
| An incident avoided | What the last documentary problem cost | When there was a recent one everyone remembers |
| What a client requires | The contract that is not signed without this | The most powerful, and the least used |

> [!IMPORTANT]
> The third turns the conversation from cost into requirement. If a large client demands to audit your documentation, this stops being an efficiency improvement and becomes a condition for invoicing that client — and that is no longer discussed at the same table.

## How to prepare it without inventing anything

1. **Count the real work it replaced** — "Chasing forty suppliers every quarter" is measurable; "we are more organised" is not.
2. **Use real consumption, not estimates** — With the breakdown. A figure that can be opened up gets questioned less.
3. **And say what has not changed too** — It lends credibility to the rest and pre-empts the awkward question later.

> [!WARNING]
> Do not promise headcount savings. They almost never happen — people stay, doing something else — and promising it turns a real improvement into a broken promise remembered for years.

## What management usually asks

**En corto**

- "What happens if we drop it?" — Answer with what you would stop being able to prove, not with what it would cost.
- "Can we spend less?" — Yes, and the breakdown says exactly where.
- "Do people actually use it?" — The best question, answered with usage data.

The third is the one always worth being able to answer. A tool that is paid for and unused is a cost; one used daily by fifteen people is infrastructure.

> [!NOTE]
> If consumption is split between group companies or departments, bring that breakdown too: many objections disappear when each area sees its own instead of an abstract total.

**What if the saving is not obvious yet?**

Say so: three months in, the honest thing is to show usage rather than return.

**How do I value an avoided risk?**

With what it cost last time it happened, if you have the figure.

**Should the full breakdown be shown?**

Yes. What cannot be opened always looks more expensive than it is.

## Ejemplos

**A manager presents the monthly cost and management finds it high.**

- Adds the chasing hours it replaces and their largest client's requirement

→ The conversation shifts from what it costs to what would happen without it.

**The cost is explained without comparing it to anything.**

- Compares it with the hours previously spent

→ The conversation has two figures.

**Management asks what is obtained in return.**

- Brings consumption alongside the period's output

→ Cost is read next to what it produced.

**One month's rise is presented without context.**

- Explains which campaign or process caused it

→ The spike stops being an alarm.

**Nobody knows which department consumes what.**

- Presents the breakdown by department

→ The conversation happens with each of them.

**A reduction is asked for without knowing where.**

- Shows which activities weigh most

→ The reduction is decided on a basis.