When a due diligence session reaches the customer quality heading, the question asked is usually a simple one: what is your complaint rate? The manner in which the answer arrives carries more information than its content. The person supplying the figure either looks at a screen and reads the result of a division defined for a stated period, or pauses briefly and says something to the effect of five or ten a month, nothing serious. The second answer need not be wrong; a manager with genuine sector experience will often name the correct order of magnitude. At the review table, however, the two answers do not belong to the same category, since the first is the output of a verifiable record system while the second is the output of one person's memory, and memory is the single class of asset that cannot be transferred at closing.
A second pattern follows immediately, and it is usually more decisive than the first: in a substantial share of companies reporting a low complaint rate, the rate is low because the channel through which a complaint can reach the company is narrow. Where dissatisfaction can be voiced only verbally to a sales representative, where entering that report into the system degrades the representative's own performance review, and where no cross-check exists for reports never entered, the resulting number is a function of the incentive structure rather than of satisfaction. Read without reference to the width of the underlying reporting channel, a low ratio looks like good news; the same data, however, may equally indicate a structure in which the visibility of defects has been institutionally suppressed.
The mechanism operating beneath this is not a management failure but a fairly rational cost economy. In a small or mid-sized company the immediate cost of logging a complaint formally is real — a record is opened, an owner is assigned, a resolution clock starts running, and all of this draws on operational attention that is already scarce. The immediate cost of resolving the matter on the telephone and closing it there is close to zero, and the customer is frequently pleased with that outcome. While the company remains small this shortcut is not merely workable but superior; the difficulty lies not in the shortcut itself but in its persistence past the threshold at which customer count and product variety rise far enough for individual resolutions to begin forming a pattern. Beyond that threshold the pattern remains invisible because nothing is recorded, and, going uncorrected because it is invisible, it repeats.
In companies that do keep records, the mechanism obstructs at a different point: definitional drift. Where what constitutes a complaint has not been fixed in writing, the same event is classified as a technical support request in one period and as a complaint in another; a return request is sometimes counted as a complaint and sometimes segregated as a commercial transaction; whether three separate reports from a single customer produce one record or three varies with the person handling them. The denominator carries a parallel ambiguity — the ratio may be divided by active customer count, order count, delivery count, or invoiced volume. When these two ambiguities combine, the resulting time series is not, in any technical sense, a trend; once a reviewer recognises this, the three-year table in hand ceases to function as analytical material.
The implementation dimension opens a further layer. The gap between a complaint handling procedure residing in a quality management system file and one that has become the operation's actual working method can be substantial, certification notwithstanding. Where the procedure genuinely runs, it leaves identifiable traces: record opening times distribute across the working day, closing notes are not copies of one another, root cause fields are not left blank, and a traceable link exists between corrective action records and the complaints that triggered them. What is typically observed in files lacking these traces is that records were created in bulk and retrospectively shortly before an audit date, a pattern visible to any reviewer who examines the timestamps in the data room.
What is sought in the measurement dimension is more than a number. Reported on its own, the ratio says little about management quality; what carries meaning is the set of dimensions along which it is tracked. In a structure permitting complaints to be broken down by product group, customer segment, geography, sales channel, and recurrence, the management team is demonstrably able to see where defects concentrate. Two derivative indicators, moreover, tend to signal more strongly than the headline ratio in most reviews: first response time alongside final closure time, and the share of total complaints represented by repeat contacts from the same customer. Where the repeat share is high, a low aggregate rate signals not resolution quality but a high threshold for reporting.
The institutional cost of these indicators rarely appears as a discrete line in the income statement; it sits dispersed across the working capital cycle, warranty provisions, and cost of sales. Return and rework costs merge into production expense, goodwill discounts extended as gestures quietly erode gross margin, and management time spent on resolution is accounted for nowhere. Because the sum of these costs is unknown where complaints go unrecorded, no demonstration is possible, in the normalised EBITDA discussion, of which portion constitutes a recurring structural burden and which a one-off event. At the point where the buy side cannot draw that distinction, it typically takes the conservative position and prices the ambiguity in its own favour.
The channel through which this reaches valuation operates, in most cases, through deal structure rather than through the multiple itself. The typical outcome observed in files where customer quality cannot be verified is that the headline price holds while a larger share of consideration migrates past closing — earn-out periods lengthen, escrow percentages rise, separate warranty headings open for customer attrition and product liability, and in certain files direct reference calls with named customers are imposed as conditions precedent. Each of these means, for the seller, that cash flow is pushed back and that a portion of risk remains on its own balance sheet; an unverifiable indicator, in other words, exacts its cost not in price but in the timing and conditionality of payment.
Ownership and continuity form the final piece of this picture. In most companies the owner of the complaint process is not formally defined; in practice the founder or general manager steps in when a report arrives from a significant customer and closes the matter on the weight of a personal relationship. In the short term this is an exceptionally effective mode of resolution with a genuine effect on customer loyalty; because no record captures the authority under which closure occurred, the threshold up to which it applied, or the consideration granted, however, the same transaction cannot be reproduced by anyone else. A reviewer classifies this as founder dependency, since the question being asked is not whether these customers are satisfied but whether they will remain satisfied eighteen months after the founder has left the table.
The intervention that neutralises this tendency is system design rather than an appeal to individual discipline, and it separates into three components. The first is the definitional layer: what constitutes a complaint, which reports fall outside scope, and how numerator and denominator are computed are fixed in a definition note not exceeding a single page, with series produced under superseded definitions retained separately whenever that note changes. The second is the channel layer: the route by which a report reaches the company is made independent of the performance of the person logging it, since the quality of a record cannot be managed while it remains a function of the logger's incentives. The third is the authority layer: the monetary limits within which each level may settle, the threshold above which a matter enters the management agenda, and the signature a closure decision must carry are all determined in advance.
BEIREK's intervention under this heading typically begins with the reclassification of existing records; reports from the preceding two to three years are re-read under a single definition and the resulting definition-consistent series is placed alongside the series the company itself has reported, because the gap between them is generally the substance of the matter. The operational cost of complaints — returns, rework, commercial discounts, freight, and management time — is then tracked as a discrete line, since in the normalised EBITDA discussion the presence or absence of that line determines which side of the argument the seller is able to occupy. The rhythm established is demanding but simple: a monthly review session addresses not the ratio itself but recurring complaints and the tail of the closure-time distribution, and every corrective decision is recorded at the moment of proposal rather than the moment of approval, since a record written afterwards carries the outcome of a decision but not its reasoning.
The complaint rate's actual function in an investment review is not to demonstrate how satisfied customers are; it is to measure the company's capacity to see, record, and close its own defects independently of the founder. Where that capacity is built, the reported number sometimes rises, because reports previously invisible now enter the record — and for a reviewer, a ratio that climbs as logging discipline takes hold is a stronger marker of institutional maturity than a low ratio that never moves. The question that matters is this: does the complaint rate a company reports today measure the defects that occurred, or the defects that were recorded?