Odoo experts for Community and Enterprise. We write the code into your repository with documentation, tests and upgrade notes, so any Odoo developer can maintain it. The price is fixed in writing before we start.
If standard Odoo or a setting already does what you need, we'll tell you on the call.
Per module: about 2 weeks · €1,500 to €4,000 · fixed price
Each piece of work sits in its own module on top of standard Odoo, so the core stays upgradeable. Where we haven't shipped something yet, we say so.
New records, screens, rules and reports for a process standard Odoo doesn't cover: approval steps, pricing rules, work orders, the PDF layout your auditor or gestor asks for.
Odoo connected to the services around it, with retries, logs and an alert when something fails, so an error never passes silently.
Several legal entities in one database: company-aware records and access rules, intercompany sales and invoices, reports per entity and consolidated.
Community or Enterprise, on Odoo.sh or on-premise. Whatever version you run, we confirm the fit in the spec, before you commit to a build. Upgrading? We port your custom modules too.
Three steps. You can stop after any of them, and you know the price before any code is written.
Walk us through the process and your setup. We tell you straight whether it needs a module, a setting, or something Odoo already does.
Standard Odoo does it? Then you don't need us.
We go through the process in a test copy of your database and write the spec: records, screens, access rights, edge cases, tests and what stays manual.
Build with another Odoo developer? The spec still works.
We build in a staging copy, you test it there, and it goes live only with your sign-off. Code, docs and tests land in your repository.
Stop at any milestone. You own everything we build.
Bigger than one module? Intercompany across several entities, for example, is split into modules, each with its own fixed price in writing.
We don't have client references to show yet, so here is our own. Antonio co-founded a subscription business with a fleet, a workshop and monthly billing, and runs it on Odoo 18 Enterprise with 22 custom modules he wrote. This is what they took off people's desks.
By business area: jobs that now run on their own, with a person on the exceptions.
We count only the modules Antonio wrote: 22 of the 38 add-on folders in that company's repository. The rest came from earlier developers or the Odoo App Store, or are internal tools.
The same jobs exist in most companies of 15 to 250: reconciling payments, reading supplier bills, scheduling work, answering customers, reporting. That's where we start with you.
The aim: if we were unavailable tomorrow, another Odoo developer could take over the work.
We commit to your GitHub, GitLab or Odoo.sh repository, never to ours. You pick the licence: LGPL-3, the same as Odoo Community, or a private one. Odoo's Enterprise licence lets you license modules built on it as you choose, as long as the licence is compatible with Odoo's terms.
Every module ships with a README covering what it does, its settings, the access rights it adds and how to switch it off. Every release gets a dated changelog entry.
Automated tests cover the rules that move money, stock or access, and they run before every release.
Odoo supports each major version for three years, and a database with custom modules can't be upgraded until those modules are ported. So each module ships with notes on what a port will involve, and we quote the port at a fixed price when you're ready to move.
We use Odoo's own patterns: inherited models and views, record rules, migration scripts. Nothing that only we understand, and nothing you need us to run.
Most of these take minutes. Anything you don't have, we sort out together on the first call.
Version, edition (Community or Enterprise) and hosting: Odoo Online, Odoo.sh or on-premise.
A list of the custom and App Store modules installed, so nothing we build collides with them.
The documents, the screens and the exceptions of the process, as it happens today.
Or access to a staging branch. We don't build or test in production.
Or we create one in your company's name and hand you the keys.
For the 90-minute spec session, and to test the module before go-live.
The person who approves the spec and the go-live. Usually finance or operations.
A short summary for your IT team.
We build and test in a copy of your database or a staging branch. Production only at go-live, with your sign-off.
Any access we get is a named user you can switch off at any time. We don't share logins.
A plain Odoo module sends nothing to an AI model. If AI would help, the spec names the service and the data, and nothing is sent without your written approval.
Code, docs and data live in your repository and your hosting. We delete our working copies when the project closes.
Need a DPA, a vendor questionnaire or anything else for group IT? Tell us on the call what your procurement requires.
We'll point you to the app or the setting. A module you don't need is a module you have to maintain.
Odoo doesn't allow custom modules there. We'll explain what moving to the Custom plan involves before you spend anything with us.
We're a two-founder firm. We stand behind what we build against the spec, but we're not a round-the-clock support desk.
That's the risk we design for. The code lives in your repository, not ours. Each module has a README, a changelog and tests, and follows standard Odoo conventions with no private framework underneath, so any experienced Odoo developer can take it over. At handover we walk your team, or your next developer, through every module. You never need us to keep it running.
You do. We hand it over under the licence you pick: LGPL-3, the same licence as Odoo Community, or a private licence. Odoo's Enterprise licence allows modules built on it to be licensed as you choose, as long as the licence is compatible with Odoo's terms.
It can. Odoo's Standard plan runs on Odoo Online, where custom modules aren't allowed. Custom code needs Odoo's Custom plan on Odoo.sh or on-premise, and Odoo.sh hosting is billed separately. Odoo also lists multi-company under the Custom plan. We check your plan on the first call, before any spec.
Community or Enterprise, on Odoo.sh or on-premise, and we port custom modules when you move to a new version. Whatever version you run today, we check your setup during the spec, before you commit to a build.
Odoo supports each major version for three years, and a database with custom modules can't be upgraded until those modules are ported to the new version. Odoo's plans don't include maintaining custom code, so we plan for it: every module ships with upgrade notes, and we quote the port at a fixed price when you're ready.
Yes. Most of our automation work isn't Odoo-specific: we build around email, WhatsApp, Google Workspace or Microsoft 365, spreadsheets, your CRM and your accounting software. See how we work with any stack.
Not in production yet. Our own operation is a single company, so our shipped work is single-company. We build to Odoo's multi-company rules, and we scope intercompany flows in the paid spec, against your entities, before we quote a build.
Not without your written approval. A plain Odoo module calls no AI service. Where AI would help, for example reading supplier invoices, the spec names the service and the data involved, and you decide.
The call is free. The written spec is €350, and it comes off the build if you book within 30 days. A single module is priced at €1,500 to €4,000, fixed in writing in the spec, with a build window of about two weeks. Bigger work is split into modules, each with its own fixed price.
We take on one or two builds a month, so the spec gives you a start date and a delivery window before you pay for anything beyond it.
Every build includes a check 30 days after go-live, and we fix anything that doesn't work as the spec says. After that, changes are quoted the same way: scoped, priced and agreed before we start.
Bring your Odoo version and one example of the process. You'll leave knowing whether you need a module at all, and roughly what it would take.