Why Businesses Struggle With ERP (and How Business Central Fixes It)

Reading Time: 3 minutes

After 30 years implementing ERP systems in factories and distribution companies across Greece and the UK, I can tell you something with complete honesty: most ERP projects fail not because the technology is bad, but because the approach is wrong.

I’ve seen it happen too many times. A company invests heavily in a new ERP system, expecting it to transform their business. Instead, they end up with overcomplicated processes, low user adoption, and data that nobody really trusts. The spreadsheets they were trying to escape from often come back in secret because the new system feels too heavy or too slow. The worst part is that everyone (finance, operations, and management) ends up frustrated and pointing fingers at each other.

The biggest mistake I see again and again is trying to implement everything at once. Companies want the “full system” live on day one, so they map every single process, customise heavily, and expect the entire organisation to change their way of working overnight. The result is usually chaos, resistance, and a system that people avoid using as much as possible.

Why Business Central Stands Out

That is exactly where Dynamics 365 Business Central stands out for me.

From the very beginning, Business Central was built with a different philosophy in mind. It feels familiar because it looks and works like the Microsoft tools people already use every day: Outlook, Teams, Excel. You don’t need weeks of training just to understand the interface. More importantly, it lets you start small. You can pick one painful process, get it working cleanly in BC, show real value to the business, and then expand step by step. That approach dramatically increases the chances of success.

I have watched teams move from complete spreadsheet chaos to real-time visibility and control in just a few weeks, not months or years. The difference is not that Business Central is magically perfect. The difference is that it doesn’t force you to change everything at once. It gives you the flexibility to implement at the pace your organisation can actually handle.

The Pattern Behind Successful Projects

The projects that succeed with Business Central usually follow the same pattern. They start with the areas that hurt the most right now: sales order processing, inventory accuracy, financial reporting, or production planning. They keep customisation to an absolute minimum at the beginning. They focus on getting the core data model right first. And they only expand once the first processes are stable and people are actually using the system.

This is why I genuinely believe Business Central is one of the smartest ERP choices for mid-sized manufacturing and distribution companies today. It doesn’t try to be everything to everyone from day one. It lets you grow with it.

A Story From Manchester

I remember one particular project in a medium-sized factory outside Manchester. They had been struggling with their old ERP for years. Instead of trying to replace everything at once, we started only with sales orders and inventory. Within six weeks they had accurate stock levels and much faster order processing. The confidence this gave the team made the rest of the rollout smooth and almost painless. That small, focused start made all the difference.

My Strongest Advice

If you are thinking about a new ERP or you are in the middle of an implementation that already feels heavy, my strongest advice is this: start small, deliver value fast, and expand gradually. That simple mindset shift is often the difference between another failed ERP project and one that actually transforms the business.

I’d love to hear your experience. What has been your biggest frustration with ERP systems in the past? Or if you are currently working with Business Central, what has surprised you the most, good or bad? Feel free to share. I read every comment and I’m always happy to compare notes from the field.