Services · Odoo 17, 18, 19

What we do — and what we measure it against.

Six services that overlap in practice. Almost every project starts at the first and ends at the last.

You don't need to know in advance which of them you need. That's part of the estimate, and the estimate is free.

Odoo 17 · 18 · 19maintained across three major versions
Source code includedno lock-in, no subscription on your own code
No external callsno CDN, no telemetry, fonts served from your own server
Based in BavariaGerman invoicing, reply the next working day

In detail

From the first assessment to the version upgrade.

Consulting and assessment

Before anything gets built, we establish whether it needs to be built. We look at how the process actually runs today, where it breaks down, and how much of that your existing system already covers — Odoo as readily as an industry package or a grown Excel landscape. Often the result is a configuration rather than a contract, and that is exactly what we tell you.

Billing: First assessment free, then by effort

Implementation

Odoo from an empty system to the point where your team works in it: module setup, migration of existing master data, access rights per role, print templates with your letterhead, and training for the people who use it daily.

Billing: Fixed price against an agreed scope

Customizing existing systems

The most common case: the system is already running, but it doesn't fit in three places. We change views, reports, calculations and print templates — and keep that separate from the core so the next update doesn't tear anything apart. That separation is where most grown systems fail. We read existing in-house development first, because it usually determines what is sensibly possible. In Odoo we know that boundary most precisely.

Billing: By effort, with a cap agreed up front

Module development

When a process repeats and isn't cleanly represented anywhere, it becomes a module of its own — with translations, access rights, documentation and a structure that survives the next version upgrade. Two such modules are on the official Odoo Apps Store and are maintained by us across three Odoo versions.

Billing: Fixed price for a clearly scoped module

Integrations and automation

Data maintained in two places is wrong in one of them. We connect systems that ought to know about each other — shop, accounting, shipping providers, time tracking, machine data — or automate steps that someone triggers by hand today. Whether Odoo sits on one side changes little about the task: it comes down to two sets of records and which one leads.

Billing: By effort; fixed price for a defined interface

Migration and support

In a version upgrade the standard is rarely the problem — the custom-built part is. We migrate including in-house development, always test on a copy, and only go live once the copy runs cleanly. The same holds for moving from one system to another: read what is there first, then decide what comes along. With Odoo we have done this ourselves across 17, 18 and 19.

Billing: Migration at a fixed price, support by effort

Process

How a project starts with us.

Four steps, and you can stop after any of them. The most expensive mistake in ERP projects is starting to build too early.

Conversation about the processYou describe how it runs today and what should be different at the end. Free of charge.
AssessmentWe say what the standard can do, what would have to be built — and what we'd advise against.
Quote with a priceBefore any work starts. Fixed price for a clear scope, otherwise by effort with a cap.
Delivery and handoverTested on a copy, with source code and documentation for you.

Describe your process