Multi-agent Claude Code teams that split design, front end, data and QA, with Supabase, Vercel and Playwright wired in over MCP and every change checked on a preview deploy.
For 25 years I've kept Citrix and virtual desktops running for banks, insurers and hospitals. Now I build with Claude and Microsoft Copilot: agents, agent teams, apps, and automation that has to work on a Monday morning.
Most teams run one, pilot the other, and need someone who understands the desktops, identities and workflows underneath both.
Multi-agent Claude Code teams that split design, front end, data and QA, with Supabase, Vercel and Playwright wired in over MCP and every change checked on a preview deploy.
Copilot Studio agents grounded in IT knowledge and actions, rolled out on the Citrix, AVD and Windows 365 desktops I already engineer, with Azure DevOps, branded custom-built DevOps alternatives and Azure Key Vault underneath for added security.
Golden images for Citrix PVS and MCS used to be patched by hand, client by client. I rebuilt the process as scheduled Azure DevOps pipelines: Windows and browser updates, BIS-F sealing and a QA hand-off, with each client isolated in its own variable groups and Key Vault.
Alongside the pipelines I built a web dashboard for image automation, packaged as a company-branded Windows installer: real-time views of every build, reporting, and scheduling, so engineers run and track image updates without opening Azure DevOps.
A clinical companion for the Shang Han Lun, the Han-dynasty treatise at the root of classical Chinese herbal medicine. A guided intake leads a practitioner from symptoms to the formulas the text prescribes.
The client app for a three-location Minneapolis salon offering hair, colour and medspa treatments. Built natively in Swift on the Boulevard platform's GraphQL API, so bookings, artists and services stay in sync with the salon's own systems.
Tuning Kaseya VSA monitor sets and the procedures that turn alarms into Freshservice tickets, so engineers see fewer, better alerts. The same triage logic I now design into agents.
Running many client environments at once teaches you that nothing ships until it has been tested, verified and piloted. Every agent build goes through the same six stages.
Outcome, constraints and acceptance checks, before any agent touches code.
Specialist agents with only the MCP tools they need, tests written alongside.
Unit, integration and regression tests, agent evals, security and code review.
Real browsers and real data. Judgment calls go to a person.
One client or a small group first, then a go or no-go call.
Staged rollout in rings, monitored, with a tested rollback.
Managed services across multiple enterprise clients. Citrix (PVS, MCS), ControlUp, Azure Virtual Desktop and Windows 365, with Azure DevOps pipeline automation, VMware PowerCLI, enterprise PowerShell, Packer, Chocolatey, Power Automate, webhooks and a custom-developed .NET workflow application package.
Pre-launch venture: a web SaaS platform with iOS and Android apps. Leading product, design and engineering with a Claude Code agent team.
Native iOS/Android and AI-assisted apps for specialist audiences, from classical Chinese medicine study to salon booking.
An agent team, a Copilot rollout or a stubborn Citrix estate: I'd like to hear what you're building.