Between Odoo partners: you bring the client, we bring the module you're missing.
Odoo Learning Partner with 99 modules published on 17, 18 and 19. Written partner terms, 25% off the subscription of single modules and one invoice a month with one line per database.
FlexigoTech is an Odoo Learning Partner
99 modules published on the Odoo App Store. Each one is really installed on a real Odoo.sh build of 17, 18 and 19. If it doesn't install, it doesn't ship.
You have the technical team and the client. You're missing a module, a connector or the time to build it.
We are another Odoo partner, so we work as equals, with three formulas, all of them in writing.
1 · Use our modules in your projects
Written partner terms, 25% off the subscription of single modules and the support of each database, with its response time. You implement and invoice your customer; we maintain the module on 17, 18 and 19.
2 · Commission the connector or module your project needs
Fixed scope in writing, delivered on the three versions, published on the App Store or kept private for your project. We work by the hour or at a fixed scope; tell us the case and we'll tell you how.
3 · Co-build industry modules with those who know the industry
You know the industry and its processes; we bring the Odoo engineering and the publishing. The module is born from a real client of yours and stays maintained for every following one.
What you get as a partner
Clear terms so that using our catalog in your projects pays off from the very first one, and in writing before starting.
Your demo databases
Your demo databases get the service with the 14-day trial. If we give you a free copy of a module in writing, it only works for those databases, never for a customer's.
25% partner discount
A 25% partner discount on FlexigoTech Cloud subscriptions of single modules, monthly and annual, for the databases you manage from your account. It does not apply to packs, to All included or to the module price.
Support for each database, with its response time
The support that comes with each database's subscription, with its response time, goes to your team or to your customer's, as you ask. You answer to your customer for your implementation.
Odoo 17, 18 and 19 in parallel
Every module is maintained on the three live Odoo versions and installed on a real Odoo.sh build of each. Whether your client is still on 17 or already on 19, the same module follows them.
All 99 modules behind you
The whole catalog is behind you: marketplaces, carriers, e-invoicing, ESG, HR, e-signature and operations, so you can cover more of the same client's needs with a single supplier.
See the full catalogWritten terms
A clear EULA, written collaboration terms and delivered code. You know exactly what you can use, on which versions and with what support, before signing anything.
No white label. The owner of each database is your customer.
Two rules we keep, written down here.
No white label
Your brand goes up front as the implementer. Authorship and maintenance of the module stay in our name, on apps.odoo.com and in the code's copyright notices.
- You present, implement and invoice your client.
- We sign the code, publish it and maintain it on 17, 18 and 19.
- No delivery that passes one company off as the other.
You implement and invoice your customer under your own brand. FlexigoTech is the author of the module and the service: it is not presented as yours, and the FlexigoTech brand is only used to say that you implement its modules.
The owner is your customer
We don't contact them, we don't sell to them directly and we don't appear before them except as the module's authors on apps.odoo.com, which is what the partner agreement requires.
- If your client writes to us, they are referred back to you.
- The support for each database goes to your team or to your customer's, as you ask.
It is a relationship between two independent companies, with no exclusivity and no exclusive distribution.
We co-build industry modules with those who know the industry
Some of our modules come from working with people who live the problem every day, so they are tested on real cases. If your team knows an industry and has a client who needs it, the module is built with you.
You bring the real case
A client in the industry, their processes and their exceptions. We build nothing without a real case, so no one ends up with modules nobody needs.
We bring the Odoo engineering
Models, views, tests and publishing on 17, 18 and 19. The module installs on a real Odoo.sh build before shipping, like the rest of the catalog.
Terms in writing before starting
Who the author is, who maintains it, how revenue from following clients is shared and whether it's published or kept private. All agreed before the first line of code.
From demo to first project in three steps
You test it first, then we agree the terms, and then you deploy, with direct support.
You test the module
Open the public demo and click each module you care about. Install it on your instance and try it with the 14-day trial, no card, using your project data.
We agree terms in writing
We sign the partner terms before your first customer. Each customer accepts the data transfer and the subscription terms from their own Odoo, and you pay the subscriptions with one invoice a month.
You implement and invoice your customer
You bring the client relationship and the deployment; we keep the module maintained across the three versions and fix the bugs. If something breaks, your team talks to whoever wrote the code.
Sign up as a partner and request the terms
Seven fields. An engineer answers you, not a salesperson, within 24 working hours. You are a partner when you manage Odoo databases for at least 3 different customers and sign the terms.
- Partner terms Install the modules on your own instance and your demo, with your project's data, before selling anything.
- Terms in writing The partner terms, in writing and signed before your first customer.
- Access to the full catalogue All 99 published modules, each with its page and its code, really installed on Odoo 17, 18 and 19.
- The owner is your customer You run the implementation and the invoice. We only write to them what the service requires: the confirmation that they are the owner, the emails of their subscription, the day 3 notice if you stop paying and security notices.
What a partner asks us before writing
Request the partner terms
Open the public demo, test the modules you care about and, once you're clear, we'll talk terms between partners, in writing and with no commitment.
