Others offer modules. We start with your process. That is not a slogan. It is the architecture decision behind individual ERP: process structure instead of module structure. Standard ERP organises work by function packages. Your business runs across that, in processes across departments. Anyone who adapts the system to modules often maintains the real process in parallel in spreadsheets. Anyone who adapts the ERP to the process keeps the record in the system. For executives and business units that is the central buying decision: does the software follow your process, or do you force your process into the software?

What module thinking costs in daily work

Module packages look tidy: inventory here, finance there, each with its own logic and its own boundary. In practice the expensive friction sits exactly at those boundaries. Status, stock, and open items live in different views. Handoffs run via export, email, or shadow lists. Approvals hang on personal knowledge, not on the record.

The result many mid-market companies know: the ERP is “live”, yet the critical process still runs outside. Double maintenance, inconsistencies, and long alignment times are then not a user problem. They are an architecture consequence. More on the product view and continuous processes: Business processes.

What process structure means in practice

Continuous processes. A record runs from start to finish without a break between systems or departmental islands. Status, stock, and open items stay visible on the same object. Anyone who opens the order sees the same state as purchasing, manufacturing, or service.

One data basis. Master data and transactional data are captured once and used everywhere. No second truth in an adjacent tool. Interfaces complement, but they do not replace central record leadership.

Grows with the business. When a process changes, the system changes with it. The next process area is added when it is needed, not because a license package forces it.

That is the counter-position to module thinking: not “which module do we book next?”, but “which process is still missing, and how does it hang on the existing record?”

Entry without big bang

Process structure does not mean digitizing everything at once. Typical starts are the areas that carry the operational core: inventory and production, projects and service, order management and finance. They access the same data basis and can be combined freely.

When growth or new requirements arrive, you connect the next process or sharpen an existing one. Data stays. No system change, no full re-import. That lowers project risk and makes interim results usable earlier. That is why process structure and fixed-price delivery fit together: scope hangs on the process, not on module boundaries. Entry via Nuclos Enterprise or the 48h prototype makes the core process visible early.

Nuclos models individual processes on the same platform, via low-code or development. Specific manufacturing, project, or approval processes emerge without a parallel point solution. Your process decides what comes next, not a fixed package. Deeper reading: Low-code in ERP.

Prerequisites decision-makers should know

1. Clear priority: which process delivers measurable value first?
2. Clean master data before the next process is connected
3. Involve business departments early, not only at go-live
4. Think interfaces to DATEV, e-invoicing, and third systems from the start

Process structure does not replace strategy and does not replace a requirements document. It makes ERP introduction and expansion controllable because scope hangs on the process, not on module boundaries. Anyone who tries to resolve unclear responsibilities inside the system only digitizes chaos. Clear rules first, mapping after.

When process structure is the right answer

Process structure fits when your competitive advantage sits in your own process: special logic in manufacturing, project business, service, or approvals that standard modules only cover with workarounds. It fits less when you deliberately take over standard processes one-to-one and consciously avoid deviations.

For the mid-market the typical situation is the first: the process is the advantage. Then individual ERP is the consistent answer, not another module add-on. Fundamentals: ERP for the mid-market and What is ERP?. Platform overview: What makes Nuclos 5 a platform for individual ERP?.