Your MSP should document everything in your name. Here's what that looks like.

Here’s a question worth asking your IT provider today: if your company disappeared tomorrow, would I still own my environment?

Most MSP clients answer this question too late — usually during an offboarding where half the answers are “we’d have to ask the former MSP” and the former MSP isn’t returning calls. By then, it’s a six-figure cleanup project.

Documentation ownership is the clearest test of whether your IT provider actually respects you as a client or treats you as a locked-in revenue stream. Here’s what good looks like.

What “documented in your name” actually means

Every account, contract, license, and piece of infrastructure has an owner record somewhere. “In your name” means:

• The legal owner is your company. Not your MSP’s company. Not an MSP tech’s personal email.
• The billing contact is your company. Invoices go to an address you control. Renewals come to you.
• The admin credentials exist in a vault you own (even if your MSP also has access). You can revoke their access without losing yours.
• The documentation of how it all works lives somewhere you can read today, not “when you need it.”

If your MSP controls any of those layers exclusively, they don’t work for you — you work around them.

The 10 things that should be in your name (and why)

1. Your domain registration. GoDaddy, Cloudflare, Name Cheap — whoever the registrar is, the account should be yours. An MSP-held domain is the single worst lock-in to untangle.
2. Your DNS hosting. Same logic. If you can’t edit your own DNS records without going through a ticket, you’re locked out of your own infrastructure.
3. Apple Business Manager account. Owned by your org, with at least one admin who isn’t your MSP. ABM recovery when you’re not the admin can take 30+ days.
4. Microsoft 365 / Google Workspace tenant. Your tenant. Your Global Admin. Your billing. MSPs often create a “delegated admin” role for themselves; that’s fine. But you should have at least one Global Admin account in your own name.
5. MDM subscription. Jamf, Kandji, Mosyle — whichever it is, the subscription should be billed to your company. Not resold through an MSP partner program where the MSP holds the contract.
6. Cloud hosting (AWS, Azure, GCP). Root account tied to your billing. Period. Anything else is either fraud risk or lock-in risk.
7. Security / backup / monitoring tool licenses. CrashPlan, Datto, any RMM tool they use — if you’re the one relying on the data, you should own the license. Not always possible with MSP-specific tools, but you should at least know what’s running and why.
8. API keys and service accounts. The ones your MSP uses to operate on your behalf. You should have a list. You should be able to rotate them unilaterally.
9. Password vault / password manager company account.Whether that’s 1Password Business, Bitwarden, or Dashlane — billed to your company, owned by you, with your MSP as a guest user.
10. Your documentation itself. In your client portal (Hudu, ITGlue, SuperOps, Confluence). Exportable. Yours.

What good documentation looks like

Not just “a list.” Here’s what we expect to see in any well-managed environment:

• Asset inventory with serial numbers, assigned users, deployment dates, MDM status, current OS version, warranty status.
• Account registry of every SaaS tool, who the admins are, how billing flows, when renewals hit, which SSO connection is used.
• Network topology — even for cloud-first shops, document your VPN, any firewall rules, how traffic routes.
• Runbooks for common operations: onboarding, offboarding, device loss, password resets, account recovery. Written so someone else could execute them.
• Vendor list with point-of-contact, contract details, what service each vendor provides, when contracts expire.
• Change log tracking significant architecture decisions, when they were made, why, and by whom.

How to audit your own setup

Short exercise, 30 minutes:

1. Write down your 10 most important digital assets (domain, M365, ABM, AWS, MDM, etc.).
2. For each one, identify: who owns the account? Where does the bill go? Who has admin access? What’s the recovery path if the admin is unreachable?
3. Count how many of those questions you couldn’t answer without asking your MSP.

If the count is zero, you’re in great shape. If it’s 1-3, there are specific gaps to close. If it’s 4+, you have an ownership problem that’s going to hurt.

The conversation to have with your current MSP

This doesn’t need to be adversarial. Most good MSPs are willing to transition ownership if asked clearly. The request:

I’d like to walk through which accounts, licenses, and documentation are currently held by your company versus mine, and transition anything that’s currently yours into our name. Can we schedule an hour to go through this?

A healthy MSP says yes and does it. A less-healthy MSP gets defensive or vague. That reaction is your signal about how the broader relationship is structured.

What we do differently

Every Reign Zero engagement starts with an ownership audit and ends with a complete asset inventory in your own client portal. We use delegated admin access where it’s genuinely necessary, but we don’t hold domains, don’t bill through our own accounts, don’t put our company name on your Apple Business Manager, and don’t store your credentials in a vault we control.

If we disappear tomorrow, you keep everything. That’s not a marketing line — it’s what the engagement document explicitly says and what the setup literally reflects.

If you’re reading this and unsure what your current setup looks like, a clarity call can include a free ownership audit across your top-10 accounts. You’ll leave with a concrete list of what’s yours, what isn’t, and what needs to change — whether you work with us afterward or not.

Ownership is the clearest integrity test of any IT relationship. Test it before you need to trust the answer.