Services

Everything from the model
down to the mouse.

Five connected practices. Engage one of them or all of them: either way you deal with the same engineer, and everything is documented, scoped and handed over as something you own.

01 · Lead practice

Microsoft 365 & Cloud Migrations

Move onto Microsoft 365 the right way. Migrations fail on the details: shared mailboxes, public folders, mapped drives, the one legacy app nobody mentioned. We find those in discovery, not at cutover.

Typical engagement: 2–8 weeks depending on data volume and complexity.

  • Tenant buildGreenfield Microsoft 365 setup with security baselines applied from day one.
  • Email migrationExchange on-premises, IMAP, Google Workspace or tenant-to-tenant moves.
  • File migrationFile servers and legacy shares into SharePoint and OneDrive with permissions intact.
  • Teams rolloutStructure, governance, external access and Teams Phone where it fits.
  • Tenant consolidationMerging tenants after acquisition, including identity and license rationalization.
  • AdoptionShort, practical sessions so the change sticks after go-live.
02

AI deployments

Most AI projects stall between the demo and the rollout. The blocker is rarely the model: it's permissions, data sprawl, governance and people. We handle that half.

Typical engagement: 2–6 weeks, fixed scope, starting with a readiness assessment.

  • Copilot readinessPermission and oversharing remediation across SharePoint and OneDrive before rollout.
  • Copilot deploymentLicensing, pilot group design, adoption sessions and usage reporting.
  • Custom AI assistantsAzure OpenAI and AI Foundry solutions grounded in your own documents and systems.
  • Retrieval & searchRAG pipelines over policy libraries, contracts, ticket history and knowledge bases.
  • Process automationAgentic workflows for triage, summarization and routine document handling.
  • GovernanceData boundaries, acceptable-use policy, audit logging and cost controls.
03

Azure cloud & infrastructure as code

Cloud that was clicked together in a portal is impossible to audit and expensive to run. We rebuild it as code: versioned, reviewable and reproducible.

Typical engagement: landing zone in 3–5 weeks, or ongoing platform support.

  • Landing zonesSubscription topology, management groups, networking and identity foundations.
  • BicepReusable module libraries with parameterized environments and sensible defaults.
  • CI/CD pipelinesAzure DevOps or GitHub Actions with what-if previews and approval gates.
  • GovernanceAzure Policy, tagging standards, RBAC design and naming conventions.
  • Cost optimizationRight-sizing, reservations, orphaned-resource cleanup and budget alerting.
  • MigrationLift-and-shift or re-platform of servers, databases and line-of-business apps.
04

Cybersecurity & compliance

You don't need a security operations center. You need the handful of controls that stop the attacks that actually happen to businesses your size, and proof they work.

Typical engagement: assessment in 1–2 weeks, remediation scoped from findings.

  • Identity hardeningEntra ID baselines, conditional access, MFA rollout and legacy auth removal.
  • Privileged accessAdmin tiering, just-in-time elevation and break-glass account design.
  • Endpoint securityDefender deployment, disk encryption, attack surface reduction rules.
  • Backup & DRImmutable backups, documented recovery plans and scheduled restore testing.
  • Posture assessmentWritten report against a recognized baseline with prioritized remediation.
  • Compliance supportEvidence gathering and control mapping for insurer or customer questionnaires.
05

Endpoint Management & Patching

The unglamorous layer that keeps every device secure and current. Devices that enrol themselves, patches that land on schedule, and access that's provisioned and revoked automatically.

Typical engagement: monthly retainer sized to headcount and device count.

  • Endpoint managementIntune enrollment, Autopilot provisioning, configuration and compliance profiles.
  • Patch managementUpdate rings, driver and firmware policies, and reporting on what's actually current.
  • Application deliveryPackaged deployments, license tracking and standardized software baselines.
  • Joiner / mover / leaverAutomated onboarding and offboarding so access ends when employment does.
  • Compliance reportingDevice compliance status, drift detection and remediation reporting.
  • Asset & documentationLiving inventory and runbooks kept current, not written once and abandoned.
Engagement models

Three ways to work together

Assessment

A time-boxed review of a specific area, such as your Microsoft 365 tenant, Azure estate, security posture or AI readiness. Delivered as a written report with prioritized, priced recommendations, yours to keep whether or not you engage further.

Most common

Project

A defined outcome with a fixed scope, fixed price and an agreed timeline: a migration, a landing zone, a Copilot rollout. You know what you're getting and what it costs before anything starts.

Retainer

Ongoing monitoring, patching and improvement for a predictable monthly fee, sized to your headcount. Includes a standing block of project hours so small improvements don't need a new quote every time.

Next step

Start with a conversation

Tell us what's on your plate. You'll get an honest read on what it involves, and a fixed-scope proposal if it's a fit.

Book a free consult Meet the founder