Writing a business case as a team leader

Workforce economics · Leadership · ~7 minute read

Why team leaders need to write business cases

Team leaders see things that nobody else in the operation sees. They watch the same call types come back twice, the same system pause add ten seconds to every call, the same product confusion drive a quarter of the contact volume. They know exactly which interventions would help: a knowledge-base update, a script change, a coaching focus, a small system fix, a process redesign. The problem is that their ideas compete for time, money, and management attention with every other idea in the operation, and the ideas that get funded are almost always the ones that arrive on a single page with a credible saving attached. This article is a practical guide for team leaders building that page: how to size the saving from a reduction in AHT, repeat calls, or overall volume; how to combine multiple levers; how to handle costs and payback; and how to present the result so it actually gets read. The companion team-leader savings calculator on this site runs the maths automatically once the inputs are in.

The three levers of operational saving

Almost every team-leader initiative in a contact centre delivers its saving through one (or more) of three levers. AHT reduction shortens each contact, so the same volume needs fewer agent-hours. Repeat-call reduction means more contacts are resolved first time, so total contact volume falls. Volume reduction deflects contacts entirely — through self-service, proactive communication, or fixing the underlying cause that drove the contact in the first place. Each lever produces a saving in agent-hours, which translates into FTE, which translates into pounds. The translation is the same in every case; the input number is what changes.

The maths in plain English

The chain of logic is short and easy to write down. The number of agent-hours an operation needs depends on the volume of contacts, the time each contact takes, the target occupancy (how fully agents can be utilised), and the shrinkage (how much paid time is off the phones for everything other than contacts). The formula is essentially:

Agent-hours required = (volume × AHT) ÷ occupancy ÷ (1 − shrinkage) ÷ 3600

(The 3600 converts AHT in seconds into hours.) FTE required is then agent-hours divided by the annual hours per agent (typically 1,950 for a 37.5-hour week over 52 weeks). Annual cost is FTE times the fully loaded cost per agent. Any change in volume or AHT flows straight through this chain to a saving in pounds.

This means a team leader can size their idea with three pieces of information: the operation’s annual contact volume, its current AHT, and its fully loaded cost per agent. The numbers usually live with the planning team and finance, and a quick conversation gets them.

Sizing each lever

AHT reduction. If the initiative is expected to remove ten seconds from every contact — a script tighten, a knowledge-base fix, a system shortcut — the saving in agent-hours is the volume multiplied by ten seconds, divided through the chain above. For an operation handling 1.5 million contacts a year at a fully loaded cost of £28,000 per FTE, ten seconds of AHT saving translates to roughly £125,000 a year. Bigger AHT saves scale linearly: 30 seconds is three times that number.

Repeat-call reduction. Repeat calls are unusual because they compound. If 25% of contacts are repeats, every 100 first-time contacts generate 33 repeats and a total of 133 contacts. Drop the repeat rate to 20%, and 100 first-time contacts generate 25 repeats and 125 total — a saving of 8 contacts per 100 first-time contacts, or about 6% of total volume. The saving compounds because preventing a repeat call also prevents the agent time on the second, third, and any subsequent calls that would have followed. A two-percentage-point reduction in repeat rate is usually worth more than it looks.

Volume reduction. Direct deflection — customers handled by self-service, an FAQ update, or a proactive notification — is the simplest case: total volume falls by the number of contacts deflected, and the saving is that volume times the average handling cost. The handling cost per contact is the fully loaded annual cost divided by the contacts each FTE handles per year (typically 4,000–7,000 voice contacts per FTE per year depending on AHT and shrinkage). A team leader who can credibly deflect 50,000 contacts a year is proposing a saving in the £200,000–£350,000 range, which is enough to fund most of the operational changes a team leader would ever propose.

Combining levers

Many real initiatives deliver across more than one lever. A coaching programme might cut AHT and reduce repeat calls. A knowledge-base improvement might do both, plus deflect some volume entirely. The saving is the sum of each lever’s contribution, but the levers interact — cutting AHT on volume that has already been deflected does not produce the AHT saving for those contacts. The cleanest way to handle this is to apply the levers in order: first deflect volume, then reduce repeats on the remaining volume, then reduce AHT on what is left. The calculator does this automatically, so a team leader can run scenarios without working through the algebra by hand.

Costs, payback, and net saving

A credible business case includes the cost of doing the work. There are usually two kinds: a one-off implementation cost (people’s time, training, system change, communication) and an annual ongoing cost (maintenance, licences, additional headcount if any). Subtract the ongoing cost from the gross saving to get the net annual saving; divide the one-off cost by the net annual saving to get the payback in years. Most operational team-leader initiatives have one-off costs in the thousands or tens of thousands of pounds and ongoing costs that are small or zero, so payback is usually short. Six months or under is excellent; under twelve months is acceptable; over two years is hard to justify unless the long-term saving is large.

Presenting the case

A business case from a team leader does not need to be long. A one-page summary almost always lands better than a five-page paper, because the audience is busy and the decision will be made on the headline numbers. The page should cover: what the initiative is, what problem it solves, the size of the saving (with the calculation visible, not just the answer), the cost, the payback period, the risks and what could go wrong, and the dependencies (what you need from the operation to deliver it). Senior management will sometimes want supporting detail, but they read the one-pager first. Operations managers and finance partners almost always appreciate the calculation being explicit — they can stress-test the numbers without asking you to redo the analysis.

Sensitivity and honesty

A credible saving number includes a range, not a single point. The team leader proposing a ten-second AHT reduction should also show what the saving would be at five seconds (the conservative case) and at fifteen (the optimistic case). The honest range is what protects the case when reality lands somewhere inside it. Finance partners are more likely to trust an analyst who admits uncertainty up front than one who promises a precise number and misses it.

Common mistakes

Four patterns recur in team-leader business cases that do not get funded. The first is using a unit cost that is too low — basing the case on salary alone, ignoring NI, pension, bonus, and other on-costs that add 20–30%. The second is over-claiming on the size of the saving — promising a saving the operation cannot actually deliver because some of the AHT or volume reduction will fall on agents who would have been idle anyway. The third is ignoring the cost side — arriving with a saving number and no implementation cost, which makes the case look incomplete. The fourth is treating the saving as ring-fenced — assuming the FTE saved will be removed from headcount, when in reality the operation will usually redeploy the freed capacity rather than reduce it. Both are valid outcomes; the case should describe which is expected and let the operation decide.

Conclusion

Team leaders sit on most of the best operational improvement ideas in any contact centre. The ideas get funded when they arrive as one-page business cases with credible savings, honest costs, and clear payback. The maths is not complicated — three inputs, a short chain of arithmetic, an explicit lever — and the discipline of doing it once converts a team leader from a person with good operational instincts into a person who shapes how the operation invests in itself. The companion savings calculator on this site automates the arithmetic; the harder work is the framing, the honest sensitivity range, and the one-page summary that lands the case on the right desk.

Pair this with understanding contact centre finance for the P&L framing that makes the saving credible to finance, and the true cost of attrition for the workforce economics that underpins the per-FTE cost figure.