Odoo implementation and customisation — in stages, fitted to your process.

When Odoo is the right choice — and when it is not.

Odoo is not just a CRM. It is a modular business system in which CRM, sales, inventory, purchasing, manufacturing and projects share one database. That is its main advantage — and its main risk, because it is easy to switch on far more than a company can start using.

Odoo usually pays off when:

• sales are tied to the movement of goods — inventory, picking, deliveries;
• you need several modules that talk to each other rather than one standalone tool;
• the process has specifics that will need customisation, and it matters that the customisations remain yours;
• Odoo is already in place, but staff work around it and go back to spreadsheets.

When we will recommend something else. If all you need is a sales pipeline and email follow-up, a dedicated CRM will be quicker to implement and easier to use. If nobody in the company will own the system, or the budget is under a few thousand, Odoo will be left half-finished — and a half-finished Odoo is worse than a spreadsheet. If it is not yet clear whether Odoo is the right system at all, it is cheaper to start with an IT and AI audit.

Three situations companies come to us with.

A new Odoo implementation

We start with the one process that creates the most manual work today — usually CRM and sales, or inventory. We configure it, migrate the data, train the people who will use it, and only then add the next module. We build customisations where the standard Odoo flow does not match how work is done in your company.

Sorting out and customising an existing Odoo

A common situation: Odoo is in place, but half the modules go unused, the fields have grown wild, and part of the process happens in email. We establish what is actually used, what blocks upgrades and where staff bypass the system — and fix exactly that, rather than everything at once. We can also take over a system implemented by another vendor.

Integrating Odoo with other systems

Odoo is rarely the only system in a company. We connect it to accounting, the online store (for example WooCommerce), courier services, document signing and e-invoicing, so data is entered only once. More on this on the systems integration page.

One module live before the next one starts.

An implementation that starts with eight modules almost always ends with two in use and six that create noise. That is why the work is split into stages, and each stage pays for itself.

Stage 1 — process and data

Conversations with the people who carry out the process every day, not only with management — because the system has to fit how the process runs, not how it is described. At the same time we check the quality of historical data: duplicate customers, empty fields, inconsistent names. That is a task for the start of the project, not the end.

Stage 2 — the first module

Configuration, the customisations that are needed, data migration and training. The new flow runs alongside the existing one for a while, and we switch off the old route only once the new one works correctly.

Stage 3 — further modules and integrations

The next modules and the connections to other systems, ranked by return. You can stop at any point — whatever is already in place keeps working.

Stage 4 — handover and an owner

Documentation, access and the customisation code in your repository. We agree who in the company owns the system — without that, a year later nobody knows why a particular field exists.

In Latvia it is almost always integration, not migration.

Odoo has its own accounting module, and the first impulse is to use it. In practice, for companies operating in Latvia, accounting usually already runs in a local system that the accountant or an outsourced bookkeeping firm knows well and that is set up for local reporting requirements.

So the solution we recommend most often is a clear boundary: sales, orders and inventory live in Odoo, and finished documents — invoices, delivery notes and payment statuses — go to the accounting system. That costs far less than moving accounting and does not require retraining people.

When the problem called “the CRM does not work” is somewhere else.

Verbasco, a B2B supplier of industrial components in Valmiera, came to us with a question about Odoo CRM. Tracing the data flow showed that the largest share of manual work was at the end of delivery: delivery confirmation and document signing happened outside the system, shipment by shipment. Both steps were pulled inside Odoo, and the CRM was fitted to the actual sales process. Day-to-day deliveries never paused.

Other Odoo CRM projects in 2025 include Airlux, as well as CRM customisations for several clients whose names we do not publish. The full case study is currently published in Latvian only; ask for it on the call and we will walk through it in English.

The licence is the smallest part of the cost.

The most common surprise in Odoo projects: licences and hosting make up roughly 10—20% of the total cost. The largest share — around 50—60% — is configuration and customisation, and 25—35% is data migration and training. A quote that allows a few hours for data migration is not a cheaper quote — it is the same project with a missing part that will come back after go-live.

Prices exclude VAT and are a starting point, not a quote. Each stage is estimated and approved separately, so you never sign for a sum covering work whose scope nobody knows yet.

Questions asked before an Odoo implementation.