Blog
What a Business Central implementation really costs
The first question every prospective client asks is “how much will it cost?” — and the honest answer is “it depends, and here is exactly what it depends on.” Two companies of the same size can land at very different numbers. This post explains the cost drivers so you can recognise them in your own project, rather than quoting figures that would mean nothing without context.
Process complexity
A business that runs close to standard processes — straightforward order-to-cash, simple purchasing, standard VAT — is fast and cheap to implement. The cost climbs with every unusual workflow, approval chain or pricing rule that has to be modelled and configured.
Why it matters: complexity you carry out of habit, not necessity, is the most expensive thing you can bring to an implementation. An early process review often finds workflows that exist only because the old system forced them — and dropping those is the cheapest saving available.
Number of customisations
Business Central does a great deal out of the box. Every requirement met by configuration or a standard feature costs a fraction of one met by custom AL code — and custom code also has to be tested, documented and carried through every future update.
Why it matters: this is why we work “standard first, custom second.” Each customisation you avoid is money saved twice: once now, and again in every upgrade for the life of the system. Custom code is sometimes exactly right — but it should be a decision, not a reflex.
Data migration scope and quality
How much history you bring across, from how many systems, and in what state, is one of the biggest and least predictable cost drivers. Clean master data and a clear scope migrate quickly. Years of duplicated customers, broken document links and inconsistent coding turn migration into the part of the project that overruns.
Why it matters: data quality, not data volume, is usually the culprit. Cleaning up before migration — or deciding to bring less history — is far cheaper than untangling it mid-project.
Integrations
A standalone Business Central is one thing. One that exchanges data with a webshop, a payroll system, a warehouse or a bank is another. Each integration adds design, build, testing and ongoing maintenance — and the count and depth of integrations often drives more cost than the core implementation itself.
Why it matters: standard connectors and APIs are dramatically cheaper than bespoke integration code. Knowing which of your systems already have a supported connector changes the budget before a line of code is written.
Training, users and companies
People drive cost too. The number of users to train, the number of legal entities or companies to set up, and the depth of training each team needs all scale the project. A finance team adopting a new system needs more than a one-hour walkthrough.
Why it matters: under-investing in training is a false economy — it shows up later as workarounds, errors and support tickets. Budget for people to actually become competent, not just to be shown the screens once.
A realistic SMB timeline
For a typical small or medium business implementing close to standard, expect roughly 6 to 12 weeks from kickoff to go-live. Heavy customisation, messy data or multiple integrations push that out; a clean, standard-first project lands at the shorter end.
Why a free estimation pays off
Because every one of these drivers varies, a real estimate requires looking at your processes, data and systems. That is exactly what a proper scoping conversation does — and why we offer it free. You walk away knowing where your costs sit and which of them you can reduce, whether or not you work with us.
Want to know what your implementation would actually cost? Tell us your story and we will give you an honest, free estimation.