Picture a textile company where the warehouse count never matches the accounting records. Purchase orders arrive by fax, one person writes them in a ledger, another keys them into a spreadsheet, and by the end of the month nobody knows which figure is correct. The owner asks why there are so many errors, and there is no clean answer. An ERP (enterprise resource planning) system can solve these problems, but first you have to convince the owner and, if there is one, the board of directors. That is exactly what a business case document is for.
A business case document is a short, plain-language write-up that explains why an investment makes sense, what it will cost, and when it will pay for itself. It is not a business plan. You do not need pages of tables and charts. But when management asks ‘why should we buy this system?’, you need a concrete answer ready. The business case prepares that answer.
The first section describes the current situation. How much time is being spent today, what mistakes are happening, and what do those mistakes cost? If two people spend two full days every month on a stock count, that is four person-days of labour. If a billing error triggered a customer dispute and a refund, that refund is a cost. If a late management report caused a missed tender, that is worth noting too. Use numbers in this section, but only numbers you can actually measure. If you are estimating, say so clearly. Made-up figures will undermine the whole document the moment someone checks them.
The second section lists the expected benefits. What will change once the ERP system is running? Stock levels will be visible in the program without a manual count. Invoice data entered once will be seen by both the accounts team and the warehouse at the same time. Order tracking will move off the fax machine and into the system. When writing these benefits, stay realistic. Do not promise that everything will be perfect. A statement like ‘monthly stock-count time could drop from two days to half a day’ is concrete and believable. Management spots inflated promises quickly, and losing their trust at this stage is hard to recover from.
The third section lays out every cost item. Buying an ERP system is not just the software licence fee. The software itself, the consultant fee for installation and setup, staff training, any new computers or a server that may be needed, and the first year of maintenance and support: all of these belong on the list as separate line items. Many companies look only at the software price, then act surprised when the consultant’s invoice arrives. Showing management the true total cost upfront prevents unpleasant surprises later. Getting written quotes from more than one vendor and attaching them to the document adds credibility.
The fourth section is the payback calculation. How many months or years will it take for the investment to pay for itself? A straightforward approach: add up the monthly time savings and error-cost reductions, convert that to an annual benefit figure, then divide the total investment by the annual benefit. The result tells you how many years the payback period is. A payback period under two years is generally seen as acceptable for a small or mid-sized business; beyond three years, management will want a stronger argument. Keep this calculation honest. Inflating the benefits may win approval in the short term, but if the system does not deliver what was promised, the credibility damage will be lasting.
There is one practical difficulty that the document should address directly: ERP implementations take time, and staff need time to adapt. In the first few months after go-live, productivity may actually dip before it improves. An accounts clerk who has worked with a paper ledger for years will make mistakes while learning the new program, and some processes will slow down temporarily. Writing this into the business case manages expectations. A sentence such as ‘we expect to reach full efficiency within six months of go-live’ is honest and shows that the proposal has been thought through carefully.
Convincing the board to approve an ERP investment is not just about finding a good system; it is about making the argument clearly and credibly. Writing the document takes some effort, but that effort is worth it. Before you submit, ask yourself four questions: have you measured the current costs honestly, are the expected benefits specific and realistic, are all investment items on the list, and is the payback calculation grounded in real numbers? If you can answer yes to all four, the document is ready to present. For a small or mid-sized business, five to ten pages is usually enough. Shorter and clearer will always be more persuasive than long and complicated.
This article was originally written in Turkish by Gökhan MERCANOĞLU on June 17, 2002 and has been automatically translated into English and other languages using machine translation.