Our ERP software has failed. Who do we call now?

You do not need an emergency call, but a first conversation. When a Business Central project is off balance, it is not the fastest vendor that helps, but someone who takes over senior, records the current state soberly and speaks plainly. The first step is a calm conversation about what really happened, not hectic activism.

What happens in the first conversation?

When an ERP project tips over, the first reflex is understandable: get somebody quickly who will fix it. But you do not fix a project in trouble with speed, you fix it with experience. The call that changes something is not an emergency call to a provider who starts immediately. It is a first conversation with somebody who understands before they act at all.

In an honest first conversation we speak plainly. Where does the project really stand, in scope, data, processes and responsibility? What is viable and must be secured, what is the actual break? That is practitioner language, not consultant rhetoric. After the conversation you should see more clearly, not be more impressed.

A good sign, incidentally, is when the person opposite asks more than they explain. Whoever offers a finished solution after twenty minutes has not understood the situation but has a standard offer ready.

What does senior takeover mean in concrete terms?

Someone sits at the table who knows off-balance situations and can assess them, not a changing junior team that first gets up to speed while the clock runs. In an off-balance situation, experience decides, not capacity. This person stays, takes responsibility, and also says the uncomfortable things early.

In practice, experience here means recognising patterns. Whether a date slips because of missing capacity, an unclarified scope or a governance that cannot decide shows in different signals, and the three causes need entirely different answers. Confusing them costs further months.

The counter-check is simple and belongs in the first conversation: have the person named by name, ask about two comparable situations this person led themselves, and have them tell you how both turned out, including the one that did not end well.

What explicitly does not happen?

What matters is what we do not do: we do not take over your project and disempower you. Control stays on your side, with Business Central as our home ground. We proceed in order:

• First we secure what exists: data, configuration and knowledge.
• Then we record the current state soberly.
• Only then do we re-establish control.

The first point is the one most often skipped and the most important. In a project in trouble, knowledge is the most volatile resource: people move on, access expires, the reasoning behind decisions disappears. Whatever is not secured now has to be reconstructed expensively later.

That is the difference between a genuine handover and yet another switch to a team without senior ownership. Do not call the one who says yes fastest. Arrange a first conversation in which somebody senior listens, records the current state and tells you honestly what holds.