When Your ERP Partner Needs to Be On-Site

“Are you also on-site?” is one of the most common questions in the first conversation about an ERP project. The honest answer is: sometimes, and then it’s important. Most of the work on SAP Business One today is no longer done in the meeting room, and that’s not a loss of quality, it’s simply more efficient.

However, “everything remote” is just as unsuitable as a principle as “always someone on-site.” Both extremes cost money, just in different areas. This article describes which project phases run better remotely, in which three moments presence really changes the course, and how you can clarify both before the project starts, instead of discussing it later.

What Runs Better Remotely

System analysis, customizing, interfaces, test runs, troubleshooting, support: No one needs a chair in your office for that. On the contrary. Those who work remotely access the system directly, document changes cleanly, and can bring in a colleague in between without anyone having to get in a car.

The practical advantage lies in the timing. A question clarified remotely takes twenty minutes. The same question during an on-site appointment waits until the next appointment takes place, or it forces a trip that costs half a day on its own. Over a project, this adds up significantly, and it’s on your bill.

There is also an effect that many underestimate: Remote work leaves better traces. Screen recordings, ticket histories, and documented configurations are readable. What is verbally agreed upon in a meeting room exists afterward in multiple versions in the minds of the participants.

The Three Moments When Presence Counts

There are situations where screen sharing systematically shows too little. They are less frequent than sales presentations suggest, but they decide the project’s success.

The first is process recording. How goods receipt, picking, or production feedback actually occur is not in any organizational chart. It’s on the note someone has been keeping next to the screen for years because the old system doesn’t cooperate at this point. Such workarounds are not shared in a video conference because they seem normal to those involved. You see them when you stand next to them.

The second is training. A room full of people going through their own documents brings more than any recording. Questions arise where the work takes place, and the half-spoken remarks among colleagues are often more valuable than what is officially asked. Planning training only as a video conference is saving at the wrong end: Team acceptance determines whether the system is used or bypassed after three months.

The third is the week after the go-live. In this phase, speed is more important than process. If a document gets stuck while shipping waits, no one writes a ticket. Someone shouts across the hall, and whoever is available solves the problem in minutes. How you prepare for this phase is detailed in the Go-live Checklist.

What an On-Site Day Really Costs

Presence is not free, even if it sometimes looks that way in the offer. Count on three items: pure travel time, travel expenses, and the fact that a travel day rarely contains eight productive hours. For a service provider sitting 300 kilometers away, a day appointment is effectively a day of work plus half a day of travel, and both end up with you in some form.

This does not mean abstaining, but planning. Bundle on-site appointments. A process recording that covers all affected areas in one go is more valuable than three individual visits. Schedule training for two consecutive days instead of five scattered mornings. And keep the go-live support deliberately short and dense.

The calculation changes, however, when the distance is small. Someone sitting half an hour away can come by for two hours the next morning without it becoming a project item. This is the practical value of regional proximity: not in constant presence, but in the ability to react quickly and proportionately.

Presence Only Helps If Your Team Is Also There

The most common reason for a wasted on-site appointment is not the service provider. It’s because the people involved are missing. If the warehouse management is doing inventory that day and accounting is in the monthly closing, a consultant sits in your meeting room talking to IT about processes that IT does not manage.

Therefore, before each appointment, determine who from the department is involved and what decision-making authority this person has. This is where it becomes clear whether internal roles are clarified: Who can decide that an approval level is omitted? Who decides on article number logic? If these questions remain open during the appointment, every decision is postponed by a week. Which roles a project needs is detailed in Setting Up the ERP Project Team Correctly.

Conversely, this also means: A well-prepared half-day with the right people brings more than two full days with those who just had time. Feel free to ask your partner beforehand who they need. If they don’t have a clear answer, they haven’t thought through the appointment themselves.

Clarify It Before the Project, Not in the Middle

Most discussions about presence arise because no one talked about it beforehand. Four points should therefore be included in the offer or kickoff protocol:

• Which appointments take place on-site, and how many days are planned for them?
• Who bears travel time and travel expenses, and are they billed as a flat rate or based on effort?
• How long does the on-site support last after the go-live, and what happens if it needs to be extended?
• What applies in case of a disruption: What response time is promised, and at what escalation level does someone come in person?

The last point is most often overlooked and is the most important in operation. A promised response time of four hours is of little use if the answer is that an appointment is available in the week after next. Therefore, don’t just ask about the response time, but about the specific procedure in case of a problem that blocks shipping or invoicing.

How to Tell That Proximity Is Only Claimed

“Nationwide on-site for you” is on many websites. Three inquiries separate the statement from reality.

First: Where are the people who are doing my project located? Not the company headquarters, but the specific consultants. Some providers have many addresses, but the experts for your topic are at one of them.

Second: Do you work with subcontractors? This is not a disqualifier, but it changes responsibility and accessibility. You should know who is liable in case of doubt and who you call.

Third: Who supports the system after the go-live? If the project team and support team have nothing to do with each other, you explain your processes twice. In small teams, you usually reach someone who knows your installation. What other criteria count, we have compiled in Which SAP Partner Fits the Midmarket.

Proximity Is Not a Main Criterion, but a Good Tiebreaker

If you compare two providers and one understands your processes significantly better, that decides, not the distance. Professional fit, experience with your industry, and realistic project planning come before the postal code. Conversely, however, it also applies: If two offers are professionally equivalent, the shorter distance is a real advantage, especially in the weeks when things get hectic.

In the end, it’s less important how many kilometers lie between you than whether your partner honestly says when they come and when they don’t. Someone who wants to travel for every little thing is selling you travel time. Someone who never comes has never seen your processes. You only notice both in the project if you don’t ask beforehand.

We ourselves work mostly remotely and are based in Lehrte near Hannover, close enough for the appointments that matter. What this looks like specifically for companies in the Hannover region is on our location page, which is in German. For everyone else, the same principle applies: Plan the three important moments consciously on-site, and do the rest where it goes faster.