Skip to main content

Contact

Talk to an Odoo Engineer, Not a Sales Queue

Tell us what you're trying to build, improve, migrate or integrate. A couple of sentences is enough: we'll come back with questions, not a brochure.

What happens next

  1. An engineer reads it

    Your message goes to the people who scope and build the work: an Odoo engineer, not a sales desk.

  2. We reply with questions

    Usually: what runs today, which edition, what must connect, what the first release should prove. If we aren't the right fit, we say so.

  3. A call, then a written scope

    A working session on your process, followed by a scoped proposal: architecture, phases, team and the project of ours that is closest to yours.

Direct channels

Enquiries reviewed by Atul Makwana, CEO & Co-Founder, Heliconia Solutions · Odoo 16 Functional Certification

Your enquiry

Fields marked are required.

We only use this to reply to you.

Optional, with country code if you'd like a call.

Optional. It helps us suggest the right scope, not the price.

Are you on Odoo today?

What the system must do, what it connects to, where it hurts today: a couple of sentences is plenty.

Optional. PDF, Word, Excel, PowerPoint, PNG or JPG, up to 5 MB. Existing process notes, a module list or a screenshot all help.

Your enquiry becomes a lead in our CRM and is read by an engineer. See the privacy policy for how we handle it.

Where we are

Vadodara and Rajkot, Gujarat, India

Visits welcome by appointment. Both offices are on the map links below.

Heliconia Office @ Vadodara

Vadodara · Head office

SWC HUB, 541-543, opposite Rajpath Complex, Bhayli
Vadodara, Gujarat, India

IST (UTC+5:30)

Open in Maps
Heliconia Office @ Rajkot

Rajkot · Branch office

1001, RK Prime, Near Nana Mauva Circle, 150 Feet Ring Road
Rajkot, Gujarat, India

IST (UTC+5:30)

Open in Maps

Prefer to talk?

Email, Call or WhatsApp

Our offices run on India Standard Time (UTC+5:30). WhatsApp and email reach us regardless of the hour.

Before you write

Questions People Ask Before Contacting Us

Bhavesh Selarka

COO & Co-Founder, Heliconia Solutions

Not answered here? Ask Bhavesh directly, the person who reviewed this page, not a sales queue. Odoo 16 Functional Certification.

Ask a question

Do you work with clients outside India?

Yes: most of our documented projects are outside India: Germany (Freiburger Bund), Sweden (Opsio), the USA (Spicy Organic), the UAE (Zealous), Sierra Leone (SLANGO, iDT Labs) and four Caribbean territories (Jo Ann’s). We work remotely across time zones from offices on India Standard Time.

We already run Odoo. Can you take over support or a stuck project?

Yes, and most of our work starts that way. Opsio came to us with legacy custom modules to migrate, ERP Happy uses our developers to extend its own team, and Zealous needed a heavily customised Odoo 16 system moved to 18 without losing what made it theirs. Tell us the version, the edition and what isn't working.

Odoo support

Community or Enterprise: do we need to decide before contacting you?

No. We implement both and recommend per workflow. If you're unsure, choose “Not sure” in the form and describe the process. The edition question is usually answered in the first call.

Community vs Enterprise

Do you take small projects?

Yes. Flintu’s self-hosted Odoo Enterprise deployment was two weeks of infrastructure work followed by hourly support. MEP Emart’s subscription automation was three to four months. Scope decides the model: project, dedicated team, or retained support.

Can we hire your developers to work inside our team?

Yes: dedicated Odoo, Next.js, React Native and Flutter developers embedded in your sprints, code review and repositories, as at PayRemit, Tubo Ventaja, iDT Labs and ERP Happy.

Staff augmentation

What should I include in the message?

What your business does, what runs today (Odoo version and edition if any), what must connect, and what the first release should achieve. Screenshots, process notes and a rough timeline help. A formal RFP isn't required.

Not ready to write yet?

Read First, Talk Later