No. We support systems built by other partners and internal teams too. We start with a structured onboarding and health assessment to understand the architecture, configuration, and any existing issues before we take responsibility for it. That process takes two to four weeks depending on system complexity, and it's what allows us to support the environment properly rather than learning it reactively.

Microsoft releases updates to Dynamics 365, Power Platform, and Azure services on a regular cycle. We subscribe to release notification channels, review update notes for impact on your specific configuration, test in a non-production environment, and deploy to production on a schedule that minimizes disruption. You're informed before updates go live, not after.

Incident volumes and resolution times by priority, open issues and their status, platform update activity, system performance metrics against baseline, and any capacity or configuration recommendations from the month's monitoring. The report is designed to give you a clear picture of system health without requiring you to ask.

Yes -and it's a common pattern. Organizations often start with block hours to cover a defined enhancement backlog or post-go-live period, then move to a shared or dedicated model once the ongoing support scope becomes clearer. We structure the commercial model to make that transition straightforward.

For systems we build -whether that's a Dynamics 365 implementation, a data platform, custom applications, or an integration layer -support is structured from the project phase rather than treated as a separate conversation after go-live. Monitoring configuration, runbooks, and support handover documentation are part of every delivery engagement, which means the transition to managed support is clean rather than a knowledge reconstruction exercise.