A five-year-old company with fourteen years of founder time on Odoo.
Entrivis was founded in 2020. Its founders have been working on Odoo since v6 (fourteen years of continuous platform experience that predates the company itself) alongside ERPNext and the modern stack built around them.
About a third of the clients we work with came to us second. The first partner went live and then drifted. Timelines slipped, customizations became unmaintainable, support quality fell, and at some point the client realized the system was costing them more than it was saving. That’s the work we are best known for: diagnosing what broke, fixing what’s salvageable, rebuilding what isn’t, and staying long enough that it doesn’t happen again.
We’re headquartered in Vadodara, India, with offices in Mehsana and Gandhinagar. We serve direct clients across India, the Gulf, the US, Canada, the UK, and the EU. And we work alongside long-standing partners in Norway, Oman, Sudan, the Philippines, and Canada: relationships that, in several cases, are as old as the company itself.
We started on Odoo when it was still called OpenERP, on version 6. Back then you fixed things by reading the source, because there wasn’t much else to read. That habit didn’t leave us.
When we founded Entrivis in 2020, we’d each spent years watching solid implementations go quiet a few months after launch: the consultant gone, the system frozen on the version it shipped with, the client quietly back on spreadsheets for everything it didn’t quite do.
We built Entrivis to be the firm that’s still there in year three.
We stay past go-live.
Thirty-five percent of our effort is stabilization, QA, and ongoing improvement work. Forty percent of revenue comes from clients more than a year old. Our longest active engagement is five years. If we ship something we can’t sustain, we have a problem with what we shipped.
We’re the partner after the partner.
About a third of our clients came to us second. The first partner went live and then drifted. We won’t name them. We will diagnose what broke, fix what’s salvageable, rebuild what isn’t, and stay long enough that it doesn’t happen again.
Founders on Odoo since v6, and we’ve stayed.
Every Odoo version from 6 to 19. Fifteen-plus migrations, including the unusual ones: v6 to v9, v10 to v18, Enterprise back to Community. We delivered a v7 to v18 Enterprise migration for an East African public sector body. The version history isn’t trivia. It’s how we keep options open for clients.
What kind of firm is this?
Thirty people, across three offices in Gujarat: Vadodara, Mehsana, and Gandhinagar. Average tenure is around three years, which in this industry is long: the people who built a client’s system are usually the people still maintaining it. From there we work across twelve-plus active geographies, mostly through long-running relationships rather than one-off projects.
We’re an Odoo Ready Partner. ERPNext is an in-house capability too: when it’s the better fit, we build it ourselves, with the same architecture, integration, and post-go-live ownership we bring to Odoo.
How we structure and price that work is set out in engagement models, and how we run it is on how we work.
Since 2020 we’ve delivered more than seventy projects for over twenty active clients. That includes fifteen-plus Odoo migrations and twenty-plus production integrations: to banks, payment gateways, logistics platforms, energy meters, and POS systems. We’ve worked on every version of Odoo from v6 to v19, which matters most on the day something breaks on a version everyone else has forgotten.
Twenty-four of those integrations are published as installable apps on the Odoo Apps Store (ten of them payment and shipping connectors) listed publicly under our name. That’s a harder thing to fake than a logo wall.
We work with three kinds of clients, and we treat all three as core.
Mid-market companies who run their operations on Odoo and need it built, migrated, or kept alive. Enterprise IT teams who need a delivery partner their security and procurement people can actually evaluate, which is why we keep a trust page most firms our size don’t bother with. And other consultancies and agencies, who bring us in as engineering capacity behind their own brand.
That last group is about forty percent of what we do. We treat white-label and capacity work as a first-class practice, not an overflow valve.
By sector, the mix runs roughly: manufacturing thirty percent, partner and white-label engagements forty percent, trading twenty percent, web and ecommerce ten percent, financial services five percent, approximate and overlapping, since a partner engagement has an industry behind it too.
We also maintain one pro bono engagement, with RRSA India, an NGO.
Every number on this site is in this table. If it isn’t here, we don’t say it.
- Founded
- 2020
- Headquarters
- Vadodara, Gujarat, India
- Offices
- Vadodara · Mehsana · Gandhinagar
- Team
- 30 people · ~3-year average tenure
- Founders
- Three co-founders, all in delivery
- Founder Odoo experience
- 14 years (since v6)
- Projects delivered
- 70+
- Active clients
- 20+
- Odoo migrations
- 15+ (v6 → v19)
- Integrations in production
- 20+
- Published Odoo apps
- 24 (10 payment & shipping connectors)
- Active geographies
- 12+
- Longest active engagement
- 5 years
- Typical engagement length
- 6 months – 1 year
- Revenue from clients 1+ year old
- 40%
- Repeat engagements
- 20%
- Effort on stabilization
- 35%
- Clients who came to us second
- ~1 in 3
- Industry mix
- Manufacturing 30% · Partner engagements 40% · Trading 20% · Web & ecommerce 10% · Financial 5%
Industry mix is approximate and overlapping: a partner engagement has an industry behind it too. Last reviewed July 2026.
See how we work before you hire us.
Start with a paid discovery, or read the case studies that show the pattern.