Skip to Content

Your Odoo, made fast. Or built right from the start.

I'm Oleg, an independent Odoo architect. I migrate versions, write the modules Odoo does not ship, and make slow systems fast. Where there is no Odoo yet, I build the first one. Versions 15 through 19.

Half an hour on a call, your screen, your real system. I answer messages within an hour or two.

Three reasons people get in touch

Almost every project starts as one of these three sentences, said out loud on the first call.

Performance

“Search takes eight seconds and the warehouse waits.”

Slow queries, a front end carrying code nobody uses, Core Web Vitals in the red. I measure first and change second, and you get the numbers from before and after. Elasticsearch when Postgres stops being enough.

How performance work goes

Migration

“Our migration was quoted at six months and nobody can explain why.”

Architecture review, then the move itself with your data and your custom modules, from any version to any newer one. What breaks is found on staging, not on the system your people work in.

How a migration goes

First implementation

“We are still on spreadsheets and not sure Odoo even fits.”

Data model, roles, reports, and the integrations you actually need: payments, search, other people's APIs. Sometimes the honest answer is that Odoo is the wrong tool, and you hear it on the first call.

How an implementation goes

All Odoo services

Start with half an hour about your Odoo

Tell me what your system does today and where it hurts. We spend half an hour on it, and you leave knowing what I would do first.

A conversation, not a pitch

Half an hour on a call, your screen, your real system. No slides and no discovery questionnaire.

What to do first

The order of work and a rough idea of the effort. If the job turns out to be small, you hear that too.

An honest answer

Including “Odoo is the wrong tool here” or “this task is not mine”. The call is free because it is not a way to sell you a project.

Odoo 15 - 19 Odoo 15 - 19 Odoo 17 Odoo 17 Odoo 18 Odoo 18 Odoo 19 Odoo 19 Odoo eCommerce Odoo eCommerce OWL QWeb QWeb Figma Figma Python Python FastAPI FastAPI Celery Celery PostgreSQL PostgreSQL Redis Redis RabbitMQ RabbitMQ Elasticsearch Elasticsearch Docker Docker Traefik Traefik Nginx Nginx Cloudflare Cloudflare Grafana Grafana CI/CD CI/CD React React Paddle Paddle

What happens after the call

Four steps, written down before anything is built, so you always know which one we are in.

  1. 1

    We look at your system

    A call and access to what already runs. I say straight away whether the task is mine, and what it costs to leave things as they are.

  2. 2

    A written estimate

    Data model, module boundaries, integration points, split into stages. You see what you are paying for before a line is written.

  3. 3

    Staging first, production after

    Every change is rehearsed on a copy of your data. Production gets it once you confirm, and there is always a way back.

  4. 4

    Handover you can read

    Monitoring, backups, documentation. If you hire an in-house team later, they inherit a system rather than a puzzle.

One Odoo engineer, from the first contact to production

I'm Oleg, an independent Odoo architect and developer registered as a sole proprietor in Ukraine. No account managers, no handover between teams: the person who estimates the work is the one who writes and ships it.

Documentation and calls in Ukrainian, Russian, English or Romanian - whichever your team actually speaks.

Hands-on Odoo
3.5 years
Clients
the EU, the USA and Asia
Working languages
Ukrainian, Russian, English, Romanian

All contacts on one page →

Not sure yet? That's what the call is for.

Half an hour, no slides, and an honest answer on whether I'm the right person for it.

Free consultation