Knowledge base
Decision-oriented knowledge for executives and IT in mid-market companies
Short definitions, practical guides, and context on ERP, digitalization, and sovereignty. Compare options, weigh criteria, and avoid common mistakes before budget and scope are locked in.
-
Featured
What makes Nuclos 5 a platform for individual ERP?
Executive answer: what Nuclos 5 delivers as a platform for individual ERP, how open source, low-code, and AI work together, and how decision-makers check fit.
- Nuclos 5 builds the ERP around your processes, not around module packages, with low-code and open source (AGPL).
- AI acts in configuration and development under governance, not as uncontrolled chat in end-user operations.
- Nuclos Workspace bundles Nuclosian in the client and Nuclos MCP as the developer tool layer.
- Source code, data, and exit options stay with you. No per-user licenses.
-
What is ERP?
Enterprise Resource Planning bundles core business processes on one data basis. What that means for the mid-market, and what matters in selection and implementation.
-
When do startups and growing companies need an ERP?
When do spreadsheets and point solutions stop being enough, and what comes next: decision basics for founders and executives.
Topic areas
- Digital transformation 4
Processes, change, and digital maturity for executives and business units.
Open topic area → - Digital sovereignty 9
Resilience, data control, and independence from platforms.
Open topic area → - Business software & ERP 12
ERP modules, industries, compliance, and operation.
Open topic area → - Workflow management 6
Model, automate, and control processes in ERP.
Open topic area → - Nuclos 5 5
AI platform for individual ERP: MCP, low-code, and customization.
Open topic area → - Business decisions 11
Investment, scope, ROI, and risk before the software decision.
Open topic area →
All articles
-
What is digital sovereignty?
Digital sovereignty in the mid-market: room to act over data, operations, and dependencies. Resilience instead of technical autarky, with a clear link to ERP.
Digital sovereignty · Resilience · Mid-market
-
What does process digitalization mean for mid-market companies?
Replace manual coordination with digital workflows. What process digitalization means concretely in an ERP context, why small pilots beat big bang, and how to start.
Process digitalization · Digital maturity · Mid-market
-
What is workflow management and why do you need it?
Answer for executives: workflow management steers recurring processes with steps, roles, and rules. When it adds value and how it differs from BPM.
Workflow · Process digitalization · Process automation
-
How do you define ERP goals and scope before choosing software?
Without measurable goals, an ERP project lacks direction. How executives and IT set goals, scope, and priorities together before software or fixed price decisions.
ERP implementation · TCO & ROI · Fixed price & scope
-
What is MCP and why does it matter for individual ERP?
Lexicon answer: Model Context Protocol connects AI tools structurally to ERP metadata and configuration. What MCP means and how Nuclos uses it under governance.
MCP · AI-native architecture · Process automation
-
What is vendor lock-in?
Vendor lock-in arises when switching or exiting a software becomes expensive or practically impossible. What that means for ERP and the mid-market, and how to check it.
Vendor lock-in · ERP selection · Exit strategy
-
Which typical mistakes ruin ERP implementations?
ERP projects often fail on planning, not software. Six common mistakes and how executives and IT avoid them before budget and timeline are fixed.
ERP implementation · Project risk · Change management
-
Why is process modeling the foundation for automation?
Before workflows run in an ERP, describe processes in a structured way. What process modeling delivers, which elements matter, and how to start with a pilot process.
Process digitalization · Requirements engineering · Workflow
-
What is the difference between BPM and workflow?
Answer for ERP executives: BPM optimises processes strategically, workflow steers tasks operationally in day-to-day work. Distinction, table, and decision help.
Workflow · Process digitalization
-
Why does fixed price with fixed scope reduce ERP project risk?
Scope, price, and delivery date are fixed before the project starts. How fixed-price ERP projects limit budget risk and scope creep, compared to time and material.
Fixed price & scope · TCO & ROI · Project risk
-
What belongs in an ERP core system, and what comes later?
Which core processes should run first on one data basis, and why extensions follow the flow, not module packages.
ERP fundamentals · Process-oriented extension
-
Why is user involvement decisive in ERP projects?
ERP without input from business departments fails in practice. How key users, pilot teams, and early feedback loops secure adoption and data quality.
Change management · ERP implementation
-
Which Nuclos entry path fits your situation?
48h prototype, requirements specification, Nuclos Enterprise, or Nuclos Workspace: which entry point fits which starting situation, from idea to productive ERP in 30 days.
ERP selection · Time-to-value · Fixed price & scope · Prototyping
-
What matters for ERP in the mid-market?
Process fit, plannable cost, and independence: what executives and IT should watch when ERP must grow with the business.
ERP fundamentals · Mid-market · Process-oriented extension
-
Why process structure instead of module structure in ERP?
Answer for executives: why standard ERP thinks in modules, why that breaks your process, and how process structure keeps introduction and expansion controllable.
Process-oriented extension · Low-code · ERP implementation
-
How do you succeed at ERP data migration without losing quality?
Bad master data in a new ERP amplifies old problems. How migration, cleanup, mapping, and spot checks become plannable before go-live pressure hits.
ERP implementation · Master data · Project risk
-
What is IT resilience for mid-market companies?
IT resilience means staying able to act when disruptions hit. What that means concretely for ERP, cloud, and critical dependencies in the mid-market.
Resilience · Digital sovereignty · Mid-market
-
Why do workflows belong in the ERP, not in a point solution?
Buyer answer: workflows steer approvals and tasks directly in the ERP. Why ERP-integrated workflow management avoids media breaks and where companies start sensibly.
Workflow · Process digitalization · Process automation
-
Why is a requirements specification better than a classic tender document?
A traditional tender document is written at a desk, without a hands-on test. How a prototype-based requirements specification takes shape in one to two weeks and still stays vendor-neutral.
Specification & tender · Requirements engineering · Fixed price & scope
-
Which funding programs fit your ERP and digitalization project?
KfW ERP digitalization loan, BAFA consulting grants, and other programs: which funding fits ERP implementation and how the application process works.
TCO & ROI · ERP implementation · ERP selection
-
When does cloud ERP fit, and when does it not?
Decision support on operations, control, cost, and customization. Nuclos Cloud as an example of a cloud entry, not as a package brochure.
Cloud vs. on-premise · Process-oriented extension · Mid-market
-
When do developers need Nuclos MCP instead of Nuclosian alone?
When IT should connect custom clients and apps to Nuclos, what Nuclos MCP provides for that, and why most teams still start with Nuclosian in the client.
MCP · AI-native architecture · Low-code · Metadata model
-
What does ERP in 30 days on agreed scope actually mean?
The 30-day claim is a delivery model, not a marketing promise. What realistically fits in 30 days, what does not, and why the agreed scope makes the difference.
Time-to-value · Fixed price & scope · ERP implementation
-
Which ERP vendor fits mid-market processes?
Which ERP vendor fits mid-market processes? Delivery models compared on time-to-value, process fit, and TCO.
Vendor evaluation · ERP selection · TCO & ROI · Vendor lock-in
-
What does low-code in ERP mean for mid-market and IT?
Answer style: low-code in ERP enables individual screens, processes, and rules on the platform. What that means for mid-market companies, business units, and IT governance.
Low-code · Process-oriented extension · Metadata model
-
How does change management succeed in ERP implementations?
ERP changes workflows and roles. Change management secures adoption, structures communication, and prevents resistance and Excel workarounds after go-live.
Change management · ERP implementation
-
What pays off with open source ERP for companies?
Open source in ERP means source code access, adaptability, and freedom of choice on operations and support. What that means concretely for mid-market and IT decisions.
Open source · Vendor lock-in · Vendor evaluation
-
Which ERP requirements does manufacturing create?
Bills of materials, production orders, real-time stock, and quality: what manufacturing SMEs should check when choosing a system, and why individual processes are the norm.
Production & manufacturing · ERP fundamentals · Workflow
-
How do you model workflows before you automate?
Buyer answer: model workflows visually and traceably. Which questions must be clear before the build, and how a pilot process keeps the entry manageable.
Workflow · Process digitalization · Process automation
-
What must production planning in ERP be able to do?
Bills of materials, production orders, capacity, and stock: what manufacturing companies should clarify before choosing a system, and why standard modules often fall short.
Production & manufacturing · Workflow
-
How does quality management belong in ERP?
Inspection plans, releases, and audit trail on the production order: why QA without media breaks belongs with production and warehouse, and how to choose the entry point.
Production & manufacturing · Workflow · Compliance & audit
-
Cloud ERP or on-premise: what is the right decision?
Cloud or your own server: the choice depends on IT resources, compliance, and flexibility. Decision support for mid-market ERP decision-makers.
Cloud vs. on-premise · Data residency · TCO & ROI
-
What does an ERP prototype deliver before the large project?
A clickable ERP prototype makes processes tangible. Clarify scope and ROI before committing budget. What the 48h prototype delivers and what it deliberately does not.
Prototyping · Time-to-value · Requirements engineering
-
How do you automate processes and manage tasks in a workflow?
Buyer answer: event-based process starts, tasks with deadline and status, escalation and notifications. How workflows run reliably and traceably in the ERP.
Process automation · Workflow · Process digitalization
-
Which ERP integrations do you actually need?
DATEV, e-invoicing, REST, and DMS: which connections must be clear before go-live, and how to tell whether an ERP takes integration seriously.
Integration & interfaces · DATEV · E-invoicing
-
What belongs in an ERP exit strategy?
Clarify export, contracts, customizations, and operations before go-live. An exit strategy is risk management for leadership and IT, not distrust of the vendor.
Exit strategy · Vendor lock-in · Data residency
-
How do you monitor, authorize, and integrate workflows in ERP?
Buyer answer: monitoring and audit trail, roles and permissions, REST integration. Transparency and extensibility for running workflows without media breaks.
Workflow · Reporting & analytics · Integration & interfaces · Compliance & audit
-
How do XRechnung and ZUGFeRD get into ERP?
Receipt, validation, approval, and posting without media breaks: what mid-market companies and finance IT must clarify for e-invoicing in ERP.
E-invoicing · Compliance & audit · GoBD
-
What should mid-market companies calculate for ERP license costs?
License models per user, module, or transaction change TCO over years. What leadership and IT should watch when calculating ERP cost.
License models · TCO & ROI · Open source
-
What does GoBD require from ERP?
Traceable documents, change history, and auditable exports: what GoBD means for ERP processes and e-invoicing, and what to watch when choosing a system.
GoBD · Compliance & audit · E-invoicing
-
What does data sovereignty mean for cloud ERP?
Where do ERP data live, who has access, how exportable are records? Check data sovereignty on cloud offers: contract, operations, and exit, not only server location.
Data residency · Cloud vs. on-premise · GDPR in ERP
-
How do you run project business in ERP without spreadsheet reconciliation?
Project structure, time tracking, budget-to-actual controlling, and billing run on one shared data basis in the ERP instead of in spreadsheets and a separate project tool. Project leads and executives see the margin before the project ends.
Project business · Reporting & analytics · Workflow
-
Why does quote-to-cash break without a shared data basis?
Quote, order, delivery, invoice, and payment often run across separate systems. Why a shared data basis inside the ERP avoids duplicate entry and reporting gaps.
Workflow · Integration & interfaces · Reporting & analytics
-
What does the GNU AGPL 3.0 mean for your ERP?
The GNU AGPL 3.0 governs free use, source code access, and a disclosure duty for network use. What this license clause means concretely for customizations to your ERP. Not legal advice.
Open source · License models · Vendor lock-in