Which SAP Partner Is Right for SMEs?
Choosing an SAP Business One partner: four partner types with strengths and limits, seven verifiable criteria and when on-site visits really matter.
Whether an SAP Business One implementation succeeds depends more on the partner than on the software. The partner sells you the licenses, manages maintenance with SAP, sets up the system and then supports it for years. You do not change partners in passing. That is why the selection deserves more than a comparison of two quote totals.
This article classifies the typical partner types, including us, names seven criteria you can check in a conversation, and answers a question that comes up in almost every first meeting: how often does the partner need to be on site?
Four partner types
Very different companies are behind SAP Business One partners. None of the types is fundamentally better; they suit different starting situations.
| Partner type | Strengths | Limits | Fits if |
|---|---|---|---|
| Large IT service provider with several ERP products and many locations | capacity, backup, often hardware, network and Microsoft 365 from a single source as well | changing contact persons, smaller customers carry less weight | you have many locations, a large IT landscape or an international rollout |
| Specialized SAP Business One partner with a small team | short communication paths, consultants know your system, implementation and support from the same people | limited capacity for large parallel projects | you have between five and a hundred users and value direct support |
| Industry specialist with its own industry solution | deep industry knowledge, ready-made processes for your industry | tied to its own add-on, less experience outside the industry | your industry has requirements the standard does not cover |
| Freelance consultant | flexible, often affordable, a lot of experience | no license sales and no maintenance, no backup | you have a partner for licenses and maintenance and need additional capacity |
We belong to the second type: we are an SAP partner with more than ten people, based in Lehrte near Hanover with a company in Denmark, with our own add-ons and consulting in German and English. We are a good fit for SMEs that want a fixed circle of consultants who know their system. For a worldwide rollout with consulting in many local languages, we are not the right choice.
Seven criteria you can check
Good partners differ less in what they promise than in what they can prove. This table helps in the conversation.
| Criterion | How to check it | Warning sign |
|---|---|---|
| Partner status with license sales | listing in the SAP Partner Finder, authorization to sell SAP Business One | licenses are supposed to come via a third party |
| Experience specifically with SAP Business One | since when, how many customers, how many consultants dedicated to SAP Business One | SAP Business One is one product among many |
| Committed response times | in writing, graded by urgency, with a procedure for failures | only “fast” and “personal” without numbers |
| Clear prices before the project | fixed price or budget with a defined scope, data migration and training explicitly included | a large pre-project before there is a price |
| In-house development | own developers for add-ons, interfaces and validation rules, source code accessible to you | every customization goes to a subcontractor |
| Industry knowledge | two references from your industry that you are allowed to call | references only as a logo |
| Support after go-live | who provides support and whether they know the project | project team and support team have nothing to do with each other |
Ask the same questions in every conversation and write down the answers. Two answers are particularly revealing: how is a failure handled that blocks shipping? And what is not included in your quote? Anyone who answers concretely has experienced both before. Our own answers to the seven criteria are on the page Find an SAP Business One partner.
Implementation, switch or migration
Depending on your starting situation, what you should look for shifts. For a new implementation, what counts is a clear sequence, a fixed price with a defined scope and a partner who sets up your core processes stably first. What that looks like is described on the implementation page.
For a partner switch, what counts is takeover experience and a sober look at what the predecessor left behind. How a switch works and which contracts you need to check is described in switching your SAP Business One partner the right way. For a migration to HANA, what counts is technical depth, a test plan and experience with add-ons and custom developments.
When the partner should be on site
“Do you also come on site?” is one of the most common questions in the first conversation. The honest answer: sometimes, and then it matters. System analysis, customizing, interfaces, testing, troubleshooting and support are faster remotely. A question clarified remotely takes twenty minutes; an on-site appointment ties up half a day of travel. Remote work also leaves better traces: ticket histories and documented settings can be looked up.
Three moments are the exception:
| Moment | Why being there matters |
|---|---|
| Process discovery | How goods receipt, picking or production reporting really work is something you see standing next to it, not in a video call. Nobody mentions workarounds, because they seem normal to everyone. |
| Training | A room full of people working through their own documents achieves more than any recording. Acceptance within the team decides whether the system is used or bypassed after three months. |
| Week after go-live | When a document gets stuck while shipping is waiting, nobody writes a ticket. Someone who is within reach solves it in minutes. |
An on-site day is not free: travel time, travel expenses and a working day that rarely has eight productive hours. So bundle the appointments, schedule the training on two consecutive days and keep the support after go-live short and intensive. And make sure that the people who matter are there on those days. A consultant who talks to IT about warehouse processes during stocktaking is wasted.
Four points belong in the quote or the kickoff minutes before the project starts:
- Which appointments take place on site, and how many days are planned for them?
- Who bears travel time and travel expenses, as a flat rate or based on actual effort?
- How long does the support after go-live last, and what applies if it is extended?
- Which response time applies in case of a failure, and from when does someone come in person?
Proximity is not a main criterion, but it is a good tiebreaker. If one provider understands your processes significantly better, that decides it. If two quotes are equivalent in substance, the shorter distance is a real advantage, precisely in the weeks when things get turbulent. For companies in the Hanover region, the way to our office in Lehrte near Hanover is short; for everyone else, we deliberately plan in the three important moments.
How to make the decision
Invite two to three partners, not ten. Give all of them the same three to five process problems and have them show you how they solve them, in the system and not on slides. Compare the quotes by what is included, not by the total. Call the references. And pay attention to whether the person across the table stays clear when it comes to limits, risks and what is not in the quote.
If you are currently torn between SAP Business One and another system, the comparison SAP Business One vs Business Central and Navision will help.
Frequently asked questions
How do I find out whether a provider is an official SAP partner?
Does SAP Business One cost the same with every partner?
Is a large partner safer than a small one?
Does my ERP partner have to be located nearby?
What should the support quote include?
Updated on November 11, 2026