Mukesh Sharma
Two-decade engineering career across enterprise architecture, MSP-stack automation and AI. Sets technical direction across all four practices.
Xentek exists because the MSP automation market is full of Power-Automate-flows-held-together-with-hope and short on engineers who'll wear the on-call rotation when those flows fail. We're an engineering-led MSP — we treat ConnectWise webhooks, Graph API calls and Huntress alert pipelines like the production code they actually are. Tests. Version control. Observability. A human on the other end of the page.
The four practices — PSA · RMM, Microsoft 365 · Graph, security pipelines, custom MSP software — sit under one roof on purpose. Most MSP problems live in the seam between two vendor APIs. A team that ships across all four is a team that doesn't shrug when the seam shows up.
No partner-to-delivery-centre handoff. The engineer who scopes your stack is the same engineer in the repo, in the standup and on the page when something misbehaves at 2am.
Two-decade engineering career across enterprise architecture, MSP-stack automation and AI. Sets technical direction across all four practices.
Twelve years of engineering work across enterprise architecture, MSP-stack automation and AI — alongside Mukesh from the start. Owns the automation practice.
Leads delivery across active engagements — sprint planning, code review, and on-call ownership.
Halifax holds engineering and customer engagements. Toronto runs consulting and sales engineering. Delhi covers MSP automation and after-hours queues. The handoff is the point.
Engineering, platform builds and customer engagements. The room where the architecture gets argued.
Consulting, sales engineering and stack reviews. The first conversation usually happens here.
MSP automation build-out and after-hours coverage. When the Halifax team logs off, this team picks up.