Skip to content

Services

From diagnosis to production

Four services you can hire on their own or as one path. They all end the same way: something working on your server and your team knowing how to use it.

Self-check

Tick whatever sounds like you

You do not need to know what to ask for. Tick one or two sentences: what fits stays lit and the rest dims.

Tick whatever sounds like you

This happens here, in your browser. Nothing is sent or stored.

01

AI agents over your own data

I set up agents that read, write and execute inside your systems using OdooClaw, my MCP server with models I trained myself. Zero cloud dependency where that makes sense.

What is usually going on

The information lives inside your systems and people still copy it into a spreadsheet to be able to think.

What you get

  • Your hardware, my trained models
  • MCP server for any client
  • Data sovereignty and predictable cost

Fits if

  • The data is already ordered inside your systems
  • There are queries a person repeats by hand today
  • You want to know what leaves your server before it leaves

Does not fit if

  • You are after a chatbot for the website
  • There is no data to search yet
  • The only condition is paying per user per month

A pilot on your real data and, if it holds up, the step into production.

02

Odoo without surprises

Implementation, migrations and custom modules built around the way your company actually works. Your Odoo should feel tailor made, not like a generic install.

What is usually going on

Every change ends up as a patch nobody understands, or there is an old version nobody dares to touch.

What you get

  • Migrations from 14, 16 and 17
  • Custom modules you can maintain
  • Deploy with Doodba and Coolify

Fits if

  • Odoo is your backbone, not a side module
  • Customisations piled up without documentation
  • A migration is on the table or close

Does not fit if

  • You want to switch ERP without a concrete reason
  • You are after installing modules without reviewing them
  • Nobody is going to maintain what gets built

Fixed scope per project, or a monthly retainer when the system is alive.

03

Process automation

I connect what you already have: Odoo, email, warehouse, accounting and the odd tool nobody owns. The repetitive work disappears and your team keeps what matters.

What is usually going on

Something gets done by hand every week and everyone assumes it has to be that way.

What you get

  • Integrations and APIs
  • Scheduled jobs and alerts
  • A trace for every run

Fits if

  • The process is defined, even if only in someone's head
  • The pieces have an API or can be connected
  • You want to know what ran, when and with what result

Does not fit if

  • The process changes every time it runs
  • It is one click a day
  • The source data does not exist yet

One process at a time, with a metric from day one.

04

Support, audit and training

I review existing setups, leave the infrastructure documented and teach your team to run it, so nobody needs me forever.

What is usually going on

It works, but nobody knows how it is wired up or what happens if it falls over tonight.

What you get

  • Performance and security audit
  • Real handover with documentation
  • Ongoing maintenance

Fits if

  • Technical or documentation debt has piled up
  • Somebody left and took the knowledge with them
  • Your team wants to run it alone, but with a safety net

Does not fit if

  • You want a vendor who never says no
  • Documentation is not in the budget
  • The goal is to depend on me more and more

A one-off audit with a written report, or ongoing support with a reserved slot.

Before we start

What I need from you

Nothing heavy. With this I can tell you whether I can help, where to start and what is not worth it.

How it starts

Three steps and we are moving

No forty page proposals. First we understand the problem, then we prove it, then we put it in production.

  1. 01

    Diagnosis

    One working session on your processes and your current setup. We come out with the concrete problem and what is actually worth automating.

  2. 02

    Working prototype

    I build something that already runs on your real data. You see it, you touch it, and we decide with evidence instead of gut feeling.

  3. 03

    Production and growth

    Deploy, monitor and document. Then evolutionary maintenance with your own team in the driving seat.

Write to me

Common questions

What people usually ask me

What is an AI agent over my own data?

A program that can read your records, understand what you ask in plain language and take real actions inside your systems. It is not a chatbot that returns text: it is another worker inside the software you already use.

Do I have to stop using Odoo?

No. Odoo is usually the backbone of the project. What I do is make Odoo work with you: agents that query, create and move records for you, plus automations that run on their own.

Which Odoo versions do you work with?

Odoo 16, 17 and 18 for new projects, and migrations from 14 and 16. I also keep older installs running while that still makes economic sense.

Do the models have to live in the cloud?

They do not have to. OdooClaw is built to run entirely on premise with my own models. When an external API genuinely beats a local model we integrate it, but you always know what leaves your server.

How does a project start?

With a diagnosis. You tell me what is holding you back, I look at what you already have, and you get a fixed scope with phases. There is no public price list because every company starts from a different place.

Can I see your code before hiring you?

Please do. All of my public work is on GitHub, with stars and forks you can check yourself. The biggest repository is OdooClaw.

Which languages do you work in?

Spanish and English, both for documentation and for meetings with your team.

Agents that work beside you, systems that maintain themselves and data that never leaves your server.