SAP Business One pricing,
and what actually moves the number
Prices range from around £30,000 to £150,000 depending on what you need.
The three typical project sizes
The right investment depends mainly on how your business works, and the size of your team often matters less than you might expect. Because every business is different, the most accurate figure always comes from understanding your processes first, and we’ll take the time to do that properly with you.
To help you get started, below are the three shapes our projects usually take, so you can get a feel for which one sounds most like you before we sit down together.
Core finance and trading,
£30,000 to £45,000
Finance, sales and purchasing on the standard functions, for 10 to 20 users. Businesses from about £5 million turnover start here, and a typical example is around £10 million. It usually takes 4 to 6 months.
Across the whole operation,
£50,000 to £90,000
Finance, CRM, warehouse, purchasing and HR for 30 to 50 users, typically with some barcode scanning and an ecommerce connection. A typical business here is nearer £30 million turnover. Expect 6 to 9 months.
With manufacturing,
£100,000 to £150,000
Manufacturing in scope alongside finance, CRM, warehouse and purchasing, for 50 to 75 users, with the kind of process depth that takes 9 to 18 months to do properly.
Treat those bands as a guide, since plenty of projects sit between them, and a business with unusual manufacturing or a difficult integration can carry a higher price on a smaller user count.
What you get back for it
Your investment brings everything together in one system, replacing the accounting package, the spreadsheets around it and the time spent rekeying between them. Month end becomes quicker because your figures are already in one place, you can see stock and cash as they are today, and your business can welcome the next site, product line or 20 new colleagues without needing extra people just to keep the admin running. These are the real returns to weigh up alongside the cost, and Codestone will happily help you shape them into a clear business case that shows the value to everyone involved.
What moves the total
Most buyers assume user numbers drive the price, but licences are the predictable part of the cost, and it is scope and complexity that actually move a quote.
How many of your processes are genuinely standard, and how many are the way they are for a reason worth keeping. How much data has to come across, and what condition it is in, which is reliably the most underestimated line in any ERP budget. How many other systems have to talk to it. Whether you need manufacturing, warehouse management or ecommerce on top of finance and sales. The last is how much of the change your own team can absorb, because a business that can free up its people properly needs fewer of ours.
Licensing and how you pay for it
Licences come in two main types. Professional users get full access across the system, and limited users are cheaper and suited to people who only need a defined slice, such as raising a sales order or booking time. Getting that mix right is worth doing carefully, because the difference across 40 users is not small.
You can buy licences outright with an annual maintenance charge, or take them on subscription and spread the cost. Hosting on Azure removes the server investment and moves it into the monthly figure. Which is cheaper depends on how long you plan to run the system, and Codestone will show you both options side by side.
How it compares with the alternatives
Most buyers weigh SAP Business One against Microsoft Dynamics 365 Business Central. Business Central is sold on subscription per user per month, so compare the total over five years or so, and let fit decide more than the first-year figure. A smaller accounting package will cost less and suits a single company with simple trading. SAP S/4HANA is the larger step for businesses whose processes have outgrown Business One, with a correspondingly larger programme.
Microsoft Dynamics 365 Business Central · SAP S/4HANA · How the ERP platforms compare
What the bands do not cover
Two things sit outside the figures above and catch people out. Ongoing support is a separate arrangement once you are live, and it is worth deciding early. Any process redesign is also consultancy time, which is often the most valuable money in the project and the least likely to be in an initial estimate.
Getting a real number
A useful quote takes a conversation about your processes, your data and your systems. It is usually an hour or two to get to something you can take to a Board, and if the number is higher than you hoped, it is better to hear that now than in month three.
What SAP Business One does · See it running on your own process
Talk to one of our experts
Transforming
World Leading Brands
Common questions
-
Is SAP Business One affordable for a smaller business?
For a business with real operational complexity, usually yes. A 15-user finance and distribution implementation is a serious investment, well short of an enterprise one. If your needs are genuinely simple, a smaller accounting package may serve you better and we will say so.
-
What is the cost per user?
Per-user licensing varies by type and by how you buy, so a single headline figure would be misleading. The more useful question is your mix of professional and limited users, which we work out during scoping and which usually saves more than negotiating the rate.
-
Are there ongoing costs after go-live?
Yes. Annual licence maintenance or your subscription, hosting if you are in the cloud and a support arrangement. Budget for those from the start so the running cost is not a surprise in year two.
-
Why can you not just publish a price?
Because the same user count can be a 4-month project or a 14-month one depending on data, integrations and how much process change is involved. A single figure would look decisive and be wrong often enough to be useless to you.
Customer Success Stories
Armitage Pet Care
Rama Carpets
Plascoat Systems
EMS
Utmost Wealth Management
Waterside Holiday Group
Consilient Health Case Study
