SOPs that survive due diligence

Why “it’s all in my head” is a discount

Every trades business runs on knowledge. The question is where that knowledge lives. If the pricing rules, the dispatch judgment, the supplier workarounds, and the way a hard callback gets handled all live in the owner’s head, a buyer is not looking at a company. They are looking at a job the owner is about to leave.

The lowest rung of process maturity is tribal knowledge: work happens from memory and owner texts, and the owner answers the same questions every week. Buyers read that condition quickly, and they price it as transition risk. Transition risk shows up as a lower offer, a longer earnout, more seller financing, or a deal that quietly stalls in diligence. Documented, verified processes are how knowledge moves from the owner into the company, and how the company becomes the thing being sold.

What to document first

You do not need everything written down. Start with the processes that create revenue, protect margin, reduce owner dependence, or reduce complaints. For most service trades, that list looks like this:

1. Call intake and booking. Revenue leaks at first contact.
2. Dispatch and schedule changes. The owner is usually the router; this is the first habit to break.
3. The standard service call, start to finish, including required photos.
4. Estimates and proposals, tied to a price book and an approval ladder.
5. Job closeout, invoicing, and payment. Faster invoices mean healthier receivables.
6. Callback and warranty handling, with the cause logged each time.
7. Customer complaints, including who has authority to resolve them.
8. Purchasing and parts, tied to the job they belong to.

The details shift by trade. For landscaping, route planning comes first because route density drives margin. For cleaning, it is the site walkthrough and quote, because scope accuracy decides whether a contract makes money. For auto repair, it is vehicle intake and inspection. The principle is the same: document where money is made or lost, not what is easiest to write.

The effort is smaller than most owners expect. A company with two to five employees can document five core processes in roughly ten to twenty hours. A practical setup for a small company is one internal SOP owner spending two to four hours a week for about twelve weeks, with little or no new software spend.

The format that actually gets used

A sustainable SOP is not a 40-page binder. It is a short, findable instruction that a real employee uses while doing the job. The formats that survive field reality are simple: a phone or Loom video of your best person doing the task, a one-page checklist of ten to twenty-five steps in plain language, photo examples of what done-right looks like, and clear decision rules for when to escalate, discount, or refund.

Each one needs a clear trigger, an observable definition of done, an escalation rule, required proof such as a photo or system note, a named owner, and a review date. Store it where the work happens, inside ServiceTitan, Jobber, Housecall Pro, or a well-organized shared drive, because a process an employee has to hunt for is a process that will not be used. And do not make yourself the owner of every SOP. That recreates owner dependence in a different form.

Proving the SOPs are real

A PDF named “SOP manual” is not proof. Proof is a trained person doing the work from the process. Two simple tests get you there. The different-person test: someone who does not normally own a process runs it using only the SOP, and it passes when they finish in roughly 80 to 120 percent of normal time with no safety, customer, or financial failure. The owner-text test: count the texts and calls you get about a documented process for one week. Fewer than two questions per process per week after training is passing.

The evidence buyers respond to follows the same logic: training completion records by employee, an SOP register with owners and review dates, a random job audit showing the required photos and notes, a callback trend that improves after a process change, and SOPs embedded in the field software rather than sitting in a folder. A buyer should be able to open the SOP, look at a job record, and see the matching proof in the system. One verified checklist that lowers callbacks or speeds up billing is worth more than a beautiful manual nobody opens.

The financial SOP buyers test first

Before a buyer ever watches a tech run a checklist, they will test one process: how you close the books. The monthly close is an SOP like any other, with a trigger, steps, an owner, and a done standard. The healthy version looks like this: bank and credit card accounts reconciled every month, P&L and balance sheet closed by the tenth calendar day, receivables over sixty days explained, and owner expenses or addbacks tagged with support saved at the time, not reconstructed later.

The rough scale buyers and lenders apply: a close by day ten is strong, day eleven to twenty-five is workable, and numbers that only exist at tax time are a red flag. SBA-style lenders also weight earnings that tax returns can support, so management financials that reconcile to the returns matter. If you can produce the same monthly packet twelve months running and explain the variances without rewriting history, you have proven the most important process in the company: that the numbers can be trusted.

Where to start

None of this is legal, tax, or financial advice, and a readiness score is not an appraisal. But process maturity is one of the clearest signals of how a sale will go, and it is fixable in months, not years. If you want an honest read on where your business stands, start with the free readiness scan. It takes a few minutes and shows you where a buyer would push first.