ERP (Enterprise Resource Planning) bundles core business processes on a shared data basis. Typical areas are finance, purchasing, warehouse, orders, production, and HR. The goal is transparency across the value flow, less duplicate entry, and traceable handoffs between departments. In the mid-market, ERP often replaces island solutions of spreadsheets, specialist software, and manual interfaces. What decides is not the feature catalog, but whether the software maps your actual flows. Individual ERP means: the system is built around your processes, not the other way around.

What does ERP deliver in daily work?

One source for master and transaction data. Customers, articles, stock, and documents are maintained once and used across multiple flows. Departments see the same status instead of spending month-end on reconciliations. Reporting is based on transactions, not on exported island snapshots. Approvals, stock, and order status sit on the object. That lowers coordination effort and error risk at the same time.

That sounds obvious and still fails often: when systems are organized by modules while the process runs across them. Then parallel maintenance appears exactly at the handoffs ERP is supposed to close. Counter-model: process structure instead of module structure. Process-first means: you select and extend along the flow, not along a module menu.

What is ERP not?

Not a substitute for clarified processes. Not an automatism that “digitizes” the organization without change. Not a synonym for maximum module scope. And not a one-off project: after go-live come growth, regulation, and new flows. Systems that can be extended amortize over the long term. Systems that push every special case into spreadsheets create hidden cost.

“ERP in 30 days” is a delivery claim on agreed scope, not a product name. The guided offer is called Nuclos Enterprise. The category remains individual ERP: built around your processes, at fixed prices, on an open-source basis. Source code, data, and decision freedom stay with you. That distinguishes sovereign platforms from pure subscription silos.

What matters in selection?

• Process fit: Does the system map your critical flow, or do you force compromises?
• Adaptability: How do special paths arise without an island solution?
• Integrations: DATEV, e-invoicing, DMS, shop, machines documented and maintainable?
• Operating model: Cloud, on-premise, or hybrid, including exit and export
• TCO and dependence: License logic, partner change, vendor lock-in

Deeper on lock-in: vendor lock-in. Manufacturing specifics: ERP in manufacturing. Mid-market perspective: ERP for mid-market companies. Feature lists alone are not a selection criterion. The critical process and exit options decide.

How does implementation succeed without big bang?

As a change project with shared goals from executive leadership, specialist areas, and IT. Realistic scope boundaries. Data strategy before mass import. Core processes first, extension when master data and acceptance hold. Teams that adopt standard processes without review often bend existing flows without benefit.

In practice: choose one end-to-end subprocess, take it live, measure, then attach adjacent flows. That lowers risk and makes benefit visible earlier. What belongs in the core and what comes later: ERP core system. A 48-hour prototype or Spec Workshops clarify scope before Nuclos Enterprise (from 10,000 euro plus VAT) starts on agreed scope. Productive ERP in 30 days on agreed scope presupposes that clarification.

Which decisions come next?

Formulate the critical flow and the measurable break ERP should close. Clarify operating model, integrations, and sovereignty requirements. Cut scope for the first productive step. Compare vendors not only by feature lists, but by process fit and exit. For self-build and AI in the client, Nuclos Workspace is the entry for specialist users and IT. For guided delivery, Nuclos Enterprise remains the product name, not the delivery number.

Further reading: ERP for mid-market companies and process structure instead of module structure. For manufacturing: ERP in manufacturing.