Evaluating Management During Due Diligence

How should quality be defined for the target business?

Quality should be defined as the target’s ability to meet customer requirements consistently, safely, and economically across the full product or service lifecycle.

The definition must be specific to the customer promise. For a manufactured product, quality may depend on conformance to specification, durability, safety, defect rates, packaging, and warranty performance. For a professional service, it may depend on technical accuracy, timeliness, responsiveness, consistency between employees, and the client’s ability to use the deliverable. For software, quality includes functional reliability, security, maintainability, release discipline, and support.

A certification can support the review but cannot replace it. ISO explains that ISO 9001 focuses on customer needs, process control, documented information, performance evaluation, risk-based thinking, and continual improvement; certification is voluntary and is performed by independent certification bodies rather than ISO itself. That makes a valid certificate evidence of a management system, not proof that every product, service engagement, or customer outcome is satisfactory. See the ISO 9001 overview.

What evidence should the buyer request first?

Start with source records that connect customer promises, operating performance, incidents, and financial consequences over the same period.

A polished quality manual or dashboard is not enough. Request underlying records for at least the period covered by the financial due diligence, and longer where product lives, warranties, contracts, or regulatory exposure extend beyond it. Reconcile counts and definitions before comparing trends. A “defect,” “complaint,” “return,” or “severity-one incident” may be defined differently across departments or may have changed after a system migration.

For each dataset, document the owner, system of record, coverage period, exclusions, and any manual adjustments. Then trace a small sample from the source record through management’s dashboard and into the general ledger. The purpose is not only to find errors; it is to determine whether management can reliably see and control quality.

How do you test whether customers experience real quality?

Use behavior, complaints, and direct interviews together; no single satisfaction score can establish quality on its own.

Customer surveys may be useful, but first inspect response rates, sample selection, question wording, timing, and whether detractors were excluded. Pair stated satisfaction with observed behavior such as repeat purchases, renewal rates, usage, share of wallet, voluntary references, support burden, and account losses. For enterprise customers, conduct interviews across decision-makers, daily users, procurement, and technical contacts because each sees a different part of the experience.

Good performance measures should show the current level, the trend over a meaningful period, relevant comparisons, and alignment with organizational priorities. NIST’s Baldrige guidance also recommends a comprehensive set covering product or service performance, customer-focused performance, operations, compliance, and financial outcomes. This is a useful antidote to dashboards that show only favorable point estimates. See NIST’s guidance on performance measurement.

What should customer interviews ask?

Ask for specific events, alternatives, and consequences rather than broad opinions.

• What outcome did the customer expect, and which features or service steps mattered most?
• Describe the most recent failure, delay, error, or escalation. What was the operational or financial impact?
• How consistently does performance vary by location, product version, project manager, or service team?
• What would cause the customer to switch, reduce volume, or refuse a price increase?
• Which competitor is the credible alternative, and where is it stronger or weaker?

How should physical products be evaluated?

Evaluate design adequacy, supplier and process control, conformance, field reliability, safety, traceability, and the effectiveness of corrective action.

Begin by selecting representative stock-keeping units, plants, suppliers, production dates, and customer segments. Inspect actual products and packaging, observe production or fulfillment, and witness testing where feasible. Review whether critical characteristics are measurable, whether test equipment is calibrated, whether nonconforming material is segregated, and whether changes to materials, tooling, suppliers, or design trigger documented approval and retesting.

For consumer products, safety and recall readiness deserve separate attention. CPSC guidance emphasizes safety by design, foreseeable use and misuse, external challenge of hazard assumptions, documented testing, reliable supply chains, and recall planning. Its guidance also notes that documentation helps identify what failed and what should be changed after a safety issue. Review the CPSC manufacturing best practices and search the CPSC recalls database for the company, brands, predecessor entities, product categories, and major suppliers.

Review warranty terms as both a legal obligation and an operating signal. In the United States, the FTC explains that written consumer-product warranties are governed by the Magnuson-Moss Warranty Act and related rules, while implied warranties arise under state law. The applicability and consequences depend on the product, transaction, warranty language, and jurisdiction, so material exposure should be reviewed by qualified counsel. The FTC warranty guide is a useful starting point for U.S. consumer products.

