Headcount is the wrong question
We are asked every week whether a business is "big enough" for Finance & Operations. Size of the payroll is the wrong axis. A 40-person lender with three entities, a core banking feed and IFRS 9 can outgrow Business Central. A 400-person distributor with one company, clean inventory and no group pack can live on Business Central for years.
The axes that matter are entity count, integration load, and the regulatory reporting you must produce without a workbook. If any of those will grow, choose the platform that can absorb the growth without a second implementation.
Choose Business Central when the shape stays simple
One to a few legal entities. A manageable integration list. Finance that wants a modern ledger, approvals and inventory without an enterprise programme. Most of our retail, food-and-beverage and NGO clients start here, with the ISVs that make it local: eTIMS, payroll, grants, procurement, POS.
Business Central is the wrong economy when you already know you need multi-book accounting, advanced warehouse, manufacturing MRP, or a consolidation that is more than "export and add". Do not buy it as a stepping stone. Migrations between the two platforms are projects, not upgrades.
Choose Finance & Operations when the group is the product
Multi-country groups. Manufacturing with real MRP. Financial services with sub-ledgers that must post under rules. IFRS overlays, lease accounting, and a chart that has to serve more than one statutory book. Nine of our seventeen ISVs are built here because that is where those problems live: payroll, disbursements, leasing, mining, oil and gas, the accounting hub.
F&O is also where a global template survives. Legal entities, consolidation, Electronic Reporting and a real ALM path are native. Business Central can imitate parts of that. It should not be asked to be the group system of record for a rollout that will cross into Europe.
How we decide in the first workshop
We count legal entities you will have in three years, not the ones you have today. We list the integrations that post, not the ones that "might". We ask who produces IFRS, and whether local tax can change without a developer. If two of those answers point at F&O, we say so before you buy licences.
The expensive mistake is a partner who implements the product they are certified on. We implement both, and we publish products on both. The recommendation is yours to challenge. It will not be a licence we are trying to place.
One partner either way
Whichever platform you choose, the failure mode is the same: a local build that cannot accept the next country. The template, the statutory pack and the refusal to hard-code tax are the work. The product is the container.
If you are about to choose, or you have already chosen and the second country is starting to hurt, that is the conversation. We will tell you which platform, and we will stay to roll it out.