Most organisations know roughly how many applications they run. Far fewer can say which of them they would build again today, which they would switch off tomorrow and which they keep only because nobody has checked. When the modernisation budget covers a handful of applications and the portfolio holds dozens, that knowledge decides where the money goes.
This article gives you a scoring model you can fill in with data you already have. It starts from Gartner’s TIME model, adds the evidence TIME leaves out, sets weights and thresholds, and works through twelve fictional applications so that you can see how the numbers turn into decisions.
The most widely used starting point is Gartner’s TIME model, usually traced to Gartner analyst Jim Duggan’s 2010 research on application portfolio triage. It rates each application on two axes, technical fit and functional fit, and places it in one of four boxes (SAP LeanIX summary):
| Low functional fit | High functional fit | |
|---|---|---|
| High technical fit | Tolerate | Invest |
| Low technical fit | Eliminate | Migrate |
TIME is simple enough to run in a workshop, which is both its strength and its weakness. In practice three things are missing:
The model below adds all three and maps the result to four decisions:
Score each application, or each major module, from 1 to 5 on six criteria. A higher score always argues for keeping it: more value, more use, better condition, lower risk, lower cost, better-controlled obligations.
| Criterion | What 1 means | What 5 means | Where the data comes from | Weight |
|---|---|---|---|---|
| Business value | Nothing important depends on it | The business stops without it | Process owners; process maps | 25% |
| Usage | No use across a full business cycle | Daily use by many people or processes | Database and application logs; single sign-on records; licences assigned versus used | 20% |
| Technical condition | Fragile, frequent incidents, hard to change | Healthy, tested, easy to change | Incident and change records; code analysis | 20% |
| Support risk | Out of vendor support; skills hard to find | Fully supported; skills available | Vendors’ lifetime-support policies; team skills | 15% |
| Run cost relative to value | High | Low | Licence and support invoices, infrastructure, people’s time | 10% |
| Regulatory exposure | Heavy obligations, weak controls | Light obligations or strong controls | Compliance register; audit findings | 10% |
Combine the six scores into two numbers:
Then apply the decision grid, with 3.0 as the threshold on both axes:
| Health below 3.0 | Health 3.0 or above | |
|---|---|---|
| Need 3.0 or above | Refactor or replace | Retain |
| Need below 3.0 | Retire | Retain at minimum cost, or consolidate |
Two rules override the grid:
For applications in the “refactor or replace” box, ask one more question: is the business logic something that sets you apart, or a standard process? Refactor the first. Replace the second with a product, unless making the product fit would mean rebuilding the old system inside it.
The portfolio below is fictional. Scores run from 1 to 5; Need and Health are calculated with the formulas above.
| # | Application | Value | Usage | Condition | Support | Cost | Regulatory | Need | Health | Decision |
|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Contract management (custom Java) | 5 | 5 | 2 | 2 | 3 | 3 | 5.00 | 2.36 | Refactor |
| 2 | Commission calculation (PL/SQL and reports) | 5 | 4 | 2 | 1 | 2 | 2 | 4.56 | 1.73 | Replace |
| 3 | Customer portal | 4 | 4 | 4 | 4 | 3 | 4 | 4.00 | 3.82 | Retain |
| 4 | Legacy BI (Oracle Discoverer) | 3 | 2 | 1 | 1 | 2 | 2 | 2.56 | 1.36 | Retire |
| 5 | HR training tracker (spreadsheets) | 3 | 4 | 1 | 3 | 4 | 2 | 3.44 | 2.27 | Replace |
| 6 | Pricing engine (PL/SQL) | 5 | 5 | 3 | 3 | 3 | 4 | 5.00 | 3.18 | Retain |
| 7 | Document archive | 2 | 1 | 3 | 2 | 2 | 5 | 1.56 | 2.91 | Retire, archive the data |
| 8 | Field service app (Mendix) | 4 | 4 | 4 | 5 | 3 | 4 | 4.00 | 4.09 | Retain |
| 9 | Supplier onboarding workflow | 3 | 2 | 3 | 4 | 4 | 3 | 2.56 | 3.45 | Retain, consolidate later |
| 10 | Old intranet | 1 | 1 | 2 | 1 | 3 | 4 | 1.00 | 2.27 | Retire |
| 11 | Integration hub (Spring Boot 2) | 4 | 5 | 3 | 2 | 3 | 3 | 4.44 | 2.73 | Refactor |
| 12 | Management dashboards | 3 | 3 | 4 | 5 | 4 | 4 | 3.00 | 4.27 | Retain |
Three applications are retired, two replaced, two refactored and five retained. The modernisation budget goes to four applications instead of twelve, and the three retirements free licences, infrastructure and support time.
A few results are worth a closer look:
Rationalisation can also mean consolidation. T-Mobile’s sales consultants worked in three separate CRM systems until a single custom platform replaced all three. Once the decisions are made, our article on phased legacy modernisation covers how to sequence the work.
This kind of decision map is what we build at the start of a modernisation, before anyone estimates a rebuild. If you would like help scoring your portfolio, book a discovery call.