How to Actually Justify a Marketing Ops Headcount, With Numbers

A marketing ops lead I worked with had been asking for a second headcount for two budget cycles, framing it as "the team is stretched thin." It got denied both times. The third attempt got approved in one meeting, because the ask changed from a workload complaint to a cost-of-inaction number: $340,000 in estimated annual revenue sitting in delayed campaign launches and unresolved lead-routing bugs that nobody had capacity to fix.

Building the number

We tracked every ticket in the ops backlog for a quarter and tagged each one with an estimated dollar impact if left unresolved — a broken lead-routing rule sending leads to the wrong queue, a campaign launch delayed by two weeks past its optimal send window, a reporting gap that led to a budget misallocation. Not every ticket got a confident number, but enough did to build a credible floor estimate.

Nobody approves a headcount for "the team is tired." Plenty of people approve a headcount for "here's the revenue currently leaking through the cracks."

Backlog tagged by impact category:
  Delayed launches        -> opportunity cost estimate
  Unresolved data bugs    -> estimated misallocation / lost conversions
  Deferred automation     -> estimated hours x loaded cost, annualized

Sum of credible-floor estimates > fully loaded cost of new hire
= the actual business case

What made it credible instead of inflated

• Used conservative, defensible estimates per ticket rather than best-case numbers — credibility mattered more than a bigger total.
• Separated "estimated" from "confirmed" impact clearly so finance couldn't dismiss the whole number over one shaky line item.
• Tied the ask to a specific, named category of work the new hire would own, not a vague capacity increase.
• Presented it as ongoing quarterly cost of inaction, not a one-time number, which better matches how a headcount decision actually gets evaluated.

The headcount got approved within a week of that version of the pitch. The workload argument had been true the whole time — it just wasn't a business case until it had a number attached.