How should service quality be evaluated?

Test whether the service outcome and customer experience remain consistent across employees, locations, channels, and demand levels.

Service quality is usually less visible than a physical defect because the service is produced and consumed through people, processes, judgment, and communication. A business may report strong gross margins while absorbing hidden quality costs through free rework, senior-staff escalation, uncompensated scope, discounts, delayed billing, or employee overtime. Therefore, review both the customer outcome and the operating effort required to produce it.

Segment results by office, team, service line, customer size, and manager. Company-wide averages can hide a profitable core and a weak location, or a strong founder-led team and a less reliable scaled operation. Review employee turnover, training, utilization, span of control, and dependency on a few experts because service quality may decline after the transaction if those people leave.

What additional work is needed for software and digital products?

Software quality review must cover functionality, reliability, security, architecture, release discipline, supportability, and the ability to maintain the product after closing.

A product demonstration confirms only that selected workflows can operate in a controlled setting. Obtain architecture and dependency information, incident records, release histories, testing evidence, vulnerability-management records, support data, and a roadmap with staffing assumptions. Reperform critical workflows in a representative environment and test failure recovery, permissions, data export, configuration, performance under load, and compatibility with customer integrations.

Security is part of product quality because vulnerabilities can impair availability, confidentiality, customer trust, and the cost of support. NIST’s Secure Software Development Framework recommends integrating secure development practices into the software development lifecycle and notes that purchasers can use the framework to communicate with suppliers during acquisition. Review the NIST Secure Software Development Framework as a structured reference, while tailoring the review to the product’s risk and regulatory environment.

Which software risks are most likely to affect valuation?

Focus on risks that require unavoidable remediation, threaten retention, or constrain growth.

• Critical knowledge concentrated in founders or a small number of engineers.
• A release process that depends on manual steps, lacks rollback, or produces recurring incidents.
• Unsupported components, restrictive licenses, or dependencies that cannot be replaced economically.
• Security findings without ownership, deadlines, verification, or customer communication plans.
• A roadmap dominated by defect correction and infrastructure work that management presents as discretionary growth investment.

Which metrics reveal hidden quality costs?

The most useful metrics connect defects and service failures to prevention, inspection, rework, warranty, support, customer concessions, and lost revenue.

American Society for Quality guidance divides cost of quality into prevention costs, appraisal costs, internal failure costs, and external failure costs. This framework is useful in due diligence because reported margins may exclude, scatter, or misclassify the cost of poor quality across operations, customer service, sales, freight, inventory, and general administrative accounts. Review the ASQ explanation of cost of quality.

Trend each metric by period and segment, but also inspect absolute severity. A low-frequency event can still be material if it creates safety, regulatory, cybersecurity, contractual, or reputational exposure. Conversely, a high ticket count may reflect active adoption rather than poor quality if severity is low and resolution is fast. Definitions and context control the interpretation.

How should quality findings change the financial model and deal terms?

Translate each material finding into recurring earnings, one-time remediation cash, working capital, growth assumptions, capital needs, or a specific contractual protection.

The same defect can affect several parts of the model. A weak product line may require higher warranty expense, additional quality staff, slower growth, inventory write-offs, and a redesign program. A service inconsistency may require lower utilization, more supervision, retraining, customer credits, and conservative retention assumptions. Avoid double counting by assigning each effect to one line and documenting the linkage.

How can an illustrative quality scorecard support the decision?

A scorecard can organize evidence, but it should not replace the underlying risks, cash estimates, or deal conditions.

Which red flags should change the deal?

Deal-changing red flags are those that undermine the reliability of evidence, create open-ended liability, or show that reported earnings depend on unsustainable quality practices.

A red flag does not automatically require abandoning the acquisition. It requires a decision about whether the issue is measurable, fixable, transferable, insurable, and appropriately priced. Where the downside cannot be bounded with reasonable evidence, scenario analysis and transaction protection are more defensible than a precise adjustment.