Free Interactive Tool · Microsoft Certified · Cape Town, SA
SME AI Decision Explorer — Copilot, licensing & the flat organisation
An interactive map for SME decision-makers: how an idea travels from a new hire to the CEO through Microsoft 365 Copilot, what each licence actually unlocks, where your conversations and files live, how the multi-cloud boundary is governed — and which decisions will still be right in five years.
The idea funnel — up and down a flattened organisation
Copilot doesn't flatten the org chart. It makes ideas legible faster — collapsing the friction between "rough thought" and "decision-ready artefact", so substance travels instead of status. Press play.
Ready
Watch a raw idea become a CEO-sponsored initiative — then watch the sponsorship funnel back down. The vertical distance stays; the friction disappears.
The SME paradox, resolved: as an SME scales, structure should move into the information layer — sensitivity labels, team boundaries, permissions — not into approval chains. Defined horizontal boundaries without corporate bureaucracy.
Who decides what — and what each person is really thinking
AI rollouts fail on people, not technology. Click each card for the paramount concern, the decision that person owns, and the training they need.
▼ Click any card to expand
The three concerns almost nobody lists: Shadow AI (staff already paste company data into personal chatbots — your governance case for sanctioned Copilot). Cost creep (Copilot Studio agents are pay-as-you-go metered; the CFO finds out in month three). The two-tier divide (frontline staff on basic licences get no Copilot while office staff do — morale and equity issue, HR's problem before it's IT's).
Where is your organisation right now? The 4 Levels of AI
Most companies have one AI power user and everyone else guessing. Rate each part of your business against the four levels — and find the single next step up.
What your licence actually unlocks (pricing verified July 2026, USD, annual commitment)
Pick a base plan, then toggle the Copilot add-on. Capabilities light up as they become available. This is the conversation to have before buying licences.
SME sweet spot: Business Standard + Copilot bundle at $23.50/user/mo (new SKU, July 2026) — but Business Premium + Copilot ($32) buys Intune, Entra ID P1 and Defender for Business, i.e. the governance you need before Copilot amplifies your permissions problems. Cheapest is rarely safest.
You ask Copilot something in Word. Then what?
The question every user asks and almost no rollout answers: where does the conversation go, where does the file live, how do colleagues get access, and how do notifications actually work. Step through it.
Rule of thumb to teach: personal OneDrive = my drafts, private by default. SharePoint / Teams site = the company's memory, where collaboration and Copilot grounding for the whole team happens. If it matters to more than you, it doesn't belong in "My files".
M365 company, AWS-mostly infrastructure, a bit of Azure — where does the boundary end?
It ends at identity, not infrastructure. You will never get one pane of glass for workloads. You can — and must — get one plane of control for people and data.
Microsoft 365
Collaboration & knowledge plane — mail, files, Teams, Copilot. Where ideas and decisions live.
AWS (primary infra)
Workloads stay here — fine. Federate AWS IAM Identity Center to Entra ID so access is granted, gated and revoked centrally.
Azure (tactical)
Native fit with the control planes below. Arc extends Azure Policy to servers anywhere.
1 · Identity — Entra IDSingle sign-in for all three clouds. Conditional Access + PIM: no standing admin rights anywhere, access is time-boxed and policy-gated — including for subsidiaries.
2 · Data — Microsoft PurviewSensitivity labels and DLP travel with the document, not the platform. Purview scans AWS S3 too. Copilot respects labels — governance before rollout, not after.
3 · Posture — Defender for Cloud + ArcConnect AWS (and GCP) accounts natively; one security score, one policy set, every cloud.
Sensitivity labels + DLP"Confidential" cannot be pasted into personal chatbots or mailed externally — the shadow-AI counter.
Privileged Identity MgmtAdmin rights expire in hours, with approval and an audit trail.
Intune + app protectionCompany data ring-fenced on BYOD; selective wipe without touching personal data.
Cross-tenant access policiesSubsidiaries collaborate under YOUR terms — B2B trust settings, not open federation.
Copilot admin controlsModel choice (Claude on/off), agent approval, Restricted SharePoint Search while permissions are cleaned up.
Authoritative vs definitive: authoritative = the system of record (Graph for people/mail/files; ERP for finance; CRM for customers — pick ONE per domain). Definitive = the accountable human decision. No AI output is definitive; it is a draft against authoritative data, with a named human owner.
Choosing AI with longevity when models expire in months
You cannot pick a model with longevity — and that's the answer, not the problem. Standardise the layers that survive model swaps. Microsoft proved the point by going multi-model itself.
Models — GPT · Claude · Gemini
Swappable engines. Choose per workload, review quarterly. Never let a contract, a curriculum or an architecture depend on one model name.
Where agents are built, governed and metered. Multi-model by design. This is the real "which AI do we buy" decision.
half-life: years owner: IT leadership
Identity, data & permissions — Entra · Purview · information architecture
The durable investment. Every model you will ever use inherits this layer's quality — or its mess. Get this right and everything above is replaceable.
half-life: a decade owner: EXCO
Model velocity, lived: GPT-4 (Mar 2023) → Copilot GA (Nov 2023) → GPT-4o (May 2024) → Claude 3.5 (Jun 2024) → o1 reasoning (Sep 2024) → Claude 4 (2025) → GPT-5 era (2025) → Claude in M365 Copilot, default-on (Jan 2026) → Agent 365 & E7 Frontier Suite (2026) → … every layer-1 bet above went stale within a year; every layer-3 investment is still paying.
How to teach AI that isn't outdated in 6 months: make layers 2–3 the curriculum spine (evergreen), and treat layer 1 as a rotating current-affairs segment. Your material stays valid; only the demos refresh.
Run this conversation with your own leadership team
The SME AI Readiness Workshop works through these six scenes with your actual licences, your actual data estate, and your actual people — half-day or full-day, online or in-person across South Africa.