AssembloERP
Nearly every owner we talk to asks the question the same way: "are we big enough for an ERP yet?" It is the wrong question. Size is not what breaks a business's data. Duplication is.
The moment the same number — today's closing stock, this month's dispatch, what a customer owes you — lives in three places, someone has to reconcile it. That someone is usually you, at 10pm, with a calculator.
The 12 signs you have outgrown your current setup
Not all of these carry the same weight. The first four are the ones that, on their own, are usually enough.
- Physical stock and book stock disagree, and nobody can say why. If a count takes a day and the variance is still unexplained afterwards, your recording layer is broken. We wrote a whole piece on the seven usual causes.
- You quote from memory. If pricing a job depends on one person's feel for material cost, your margin is a guess. See true job costing.
- Material goes out for job work and comes back short. Scrap, loss and vendor over-consumption are invisible without tracking. This is the single most expensive blind spot in Indian manufacturing.
- Two people maintain two versions of the item master. Different codes for the same part means every report is quietly wrong.
- Month-end takes more than three days to close.
- You find out about a stock-out from the customer, not the system.
- Purchase decisions are made by walking to the godown and looking.
- You have more than one branch or godown and no live view of either.
- Batch, lot or expiry matters to your buyers and you track it on paper.
- Your team WhatsApps photos of registers to each other as a workflow.
- A GST notice or audit query takes days to answer because the trail is spread across files.
- Your best operations person is irreplaceable — because the process lives in their head.
Five reasons to wait
We turn away business over these, because an ERP bought at the wrong moment gets blamed for problems it never caused.
1. Your product or process is still changing every month
If you are still deciding what you make and how, any system you configure now will be re-configured twice. Get the process stable first, even on paper.
2. One product, one location, one person entering data
A single-SKU trader with one godown and one operator does not have a data problem. A good billing tool plus disciplined stock entry is enough. Come back when you add the second location.
3. Nobody internally owns the data
Software does not create discipline. If no one is accountable for item codes, opening balances and daily entry, an ERP just distributes the mess wider and faster. Appoint the owner before you buy the tool. This is the number one cause in the projects that fail.
4. You are mid-audit or in the last month of the financial year
Never go live in March. Cut over at the start of a quarter, ideally at the start of the financial year, with clean opening balances.
5. The real problem is one specific gap
If the pain is only e-invoicing, or only dispatch paperwork, buy or build for that. A full ERP to solve one workflow is expensive theatre. Sometimes the honest answer is a small custom build instead.
What "ready" actually looks like
| Area | Ready | Not yet |
|---|---|---|
| Item master | One code per item, agreed by stores and accounts | Two lists, two naming styles |
| Ownership | A named person accountable for data | "Everyone" enters data |
| Process | Stable for at least two quarters | Changing monthly |
| Opening stock | Countable within a weekend | Unknown, historically |
| Sponsor | Owner or a director actively involved | Delegated to the IT vendor |
If you are on the line
The cheapest next step is not a demo. It is a count. Pick your ten highest-value items, count them physically, and compare with your books. The size of that variance tells you more about your readiness than any feature list.
Then, if the numbers do not match, look at what an ERP actually costs before you look at features — we published a full three-year cost breakdown, including the parts vendors leave out.
