How to calculate the business case for software modernization

Your software still runs. Orders get processed, invoices go out, stock gets tracked. But your team can't access it from home, your accountant re-keys data from one system into another every morning, and your new hire asks why there's no mobile app. You know something has to change — but the board wants a number before they'll approve anything. This article gives you a structured framework to calculate the real business case for modernizing your software, so you can walk into that meeting with hard figures instead of gut feeling.

Why "it still works" is not a good enough reason to keep it

Legacy systems create two kinds of cost: the costs you can see on an invoice, and the costs buried in lost hours, missed integrations, and decisions made on stale data. Most businesses dramatically undercount the second category.

Consider a mid-sized wholesale distributor running a FileMaker-based ERP that was built in 2012. It tracks inventory, sales orders, and customer data — and it does that reliably. But:

• Every order placed through the webshop has to be manually re-entered into FileMaker by a backoffice employee — every single order, every single day.
• The sales team works from the office because the system isn't cloud-accessible, so they can't check stock levels during a customer visit.
• The CFO exports data to Excel every Monday morning to build a dashboard that could be automated.
• The system has no API, so connecting it to a modern WMS, a CRM, or a BI tool would require a custom data bridge or manual exports.

None of these costs appear as a line item. But they are very real — and they compound every year.

What does "modernization" actually mean — and how is it different from replacement?

Before you can build a business case, you need to be precise about what you're comparing. These are the four options on the table:

1. Do nothing — keep the current system as-is, accept its limitations.
2. Extend and modernize — keep the existing core, but add modern capabilities: cloud hosting, API connectors, mobile access, AI-assisted workflows, or a web front-end layered on top.
3. Rebuild on the same platform — redesign the solution from scratch in the same technology (e.g. FileMaker), applying current best practices and architecture.
4. Replace entirely — migrate to a new platform (SAP, Dynamics, a SaaS ERP, or a custom-built web application).

The business case you build must compare at least two of these options against each other, with a shared set of variables: total cost of ownership (TCO), expected time to value, risk exposure, and business value unlocked.

Step 1 — Inventory your current costs (the full picture)

Start by documenting what your current system actually costs your business. Most organizations only count licensing and hosting. The real cost inventory has five layers:

1. Direct operating costs

• Licensing fees (FileMaker, hosting, server maintenance)
• IT support and internal developer time spent on maintenance
• Third-party tools purchased to compensate for missing features (e.g. a separate timesheet app because the ERP has no time-tracking)

2. Manual process costs

Map every workflow that requires a human to do something a system should do automatically. For each one, estimate:

• How many times per day/week does this happen?
• How many minutes does it take?
• What is the fully loaded hourly rate of the employee doing it?

Example: Backoffice re-entry of webshop orders — 35 orders/day × 4 minutes × €35/hr = €81.67/day → ~€21,000/year — just for that one manual step.

3. Error and rework costs

Manual data entry means errors. Errors mean credit notes, customer complaints, stock mismatches, and time spent finding and fixing them. Even a conservative estimate of 1 error per 50 manual entries adds up quickly once you count the resolution time.

4. Opportunity costs

What business can you not do because of the system's limitations?

• Sales team can't work remotely → how many deals take longer or fall through?
• No real-time stock visibility → how often do you oversell or turn away an order you could have fulfilled?
• No API → which partner integrations, marketplace connections, or automation opportunities are blocked?

These are harder to quantify but often the largest number on the sheet. Use conservative estimates and be explicit about assumptions.

5. Risk costs

Legacy systems carry platform risk (vendor discontinues support), security risk (unpatched vulnerabilities), and key-person risk (one developer who knows the system retires). Assign a probability-weighted cost to each: probability of event × estimated cost of recovery.

Step 2 — Build the cost model for each modernization scenario

Now cost out your options. For each scenario, calculate:

Cost category	Do nothing	Modernize existing	Full replacement
One-time implementation cost	€0	€25,000–€80,000	€80,000–€300,000+
Annual operating cost	€X (current)	€X ± delta	€Y (new platform)
Migration / data conversion	€0	Low–medium	High
Training and change management	€0	Low	High
Time to go live	—	2–6 months	6–18 months
Risk of disruption	Low	Medium	High

The numbers above are illustrative — your real figures will depend on system complexity, team size, and integration scope. The point is to put every option in the same table so you're comparing apples to apples.

A note on "do nothing" costs: Do nothing is not free. Every year you delay, you accumulate the manual process costs, opportunity costs, and increasing risk premium from the first step. Make that visible in the table — it's often the most persuasive number in the whole analysis.

Step 3 — Quantify the value each scenario unlocks

Costs are only half the story. For each modernization scenario, estimate the value it would create:

