The wrong question, asked at almost every kick-off

Most ERP evaluations start with a feature comparison: does the platform do multi-entity consolidation, advanced production planning, deep warehouse orchestration, complex revenue-recognition waterfalls. Business Central usually loses that comparison against NetSuite, against Dynamics 365 Finance & Operations, against SAP — because it was never built to win it. That is not a weakness to be argued away. It is a design choice, and design choices are meant to fit a purpose, not every purpose.

The better question for a growth company is narrower and more useful: given where we are today — headcount, entity count, process maturity, existing IT stack — which platform's strengths overlap with our actual constraints? For a meaningful share of companies moving off spreadsheets or entry-level accounting software, the honest answer is Business Central, and the reasons are specific rather than generic.

Where Business Central genuinely plays to its strengths

Strip away the marketing language and four structural advantages remain, each of them real and each of them a reason growth companies choose the platform and keep it:

  • A standardised implementation model. Business Central was designed to go live in weeks, not quarters, using accelerated, template-driven configuration rather than a ground-up build. For a company that needs clean finance running before the next funding round or the next audit, time-to-value is not a nice-to-have — it is the requirement.
  • Native integration with Microsoft 365 and the Power Platform. Growth companies in this segment are already running Outlook, Excel, Teams and SharePoint. Business Central sits inside that same tenant rather than beside it — Power BI as the reporting layer, Power Automate for workflow, Power Apps for lightweight extensions. The finance system becomes one more application in a stack the team already knows, not a second world with its own logins, its own admin model and its own learning curve.
  • Licensing that scales cleanly with headcount. Per-user, per-module licensing tracks the thing that actually changes as a growth company grows: the number of people who need access. There is no step-function re-negotiation at each growth stage, no forced platform migration triggered purely by adding twenty employees. The commercial model moves at the same pace as the org chart.
  • A strong fit for two specific business models. Project-based services businesses get clean job costing, resource planning and margin visibility without a heavyweight build. Subscription and SaaS companies get the revenue-recognition discipline, dimension-based reporting and light-to-moderate inventory handling they actually need — without inheriting the manufacturing and distribution depth they do not.
The platform is not trying to be everything. It is trying to be very good at getting a Microsoft-centric growth company from spreadsheet finance to standardised, auditable finance, fast — and then to stay out of the way while the business scales.

The growth-company profile where it plays out best

Fit is a function of profile, not size alone. In practice, the companies where Business Central performs best share a recognisable set of characteristics:

  • Roughly 20 to 250 employees — past the point where spreadsheets and entry-level accounting software hold, but not yet running a group structure that needs deep multi-entity consolidation.
  • One legal entity, or a small number, without the layered ownership structures, partial consolidations and cross-currency group reporting that change the calculus entirely.
  • Standardising finance for the first time — coming off QuickBooks, Xero, or a patchwork of spreadsheets that a small team has outgrown, rather than replacing a mature ERP that already carries deep process history.
  • A Microsoft-centric IT environment already in place, where the decision-makers value time-to-value and operational simplicity over deep, bespoke customisation.
  • An operating model closer to services or SaaS than to manufacturing or complex distribution — two of the five practice areas the group is built around, alongside finance and consolidation, manufacturing, and retail.

Fit, not deficiency

None of this is a statement about Business Central being "smaller" than other platforms in a way that counts against it. A scalpel is not a lesser tool than a multitool because it does fewer things — it is the better tool for the job it was built for. The right framing for a growth company evaluating Business Central is which growth profile fits, not which platform is objectively superior.

Where the natural boundary sits — and what that means

Every platform has a point past which a different configuration serves the business better, and being honest about that boundary is part of giving good advice rather than selling a licence. For Business Central, two scenarios sit past that boundary:

  • Consolidation at real multi-entity scale. Once a group is running a double-digit number of legal entities, multiple currencies, and partial-ownership consolidation with statutory depth, a platform built for that scale from the ground up — inside the group's portfolio, that is NetSuite — is typically the better long-term architecture.
  • Deep manufacturing operations. Advanced production planning, complex routings, shop-floor scheduling and multi-site manufacturing orchestration sit more naturally on Dynamics 365 Finance & Operations, or on a NetSuite build configured for manufacturing depth, than on Business Central's lighter production module.

Neither of these is a criticism of Business Central. It is simply where a different growth profile — bigger, more entities, heavier operations — starts to outgrow what the platform was designed to do well. The honest advisory answer, in either direction, is the same: match the platform to the profile, not the profile to the platform.

When the rescue conversation starts instead

The implementations that end up needing a rescue are rarely the ones where Business Central was the wrong platform. They are the ones where it was implemented without finance-first discipline — chart of accounts copied from a spreadsheet rather than designed, dimensions bolted on after go-live, reconciliation left as a manual monthly exercise because no one owned the design decision up front. The platform absorbs a surprising amount of that neglect before it becomes visible; then a funding round, an audit, or a new CFO surfaces it all at once.

That is a delivery-discipline problem, not a platform problem, and it is the same pattern the group addresses on its Finance & Operations rescue work: stabilise the finance foundation first, then let the platform do what it was already capable of doing. For Business Central specifically, most of that work is preventable at implementation time — which is the more valuable conversation to have.

The decision, put plainly

If your company is standardising finance for the first time, running on Microsoft 365 already, operating as a services or SaaS business, and somewhere between twenty and a few hundred people — Business Central is very likely to be the right platform, and the right question is how to implement it with finance-first discipline from day one. If your reality looks like dozens of entities, multiple currencies and statutory consolidation, or deep manufacturing planning, the more useful conversation starts one level up, at architecture, before it lands on a specific platform.