Building the business case for Strategic Meetings Management

Most business cases for Strategic Meetings Management fail in the same way. They open with a saving, the saving is built on an assumption, somebody in the room asks where the assumption came from, and the rest of the case never gets heard.

This guide is about avoiding that. It covers who you are actually writing for, how to build a baseline you can defend when the underlying data is poor, which benefits are worth claiming and which are worth arguing rather than quantifying, and how to present an ask that survives contact with a finance director.

It contains no savings percentages, no benchmark figures and no industry statistics — deliberately, and we explain why below. What it contains instead is a method for building your own number from your own data, which is the only version that will hold up when challenged.

A business case addressed to “the business” is addressed to nobody. The people who will decide this care about genuinely different things, and the same proposal reads as essential to one and as overhead to another.

Write the core document once, then write a short covering section for whoever is the primary decision-maker. If you cannot name that person, the case is not ready.

A finance director is not primarily assessing whether meetings management is a good idea. They are assessing whether you have done the work properly, because if the method is sound the conclusion usually follows, and if it is not, nothing else in the document matters.

That means leading with what you can evidence and stating what you cannot. A baseline described as approximate, with the gaps named, is treated as credible. A precise-looking figure that turns out to have excluded accommodation or catering is treated as a reason to distrust everything else in the paper.

The finance-specific argument that tends to land hardest is not savings at all. It is committed but uninvoiced exposure — the cancellation and attrition liability the organisation has already signed up to, spread across contracts held in individual inboxes, which does not appear in any system they currently see. That is a genuine control gap and it is theirs to care about.

An operations director hears “centralise” and thinks about friction. Their reasonable worry is that a programme adds a step to a process that currently works, for the benefit of people who do not have to live with the step.

Answer that directly rather than around it. State the response commitment. State that no approval is being added that was not already required — the existing thresholds stay exactly as they are, which is the point of the meetings approval process mirroring delegated authority rather than inventing its own. And make the operational argument that belongs to them: capable people are currently spending working days ringing round venues, and that time is a real cost that appears in no budget.

This is also where to be honest that some autonomy is being reduced. Pretending otherwise insults an audience that can see it perfectly well, and the concession makes the rest of the case more credible.

Procurement usually needs the least persuading about the principle and the most help with the specifics. The argument writes itself: here is a category of meaningful size that is bought by dozens of people with no aggregated view, no negotiated terms and no supplier management — disciplines that are applied as standard to every other category of comparable value.

What procurement needs from the case is the evidence that makes it actionable: supplier concentration, group-level aggregation, the number of separate signatories, and the proportion of activity that currently touches procurement at all. See meetings spend management and supplier management.

Build the problem statement entirely from evidence you can actually gather, and gather it before you write anything. Almost all of it is available from systems your organisation already has.

Note what is not on that list: any claim about what this is costing you. The problem statement establishes that the organisation cannot see or control a category — which is the argument meetings spend visibility makes in full. The cost of that comes later, carefully, and in a form you can defend.

Structural facts of this kind are also harder to argue with than financial ones. Nobody disputes how many people hold signing authority. Everybody disputes a savings estimate.

Your data will be poor. Meetings spend hides under venue names that look like hotels, in card transactions coded to entertainment, inside travel bookings, in catering invoices and in departmental budgets that never touch a purchase order. That is normal and it is not a reason to delay.

What matters is not precision but defensibility. A baseline is defensible when a sceptical reader can see exactly how it was built, what it includes, what it excludes and how confident you are in each part. The method is set out in full in how to measure meetings spend; what follows is what the business case specifically needs.

Rather than presenting a single figure, present the baseline in three layers. This is the technique that most reliably survives challenge, because it shows the reader precisely where the uncertainty is instead of burying it.

Then make the argument that the layering itself supports: the reason the organisation has three tiers of confidence about its own expenditure in this category is the absence of the programme you are proposing. Present it as evidence rather than as an apology for imperfect data.

Write the limitations into the baseline section rather than a footnote. Name what you could not see, the period covered, whether it was representative, and what would change the number materially.

This feels like weakening your own case and does the opposite. A reader who finds a stated limitation reads the author as careful. A reader who finds an unstated one reads the author as either careless or selective, and there is no recovering from the second.

A business case built on a number you cannot defend collapses at the first challenge — and it collapses in a way that makes the second attempt considerably harder, because the next version is read by people who remember the first.

Separate benefits into three groups and treat each differently: those you can quantify from your own data, those you can size directionally, and those you should argue rather than monetise. Mixing them is what makes a case look inflated.

The mistake to avoid is attaching invented figures to the last three categories to make the total look better. A reader who sees a monetised duty-of-care benefit stops believing the quantified ones. Say plainly: these are the benefits we can size, these are the benefits we are asserting, and we are not going to dress the second group up as the first.

At some point someone will ask what this is worth. You need an answer, and the answer cannot be a percentage you read somewhere.

There are three honest routes, in descending order of strength.

A business case with no cost section is not a business case. It is also the fastest way to lose a finance director, who has read enough proposals to know that every initiative costs something and will assume you are hiding the figure rather than that it does not exist.

Include a risk section and put the real risks in it. A risk register containing only risks you have already mitigated is read as decoration.

You will get this objection, often from the most senior person in the room, and it is usually true. Do not deflect it. It is the most useful thing anyone will say to you, and how you handle it decides the meeting.

The productive response has three parts.

The structural differences worth naming are set out in centralising meetings and events, and the sequencing argument behind them in implementing Strategic Meetings Management. Both are worth reading before the meeting rather than after it.

There is a version of this objection that is not about process at all, which is the department protecting a supplier relationship it would prefer not to explain. That is a governance matter for the sponsor and not something a business case can resolve. Recognise it when you see it and do not spend the meeting on it.

Every business case needs a single, specific, answerable ask. Vague asks get vague responses, and a paper that ends with “we recommend exploring options” has invited the committee to do nothing.

Make the ask as small as it can be while still being meaningful, because a small ask that succeeds creates evidence for a larger one. The ask that most often works is not a programme at all. It is permission to run a defined pilot, with a named owner, for a defined period, with a named review date at which a fuller decision is made.

Short. Most business cases are too long, and length is usually a symptom of uncertainty about what is being asked. Aim for something a decision-maker reads in full rather than skims, with the detail in appendices for the people who want it.

If you want a structured way of identifying what is missing before you start writing, the Strategic Meetings Management checklist covers the same eight areas an evidenced case tends to draw on, and why Strategic Meetings Management sets out the broader argument in a form you can borrow from.

One test before you circulate it: hand it to someone who disagrees with you and ask them to find the weakest claim. If the weakest claim is a number, rebuild it or remove it. If the weakest claim is an assertion you have explicitly labelled as an assertion, you are in good shape.

If the evidence underneath the case is thin and you need something more substantial than an internal exercise, an SMM assessment produces the current-state description, baseline and findings in a form designed to feed directly into a paper like this.