Using Benchmarks in Budget Conversations
A benchmark in a budget meeting is a sharp tool, and it cuts whoever is holding it. You bring a comparison to show that your spend is reasonable, and the first question back is "so why are we above the peers?" You bring one to show that you are below the peers, and the second question is "then why do you need more?" Every comparison invites the opposite reading, and a finance director's job is to find it. That is not hostility. It is what the meeting is for.
This guide is about bringing a benchmark into that room and leaving with it intact. You will learn the order to present comparisons in, so the strongest evidence speaks first. You will learn what to say when your figure is above the group and when it is below. You will learn when "we are normal, and normal costs this much" is honest and when it is not. And you will learn how a benchmark and a budget case divide the work. There is a template paragraph for a budget document, and a rehearsal of the three challenges you will be asked, with answers.
One warning first. Nothing here makes a weak comparison strong. If the definitions do not match or the published figure has no source, this guide will only help you say so gracefully. That is worth something, but it is not a budget.
In this guide
- Why a benchmark cuts both ways
- The order of presentation
- When you are above the group, and when you are below
- "We are normal, and normal costs this much"
- Pairing the benchmark with a budget case
- The template paragraph
- The three challenges and their answers
- A war story and a checklist
- Where to go next
Why a benchmark cuts both ways
A benchmark cuts both ways because it is a comparison, and a comparison always has two sides. A benchmark, as the rest of this pillar uses the word, is one of your measurements set against a reference. That reference is your own past, a peer, or a published figure. In a budget meeting, whichever side you point at, the room will look at the other. If you say "our cost per device is in line with peers", the room hears "so it could be lower". If you say "our downtime is lower than last year", the room hears "so the current spend is working, and we can stop there".
This is why the comparison must arrive with its definitions and caveats attached, as support for a claim rather than as the claim itself. A benchmark that arrives naked will be dressed by whoever speaks next, and they will not choose the outfit you would have chosen. Am I Normal? What Benchmarking Can and Cannot Tell You lists the modest claims a benchmark can honestly carry. In a budget meeting, those are the only ones to make.
The same sharpness works for you. A finance director who has just sat through a slide of unsourced supplier figures will find a properly defined comparison from your own data refreshing. Precision is rare in these meetings. It gets noticed.
The order of presentation
Present comparisons in order of how much they can be trusted. That means your own trend first, peers second, and published figures last with their caveats spoken aloud. The order matters because the first number in a meeting sets the frame for everything after it. If the first thing the room hears is your own year-on-year figure, measured the same way twice, every later comparison is judged against something solid. If the first thing they hear is a survey figure, the rest of the meeting is spent defending it.
| Order | Comparison | What to say with it | What it earns you |
|---|---|---|---|
| 1 | Your own trend (same measure, same definition, previous period) | "Measured the same way, this went from X to Y." | Credibility. Nobody can dispute the reference. |
| 2 | Peer group (three to six similar organisations, definitions exchanged) | "Peers of similar size and hours, with matched definitions, reported a range of A to B. The differences we can account for are these." | Context. "We are not unusual" becomes defensible. |
| 3 | Published figure (source and definition known) | "A report from [source] gives C, defined as D, which differs from ours in this way, so it is context only." | Little, and only if the caveats are stated by you before anyone else states them. |
| — | Published figure (source or definition unknown) | Do not present it. If someone else does, ask for the source. | Nothing. |
The third row is the one people get wrong. And the mistake is not quoting a published figure; it is quoting one without saying its weakness first. "A supplier report gives this figure, though it does not say how down was defined, so I am treating it as background" removes the objection before it is raised. Present the figure as solid and let the finance director find the gap, and the gap becomes the meeting.
Keep it to three measures at most: critical-service downtime, alerts per person per week, and cost per monitored device cover most budget questions. A slide of twelve comparisons invites twelve arguments, and you will lose at least one for reasons that have nothing to do with the network.
When you are above the group, and when you are below
Above the group
If your figure is higher than the peers', there are two honest responses. You must pick one before the meeting, because picking during it looks like improvising. The first is to explain the difference by structure: the device mix, the hours covered, and the number of sites. There are also the things your organisation asks of the network that the peers' do not. "Our cost per device is above the group because we run three sites with remote probes and cover nights. The two peers with night cover are in the same range as us." That is a complete answer, provided it is true and you can show the peer data.
The second response is to admit it and propose the change. "Our alerts per person are above the group. We think the wireless thresholds are too tight, and the fix is on the roadmap for next quarter." That turns a weakness into proof that you are the person who finds weaknesses. Finance directors fund people who do that. The third thing, arguing that the peers' figures are wrong, is the one to avoid. That is because it is the moment the benchmark stops being yours and becomes a fight about theirs.
Below the group
If your figure is lower than the peers', the temptation is to claim credit. The honest move in that case is to check first whether the credit is yours. A lower downtime figure with a looser definition of down is not a better figure; it is a shorter clock. A lower cost per device with the people's time left out is not efficiency; it is arithmetic. Before you say "we are doing well", make sure the peer definitions match yours. Say so in the meeting: "our figure is below the group, measured the same way, and we have checked the definitions". Without that sentence, the first person to ask "how do they define it?" takes the credit away in front of everyone.
The second trap below the group is that a good figure invites "then the current budget is clearly enough". The answer is that the figure describes the past and the case describes the future. The trend says where you are, and the budget case says what changes if the estate grows or the staff do not. Which brings us to the argument every administrator eventually needs.
"We are normal, and normal costs this much"
The most useful sentence a benchmark can support in a budget meeting is "we are normal, and normal costs this much". That sentence is honest only when three things are true at once. The definitions were matched before any figure was exchanged. The peers genuinely resemble you in size, hours, and shape. And your own trend, measured the same way, is consistent with the peer range. That keeps the comparison from resting on a single lucky year. When all three hold, the sentence does real work: it shifts the question from "why do you cost this?" to "what would it take to cost less?", and the answer to that is usually a change the business would not accept.
When any of the three fails, the sentence is a bluff, and budget meetings are attended by people whose profession is finding bluffs. If the definitions were not matched, say "we have peer figures, but the definitions differ, so I am not leaning on them". If the peers are not really like you, say so. If your trend is one year long, say "this is one year under the new definition; next year we will have a comparison". Each of those costs a little in the room and buys back a great deal the first time someone checks.
The argument also has a limit: "normal" is not the same as "what the business needs". The targets your own organisation has agreed for its services, of the kind described under Internal SLAs, are what "enough" is measured against. A benchmark can show that you spend what similar organisations spend. Only the internal targets can show whether that is the right amount for yours. (It is possible to be perfectly normal and still missing the target. Plenty of organisations are, in at least one area, and the honest ones know which.)
Pairing the benchmark with a budget case
A benchmark and a budget case answer different questions, and the meeting goes well when each is asked to answer only its own. The benchmark supports "this is reasonable". Our spend, our staffing, and our outage rate are in the range of similar organisations or moving in the right direction. The budget case supports "this is needed". Here is the evidence of a problem, the consequence of leaving it, the options with their costs, and a decision by a date. Building a Budget Case From Monitoring Data is the guide to the second half. The benchmark is one paragraph inside it, not the whole document.
The pairing works because each covers the other's weakness. A budget case without a benchmark invites "is this a lot?" and has no answer. A benchmark without a case invites "so what?" and has none either. Together, the case says "the core switch runs out of capacity in the spring and here are three options". The benchmark adds "and the option we recommend keeps our cost per device where it has been for three renewals". The second sentence makes the first easier to approve.
Where the money should go, once approved, is a third question, answered in Where Monitoring Spending Actually Helps. The benchmark can tell you that your cost per device is in line. It cannot tell you whether the next unit of money is better spent on a second probe or a bigger licence tier. That is judgement, and judgement is what the meeting is paying you for.
Tip: put the benchmark paragraph after the evidence and before the options in the budget document. Readers who have just seen a graph of the problem are ready to hear that the fix is in a reasonable range. Readers who have just seen the price are not.
The template paragraph
The paragraph below is the form I use in a budget document to state a comparison. It is deliberately plain. It states every definition and every caveat before anyone can ask. And it ends by saying what the comparison does not support. That is the sentence that keeps the finance director on your side. Fill the brackets; delete the peer or published sections if you do not have them, rather than filling them with something weaker.
Comparison: [measure], [period] Our figure: [value], measured as [definition: what counts as down, what counts as a device, which hours are included, planned work in or out], taken from [source: availability report, discovery inventory, fortnight time log] on [date]. Our own trend: [previous period value] to [this period value], measured the same way. [One sentence on direction and the reason, if known.] Peer comparison: [N] organisations of similar [size, sector, hours], definitions exchanged in writing before any figure. Their figures ranged from [low] to [high]. Differences we can account for: [site count, hours covered, device mix]. Published figure, if quoted: [source and title], which defines the measure as [their definition]. [It matches ours. / It differs in X, so it is included as context only.] What this comparison supports: [we are not unusual / the trend is in the right direction / this area is worth a closer look]. What it does not support on its own: the amount requested. The case for that is set out in section [N].
The last two lines are the ones people are tempted to cut, and they matter most. "What it supports" keeps you inside the honest claims. "What it does not support" tells the reader you know the difference between a comparison and a case. A reader who knows that you know will argue with you less.
The three challenges and their answers
Three challenges come up in nearly every budget conversation where a benchmark is mentioned, and all three can be rehearsed. The answers below are the shape; the substance comes from your worksheet.
"Where did that number come from?"
The answer is a source, a definition, and a date, in that order, in one breath. "From the availability report in the monitoring console, counting the six critical services, all hours, planned work excluded, for the twelve months to the end of last month." For a device count, the source is the discovery inventory. If that count differs from the count on the licence, say so before someone finds it. Tracking Licenses and Usage is the guide to knowing your own count. For a people figure, the source is the fortnight time log. If the honest answer is "an estimate", say so and say what it was based on. Never dress an estimate as a measurement.
"Are they really like us?"
The answer is the list of things you matched on and the list you could not. "Their device count is similar, within a factor of two, and all have more than one site. Two of the four have night cover like ours. None of them runs a warehouse, which is why I have shown the range rather than an average." Naming the differences yourself is what makes the comparison survive. If you do not know the peers well enough to name them, the honest answer is "not closely enough to lean on". In that case, you fall back to your own trend, where the case should have been resting anyway.
"What if we did nothing?"
This challenge is not about the benchmark at all, and the mistake is to answer it with one. "Peers spend more" is not a consequence. The answer belongs to the budget case: the trend line and the date it crosses the limit. The answer also includes the outage that would follow, and what that outage costs in the business's own terms. If the business has agreed a figure for the cost of an hour of a critical service being down, the arithmetic is a single cell. In that case, put last year's downtime minutes in B2 and the business's own per-minute figure in C2:
=B2*C2
Use the business's figure, not yours. A cost per minute the finance director supplied is one the finance director cannot argue with. One you invented is what the meeting will spend twenty minutes on. If no such figure exists, ask for one to be agreed, and use the minutes on their own until it is. Everyone in the room knows what a minute is.
A war story: the slide deck and the definitions
Harbourview Clinic's steering committee met to decide the monitoring renewal, and a supplier's slide deck had reached the committee first. It had a chart of what "organisations like yours" spent on monitoring and staffing, with the clinic well above the line. The administrator, asked to explain, brought two sheets of paper. They were the benchmark worksheet from the first guide in this pillar, every definition filled in, and the fortnight time log. She asked the committee what the slide meant by a device and by an administrator, and the room agreed it did not say. She then showed the clinic's own figures under stated definitions and the trend across three renewals. She also showed two peers with night cover whose figures sat in the same range. The chair asked whether the supplier's chart could be redrawn with the definitions added, and the supplier said it would take a while. The renewal was approved on the clinic's figures. And the slide was not mentioned again, which is the best thing that can happen to a slide.
The committee was not naive. They had a chart and no alternative, and the administrator gave them one that could be checked. That is the whole technique: a worksheet, a time log, and the nerve to ask a polite question in a room where nobody else has.
The checklist
Before a benchmark goes into a budget document or a meeting, check it against this list.
- The comparison is presented in order: own trend, then peers, then published figures with caveats spoken first.
- Every figure carries its source, its definition, and its date, and I can say all three in one breath.
- No published figure without a known source and definition appears anywhere in the document.
- If we are above the group, I have chosen in advance between explaining the structure and proposing the change.
- If we are below the group, I have checked that the peer definitions match before claiming any credit.
- "We are normal" is only claimed when definitions were matched, the peers resemble us, and our own trend agrees.
- The benchmark paragraph says what it supports and what it does not, and the amount requested is argued in the case, not the comparison.
- The "what if we did nothing" answer uses the business's own cost figure or plain minutes, never one I invented.
- The three challenges have been rehearsed aloud with someone who enjoys asking them.
Where to go next
The comparisons this guide presents are built in the rest of the pillar. Find the worksheet and the honest-claims table in Am I Normal? What Benchmarking Can and Cannot Tell You. Find the uptime figures and the peer-group email in Benchmarking Uptime and Incident Counts Fairly. And find the cost and staffing ratios in Benchmarking Monitoring Spend and Staffing Without Inventing Numbers. For the parts of the practice a budget meeting never asks about, Healthy Signs is the self-assessment. All of them are under Am I Normal? Benchmarking Your Network and Monitoring Practice. The wider craft of putting monitoring evidence in front of management is under Translating Monitoring Data for Management.
Put this into practice with SysPeep Monitor
The figures that survive a budget meeting are the ones with a source, a definition, and a date. Most of them come out of the monitoring. SysPeep Monitor keeps availability and alert history as reports in one web console. Its auto-discovery gives you a device count you can defend against the one on the licence. The free trial installs on any Windows machine in minutes.
Download Free TrialLearn About SysPeep