A board asking why this investment and why now needs numbers built from the business's own data, not savings estimates copied from a vendor brochure.

The business case sits between the readiness assessment and the decision to proceed. It quantifies what the current state costs, what the target state is expected to deliver, and what the investment and risk look like over several years. Sometimes it concludes that the project should wait, which is a useful outcome.

Costing the status quo

Most businesses underestimate what their current systems cost because the costs are spread thin: finance staff consolidating by hand each month, sales staff re-keying orders into two systems. Other costs are inventory write-offs from stock the system said existed, audit fees inflated by poor documentation, and Zakat computed by hand from spreadsheets every year. Each of these gets a number you can defend, so the baseline rests on figures rather than assumptions.

Building benefits that survive scrutiny

Benefits are split into hard savings, cost avoidance and strategic value, and each is tied to a specific mechanism and owner. A claim that the new system will shorten the month-end close is credible only if the case explains which manual steps disappear and who is accountable for the new timeline. Benefits nobody owns rarely materialize.

The full investment picture

Licensing is rarely the whole cost. The case includes implementation fees, internal staff time diverted from normal duties, data migration and cleansing, integration with banking, payroll and ZATCA, training, contingency and support in later years. Showing the full total, not just the license quote, makes the case trustworthy when costs arrive as expected.

A hypothetical example

A finance director at a Riyadh distribution group is asked to justify a new ERP to a board that remembers the last system going over budget. The business case sets out the current cost of running several unconnected entities, models a phased implementation that limits risk early on, and shows a payback period the board can test.

What you receive

A board-ready document with an executive summary, a current-state cost baseline and target-state benefits by category and owner. It holds a multi-year investment schedule, cash flow and payback analysis, a risk register with mitigations, and a recommended decision with the alternatives considered. It becomes the yardstick for the PMO to track realized value after go-live.

Showing the risks

A business case that shows only upside invites skepticism from any experienced board member. The risk register covers the usual failure modes of ERP projects, such as data migration overruns, key staff leaving mid-project and ZATCA integration delays, each with a likelihood, an impact and a named mitigation. Leadership approves projects more readily when it can see the risks have been thought through.

Reviewing the case at decision points

A business case is not written once and filed. It is revisited at each major decision: after vendor selection, when real pricing is known; after design, when scope is clear; and at go-live, to set the benefits baseline. Each review asks the same question: does this investment still make sense on today's numbers, and if not, what changed?