There is a recognisable moment when a company stops being served by its accounting package: stock lives in a spreadsheet, orders are keyed twice, and month end takes three weeks because everything has to be reconciled before it can be reported. Business Central is Microsoft's answer for exactly that point — a full ERP that a mid-market business can genuinely implement.
Business Central is a comprehensive business management application for small and mid-sized organizations, covering finance, supply chain, manufacturing, projects and service operations. These are the four conditions that usually mean it is time.
It was designed for the ledger and is now being used for stock, jobs, quoting and scheduling through a growing collection of workarounds and add-ons that nobody fully understands.
Pricing, inventory, forecasting or job costing runs in a workbook maintained by one person. Everybody knows this is a risk; nobody has had a quiet enough quarter to replace it.
An order goes into the quoting tool, the accounting system and the shipping platform. Each rekey is a chance to be wrong, and reconciling the differences takes longer than the entry did.
By the time the management accounts arrive, the period they describe is long over. Decisions get made on instinct because the numbers are not available when the decision is.
Where the return actually comes from: For a mid-market business the return is rarely one dramatic saving. It is volume absorbed without proportional hiring; errors that stop reaching customers; a month end that closes in days instead of weeks; and working capital released because inventory is finally visible enough to plan from. Revenue growth follows indirectly but reliably — quoting from accurate cost and availability wins more of the right work, and a business that is not bottlenecked on one person's spreadsheet can take on more of it.
The capability that matters when you are comparing it against staying where you are.
General ledger, receivables, payables, fixed assets, cash flow forecasting, bank reconciliation and multi-entity consolidation — with dimensions that let you report by department, project, location or customer without rebuilding the chart of accounts.
Purchasing, sales orders, inventory across locations, warehousing, assembly and light manufacturing, with availability and replenishment planning built in rather than bolted on.
Job budgets against actuals, resource planning, time capture and work-in-progress — enough for a business that delivers work as projects without needing a separate system.
Microsoft's current release wave adds agents that handle document interpretation, categorisation and approval in payables and expenses, plus assistance with sales and purchasing tasks.
Work inside Outlook and Excel rather than beside them — quotes raised from an email thread, data edited in Excel and written back, reports built where finance already works.
Power Apps and Power Automate for workflow, plus a proper extension model for genuine development, with recent investment in Model Context Protocol support for connecting Copilot Studio agents.
Microsoft's direction here is agentic ERP: AI agents that carry out routine processing in payables, expenses, sales and purchasing rather than merely suggesting actions. For a mid-market business this matters more than it does for an enterprise, because the finance team is small and the routine processing is a disproportionate share of its week.
We baseline from your current close cycle, inventory position and error rates before committing to any target.
Typical improvement when finance and operations share one system
Reduction where rekeying between systems is eliminated
Working capital released as visibility improves
Current position rather than last month's report
Volume absorbed without proportional hiring
No reconciliation between operations and the ledger
How to read these: How to read these: the figures above are typical ranges we plan and measure against, not guarantees. In your first engagement we agree the baseline, the target and the measurement method in writing, then report against them.
Microsoft's product documentation frames Business Central's value in the following terms.
Where this comes from: Where this comes from: these themes follow Microsoft's Business Central documentation and release plans on learn.microsoft.com, including the 2026 release wave 1 plan covering AI agents in payables and expenses. The numeric ranges above are ours, drawn from comparable implementations, and are planning figures rather than Microsoft benchmarks.
The same product, configured around very different operations.
Multi-location inventory, customer-specific pricing, purchase planning against lead time, and margin by customer and product.
Bills of material, assembly and production orders, capacity planning and actual versus standard cost by run.
Job costing, resource planning, time capture and work-in-progress — where projects are the business but a full enterprise suite is overkill.
Job budgets, subcontractor management, progress billing and retention, with cost visible while the job is still running.
Fund and grant tracking with restricted fund reporting, at a licence cost a small finance team can justify.
Inter-company transactions and consolidation across entities and currencies without a separate consolidation tool.
We deliberately scope phase one smaller than most firms propose. It should prove itself before phase two is commissioned.
Establishing whether you actually need an ERP yet, and if so, how much of one.
The core build: configuration, migration, integration and go-live to a fixed price.
The layer that makes it fit your business rather than the other way round.
Implementation, customization, support and integration — scoped for an organization where everyone involved also has a day job.
Environment design, tenant and licensing setup, configuration, data migration, testing and go-live — scoped to a fixed price and a fixed date, against outcomes agreed in writing before we start. For a mid-market business that means a phased go-live with a parallel run, and a time commitment from your team that we agree in hours upfront and hold ourselves to.
Where the product stops short of your process, we extend it inside the platform rather than beside it, and we build it as configuration you can maintain wherever that is possible. Configuration over code wherever possible, with Power Platform for workflow, so your own team can adjust things later without a change request and a consulting day.
Managed support after go-live: a named team, agreed response times, release management for Microsoft's update cadence, and a backlog we work through with you. Support priced for a business without an internal applications team, plus release management for Microsoft's two annual waves so updates are tested rather than experienced.
Connecting this platform to the systems you are keeping, with monitored, re-runnable interfaces and a documented contract for every field that moves. Connections to e-commerce, payroll, banking, CRM and any industry system you are keeping — before we recommend replacing any of them.
We will tell you if Business Central is more than you need. Plenty of businesses at this threshold are better served by properly integrating what they already have, or by a Power Platform application over their existing accounting system, and recommending that costs us a much larger engagement.
The failure mode in mid-market ERP is not technical complexity. It is that the client's key people were never actually available and nobody said so at the start.
We map how the business actually runs today, including every workaround and spreadsheet.
We agree the chart of accounts, dimensions and process design before anything is configured.
We build it, then show you your own data in it — not a demo company.
We move data with reconciliation back to your last closed period, and run parallel before cutover.
Permissions, segregation of duties and backup validated, then a hand-over your team can run.
We reconcile migrated data back to your last closed period before go-live. If the new system cannot reproduce a set of accounts you have already signed off, the migration is not finished — and finding that in testing costs a fraction of finding it in your first month end.
Enterprise ERP firms are structurally unsuited to companies this size. We are built for it deliberately.
You should not be sold an enterprise programme for a seventy-person company. We propose the smallest phase one that solves the real problem and build from there once it has proved itself.
Configuration over code, documentation written for your staff, and training as a deliverable. If you can only change things by calling us, we designed it badly.
The migration is judged by whether your finance team can close. That is the deliverable, not the go-live date.
The ERP, Microsoft 365, security, devices and support from one team — because at your size, managing six vendors is itself a job.
Two illustrative engagements showing the shape of the work.
Stock lived in spreadsheets, orders were keyed into three places and month end took the finance manager the best part of three weeks. Growth had stalled on administrative capacity rather than demand.
Three trading entities each ran separate books, and group reporting was assembled quarterly in a spreadsheet that only the financial controller could operate.
Practical pieces on knowing when and how to make the move.
Four symptoms that reliably indicate an ERP conversation, and two that look like it but are not.
Read moreWhy data migration should be judged against a period you have already signed off.
Read moreHow to scope a first ERP phase that proves itself instead of consuming a year first.
Read moreSend us a chart of accounts, an item list and a month of transactions. We will configure a demo environment with your data in it, walk your finance and operations leads through their own month end, and tell you honestly what a phase one would cost.
Describe the situation in your own words.
