Standard package and individual project address different starting situations
A pre-configured rental model is strong when a company is willing to adopt proven standard processes and the initial scope remains clearly defined. The calculation becomes more predictable because roles, processes, and services are prepared. However, this advantage disappears if every exception is to be implemented individually immediately. Standardisation is therefore not only a technical but also an organisational decision.
An individual project makes sense when special pricing logic, multiple companies, extensive data migration, portals, or business-critical integrations determine core operations. It offers more design freedom but also requires more analysis, testing, and ongoing responsibility. The decision should not depend on the size of the company but rather on how much the business model is shaped by indispensable special processes.
A controlled expansion is possible between both models. A company can start close to the standard and later expand purposefully if the basis, versioning, and delineation remain well documented. A roadmap organises wishes according to benefits and follow-up costs. This way, it remains visible which additions will become part of the common product standard and which must be operated permanently on a customer-specific basis.
Recognising the suitable model
- Share of transactions in the prepared standard
- Indispensable special roles and approvals
- Scope of migration and integrations
- Willingness to standardisation and controlled expansion
The pre-configured rental model
A VisionSolution represents recurring processes of an industry in a defined standard. Basic setup and ongoing operation remain clearly delineated. This reduces project effort and makes monthly costs more predictable.
- 500 euros one-time setup
- 169 euros per month in the defined standard scope
- Prepared industry processes
- Additional customisation requests are offered separately
When the prepared standard fits well
The model is suitable for smaller companies whose core processes are close to the industry configuration. Particularly important are the willingness to use the prepared process, a manageable data transfer, and few individual interfaces.
The individual Odoo implementation
In the individual project, apps, roles, data, documents, approvals, and integrations are designed to fit the organisation. Implementation effort, Odoo licenses, as well as hosting or server are calculated separately.
When individuality becomes necessary
Multiple companies, complex pricing logics, extensive migrations, industry-specific evidence, individual portals or many third-party systems can exceed the standard framework. In these cases, a structured project protects against hidden compromises.
Four questions for the decision
The right choice arises less from the size of the company than from the actual complexity.
- How close are our core processes to the prepared standard?
- Which data needs to be transferred?
- Which external systems need to be connected immediately?
- Which special roles, approvals and documents are indispensable?
Objectively assess proximity to standard
A brief fit-check examines not only functions but also data, roles, documents and exceptions. If the prepared process fully covers the most common business case and special cases remain rare, a standard package is attractive.
If core revenue depends on individual pricing rules, portals, multiple companies or specific evidence, the scope should not be artificially squeezed into a package. An honest delineation protects both sides.
- Share of transactions in the standard process
- Number of indispensable special roles
- Scope of legacy and master data
- necessary integrations for launch
- industry-specific document and evidence obligations
Switching from the rental model to an expansion stage
A pre-configured start can be expanded later. For this, extensions must remain versionable, documented and distinguishable from the standard. Before any expansion, it will be checked whether configuration is sufficient or if individual development is sensible.
A roadmap prevents many small individual requests from gradually undermining the original advantage of the standard. Recurring requirements can flow into the product base; custom logic remains managed separately.
In conclusion
Frequently asked questions on the topic
Are there really no further standard costs included in the rental model?+
For the defined standard scope, a one-time fee of 500 euros and a monthly fee of 169 euros apply. Individual extensions or special adjustments are offered separately in advance.
Can a VisionSolution be expanded later?+
In principle, yes. Before any expansion, it will be checked whether it is possible within the standard or needs to be planned as a separate adjustment.
Is an individual project tied to a specific industry?+
No. An individual Odoo implementation can be planned independently of the industry along the actual business processes.