MS Dynamics Guys home

Hire Microsoft Dynamics 365 experts

Hire Microsoft Dynamics 365 developers and consultants

In short

MS Dynamics Guys provides Microsoft Dynamics 365 developers and consultants who join your team. This page matches the work waiting in your backlog to a role, and shows where each role's work ends. We assess each specialist before you meet them. You decide who joins, and your lead directs the work. The product matters as much as the role: Microsoft Dynamics 365 Business Central needs different skills from a customer relationship management (CRM) app such as Microsoft Dynamics 365 Sales.

Describe your team gapSee how we assess specialists

Which specialist closes the gap in your team?

Find the row that sounds like your team. The last column shows when a different role is the better hire.

Microsoft Dynamics 365 team gaps and the role to start with
If your gap isStart withChoose another role when
C# plug-ins, custom APIs (application programming interfaces), form scripts or Power Apps component framework (PCF) controls are waiting in your CRM backlogA Microsoft Dynamics 365 CRM developerMost items are forms, views, business rules or security roles: configuration work for a CRM consultant.
Nobody runs the workshops that compare your processes with the standard CRM apps, configures the apps or prepares user acceptance testingA Microsoft Dynamics 365 CRM consultantThe process is agreed and the remaining items need code. Then hire a CRM developer.
Leads, opportunities, pipeline stages or forecasts in Microsoft Dynamics 365 Sales no longer match how your team sellsA Microsoft Dynamics 365 Sales consultantThe gap is outside sales, for example in case handling. Start with a Customer Service consultant or a CRM consultant.
Case handling, queues or routing in Microsoft Dynamics 365 Customer Service no longer match how your service desk worksA Microsoft Dynamics 365 Customer Service consultantThe gap is in leads, opportunities or forecasts. Start with a Sales consultant.
Extensions in AL, the Business Central programming language, are waiting: new fields and pages, reports, integrations or fixes before the next major updateA Business Central developerThe change is setup, posting groups or a Word or Excel report layout that users with the right permissions can add. A Business Central consultant handles that.
Finance setup, posting groups, dimensions, inventory processes or migration checks in Business Central have no ownerA Business Central consultantThe requirement needs new tables, pages or event subscribers. That needs an AL developer.
A consultant is missing, but you cannot say whether you need a functional consultant, a technical consultant or an architectA consultant: compare the three types firstYou already know the product and the process. Go to the consultant page for that product.
One business process spans canvas apps, cloud flows and Dataverse tables, and someone must govern the environmentsA Power Platform developerThe work is one app or one set of flows. A Power Apps or Power Automate specialist is a closer match.
Canvas or model-driven apps need to be built, repaired or made fasterA Power Apps developerThe app is a Microsoft Dynamics 365 CRM app with plug-ins behind it. That is CRM developer work.
Cloud flows fail without alerts, run under a former employee's account or need approval stepsA Power Automate developerA rule must apply while a Dataverse record is saved. Cloud flows run only after the save. First check whether a business rule with table scope can enforce it. If not, a CRM developer writes a synchronous plug-in.
Power BI report totals, models or refresh jobs need work, and your lead can set priorities and review changesA client-directed Power BI developerStandard reports already meet the need, or you want a provider to run an ongoing managed reporting service.
Decisions about apps, data, security and integrations have no owner, and teams build on different assumptionsA solution architectThe design is settled and the backlog is delivery work. Add developers or consultants instead.
Interfaces between Microsoft Dynamics 365 and other systems fail, and nobody owns the fixAn integration engineerThe interface is new and fully specified, and you want a supplier to own the result. Buy it as an integration project instead of a role.
Data must move from an old system, with mapping, trial loads and reconciliationA data migration engineerYou want a supplier to own the whole migration and its acceptance. A migration project fits better.
Extensions in X++, the programming language of finance and operations apps, are waiting in Microsoft Dynamics 365 Finance or Supply Chain ManagementA finance and operations developerThe open questions are about finance or warehouse processes. A functional consultant for that product comes first.
Finance or supply chain processes in Microsoft Dynamics 365 Finance or Supply Chain Management have no owner, from the period-end close to warehouse workA Finance consultant or a Supply Chain Management consultantThe requirement needs custom code. Add a finance and operations developer.
A Microsoft Dynamics NAV system runs customizations in C/AL, the NAV language, and needs maintenance or a plan to move to Business CentralA Dynamics NAV developerYou want a supplier to own the whole upgrade to Business Central. That is an upgrade project, not a hire.

Many gaps need two roles, often a consultant and a developer. Without someone who owns the process, a developer builds exactly what was asked, and that may differ from what the business needs.

Role pages for Microsoft Dynamics 365 specialists

Each page explains the work a role can own, how we assess it and how an engagement starts. A page appears here only when MS Dynamics Guys offers what it describes.

