Where an MSP is the better choice, and where I am

Five differences

First output

A typical MSP: A support-tier proposal and an onboarding call.
A typical large integrator: An assessment deck, a service-tier recommendation and an operating-model workshop.
Working with me: A written architecture record and delivery backlog, five business days from the €499 workshop.

Operating model

A typical MSP: Your estate runs through their helpdesk queue and their standard tooling.
A typical large integrator: A provider account team manages the estate through its own delivery queue.
Working with me: I do the engineering myself, inside your tenant and your repository. I use AI tools only on my own drafts and scripts. No configuration, export or personal data from your systems goes into them (Terms of Service, section 14, Processing personal data for you).

Procurement

A typical MSP: A bundled monthly contract sized to a support tier rather than an individual licence rate.
A typical large integrator: A contracted managed-services programme with provider-defined bundles and a multi-year term.
Working with me: Licences procured through the Pax8 marketplace and billed by Michal Jatczak, trading as ITSailor. Marketplace prices are based on Pax8 suggested retail, and billing can move to you; Microsoft states a partner-of-record transfer takes up to 72 hours.

Audit posture

A typical MSP: Compliance evidence, where it exists, sits inside internal helpdesk tickets.
A typical large integrator: Governance sits inside a broader managed programme, scoped and priced on its own.
Working with me: An evidence pack you keep, built from read-only exports of your tenant.

Exit

A typical MSP: Offboarding means extracting configuration from someone else's monitoring tool and documentation habits.
A typical large integrator: Knowledge transfer is negotiated as its own project once the contract ends.
Working with me: An Exit Kit delivered within 24 hours of the engagement closing under a Statement of Work (Terms, section 07).

Five differences between a typical MSP, a typical large integrator and working with me
Dimension	A typical MSP	A typical large integrator	Working with me
First output	A support-tier proposal and an onboarding call.	An assessment deck, a service-tier recommendation and an operating-model workshop.	A written architecture record and delivery backlog, five business days from the €499 workshop.
Operating model	Your estate runs through their helpdesk queue and their standard tooling.	A provider account team manages the estate through its own delivery queue.	I do the engineering myself, inside your tenant and your repository. I use AI tools only on my own drafts and scripts. No configuration, export or personal data from your systems goes into them (Terms of Service, section 14, Processing personal data for you).
Procurement	A bundled monthly contract sized to a support tier rather than an individual licence rate.	A contracted managed-services programme with provider-defined bundles and a multi-year term.	Licences procured through the Pax8 marketplace and billed by Michal Jatczak, trading as ITSailor. Marketplace prices are based on Pax8 suggested retail, and billing can move to you; Microsoft states a partner-of-record transfer takes up to 72 hours.
Audit posture	Compliance evidence, where it exists, sits inside internal helpdesk tickets.	Governance sits inside a broader managed programme, scoped and priced on its own.	An evidence pack you keep, built from read-only exports of your tenant.
Exit	Offboarding means extracting configuration from someone else's monitoring tool and documentation habits.	Knowledge transfer is negotiated as its own project once the contract ends.	An Exit Kit delivered within 24 hours of the engagement closing under a Statement of Work (Terms, section 07).

AssertedDescriptions of other suppliers are general and name no firm.

When an MSP is the better choice

Some jobs are a better fit for an MSP than for me.

Onsite hands for hardware failures, cabling and physical break/fix.
A hardware fleet living on your premises that needs local physical support.
A 24/7 phone helpdesk covering every device in the building.

I do not sell any of these. My work happens in the cloud and in code.

Working beside your MSP

If you already have an MSP, I take a scoped project in your tenant and leave the running of it with them.

What I take: A fixed project such as tenant hardening, a device baseline or a data access review. Your MSP can be the named approver for each change, and it receives the Exit Kit, the runbooks and the evidence pack when the work closes.
What stays with them: The helpdesk, the hardware, daily administration and any SOC or MDR coverage. After a handover I offer ten hours a month for changes, reviews and questions on what I built, and nothing wider.

How an engagement runs, what I need from you and what I do not do are on the page about working with me.

Send a brief, or read a sample report first

Send a brief See the sample report

The sample shows the format of the workshop deliverable. Its findings are illustrative. Book the architecture workshop.