The need for an ERP system doesn’t start with a technical decision. It starts with a feeling that keeps coming back in management: the numbers don’t match, reports arrive late, and every department keeps its own version of the truth. As the organization grows, that feeling turns into a daily cost, even if it never shows up as a line in the budget.
By a custom ERP system we mean a system built around your processes and business rules and implemented module by module, not an off-the-shelf package that makes you change the way you work to fit it. You don’t need technical expertise to notice the signs below, only an honest look at what happens in day-to-day work.
We look at each sign from three angles: what it costs you in daily work, how to spot it this week, and what it looks like in a hypothetical example. After that comes a short self-assessment checklist that brings all the signs together.
The six signs
The same data is entered more than once
Sales records the order, the warehouse enters it again, and accounting copies it into a third spreadsheet. Each re-entry is time that adds no value and a new chance for a mistake in a quantity, a price, or a customer name, and those mistakes surface later on invoices and in customer complaints.
To spot it this week, pick a single order and follow it from the moment it comes in until payment is collected, counting the times its details were written down again in a file, a program, or a ledger.
Suppose a regular customer’s order arrives in a WhatsApp message, then gets written into the sales spreadsheet, then onto the dispatch note, then onto the invoice. Any mistake in the spreadsheet passes silently into every step after it and is caught only when the customer objects.
Reports take days to put together
When a manager asks for a simple figure on inventory or receivables, someone starts collecting Excel files from the departments and reconciling them by hand. The cost here is twofold: time spent compiling instead of analyzing, and a decision made before the figure arrives or based on an outdated one.
This week, note every management question whose answer needed more than one file, how long it took to get the answer, and who prepared it.
Suppose the general manager asks at the start of the week about overdue receivables from the customers of one particular branch. The answer arrives three days later, and in the meantime a sales rep has pitched a new order to a customer who is behind on payments.
Business rules live in people’s heads
Allowed discount limits, approval authority, and exceptions are known to particular employees. When one of them is away, the process stalls or the rule is applied differently, and training a new employee becomes word of mouth that no one can verify.
This week, ask two employees who do the same job about a single rule, such as the discount limit or the terms for selling on credit, and compare their answers.
Suppose the sales officer at the main branch grants a special discount only after the manager approves it, while a colleague at another branch grants it without checking with anyone. Neither of them is wrong on purpose, but the rule isn’t written down.
Inventory in the records does not match inventory on the shelves
Discrepancies only appear at stocktake, and no one can tell when they arose or at which step. The result is orders accepted for goods that aren’t there, or slow-moving stock bought again because no one saw it in the records.
This week, pick a few fast-moving items, count them physically, compare the result with the records, and then try to trace the cause of each discrepancy.
Suppose the warehouse releases goods against a paper dispatch note that is entered at the end of the day, and some of these notes aren’t entered until the following week. In that case the records aren’t wrong, but they are always behind the shelves.
Multiple currencies and branches confuse the accounts
The organization deals in more than one currency, exchange rates change from one day to the next, and each branch has its own way of recording transactions. Comparing branches, or knowing the actual profit on each deal, becomes hard work, and the figure differs depending on who prepared it.
This week, ask two branches for the same sales report for the same period, and note which currency each one comes in, at what exchange rate, and when that rate was applied.
Suppose one branch converts its sales into the base currency at the rate on the invoice date, and another at the month-end rate. Each report is correct in its own way, but adding them together into a single figure means nothing.
Off-the-shelf tools have become a burden
The organization adopted off-the-shelf software, then started working around it with side spreadsheets and manual procedures because it doesn’t fit the way the organization works. Now the team serves the software instead of the software serving the team, and the data is split between the software and the spreadsheets around it.
This week, gather the files that are kept up to date alongside the current software, and ask of each one: what does the software not cover that made us need this file?
Suppose the sales software doesn’t support installment sales the way the organization handles them, so each installment is recorded in a separate spreadsheet, checked by hand before every collection, and missing from every report the software produces.
When several signs from this list appear together, the problem most likely no longer lies in any one tool but in the absence of a single system that connects the processes and applies the same rules at every step. A single sign on its own may need nothing more than a change in procedure or a simpler tool, and it helps to know that before you commit to a full project.
A quick self-assessment checklist
Answer each item with yes or no, based on what you actually observed this week, not on your general impression.
- The details of a single order were written in more than one place before its invoice was issued.
- A simple management question required compiling files from more than one department.
- Two employees gave different answers about the same business rule.
- A discrepancy appeared between recorded and actual inventory with no clear cause.
- The way currencies were converted, or transactions recorded, differed from one branch to another.
- The work relies on side spreadsheets because the current software doesn’t cover what you need.
If you answered yes to one or two items, start by fixing the procedure itself. If yes comes up across several related items, that is a signal that the time is right to look into a custom system.
What you should know before you decide
A system can’t make up for a process nobody has agreed on. If two departments disagree about the moment an order counts as confirmed, coding one side’s view into the system moves the disagreement onto the screen instead of settling it. That is why any serious ERP project starts by documenting the business rules and agreeing on them before a single line of code is written.
A system doesn’t fix an unclear process. It locks it in as it is.
Nor does a custom ERP system have to be a huge project delivered all at once. You can reduce the risk by dividing it into modules: start with the module that tackles the pressing problem you have today, then add the next modules once the team is used to the first one and its value shows in the work.
Involving the people who carry out the processes every day in reviewing each stage brings the exceptions to light early, and it makes the move to the system a decision the team shares in rather than an order imposed on it.
Where to start
Before talking about screens, go over the questions we set out in the article “Five questions before you start any software project” and then move on to the following steps:
- Draw up a process map of how the work actually happens today, not how the written procedures describe it.
- Write down the business rules in clear language and number them: who approves what, within which limits, and what the exceptions are.
- Choose the first module by impact: the process where time is lost or costly mistakes keep recurring.
- Agree in advance on a simple measure of success, such as the time it takes to prepare a particular report or the number of times data is re-entered.
- Plan early for migrating and cleaning your existing data; it is a step that needs its own time and its own decisions.
If you have noticed some of these signs in your organization, start by putting your current processes on the table before talking about screens and technologies. You can discuss your situation with the ITS team, so that together we can identify the first module worth starting with and what can wait.
Related serviceCustom ERP systems