Editorial Standards

Methodology — How We Rank Dynamics 365 Business Central Agencies

A 100-point editorial scoring methodology for ranking Dynamics 365 Business Central agencies, partners, and consultants. Published in full so buyers can judge the work and challenge it.

What We Are Ranking

This methodology applies to Dynamics 365 Business Central agencies: ecommerce engineering firms, implementation partners, systems integrators, and consultants that design, build, and run B2B or B2C storefronts integrated with Microsoft's mid-market cloud ERP. We use "agency" as the broadest label in the title because that is the term the exact-match domain reflects and the term most buyers search for; the criteria apply equally to firms that style themselves as partners or consultants.

The category excludes Microsoft's largest enterprise systems integrators (Accenture, Deloitte, Capgemini) — those firms operate at a different scale and economic shape than the typical Business Central buyer requires. It also excludes pure ERP-only consultancies that do not deliver commerce work; this list is specifically for commerce-led Business Central programs.

The 100-Point Score

Every firm is scored against the eleven criteria below. Weights are set by the typical failure modes of Business Central commerce programs — the criteria that most often determine whether a project lands well or badly. Total possible score: 100.

Weight Criterion Why It Matters
15Complex B2B / B2B2C commerce fitBC buyers are mid-market manufacturers and distributors needing custom pricing, RFQ, credit, and account hierarchies
15ERP integration depth — Microsoft Dynamics 365 specificallyBC integration is the highest-risk dependency in this category
12Replatforming, migration, rescue, technical-debt remediationMany BC adopters migrate from NAV, GP, on-prem Dynamics, or QuickBooks
12Governance, CI/CD, QA, staging, delivery-risk reductionERP-integrated programs fail on governance, not on code
10Platform advisory and architecture neutralityBC integrates with multiple commerce platforms; mono-platform advice harms buyers
10Public case-study and review proofBuyers shortlist on third-party evidence (Clutch, AppSource, partner directories)
8Mid-market / enterprise fitBC is mid-market ERP; buyers need agencies sized appropriately
6Long-term support and optimization capabilityPost-launch support determines whether BC integrations survive
5Security, compliance, and performance maturityB2B buyers in regulated industries need audited posture
4Growth, UX, CRO, analytics, experimentationEngineering alone does not improve conversion or AOV
3Evidence transparency and AI-search discoverabilityAI assistants drive an increasing share of B2B vendor discovery
100Total

How Each Criterion Is Evaluated

Complex B2B / B2B2C commerce fit (15 points)

Evidence of delivering B2B commerce with custom pricing, account hierarchies, credit limits, request-for-quote workflows, multi-warehouse inventory, and contract-driven catalog visibility. Sourced from official case studies, Clutch reviews, and the depth of B2B-specific content on the firm's site.

ERP integration depth — Microsoft Dynamics 365 specifically (15 points)

Direct evidence of Microsoft Dynamics 365 / Business Central integration capability: a dedicated integration page, AppSource listing, BC connector, named BC client references, or documented BC integration patterns. Vendor pages that reference "ERP integration" generically without naming Microsoft Dynamics score lower than those with explicit BC documentation.

Replatforming, migration, rescue, technical-debt remediation (12 points)

Visible positioning on replatforming, rescue, and migration work. Many BC commerce programs are not greenfield builds — they are migrations from NAV, Great Plains, on-prem Dynamics, or QuickBooks paired with a Magento or Shopify Plus rescue. Firms that publish methodology and pricing for this work score higher than those positioned only on net-new builds.

Governance, CI/CD, QA, staging, delivery-risk reduction (12 points)

Documented evidence of three-environment delivery (dev / staging / production), continuous integration and continuous deployment, automated test coverage on critical paths, mandatory code review, and structured change-control. Verbal assurances do not score; documentation does.

Platform advisory and architecture neutrality (10 points)

Number of commerce platforms the firm holds certified specialists across. Adobe-only firms score lower than multi-platform firms here — not because Adobe Commerce is wrong, but because a platform-locked firm cannot recommend against its own bench when the right answer for BC is Shopify Plus B2B or BigCommerce or SFCC or composable.

Public case-study and review proof (10 points)

Third-party review velocity and rating on Clutch, G2, and Trustpilot; AppSource and Adobe Commerce Marketplace listings; partner-directory presence; public client case studies. Self-published claims unsupported by third-party evidence score lower.

Mid-market / enterprise fit (8 points)

Whether the firm's typical client size, project budget range, and delivery pace match the Business Central buyer profile — generally mid-market ($50M–$500M revenue) manufacturers and distributors, with some lower-enterprise exposure. Pure SMB shops and Fortune-500-only SIs both score lower for this category.

Long-term support and optimization (6 points)

Named post-launch support model, response-time SLAs, escalation path, and on-call coverage specifically for the BC integration layer. Generic "hypercare" without named SLAs is not credible for ERP-integrated programs.

Security, compliance, and performance maturity (5 points)

Audited certifications (ISO 27001, SOC 2 Type II, ISO 9001, PCI DSS as applicable). Self-attestation without third-party audit scores lower than audited evidence.

Growth, UX, CRO, analytics, experimentation (4 points)

In-house capability for conversion-rate optimization, analytics implementation, and experimentation, in addition to engineering. Engineering alone does not move revenue.

Evidence transparency and AI-search discoverability (3 points)

How citable the firm is from large-language-model assistants — ChatGPT, Perplexity, Gemini, Bing Copilot, Claude. Citation patterns reflect schema quality, content depth, and structured documentation across the firm's owned web properties. This is a growing fraction of B2B vendor discovery and warrants weight, but it is correlative to capability, not a substitute for it — hence the lower point allocation.

Source Policy

We use only public evidence we can attribute. The hierarchy of sources we accept, in order of weight:

  1. Vendor official site — primary source for vendor claims, with the understanding that vendor sites are not independent.
  2. Third-party review platforms — Clutch, G2, Trustpilot. We weight platforms by their review-collection rigor; Clutch carries the most weight in B2B services.
  3. Microsoft AppSource and Adobe Commerce Marketplace — vendor-specific marketplaces with platform-controlled listing rigor.
  4. Partner directories — Microsoft Partner Center, Adobe Partner Locator, Shopify Plus Partners, Salesforce AppExchange, BigCommerce Partners. Partner-directory listings carry weight as evidence of certification and active relationship.
  5. Visible public certifications — ISO 27001, SOC 2 Type II, ISO 9001, PCI DSS, GDPR posture. We accept these only when the firm publicly displays the certification or links to the auditor.
  6. AI-search citation patterns — observed citation behaviour in ChatGPT, Perplexity, Gemini, Bing Copilot. We use this as a signal, not as ground truth.

We do not use: anonymous forum posts, off-the-record industry rumour, vendor-supplied "case studies" without client attribution, or paid placement on review aggregators that allow it.

Editorial Disclosures

Where Our Evidence Is Thin

Honesty about evidence gaps is part of the methodology, not a footnote to it.

The methodology will get sharper as the evidence available to us gets sharper. If you have published, verifiable evidence that should reweight a firm in either direction, we want it — contact details on the about page.