Extend your delivery capacity
Dynamics 365 delivery support for Microsoft partners and ISVs
Short answer
MS Dynamics Guys helps Microsoft partners, consultancies and ISVs add technical delivery capacity. Bring assessed specialists into your team, assemble a dedicated workstream team, or outsource an agreed development package. Your organization retains its client relationship. We define leadership, client communication, access and handover before work begins.
Add the skills your project is missing
| Skill area | Work to scope |
|---|---|
| CRM and Dataverse | Plug-ins, custom APIs, Power Apps component framework (PCF) controls, solution releases and functional configuration. |
| Business Central | AL extensions, reports, APIs, integrations and update testing. |
| Finance and Supply Chain Management | X++ extensions, data entities and technical work against approved functional designs. |
| Power Platform | Power Apps, Power Automate and Dataverse work within agreed governance. |
| Migration and integration | Mapping, trial loads, reconciliation, interface reliability and release handover. |
Match the skill area to your workstream. The proposed role, allocation and start date are confirmed for the engagement.
Choose the delivery responsibility
| Model | How the work is directed |
|---|---|
| Your team directs specialists | Use staff augmentation for capacity inside your existing backlog. Your lead assigns work, reviews changes and approves releases. You interview and select the proposed specialists. |
| A coordinated workstream team | Build a dedicated team with an agreed lead, allocation and review plan. Your organization keeps business priorities and acceptance; name who directs the daily work. |
| We deliver a work package | Use scoped delivery when the required result, interfaces and acceptance tests are clear. MS Dynamics Guys takes responsibility for that agreed package and its handover. Your wider client contract remains separate. |
A dedicated allocation, white-label presentation or specific non-solicitation terms can be discussed as part of the agreement. They are not assumed simply because an engagement uses external specialists.
Set boundaries that protect the client relationship
| Decision | Agree before onboarding |
|---|---|
| Client communication | Who joins client meetings, whose name is used and who can make commitments. |
| Scope changes | Who estimates, approves and informs the client. |
| Source and intellectual property | Repository access, ownership and third-party dependencies under the contract. |
| Security | Named accounts, permitted environments, least-privilege access and removal at exit. |
| Quality | Review rules, acceptance tests, release approvals and evidence required for a completed task. |
| Commercial terms | Allocation, rate basis, working hours, notice, replacement and handover. |
Start with one useful work package
A first package should be small enough to review and real enough to show how the teams work together. Examples include a tested AL extension change, a Dataverse plug-in fix or a documented integration repair. Agree the acceptance criteria before work starts. These are example scopes, not claims about completed client projects or a free-trial offer.
Use the review to assess code quality, communication, estimation and handover. Add capacity only when the next work and the responsibilities are clear.
What to include in your partner brief
Tell MS Dynamics Guys which Dynamics product you deliver, the backlog or work package, the roles needed, working-hour overlap and expected term. State who leads delivery and whether the specialist will meet your client. Share source code or client information only through an agreed access process.
Partner delivery questions
Does this page mean MS Dynamics Guys has a Microsoft partner designation?
No. This page describes services for Microsoft partners and other delivery companies. MS Dynamics Guys is an independent services company and does not claim a Microsoft partner designation on this site.
Can specialists work in our repository and tools?
Yes. Agree the repository, task system, access rules and review process during onboarding. Your lead controls the work in a staff augmentation engagement.
Can the engagement be white label?
Discuss the required presentation, client communication and contract terms with MS Dynamics Guys. White-label responsibilities must be agreed before the specialist joins client-facing work.
Can we start with a part-time role or a work package?
Share the allocation or deliverable you need. MS Dynamics Guys reviews the scope and availability, then confirms whether it can support the requested arrangement.
When your project pipeline exceeds your team
- A sold project needs AL, X++ or Dataverse development capacity that your current team cannot cover.
- A delivery phase needs a specialist alongside your functional consultants.
- Several client workstreams need shared technical leadership and a documented allocation plan.
- Your team wants to outsource a bounded component while retaining the wider client contract.
Use the team-and-budget planner to compare allocation assumptions.
White-label and subcontracted delivery
Tell MS Dynamics Guys how the specialist should appear to your client and what approvals your contract requires. Agree meeting participation, commitments, document branding, source ownership and any non-solicitation terms before client-facing work starts. White-label presentation does not change technical responsibilities or remove the need for client approvals.
Partner-led NAV migration staffing
The Ardent / Halden NAV-to-Business Central engagement was partner-led. MS Dynamics Guys supplied a C/AL developer and a separate data migration engineer.
Your next step
Add delivery capacity without losing clarity
Send the product, skills and work you need covered. We will help define the role or package and who owns each decision.