Business Central Consultant & Consulting Services

We work as the Business Central consultant for small and mid-sized manufacturers and distributors, either leading an implementation or picking up a system that went live and never got finished.

• Implementation and phased go-live planning
• Process mapping before configuration
• Item setup, units of measure, BOMs and routings
• Purchasing, vendors and receiving workflows
• Warehouse locations, bins and pick/put-away flows
• Production orders and shop floor consumption posting
• Finance, posting groups and dimension design
• Multi-location and multi-entity configuration
• Migration from legacy ERP, Dynamics GP or QuickBooks
• Integrations to shipping, EDI, CRM and line-of-business systems
• Power BI reporting on Business Central data
• End-user training and post-go-live support

Most Business Central projects that disappoint were sold as software installs. The questions that actually predict success are about process and sequencing, not feature lists.

• Ask who documents your current process, and whether that happens before configuration
• Ask how the rollout is phased — a single big-bang cutover is a warning sign
• Ask who owns item, BOM and inventory data cleanup, and when it happens
• Ask how dimensions will be designed for operational reporting, not only accounting
• Ask who supports the network, Wi-Fi, identity and licensing the ERP runs on
• Ask what happens after go-live, and for how long
• Ask for anonymized examples of comparable work rather than logos

The software is rarely the problem. Implementations struggle when the current process was never documented, when item and BOM data is inconsistent, when dimensions are designed for accounting alone, and when the plant is asked to change five workflows on the same Monday.

Phasing matters. Purchasing and receiving stabilized first, then inventory accuracy, then production, then reporting — each phase with people trained on the part they touch.

Business Central runs on the network, the identity platform and the devices we already manage. Scanners need Wi-Fi that holds in the aisles. Users need Entra ID accounts, MFA and licensing. Reporting needs data anyone can trust.

Most consultancies stop at the application boundary and most MSPs stop before it. Understanding both sides is why our ERP work tends to land.

Consulting is scoped per project rather than sold as a fixed package, because the range between a clean single-location rollout and a multi-entity manufacturer with legacy data is large. Cost is driven by how many modules go live, how much data cleanup is required, how many integrations are involved, and how much training the team needs.

Microsoft licensing is separate from consulting and billed per user. We put scope in writing before work starts.

We describe project work in anonymized form unless a customer has approved being named. Nothing on this site presents an invented customer, statistic or outcome.