Dynamics 365 and Power Platform Experts in Yerevan: A Buyer’s Guide

Why "where is the team" is a real question

When a mid-market company or a Microsoft partner goes looking for Dynamics 365 and Power Platform help, the shortlist usually collapses into three shapes: a global systems integrator, a local generalist, or a specialist consultancy that does this and little else. The brand names get most of the attention, but the thing that actually decides how the project feels day to day is far more boring: what time zone is the person doing the build in, how senior are they, and can you reach them when something breaks.

Solzet works from Yerevan, Armenia, and that geography is not a footnote. Armenia sits in GMT+4, which gives roughly 6 to 8 hours of daily working overlap with the UK and Ireland and a comfortable adjacent-time-zone relationship with the rest of Europe. For a team in Dublin or Manchester running Dynamics 365, that overlap is enough for a real standup, a live sprint review, and a stakeholder workshop over Teams - not an email you send at 5pm and read the answer to the next morning. We work on B2B contracts and speak Russian, English, and Armenian, which also makes local delivery inside Armenia and the wider Caucasus straightforward rather than an exception.

What we actually build (and what we deliberately do not)

We focus on the Dynamics 365 Customer Engagement apps and the Power Platform, and we are honest about that boundary. On the Dynamics 365 side that means Sales, Customer Service, Field Service, and Customer Insights on Dataverse: data modelling, security roles, business process flows, plugins and business rules, and the integrations to your ERP, telephony, email, and BI tools. On the Power Platform side it means canvas and model-driven Power Apps, Power Automate cloud and desktop flows, and Power Pages portals, all sitting on the same Dataverse as the CRM. Where the standard controls run out of road, we extend the UI with custom PCF components written in TypeScript and React rather than forcing users to live with an awkward form.

What we do not do is the Microsoft ERP and finance side - Business Central, or Finance and Supply Chain Management. That is a deliberate line. A consultancy that claims to do everything usually means a different set of people show up for each thing, and the depth is uneven. Keeping to Customer Engagement and the platform around it is how the same engineers who scoped your project are the ones who build it.

The work nobody plans for: fixing a mess

A large share of what we do is not greenfield at all. It is taking over a Dynamics 365 environment that another partner built and that is not delivering. If you have searched for a company that specialises in fixing messed up Dynamics implementations, that is a real category of work, and the instinct that matters most is what happens first.

Our answer is an audit, not a rebuild. Starting again from scratch is the expensive, disruptive option that a lot of firms reach for because it is easier to sell than to untangle someone else’s decisions. Instead we document the technical debt, the data quality problems, and the customization choices that are causing pain, then propose a remediation roadmap that fixes the highest-impact issues first while production keeps running. Sometimes the biggest problem is not technical at all - it is that people have quietly stopped using the system. A CRM that users route around with spreadsheets is a failed system whatever its config looks like, so rescuing adoption across the business is its own workstream: simplifying forms, removing friction with targeted Power Apps and flows, and adding the reporting managers actually asked for.

Field Service deserves a specific mention because it is one of the hardest Customer Engagement apps to get right and one of the most common to stall. Recovering a Field Service rollout usually means going back through work order and booking configuration, resource scheduling and the schedule board, the technician mobile app, and the integrations to inventory and finance that get skipped on a rushed first attempt. We have written about how these rollouts go wrong, and you can see the shape of a full recovery in our field service case study.

A due-diligence checklist for choosing a partner

Whether you end up working with us or not, the same questions separate a partner who will deliver from one who will hand your project to a junior team after the pitch. Before you sign anything, work through this:

- Ask which specific Microsoft certifications the engineers who do the build hold, not the sales team. For this stack, look for PL-200, PL-400, and PL-600, plus MB-210, MB-230, and MB-240. - Confirm that senior people stay on through delivery, rather than the work being handed down once the contract is signed. - Check the real time-zone overlap with your working hours - how many hours a day you can actually reach the team live. - Ask how they handle a troubled project. Do they insist on a rebuild, or do they audit first and remediate in priority order? - Review the contract for IP ownership, an NDA, and a GDPR-compliant data processing agreement before any data changes hands. - Ask what happens after go-live: is there a support package, and who owns the source code, solutions, and documentation? - Request references relevant to your app - Sales, Customer Service, or Field Service - not a generic capability deck.

After go-live is not an afterthought

The reason those last two questions matter is that most of a system’s life happens after launch. We provide continuous support for organizations running Dynamics 365 and the Power Platform, scaled from a part-time consultant of around 20 hours a month up to a full managed-service team. In practice that is new Power Automate flows as processes change, Power BI reporting on Dataverse, PCF upgrades, day-to-day user support, and applying Microsoft’s twice-yearly release waves before they break something. On a B2B engagement the boundaries are written down: a mutual NDA, a GDPR-compliant data processing agreement, and IP that belongs to your organization or your end client as defined in the statement of work. For Microsoft partners who bring us in as a white-label subcontractor, our consultants work under your brand and keep your end clients off their public profiles.

If you want a candid read on your current Dynamics 365 estate - whether that is a fresh implementation, a rescue, or ongoing support - that straight answer is what our services are built to give.