Operational Due Diligence Checklist: What Acquirers Will Actually Ask About Your Operations

An acquirer's operational due diligence checklist tests four areas: delivery processes and project margin, key person risk and founder dependency, contract quality and revenue durability, and governance, records and management information. Every question probes whether your revenue is produced by a system rather than by individuals, and weak answers get priced as a lower multiple, a longer earn-out or heavier warranties, which is why the founders who keep their price intact are the ones who ran the same checklist on themselves months before anyone opened a data room.

This article sets out the operational questions that diligence teams in technology services deals actually ask, what a weak answer costs you in price or terms, and how to run a pre-diligence review so that the gaps are closed before they become negotiating leverage for the other side.

What is operational due diligence?

Operational due diligence is the part of an acquisition or investment process in which the buyer examines how a business actually runs, covering how work is won, delivered, staffed, governed and reported, in order to judge whether past performance will continue once the buyer owns it. It sits alongside financial, legal, tax and commercial diligence, and in a technology services business it often carries the most weight, because the asset being bought is largely people, processes and client relationships rather than products or property.

Financial diligence checks that the numbers are real, whereas operational diligence checks that the numbers are repeatable, and the distinction matters because a services business can show three excellent years that were produced entirely by heroics, favourable luck and a founder working every weekend. An acquirer cannot buy heroics, so the diligence team is looking for evidence that revenue, margin and delivery quality are produced by a system rather than by individuals, and every document request and management interview is a probe against that single question.

Who runs it and how it unfolds

Operational diligence is usually carried out by the buyer's own operating team, by an external advisory firm the buyer appoints, or by a combination of the two, and on private equity backed deals it is common for an operating partner to lead the management interviews while advisers work through the data room. The process tends to begin with a written information request list, moves into a virtual data room where documents are uploaded against that list, and then continues through management presentations, one-to-one interviews with your leadership team and follow-up questions that arrive in waves as each answer raises the next one.

The pace is set by the buyer, not by you, and the follow-up waves are where most of the pain sits, because a team that answers the first request list well but cannot support its answers with evidence in the second round has told the buyer more than any single document would.

The operational due diligence checklist, section by section

Delivery processes and project health

Expect the diligence team to ask how projects move from signed contract to delivery, who estimates and approves scope, how progress and margin are tracked while work is in flight, and what happens when a project starts to slip. They will ask for a list of every current engagement with its status, budget position and margin to date, and they will compare what the project tracker says against what the management interviews reveal, because a gap between the two tells them that your reporting is decorative rather than operational.

Specific questions to prepare for include: what proportion of projects deliver at or above their estimated margin; how utilisation is measured and what it has been for the last eight quarters; how change requests are captured and charged; and whether there is a documented delivery methodology that new joiners actually follow. A methodology that exists only as a slide from three years ago counts against you, since the acquirer will conclude that delivery quality depends on whoever happens to be running each project.

Key person risk and founder dependency

This is the section where founder-led firms lose the most value, because the diligence team will interview your leadership without you in the room and ask them directly which decisions they can take alone, which clients would wobble if the founder stepped back, and who owns the largest relationships. If the honest answer is that pricing, hiring, escalations and the top five accounts all route through you, the acquirer has just discovered that a substantial part of what they are buying walks out of the door at the end of your earn-out, and they will price accordingly or extend the earn-out to compensate.

They will also ask about depth beneath the leadership team: who could step up if the delivery lead resigned during the deal, whether knowledge of key accounts is documented or held in individual heads, and what notice periods and incentives tie senior people in. The pattern they are hunting for is what we have called elsewhere the founder dependency problem, and it is visible to an experienced diligence team within two interviews.

Contract quality and revenue durability

Every client contract will be read, so expect questions about termination notice periods, whether rates are fixed or indexed, what liability caps you have accepted, whether contracts contain change of control clauses that let clients walk away on acquisition, and how much revenue sits on expired or evergreen agreements that were never renewed properly. A book of business where the top three clients can terminate on thirty days' notice is worth materially less than the same revenue on twelve-month committed terms, and no amount of relationship warmth changes that arithmetic.

They will also examine concentration, asking what percentage of revenue comes from the largest client and the largest sector, and how much of the pipeline depends on referrals from relationships the founder personally holds. These are the same tests investors apply earlier in the lifecycle, which is why the groundwork described in preparing a business for investment pays off twice.

