Odoo_

Sound familiar?

Odoo runs your business. Not as a side tool - as the actual system of record for purchasing, sales, warehouse, and accounting. Over the years it's been shaped around how your company really works: custom modules here, an integration with your warehouse partner there, a report someone in finance asked for two years ago that everyone now depends on.

To keep that running, you've built up a small internal team - a developer, maybe a sysadmin, sometimes both wearing several hats. They're competent people. But you didn't start this company to run an in-house software shop, and you can feel it: every hire is a gamble, every vacation is a coverage gap, and every time someone asks "can we get better numbers out of Odoo than this?" the honest answer is "not really, not without more headcount."

That's the quiet tax most Odoo-run companies pay without ever putting a number on it. We put a number on it below.

Devlr_ takes over your Odoo end to end - the codebase, the infrastructure, the support tickets, the change requests, the "why did this break" calls. One team, one monthly bill, one person you actually know by name.

We can do this at a fixed cost because of how we work: computer science and data science engineers, working alongside agentic AI systems built specifically for Odoo's internals, do the work of a much larger traditional team. You get the coverage and depth of a full department without carrying it on your own payroll.

The Pod: A self-contained team of specialised professionals (such as developers, designers, and architects) working together.

Minimum term is 6 months for Care and Partner, 12 for Command — long enough for us to actually know your business, short enough that you're never stuck.

We bill in points, not hours, because nobody wants to argue over a timesheet:

• A quick fix or question is 1 point.
• A proper change request — a new field, a reworked report, etc. — is 3 points.

Points reset every month; they don't carry over, and neither do we let work quietly balloon past what's included. If something's clearly bigger than a change request — a new module, a new integration, a real project — it gets its own scope and its own quote, agreed with you before anyone touches it. You'll never open an invoice and find a surprise on it.

Signing up doesn't mean waiting around while we "get up to speed" in the abstract. Here's the real sequence:

By the start of month two, full SLA coverage is live and we're already working from a documented understanding of your business — not guessing.

"Fixed cost" only means something if it comes with a promise attached. Here's ours:

If we miss a critical SLA, you get a day of plan value credited back — no discussion needed. And when something does escalate, it always reaches an actual person: your engineer, then your PM, then a tech lead. Never a ticket sitting in a queue.

Every month you get a short, honest scorecard: how we did against SLA, how many points you used against what's included, and how satisfied people on your team were with each ticket. No dashboards to log into, no black box — just the numbers that tell you whether this is working.

Return on investment is the real test of a plan like this — not a promise, a number you can check every month. Start with the sticker price of an in-house developer, which is never the real cost. Here's what a typical setup — one Odoo developer plus a part-time sysadmin — actually adds up to once you count what usually gets left off the spreadsheet

And that's before anything actually breaks — before the person who understood your customisations gives notice, before a busy month forces you to scramble for a contractor. Our Partner plan replaces that whole setup for €54,000 a year, backed by a contractual SLA instead of a hope that nobody quits.

That's the ROI in plain terms: a fixed, predictable plan that costs less than the payroll it replaces, and starts paying for itself before your first change request is even filed.

Is this really a team, or one person with some AI tools bolted on?
It's a team of computer science and data science engineers working alongside AI agents — that's the honest version. You get a real, named PM as your point of contact, so you're never waiting on one engineer's calendar or wondering who's actually behind the work.

If we ever leave, what happens to our code and our data?
It's yours, full stop. We document as we go, so nothing lives only in one person's head. Exportable database, no proprietary glue, no lock-in — your stack, your rules.

What's not covered by the plan?
Anything past a quick fix or a bounded change request. New modules, integrations, or bigger redesigns always get scoped and quoted separately, and you approve it before anyone starts. No surprises on the invoice, ever.

Who actually has access to our system?
You always know exactly who, when, and why. Access list and audit log available on request, and a formal off-boarding process the day the contract ends.