The technical side of your Odoo project, built by an Odoo Learning Partner with 117 published modules and invoiced to your consultancy.
You bring the client, the analysis and the relationship; we deliver the implementation, the modules and the connectors, invoiced to your consultancy and co-branded with you. A public demo so your client sees it working before signing.
You have sold the project. The client is waiting. And you have no Odoo team.
It is the usual situation for a technology or business consultancy that has closed an Odoo project without developers on staff. The options that show up first do not fit:
A platform freelancer
One person with no company behind them: if they vanish mid-project, the problem is yours and your client's.
Another partner who wants your client
An integrator with its own sales team that, once done, sells directly to the client you brought.
Hiring a team for one project
Building a technical department for a single project does not pay off, and your client cannot wait for you to train it.
The whole technical side, invoiced to your consultancy
Everything from the analysis you have already done to the working system. You remain your client's point of contact; we work co-branded with you.
Implementation
Configuration of Odoo 17, 18 or 19 according to the analysis you sold: sales, purchasing, stock, accounting, projects. Odoo Studio when configuring is enough.
Modules
The 117 we already have published, or the one your project needs built to order, tested on the three live Odoo versions.
See the catalogueConnectors
Marketplaces and carriers with our own connector: Amazon, Mirakl, Shopify, Temu, AliExpress, Correos Express and MRW. And whatever is missing, built on your client's system API.
Migration
Version upgrade to Odoo 19 and data transfer from the previous system, with tests before cut-over.
Support
After go-live, second-level support for your consultancy: you attend your client, we solve the technical side.
Invoiced and co-branded
We invoice your consultancy, never your client. Your brand in front as implementer; ours as author of the modules, which is what the partner agreement requires.
You, in front. Us, on the technical side.
Your consultancy
- The client relationship and the sale
- Process analysis and requirements
- Project management towards your client
- The invoice to your client, with your margin
FlexigoTech
- Implementation, modules, connectors and migration
- Environments, tests and a demo so your client sees it working
- Technical documentation and handover
- Second-level support after go-live
Your brand in front; our authorship where the partner agreement requires it
We work co-branded with you: your consultancy appears as the implementer towards your client and FlexigoTech as the author of the modules. It is not a hidden brand: the Odoo partner agreement (clause 8.1) does not allow creating confusion between companies, and module authorship is recorded on apps.odoo.com.
Your client is yours: we do not contact them, we do not sell to them directly and we do not appear before them except as module authors on apps.odoo.com. If they write to us directly, we refer them to you.
And to be clear: FlexigoTech implements directly when the client comes on their own. When they come with you, they are yours.
What you can check before writing to us
Only facts you can verify on apps.odoo.com or in the demo. No figures you cannot check.
Odoo Learning Partner
Part of Odoo's partner programme, Learning level.
Modules on the App Store
Published under our name on apps.odoo.com. The full catalogue, with price and demo, is on this website.
See the catalogueInstalled on Odoo 17, 18 and 19
Every module is tested with real Odoo.sh builds on the three live versions before publishing.
Public demo
Your client can see it working before signing, without installing anything.
Open the demoBy the hour or at a fixed scope. Always in writing.
We do not publish rates: every sold project is different. Tell us about yours and we tell you how we would do it and under which model.
You tell us about the project
Client sector, what has been sold and when it has to be ready.
Scope in writing
By the hour or at a fixed scope, in phases, with what is in and what is out. Invoiced to your consultancy.
Build with a demo
Your client sees the system progress in a test environment, not in a slideshow.
Go-live and support
Launch, documentation and second-level support for your consultancy afterwards.
Senior external Odoo developer, with a company behind
Many consultancies land here searching for «freelance Odoo developer», «senior Odoo developer Spain» or «Odoo outsourcing Spain». What you find is different: a limited company with a tax ID, an Odoo Learning Partner, with 117 published modules you can verify on apps.odoo.com and a public demo. We are not a profile on a freelance platform.
Platform freelancer profile
- One person
- Portfolio described on a profile
- Tested when the project starts
- If they vanish, the project stops
FlexigoTech
- A company with a tax ID, a contract and a written scope
- 117 modules verifiable on apps.odoo.com
- Real Odoo.sh builds on 17, 18 and 19 and a public demo
- Odoo Learning Partner, with company liability
What consultancies ask us before starting
In writing and by habit. We do not contact them, we do not sell to them directly and we do not appear before them except as module authors on apps.odoo.com, which is what the Odoo partner agreement requires. If they write to us directly, we refer them to you.
You. You are their point of contact and the one who invoices them. We answer to you, in writing, for the agreed technical scope and for the deadlines we have signed with you.
Second-level support for your consultancy: you collect the incident from your client, we solve it. It is agreed before starting, under the same model as the project: by the hour or at a fixed scope.
We invoice your consultancy; you invoice your client with your margin. There is no FlexigoTech invoice to your client. Licences for the published modules are purchased in the name we agree in writing.
Yes. First the public demo, with the already published modules installed and working; then a test environment of the project itself where they see their system progress before cut-over.
Then the partner programme is for you: use our modules in your projects with NFR keys for your demo, or commission only the module or connector you are missing.
Do you have a technical team and only need one module?
Then the partner programme is for you: NFR keys, modules on 17/18/19 and the connector you are missing, built to order.
Tell us about the project you have closed
Client sector, what has been sold and when it has to be ready. We tell you how we would do it, by the hour or at a fixed scope, in writing.