Nuclos offers four entry points: 48h prototype, requirements specification, Nuclos Enterprise, and Nuclos MCP. Starting on the wrong path costs mainly time, not money. Each path is bookable on its own and combinable. Executives and IT leaders should clarify the starting situation first: what is already defined, and who will operate and extend the system later?

When does the 48h prototype fit?

The 48h prototype fits when scope is still unclear or you need to test whether Nuclos matches your processes. There is no complete requirements document, internal approval for a larger project is missing, or the team needs a tangible result instead of slides.

In a two-day workshop we model one sub-process as a clickable ERP prototype. Fixed price 950 Euro plus VAT. Your team tests the result. When you commission Nuclos Enterprise, we credit the investment. The prototype continues; it is not discarded.

A weaker start when scope and requirements are already clear. Then go directly to Nuclos Enterprise.

When does the requirements specification fit?

The requirements specification fits when requirements must be elicited in a structured way. Multiple stakeholders need to align before the project, or you need a vendor-neutral document for internal decisions or tendering.

The result is a robust specification document you own. No vendor binding. It serves as input for Nuclos Enterprise or external tendering. Cost depends on scope and workshop depth; proposal after a short discovery call.

When does Nuclos Enterprise fit?

Nuclos Enterprise fits when requirements are clear: your own specification, completed requirements document, or output from the 48h prototype. You want guided delivery with fixed price and go-live date. No in-house IT team for self-build.

Result: productive ERP on agreed scope, go-live typically within 30 days. Fixed price from 10,000 Euro plus VAT, binding in the proposal. Open source: code and data stay with you. Additional scope is planned as phase 2.

When does Nuclos MCP fit?

Nuclos MCP fits when an in-house IT team or development partner wants to build and iterate independently. You already run Nuclos and want to extend it. Consultants or integrators deliver Nuclos projects on their own.

Result: cloud-based development environment with low-code, AI, Git, Jira, MCP, and deployment automation. Monthly subscription by package. Same platform as Nuclos Enterprise. Many customers combine guided first delivery and later self-build.

Entry paths at a glance

All paths use Nuclos 5 as the platform. Many customers start with the prototype and move to Nuclos Enterprise. Existing customers extend via Nuclos MCP. Before the project, review common pitfalls: ERP implementation pitfalls. Non-binding orientation in a contact call.