ERP, without the brochure
ERP is one system of record for the work that makes you money and the work that keeps you legal: orders, stock, jobs, invoices, payments. Custom ERP means that system is designed around your process rather than a vendor’s module list.
Most businesses do not start here. They start with Excel, Tally, a billing package, and a folder of WhatsApp photos. Custom ERP becomes interesting when those pieces start contradicting each other, and when hiring another person to reconcile them is the current “strategy”.
When custom is justified
- Your process is unusual and it is also why customers buy from you — a packaging line, a jobbing shop, a multi-branch service operation with its own billing rules.
- You have already tried a package and the “customisation” quote is approaching the cost of a system you would own.
- You need the data model under your control because you will still be running this in ten years.
When those are not true, buy a product and implement it properly. The comparison is custom ERP versus SAP versus Odoo.
What an implementation actually looks like
Not “go live on the first of the month with everything”. A first live slice — say, orders and stock for one branch — then accounts, then production. Parallel-run the old spreadsheet until the new numbers are trusted. That sequence, and the money attached to it, is in ERP cost and timeline.
We build these as ERP solutions, usually on ASP.NET Core, because the long-term cost is in change, and a system you can change without a vendor’s permission is the point of going custom.