How much Business Central will cost your company
Answer five questions and get an estimate of Microsoft license costs plus an implementation budget range. Takes one minute — no contact details required.
How we calculate
Licenses — official Microsoft prices (from November 2025): Essentials $80, Premium $110, Team Member $8, Device $45 per user per month. All full users in one environment must share the same license type — so if even one person needs manufacturing, everyone moves to Premium.
Implementation — the industry rule of thumb: a project budget typically equals 1.5–2.5× the annual license cost and depends on process complexity, the amount of AL development, the number of integrations and the quality of data in the legacy system. The calculator maps your scenario to typical market budgets:
Not included in the estimate: post-go-live support subscription (SLA), Power BI Pro and AppSource solutions — we scope those separately for your scenario. Typical implementations are also available as fixed monthly packages.
You are on the calculator — the fastest way to a number for your own headcount. Three other pages cover the rest of the picture: Licence pricing per userWhat an implementation costsUK prices in sterling
What actually drives the cost
Two numbers make up a Business Central budget, and they behave very differently. Licences are a predictable monthly subscription paid to Microsoft, calculable to the dollar. Implementation is a one-off project paid to a partner, and it varies by a factor of five between two companies of the same headcount.
The calculator above models both. The factors below are what move the second number.
| Factor | Effect on budget | What you control |
|---|---|---|
| Number of users | Direct effect on licences, moderate on the project | The mix matters more than the count — see below |
| Areas covered | High | Finance only is a different project from finance plus warehouse plus manufacturing |
| State of your data | High, and usually underestimated | Duplicate counterparties and inconsistent item codes become billable hours |
| Customisation | High, and recurring | Every deviation from standard is development, testing and ongoing maintenance |
| Integrations | Medium per connection | Bank, e-commerce, POS, EDI — check AppSource before commissioning code |
| Reporting | Low to medium | Standard financial reports cover most needs; Power BI is a separate scope |
| Training | Medium | The most frequently cut line, and the one that decides adoption |
| Support after go-live | Recurring | Whether it sits inside the project fee should be in the contract |
The user mix is where money is saved
Most overspend on licences comes from one habit: counting headcount and buying that many full users.
A workforce usually splits three ways. People who create documents daily — finance, warehouse, purchasing, sales — need full licences. People who only read data and approve things — department heads, directors — are covered by Team Member. Shared terminals, such as a goods-in station used by three shifts, are covered once by a Device licence rather than per person.
For a 25-person company the difference between the naive and the correct mix runs into five figures over three years. The arithmetic is worked through in Business Central pricing per user.
What the estimate deliberately excludes
- Post-go-live support subscription. Scoped against your actual usage rather than guessed.
- Power BI licences where reporting goes beyond built-in financial statements.
- AppSource extensions — each carries its own per-user subscription.
- Database capacity above the allowance included with your users.
These are left out on purpose. An estimate that silently folds in assumptions produces a number you cannot check, which is worse than a number with visible boundaries.
How to read the result
Treat the licence figure as close to final — it comes from Microsoft's published list prices and changes only when Microsoft changes them. Treat the implementation range as a bracket for planning, not a quote: the same scope quoted by two partners differs mainly in how much discovery each one does before committing.
Where the estimate should send you next depends on what you are deciding. If the question is whether an ERP is justified at all, start with who Business Central fits. If you are comparing platforms, the ERP selection guide covers the criteria that matter. If the project is already decided and you need the breakdown by stage, read what an implementation costs.
Want an exact figure instead of a range?
Leave your details — your calculation is attached to the request automatically. We'll run a free process audit and fix the scope.
or write directly: info@nbcs365.com · +380 98 107 5878
Business Central cost: typical scenarios
The calculator returns a range. These examples show what that range is made of in real projects.
| Scenario | Users | Licence | Timeline | Scope |
|---|---|---|---|---|
| Retail, basic accounting | 5–15 | Essentials | 8–10 weeks | Finance, sales, purchasing, simple inventory |
| Distribution | 20–50 | Essentials | 12–16 weeks | Multiple warehouses, lot tracking, bank and webshop integration |
| Manufacturing | 30–80 | Premium | from 16 weeks | BOMs, routings, planning, costing |
| Professional services | 10–40 | Essentials | 10–14 weeks | Projects, time tracking, profitability, resources |
Essentials or Premium: which to choose
| Capability | Essentials | Premium |
|---|---|---|
| Finance, general ledger, budgets | Yes | Yes |
| Sales, purchasing, inventory | Yes | Yes |
| Projects and time tracking | Yes | Yes |
| Manufacturing (BOMs, routings, planning) | No | Yes |
| Service management | No | Yes |
Simple rule: if you manufacture with bills of materials you need Premium. If you buy and resell, Essentials is enough. Licence types cannot be mixed within one company.
Frequently asked questions about cost
How accurate is the cost calculator?
It returns a range based on user count and module scope. Treat it as a planning benchmark, not a quotation. An exact figure follows a process analysis — usually one or two workshops.
What is included in the estimate and what is not?
The estimate covers Microsoft licences and implementation work. It excludes complex data migration, non-standard integrations and custom development for unique processes — those are scoped separately after analysis.
Can implementation cost be reduced?
Yes, in three ways: use standard functionality instead of customisation, implement in phases, and prepare data with your own team. The largest saving comes from avoiding unnecessary customisations.
Do we pay for licences during implementation?
Yes, the subscription starts at project kick-off since the team works in the system during configuration and testing. Fewer licences are usually needed during implementation than after go-live.
What happens to cost as the company grows?
Licences scale monthly: add users and pay for them from the next period. That is the main advantage of subscription over a perpetual purchase — you do not overpay upfront.