Mid-market companies need ERP that maps uneven growth: new sites, products, employees, sometimes new business models. What decides are process fit, plannable cost, and the ability to extend flows without starting a large project every time. Off-the-shelf standard promises speed and often fails on special cases. Individual ERP is built around your processes and keeps source code and data in your hands. The category is not “one more module package.” It is software that carries your critical flow and grows with it.

Which requirements are typical in the mid-market?

• Process fit: Industry-specific and company-specific flows instead of permanent compromise
• Process-oriented entry: Core first, extension when the need is there (extend process-oriented)
• Integration: Connect DATEV, e-invoicing, machines, DMS, and existing systems
• Cost planning: Per-user license costs scale with growth. Open source and fixed operating models change the math
• Independence: Avoid vendor lock-in; keep operators and hosting switchable

ERP in the mid-market is not an IT topic alone. Executive leadership sets priorities, specialist areas deliver processes, IT secures operations and integration. Shared frame: What is ERP?. Without shared goals every system becomes a project construction site without benefit proof.

Why do shelf ERP and island solutions often fail?

Shelf ERP covers the average. Project business, batches, serial production, or customer-specific approvals land outside. Island solutions solve single cases and create duplicate entry at every handoff. Both cost transparency and bind capacity in reconciliations instead of in control.

Individual ERP platforms address that through adaptability at metadata and low-code level. Nuclos models flows on one data basis. Special logic is added when the core holds, not because a package sells it together. Process-first instead of module-first: you extend the flow you need, instead of activating modules you later work around.

How do you plan cost and growth realistically?

Compare total cost of ownership over five years: licenses or subscription, integration, operations, adaptations, training, exit. Per-user models punish growth even when benefit per person rises. An open-source basis and clear operating options (cloud or on-premise) make the math more plannable when scope and integrations are included.

Price anchors in the guided offer: the 48-hour prototype as entry (950 euro plus VAT, creditable) and Nuclos Enterprise from 10,000 euro plus VAT, always on agreed scope. “ERP in 30 days” is a delivery claim on that scope, not a free pass for unlimited requirements and not a product name. For specialist users and IT who want to extend themselves, Nuclos Workspace remains the self-build path.

How do you start without large-project risk?

Clarify scope and ROI before the large project. A 48-hour prototype or Spec Workshops create a reliable basis before budget and runtime are fixed. Take the core process live, measure, extend. That creates time-to-value without big-bang pressure. Change and user involvement belong from the start, otherwise the technical go-live does not carry into daily work.

Check questions:

1. Which flow causes the largest break today?
2. Which master data and integrations are mandatory for that?
3. What comes later on purpose?
4. How are exit, export, and partner change regulated?
5. Who decides functionally, who operates technically?

Which decisions come next?

Define growth scenarios and the critical process. Set TCO and sovereignty criteria. Cut the first scope. Compare vendors by process fit and switch options, not only by demo features. AI-assisted configuration helps within the platform frame. It does not replace a scope and change decision.

Further reading: What is ERP? and process structure instead of module structure. For operating-model decisions: cloud vs. on-premise.