Operational Due Diligence for the First 100 Days
Use operational due diligence to find the queue, constraint, and ownership gaps an acquisition inherits, then sequence the first 100 days around evidence.
Want this inside your company?
Tell us the outcome you need, and we'll show you what we can build.
Operational due diligence should tell an acquirer where work waits, which constraint limits throughput, who owns the exception, and how much cash or customer value is attached to it. Financial diligence can show margin pressure. It rarely shows the desk where a quote waits nine days or the handoff that turns revenue into late cash.
The first 100 days should convert that hidden operating picture into a ranked map before the value-creation plan hardens around assumptions.
What diligence often misses
A conventional data room is rich in totals:
- revenue by customer
- gross margin
- headcount
- churn
- backlog
- working capital
- system inventory
- contracts and liabilities
An operator needs movement:
- age of work in every important queue
- rework and exception rate
- approval time
- capacity by role
- handoffs per deliverable
- concentration of knowledge
- days from commercial commitment to cash
- promises not represented in the system of record
The P&L tells you the symptom. The queue often reveals the mechanism.
Days 1 to 30: protect and observe
Do not begin with a new dashboard or a broad reorganization.
First:
- Protect payroll, billing, customer delivery, security, and regulatory work.
- Freeze unnecessary system changes.
- Name the critical weekly outputs.
- Capture a baseline from existing records.
- Interview the people who do and receive the work.
- Record where items wait, return, or need manual rescue.
Ask specific questions:
- What work is older than it should be today?
- Which approval has no backup?
- What spreadsheet must be correct for the company to bill?
- Which customer promise lives only in email?
- Where do people re-enter the same data?
- What gets checked twice because nobody trusts the first check?
- Which metric improves while cash or customers get worse?
The goal is not a list of complaints. It is a map with evidence.
Interview the work, not the org chart
Interview a vertical slice:
- person doing the work
- person approving it
- person receiving it next
- manager accountable for the outcome
- customer-facing role dealing with failure
Compare their descriptions of the same process. The disagreement is data.
For each recurring output, capture:
| Field | Example |
|---|---|
| Trigger | Signed order |
| Finished output | Invoice accepted by customer |
| Volume | 240 per month |
| Median cycle time | 6.2 days |
| Oldest open item | 31 days |
| Rework | 18% returned for missing field |
| Longest wait | Commercial-to-finance handoff |
| Owner | Unclear after sales closes |
| Cash or customer impact | Delayed billing and disputed scope |
This is not a benchmark exercise. Use the acquired company's own timestamps and samples.
Days 31 to 60: rank constraints by money
Score each constraint on:
- cash trapped or delayed
- revenue at risk
- customer impact
- volume affected
- controllability
- time to evidence
- dependency on another initiative
A loud problem with no measurable connection to value may rank below a quiet approval queue that touches every order.
Avoid fake precision. A score helps compare; it does not turn assumptions into audited dollars. Label estimated impact and show the calculation.
The revenue leak audit gives a practical scoring model. A formal bottleneck diagnosis turns interviews and operating data into a ranked evidence pack.
Days 61 to 100: change one constraint
Pick one or two interventions that can show evidence inside the first quarter.
Examples:
- remove a redundant approval from standard quotes
- create one owner for renewal preparation
- reject incomplete work before it enters delivery
- unify a customer handoff into one record
- produce a daily exception queue for invoices blocked from sending
For each:
- baseline
- owner
- expected mechanism
- protected guardrail
- review date
- stop condition
Do not declare "automation" the intervention. Name the changed output and decision.
Why day one matters more now
Bain's 2026 Global Private Equity Report says low prices, cheap debt, and easy multiple expansion are gone for the foreseeable future. It argues that current deals require faster EBITDA growth, sharper value creation, and movement from full-potential diligence to execution on day one (Bain Global Private Equity Report 2026).
That is Bain's market analysis, not proof that every deal needs the same 100-day playbook. It supports a practical point: when return depends more on operating improvement, the quality of the operating baseline matters earlier.
Speed does not mean changing everything in week one. It means collecting the evidence that lets the company move without guessing.
The view from the acquired company
The acquired team usually experiences due diligence as repeated extraction followed by a plan written elsewhere.
A better process gives them:
- a clear reason for each request
- fewer duplicate data asks
- a chance to correct false process maps
- visibility into how constraints were ranked
- named owners for decisions
- a record of which work will stop
Do not turn interviews into performance reviews. People hide failure modes when they think honesty will remove their role.
The best operators are often already running manual rescue systems. Those workarounds are not evidence that the process is fine. They show where the formal system failed.
What the first-100-days pack should contain
Keep it short:
- Current operating map.
- Five largest queues or failure modes.
- Evidence and confidence level for each.
- Cash, customer, and capacity connection.
- One or two interventions in flight.
- Owners and review cadence.
- Risks deliberately not addressed yet.
- Decisions needed from the board or sponsor.
No 80-slide transformation deck. The pack should help an operator decide on Monday.
Operational due diligence FAQs
When should operational due diligence start?
Before close when access and deal process allow it. Continue after close because data-room material rarely contains enough queue-level evidence. Protect clean-team, confidentiality, employment, and competition-law boundaries.
Who should lead the first 100 days?
One accountable operating leader should own the plan, supported by functional managers and the deal team. External specialists can diagnose or install a defined output, but internal leadership must own tradeoffs and people decisions.
What data should an acquirer request?
Request time-stamped samples of important work: opportunities, quotes, orders, delivery, invoices, support, renewals, and exceptions. Totals matter, but item-level age and rework reveal the operating mechanism.
Should the acquired company replace its systems immediately?
Usually not before the constraint is understood. A system migration can consume the first 100 days while preserving the same approval rules and handoff failures in a new interface.
Buy the company with its constraint. Find it before the plan starts treating symptoms.
Posted by @speedy_devv
Want this inside your company?
Tell us the outcome you need, and we'll show you what we can build.
Fractional COO vs Installed Operations: What Do You Need?
Compare a fractional COO, operations consultant, full-time hire, and installed system by leadership need, handover value, speed, and ongoing ownership.
The 30-Day Window After a Raise
A funding round is a dated buying signal with a short shelf life. When the window opens, why it closes, and the one thing to send instead of a congrats email.