Before anything else, a clarification that settles half the conversations we have about this product. Microsoft publishes Dynamics 365 as a family of CRM and ERP applications rather than as one system, and Dynamics 365 Business Central is the mid-market ERP application within that family — the one this page is about, and the one our catalogue entry is named after. A quotation for Dynamics 365 is not a quotation for anything until it states which application, on which plan, for how many users. Establishing that is the first thing we do, and we earn nothing different depending on the answer. The product sits in our ERP systems category alongside everything it is usually weighed against.
It fits mid-market organisations that have outgrown accounting software and want finance, sales, service and operations in one place, which is how Microsoft itself frames the product. It fits estates that are already Microsoft-centred, where a second vendor's interface would be tolerated rather than adopted and the argument for staying inside one ecosystem is as much about adoption as about technology. It fits distribution and light manufacturing operations that need inventory and supply chain in the same system as the ledger. And it fits organisations that want a broad standard platform and have the discipline to stay close to it.
We do not recommend it when the requirement is enterprise-scale finance and operations across many entities and countries: that is a different application inside the same family, sized and priced differently, and conflating the two is the most expensive mistake available on this platform. We do not recommend it when the real pain is bookkeeping rather than operations — a full ERP is an expensive way to fix an accounting problem, and a dedicated accounting platform will cost less and land sooner. And we are cautious where the appetite for process change is low, because the economics of a standard cloud suite depend on staying close to standard. In those cases we say so, and an impartial ERP assessment is where that conversation starts.
We restrict this section to what Microsoft publishes. On its own Business Central product page, Microsoft describes the application as connecting finance, sales, service and operations in a single easy-to-use solution and, in its manufacturing material, as bringing finance, production, inventory and supply chain operations together in a single platform. Its entry-level plan is described as comprehensive business management for finance, sales and operations, with Microsoft Copilot included. Microsoft's Dynamics 365 landing page presents the wider family as CRM and ERP solutions, with Business Central listed as one product among several. Anything a salesperson adds beyond that is a claim we would have to verify before repeating, so we do not repeat it here.
The first limitation is the one every standard cloud suite shares: the economics assume you stay close to standard, and heavy extension is both possible and the usual route to dreading every update. The second is the ceiling — this is the mid-market application, and an organisation that grows past it faces a move to a different application in the same family rather than a configuration change. The third is that the licence conversation understates the work: data migration, integration to everything outside the Microsoft estate, and the redesign of processes that currently live in spreadsheets are the real programme, and none of them is on the quotation. Plan the second and third before you negotiate the first.
A Saudi implementation has to satisfy local obligations that a global template does not cover on its own: ZATCA e-invoicing has to work in production from the first day, VAT at 15% has to be configured and reconciled, and Arabic-language documents and right-to-left output have to be tested rather than assumed. We establish which obligations bind you, and we confirm data residency and regional availability in writing with the vendor rather than repeating a claim on your behalf. For a sector view, see retail.
Microsoft publishes per-user prices for this product. We do not reproduce them: they move, they vary by region and agreement, and a figure copied onto an advisor's page is a figure someone will later hold us to. What we build with you instead is the three-year picture — subscription, implementation fees, data cleansing and migration, integration to everything that is not Microsoft, training, and the internal capacity you will divert for the duration. On a mid-market cloud ERP the ratio of services to subscription is the number that surprises boards, and it is the one we model first, from your scope rather than from a benchmark.
The comparisons that matter are published rather than asserted: see NetSuite vs Dynamics 365 and SAP S/4HANA vs Dynamics 365, or browse all our independent software comparisons. The deciding factors are usually how Microsoft-centred your estate already is, the depth your vertical demands, the number of entities you consolidate, and how much process standardisation your organisation can absorb. Where the shortlist is genuinely two cloud suites, Oracle NetSuite ERP is the sibling question.
We start from your operating model: entity structure, transaction volume, inventory and order complexity, and the reporting the board actually reads. Candidates are scored against criteria agreed with you before any vendor conversation, and the scoring is written down so your own people can challenge it. If the evidence says a lighter platform fits, that is the recommendation, even though it is the smaller engagement.
We inventory every interface the suite will have to carry — banking, e-invoicing, warehouse and logistics, payroll, e-commerce — decide which survive and which retire, and design the integration layer before configuration begins. Interfaces discovered late are the most reliable cause of a delayed go-live, on this platform as on every other.
Training is planned by role and by process rather than by module, and it starts before cutover. Super-users are identified early and given real time to become competent, because they are who the business will actually ask. The first period close runs with our people on call, since that is when an ERP is genuinely judged.
We publish no percentages and no counters on this page. What we will say about outcomes is structural: the implementations that go well are the ones where the organisation agreed to change process before it agreed to change software, and where the integration map existed before configuration started. Ask us for references in your sector and we will arrange direct conversations.
We do not quote a standard duration. The timeline is set by which application you are actually buying, entity count, data quality, the number of interfaces, and how much legacy configuration you insist on carrying forward. We size it during the assessment with the assumptions written down so you can challenge them.
Subscription, implementation fees, data migration, integration, training and change management, and the internal capacity you divert. We model it with your figures rather than publishing a range, because a range not built on your scope is a guess wearing a number.
Compliance posture is configuration- and deployment-specific, so we do not answer this generically in either direction. We establish which ZATCA and statutory requirements bind you, confirm the residency position in writing with the vendor, and verify the configuration against those requirements before go-live rather than after.
Typically another mid-market cloud ERP, an enterprise platform where size justifies it, and — where the pain is narrower than it looks — a dedicated accounting platform. The evaluation and its scoring are part of the deliverable, so you can see what was considered and why it lost.
Yes, and on most estates it has to — banking, e-invoicing, warehouse and e-commerce systems normally stay. The question is which interfaces survive the move and who maintains them when an API changes. We audit that dependency chain as part of the assessment.
This heading promises numbers, and we are going to break that promise deliberately. We publish no counters, no project totals and no percentages, here or anywhere else on the site, because an advisor's counter cannot be checked by the reader who most needs it. What we will state about our own work is checkable: we take no vendor commission, we do not bid for the implementations we scope, we score candidates against criteria agreed with you before any demonstration, and we hand over the written evaluation whether or not you engage us further.
We name clients only with their consent, and in direct conversations rather than on a product page. The organisations we work with on this platform are mid-market groups in distribution, retail and services, and references from Saudi organisations in comparable sectors are available on request.
Every engagement ends in a written, evidenced recommendation with the operating-model analysis, integration map and cost model behind it. The deliverable is yours regardless of who implements, and it is the thing worth judging us on.
We do not publish testimonial quotes on this page. Speak to our references directly; an unmediated conversation with someone who has been through an implementation tells you more than a curated pull-quote ever will.
We publish no accreditation claims, and we hold no vendor partner designation on this platform. That is also why this page is titled independent advice rather than independent partner: next to a Microsoft product name the word partner means something specific to Microsoft, and we are not going to borrow it. What qualifies us is narrower and easier to check — we take no vendor commission, we do not implement what we recommend, and every recommendation is written down with its evidence, so you can audit the reasoning instead of the badge.
Continue with our ERP systems category, ERP consulting, the NetSuite vs Dynamics 365 comparison, or retail if that is your sector.
If Dynamics 365 is on your shortlist, or a partner has already quoted you for it, book an evaluation before you negotiate. You will leave with a fit verdict that names the application, an integration map and a cost model you can hold the vendor to. Request a demo or ask for an impartial assessment.
Unlimited support included.
One-on-one onboarding sessions.
Training videos, webinars, & demos.