Quick answer
Customise Odoo when most of your processes are standard (sales, invoicing, stock, CRM) and only a few steps are unusual. Build bespoke software when the thing that makes your firm different is the process itself, or when Odoo would need so many custom modules that upgrades become projects in themselves. Many firms mix both.
Odoo is an attractive answer for a growing firm. One system for quotes, jobs, stock, invoices and the CRM, with apps you switch on as you need them, sounds far better than five tools stitched together with spreadsheets. Then the questions start. Can it handle the way we price jobs? Can engineers use it on site without signal? Do we need a partner to set it up? And at some point someone asks whether it would be simpler to have something built that fits exactly. This guide compares the two honestly.
What Odoo is, briefly
Odoo is a suite of business apps that share one database: CRM, sales, invoicing and accounting, inventory, manufacturing, projects, field service, HR, website and more. You switch on the apps you need. It comes in two editions: Community, which Odoo describes as open source, and Enterprise, which is licensed and built on top of Community. Odoo’s editions page sets out the comparison.
Odoo can be customised in two main ways. Odoo Studio lets you add fields, change forms and build simple automations without code. For deeper changes, developers write custom modules in Python, following the framework described in the Odoo documentation.
At the time of writing (November 2026), Odoo’s pricing page lists a free plan for a single app, a Standard plan and a Custom plan, each charged per user per month. Studio (beyond the free single-app plan), the external API and the choice of Odoo.sh or on-premise hosting are listed on the Custom plan, so a business planning to customise should budget for that tier and check the current prices directly.
Side by side
| Customised Odoo | Bespoke software | |
|---|---|---|
| Starting point | A working system on day one | Nothing until the first release |
| Fit to your process | Good for standard processes; you adapt to it in places | Built around exactly how you work |
| Ongoing costs | Per-user subscription, plus partner or developer time | Hosting and maintenance; no per-user licence |
| Upgrades | New versions arrive regularly; custom modules may need updating each time | You decide when and what changes |
| Breadth | Accounting, stock, HR and dozens of other apps available | Only what you build or connect |
| Ownership | You configure and extend someone else’s platform | You own the code, usually outright |
| Speed to value | Fast for standard needs | Slower at first, faster for the unusual parts |
| Risk | Over-customising turns upgrades into projects | Under-specifying leads to rework |
When customising Odoo is the better choice
- Most of your work is standard. Quote, order, deliver, invoice, chase. Odoo handles that flow well out of the box.
- You need breadth. If you want stock, accounting, purchasing and HR in one place, building all of that bespoke would be slow and expensive.
- Your changes are small. A few extra fields, a custom report, a tweak to the quote template and some automations are well within Studio’s reach.
- You want a supported platform. Odoo has a large ecosystem of partners and developers, so you are not tied to one person.
For a wholesaler, a small manufacturer or a distributor whose processes look like most others in its sector, a well-configured Odoo is often the right answer.
When bespoke software is the better choice
- Your process is your advantage. A specialist pricing model, an unusual job workflow, or a customer experience competitors cannot copy is worth owning outright.
- You only need part of what Odoo does. If the core need is job management for a field team plus a customer portal, paying per user for a full suite may not make sense.
- Customisations keep growing. Each custom module is code that has to be checked and updated when Odoo moves to a new version. Past a certain point, you are maintaining bespoke software anyway, inside someone else’s framework.
- User numbers make per-seat pricing expensive. Many occasional users, such as site staff who only log a few jobs a week, can tip the sums towards a tool without per-user licences.
Our guide to no-code and custom development explains the same trade-off in more general terms.
The hidden cost: upgrades
This is the point firms most often underestimate. Odoo releases new major versions regularly, and each one can change the structures that custom modules depend on. Light Studio changes usually carry over smoothly. Heavy custom modules may need a developer to update and retest them before you can upgrade, and staying on an old version for too long brings its own problems.
Ask any Odoo partner two questions before customisation starts: what will it cost to upgrade these modules to the next major version, and how will they be kept compatible over time? If the answer is vague, factor in the risk.
The middle way: Odoo plus small bespoke tools
You do not have to pick one. A common and sensible pattern is to run Odoo for the standard back office, such as accounting, stock and purchasing, and build a small bespoke tool for the part that is genuinely different: a quoting calculator, a field engineer app, or a customer portal. The bespoke tool talks to Odoo through its external API, so data stays in one place.
That keeps Odoo close to standard, which makes upgrades easier, while giving you a tailored experience where it matters. It does need the Custom plan for external API access, and a clear decision about which system owns which data. Our API Development and Integration service builds exactly this kind of connection, and our guide to client portals for small businesses covers one of the most common add-ons.
A worked comparison
Consider a commercial cleaning firm with 40 cleaners across the Midlands, 6 office staff, and contracts priced by site, frequency and floor area. It needs scheduling, timesheets, invoicing and a portal where clients can see visit logs.
- Odoo route: Field Service, Planning, Timesheets and Invoicing cover much of it. Pricing by floor area and the client portal need customisation. If cleaners all need logins, per-user costs rise quickly, so the licensing model needs checking carefully.
- Bespoke route: a scheduling and visit-logging app for cleaners, a client portal, and an integration with an existing accounts package. Higher upfront cost, no per-user fees, and exactly the workflow the firm wants.
- Mixed route: Odoo for office staff and invoicing; a light bespoke app for cleaners and the client portal, connected by API.
There is no universal winner. The right answer comes from writing down the process, counting users, and pricing the next three years rather than the first month.

