How it works
Understand. Document. Support.
Three simple steps, and continuous support.
Most support arrangements start with a handover meeting and a shared folder of documents. We start with the system itself. Here's what happens, step by step.
Understand
We build a complete picture of your environment before we touch anything.
We apply our intelligent tooling to your Dataverse environment and to the code base behind it — plugins, custom workflows, scripts, portals and anything else that has been added over the years. Alongside that, we map the systems connected to Dynamics: integrations, portals, websites and custom code that reads or writes your data. The result is a picture of the whole estate, not just the parts inside Dataverse.
What you receive is a written review. It sets out what is in your system, how portable it is, and every gap, risk and issue we find, with a recommended path to fix them, in priority order. Where components belong to a former partner rather than to you, we say so, and we say what the licence position means for you.
Nobody on your team has to sit through long discovery workshops or dig out old design documents. If they exist, we will read them. If they don't, we'll ask for anything we need to fully understand your system.
Document
We catalogue everything in your system as it is today, not just what was in the original design.
Documentation is retrofitted from the live system, not from memory. It covers the data model, the plugin and integration map, the security model, form logic, and the reasoning behind decisions made years ago by people who have since moved on. Where a reason can't be recovered, we record that too, so the next person knows it is an open question rather than a settled one.
Every page is reviewed by a consultant before it reaches you. It is written for the people who will actually use it: your administrators, your analysts, your next developer, and us.
This is where the loop in the diagram comes from. Every fix, enhancement or upgrade we make updates the documentation as part of the same piece of work. It never drifts out of date, because keeping it current is not a separate task that competes for time. And it is yours, from day one.
Support and remedy
Then we run with it.
Support starts proactive. Because we have reviewed your environment, we know where it is fragile, so we raise the issues we find before your users hit them, explain what it will take to put right, and fix them.
Every change we make is covered by automated regression testing that uses the system exactly as your users do, so a fix in one place doesn't quietly break something elsewhere. A by-product of that testing is a set of short walkthrough videos for the scenarios your users struggle with. They cost you nothing extra and are refreshed whenever the system changes.
Day to day, that means fixes, enhancements, upgrades, and the things you'd never get round to. Where your system depends on proprietary components you don't own, we re-implement them as code that is yours, so nothing in your estate is held hostage to a supplier you no longer work with.
Where most organisations start
With the review described in step one. It stands on its own: a written account of your estate and a prioritised plan, whether or not you go any further with us.
Talk to us about your system
Tell us what you have and where it hurts. You'll hear back from a consultant, not a bot.
- info@d365-support.com
- Phone
- +44 (0)1865 648551