← Back to Resources

Blog articles

Use it or lose it: turn year-end budget into a live workflow in weeks

5 min readAlison Crawford
A 2026 budget binder with a "Use it or lose it" note beside a notebook sketch: fund this year, build in weeks, execute in your systems, recover revenue

In short

  • Year-end budget that goes unspent often gets cut from next year's plan. Spent on another report or license, it rarely changes anything.
  • The better use is one live execution workflow aimed at the revenue leak: the roughly 3% of COGS lost to work that happens outside your systems of record. For a company with $1B in COGS, that's about $30M a year.
  • Speed comes from scope. One supply chain workflow, one owner, one number, running on top of the systems you already have.
  • Emerix gets a first workflow live in about 12 weeks from kickoff, so budget committed now is starting to make an impact in weeks, not years.
  • Choose the first supply chain workflow by dollars at stake, volume, and how much of the work lives in email, portals, and spreadsheets.

Every finance team knows the October conversation. Department heads check what's left in their budget. Whatever goes unspent gets swept back, and next year's budget number often shrinks to match.

So in the last few months of the year, money gets committed fast, usually to whatever is easiest to approve. Another license. Another report. Another dashboard that nobody opens in March.

Now imagine being the leader who spends it differently. The workflow you fund in Q4 is live and starting to make an impact about 12 weeks after kickoff, and it's delivering real ROI over the year that follows. While everyone else is explaining a dashboard, you're reporting results.

For supply chain leaders, it's a low-risk opportunity to finally fix a pain point that's been leaking money for years.

Why the revenue leak belongs in your budget, this year and next

Most supply chain execution doesn't happen in the system of record. Somewhere between 40% and 60% of it happens in inboxes, supplier portals, PDFs, and spreadsheets. It's the PO change that sits unread in someone's inbox until the shipment is already late. The chargeback that gets written off because nobody had time to dispute it. The inventory sitting in one warehouse while another stocks out. And because none of it lives in the system of record, nobody sees the cost until it shows up in the P&L.

The cost has a name: the revenue leak. It runs about 3% of COGS. For companies with $1B to $10B in COGS, that's $30M to $300M a year spent on things you never should have paid for: fines, chargebacks, expedited freight, and write-offs.

That changes the math on budgeting, not just on spending what's left in December. The leak deserves a line in next year's plan, not whatever happens to be left over. A report shows you the leak. A workflow starts closing it. One is a cost line. The other is margin you get back.

The test for any budget line is simple, whether it's committed this quarter or planned for next year. Within two quarters, will it show up as revenue protected, margin recovered, or cycles shortened? If the honest answer is "we'll know more," it's the wrong place for the money.

What it takes to get a workflow live in weeks, not quarters

Speed comes from scope, not shortcuts. Enterprise projects stall when they try to change everything at once: a new system, a migration, a retrained team. A first workflow avoids all three.

  1. One workflow. A single, bounded process with a clear start and end, like disputing OTIF chargebacks or handling PO changes.
  2. On top of the systems you already run. The execution layer reads from and acts in your ERP, WMS, and supplier portals. Nothing gets ripped out.
  3. One owner and one number. A named business owner and a metric agreed before kickoff: dollars recovered, cycle time, or hours handed back to the team.
  4. Your team sets the controls. You decide where the workflow acts on its own and where it asks first. Human-in-the-loop is how trust gets built, not a limit on what the workflow can do.

That's how Emerix gets a first workflow live in about 12 weeks from kickoff, instead of waiting on a go-live next fall.

How to choose the first workflow

This is the best part: choosing the problem your team finally gets to stop fighting. Score your candidates on four things.

  • Dollars at stake. Fines, deductions, lost sales, expedite fees. The bigger and more visible the number, the easier the case at the next budget review.
  • Volume. A process your team touches dozens of times a week pays back faster than one that comes up twice a quarter.
  • Where the work lives. The more of it that runs through email, portals, and PDFs, the bigger the gap a workflow can close.
  • An owner who wants it fixed. A team that's tired of the firefighting will champion the result.

Three workflows tend to score well on all four: OTIF chargebacks and deductions, PO change management, and inventory rebalancing across locations.

Five questions to ask before you commit year-end budget

  1. What will be live, and when? Ask for the date it will be running in production on your real orders, not a project plan.
  2. What does it run on? If the answer starts with replacing a system, the timeline isn't weeks.
  3. How will we measure it? Agree on the metric and the baseline before kickoff, so the result is clear by the next budget cycle.
  4. Who stays in control? Ask how approvals, exceptions, and audit trails work, and how security is certified.
  5. What comes second? Whatever you buy first should make the next problem faster to solve.

Back to October. The budget is going to get spent either way. The only question is what you'll be looking at in March: another report on the leak, or a workflow that's already closing it.

Ready to recover your 3%?

Book a discovery call

Frequently asked questions

How should supply chain leaders spend year-end budget?
Put it toward one live execution workflow aimed at a measurable cost, like OTIF chargebacks or PO changes, rather than another report or license. Scoped to one workflow running on top of existing systems, it can be live in about 12 weeks and show results by the next budget cycle.

What is "use it or lose it" budget?
It's money left in a department's annual budget near year-end. If it isn't spent, it's often returned and next year's allocation is reduced. That pushes teams to commit spend before the fiscal year closes.

Can a supply chain workflow really go live in weeks?
Yes, when the scope is one workflow running on top of existing systems. Emerix gets a first workflow live in about 12 weeks, without replacing the ERP or WMS.

What is the supply chain revenue leak?
It's the avoidable cost of execution work that happens outside systems of record, in email, portals, PDFs, and spreadsheets. It runs about 3% of COGS, or roughly $30M a year for a company with $1B in COGS.

Which workflow should we start with?
Pick one with real dollars at stake, high weekly volume, work that lives outside your systems, and an owner who wants it fixed. OTIF chargebacks, PO change management, and inventory rebalancing are common first choices.

About Emerix
Emerix is the AI Execution Layer for supply chain. It runs autonomous workflows on top of the systems you already have, detecting issues, deciding the best response, and executing it directly in your systems of record. Enterprises use Emerix to Protect Revenue, Optimize Profitability, and Accelerate Cycles. Emerix is backed by Lightspeed and is SOC 2 Type II certified.