M&A Due Diligence Checklist for Operators

Most due diligence articles are written from a deal team lens. They spend most of their time on legal files, historic financials, tax items, and document control. Operators need a different working list. They need to know whether the target can keep serving customers, keep key people, run its core systems, and fit into the buyer’s operating model without a rough first quarter.

If you want the wider NMS view on the full deal cycle, see our pages on mergers and acquisitions full lifecycle services, post-merger integration strategy and execution, private equity due diligence checklist, Day 1 readiness checklist, and risk management.

Why Operators Need a Different Checklist

A banker asks whether the deal is priced well. A lawyer asks whether the contract protects the buyer. A finance lead asks whether the numbers hold. An operator asks a harder question: can this business keep running after close, and can it hit the plan without customer loss, staff exits, or system trouble?

That difference matters because many acquisition problems do not start in the model. They start in the handoff from pre-close diligence to post-close execution. A good operator checklist closes that gap.

The Operator Checklist

1. Deal Logic and Walk-Away Rules

Start with the operating case for the deal, not the model alone. Write down the few reasons this asset matters, then write down the conditions that would make the deal a bad fit from an operating seat.

• List the top three operating reasons for the deal, such as market share, product depth, route density, plant use, or service reach.
• Write the few value levers that matter most after close, such as sales force use, purchasing savings, plant loading, or faster product rollout.
• Set clear walk-away rules, such as customer loss risk above a set level, major system debt, weak local leadership, or vendor dependency with no near-term fix.
• Name the executive who owns the operator view in the deal room and in the investment memo.

2. Customer Base and Revenue Quality

Operators should not stop at revenue totals. Test how stable the revenue is, how hard it is to keep, and what could break when ownership changes.

• Review revenue by customer, product, channel, and geography for at least three years.
• Check customer concentration and gross margin by account.
• Pull churn data, renewal rates, return rates, backlog, and service complaint trends.
• Review change-of-control clauses, rebate terms, special pricing, and side letters.
• Interview commercial leaders on the top ten accounts and ask which ones are most at risk after close.
• Map where key account trust sits with one founder or one salesperson.

A deal can look strong on trailing revenue and still break after close if the top customers are tied to one relationship, one product line, or one pricing exception no one saw in time.

3. Operating Model and Service Delivery

This is the heart of operator due diligence. You need to know how work moves through the business, where delays start, who fixes daily issues, and which steps are fragile.

• Map the core flow from lead to order, order to cash, source to pay, and issue to resolution.
• Review on-time delivery, fill rate, backlog age, scrap, rework, service levels, and quality trends.
• Ask where manual work sits inside the flow and which steps depend on one person, one spreadsheet, or one custom tool.
• Test whether process owners can explain actual work, not only policy files.
• Visit a site or observe live work if the target has plants, warehouses, field teams, or service centers.

Many generic lists mention operations. Very few tell buyers to test where work actually jams, how often it jams, and who gets the call when it does.

4. Supply Chain, Vendors, and Facilities

Weak supply lines often show up after close, when the buyer learns that the target depends on a few suppliers, thin buffer stock, or informal side arrangements.

• List the top suppliers by spend, category, and site dependency.
• Flag sole-source vendors, long lead materials, and freight lanes with little slack.
• Review purchase terms, rebate structures, volume breaks, and renewal dates.
• Check inventory policy, stockouts, slow movers, and write-off history.
• Inspect key facilities, machine uptime, maintenance discipline, and recent capital spend.
• Review leases, landlord consent needs, and site-level permit exposure.

5. Technology, Data, and Cyber

Operators need more than a software inventory. They need to know what systems run the business, what breaks when those systems fail, and how hard it will be to join the target to the buyer stack.

• List the systems that run finance, sales, service, supply chain, payroll, reporting, and customer data.
• Map how those systems connect and where manual uploads sit between them.
• Review uptime, incident logs, disaster recovery plans, and role-based access rules.
• Check known cyber events, open patches, data privacy controls, and third-party software risk.
• Test the cost, time, and business risk of keeping systems separate for a period versus moving them fast.
• Ask which reports leaders trust, who builds them, and how long they take to update.

The right question is not only “What software do they use?” The right question is “What must keep working on Day 1, and what can wait?”

6. People, Roles, and Incentives

Many deals lose value because the buyer sees an org chart and thinks it sees the real power map. It does not. Operators need to find the people who hold customer trust, process knowledge, and daily control.

• Map the formal org chart and the informal influence chart.
• List the roles that would hurt the business if vacant for even 30 days.
• Review turnover by function, regretted exits, open roles, and hiring cycle time.
• Check bonus design, retention terms, sales incentives, and founder payouts that may shape behavior before close.
• Interview the next layer below the top team, not only the top team.
• Ask what would make key people stay and what would make them leave.

