Home / How we work
PILLAR 4 · BRAND PROMISE

Vendor-neutral on AI.
Microsoft-aligned on infrastructure.
MacOS endpoints welcome.

We earn margin on the engagement, not on the licence. That changes the answer when you ask us what tool you should use. The other three pillars are services you can buy. This one is how we work — and the reason no major competitor can copy it without restructuring their margin model.

What this means in practice → See the exit clause
"We earn margin on the engagement,
not on the licence."
THE STRUCTURAL REASON EVERY OTHER PROMISE ON THIS PAGE IS REAL
What this means in practice

Three principles. Concrete behaviours.

"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.

01
Principle 1

AI-vendor agnostic — for real.

We build with Microsoft Copilot, Microsoft Copilot Studio, Power Automate, Anthropic Claude, Claude Desktop, 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 have the right to tell you Copilot isn't the right answer for your use case.
  • No contract makes us biased toward the answer being yes.
  • We've delivered Copilot rollouts and Claude integrations side by side, in the same quarter.
  • Our SoWs name the tool selected and the alternatives considered — every time.
02
Principle 2

Microsoft-aligned on infrastructure — honestly.

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.

  • Microsoft 365 — managed since 2017. Tenant operations, security, M365 Copilot.
  • Microsoft Defender, Sentinel, Purview, Intune — full security stack management.
  • Azure infrastructure — our default build environment.
  • Where a use case genuinely needs non-Microsoft infrastructure, we'll say so and recommend a different partner. We earn margin on the engagement — that recommendation costs us nothing.
  • MacOS endpoints fully supported. Mixed-fleet environments are normal.
03
Principle 3

Anti-lock-in as a stated discipline.

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.

  • Prompts and configurations live in client-owned source repositories — not vendor-locked tooling.
  • Data flows documented end-to-end, with substitute-vendor paths noted where realistic.
  • 30-day exit clause on every engagement — full documentation handover.
  • Where vendor lock-in is unavoidable (deep Microsoft Graph integration, for example), it's named explicitly in the SoW. You make the choice with eyes open.
  • No surprise migration fees if you leave. The work is yours.
The tools we actually deploy

Named vendors. Honest depth statements.

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 / Sentinel / Purview / Intune Deep Full security stack management — endpoint, SIEM, DLP, MDM. Essential Eight ML2+ aligned across the client base.
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) Working Integration projects and internal pilots. Selected for reasoning-heavy use cases where stack alignment is less important than model behaviour.
Claude Desktop Working Internal pilot. Surfacing in client conversations. Recommended where individual knowledge-worker workflows benefit from a desktop-native assistant.
Azure OpenAI Service Working Selected when Microsoft-stack alignment matters more than model choice — particularly for regulated industries where data-residency control is a requirement.
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

The exit clause

If you're wondering if it's real — read the contract.

Every Evisent engagement contract — Sprint, Bundle, Build, MSP — includes the same exit clause. We didn't write it to sell the website. We wrote it because we believe it, and because we want the buyer to be able to verify it before they book.

  • 1
    30 days' notice from either side.
    No long-form lock-in periods. No "minimum 3-year terms".
  • 2
    Full documentation handover.
    AUP, AI inventory, Purview config export, governance report archive, source artefacts. Yours.
  • 3
    Source artefacts in client-owned repositories.
    Prompts, flows, agent configurations live in your tenant or your repo from day one — not ours.
  • 4
    Co-operation with a successor provider.
    Up to 4 hours of handover support at no extra cost. We make the handover clean because we believe in being judged on whether the next provider says "we inherited a good environment".
  • 5
    Ask us for an example before you book.
    Email info@evisent.com.au with "sample contract" in the subject — we'll send a redacted SoW from a comparable engagement.
Statement of Work — Section 9
Exit, continuity, and portability
9.1 · Termination notice
Either party may terminate this engagement on 30 days' written notice. No early-termination fees apply.
9.2 · Documentation handover
Within 14 days of termination, Evisent shall deliver to the Client all governance documentation, AI inventory records, Microsoft Purview configuration exports, and source artefacts (prompts, flows, agent configurations) in the format specified at Schedule C.
9.3 · Successor support
Evisent shall provide up to 4 hours of handover support to a successor provider at no additional cost. Further hours billable at standard rates.
9.4 · Source artefact ownership
All prompts, flows, agent configurations, and integration scripts produced under this engagement vest in the Client on creation, in the Client's repository or tenant. Evisent retains no licence to Client artefacts beyond the term.
9.5 · Vendor lock-in disclosure
Where the architecture introduces vendor lock-in that cannot be cleanly substituted (e.g. deep Microsoft Graph integration), Evisent shall disclose this in writing at Schedule B before commencement.
Why this is hard to copy

The structural reason.

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.

The trade-off we made
We don't take licence margin. We don't sell licences alongside services in a way that rewards us for picking one platform over another. Our gross margin comes from the engagement itself — the Sprint, the Bundle setup, the Build hours, the monthly retainer. This means our annual revenue per client looks lower than competitors who take 20% on M365 resale. It also means we have the right to say "that vendor isn't the right answer" without it costing us anything. That trade-off is the brand.
Two ways to test the claim

Read a sample contract. Or book a sprint and see for yourself.

The clauses on this page are in every Evisent engagement contract. You can read one before you book — email info@evisent.com.au with "sample contract" — or you can book the Sprint and see the brand in delivery.

Book the Sprint → Request a sample contract