How to decide
- Map your processes and mark which are standard and which are genuinely yours.
- Count users, including occasional ones, and estimate the per-user cost over three years.
- List the customisations Odoo would need and ask for a written estimate, including upgrade costs.
- Get a bespoke estimate for the same scope, including hosting and maintenance.
- Compare totals, but also compare fit: which option will your team actually use every day?
If you currently run on spreadsheets and a CRM, our guide to CRM costs for small businesses helps price the simpler alternatives too.
Getting bespoke software built
Our Custom Business Software service starts from £1,499, building tools such as CRMs, quoting tools and job management around how your firm works, with each project scoped before work starts. For larger platforms with portals and dashboards, our web app development cost guide sets out what drives the price. All our prices are on the pricing page.
Get the UK Website Project Brief Template (free)
A two-page template for briefing any UK web designer: sitemap, integrations, audience and deliverables. Cuts revision rounds in half.
No spam. UK GDPR compliant. We only use your email to send this resource, unless you tick the box to hear from us.
Frequently asked questions
Can Odoo be customised without coding? +
Partly. Odoo Studio lets you add fields, change forms and views, and build simple automations without writing code. Deeper changes, such as new pricing logic or complex workflows, need custom modules written in Python by a developer. On Odoo's current pricing, Studio is included in the Custom plan, so check that tier when budgeting.
Why do Odoo upgrades cost money? +
Odoo releases new major versions regularly, and changes between versions can affect custom modules. Light configuration usually carries over, but heavy custom code may need updating and retesting before you can upgrade. Ask any partner for a written estimate of upgrade costs before customisation starts, and keep customisations as light as possible.
Is bespoke software more expensive than Odoo? +
Usually upfront, not always over time. Odoo charges per user per month, plus partner or developer time for customisation and upgrades. Bespoke software costs more to build but has no per-user licence. Firms with many occasional users or highly specific processes often find bespoke, or a mix, cheaper over three years.
Can I use Odoo and bespoke software together? +
Yes, and it is often the best answer. Run Odoo for standard back-office work such as accounting and stock, and build a small bespoke tool for the part that is genuinely different, such as a quoting calculator or field app. The two connect through Odoo's external API, which on current pricing sits on the Custom plan.


