- The ask for a local partner is usually a fear of being stranded after go-live, not a real need for physical proximity.
- Business Central is SaaS in Microsoft's cloud, so day-to-day support is remote screen-shares, tickets, and calls, handled as well from across the country as across town.
- On-site is an event you schedule, like a kickoff or quarterly visit, and shouldn't be the criterion that picks your partner.
- What actually prevents getting stuck is a defined support model and real training so the knowledge lives in your company, not one consultant's head.
Yesterday, a CEO who joined a Business Central demo midway through pushed back on one thing harder than anything else: he wanted a partner "down here," close by, for both the build and the support afterward. "I just want to make sure we don't get stuck with something we don't know how to use, or nobody can manage," he said.
It's a completely reasonable worry. It's also usually aimed at the wrong target.
The geography ask is really a fear
When a non-technical owner asks for a local partner, the real question underneath is: who's my safety net after go-live? The fear isn't distance. It's being handed a system and left alone with it. Geography just feels like the answer because "someone nearby" sounds like "someone who'll show up."
How cloud ERP support actually works
Here's what's really going on. On-site presence for implementation and go-live is common, and it gets scheduled and priced in. But ongoing support for a cloud system is overwhelmingly remote, and not because partners are cutting corners. Business Central is a SaaS (software-as-a-service) product that lives in Microsoft's cloud. There's no server in your closet for anyone to drive out and touch. Day-to-day support is screen-shares, tickets, and quick calls, which a partner across the country handles exactly as well as one across town.
On-site is an event you schedule, like a kickoff or a go-live, not a person who needs to sit nearby. If having someone in the building on a regular cadence matters to you, that can be arranged as a scheduled quarterly visit. It just shouldn't be the thing that picks your partner.
What actually prevents "getting stuck"
The real protection against the CEO's fear isn't a zip code. It's a defined support model and real training, for current staff and for the people you hire later, so the knowledge lives in your company and not just in one consultant's head. The safety net is the relationship and the documentation, not the drive time.
One related tip from that same call: make sure the person who will actually own the system day to day, usually your controller or operations lead, is in the demos. On this one, that person had to be pulled in live, halfway through. The buying committee should include the people who'll live with the choice.
If you're weighing implementers and worried about being left high and dry, that's worth talking through honestly, including what "support" really looks like for a cloud system. We're happy to walk you through how it works. Let's talk it through.