Insights · 8 min read
SAP, Odoo, or a system built for you. The real decision is how much you are willing to bend your processes to fit a product, and it shows up in cost per user over time.
By GGP Editorial
When a company outgrows its spreadsheets, the ERP conversation starts, and it almost always lands on the same three doors: SAP, Odoo, or a system we build for you. People treat this as a software choice. It is really a choice about how much you are willing to change the way your business works to fit someone else's product.
I have sat on both sides of it. We build custom ERP and business systems, and we have also watched clients try SAP or Odoo first and come back with a bill and not much to show for it. This is the comparison I would give a client who asked, written for the person who signs the cheque rather than the IT manager who already has a favourite vendor.
SAP is the enterprise standard. S/4HANA for large companies, Business One for smaller ones. It is a packaged product with deep functionality and a large partner network, and its price is negotiated, not listed on a website.
Odoo is the modular alternative. An open-source core with a paid Enterprise edition sold per user per month, so you can start small and add apps as you go. It is the transparent one, which is why it anchors most comparisons.
A custom ERP is software written to your processes, your data model, and your reporting. You own it, you do not pay a per-user licence forever, and it does exactly what you asked for and nothing you did not.
Odoo is where the numbers are public, so it is worth spelling them out. There is a free tier that covers one app for a small team, and a free open-source Community edition. The paid Enterprise edition is per user per month.
At the time of writing, the Standard plan starts around US$17 per user per month on annual billing and the Custom plan around US$26, with monthly billing running higher. Extra apps and Odoo.sh hosting add to that, and so does the work of configuring the modules to match how your business runs.
| Item | Cost model |
|---|---|
| Odoo Enterprise licence | Roughly US$17 to 26 per user per month on annual billing |
| Extra apps and hosting | Additional, per app and per hosting tier |
| Implementation and setup | One-time, varies with scope |
| Ongoing | Recurring licence plus maintenance |
The licence number is only the start. The real Odoo budget is usually in the setup: mapping your processes onto its modules, migrating your data, and training people who have been running on spreadsheets for a decade.
SAP does not publish a price list the way Odoo does. A deal is negotiated, and the software licence is rarely the biggest line on the invoice. You pay for the licence or subscription per user, plus annual maintenance, plus the implementation, which a partner does and which often costs several times the licence itself.
Customising SAP to your processes, integrating it with your other systems, and training staff is where the budget goes. That is why SAP is rarely the cheap option for a mid-size company. It is chosen by firms that need its depth, that operate in heavily regulated industries, or that already run on it and have no appetite to move.
A custom ERP has no per-user licence. You pay to build it, then you pay to maintain and extend it. The build is driven by scope: how many modules, how many integrations, how much reporting, how tangled the data model.
A typical first build covers a few modules, sales, purchasing, inventory, and finance, plus the integrations to your existing tools and a reporting layer your finance team will actually want to read. The scope grows when the process is unusual, because unusual is exactly where packaged software stops helping.
The honest trade-off is that the first cheque is larger than Odoo's first invoice, but you are not paying a licence in perpetuity, and the system fits your processes instead of asking your processes to fit it. We have written about where that build budget goes in our custom software development cost breakdown.
Price per user is a seductive number because it is the only one every vendor will quote you. It hides the actual decision. SAP and Odoo are products, and using a product means accepting its way of modelling your business. If your business is standard, that is fine. If your margins live in how you quote, schedule, or bill, forcing those processes into a generic product is where the project stalls.
Count your users. A hundred users on Odoo or SAP add up quickly. A custom system costs roughly the same to build whether ten or a hundred people log in. That is the crossover people forget: packaged software gets more expensive as you grow, and custom software gets cheaper per user as you grow.
| Situation | What usually fits |
|---|---|
| Standard processes, need it live fast, budget matters | Odoo |
| Large enterprise, deep industry depth, already on SAP | SAP |
| Unusual or proprietary processes, many users, want ownership | Custom ERP |
| Heavy integrations with tools you already run | Custom, or custom built around Odoo modules |
None of these is a universal winner, and any vendor who tells you otherwise is selling. The question is which trade-off you can live with for the next five years.
Whichever route you take, three lines show up late and sting. Implementation is configuring the product to your reality, and it is where Odoo and SAP projects quietly double in size. Data migration means taking years of messy spreadsheets and getting them clean enough to live in a system that enforces structure. And no ERP survives contact with the business unchanged. You will want changes within a year, and each change on a packaged product is a customization, a consultant, or a wait on the vendor's roadmap.
Data migration deserves its own warning. A customer record that is three records in the old system has to become one in the new one, and someone has to decide which of the three is right. That kind of cleanup is not glamorous, and it is rarely in the first quote.
Budget for those three before you compare licence prices. They are the reason two companies can pay wildly different amounts for the same product.
GlobeSoft builds custom ERP and business systems, and we have delivered financial, property, and inventory systems for clients in Brazil, South Africa, Singapore, and the US. Our stack is Java, Spring Boot, and Spring Cloud with MySQL and Redis underneath, and we take on work across industries as long as it is legal.
When a client asks us SAP versus Odoo versus custom, our answer is rarely the same twice, because the right answer depends on their processes, their user count, and whether their edge is in the software or in the operations. If you are still deciding, we have written about the build versus integrate question and the wider build versus buy decision for ERP, both worth a read.
Is custom ERP cheaper than SAP?
It depends on users and time horizon. Custom ERP has no per-user licence and a larger upfront build. SAP has an ongoing licence plus implementation. Over enough years and users, custom usually wins on cost; for a small team that needs something fast, it rarely does.
Can I start on Odoo and move to custom later?
Yes, and many companies do exactly that. Odoo gets you running while you learn what your real requirements are. The main cost of the later move is data migration, which is manageable if you keep your data clean from the start.
How long does a custom ERP take to build?
Months, not weeks, and the range is driven by the number of modules and integrations. A focused system for one function is faster than a full company-wide rollout.
Do I need an ERP at all?
If your departments run on separate spreadsheets and you spend the end of every month reconciling them, you probably do. The question is less whether than which, and the answer usually comes down to how unusual your processes are and how many people will use the system.
What does GlobeSoft build ERPs in?
Java, Spring Boot, and Spring Cloud on the backend with MySQL and Redis, and Vue or React on the front. The stack matters less than getting your data model and integrations right before the first screen.
The SAP versus Odoo versus custom decision is not about which product is best in the abstract. It is about how much of your business you are willing to reshape, how many people will use the system, and how long you plan to keep it. Count the users, write down the three processes that are most unusual about your business, and the answer usually gets clearer.
Tell us what you are building and where you are today. We typically reply within 24 hours.
