For operations teams - Odoo, ERP and AI automation
Your ERP should fit the business, not the other way round.
We build, extend, upgrade and rescue Odoo systems for growing businesses, and wire practical AI into the workflows that run on them. Every change is versioned, tested on a copy of your data and shipped with a written way back.
$ ramco odoo --review your-system modules custom, in git, documented ok studio edits tracked, not orphaned ok upgrade tested on a prod clone pass security access rules reviewed pass deploy rollback written first live $ ramco ai --attach workflow model = fit for the task data = stays in your systems human = in the loop
What we do
Odoo Community or Enterprise, cloud-hosted or on your own servers. From a single custom field to a full implementation.
Custom modules
New models, screens, reports and automations built as proper, upgradable modules.
- Python, OWL, QWeb
- Portals and dashboards
Studio to code
Turn fragile Studio customizations into versioned modules you can test and upgrade.
- Field-safe conversion
- No data loss on upgrade
Upgrades and migrations
Move between Odoo versions, or off spreadsheets and legacy tools, without losing history.
- Rehearsed on a clone
- Data import pipelines
Integrations
Connect Odoo to email, calendars, payment, mapping and the other tools you rely on.
- REST and JSON-RPC
- Microsoft 365, Google
AI automation
Agents and LLM tools that draft, classify, summarize and route work inside your ERP.
- Document intake
- Human approval steps
Hosting and operations
Docker-based Odoo on AWS or Google Cloud, with backups, monitoring and safe deploys.
- Managed databases
- Staging and prod
Ways to work with us
Most clients start with one of these. All of them end with code and documentation you own.
System review
We read your modules, Studio changes, access rules and hosting, then give you a plain-language report: what is solid, what is risky, and what to fix first.
Project build
A defined piece of work, from new modules to a full implementation or a version upgrade, delivered through the six-step process with milestone reviews.
Ongoing development
A standing arrangement for change requests, fixes and improvements, with a change log and release notes your team can actually read.
How we keep your ERP safe
An ERP holds the business. These habits are why changes land quietly.
Rehearse on a clone
Every upgrade and data change runs first on a copy of your production database.
Rollback written first
We write the way back before the way forward, so no deploy is a one-way door.
Everything in git
Modules are versioned and reviewed, never edited live on the server.
Access reviewed
Groups, record rules and portal access are checked so people see only what they should.
Documented changes
Each change has a request, a log entry and notes for the people who use it.
Watched after launch
Logs and behavior are checked after release, not just on the day.
Common questions
If yours is not here, ask. You will get a straight answer.
Community or Enterprise?
Both. We will tell you honestly whether Enterprise features are worth the license for your business, or whether Community plus a few custom modules covers it.
Can you work on a system someone else built?
Yes, and it is a common starting point. A system review comes first, so we both know what we are dealing with before any change is made.
Do we own the code?
Always. Modules live in your repository, with documentation, and you are free to take them to anyone.
How do you use AI with our data?
Only where it earns its place, with your data kept in your systems and a person approving anything that matters.
Let's look at your system