EspañolBetween Odoo partners: you bring the client, we bring the module you're missing.
Odoo Learning Partner with 105 modules published on 17, 18 and 19. Free NFR keys for your demo, terms in writing and a direct line to whoever writes the code.
FlexigoTech is an Odoo Learning Partner
105 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, not a generic software supplier. That's why the collaboration is set up between equals, with three formulas and all of them in writing.
1 · Use our modules in your projects
Free NFR keys for your demo, referral and volume terms in writing and second-level support to your team. You implement and own the relationship; 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.
Free NFR keys to test
Free Not-For-Resale licenses for your test and demo environments. Install the modules on your own instance, play with them and show your client before paying anything.
Referral and volume terms in writing
Margin for you whether you bring us the client (referral) or buy for several projects (volume). We agree the percentage per case and it goes in writing; no fine print.
Second-level support to your team
You give first-level support to your client; we give second-level support to your technical team. A direct channel to whoever wrote the module: a real bug gets reproduced, fixed and shipped, with no ticket queue.
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 105 modules behind you
You don't get a single product: the whole catalog is behind you. Marketplaces, carriers, e-invoicing, ESG, HR, e-signature and operations, so you cover more of the same client's needs with a single supplier.
See the full catalogLicense and support in writing
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.
Co-branded, not private-label. And your client stays yours.
Two rules we actually keep, written here so they don't have to be negotiated later.
Co-branded, not private-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.
Why not private-label: the Odoo partner agreement (clause 8.1) does not allow creating confusion between companies. We comply with it and it helps you comply too.
Your client stays yours
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.
- First-level support is yours; second-level, ours to your team.
Said plainly: FlexigoTech implements directly when the client comes on their own. If they come through you, they're yours.
We co-build industry modules with those who know the industry
Some of our modules are born from a direct collaboration with those who live the problem every day: more real-world testing, better support and zero compatibility surprises. 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. Nothing gets built without a real case: it's the rule that avoids 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 other 117.
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
No endless forms or long sales cycles. Test first, agree next, deploy with direct support.
You request NFR keys and test
Open the public demo and click through any module you care about. Request NFR keys and install it on your own instance to validate it with your project's data.
We agree terms in writing
We decide the formula together: referral, volume or commissioning a new module (by the hour or at a fixed scope), and the Odoo versions you need. All in writing, with a clear EULA and terms.
You deploy with second-level support
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 your NFR keys
Seven fields. An engineer answers you, not a salesperson, in under 24 working hours. There is no entry fee and no volume commitment.
- NFR keys to test Install the modules on your own instance and your demo, with your project's data, before selling anything.
- Terms in writing Referral, volume or commissioning a new module: the formula, the licence and the support, all in writing before we start.
- Access to the full catalogue All 105 published modules, each with its page and its code, really installed on Odoo 17, 18 and 19.
- Your client stays yours We never sell to them on our own account and we never write to them. The relationship, the invoice and the deployment are yours.
What a partner asks us before writing
Request your NFR keys or tell us the module you're missing
Open the public demo, test the modules you care about and, once you're clear, let's talk terms between partners. In writing and with no commitment.