Rapidly Scale Your Dynamics 365 Team: Staff Augmentation and Subcontracting
For the partner who has won the work and cannot staff it, and for the team whose senior Dynamics 365 Customer Engagement lead is leaving in three weeks.
If you have an awarded Dynamics 365 project and a resourcing gap that starts now, this is how Solzet fills it. We provide senior Dynamics 365 Customer Engagement and Power Platform consultants into your delivery team in one of two ways: white label, under your brand and your email as a subcontractor to your Microsoft partner business, or directly, as augmented capacity inside your own team. The people are senior only, certified, and the ones who talk to you on the first call are the ones who do the work. The vetting cycle is compressed by talking to engineers instead of a sales layer, by standard contracting paperwork rather than a bespoke negotiation, and by an optional fixed-price pilot work package that lets you judge us on your own backlog before you commit to a quarter. Roles we are asked for most urgently are the senior Customer Engagement lead, the Dataverse and plugin developer, and the PCF engineer.
The short answer
- What you get. Named senior consultants in Dynamics 365 Customer Engagement, Sales, Customer Service, Field Service and Customer Insights, plus Dataverse, Power Apps, Power Automate, Power Pages, plugins, integrations and PCF controls. Certifications across the team include PL-200, PL-400 and PL-600 on the Power Platform and MB-210, MB-230 and MB-240 on Dynamics 365. No juniors placed behind a senior profile.
- How they join. White label as a subcontractor, working under your brand, your email and your documentation templates in front of your end client. Or directly as staff augmentation inside your own team, in your Azure DevOps or GitHub, your Teams channels, your definition of done. The commercial relationship stays business to business either way.
- How fast. The parts we control are measured in days: a technical call with the engineer who would do the work, named profiles against your role brief, a mutual NDA and a data processing agreement from standard templates, and a small first work package that can start while the wider agreement is still being papered. The parts you control, tenant access, licences, your own security review and any end client approval your prime contract requires, are usually what set the real start date.
- What we will not do. Tell you a senior Customer Engagement lead is sitting idle waiting for your call. We assemble delivery pods from a network of senior Microsoft specialists rather than carrying a large idle bench. If the right person is mid engagement we say so on the first call and tell you when they free up, instead of substituting somebody weaker and hoping you do not notice.
If what you need is the contracting model in full, the white label boundary, the minimums and the intellectual property terms, that lives on our Dynamics 365 subcontracting and white label service page. This page is about the week you are in now.
The four situations that make this urgent
Nobody searches for staff augmentation in the abstract. These are the four versions of the problem we are actually called about, and the right engagement shape is different in each one.
You won the deal and the bench is already committed
A Microsoft partner signs two implementations in the same month and has the consultants for one of them. Turning the second one down costs the revenue and the relationship, so the delivery gap gets filled from outside. This is the most common reason partners come to us, and it is the case white label subcontracting exists for: our consultants appear to your end client as members of your team, and the client sees your brand throughout.
Your lead has resigned in the middle of a build
The person who held the data model, the security roles and the reasoning behind half the configuration is leaving in three weeks. Recruiting a permanent replacement takes a quarter you do not have, and a contractor who needs six weeks to understand the solution is not a replacement either. What you need is somebody senior enough to read an existing Dataverse solution, the plugin registrations and the environment strategy, and be useful in the first sprint.
The go live moved and the plan no longer fits the team
A date got pulled forward, a phase two became phase one, or discovery found twice the integration work anybody scoped. The team is not wrong, it is simply the wrong size for the new plan. Adding capacity to specific workstreams, integrations, migration, custom controls, is usually cheaper and faster than renegotiating the date, and it is easier to unwind afterwards.
One phase needs a skill nobody in the team has
The build is fine until the requirement lands that needs TypeScript and React inside a model driven app, a plugin that has to behave correctly under a bulk import, or an integration with real transaction volume. Hiring permanently for one phase does not pay back. This is the shape of the engagement in our case study with a UK Microsoft Solutions Partner, where two of our senior developers delivered eight custom PCF controls inside their delivery team over three months.
The wider argument about why partners subcontract at all, and how to structure it so it protects margin and the client relationship, is in our post on why Microsoft partners subcontract D365 work.
Two ways the same people join you
The consultants, the rates and the legal terms are identical across both. The only question is whose brand faces the end client.
White label subcontracting, under your brand
For Microsoft partners and systems integrators. Our consultants use your email addresses and your communication channels, deliverables and documentation carry your branding, they join client meetings as members of your team, and your end clients do not appear on their public profiles. The commercial relationship is between your organisation and Solzet only: you bill your client at your rates and you pay us at ours. You keep the client relationship, the accountability and the margin, and you take on work you would otherwise have to decline. The full contracting model, the minimums and the intellectual property terms are on our Dynamics 365 subcontracting page.
Direct staff augmentation, inside your own team
For organisations running Dynamics 365 themselves. Our consultants join your team under their own names, work in your Azure DevOps or GitHub, your Teams channels and your environments, attend your standups and sprint reviews, and are managed by your delivery lead against your definition of done. You are adding senior capacity to your own effort rather than outsourcing a deliverable, so the direction stays with you. Where you would rather hand over a defined outcome instead of a seat, we scope it as a fixed price work package instead.
The roles we are asked for
Listed in the order they turn up as urgent gaps rather than alphabetically. Every one of them sits inside Dynamics 365 Customer Engagement and the Power Platform, which is the only thing we do, and which is why a consultant can be useful in your first sprint rather than your fourth.
Senior Dynamics 365 Customer Engagement lead
The role behind most urgent requests. Owns the functional design and the technical shape of a Customer Engagement build: the Dataverse data model, security roles and business units, the model driven apps, business process flows, the boundary between configuration and code, and the environment and solution strategy. Runs workshops with the business, writes the design decisions down, reviews what the rest of the team builds, and is senior enough to say no to a requirement that will cost more than it returns. On a rescue this is the person who reads what is already deployed before anybody writes new code.
Dynamics 365 Customer Engagement functional consultant
Configures and documents Sales, Customer Service, Field Service and Customer Insights on Dataverse: entities and relationships, forms and views, business rules, queues and routing, service level agreements, work orders and scheduling, journeys and segments. Runs requirement workshops, writes user stories against the actual configuration, and handles user acceptance testing and the training that follows. Certifications on the team include MB-210, MB-230, MB-240 and PL-200.
Dataverse and plugin developer
The code side of a Customer Engagement build. Plugins and custom APIs in C#, asynchronous workflow activities, server side logic that has to stay correct under a bulk data load, and the performance work that follows when a synchronous step lands in the wrong pipeline stage. Also the person who knows why a rollup field, a calculated column, a business rule and a plugin are four different answers to what looks like one requirement. Typically PL-400 certified.
PCF and front end engineer
Custom PowerApps Component Framework controls in TypeScript and React, packaged as managed solutions, tested across browsers, documented for whoever maintains them next. This is a scarce skill inside most Dynamics teams and one of the most common single skill gaps we are called for. Our documented delivery of this shape is eight controls for a UK Microsoft Solutions Partner, built inside their Azure DevOps with their pull request review process.
Power Platform and integration engineer
Power Automate flows that survive contact with production, Power Apps canvas and model driven work, Power Pages portals, and the integrations that connect Dynamics 365 to the rest of the estate through Dataverse APIs, custom connectors, service bus and webhooks. Includes the unglamorous half of the job: error handling, retries, idempotency, and knowing what happens to the flow when the upstream system is down for an hour.
Solution architect
For a programme rather than a project. Environment and licensing strategy, tenant design, the application lifecycle management pipeline, integration architecture, data migration approach, and the governance that keeps a growing Power Platform estate from becoming unsupportable. PL-600 certified. Often engaged part time alongside a full time lead rather than as a full seat.
Application lifecycle and environment engineer
Solution based deployment with the Power Platform command line interface and Azure DevOps or GitHub pipelines, managed solution layering, environment strategy from development through test to production, and the discipline that stops manual export and import from quietly becoming your release process. Frequently the first thing an incoming lead asks for on a project that has been running without it.
Support and hypercare consultant
For the weeks after a go live, when the build team is being released and the issues are arriving. Triage, fixes, small enhancements, release wave updates, and the day to day user support that otherwise lands on the one person who cannot afford the interruption. Runs at part time capacity from around twenty hours a month upward.
If the gap is specifically a PCF developer and you are weighing a freelance marketplace against a dedicated team, that comparison is made in full in hire PCF developers: in house team against freelancers. If you are building a lasting Power Platform capability rather than covering a phase, read building a Power Apps centre of excellence with a nearshore team.
How onboarding runs when the start date is now
Eight steps, and the useful thing about them is which ones we control. Steps one, two, three, six and seven are ours and move in days. Step four moves in days if your legal team is working from a redline rather than a blank page. Step five is yours, and it is usually the one that sets the real start date, which is why it should begin on day one rather than after signature.
- 1
Send the role brief, not a request for a capability deck
Tell us which apps are involved, what stage the build is at, which roles are missing, what the start date and the end date look like, and whether the work is white label under your brand or direct inside your own team. If you have a statement of work or a backlog, that is better than a job description. What we do not need is a discovery call to establish whether we do Dynamics 365, and what you should not need is a two week qualification process before you speak to anybody technical.
- 2
Talk to the engineer, not to a sales layer
The first call is with a consultant who would be on the engagement, and it goes both ways. We ask what is actually deployed, what the environment and solution strategy looks like, what the integration surface is, and where the project is genuinely stuck. You ask whatever you need to judge whether this person can hold your build. If the fit is wrong, that call is where it should end, and we would rather it ended there than after a month of paperwork.
- 3
Get named profiles against the brief, with the constraints stated
We come back with the specific people we would put on it, their Dynamics 365 and Power Platform background, their certifications, and their real availability including anything they are still finishing. If a role cannot be filled at the seniority you asked for by the date you asked for, that is in the same message rather than discovered in week three. You can interview anybody proposed, and the person you interview is the person who starts.
- 4
Paper it from standard templates, in parallel with everything else
A mutual non disclosure agreement, a business to business services agreement, a GDPR compliant data processing agreement, and a statement of work that defines scope, rates, invoicing, intellectual property ownership, confidentiality and non solicitation. We work from standard templates that have been through other buyers legal reviews, so the usual path is a redline rather than a drafting exercise. Contracting runs alongside the technical steps rather than blocking them.
- 5
Provision least privilege access to the environments
Our consultants work in your tenant, through guest accounts you create and can revoke, with the security roles the work actually needs and multi factor authentication and conditional access as your policy requires. We do not need production access to start on most workstreams: a development environment, the solution, and read access to the backlog is enough for the first days. This is the step that most often sets the true start date, so start it early and in parallel.
- 6
Run a first work package that produces something reviewable
The first commitment does not have to be a quarter. A scoped work package, a set of controls, a migration slice, a workstream in the backlog, priced fixed or as a short time and materials block, gives you a deliverable to judge in weeks rather than a reference to trust. It also surfaces the things that only show up in real work: how your review process feels from the inside, whether the environments are as documented, and whether our estimates hold on your codebase.
- 7
Ramp on the existing solution instead of waiting to be briefed
A senior person joining an in flight Dynamics build should not be idle waiting for documentation. In the first days we read the solution layers and what is unmanaged in production, the plugin and flow registrations, the security model, the integration endpoints, the backlog and the open defects, and we come back with what we found, including the parts that contradict the documentation. That read is useful to you even if the engagement stops there.
- 8
Set the review rhythm and the exit conditions on day one
Your standups, your sprint reviews, your definition of done, your repository, your pull request process. We also agree at the start what handover looks like at the end: code in your repository, documentation in your format, decisions written down, and a notice period that lets you unwind capacity without an argument. Augmentation that cannot be reversed cleanly is not flexibility, it is a dependency.
Which weeks of vendor vetting are real
A standard supplier onboarding takes six weeks because of eight separate steps, and only some of them protect you. The table separates the ones worth keeping from the ones that exist because that is how the process was drawn. We are honest in it about the two rows we cannot shorten at all.
| Step | Why it normally takes weeks | What happens here instead |
|---|---|---|
| Qualification and discovery calls | Two or three meetings with account managers before anybody technical appears, each one re establishing facts the previous one already covered. | The first call is technical and it is with somebody who would be on the engagement. There is no separate qualification stage to get through. |
| Capability and reference checking | A capability deck, a reference programme, and a set of case studies that describe outcomes without describing the work. | A published case study of the same engagement shape, a technical conversation deep enough to expose whether the person has done this before, and a first work package that shows you the work itself. |
| Profile submission and interviews | Anonymised profiles, then a substitution at the point of contract, then interviews with people who may or may not be the ones assigned. | Named people with their real availability, interviewed by you if you want, and the person you interview is the person who starts. No substitutions after signature without your agreement. |
| Master agreement negotiation | A bespoke master services agreement drafted from scratch and passed between two legal teams for weeks while the delivery date does not move. | Standard business to business templates covering the non disclosure agreement, the data processing agreement, intellectual property, confidentiality and non solicitation. Usually a redline rather than a draft, and it runs in parallel with the technical steps. |
| Your security and vendor risk review | A questionnaire, a review board, and a queue. Genuinely necessary, and entirely inside your organisation. | We cannot shorten this one, but we can start it on day one instead of week three, and we answer the questionnaire from documents we already maintain. Where a review board has a fixed cadence, that date is usually the real start date. |
| Tenant access, accounts and licences | Guest accounts, security roles and licence assignment handled by a team that has other priorities, discovered as a blocker on the first morning. | We send the exact access list at the point of the role brief so provisioning can run alongside contracting. Most workstreams can start in a development environment without production access. |
| End client approval of a subcontractor | Buried in a prime contract clause and found late, then handled as an exception under time pressure. | We raise it at the start, because it is a common clause. Our default posture is white label and invisible, and we will sign whatever confidentiality and non solicitation terms your client contract obliges you to pass down. |
| Knowledge transfer into the existing build | A month of shadowing before the new person produces anything, priced as productive time. | A senior consultant reads the solution, the registrations, the security model and the backlog directly, and reports what is actually deployed. Useful output in the first days rather than after the handover meetings. |
The honest summary of that table is that we can compress our half of the process to days, and that your security review, your provisioning queue and any end client approval clause are what actually decide when somebody starts. A supplier who quotes you a start date without asking about those three has not thought about your organisation at all.
Engagement models, and the fixed price pilot
Three models, and the third one is the answer to the hardest problem in urgent staffing: how do you commit to a supplier you have known for a week. A fixed price work package scoped as a pilot gives you a deliverable to judge instead of a reference to trust, and it converts into either of the other two models afterwards without renegotiating the legal framework.
| Model | Best for | Typical minimum | How it is billed |
|---|---|---|---|
| Dedicated resource | A named consultant on your project for a defined period, typically three to twelve months. Continuity, deep context and predictable capacity, which is what a lead role needs. | Around three months at half time, eighty hours a month. | Monthly, against an agreed monthly capacity. |
| Time and materials | Ongoing support, defect work, enhancement backlogs and workstreams whose size is not yet known. Capacity flexes month to month. | No strict minimum, though we recommend at least forty hours a month so context is not lost between engagements. | Tracked and invoiced monthly against actual hours. |
| Fixed price work package | A defined deliverable: a set of PCF controls, a migration slice, an automation pack, a module configuration. Also the cheapest way to test a supplier before committing a quarter. | Whatever the deliverable is, once the scope is clear enough to price. | Fixed price against agreed acceptance criteria, invoiced on milestones. |
A pilot team is simply the smallest useful version of the pod: usually one senior consultant who owns the design conversation plus one developer, on a scope both sides can describe in a paragraph. If you are still weighing whether to run the work internally instead, our consultant against do it yourself decision guide costs the line items and is honest about when the internal route wins.
Vet us properly in one call: eight questions
Compressing a vetting cycle is not the same as skipping it. These eight questions get you most of the way in forty five minutes, they work on any Dynamics 365 supplier and not just this one, and every one of them is a question we would rather be asked early than late.
Is the person on this call the person who will do the work?
The single most useful question in urgent staffing. It separates a delivery team from a sales pipeline, and the answer is easy to verify in the next five minutes by asking something technical.
Can I interview the named consultant, and will they be the one who starts?
Profile substitution after signature is the classic failure of urgent staffing. Ask for the commitment explicitly and have it written into the statement of work.
What is the seniority floor, and who reviews their work?
A senior profile with a junior behind it is the other classic failure. Ask who does code and configuration review, and what happens when the consultant hits something outside their depth.
What can you actually start without production access?
Tests whether the supplier has thought about your provisioning queue at all. A supplier who cannot answer this will be idle and billing while your identity team works through its backlog.
Who owns the code and the documentation, and where does it live?
It should be your repository, your intellectual property, and your documentation format, stated in the statement of work rather than assumed. If the work only exists on the supplier side, you have bought a dependency.
What happens to the knowledge when the engagement ends?
Ask for the handover shape up front: written decisions, documented solution, a named person on your side who has been in the pull requests. Augmentation without handover quietly becomes a permanent cost.
What is the notice period, and how do I scale down?
Flexibility is the reason to augment rather than hire. If the exit terms are punitive, you have taken on the cost of a permanent hire without any of the benefits.
What are you not good at?
A supplier who has no answer has either not thought about it or is willing to say anything. Ours is on this page, in the section on where we are the wrong answer.
What goes wrong in urgent staffing, and what we do about it
If you have bought capacity under time pressure before, you have probably met at least two of these. They are worth naming, because the countermeasure for each one belongs in the statement of work rather than in a sentence on a website.
The profile and the person are not the same
A strong anonymised profile wins the contract and a weaker consultant arrives. Our answer is that the people are named before signature, you may interview them, and any change of person during the engagement needs your agreement. It is a term in the statement of work rather than a promise on a page.
Urgency is used to skip the boring paperwork
Under time pressure the non disclosure agreement, the data processing agreement, the intellectual property clause and the non solicitation terms get deferred and then forgotten, which is exactly the situation that hurts when something goes wrong. We paper the standard set before access is granted, in parallel with the technical steps, so speed does not cost you the protections.
Capacity arrives without direction and produces noise
Adding people to a project without a workstream to own produces coordination overhead rather than throughput. We ask what the added person owns end to end before they start, and if the honest answer is that nobody has decided, we would rather spend the first days on that than bill for attendance at your standups.
The knowledge leaves when the contractor does
The most expensive version of this is a build that only the departed contractor understood. Everything we write goes into your repository through your review process, decisions are written down as they are made, and handover is defined at the start rather than negotiated at the end.
The end client finds out through the back door
In a white label engagement, a consultant appearing on a public profile or emailing a client from the wrong address is a genuine commercial problem for a partner. Our default is your email, your templates, your brand, and end clients kept off our consultants public profiles, backed by the confidentiality terms in the agreement.
Who you are actually hiring
Solzet is a Microsoft Dynamics 365 Customer Engagement and Power Platform consultancy based in Yerevan, Armenia, founded in 2024 by senior practitioners with eight or more years each in the ecosystem. We implement Sales, Customer Service, Field Service and Customer Insights, build Power Apps, Power Automate and custom PCF controls, and take over implementations that have stalled. Capacity is assembled into a delivery pod per engagement from a network of senior specialists rather than drawn from a standing bench, which is why we can put strong people on a project quickly and also why we will tell you when a specific person is not free.
Certifications across the team include PL-200, PL-400 and PL-600 on the Power Platform and MB-210, MB-230 and MB-240 on Dynamics 365. The team works in English, Armenian and Russian. Armenia is UTC+4 with no daylight saving, which leaves roughly four to six hours of daily overlap with Western European hours and six to eight with the UK and Ireland, enough for standups, pairing, sprint reviews and joint client workshops inside your working day.
Engagements are business to business: a services agreement, a mutual non disclosure agreement, a GDPR compliant data processing agreement, and a statement of work covering scope, rates, invoicing, intellectual property ownership, confidentiality and non solicitation. Our consultants work in your tenant through guest accounts you create and can revoke, with least privilege roles and whatever multi factor authentication and conditional access your policy requires. Client data stays in your tenant, and code goes into your repository through your review process.
The documented delivery of exactly this shape is our PCF controls development for a UK Microsoft partner, where two of our senior developers joined the partner delivery team white label for three months. For the broader picture of who we are and how we work, see the company profile and our Dynamics 365 consulting and development service.
Where we are the wrong answer
You are deciding under time pressure, so the fastest thing we can do is rule ourselves out early where we should be. There are five situations where hiring us would be a mistake, and we would say so on the first call rather than after the paperwork.
You need a Dynamics 365 product outside Customer Engagement
We work on Dynamics 365 Customer Engagement, Sales, Customer Service, Field Service and Customer Insights, and on the Power Platform around them. If your gap is on the finance, supply chain or trade side of the Dynamics range, we are not the supplier for it and we will say so on the first call rather than sending a consultant to learn on your project.
You need people on site, or in a specific jurisdiction
Our consultants work from Yerevan. We join workshops, standups and client sessions over Teams, and that covers the great majority of Customer Engagement delivery, but if your contract requires people physically on site, security clearance in your country, or delivery from a named jurisdiction, that is a hard constraint we cannot meet.
You need a large team assembled next week
We assemble pods from a network of senior specialists rather than carrying a large idle bench, so a handful of senior people at short notice is realistic and a team of fifteen next Monday is not. If that is genuinely the requirement, a staffing firm with a standing bench is a better call than us, and you should expect the seniority to vary across the group.
You want a body shop billing hours against a rate card
We are senior only and we ask questions about the design, which is the point of hiring at this level and occasionally an irritation if what you wanted was silent throughput. If the requirement is the cheapest hands that can follow a specification exactly, our rates will not be competitive against suppliers who staff it differently.
What you actually have is a failing project, not a staffing gap
Adding people to an implementation whose design is wrong makes it later, not earlier. If the real situation is a stalled or overrun build, the honest first step is a diagnostic and a scope reset rather than three more seats, and we would rather sell you that.
On that last one: if the project is stalled, overrun or has lost its partner, the honest first step is a health check and technical audit or a rescue and takeover, not three more seats on a plan that is not working.
Frequently Asked Questions
We urgently need senior Dynamics 365 CE leads. How fast can Solzet actually start?
The steps on our side are measured in days rather than weeks: a technical call with the consultant who would take the role, named profiles with their real availability against your brief, and standard contracting templates covering the non disclosure agreement, the data processing agreement, intellectual property and non solicitation. In practice the start date is set by whichever of the following takes longest: your own security or vendor risk review, guest account and licence provisioning in your tenant, any end client approval your prime contract requires for a subcontractor, and the notice a specific consultant owes a current engagement. We tell you which of those is binding on the first call rather than quoting a start date we do not control, and we will not claim a senior Customer Engagement lead is sitting idle waiting for the phone to ring.
What is the difference between staff augmentation and white-label subcontracting here?
They are the same people under two different commercial arrangements. In white-label subcontracting you are a Microsoft partner or systems integrator, our consultants work under your brand and your email in front of your end client, and the contract is between your organisation and Solzet with no relationship between us and your client. In direct staff augmentation you are the organisation running Dynamics 365, and our consultants join your internal team under their own names, in your tooling, managed by your delivery lead. The engagement models, rates and legal terms are the same. Which one you pick depends on whose brand faces the end client. The contracting model in full is on our Dynamics 365 subcontracting page.
What does a senior Dynamics 365 Customer Engagement lead cover in your definition?
The functional and technical shape of a Customer Engagement build. The Dataverse data model, security roles and business units, model driven apps, business process flows, the boundary between configuration and code, and the environment and solution strategy. They run workshops with the business, write design decisions down, review what the rest of the team produces, and are senior enough to push back on a requirement that costs more than it returns. On an in flight or troubled project they start by reading what is actually deployed, the solution layers, the plugin and flow registrations, the security model and the integration points, before proposing anything new.
Can we test you on a small piece of work before committing to a full quarter?
Yes, and it is usually the fastest route through an urgent decision. We scope a defined deliverable as a fixed price work package, for example a set of PCF controls, a migration slice, an automation pack or one workstream from your backlog, with written acceptance criteria and milestone invoicing. You get something reviewable in weeks and a real view of how we work inside your review process, and we get a proper read on your environments and estimates before either side commits to a longer arrangement. If it goes well it converts to a dedicated resource or time and materials engagement without renegotiating the legal framework.
What is the minimum engagement, and how do we scale it back down?
For a dedicated consultant the practical minimum is around three months at half time, eighty hours a month, because a lead role needs continuity to be worth anything. Time and materials has no strict minimum, though we recommend at least forty hours a month so context is not lost between blocks. Fixed price work packages have no minimum beyond a scope clear enough to price. Scaling down is a notice period agreed in the statement of work, and we define handover at the start: code in your repository, documentation in your format, decisions written down. Augmentation you cannot reverse cleanly is a dependency rather than flexibility.
How do you protect our end client relationship if we are a Microsoft partner?
Our consultants use your email addresses and channels, deliverables and documentation carry your branding, they attend client meetings as members of your team, and your end clients do not appear on their public profiles. The commercial relationship exists only between your organisation and Solzet. Contractually that is backed by a mutual non disclosure agreement, a non solicitation clause, confidentiality terms we will match to whatever your client contract obliges you to pass down, and intellectual property assigned to your organisation or through to your end client as the statement of work defines. Our incentive is that you win the next deal, because that is where the next engagement comes from.
Which skills do you actually cover, and which do you not?
Dynamics 365 Customer Engagement, meaning Sales, Customer Service, Field Service and Customer Insights, along with Dataverse, model driven and canvas Power Apps, Power Automate, Power Pages, plugins and custom APIs in C#, integrations, data migration, application lifecycle management with the Power Platform command line interface, and custom PCF controls in TypeScript and React. Certifications across the team include PL-200, PL-400, PL-600, MB-210, MB-230 and MB-240. We do not cover the finance, supply chain or trade side of the Dynamics range, and we do not offer generic software development outside this ecosystem. The narrow focus is why a consultant can be useful in your first sprint rather than your fourth.
How does the time zone work for daily collaboration?
Yerevan is UTC+4 with no daylight saving, which leaves roughly four to six hours of daily overlap with Western European hours and six to eight with the UK and Ireland. That is enough for daily standups, pairing, sprint reviews and joint client workshops inside your working day rather than handing work over as a recording. For clients in the United States the overlap is the European morning against the American start of day, which works for a daily sync and for asynchronous review, and we say so plainly rather than pretending it is the same as being in the next room.
What contracts and data protection terms apply?
Every engagement is business to business: a services agreement, a mutual non disclosure agreement, a GDPR compliant data processing agreement, and a statement of work defining scope, rates, invoicing, intellectual property ownership, confidentiality and non solicitation. Our consultants access your systems through guest accounts you create and can revoke, with least privilege security roles and whatever multi factor authentication and conditional access your policy requires. Client data stays in your tenant. Solzet is a registered Armenian company and we invoice in euros, dollars or pounds by international transfer.
Have you done this before, or is this a new service line?
It is a large share of what we do. The documented example on this site is a UK Microsoft Solutions Partner that won a Dynamics 365 implementation and had no in house TypeScript and React capacity for the eight custom PCF controls the project required. Two of our senior developers joined their delivery team white label for three months, worked in their Azure DevOps with their pull request review process, delivered all eight controls as documented managed solutions, and the partner engaged us again on later projects. The case study is on this site with the technical detail.
Send the role brief
Tell us which apps are live or being built, which roles are missing, the dates, and whether the work is white label under your brand or direct inside your team. You will get a technical call with the consultant who would take the role, named profiles with their real availability, and a straight answer about which step sets your start date.