The partners agree the business needs a system. Then one of them asks what it will bring back, and the meeting stalls. Vendors have slides of percentages drawn from surveys of companies that look nothing like yours. Put those aside. A business case that persuades a cautious partner is built from figures already sitting in your own office.
What an ERP business case is
It is a one-page comparison. On one side, what the present way of working costs you every month. On the other, everything the ERP will cost, in the first year and in each year after. ERP ROI is the gap between the two over a period you choose, and payback is the point where the savings have covered the spend. The arithmetic is easy. The effort goes into finding honest inputs.
Working out what the manual process costs
List the double entry
Write down every place the same order, receipt or payment is typed or written a second time, and by whom.
Note the hours
Ask each person to record, over a normal fortnight, the time spent on that re-entry, on matching sheets and on preparing reports by hand.
Price the hours
Multiply by what each person costs you per hour, taken from your own salary sheet. This is the monthly cost of duplicated work.
Measure stock differences
Take your recent physical counts and compare them with the books. The value written off, or never explained, is a cost of the present method.
Measure slow recoveries
From the ageing of receivables, note how much sits beyond your agreed credit days and what that money costs you in borrowing or in purchases you could not make.
Count the errors
Credit notes for wrong prices, goods sent twice, supplier bills paid twice, orders lost on WhatsApp. Go back through a few months of records and total them.
Where each figure comes from
| Cost of the manual process | Where to find your figure | What to be careful of |
|---|---|---|
| Hours of double entry | Staff time notes and the salary sheet | Count only the time a system would remove, not the whole job |
| Stock differences | Physical count sheets against the stock register | Some loss is theft or damage, which a system reveals but does not prevent |
| Late recoveries | Customer ledgers and the ageing report | A system shows who is overdue; someone still has to collect |
| Errors and rework | Credit notes, returns, supplier statements | Use a typical period, not your worst month |
| The owner's time | Your own diary | Be honest about the hours spent asking people for figures |
The costs to include on the system side
- The build or the licence, as given in the written quote.
- The data move: cleaning the lists and loading opening balances.
- Hardware you do not already own, such as printers, scanners or a better internet line.
- Hosting, if the system runs online.
- Yearly support, and the changes you will certainly ask for.
- Your own people's time for discovery, testing and training. This is the line that is easiest to forget.
- A slower spell around go-live while staff learn.
Total these for the first year, then for each year after. That is the cost of ownership, and it is the only fair figure to set against the savings. For more on the individual lines, see what drives ERP software cost and software cost after launch.
Presenting payback
Put the monthly cost of the manual process beside the monthly saving you expect. Do not assume the system removes all of it. Decide, line by line, what share you can defend. Re-typing between sales, stores and accounts goes almost entirely. Recoveries improve only if somebody acts on the overdue list. Take the system's own monthly running cost off that saving, then divide the one-time cost by what is left. The answer is the number of months to payback.
Show it as a range. Work it once with cautious assumptions and once with hopeful ones, and write the assumptions underneath. A partner who can see how you reached the figure will argue with an assumption, which is useful. A partner shown one confident number tends to distrust all of it.
Leave out benefits you cannot put a figure on, such as better decisions or happier customers. Mention them in a sentence under the table. They are real, but guessed rupee values weaken the numbers that are solid.
When the case does not add up
Sometimes the sums say no. A business with one godown, a handful of staff and an owner who sees every bill may find that the manual process costs little. A tidy spreadsheet or an accounting package is then the right answer for now, and it is worth knowing that before any money is spent. Run the figures again when you add a branch, a second godown or salesmen on routes, because that is where the cost of manual work climbs.
A smaller first phase changes the result too. One module aimed at the costliest problem needs less money and starts saving sooner than a full system; the basic ERP system guide describes that starting point. Operix does not publish prices. The written quote for ERP software sets out the modules, users and branches it covers, which is the breakdown this calculation needs. Distributors can see the processes involved on our distribution software page. Book a demo and bring your figures; if they do not justify a system yet, we will say so.
Questions people ask
How do you calculate ERP ROI?
Total what the manual process costs per month in staff hours, stock differences, late recoveries and errors, and estimate the share an ERP removes. Compare that saving with the full cost of the system over the same period.
What is a good payback period for an ERP?
There is no universal figure; it depends on your margins and on how much manual cost you carry. What matters is that the period is worked out from your own numbers and that the partners accept the assumptions.
What is included in ERP total cost of ownership?
The build or licence, data migration, hardware, hosting, yearly support and changes, and your staff's time during the project. Leaving out the yearly costs makes the case look better than it is.
How do I convince my partners to invest in an ERP?
Show them the monthly cost of the present process using figures from your own books, then the full cost of the system and the payback range. Written assumptions carry more weight than a vendor's brochure.
Is an ERP always worth it?
No. A small business with one location and an owner who sees every transaction may not recover the cost. Rework the figures when the business adds branches, godowns or a sales team.