Application Rationalization for Mid-Sized Companies

Application rationalization sounds like something only Fortune 500 companies do, with consultants, frameworks, and multi-year roadmaps. But the core idea is simple and arguably matters more for mid-sized companies: decide deliberately which applications you keep, and stop paying, in money and attention, for the rest.

A company with 150 employees and 60 applications doesn’t need an enterprise framework. It needs a clear-eyed afternoon with the right list.

Why mid-sized companies need it most

Large enterprises have architecture teams whose job is to manage the portfolio. Small startups have few systems to begin with. Mid-sized companies are in between: big enough to have accumulated real sprawl, but rarely staffed to manage it.

The result is a portfolio that grew through individual departmental decisions, acquisitions, and contractors, with no one looking at the whole.

A right-sized approach

Step 1: Inventory

List every application and record its purpose, owner, users, annual cost, and what it connects to. (See How to Inventory Your Company’s Software.)

Step 2: Score each application on two axes

Keep it simple:

Step 3: Place each application in a quadrant

  Good health Poor health
High value Keep and maintain Invest: modernize or rebuild
Low value Consolidate into something else Retire

This one table resolves most decisions quickly.

Step 4: Look for functional overlap

Group applications by what they do: communication, project tracking, document storage, reporting, CRM. Wherever there’s more than one tool per job, pick a winner.

Step 5: Sequence the work

Start with retirements, which are quick wins that reduce cost and risk immediately. Then do consolidations. Save rebuilds for last, after you’ve simplified everything around them.

Common pitfalls

Make it ongoing

The most valuable outcome isn’t the one-time cleanup. It’s a habit: a quarterly look at the portfolio, a short checklist before adopting new tools, and clear owners for what remains. Quarterly portfolio reviews are built into our managed software services for exactly that reason.

If you’d like this done for you, start with a Software Portfolio Audit.


Tell us what you're running.

Two quick steps. I'll read it personally and reply with an honest read on your situation and whether our team can help, usually within one business day.

  • I lead every engagement personally
  • No sales sequences, and your details are only used to reply

Prefer email? [email protected]

Step 1 of 2

Which sounds most like you?
What's prompting this? Pick any that apply
How many business-critical custom systems?
Timeline
Where should I reply?