• Time savings from automation: Use your manual process inventory. If automating order entry saves €21,000/year, that's a direct, defensible line in your business case.
• Revenue upside from new capabilities: Cloud access for the sales team → more calls made from the road → conservative estimate: 5% improvement in close rate on €1.2M pipeline = €60,000.
• Integration value: Connecting FileMaker to your webshop via API eliminates the manual order entry entirely. Connecting it to your logistics partner eliminates manual shipping label creation. Each connector has a calculable payback period.
• AI-assisted workflows: Adding AI features — like automated document classification, smart order prioritization, or anomaly detection in inventory — can reduce decision time and surface issues before they become costly. Estimate conservatively but include them.
• Risk reduction value: A cloud-hosted, API-connected system that runs on a supported platform eliminates several of the risk line items you priced in Step 1.

Step 4 — Calculate ROI and payback period

With costs and value both on the table, you can now calculate:

ROI formula:

ROI = (Total value created − Total cost of modernization) ÷ Total cost of modernization × 100%

Payback period:

Payback = Total implementation cost ÷ Annual net savings (savings + revenue upside − new operating cost delta)

FileMaker ERP example continued: The wholesale distributor in our example calculates:

• Annual manual process costs identified: €47,000
• Opportunity cost (conservative): €35,000/year
• Risk premium: €8,000/year
• Total current hidden cost: €90,000/year

Modernization option: extend the existing FileMaker system with cloud hosting, an API connector to the webshop, a mobile interface for the sales team, and an automated reporting dashboard.

• Implementation cost: €52,000
• Annual operating cost increase: €4,000
• Annual savings + value unlocked: €78,000
• Payback period: 52,000 ÷ (78,000 − 4,000) = 8.4 months
• 3-year ROI: ((78,000 × 3) − 52,000 − (4,000 × 3)) ÷ 52,000 = ~295%

Compare that to full replacement: estimated €180,000 implementation, 14-month timeline, high disruption risk, and a similar value ceiling. Same destination, three times the cost, and the business runs disrupted for over a year.

This is why modernizing without starting over is often the more rational path — not because replacement is never right, but because the business case rarely supports it when the core system is structurally sound.

Step 5 — Stress-test your assumptions

Before presenting the business case, pressure-test it:

• What if implementation runs 30% over budget? Does the payback period still make sense?
• What if the manual process savings are 50% of your estimate? Still a positive ROI?
• What's the worst-case scenario for "do nothing"? What if a key developer leaves, or the hosting environment becomes unsupported next year?

A business case that survives a 30% cost overrun and a 50% value haircut is a genuinely strong one. Present the base case, the conservative case, and the worst-case-do-nothing scenario side by side.

Decision checklist: modernize vs. replace

Use this checklist to sense-check your framework output:

Lean toward modernizing the existing system if:

• The core data model and business logic are fundamentally sound
• The main gaps are in integration, accessibility, or UI — not core functionality
• The implementation risk of replacement is high (complex data, critical uptime requirements)
• Payback period for modernization is under 18 months
• Team knowledge of the existing system is a genuine asset

Lean toward full replacement if:

• The existing system's architecture cannot support the required integrations or scalability
• The platform is genuinely end-of-life with no credible roadmap
• The business model has changed so fundamentally that the old system maps to the wrong processes
• The TCO of modernization over 5 years exceeds the TCO of a new platform
• Compliance or security requirements cannot be met by extending the current system

FAQ

How long does it take to build a business case for software modernization? For a mid-sized company with one primary system, a solid business case can be assembled in 2–4 weeks if you have access to HR cost data, process documentation, and system usage data. The manual process inventory is usually the most time-consuming part.

Do I need exact numbers, or are estimates acceptable? Estimates with explicit assumptions are better than no numbers — and more honest than false precision. Document your assumptions clearly. A decision-maker who understands the methodology will trust it more than a suspiciously exact figure.

What if my system is FileMaker and I'm not sure it can support modern integrations? Modern FileMaker (FileMaker 19 / Claris Pro) supports REST APIs, OData, and cloud hosting via Claris Cloud. The integration capability is real — the question is whether your current implementation is architected to use it, or whether that work is part of the modernization scope.

How do I handle intangible benefits like "better user experience"? Convert them to proxies: reduced onboarding time for new staff (€X per hire × Y hires per year), reduced support tickets, reduced error rates. User experience has a measurable cost when it's bad — quantify that instead of leaving it as a soft benefit.

What's the biggest mistake companies make when building this business case? Undercounting the cost of doing nothing. Every analysis focuses on the investment required to modernize. The hidden costs of staying still — manual labor, missed integrations, compounding risk — are usually larger, and they're already being paid.

---

If you're at the point where the numbers point toward modernization but you're unsure where to start, that's exactly the kind of conversation Loggix is built for. Whether it means extending an existing FileMaker system with API integrations and cloud access, building a web application layer on top of your current data, or mapping out an AI-assisted workflow that eliminates your most expensive manual process — the right next step starts with understanding your specific system and your specific costs. That's a conversation worth having before you sign anything.