Somewhere in your business there is probably a person who, if they left tomorrow, would take a working knowledge of forty systems out of the door with them. They own the finance integrations and the HR platform and the booking system nobody else understands and the vendor relationships and the security reviews and the renewals calendar. They are, in effect, the documentation. And when the estate gets too big for them, the reflex across most retail IT functions is the same: ask for another pair of hands.

It's the wrong reflex. Not because the person isn't overstretched - they almost certainly are - but because headcount doesn't solve the problem they actually have. The problem with managing application sprawl on a team of two isn't the two. It's the eighty.

This is the normal state of retail IT now

It's worth being clear that this situation is not a failure of planning. It's the predictable result of a decade of doing exactly what the business asked for.

Retailers spent years rationalising: collapsing on-premises estates, moving to SaaS, outsourcing the big platforms, consolidating vendors. On-prem footprints that once ran to dozens of applications have been cut to a handful. Large ERP teams have been reduced to two or three people overseeing an outsourced contract. The savings were real and the strategy was sound.

But rationalisation has a quiet side effect. The applications didn't all disappear; many simply moved to SaaS and changed owner. What's left is a lean internal team holding a wide, shallow portfolio of business applications across finance, HR, security and operations - most of them third-party, most of them low-drama individually, and collectively far more than any small team can hold in its head. The lean estate isn't an anomaly to be fixed with hiring. It's the environment. The question is how you operate well inside it.

The real cost isn't on the licence schedule

Ask a CFO what an 80-application estate costs and you'll get a number made of licence fees. That number misses the expensive part.

The genuine cost of sprawl is concentrated in two places that don't appear on a balance sheet. The first is key-person risk. When one or two people carry the operational knowledge of the whole estate, the organisation has a single point of failure it can't see and can't easily price. A resignation, a long illness, a competing priority - any of these turns "we manage 80 applications" into "we no longer know how half of them work."

The second is cognitive load. Every application, however small, generates a trickle of demand: a renewal, a security review, an integration that breaks, a vendor that changes its terms, a user who needs access. Eighty small trickles is a flood, and it lands on the same desk. The result is a team permanently in reactive mode, with no capacity left for the improvement work that would reduce the load. They're too busy bailing to fix the leak.

Why more people won't fix it

There are two reasons hiring fails as a strategy here, and the first is simply that the budget usually isn't there. In a constrained year, a request for headcount to manage existing systems - rather than to deliver something new - is the easiest line for finance to decline.

But even with an open chequebook, headcount scales badly against sprawl. Onboarding a new person into eighty largely undocumented applications is a year-long exercise in shoulder-surfing, and until it's done you've added a salary without subtracting much load. You can't recruit your way out of complexity that lives in one person's head; you can only move the bottleneck. The work doesn't get smaller. It just gets a second owner who also can't take a holiday.

Sprawl is a structural problem. Throwing labour at a structural problem buys you time, not a solution.

Stop managing applications. Govern a portfolio.

The shift that actually works is a change of frame: from heroically managing individual applications to governing the estate as a portfolio. Three moves do most of the work.

Cut the count. Most large estates carry redundancy nobody has had time to remove - two tools doing one job, applications that quietly lost their users, a system retained because decommissioning it felt risky. A rationalisation pass that actually retires the dead weight is the highest-leverage thing a lean team can do, because every application removed removes its entire trickle of future demand forever. You don't need to manage 80 well. You need to be managing 55.

Standardise the lifecycle. The reason a small team drowns is that each application is handled as a one-off - bespoke onboarding, ad-hoc renewals, no consistent offboarding. Turning that into a repeatable process - a standard security gateway for anything new, a managed renewals calendar, a clean exit procedure - converts heroics into routine. Routine is what a small team can sustain; heroics are not.

Consolidate the connective tissue. Eighty applications shouldn't mean eighty logins, eighty access reviews, and eighty separate security postures. Pulling identity together under single sign-on and consistent access governance turns a sprawling set of individual relationships into something closer to a single managed system. It reduces the per-application overhead that makes the estate feel infinite.

None of this is a transformation programme. It's governance, and it's mostly within reach of existing operational budgets if it's framed as efficiency rather than a new project.

"But I can't just switch things off"

The most common objection to cutting the count is fear, and it's reasonable. When you can't fully see what an application connects to or who quietly depends on it, retiring it feels like defusing a device you can't x-ray. So nothing gets switched off, the estate only ever grows, and the fear compounds.

The way through is not bravery; it's visibility. A proper inventory - what each application does, who actually uses it, what it integrates with, and what it costs to keep versus remove - turns a frightening decision into a routine one. Most of the estate, once mapped, sorts quickly into keep, consolidate, or retire. The genuinely load-bearing systems reveal themselves, and so do the ones being kept alive purely by inertia. You're not switching things off blind. You're switching them off because you finally know you can. That single piece of work - seeing the estate clearly - is what unlocks every other move.

From firefighter to orchestrator

The deeper point is about the role itself. A lean applications team that spends its days reacting will always be measured by how much it can absorb. A team that governs a portfolio is measured by how well the estate runs - and that's a job you can do with two people, because you've designed the work down to a size that fits.

This is what punching above your weight actually means in retail IT. It isn't working longer hours against an ever-growing list. It's changing the shape of the list. The teams that thrive in the lean-estate era are the ones that stop trying to be everywhere at once and start building the structure that means they don't have to be. The estate stops being a list of things that might break and becomes a system that mostly looks after itself.

Where to start

You don't need a budget round to begin. Start with an honest inventory - what you have, who uses it, what it costs, and what it would take to remove. Most teams are surprised by how much of the estate is a candidate for retirement. From there, pick the single highest-load application and standardise its lifecycle as a template for the rest. Small, compounding moves beat a grand plan that never gets funded.

Where it helps, this is also exactly the kind of work a partner can carry without a large commitment - rationalisation support, lifecycle and vendor governance, identity consolidation, and targeted resource augmentation that gives a stretched team room to breathe and think. Not a transformation programme. A way to make the estate the right size for the team you already have.

The instinct, when one person is running eighty applications, is to find them some help. The better instinct is to ask why it's eighty.

VE3 helps lean retail IT teams govern large application estates without large budgets - rationalisation, lifecycle and identity governance, and the targeted support that turns firefighting into a system that runs itself. Get in touch for a 30-minute conversation.