Runbooks written on live tenants. Proven with evidence, not settings.

Executable Microsoft 365 fix packs, deployment playbooks, and documentation templates for solo MSP techs and small IT shops. Every procedure reads the real state, makes the smallest change that fixes it, and proves the fix before close-out.

Digital products · Secure checkout by Stripe · Delivered by email

Start with the flagship

The mail-flow pack is the procedure set behind real tenant fixes — group mail that never reaches inboxes, traces that "show nothing," and changes made confidently to the wrong tenant.

Flagship · Runbook Pack

M365 Tenant Fix Runbook Pack: Mail Flow & Groups

Group mail-delivery diagnosis and fix (member vs. subscriber), the message-trace proof workflow, a tenant-identity verification checklist, and close-out templates. PDF runbook plus four field-ready PowerShell scripts.

CA$97CA$149
Launch price · PDF + PowerShell scripts · ~25–35 pages See what's inside →
Playbook

Outlook Add-in Deployment Playbook

Deploy a vendor Outlook add-in across client tenants without the stalls: portal vs. Exchange Online PowerShell routes, tenant authorization and consent, and post-deploy verification your clients' security files will pass.

CA$69
PDF playbook + checklists · ~15–20 pages See what's inside →
Templates

IT Documentation & Site Survey Template Pack

Network survey pack, camera-system design checklist, and the client documentation templates — asset register, change log, tenant-change record, close-out note — that make a small shop document like a big one.

CA$39
Editable Word/Excel + PDF examples See what's inside →

How buying works

No accounts, no portals, no licence servers. Three steps and the pack is in your inbox.

1

Check out with Stripe

Pay on Stripe's secure hosted checkout. We never see or store your card details.

2

Get the delivery email

Your pack arrives by email at the address you checked out with — PDF, scripts, and templates, packaged and versioned.

3

Run it on your tenant

Follow the verification discipline in the pack: read state, change small, prove it with a trace.

The working standard behind every product

These products are generalized from live field procedure — the method is what's for sale, never a client's data. Six rules run through all of it: verify the tenant from the connection, pin the case before changing anything, read before you write, -WhatIf first, a setting is not proof (a trace is), and disconnect when you're done.