Every MSP owner has preached documentation to their techs for years, and most MSPs’ own environments are documented the way the cobbler’s kids are shod. That’s an operational annoyance while you own the business. The day you sell it, it becomes a discount, because a buyer looking at an undocumented shop is looking at a company whose real operating system lives in the heads of people who are free to leave. There’s a name for that on the buyer’s side of the table: key-person risk, priced accordingly.
Turn it around and documentation becomes one of the cheapest value projects available. It needs no new revenue, no new hires, and no market luck. Just discipline, over about a year, applied to writing down what your team already knows.
Why buyers pay for paper
Follow the buyer’s logic through one concrete fear. They’re acquiring your shop, and your senior tech (the one who built half the client environments) gives notice in month three. Question: what does the buyer own at that moment? If the answer is “a populated documentation platform with current credentials, network maps, and runbooks,” the departure is a hiring problem. If the answer is “whatever’s in Dave’s head,” the departure is a service crisis across a dozen clients, followed by churn, and the buyer will have modeled that scenario before making an offer. Documentation converts irreplaceable people into replaceable people, and while that sentence sounds cold, it’s precisely what makes a business durable enough to command a premium. It’s also better for Dave, who can take a vacation.
The same logic applies to you. Owner dependence is the biggest key-person discount of all, and the parts of your role that can be written down (how you quote, how you escalate, which vendor rep actually answers) are the parts a buyer can believe survive your exit.
There’s a second, quieter payoff: documentation accelerates the deal itself. Diligence is largely a documentation exam, and shops that can produce contracts, network diagrams, and process docs on request move through it weeks faster, with fewer of the delays that stretch timelines and erode trust. Buyers read the speed itself as evidence of a well-run company, because it is.
What buyers actually check
Not everything deserves documentation for sale purposes, so aim at what gets inspected. In rough priority order:
Client environment documentation. The core asset: per-client network maps, asset inventories, credential vaults (in a real password manager with access controls, never a spreadsheet), configurations, and the “quirks file” every environment has. Buyers will pull up three or four clients at random in your documentation platform and see whether what’s there matches reality and when it was last updated. Stale documentation reads worse than sparse documentation, because it means the habit died.
Runbooks for recurring operations. Onboarding a client, offboarding a client (and an employee, cleanly and securely), patch cycles, backup verification, incident response, the monthly billing run. The test a buyer applies: could a competent new hire execute this from the page? “Ask Dave” is not a runbook.
The sales and service pipeline. How a lead becomes a quote becomes an agreement becomes an onboarded client, with templates. This is the process most likely to live entirely in the owner’s head, and its absence is read as “revenue growth departs with the seller.”
Ticket hygiene as de facto documentation. Your PSA’s history is documentation whether you curated it or not: time entries, resolution notes, SLA performance. Buyers mine it, and thin, joke-filled, or time-traveled ticket data undermines the story your polished wiki tells. (Your PSA and RMM get their own diligence post later in this series.)
The corporate drawer. Entity records, client and vendor contracts in one indexed place, insurance policies, employee agreements. Less glamorous than runbooks and checked earlier, because it feeds the ten-minute screen.
The twelve-month version
Documentation projects fail by trying to document everything, so here’s the triage that works. Months one to three: get the corporate drawer and credential management right, and pick one documentation platform as the single source of truth (buyers don’t care which, they care that it’s populated and current). Months three to nine: client environments, biggest first, one per week as a standing engineering task with a rotation, so the habit outlives the initiative. Months nine to twelve: the top ten runbooks, chosen by asking “what would break if the person who does this won the lottery?” Then, permanently: documentation review as part of ticket closure, so the asset maintains itself.
Assign it an owner, put it on the same dashboard as revenue, and treat “is it current?” as the metric rather than page count. A year of this, run as a normal operational priority rather than a heroic sprint, is achievable for any shop with a functioning team.
The payoff shows up in every channel at once: the multiple (key-person risk priced down), the structure (less earnout insisted on to cover transition risk), the timeline (faster diligence), and the operating business you still own in the meantime, which runs better documented, sale or no sale. It’s the rare project with no bad outcome, which is why it sits in the first quarter of every pre-sale runway plan we build with owners. The knowledge is already in the building. The project is just getting it onto paper the building keeps.