1. Home
  2. Blog
  3. ERP Strategy: Targets, Business Case, Scope and System Selection

ERP Strategy: Targets, Business Case, Scope and System Selection

  • 7 min read
  • Tranquil team

An ERP strategy rarely starts as a strategy. It starts with something specific, such as the company’s turn for the second phase of ZATCA e-invoicing, a new branch that the accounting package cannot handle, a stock count that is off by more than anyone is comfortable with, or an auditor’s letter about manual journals. The risk is that the trigger also becomes the scope, and the company buys a system to fix one problem without deciding what else it should change.

The strategy is the short set of decisions made before choosing a system. What the company wants to be different in two or three years, what it is willing to spend and change to get there, what goes live first, and who owns the result. None of it needs a consultant’s framework. It needs the finance, operations and sales heads in one room with real numbers.

Start an ERP strategy from targets, not modules

A list of modules is not a goal. Write three to five targets that the owner or the board would recognize, each with today’s figure, the figure you want and the date. Days from month-end to a trial balance the CFO trusts. Value of stock count differences at the last count. Share of sales invoices issued without re-keying. Days to collect from the largest customers. Hours HR spends preparing the monthly payroll.

Measure today’s figures before the project starts, because nobody can reconstruct them a year later. The targets then decide the scope. If the main target is a faster close, inventory costing and bank reconciliation matter more than a mobile app for the sales team. The questions worth asking at this stage are collected in ERP implementation questions.

The business case: a worked example

A trading company with three branches prepares a three-year case. The figures are hypothetical and are not Tranquil prices. Costs are a one-off implementation fee of 150,000 riyals, a subscription of 60,000 a year, and 60,000 of internal staff time in the first year for data cleansing, testing and training.

Expected benefits are 174,000 a year once the system is running. That is an accountant’s post the company no longer needs to add as it grows (96,000), lower stock write-offs (60,000), and the financing cost saved on 300,000 riyals of receivables collected sooner, at 6% (18,000). Go-live is planned for the middle of year one.

Year Costs (SAR) Benefits (SAR) Net (SAR) Cumulative (SAR)
1 270,000 87,000 −183,000 −183,000
2 60,000 174,000 114,000 −69,000
3 60,000 174,000 114,000 45,000

The case pays back during the third year. Two changes show how fragile it is. If go-live slips by six months, the first year’s benefits fall to zero and the three-year total becomes −42,000. If the internal staff time is left out, as it often is, the case looks 60,000 better than it really is. A business case is worth more as a list of the assumptions that management will watch than as a single return figure. More on measuring the return after go-live is in ERP ROI.

Scope, phasing and who owns the decisions

In the mid-sized companies we work with, finance, sales, purchasing and inventory usually go live together, because these modules post into each other and a half-connected system produces the reconciliations the project was meant to remove. HR and payroll, projects or production can follow once the core has closed a few months cleanly.

A single go-live date for everything shortens the period of running two systems but puts more weight on testing. A phased plan lowers the risk of each step but needs temporary links between the old and new systems.

Whatever the phasing, each module needs an owner from the business, not from IT. The finance manager owns the chart of accounts and posting rules, the warehouse manager owns item codes and locations, and the sales manager owns customer data and price lists. A small steering group with the authority to decide, meeting every two weeks, keeps scope under control.

Every request that was not in the original scope goes to a list for a later phase unless it is needed for the business to operate on day one. How projects fail when this is skipped is described in ERP implementation failure reasons.

Choosing the system and the implementation partner

Feature lists from vendors look alike. What separates them is how the system handles your own transactions. Prepare five or six scenarios from your business, with your item codes and real documents, and ask each vendor to run them in a demo. A sale with a partial delivery and a credit note. A purchase with landed costs. A stock transfer between branches. A month-end close. A payroll with overtime and a new joiner. Watch what needs a workaround.

For a Saudi company, a few points are not optional. The system must handle ZATCA e-invoicing in the integration phase, the VAT return, and Arabic and English for users and printed documents.

Ask how a customization is carried through future upgrades, and who pays for that. Ask for reference customers of similar size in your sector and call them. Read the contract for how you get your data out at the end. If the choice is between an ERP and a better accounting package, the trade-offs are set out in ERP vs accounting software.

Measuring results after go-live

Go back to the targets three, six and twelve months after go-live and compare them with the baseline. Expect the first close in the new system to be slower than the last one in the old, while people learn where things are. If the figures have not moved by month six, the usual causes are users keeping side spreadsheets, master data that was migrated without cleaning, and posting rules that send entries to the wrong accounts.

The benefit owner named in the business case should present these figures, not the IT manager or the vendor. After the first year, the same review decides what goes into the next phase. The steps of the project itself are covered in ERP implementation.

Where Tranquil ERP fits

Tranquil ERP covers eight modules: accounting and finance, sales and distribution, procurement, inventory and warehouse, production, project management, HR and payroll, and fixed assets and equipment. Every screen works in Arabic and English, with Arabic right to left. The same screens are shaped to how a company works through 166 on/off settings and approval settings per document, rather than through custom code, which matters when the system is upgraded.

It is ready for the second phase of ZATCA e-invoicing, with onboarding per branch, clearance of B2B invoices and reporting of B2C invoices, and it prepares the VAT return from the same postings. Opening balances, items, customers, suppliers and employees can be loaded from Excel templates, which shortens data migration. The modules are listed on the Tranquil ERP features page.

Frequently asked questions

How long should an ERP business case cover?

Three to five years is usual. A shorter period ignores the years when the benefits come in, and a longer one depends on assumptions nobody can test. Show the yearly figures, not only the total, so that the effect of a late go-live is visible.

Should we customize the ERP to match our current processes?

Only where the process gives the company an advantage or a regulation requires it. Most other differences are habits, and changing the habit costs less than maintaining a customization through every upgrade. Settings and approval rules usually cover what remains.

Is it better to go live with all modules at once or in phases?

It depends on how closely the modules are linked. Finance, sales, purchasing and inventory post into each other, so they usually go live together. HR, projects or production can follow once the core has closed a few months without problems.

Who should own the ERP project?

A senior executive, usually the CFO or the general manager, with a named owner for each module from the business. IT runs the infrastructure and the integrations, but decisions on processes, data and scope belong to the people who will live with the results.

Tranquil in practice

In the demo we show this article’s topic on Tranquil’s own screens and answer your team’s questions.

Dammam +966 13 848 8080, +966 13 817 7724, Riyadh +966 11 213 1330
[email protected]
Sunday to Thursday, 8 am to 5 pm.