Short answer
With AI, almost anyone can build something in Odoo. What matters is when it makes sense for you, and that doesn't depend on how hard it looks, but on five questions: do you have time to test and fix it, what happens if it fails, how many parts of Odoo does it touch, who maintains it, and is it what your company does best.
Count how many times you land on “hire”: with 0 or 1, do it yourself with AI's help; with 2 or 3, do it yourself with support; with 4 or 5, hire someone.
The video is in Spanish and lasts 11 minutes. To follow the test, keep a sheet of paper at hand and think of something concrete you want to change in your Odoo.
What you will see in the video
The 5 questions of the test
Think of something concrete you want to change in your Odoo and, for each question, note whether it falls in the “do it yourself” column or the “hire” column.
| Question | Do it yourself if… | Hire someone if… |
|---|---|---|
| 1. Do you have time to test and fix it? | You can spend a few hours on it and test it again whenever something changes. | You would do it in the gaps your job leaves you. |
| 2. What happens if it fails? | The worst case is that a screen or a report looks odd. | It touches money, taxes or stock: a wrongly issued invoice, wrongly valued stock, a fine, an inventory that doesn't match. |
| 3. How many parts of Odoo does it touch? | It only adds a field, a filter, a view or a report. | It changes flows that cross several modules. |
| 4. Who maintains it? | It is configuration, or you can review it with every update. | It is custom code and a new Odoo version can break it. |
| 5. Is it what your company does best? | Learning to build gives you an edge or is part of your business. | Every hour you spend on it is an hour taken from selling or serving your customers. |
Question 1: do you have time to test and fix it?
AI gives you the solution in minutes. What takes time is testing that it works in every case and fixing what doesn't. If you don't have that time, you don't have it: if you would do it in the gaps your job leaves you, it goes in the “hire” column.
Question 2: what happens if it fails?
What matters is not the difficulty, it is the cost of the error. A report that looks ugly is something you fix with no consequences; something that touches money, taxes or stock is different: a wrongly issued invoice, wrongly valued stock, a fine, an inventory that doesn't match.
Question 3: how many parts of Odoo does it touch?
Adding a field, a filter, a view or a report is something you can do yourself. Changing a flow that crosses several modules is another matter: a sale that moves inventory, values it and must also be reflected in the report and in the accounting entry.
In Odoo everything is connected. A change in sales can throw accounting off and you don't see it until month-end close. That is why, when Ganemo builds, it doesn't test isolated cases: it tests combinations.
Question 4: who maintains it?
Your company's processes change, Odoo changes version and sometimes the person who runs or manages the system changes and wants to manage it differently. If yours is configuration, or you can review it with every update, do it yourself. If it is custom code, a new Odoo version can break it.
- You depend on the changes Odoo makes, and also on those of the third-party modules and integrations you buy. If your module touches any of them, it has to be maintained with every update.
- We are not talking only about major version jumps such as 19 to 20 or 20 to 21: between versions there are also revisions that can affect your module.
- Updating is not copy and paste. The author says they recently moved one of their own modules from version 19 to 20 and parts had to be redone.
Something cheap to build can be expensive to maintain.
Question 5: is this what your company does best?
This is the most honest question. Even if you can do it yourself, every hour you spend on it is taken from selling or serving your customers. If learning to build gives you an edge, or it is part of your business, do it yourself.
A technical person will think “I do it myself”, but they work on this for a living and may want to sell that service. If you are an entrepreneur, business owner, manager or company director, you probably don't want to be maintaining or developing this on your own: getting confidently through all that work costs more if you handle it in-house.
How to read your result
No single question is decisive on its own. Count how many times you landed in the “hire” column:
| Times in “hire” | What to do |
|---|---|
| 0 or 1 | Do it yourself, with AI's help. |
| 2 or 3 | Do it yourself, but with support: someone to speed you up, plus tools and a working harness that make the process easier. |
| 4 or 5 | Hire someone. Going cheap will end up costing you more. |
Case 1: a “Delivery zone” field — do it yourself
The goal is to identify each customer's delivery zone, be able to filter sales by it and have it show up in reports.
- Time: a short while. It will take about 20 minutes.
- If it fails: nothing serious, you fix it yourself.
- Parts it touches: it adds a field and works with one model, plus a few reports.
- Maintenance: it is configuration.
- Focus: just a few minutes.
Result: no question lands on the right, so do it yourself, with AI or even without it. You can also ask us. And for this particular case you may not even have to do it: specialized delivery and route-management apps already exist, and installing a module may be enough.
Case 2: a quotation layout with your logo and your style — do it yourself, with support
It is a quotation with your logo, your terms and your own design for layout, spacing and line height.
- Time: several hours; at best a couple, if not more, while you fine-tune every detail. You can do it yourself.
- If it fails: it looks bad and you fix it.
- Parts it touches: only the document.
- Maintenance: the templates must be reviewed with every version. This is where it starts to weigh.
- Focus: hours of back and forth over the design; in the author's opinion, this one is worth delegating.
Result: only the last two questions land on the right, right at the limit. You can do it yourself if someone supports you so you move faster. Design involves your own judgment and taste, so it helps to have direct contact with the deliverable. AI makes it easy, but if you have never done it you need initial guidance to get up to speed. With a support pack you can ask for guidance while you develop on Odoo yourself.
Case 3: calculating the detraction automatically on service invoices — hire
The goal is for the detraction (a Peruvian tax withholding mechanism) to be calculated automatically on service invoices and linked to its deposit.
- Time: it could be several days, including tests of different scenarios and real cases.
- If it fails: SUNAT (the Peruvian tax authority) and fines.
- Parts it touches: sales, accounting, payments and reconciliations.
- Maintenance: code, regulations and constant changes, not only from one version to the next.
- Focus: it is not your business.
Result: five out of five on the right, no doubt. An error reaches you as a fine, it touches three areas at once and it changes with the regulations. Even so, the detraction is part of the standard Peruvian accounting localization and Odoo already includes its features with electronic invoicing, so the sensible route is to implement it together with your electronic invoice. The case is only an example for the test.
Decide with the questions, not with fear
Decide with these five questions, not out of fear that it will go wrong or out of enthusiasm that AI does everything. There are things you have to do yourself and things you don't.
If your requirement came out as “do it yourself”, the Ganemo YouTube channel has videos that teach you how. If you prefer an implementation pack, you can ask that, during the process, we teach you how to use AI tools so you can implement your own developments with autonomy and take them to production.
Frequently asked questions
According to the video, with AI almost anyone can build something in Odoo. The question that matters is when it makes sense for you, and you decide that with five questions: time, cost of error, parts of Odoo touched, maintenance and focus.
Those that only add a field, a filter, a view or a report, and where the worst that can happen is that a screen looks odd. They are fixed with no consequences.
Because Odoo changes versions and revisions, and third-party modules and integrations change too. Custom code has to be maintained with every update, and moving it from one version to another is not copy and paste: parts have to be redone.
Do it yourself, but with support: someone to help you go faster and tools that make the work easier. With a support pack you can ask us to guide you while you develop.
Want to change something in your Odoo and not sure whether to do it yourself or hire?
Tell us what you want to change and we will go through it with you using these same questions.
00:00 I sell development on the Odoo ERP, and in this video I'm going to tell you when you don't need to hire me. With AI there are many things you can do yourself today, and there are others that, if you do them alone, will cost you more. At the end you will have a 5-question test to tell which is which, and we will try it on 3 typical Odoo cases. The problem is no longer whether you can: with artificial intelligence almost anyone can. The problem is knowing when it makes sense for you. And the answer doesn't depend on how hard it looks, but on five things.
00:38 Keep a sheet of paper at hand and think of something concrete you want to change in your Odoo. For each question, note whether it lands in the left column or the right column.
00:48 Question 1: do you have time to test and fix it? Do it yourself if you can spend a few hours on it and test it again whenever something changes. Hire if you would do it in the gaps your job leaves you. Watch out with this one: AI gives you the solution in minutes; what takes the time is testing that it works in every case and fixing what doesn't. If you don't have that time, you don't have it.
01:15 Question 2: what happens if it fails? Do it yourself if the worst case is that a screen or a report looks odd: you fix it with no consequences. Hire if it touches money, taxes or stock: a wrongly issued invoice, wrongly valued stock, a fine, an inventory that doesn't match. A report looking ugly is not the same thing. What matters is not the difficulty, it is the cost of the error.
01:44 Question 3: how many parts of Odoo does it touch? Do it yourself if it only adds a field, a filter, a view or a report. Hire if it changes flows that cross several modules: a sale that moves inventory, values it and must also be reflected in the report and in the accounting entry. In Odoo everything is connected. A change in sales can throw accounting off, and you don't see it until month-end close. That is why, when we build, we don't test isolated cases, we test combinations.
02:17 Question 4: who maintains it? When your processes change, when Odoo changes version, when you change director or manager and want to run it differently. Do it yourself if it is configuration or if you can review it with every update. Hire if it is custom code: a new Odoo version can break it. Let's generalize: when there is code that you don't depend on directly to fix. Odoo changes without depending on you, and you depend on the changes Odoo makes. And if you buy third-party modules or integrations, you also depend on their changes. If your module touches those integrations or those modules, it has to be maintained with every update.
03:07 And by version I don't only mean a jump from 19 to 20 or from 20 to 21. Between versions there are revisions that can also contain changes that affect your module, and it has to be maintained and updated. It is not copy and paste. We recently moved one of our own modules from version 19 to 20, and it wasn't copy and paste: parts had to be redone. Something cheap to build can be expensive to maintain.
03:35 Question 5: is this what your company does best? Do it yourself if learning to build gives you an edge, or it is directly part of your business. Hire if every hour you spend on it is taken from selling or serving your customers. This last one is the most honest. A technical person will think “I do it myself”, but of course, you are technical, you do this for a living, you provide support on this, you want to sell that service. As an entrepreneur, business owner, manager or company director, you don't want to be maintaining it or developing it on your own, because the cost of getting confidently through all that work is higher if you handle it in-house.
04:22 Now count how many times you landed on the right, because none of these questions is decisive on its own. If you landed once or never, do it yourself, with AI's help. If you landed two or three times, do it yourself, with support that speeds you up, with tools and a harness that make the work easier. And if you landed four or five times on the right, hire: going cheap will end up costing you more.
04:53 Let's try it on three typical cases. First case: a “Delivery zone” field, to identify each customer's zone, filter sales and have it show up even in my reports. Time: a short while, you do it yourself. If it fails, nothing serious, you fix it yourself. Parts it touches: it only adds a field and works with one model, and a few report models; not that critical. Maintenance: it is configuration, you maintain it yourself. Focus: it will take 20 minutes. Do it yourself. None land on the right, so, with AI's help or even without it, you can do it yourself. Or not: you can also ask us. I understand most people fall in that space where they value their time too much to spend it on these things. And for this particular case you wouldn't even have to: ask us and we already have specialized apps for delivery and route management, so it is a matter of installing a module.
06:04 Case B: a quotation layout with your logo, your terms, your style, your own layout design, spacing and line height, the way you want it. Time: several hours; at best a couple, if not more, while you fine-tune every little detail, but you can do it yourself. If it fails, it looks bad and you fix it: you can do it yourself. Parts it touches: only the document, so you can do it yourself too. Maintenance: the templates must be reviewed with every version. Here it starts to weigh, and here I would start considering whether to hire; sides will form. Some will say “better to hire” and others, “it is your own customized matter, do it yourself, you have more freedom and autonomy for whatever customizations you want”. And one point more important to me, the fifth question, your focus: hours of back and forth over the design. In my opinion, that is something you should hire.
06:48 But of the five questions only the last two went to the right column. We are at that limit where you can do it yourself if someone supports you so you move faster. If you had to learn a lot, with a long learning curve, no; but if it is enough to give people a couple of instructions, make sure with tests that it is going well and have a guide to start quickly, I would say keep it on your side. By the way, we don't like this kind of project, because in design a lot of personal judgment and taste comes in, and there is no accounting for taste. It is better that you have direct contact with your product, your design, the deliverable, and ask the AI for it directly. I prefer, and I hope you do too, to do it yourself.
07:56 Where is the problem? Sometimes doing it yourself requires an initial curve so you pick up speed. With AI tools it is easy, but, as with everything, if you have never done it you need initial guidance. Do it yourself with initial support and that way you become the owner of all your formats and reports. On this same channel you have several videos showing how to build your custom reports with AI. And if you want a support pack with us, we can guide and accompany you through the development process so you gain autonomy by developing on Odoo yourself, using the hours of your support pack.
08:46 Now, the last case: I want the detraction to be calculated automatically on service invoices and linked to its deposit. Time: it could be several days, including tests of different scenarios and real cases that happen. I would say: hire. If it fails, SUNAT and fines: hire, let them do it. Parts it touches: sales, accounting, payments, reconciliations; probably hire. Maintenance: code, regulations, constant changes, not only from one version to the next: hire. And your focus is not your business: hire. Of the five questions, all five say hire, so there is no doubt here. An error reaches you as a fine, it touches three areas at once and it changes with the regulations.
09:34 Of course, detraction matters are part of the standard Peruvian accounting localization and I'm only using it as an example; Odoo already includes all the detraction features with your electronic invoice. So implement it with your electronic invoice: our commercial contact details are there.
09:58 Whatever you decide, decide it with these questions, not out of fear that it will go wrong or out of enthusiasm that AI does everything. There are things you have to do yourself and things you don't. If, for the requirement you are looking at, you got “do it yourself”, on this same channel you have videos that teach you how. If you want an implementation pack with us, ask that during your implementation we teach you how to use AI tools, so you yourself, with autonomy, can implement your own developments and launch them to production. Write to us on the commercial WhatsApp or at our commercial email.
Edited transcript, translated from the Spanish original: filler words and repetitions were removed and speech-recognition errors were fixed. The ideas and figures are the author's.