Choosing a D365 Partner: A Process-First Scorecard That Works

Here's one of my favourite trends in the Dynamics 365 world: the partners winning the best deals are increasingly the ones who understand how their clients' businesses actually run. Not the cheapest licence quote, not the slickest demo, but the team that walks in already speaking the language of a food manufacturer, a housing association or a wholesale distributor.

That's great news for anyone who loves the craft of consulting. It rewards curiosity, industry knowledge and genuinely caring about the client's outcome. It also means more of your working week is spent with clients and colleagues solving interesting problems, which is the best part of the job. Here's what process-first really means, what the evidence says, and how to build a career around it, whether you work for a partner or you're choosing one.

What "process-first" actually means

A process-first partner starts with how the business works and what it needs to improve, then shapes the technology around that. In practice, that tends to look like:

• Industry reference processes they can walk a client through on day one.
• Consultants with real sector experience, not just product knowledge.
• Fit-gap workshops that challenge "we've always done it this way" in a friendly, constructive way.
• A bias towards standard functionality and away from heavy customisation.
• Change management and training treated as part of the project, not an afterthought.
• Measurable outcomes agreed up front, like days to close the month or order to cash time.

The opposite is the "system install" approach: gather requirements, configure to spec, go live, hand over. It can work, but clients increasingly expect more.

What the evidence says

Clients are focusing on key processes

Panorama Consulting's 2025 ERP Report found 61% of organisations were pursuing what it calls ERP implementations, focused on stabilising core business processes, up from 50.4% the year before. More than half improved key business processes, rather than trying to improve everything or nothing. The median project timeline was nine months, down from 15.5 months in the previous report, which Panorama links partly to SaaS adoption (Panorama Consulting, press release). Commentary on the report notes the growing availability of pre-configured industry templates may be part of the reason (iStart).

Worth noting that the Panorama sample is fairly small, 172 organisations, mostly large ones. But the direction is clear: targeted, process-led projects that deliver value quickly.

The problems clients face are process problems

When Nigel Frank asked people working at Microsoft partners about the challenges their clients face moving to Dynamics, the top answers were:

• Data mapping and migration from legacy systems, 38%
• Lack of in-house technical knowledge, 37%
• Lack of change management on the client side, 35%
• Underestimating the time needed to replace the legacy system, 32%
• User adoption, engagement and training, 31%

(Nigel Frank)

Not one of those is fixed by a better licence discount. They're fixed by partners who understand the client's processes, people and data. Panorama makes a similar point about change management, noting that fewer than a third of organisations reported an intense focus on it.

Microsoft builds its method around it

Microsoft's own Success by Design framework for Dynamics 365 implementations is built around reviewing the solution against the customer's business goals and processes at each stage. Process-first isn't a partner marketing gimmick. It's how Microsoft wants its products implemented.

Investors are paying for it

In the partner M&A market, DynamicsFocus reports that vertical IP and advanced specialisations are commanding real valuation premiums (DynamicsFocus). When the people buying partners pay more for industry depth, you know it's valued.

How to spot it in the first meeting

You can usually tell within an hour whether a partner thinks process-first. Good signs include:

• They ask more questions than they answer, and the questions are about your business, not your server estate.
• They bring someone who has worked in or with your industry.
• They talk about your month end, your order cycle or your service levels before they mention a single module.
• They're happy to say "you don't need that customisation, here's how standard handles it".
• They ask who in your team will own the change, and how much time they'll have.
• They talk about what happens six months after go live, not just on the day.

Less encouraging signs are a demo that could have been shown to any company, a proposal that arrives before anyone has understood your processes, or a team that changes completely after the contract is signed.

A scorecard for judging a partner

Whether you're a client choosing a partner or a consultant choosing an employer, here's the scorecard I'd use. Score each from one to five.

Industry depth

• Do they have several live clients in your sector?
• Can they name the sector-specific processes and regulations without notes?
• Do they have industry templates, accelerators or ISV partnerships?

People

• Will the consultants in the sales meeting be on the project?
• How many years of sector experience does the proposed team have?
• What certifications do they hold, and are they current?

Method

• Do they run process workshops before writing a statement of work?
• How do they handle gaps: standard first, then Power Platform, then customisation?
• Is change management and training built into the plan and budget?

Data

• Do they have a clear data migration approach and tooling?
• Who owns data cleansing, and when does it start?

Outcomes

• Will they agree measurable success criteria?
• Can they share references who'll talk about results, not just go lives?

Stability

• Who owns the partner, and how has headcount changed?
• What's their consultant turnover like?

A partner who scores well on industry depth, people and method will usually beat a cheaper one that doesn't, because the cost of a project that misses its goals dwarfs any saving on day rates.

What it means for your career

This is the exciting bit for consultants. The market is rewarding exactly the things that make consulting fun.

Pick a sector and fall in love with it

Whether it's manufacturing, distribution, professional services, not-for-profit or financial services, getting genuinely good at one industry makes you the obvious person to put in front of those clients. Read the trade press, go to the industry events and learn the jargon.

Get great at workshops

The consultant who can run a lively, structured process workshop, draw the current and future state on a whiteboard and gently challenge a client's assumptions is worth a lot. Practise it. Ask to shadow the best facilitators in your team.

Learn the commercial side

Get involved in pre-sales. Helping shape a solution in front of a prospect is how you learn what clients value, and it's one of the quickest routes to senior roles.

Speak in outcomes

Instead of "I configured fixed assets", say "I helped the finance team cut month end from eight days to four". Clients and hiring managers remember outcomes.

Embrace the AI layer

Process knowledge is what makes AI useful. Agents in Business Central, Copilot in Finance and Copilot Studio agents all need someone who understands the process they're automating. Consultants who know their sector and the new tools are going to have a wonderful few years, because they'll be the ones designing how work gets done in the AI era rather than watching from the sidelines.

Building sector knowledge this month

You don't need years to start building industry depth. Here's a simple plan for the next few weeks:

• Choose your sector. Ideally one you've already worked in or enjoyed a project with.
• Subscribe to two trade publications and read them every week.
• Map the five core processes for that industry on a page, with the typical pain points in each.
• Learn the regulations that shape those processes, like food traceability, housing regulation or financial reporting rules.
• Find the ISVs that serve that sector in the Dynamics world, and get a demo of at least one.
• Join an industry event or user group and listen to what clients complain about over coffee.
• Write it up. A short LinkedIn post or internal briefing on what you've learned makes you the go-to person surprisingly fast.

It's genuinely enjoyable work, and it compounds. Every project in that sector makes you better at the next one.

Questions to ask in your next interview

If you're interviewing with a partner, use the scorecard in reverse:

• Which industries do you focus on, and how many clients do you have in each?
• How do you run discovery and fit-gap?
• How much of a typical project is standard versus customised?
• How do you handle change management?
• How would I build sector expertise here?

The answers tell you a lot about whether you'll be doing thoughtful, process-led work with great people, or just configuring to spec.

What to do next

• Look for sector-focused partner roles on our jobs board.
• See what industry specialists earn on our salaries page.
• Highlight your sector experience in the consultants directory.
• Research partners and their industry focus on our employers page.