Operations due diligence is an operator’s independent read on a target’s operating model, delivered before the transaction commits you to it. It answers the questions the data room is designed to keep abstract: can the delivery engine scale at the rate the thesis assumes, or does it already run hot at current volume? Is quality a measured system or an asserted virtue? How concentrated are decisions, relationships and knowledge in the founder? Where does margin quietly leak — rework, credits, write-offs, unbilled hours? And does cash behave the way the model says, or the way the billing process actually works? The output is a board-grade written assessment, ranked by financial exposure.
The craft here is not deal experience — it is operating experience, pointed at someone else’s operation. For nineteen years my job has been reading operating models from inside and finding where they leak: auditing quality across 2,000+ campaigns and 450 clients and moving the score from 95% to 99%; building the measurement a global network relied on to protect more than USD 20 million in billings; compressing a billing cycle from roughly two months to fifteen days across 75 entities, which required understanding exactly where cash gets stuck and why. Due diligence applies that same discipline to a target: the same questions, the same evidence standards, compressed into a deal timetable.
The assessment is built for the people who must act on it. For an investment committee: the operational risks that should price into the deal, ranked by exposure, with the evidence trail behind each. For the deal team: the specific claims in the CIM that did and did not survive contact with the operation. For whoever owns the asset after close: what the first hundred days should actually contain — not the template plan, but the sequenced repairs this specific operation needs, in the order the risk demands. Where a full review will not fit the timetable, a narrower pre-LOI red-flag read exists for exactly that purpose.