Middle managers often tell you more about post-close reality than the executive deck does. They know where decisions stall, where rework starts, and which leaders the staff trust.

7. Legal, Regulatory, and Contract Risk That Hits Operations

Operators do not need to redo legal diligence. They do need a clean read on which legal or regulatory issues can interrupt work after close.

• List licenses, permits, certifications, and customer approvals that keep the business open.
• Review contracts that limit pricing, territory, sourcing, staffing, or service changes.
• Check labor matters, safety matters, environmental claims, and open agency findings.
• Flag issues that need consent before close versus items that can be fixed after close.
• Translate legal findings into an operator risk list with owners, dates, and next steps.

8. Synergy Math and One-Time Cost

Bad synergy models often fail because no one asks what each line item needs in real life. Operators should break every synergy into work, time, owner, and risk.

• List each synergy line item with a named owner.
• Write what must happen before each item can show in the P and L.
• Separate run-rate value from Day 1 value.
• List one-time cost by workstream, such as systems, severance, site moves, consulting, rebranding, and legal work.
• Mark which synergy items depend on customer contract change, system change, or plant move.
• Test downside cases if one major synergy item slips by one or two quarters.

Operators should be careful with any synergy that depends on fast system change, heavy org redesign, or major account repricing in the first 90 days.

9. Day 1 and Day 100 Readiness

If the buyer cannot describe how the combined business will run on Day 1, the diligence work is not finished. Pre-close diligence should feed the first operating plan.

• Set the Day 1 governance model, approval rights, and meeting rhythm.
• List which policies stay in place on Day 1 and which ones change later.
• Set the communication plan for staff, customers, vendors, and partners.
• List all Day 1 dependencies for payroll, invoicing, customer support, sales reporting, system access, cash control, and issue routing.
• Write the Day 100 plan with a short set of actions, dates, and owners.

Operator Red Flags Before Close

These are common stop signs that deserve real attention before a buyer moves forward:

• More than a third of revenue tied to a few accounts with relationship risk.
• Core work run through manual files with little process control.
• Weak second-line leadership under a strong founder.
• ERP, CRM, or billing tools that no one wants to touch because the business does not trust them.
• Vendor concentration with no tested fallback source.
• Service levels that hold only through overtime, heroics, or one-off fixes.
• Synergy cases based on headcount cuts before the buyer understands who does the work.
• No clear Day 1 plan for approvals, reporting, and customer contact.

How to Run the Workstream

The cleanest operator workstreams are simple and fast. They use a short list of high-value questions, focused interviews, and direct site-level proof.

1. Set the operator thesis and walk-away rules before the full request list goes out.
2. Ask for the few files that show customer risk, process health, org depth, and system truth.
3. Interview leaders and the level below them.
4. Visit a site or observe work where the operating model matters most.
5. Convert findings into Day 1 tasks, risk owners, and deal term asks.

Pages Worth Reading

Some ranking pages are useful as reference points, mainly for legal and broad deal process items. They work best when paired with an operator-led workstream.

• DFIN on M and A due diligence checklist
• Diligent on a 20-point due diligence checklist
• Bloomberg Law on M and A due diligence checklist
• Wolters Kluwer on building a due diligence checklist
• Ansarada on operational due diligence
• EY on due diligence questions before signing a deal

Where NMS Can Help

NMS Consulting supports buyers that need more than a document review. Our work can help clients test operating risk before close, set Day 1 actions, and move from diligence into post-close execution with a clean handoff.

Read more on mergers and acquisitions, post-merger integration, and private equity.

Frequently Asked Questions

What is the difference between operator due diligence and banker due diligence?

Banker diligence usually centers on price, terms, debt, working capital, and legal exposure. Operator diligence centers on whether the buyer can run the target after close without customer loss, staff exits, system failure, or missed synergy goals.

When should operators join the due diligence process?

Operators should join before the request list is locked so they can test customer risk, service delivery, staffing, system fit, and Day 1 needs before the deal structure is fixed.

What should operators ask for in a due diligence data room?

Ask for customer concentration files, churn reports, service levels, org charts, vendor lists, system maps, backlog reports, quality metrics, incident logs, and any file that shows what the business must keep doing on Day 1.

What are the biggest operator red flags before close?

The biggest red flags are revenue tied to a few accounts, one-person process ownership, weak middle management, fragile systems, vendor dependency, hidden manual work, and no realistic Day 1 operating plan.

How does due diligence connect to post-merger integration?

Due diligence should feed the Day 1 plan, Day 100 plan, synergy model, staffing choices, risk controls, and communication plan. If those links are missing, the buyer is likely to relearn facts after close at a much higher cost.

Is this checklist useful for private equity operators?

Yes. It works for private equity operating partners, corporate development teams, COOs, integration leads, and function heads who will own execution after the transaction closes.