One specialist, several roles or a result you hand over

On this site, an outsourced developer works for another company but joins your team, and your lead directs the work. In an outsourced project, the supplier directs the work and answers for the result. Count the rows of the first table that match your gap, and check who on your side can lead them:

  • One row matches. Add one specialist who works under your lead. This arrangement is called staff augmentation.
  • Two or more rows match, and your lead can direct each person. Write a separate role brief for each role. We assess each person on their own, and you interview each one.
  • The work is one result with clear edges, not a stream of tasks. Buy it as a development project with a written scope, not as a hire.

Who directs the work?

When a specialist joins your team, your side directs the work. Your lead sets priorities and accepts finished work. Each role also needs a counterpart on your team, such as a code reviewer or a process owner. The next table names them for each role, in the column Needs from your team.

MS Dynamics Guys does not run a second backlog next to yours. Microsoft Dynamics 365 staff augmentation explains what we answer for as the supplier.

If nobody on your side can lead the work, adding people moves the problem without solving it. Staff augmentation versus project outsourcing compares who decides what when the supplier leads the work instead.

Where functional and technical roles meet

Delays in a Microsoft Dynamics 365 team often start at a hand-off between roles. Titles vary between companies, so compare the work in each row. The split applies whoever supplies the people.

How work divides between functional and technical Microsoft Dynamics 365 roles
RoleWorks onDeliversNeeds from your team
Functional consultantHow each business process runs in the app: workshops, setup, configuration and the scripts users follow in acceptance testsConfigured processes, test scripts, short guides for key tasks and a record of process decisionsProcess owners who decide how the business works and who run the acceptance tests
Technical consultantThe technical setup of a workstream: environments, security roles, data import templates, integration settings and the specifications developers build fromEnvironment and security setup, import templates, integration settings and developer specifications, plus code only when the role brief says soAgreed requirements, administrator access outside production and design decisions from your lead or architect
Developer (CRM, Business Central, Power Platform)Code and low-code builds where configuration stops: C# plug-ins on Dataverse, AL extensions in Business Central, and canvas apps and cloud flows on Power PlatformReviewed code and solution files in your repository, automated tests where the platform supports them, and release notesWritten requirements, a code reviewer and a person who approves releases
Solution architectDecisions that cross apps, data, security and integrations, and reviews of other people's designsDesign decisions with their reasons, design reviews and a list of technical risksA person or board on your side with the authority to approve design changes
Integration engineerData that moves between Microsoft Dynamics 365 and other systems: interfaces, middleware, error handling, monitoring and reconciliationInterface specifications, integration code, alerts and a procedure for failed messagesOwners of the other systems, and a decision on which system owns each record
Data migration engineerMoving data out of an old system: profiling, mapping, trial loads, reconciliation and cutoverMapping documents, load scripts, reconciliation reports and a cutover checklistBusiness owners who sign off the reconciled data and decide how much history to move

Rework often starts at one of two hand-offs. A consultant writes a requirement that a developer can only build by guessing. Or a developer builds an integration before anyone decides which system owns the data. Before work starts, agree who writes each specification and who signs it off.

Copy the row for each role you add into its role brief, then replace the last column with names from your team. An outside specialist then knows where their work ends and whom to ask.

How a role brief becomes a shortlist

A role brief is a short description of the gap in your team. These steps show how we check it and, if we can staff the role, turn it into a shortlist of assessed candidates. No step has a fixed duration, and this page promises no shortlist date. Timing depends on the role and on the candidates we can assess.

  1. You describe the gap

    Tell us the product, the work that is waiting and who will direct it.

  2. We check the brief with you

    We ask about anything unclear, and we may suggest a different role, or a project instead of a hire. Then we tell you in writing whether MS Dynamics Guys can staff the role, and on what assumptions.

  3. We match people to each role

    We look for people who have done this kind of work on this product. Each role brief gets its own search, so a gap that needs two roles gets two shortlists.

  4. Each candidate is assessed for the role

    The task depends on the role and the product, for example a code review for a developer. How we assess specialists explains the task for each role, who reviews it and what an assessment cannot show.

  5. You receive a written summary

    For each candidate, we write down what we tested, where the candidate was strong and which gaps your interview should probe. Only candidates who passed the assessment reach the shortlist.

  6. Your interview decides

    You interview each candidate in your own format and decide who joins. If nobody fits, tell us what was missing. We correct the brief with you before the search continues.

Contracts and access follow your decision.

Microsoft Dynamics 365 staff augmentation explains onboarding and how the specialist then works inside your team.

Which role would MS Dynamics Guys suggest if you cannot name it yet?

