Search for what SAP Business One costs and you will find a great deal of writing that never answers the question. There is a reason for that, and it is not evasiveness: SAP does not publish a public price list for Business One. Licences are sold through partners, and the final figure depends on how many people need access, what each of them needs to do, and how much work it takes to get the system fit for your business.
That said, “it depends” is not an answer either. So here is how the pricing actually works, with the ranges a UK business should expect, and — more importantly — what moves the number.
The three components of the cost
Every SAP Business One quote breaks into three parts. Confusing them is where most budgeting goes wrong.
- Licences — what you pay for people to use the system
- Implementation — what you pay to make it work for your business
- Ongoing costs — maintenance or subscription, hosting, and support
The first is the number people ask about. The second is usually the largest. The third is the one that decides whether the project was good value five years later.
1. Licences: Professional and Limited
SAP Business One licences come in two main types, and getting the mix right is the single biggest lever on your licence bill.
Professional licences give full access to everything — finance, sales, purchasing, inventory, production, administration. Your finance team, system administrator and anyone doing month-end needs one.
Limited licences are restricted to a functional area: Limited Financial, Limited Logistics or Limited CRM. A warehouse supervisor who only receives goods and picks orders does not need a Professional licence. Neither does a salesperson who raises quotations.
As a broad UK guide, independent buyer research puts subscription licensing at roughly £120–£160 per Professional user per month and £65–£95 per Limited user per month. Buying outright instead, a perpetual Professional licence typically lands in the region of £2,400–£3,200 per user, with Limited licences around half that, plus annual maintenance of 18–22% of the licence value.
Treat those as orientation, not a quote. Partner pricing, volume and the package you choose all move them.
The mix matters more than the rate
A twenty-user business that licences everyone as Professional will pay roughly twice what a business that licences eight Professional and twelve Limited will pay — for the same twenty people doing the same jobs. Before you ask anyone for a price, write down every person who will touch the system and what they actually need to do in it. That exercise is worth more than any negotiation.
2. Subscription or perpetual: which is cheaper?
It depends entirely on your time horizon, and the arithmetic is worth doing properly.
Subscription spreads the cost, includes updates and support, and keeps the commitment short. It is usually right if cash flow matters, if headcount is likely to change, or if you want the option to walk away.
Perpetual means you buy the licence outright and pay annual maintenance afterwards. It costs considerably more in year one. Somewhere between year four and year six, depending on the numbers, it becomes the cheaper option — and from then on the gap widens.
The practical test: if you are confident you will still be running this system in seven years, perpetual usually wins. If you are not confident, the flexibility of subscription is worth paying for. It is also a capital-versus-operating-expenditure question, and your accountant may have a firmer view than your IT preference does.
3. Implementation: the number that actually decides your budget
This is where quotes diverge wildly, and where the honest conversation needs to happen.
UK partners typically charge in the region of £120–£200 per hour for implementation work. For a straightforward deployment at a small business — standard finance and distribution processes, clean data, no unusual integrations — implementation commonly runs from around £16,000 to £40,000. A mid-sized business with manufacturing, multiple locations or integrations to existing systems should expect meaningfully more.
What drives that figure:
- Data migration. How much history you bring across, and what condition it is in. This is consistently the most underestimated line in any ERP project.
- Integrations. Every connection to an existing system — e-commerce, EDI, a bespoke application, a payroll package — is a separate piece of work.
- Customisation. Every deviation from standard functionality costs money twice: once to build, and again at every upgrade.
- Number of processes. A business running three straightforward workflows is a different project from one running fifteen, even at the same headcount.
- Training. How many people, in how many roles, and whether you train on real data or a demo company.
The costs that rarely appear in a first quote
Ask about these explicitly. A good partner will raise them unprompted; it is a useful test.
- Hosting. If you are not on SAP’s own cloud, someone has to host the system. Budget for it.
- SQL Server or HANA licensing. Depending on deployment, the database may be a separate cost.
- Add-ons. Much of the SAP Business One ecosystem is third-party — warehouse management, advanced reporting, e-commerce connectors, document automation. Each carries its own licence and support fee.
- Your own people’s time. Not an invoice, but the real cost of the project. Expect your finance lead and a key user from each department to lose meaningful time for several months. Projects fail when businesses pretend this cost is zero.
- Year two support. Clarify what the ongoing support arrangement covers and what is billed separately, before you sign anything.
A sensible way to budget
If you want a rough planning figure before you have any quotes:
- List every user and assign them Professional or Limited.
- Price the licences from the ranges above for a first-year figure.
- Multiply that first-year licence figure by two to four for implementation, depending on how complex you honestly are.
- Add 15–20% contingency. You will use some of it.
That will not be exact, but it will tell you quickly whether the project is in the right order of magnitude for your business — which is usually what you need to know before spending time on vendor meetings.
Is it worth it?
The honest answer is that it depends on what the current situation is costing you, and most businesses have never worked that out. Before committing to any ERP spend, put a number on the following:
- Hours per month spent re-keying data between systems
- How long month-end takes, and what that costs in salary
- The cost of stock you hold because you do not trust your stock figures
- Decisions made late, or made on figures that turned out to be wrong
For many businesses that total is larger than the ERP project. For some it is not — and in that case the right advice is to wait. A system bought before the business needs it becomes an expensive filing cabinet.
Getting a real number
Ranges are useful for planning and useless for deciding. A genuine figure needs someone to look at your user count, your processes and your data.
Book a free consultation and we will give you a realistic range for your situation — including, where it applies, the advice that you are not ready for ERP yet.
Oskar Systems Ltd is a UK ERP consultancy working with SAP Business One and Microsoft Dynamics 365 Business Central. The figures above are indicative ranges drawn from independent UK buyer research and are intended for planning purposes only; confirm current pricing for your own requirements before budgeting.