Cutting Deep Without Cutting the Core

The Problem

A revenue drop of that magnitude doesn't just open a budget gap. It forces fundamental questions about organizational structure, role criticality, and how much overhead the business can actually sustain — all at once, under time pressure, with real consequences for real people.

Those questions get answered one of two ways. With a framework — grounded in data, modeled against recovery scenarios, executed deliberately. Or without one — reactively, emotionally, by seniority or org-chart position or whoever's loudest in the room. The second way is faster and almost always wrong. It cuts the wrong roles, keeps the wrong overhead, and hollows out the operational core the business needs to climb back.

And there's a trap inside the crisis: when leadership thinks “cost,” it thinks “headcount,” because payroll is the biggest and most visible line. But headcount is rarely the only place the money is, and cutting there first — hardest — does the most damage to the recovery. The reflex to reach for people first is exactly the reflex that has to be checked.

What We Did

We attacked the cost problem on two fronts, deliberately, and in an order that protected the business.

The vendor stack came first. Before touching a single role beyond what was clearly necessary, we went after the $1.3M the business was spending on software and vendors — because every dollar recovered there was a dollar that didn't have to come out of payroll. Three levers did the work:

• Consolidation — overlapping tools doing the same job, collapsed into one. In one case, a document and e-signature platform that had been the right call years earlier had quietly become redundant once a subcontractor management system absorbed the same function. Instead of renewing it out of habit, we cut it — a small example of the larger discipline: re-examining every tool instead of paying for inertia.

• Alternatives — expensive platforms replaced with options that did the same work for a fraction of the cost.

• Negotiation — existing contracts reopened and renegotiated rather than auto-renewed.

That work took software and vendor spend from $1.3M to $650K — a 50% cut, and $650,000 a year that no longer had to be found somewhere more painful.

Then the organization. With the overhead already lighter, the workforce resizing could be shallower and sharper than it would otherwise have been. We led that resizing across multiple cycles, bringing structure to a process that rarely has any: organizational analysis to identify critical roles and redundancies; scenario modeling to stress-test each approach against projected recovery timelines; execution planning to minimize operational disruption and legal exposure; and communication frameworks to support leadership through the change. Every decision was grounded in data — not gut feel, not seniority alone, not position on the org chart.

The Outcome

All told, the work took roughly $400,000 per month out of the business's overhead — without gutting the operational core that recovery would depend on.

The software and vendor stack was one concrete piece of that: spend on it was cut in half, from $1.3M to $650K a year, with no loss of capability the business actually needed. Those savings came from redundancy, overpayment, and inertia, not from function — and they were real dollars that never had to come off the payroll line.

On the people side, leadership had a clear, defensible rationale for every decision made — the kind that holds up to the board, to employees, and to the leaders themselves at three in the morning. Because so much cost had already come out of overhead first, the headcount cuts went less deep than a headcount-only approach would have forced.

And the business navigated one of the steepest contractions in its history without losing the operational core it needed to recover. When conditions improved, the infrastructure to scale back up was still intact — because the cutting had been done with the recovery in mind, not just the crisis.

Why This Matters for Your Business

The specifics here are a industry market collapse. The situation finds almost every business eventually — a downturn, a lost contract, a market shift that drops revenue faster than the cost base can follow.

Cut on every front, not just the obvious one. Payroll is the reflex because it's the biggest line, but the vendor stack is often bloated in ways nobody's looked at in years — overlapping tools, overpriced platforms, contracts on autopilot. Halving software spend meant real money that never had to come out of people. The most humane cost cut is the one you find somewhere other than headcount.

A framework turns an emotional decision into a defensible one. The difference between resizing by data and resizing by instinct shows up years later, in whether the business could recover. Structure isn't bureaucracy in a crisis — it's what keeps a survival decision from becoming a fatal one.

Cut for the recovery, not just the crisis. The goal was never only to stop the bleeding. It was to come out the other side with the operational core intact and the ability to scale back up. That requires modeling the recovery while you're still in the fall — and sequencing the cuts so the business that remains is one that can actually grow again.

When the pressure is on to cut fast, we help you cut smart — finding the money in the places that hurt least, and protecting the core you'll need when it's time to rebuild.