The contractor rolodex lives in DMs, not runbooks

Your best freelancers trust you because you communicate casually. That trust does not transfer automatically to a spouse who has never met them.

Write the “who owns what” layer

Capture names, scopes, billing rhythms, and the one sentence of context that preserves tone: who is allowed to pause work, who must be paid first, and who can deploy a hotfix.

Relationships built in chat do not transfer by default

Your best freelancers trust you because you communicate casually. That trust does not automatically extend to someone stepping in cold who has never met them. DMs are fast; they are also amnesia the moment context switches.

Freeze the rolodex in plain language

• Name, scope, billing rhythm, and the one sentence of tone context.
• Who can pause work vs who must be paid first.
• Which relationships are allowed to hear bad news first.

Continue with the next entrepreneur continuity piece and another angle on the same portfolio pressure.

DMs are not contracts; capture intent in writing

Tone and scope live in threads. Pull the durable parts into the manual so a successor does not negotiate tone from scratch during a crisis.

Renew contractor sections quarterly

Rates, scopes, and availability change. A stale contractor entry can be worse than none if it sends someone to the wrong human.

Next, tighten another edge with this related entrepreneur article.