Business processes · ERP
Process-led ERP design: the system follows the process
Two ways to design an ERP
Feature-led design
- Starts from what the software can do
- Every department asks for its own fields and reports
- Old workarounds are rebuilt in the new system
- Customisations pile up and make upgrades harder
- Users learn screens, not processes
Process-led design
- Starts from the agreed end-to-end process
- Each record has one owner and one place it is entered
- Standard functionality is used wherever the process allows
- Customisation is the exception and is justified case by case
- Training follows the process each person runs
What the design covers
- 01
Organisation structure
Companies, branches, warehouses, cost centres and how they report and consolidate. - 02
Master data
Customers, suppliers, items, price lists and the chart of accounts: structure, naming and who maintains each. - 03
Transaction flows
The documents and statuses for each process, such as quote, order, delivery, invoice, and what each step posts. - 04
Controls and approvals
Approval limits, segregation of duties, locked periods and audit trail. - 05
Integrations
Which system owns which data, what moves where and when, and how errors are handled. - 06
Reporting
The reports and dashboards each role needs, built from data captured in the process rather than added afterwards.
Why it saves money
Every customisation has to be specified, built, tested, documented and maintained through each upgrade. Every duplicate data entry point creates reconciliation work. Process-led design reduces both, which is why it lowers the cost of implementation and the cost of running the system for years afterwards.
It works with any ERP. We use it for every ERPNext implementation, and we can apply it to projects on other platforms alongside your chosen partner. See also what drives ERP cost.
FAQ
Frequently asked questions
What is process-led ERP design?
It is an approach to configuring an ERP in which the agreed business processes drive the design: organisation structure, data, documents, approvals, integrations and reports. The system is set up to support the process rather than the process bending to the software.
Does process-led mean we never customise?
No. It means customisation is the exception. If a process step genuinely creates value and the standard system cannot support it, a customisation can be justified. What we avoid is rebuilding old workarounds.
Can you do the design if another partner implements the ERP?
Yes. We can lead process mapping and design, write the requirements and acceptance tests, and work alongside your implementation partner so the configuration matches what the business agreed.
Talk to us about your ERP or IT
Tell us where things stand and what is getting in the way. We will tell you plainly whether and how we can help.