OdooBots
Loading
About

About OdooBots

OdooBots was founded in Chennai in 2021 by M. A. Leelairajan, who brings over nineteen years of building practical software for businesses — more than fifteen of them in CRM. The motto he started with — maximum quality in minimum timeframe — is still the one the delivery team is measured against.

We implement, customise, integrate, migrate, host and support Odoo for businesses across India and the Gulf. That is all we do, and this page is about how we do it.

Karthik RajOdoo Technical Consultant, 10+ years| Reviewed by Arun Kumar| Updated 21 October 2026| Odoo 16–19, Community & Enterprise
0Odoo projects delivered
0Consultants & developers
2021Founded in Chennai
ChennaiAmbattur, Tamil Nadu

Businesses running Odoo with OdooBots

Dhanalakshmi Industries logo Sanjeev Autoparts logo Electro Flux Equipments logo Anchor Marine Equipment Company logo NEXG logo PV Constructions logo SESS logo
Definition

Who OdooBots is

An Odoo implementation company in Ambattur, Chennai, founded in 2021 and working with businesses across India and the Gulf. We cover the whole life of an Odoo system: implementation, customisation, integration with the tools you keep, migration from what you run now, hosting, training and support. We do not implement other ERP products, which is why our comparison pages name the cases where another one fits better.

The thing we would most like you to take from this page: we turn down work. If your problem is bookkeeping, if nobody internal can own the project, or if another product suits you better, we would rather say so on the first call than three months in.

Founded
2021, in Chennai, by M. A. Leelairajan.
The experience
His, not the company’s — 19+ years in business software, 15+ in CRM.
What we do
Odoo only — implementation, customisation, integration, migration, hosting, training, support.
Where
Ambattur, Chennai. Clients across India and the Gulf.
How we work

Five things we do differently, and why

These are not values on a wall. Each one came from a project that went badly before we changed how we worked.

  1. A diagnosis, not a demonstration

    The first call is us asking what breaks today, not us showing features. A demonstration tells you what the software can do; it tells you nothing about whether your project will work.

  2. The price is fixed before we invoice

    Implementation is quoted in writing after the diagnosis, and hosting is published on the site. If scope changes, the change is quoted before it is built rather than after.

  3. Configuration before code

    Everything configurable is cheap and survives upgrades. Custom modules are named separately in the quote so you can see exactly what you are paying developer rates for, and why.

  4. We name the limits

    Every page on this site has a section saying where Odoo needs development or where another tool is better. That section exists because the alternative is discovering it during user acceptance testing.

  5. One named internal owner

    We ask who inside your business can decide that a process changes. Projects with that person succeed and projects without them do not, on any ERP, and we would rather raise it before the quotation.

Services

What we do

Seven services, each written up properly on its own page rather than summarised here.

Odoo implementation

A new Odoo system end to end — scoping, configuration, data migration, training and go-live. See Odoo ERP implementation.

ScopingConfigGo-live

Odoo customization

Custom modules built to survive version upgrades, quoted separately so the cost of code is visible. See Odoo customization.

ModulesUpgradeableQuoted

Odoo integration

Connecting the systems you are keeping — stores, gateways, Google, Microsoft, custom APIs. See integrations.

StoresPaymentsAPIs

Odoo migration

Version upgrades and moves to Odoo from Tally and other systems, with cut-off and opening balances handled properly. See Odoo migration.

UpgradesTallyBalances

Training and consultancy

Role-based training on your own database, and consultancy for the decisions that come before a project. See Odoo training.

Role-basedYour dataAdvice
Trust · honest advice

When we will tell you not to buy from us

Six situations where we would rather lose the enquiry. Each of these has happened, and each of them appears somewhere on this site in more detail.

Your problem is bookkeeping

If what hurts is entering vouchers and filing GST, Tally does that better and cheaper. Moving to Odoo for accounting reasons disappoints people.

Nobody internal can own it

An ERP needs one person who can decide a process changes. Without them the project fails regardless of budget or product.

You need hotel rooms managed

Odoo has no reservation engine or night audit. Keep a property management system and let Odoo run food, stores and accounts behind it.

You consolidate many subsidiaries

Multi-entity consolidation across currencies with eliminations is where NetSuite and SAP are genuinely ahead.

You run on Microsoft 365 entirely

If identity, documents and reporting are all Microsoft, Dynamics removes friction that an integration only reduces.

The project cannot be funded properly

A half-finished implementation is worse than the system you have now. Better to wait a quarter than to stop halfway.

Where to find us

OdooBots, Ambattur, Chennai

We work on site across Chennai and remotely across India and the Gulf. The office is real and you are welcome in it.

Address33/359, 1st Floor, Nethaji StreetGnanamoorthy Nagar, Ambattur, Chennai 600053
Phone+91 98414 81435Mon–Sat, business hours IST
Founded2021, by M. A. Leelairajan19+ years in software, 15+ in CRM
Delivered630+ Odoo projects30+ consultants and developers
FAQ

About OdooBots: frequently asked questions

When was OdooBots founded?
In 2021, in Chennai, by M. A. Leelairajan. The company works from Ambattur and serves clients across India and the Gulf.
How much experience is behind the company?
The founder, M. A. Leelairajan, has over nineteen years building business software, more than fifteen of them in CRM. The company itself was founded in 2021 and has since delivered 630+ Odoo projects with a team of 30+ consultants and developers. We keep those two separate because they are two different things, and conflating them is how an about page stops being believable.
Do you work only with Odoo?
Yes. We implement, customise, integrate, migrate, host and support Odoo and nothing else. That is also why our comparison pages name the cases where SAP, NetSuite, Dynamics, Zoho or Tally suits a business better — we are not competing for that work.
Do you work outside Chennai?
Yes, across India and the Gulf. Requirement workshops run on site or remotely depending on the project, and our implementations include clients in the United Arab Emirates. See our case studies.
What does an engagement start with?
A free diagnosis call. It is a scoping conversation rather than a demonstration: we ask what breaks today, who owns the project internally, and what your data looks like. The written quotation follows that, and the price is fixed before any invoice.
Do you turn work down?
Regularly. If the problem is bookkeeping, if nobody internal can own the project, if you need hotel room management, or if another product genuinely fits better, we say so. Those situations are listed on this page and explained across the site.
Who will actually work on our project?
Named consultants and developers from our own team rather than a rotating pool. The people who appear on our pages as authors and reviewers are the people who do the work. See Odoo experts.

Start with a diagnosis, not a demonstration

Tell us what breaks today and who inside your business would own the project. Those two answers tell us more than any requirements document, and the call is free.