How to build a business case for media planning software

A strong business case for media planning software should prove four things: the current process has a measurable cost, the proposed platform removes specific work or risk, the team will adopt it and the expected value exceeds the total cost of implementation.

'AI will make us faster' is not a business case. Leadership needs to see where the hours are currently spent, which errors the platform would prevent and how the change supports agency growth or client retention.

Start with the current-state cost

Map the hours required for a typical plan. Include reading and retyping the brief, building personas, creating channel scenarios, formatting the workbook, managing revisions, preparing client views, updating pacing and reconciling actuals.

Multiply the hours by the true cost of the people doing the work. Use loaded employment cost rather than salary alone if finance can provide it. Separate junior production time from senior review time, because reducing senior checking often creates more value than removing basic administration. Then calculate the annual volume. If the agency creates 20 plans a month and each consumes eight avoidable hours, the opportunity is far larger than it appears when looking at one campaign.

Quantify the cost of fragmentation

The visible hours are only part of the problem. Record how many systems and files are involved: client brief, planning workbook, audience deck, activation sheet, platform exports, pacing tracker and reporting dashboard.

Each handover creates duplication and the possibility of mistranslation. A budget changes in the workbook but not in the pacing sheet. A persona changes in the deck but the platform targeting remains the same. A campaign is built from the wrong version. Estimate how often these incidents occur and the time spent correcting them. Use real examples rather than hypothetical disasters. Leadership will trust a modest number supported by evidence more than an exaggerated risk estimate.

Measure budget risk

Overspend and underspend can create direct financial exposure, make-good work, lost fee revenue and damaged client confidence. Review the previous year for material pacing incidents.

For each incident, record the amount at risk, whether it was recovered, the hours spent investigating and the senior stakeholders involved. Do not claim the software would have prevented every issue. Identify which incidents would probably have been detected earlier through automated actual-versus-planned monitoring. A platform that flags drift daily may pay for itself through one avoided error, but the case is stronger when risk reduction is supported by process evidence.

Define the future-state workflow

Show exactly what changes. For example:

1. The planner uploads the brief rather than retyping it.
2. Objectives, audiences, markets, KPIs and budget are extracted into structured fields.
3. Personas and channel allocation are drafted for review.
4. The approved plan becomes the live pacing baseline.
5. Connected platform data refreshes actual spend automatically.
6. Exceptions are reviewed in one portfolio view rather than several trackers.

This future-state description allows stakeholders to challenge assumptions. It also prevents the agency from buying software without changing the underlying process.

Calculate efficiency value

Estimate the time saved at each step and apply a conservative adoption rate. If the tool could theoretically save five hours per plan, the business case might assume only three during the first six months.

Separate capacity from cash savings. The agency may not reduce headcount, but it can use released time for more strategic work, faster pitches, additional clients or better optimisation. Explain which outcome leadership intends to pursue. For example, if planners regain 40 hours a month, the value may be the ability to absorb two additional clients without hiring immediately. That is a commercial growth case, not a cost-reduction case.

Include quality and standardisation

Software can improve the consistency of plans by enforcing common fields, storing rationale and reusing personas or historic performance. This matters when quality currently varies by planner or office.

Define how quality will be measured. Possible indicators include fewer revision rounds, fewer activation clarifications, faster senior approval, improved completion of planning fields and fewer campaigns that cannot be mapped back to an approved line. Standardisation is especially valuable during hiring and handover. New planners can work within a shared method rather than reverse-engineering several inherited workbooks.

Include client-facing value

The platform should improve something the client can feel: faster turnaround, clearer rationale, live pacing visibility, fewer budget surprises or stronger response to changing performance.

Avoid presenting the tool as internal efficiency only. Clients are more likely to value a process that connects the approved plan to ongoing decisions. This can support retention and differentiation in pitches, particularly for smaller agencies competing with larger networks. Do not promise that software alone will improve campaign performance. Position it as a better decision and control environment.

Calculate total cost of ownership

Include licences, onboarding, integrations, training, migration, internal administration and any overlap period with existing tools. Add the cost of the pilot and the time required to define the new process.

Ask whether pricing changes with users, accounts, integrations or media spend. Model the cost at today's size and at the expected size in 12 to 24 months. A platform with a higher licence but faster adoption may be cheaper than a configurable system requiring permanent internal support.

Propose a pilot with clear measures

A business case is more credible when it asks for a controlled pilot rather than a full agency commitment. Select one client with representative complexity and run the workflow from brief through pacing.

Measure time to first draft, revision rounds, manual data steps, mapping accuracy, planner satisfaction and time spent on weekly pacing. Compare the results with a similar recent campaign using the existing process. Set a decision date and success threshold. Without this, pilots continue indefinitely and nobody makes a firm adoption decision.

A simple business-case structure

Use a one-page summary containing:

• Current problem and its annual cost.
• Proposed change and expected benefits.
• Total cost of ownership.
• Pilot plan with success measures and a decision date.
• Risks and recommendation.

Attach the detailed calculations separately. Senior stakeholders should be able to understand the decision without reading every assumption, while finance and operations can inspect the model.

Turn the business case into evidence

Run a Medusa pilot using a real brief and live campaign. The pilot can replace assumptions with measured planning time, adoption feedback and pacing visibility before the agency commits to a wider rollout.