We suggest a role from the work itself, not from the title you started with. We sort each backlog item or ticket you send by what it needs first:

  • A decision or a setting. A process rule that nobody has agreed, or the setup of standard features, points to a functional consultant for that product.
  • Code. Work that configuration cannot do points to a developer for that product.
  • A choice across systems. A question such as which system owns customer data points to an architect, or to your own design lead.

The largest group names the first role to consider, and the next group names the second. We reply with a proposed role brief for each role. It states the product skills, the work the person would own and what stays with your team. If the items are unclear, we may ask for a short screen-share of your environment. Suggesting a role needs no access to your production data.

Sometimes the answer is not a hire. If most items are small changes to a live system, a support service may suit you better. If a standard feature, a Microsoft Marketplace app or another provider meets the need, we say so.

When MS Dynamics Guys fits

MS Dynamics Guys fits teams that run Microsoft Dynamics 365, know which work is waiting and want specialists inside their own process.

A good fit when

  • A named person on your side will direct each role you add, with a reviewer or process owner to check the work.
  • Your CRM apps on Dataverse need a developer for plug-ins, custom APIs or custom controls.
  • Your CRM processes need a consultant for workshops, configuration and test preparation.
  • Your Business Central extensions need an AL developer.
  • Your Business Central setup, finance processes or migration checks need a functional consultant.
  • Your apps and flows on Power Platform need a developer who also takes care of environments and ownership.
  • You can list the waiting work as backlog items or problems, even if you cannot name the role yet.

Choose another route when

  • You want to recruit a permanent employee for your payroll. MS Dynamics Guys supplies specialists under a services agreement instead.
  • You want to browse available people before anyone has described the work. We introduce candidates only for a defined role.
  • Nobody can describe the work yet, not even as backlog items or problems. A short consulting engagement can define it first.

Questions about hiring Microsoft Dynamics 365 specialists

Can one specialist cover two Microsoft Dynamics 365 products?

Sometimes, when the products share a platform. Microsoft Dynamics 365 Sales and Customer Service both run on Dataverse, and so do model-driven Power Apps. A developer who knows Dataverse can often work across them.

Business Central is a separate product. Its code is AL, not C#, and it connects to Dataverse through an integration. Do not assume that strength in one product carries over to the other. We assess each product separately and tell you which one a candidate passed.

Sometimes the real need is the link between the two products, such as Microsoft's standard integration between Business Central and Microsoft Dynamics 365 Sales. List that link as its own item in your brief. Setting up the standard integration is mostly configuration, but deciding which system owns each record is a decision for your side.

Within Power Platform, one developer can often cover apps, flows and Dataverse tables together. The Power Platform developer page compares that generalist with a specialist in one tool.

Can we hire remote or dedicated Microsoft Dynamics 365 developers?

Both words describe the working arrangement, not a different role. A dedicated developer spends the agreed hours on your work only. A remote developer works from outside your offices, inside your repository, backlog, chat and meetings.

The share of time, the working hours and the overlap with your time zone are agreed in writing for each engagement. Put your time zone and the hours you need covered in the brief. We confirm whether we can meet them before any introduction.

What should we prepare before the first call?

Bring examples of the work, not a job description. We can name the role with you on the call.

  • Five to ten real backlog items, support tickets or problem descriptions, with personal and confidential data removed.
  • The Microsoft Dynamics 365 products and versions those items touch, and whether each runs online or on-premises.
  • Who on your side decides how each process should work, who reviews technical work and who approves releases. If nobody holds one of these jobs, say so, because that gap can change the role you need.

Your hours, time zone and security rules complete the role brief.

How is this different from recruiting a Microsoft Dynamics 365 developer or hiring a contractor?

A recruiter finds a person for you to employ. A freelance contractor signs a contract with your company directly. With MS Dynamics Guys, your company signs a services agreement with ours, and the specialist works in your team under that agreement.

Microsoft Dynamics 365 staff augmentation explains how that business-to-business arrangement works day to day.

If you might want to employ the person directly later, raise it at the start, because the agreement has to cover it.

Is a Microsoft Dynamics 365 engineer different from a developer?

Often they are the same job with a different title. On this site, a developer writes product code, such as C# for Dataverse or AL for Business Central. An engineer title marks a separate discipline with its own deliverables: integration, data migration, testing or release work. Each discipline needs its own assessment, so name it in your brief rather than relying on the title.

What if the role we need is not on this page?

Ask anyway, and describe the work rather than the title. A role page appears only when MS Dynamics Guys offers that role. A missing page usually means we do not offer it at present, and we tell you that plainly so you can look elsewhere.

Older products such as Dynamics NAV, Dynamics AX and Dynamics GP are a separate decision for each product and version. Name the exact version in your brief.

Describe your team gap

Send a few lines about the gap and the work that is waiting. We reply with the role we would suggest and whether MS Dynamics Guys can staff it, before any introduction.

Describe your team gapDiscuss a project instead

Product documentation referenced on this page