Microsoft 365, security, devices, Copilot, AI agents and standards

Every project has a motive. We start there.

A Copilot rollout, an audit finding, a breach, a device refresh, a divestiture — we start with why you are moving and engineer the Microsoft 365 work backwards from it. Architects on the keyboard, documents you own, no dependency.

Find your motiveTake the 26 questions
FORM SM-00MOTIVE STATEMENT
We need to roll out Copilot safely
by next quarter
because the licences are paid for and nobody trusts our permissions.
SIGNED — CIO1 / 1

Pick your motive

We don't sell services. We answer motives.

Choose the sentence that sounds most like your last leadership meeting.

The uncomfortable questions

Twenty-six questions. How many can you answer with evidence?

Be honest — nobody's watching. Every Not sure turns over to show what we'd check and what you'd walk away with.

PROVEN0
NOT SURE0
UNANSWERED26
YOUR NOT-SURE LIST IS YOUR SCOPESend it to us. Get a read-only Tenant X-ray.

Before you ask

How we touch your tenant.

01Read-only firstYou see every permission we request before you approve it.
02Time-boxedEligible, not standing. Access ends with the engagement.
03On the recordEvery action lands in your audit log, under a named person.
04Revoked on exitWe remove ourselves with you watching — and hand you the proof.

The Motive Method

Four moves. The last one is leaving.

M¹Motive

One sentence, signed by the person who owns the outcome. Every decision after this gets tested against it.

M²Map

Tenant, identities, devices, mail flow, data, owners. We read your environment before we write a single recommendation.

M³Move

Architects implement. Waves, cutovers, pilots — shipped in your tenant, with rollback written before go-live.

M⁴Manual

Standards, SOPs and runbooks your team can run without us. Success is when you stop needing to call.

What we leave behind

Paper, not dependency.

Every engagement ends with a document set that passes an auditor, onboards a new hire, and survives the people who wrote it.

SM-POLv1.0
PolicyAcceptable use, AI usage, data sharing
SM-STDv1.0
StandardIntune, Exchange, Conditional Access
SM-SOPv1.0
SOPDevice enrolment, leaver handling
SM-ADRv1.0
ADRWhy we chose X over Y, in writing
SM-HLDv1.0
HLD / LLDTarget architecture and build detail
SM-RUNv1.0
RunbookCutover, rollback, break-glass

Anti-promises

Things we won't do.

80-slide strategy decksYou get a two-page brief and a working change.
Juniors learning on your tenantThe architect you meet is the one who builds it.
Open-ended retainersFixed scope, fixed exit. Extend only if you want to.
Tools you don't needIf your existing licences do the job, we say so.

Engagements

01Motive Diagnosis

A 30-minute call. You leave with your motive written down and an honest view of whether you need us.

30 MIN
02Map Sprint

Environment read-out, risk-ranked findings and a clear plan. Useful even if you build it yourselves.

2 WEEKS
03Build Engagement

Architects implement the plan in your tenant — device rollout, Copilot launch, security baseline, custom agents, standards set.

6–12 WEEKS
04Fractional Architect

A named architect a few days a month for design reviews, CAB, and the questions nobody else can answer.

MONTHLY