People, resourcing and commercial discipline

Because headcount is the cost base of a services firm, the diligence team will want to see an organisation chart with roles, tenure and cost, attrition for the last two years, the ratio of employees to contractors, and how the bench is managed when a large engagement ends. They will ask how rates are set and who is allowed to discount, how often pricing is reviewed, and whether pipeline coverage is tracked against the resourcing plan, since a business that wins work it cannot staff, or staffs people it has not yet sold, is showing the buyer that growth and delivery are not talking to each other. Contractor arrangements also draw scrutiny on employment status grounds, so expect questions about how long individual contractors have worked for you and on what terms.

Governance, records and management information

This is the least glamorous section and the one most often failed. Diligence teams will ask for board minutes, management accounts, the risk register, employment contracts, IP assignments from every contractor who ever wrote code or content, data protection records and evidence that policies are actually operated rather than filed. They will ask how quickly you can produce monthly accounts, whether forecasts have historically been accurate, and whether the leadership team runs a regular operating cadence with documented decisions.

Weakness here rarely kills a deal on its own, but it slows everything down, invites deeper digging elsewhere, and signals a business that is managed by instinct, which colours how every other answer is received.

A condensed checklist to work through

For founders who want the whole exercise in one place, the questions below summarise what a diligence team will try to evidence, and each one should be answerable from a document, report or system rather than from your recollection.

1. Can you produce a current list of every engagement with status, budget position and margin to date?
2. What proportion of projects delivered at or above estimated margin over the last eight quarters?
3. How is utilisation measured, and is the figure consistent across reports?
4. Is there a delivery methodology that new joiners actually follow?
5. Which decisions still require the founder, and are decision rights written down for everything else?
6. Who owns each of the top ten client relationships, and would those clients stay without the founder?
7. Who could replace each member of the leadership team at short notice?
8. What are the termination, rate and change of control terms in every client contract?
9. What share of revenue comes from the largest client and the largest sector?
10. How much revenue sits on expired or never-renewed agreements?
11. What has attrition been, and how is the bench managed between engagements?
12. Who can approve discounts, and how often are rates reviewed?
13. Do you hold signed IP assignments from every employee and contractor?
14. How quickly are monthly accounts produced, and how accurate have forecasts been?
15. Are board and leadership decisions minuted, and is the risk register actually used?

What a weak answer costs

Weak answers get priced, and they get priced in predictable ways. Poor contract terms and client concentration reduce the headline multiple; founder dependency lengthens the earn-out and shifts more of the consideration into deferred or contingent payments; unreliable management information leads to heavier warranties and indemnities, larger retentions held in escrow, and a longer exclusivity period during which you are locked in while the buyer keeps digging. The deal you announce and the cash you eventually receive can diverge a long way, and most of that divergence is manufactured in operational diligence.

Acquirers rarely walk away because of what they find; they walk away because of what they suspect you are hiding, and gaps in your records look like hiding.

Running your own pre-diligence review

Six to twelve months before you expect a process, work through the checklist above as though you were the buyer, which means asking for the documents rather than the explanations. Pull every client contract and log the termination, rate and change of control terms; list the decisions that currently require the founder and start moving them, with written decision rights, to named owners; reconcile what the project tracker says against actual margins for the last four quarters and fix the tracking before you fix the story; and assemble a data room now, so that the act of populating it exposes the gaps while there is still time to close them.

Where the review reveals structural problems rather than missing paperwork, deal with them in order of price impact: founder dependency and delivery margin first, contract hygiene second, governance records third. A longer runway helps considerably, and the sequencing is covered in more depth in our two-year exit readiness plan.

Where Vitori fits

Running an honest pre-diligence review on your own business is hard, partly because you are too close to it and partly because fixing what you find is an operating job rather than a reporting job. Vitori's Operational Scale Framework assesses Growth, Delivery and Operations against the same maturity questions a diligence team will ask, and where the gaps are structural we can embed through our Operator model, including as a fractional COO, to close them, staying accountable until the changes hold rather than leaving you with a findings deck. You do not need us to run the checklist in this article, and whether you close the gaps with Vitori or anyone else, the work is the same: build a business that demonstrably runs, and scales, without the founder in every decision, because that is precisely what an acquirer is paying for.