On AI Builds, we earn margin on the engagement — the engineering work — not on the AI vendor's licence. That changes the answer when you ask us what tool you should use. (Managed IT is different: Microsoft licensing flows through our CSP, transparently itemised on every bill.) Vendor-neutrality is the operating principle that sits across both departments.
"Vendor-neutral" is one of the most overused words on MSP websites. The principles below are the specific behaviours that make our claim real — and the ones a sharp buyer can check.
We build with Anthropic Claude, Microsoft Copilot, Copilot Studio, Power Automate, and Azure OpenAI Service. We govern AI from any vendor your team is using — ChatGPT, Gemini, Perplexity, whatever's there. We pick tools per project, for fit, not for partner margin.
We build inside Microsoft 365 and Azure. We don't deliver AWS-native or GCP-native infrastructure work. We have deep expertise in one stack, and that's where our work lives. The trade-off: you get genuine depth in a Microsoft-aligned environment, rather than shallow breadth across three clouds.
Most AI engagements quietly create lock-in: bespoke prompts in vendor-locked tooling, data pipelines that don't export cleanly, governance structures assuming one vendor's posture. We architect against this by default. The buyer should always be able to leave. They mostly won't, but the option is the point.
Every tool below is on this list because it's in active delivery. We don't list partnerships to look more impressive. If we wouldn't pitch up to a client with this tool today, it isn't on this page.
| Tool | Depth | How we use it |
|---|---|---|
| Microsoft 365 | Deep | Managed since 2017. Tenant operations, security, identity, M365 Copilot configuration, licensing advice. |
| Microsoft Defender / Purview / Intune | Deep | Full security stack management — endpoint, DLP, MDM. Essential Eight ML1 baseline across the client base; ML2+ where regulators require it. Sentinel SIEM available as an add-on. |
| Microsoft Copilot (M365) | Deep | Deployed across client environments and configured to Essential Eight / Purview standards. Governance overlays included. |
| Microsoft Copilot Studio | Working | Custom agent builds in active delivery. M365-integrated agents for client-onboarding, support, and document workflows. |
| Power Automate | Deep | Workflow automation across client environments. Power Apps integration. M365-connector-led, with selective Claude/Copilot AI steps. |
| Anthropic Claude (API + Enterprise) | Deep | Our preferred model family for reasoning-heavy work, Builds, and internal operations. Selected when model behaviour matters more than stack alignment — which is most of the time. |
| Azure OpenAI Service | Deep | Selected when Microsoft-stack alignment, data-residency control, or regulated-industry constraints make Azure-hosted models the right call. |
| Azure infrastructure | Deep | Our default build environment. Where AI integrations need supporting infrastructure (vector stores, sandboxes, identity), Azure is the path. |
| ChatGPT / Gemini / Perplexity / others | Govern only | Awareness, not deployment. We govern what your staff are already using — Shadow AI Discovery and Acceptable Use Policy coverage extend to any vendor. |
"DEEP" = ACTIVE DELIVERY ACROSS MULTIPLE CLIENTS · "WORKING" = ACTIVE DELIVERY OR LIVE PILOTS · "GOVERN ONLY" = COVERED BY OUR GOVERNANCE LAYER WITHOUT EVISENT DEPLOYMENT
Most engagements start with a single Build. The second and third follow once the first one is paying for itself. By Build 3 the question is no longer "is this working" — it's "is the whole AI program paying off, and can we prove it to the board?" We answer that with the same dashboard for every client.
Every dollar of AI spend reconciled against the hours it returned. ROI multiplier on the front page. Not a slide we prep at QBR time — a number that updates monthly, automatically.
Drill into any automation to see active users and run counts. Drill into any user to see their patterns. The build nobody uses is the worst kind of build — adoption visibility is how we catch it early.
Named risks, residual ratings, named owners, last review dates, controls. Maintained continuously — not assembled the week before the board paper. Ready for external assurance.
The demo shows a sanitised version with fictitious data. See the real case study that the system was first built for.
Every major Australian MSP pitching AI has channel-partner-aligned answers baked into their margin model. Microsoft margin. AWS margin. Vendor SPIF programs. The website says "vendor neutral"; the commission plan says otherwise.
If the way we work fits the way you want to be served, the AI Readiness Sprint is the cleanest first engagement. Two weeks. From $4,950 + GST. No MSP relationship required.