Selection criteria
What makes a good Microsoft Dynamics 365 partner.
Six levers that in our experience decide between smooth implementations and expensive learning loops. When comparing multiple Microsoft CRM partners, ask exactly these questions. The criteria are vendor-neutral, so you can use them to gauge any partner's answers.
01 · Depth of practice & platform history
How long has the partner been working with Microsoft CRM technology?
Microsoft Dynamics 365 emerged from Dynamics CRM in 2016 — which itself has been developed since 2003. Partners who have worked with the earlier versions (Microsoft CRM 3.0, 4.0, 2011, 2013, 2015) and with on-premises installations have lived through two decades of platform history: data-model breaks, cloud migration, the app-module split, Power Platform, Copilot. That history shows later in architecture decisions that must still hold five years after go-live.
02 · Software-development depth
Can the partner build software in general — or only configure D365?
Standard customizing rarely suffices for resilient implementations. A partner with real software-development depth delivers pro-code extensions on Power Platform, Azure Functions integration, custom .NET apps — and can develop outside the Microsoft stack when the project demands it. Pure out-of-the-box configurators hit the ceiling quickly when requirements exceed D365's built-in tooling.
03 · Industry understanding
Does the partner understand your business — or must you explain it?
Industry experience shortens the discovery phase by weeks. A partner who knows member management for associations, course billing for training providers, or field-service dispatching in industry from three running projects asks qualified, detailed questions instead of presenting generic best-practice slides.
04 · Process maturity & delivery methodology
Repeatable quality — or does the outcome depend on the individual consultant?
Consistent implementation quality emerges from documented delivery processes, not from individual talent. A partner with established process methodology can describe architecture-review procedures, sprint structures, hyper-care handovers, and Application Care transitions transparently — and delivers comparable quality project after project. Ask for the delivery handbook or quality-management system.
05 · Pre-built modules & add-ons
Productized solutions reduce time-to-value
A partner who operates their own ready-made add-ons on Microsoft Dataverse (vertical solutions, licence tools, adoption helpers) saves you weeks of customizing and delivers proven architecture instead of greenfield risk. Look for concrete products with customers in live operation — not for hypothetical "we could build that too" lists.
06 · Partner size & accountability
Who decides on escalations — and how far away is management?
At large Microsoft generalists, you negotiate in sales with senior architects and often receive a junior or offshore team in delivery. At smaller boutique partners, the same individuals stay active pre- and post-contract, escalations reach management quickly, and accountability does not disappear between hierarchy layers. The right size depends on your project — personal reachability matters more than absolute company size.
These six points are market standard for good selection diligence. The next section shows where arades GmbH delivers credibly against each one.