Skip to Content Skip to content
Saxon Digital
Pricing

Priced to the size of the operation.

A five-person shop and a fifty-person manufacturer are not the same proposition, so we do not charge them the same. Scoping is banded by headcount; everything after it is fixed once scoping is done. Odoo licences are paid to Odoo directly and are not included in any figure on this page.

How Odoo project budgets break down

Scoping
£1,500–£6,000
banded by headcount, see below

Documentation, user stories, working sessions and a verification visit. You leave with a written architecture, a module list, a full implementation timeline and a fixed price.

  • Discovery questionnaire
  • User stories per role
  • Working sessions, in person or Teams
  • On-site verification visit
  • Module and licence plan
  • Migration assessment
  • Fixed build quote
Deployment · most start here
from £12,000
typically 8–14 weeks

The build. Configuration, data, integrations and the custom work the standard product doesn't cover.

  • Everything in Scoping
  • Configuration and custom modules
  • Data migration and reconciliation
  • Integrations
  • Training and handover
Managed
from £600 /mo
rolling, 60 days' notice

After go-live. Hosting, upgrades and a support line that reaches the people who built it.

  • Hosting and backups
  • Version upgrades, tested first
  • 2-hour response on a system-down
  • Quarterly review
Scoping bands

What discovery costs depends on how much operation there is to discover.

Headcount is the band, because it is the honest driver: more people means more roles to interview, more process variation and more exceptions that only one person knows about. It is also the one number you can answer without sending us your accounts.

1–9 people
£1,500

One or two roles doing most things. Usually a week, and often the whole operation fits in a single working session plus a visit.

10–49 people · most clients
£3,500

Distinct departments, several existing systems, and a process that differs depending on who you ask. Two weeks.

50–249 people
£6,000

Multiple sites or shifts, formal approval chains, and an existing IT estate that has to be mapped before anything is replaced. Three to four weeks.

250+ or multi-site
On the call

Quoted against the number of sites, entities and systems in scope. We will give you a range on the first call and a figure in writing within the week.

When the band is wrong

Headcount is a proxy, not a rule. A four-person e-commerce business running five systems can be more work than a thirty-person firm running one. If your operation is unusual for its size we will tell you which band it actually sits in before you commit, not after.

Why it is paid separately

Scoping is a deliverable, not a sales process. You get the architecture, the module plan and a fixed build price whether or not you appoint us, and you are free to take it to another implementer. That only works if it is paid for on its own terms.

Custom modules

Own the code outright, or licence it for a lower entry cost.

Custom modules are the one part of a build you have a choice about. Both routes are priced openly, and you can move from the second to the first at any point.

Route A · Assignment

You own it.

Full development fee. No licence.

Copyright in the custom modules is assigned to you on final payment. Source code, repository and documentation come with it. Nothing further is owed to us, ever.

  • Development at £650 per day
  • Full assignment of copyright
  • Repository handed over
  • Support agreement optional
Route B · Licence

We own it, you licence it.

50% off the development fee, then a monthly licence priced per module.

Half the build cost to get live, in exchange for a monthly licence for as long as you use the modules. We keep the right to reuse and improve them for other clients, and you get those improvements. You can buy the modules outright at any point for a fee agreed at the start, plus interest for each year elapsed.

  • Perpetual, irrevocable right to use and modify
  • Transfers if you sell the business
  • Source code held in escrow
  • Buy-out at any time at a fee agreed up front

Stated plainly

Route B costs less to start and more over time. Licence payments are not credited against the buy-out — they pay for the right to use and for the improvements that arrive. Both the licence fee and the buy-out figure are written into the agreement before you sign, so you can do the arithmetic for your own time horizon.

Which we recommend

Route A if the module is specific to how you trade, you intend to keep it for a decade, and cash at the start is not the constraint. Route B if getting live matters more than owning the code, or if the module is something other businesses in your sector would also use.

What is never licensed

Your data, your configuration, and your Odoo database. Those are yours under both routes and are exportable on request at any time, including after we part company.

What isn't in the price.

Odoo licences

Paid to Odoo per user per month. We'll tell you the number in scoping so there are no surprises.

Third-party fees

Payment providers, courier accounts, bank feed subscriptions. Yours, in your name.

Hardware

Scanners, label printers, tills. We'll specify what works and you buy it directly.

Scope you add later

Quoted as its own fixed piece before it starts. The original price does not quietly move.

Every number on this page becomes a fixed one after scoping.