In a board session, the marketing function typically presents the volume of qualified demand generated during the period, while the sales function presents closed business and open opportunities, and the distance between the two presentations is usually absorbed by a polite silence. When someone at the table asks for the number that sits between them — how many of the leads marketing classified as qualified were actually accepted by sales as opportunities — the room does not produce one answer but two, each internally coherent. Marketing counts records that crossed its scoring threshold; sales counts conversations that entered its calendar. These two sets intersect without overlapping, and in most companies there is no record anywhere of where the non-overlapping portion went.
Asked at the diligence table, the same question changes register entirely. The review team does not want a summary dashboard; it wants the underlying cross-section — for records flagged as MQL in a specified month, the date on which each was accepted or declined as an SQL, the individual who made that call, and the stated reason. The request surfaces, often for the first time, a question the company has never asked itself: is declining a lead a decision, or merely a silence? Where the answer has no correlate in the record, the conversion ratio is describing not a structure that exists inside the company but a statement assembled for presentation — which, in review terms, is the existence question answered in the negative.
The mechanism beneath the gap is that the two decisions are different in kind. The MQL is a threshold decision: a composite score built from behavioural signals, firmographic fit and channel origin crossing a defined level. The SQL is an acceptance judgment: a representative deciding, against quota, calendar and an intuition about probability of close, whether to take ownership of the record. Because one rests on rules and the other on discretion, the transition between them becomes not a measurement but an implicit negotiation in which each side defends its own denominator — marketing lowering the threshold to demonstrate volume, sales raising the acceptance bar to protect its own conversion rate, both reporting improvement on the indicator they control.
In certain conditions this arrangement is entirely functional, and calling it an error would misread it. While the team is small, the founder or first sales lead is in effect the boundary itself; one person knows which demand is real, verbal alignment moves faster than written criteria, and maintaining an acceptance-criteria document costs more than it returns. The difficulty lies not in the shortcut but in the shortcut persisting after the conditions that justified it have changed — once channels multiply, once the sales team is split into territories, once an outside agency enters the flow, or once the founder steps back from the daily rhythm, the judgment carried by one person becomes impossible to replicate, and nothing has been built to stand in its place. From that point forward the company does not manage its demand pipeline; it observes it.
On the execution dimension, the most frequently observed omission is the absence of a return path for rejection. In most configurations an MQL that sales declines to accept is not returned to marketing with a coded reason; the record either sits in the system, closes quietly, or reappears on the same list in the next campaign. Because the reason is never encoded — wrong segment, no budget, contact without decision authority, timing mismatch, duplicate record — marketing cannot learn which signal misleads and cannot recalibrate its threshold. The conversion ratio consequently becomes a residual obtained by dividing two figures pulled from two different systems at period close; and since the denominator consists of leads that entered during the period while the numerator is dominated by acceptances carried over from earlier ones, the ratio falls when intake accelerates and rises when it slows, with that movement then read as performance.
The first surface on which the institutional cost appears is unit economics. Without channel-level conversion, customer acquisition cost can only be computed as total marketing spend divided by total new customers, which reports the average rather than identifying which channel is profitable. A budget managed against an average migrates inexorably toward the highest-volume channel, and the inverse relationship between volume and quality reaches the financial statements on a lag. Where sales cycle length, stage-level dwell time and the share of unaccepted demand are all unknown, pipeline coverage ceases to be a measurement and becomes an assumption — and a revenue forecast is no sturdier than the assumption on which it rests.
The second surface is valuation directly. A growth capital provider is not purchasing historical revenue but the production function that generates it, and the justification for any multiple paid is the belief that the same inputs will reproduce the same outputs. Where the acceptance mechanics of the demand pipeline cannot be demonstrated, that belief gives way to a judgment, and judgment tends to settle on the cautious side: a portion of value moves from headline consideration into earn-out, documentation of sales process appears among conditions precedent, representations and warranties expand to cover the accuracy of marketing data, and the escrow percentage moves upward. None of these shifts constitutes an objection to the company’s performance; each is the price attached to an inability to show that performance is reproducible independently of the founder.
The third surface is institutional memory, and it is generally the last to be noticed. Where stage transitions in the CRM can be edited retroactively — and in most configurations the permission matrix allows precisely this — conversion data for prior periods becomes rewritable to suit present requirements, and a review team will see this on the first audit trail it pulls. A record set whose timestamps are not locked cannot be treated as verifiable regardless of whether it happens to be accurate; an undocumented practice occupies, from an investor’s standpoint, the same category as a practice that does not exist. The continuity question is answered here as well: where the system rather than one person’s intuition carries the conversion, the ratio does not move when that person leaves.
The intervention that neutralises this tendency is system design rather than individual discipline, and it separates into four components. The first is binding the MQL and SQL definitions to a single acceptance-criteria document carrying the joint signature of marketing and sales — a document that enumerates not the scoring threshold but the minimum conditions required for acceptance, namely decision authority on the part of the contact, a defined need, a budget window, and geographic and segment fit. The second is a bidirectional path on which every unaccepted record returns to marketing tagged with a reason drawn from a closed code list; a free-text reason field cannot be analysed, so the list must remain short and exhaustive. The third is constructing measurement on a cohort rather than a period basis, tracking leads that entered in a given month by elapsed time from entry, with stage timestamps locked against subsequent alteration. The fourth is the existence of one owner for the boundary — authority to amend the definition, responsibility for reporting the measurement, and the mandate to resolve disputes between the two functions consolidated in a single role.
BEIREK’s intervention in this area begins not by building another dashboard but by defining the place where the acceptance decision enters the record. We draft the acceptance criteria as an internal protocol jointly signed by both functions, derive the rejection taxonomy from the company’s own observed objection patterns rather than from a generic template, and reconfigure the CRM permission matrix to close off retroactive stage editing. A quarterly recalibration rhythm then runs on top of that structure: cohort data is opened, the divergence between scoring threshold and acceptance bar is examined, the definition is amended where warranted, and the date of any amendment is itself recorded — so that historical ratios can be read with knowledge of the definition under which they were produced. What that rhythm yields is an evidence chain that can enter a data room directly, allowing the reviewing party to see not the ratio but the manner of its production.
A company’s demand generation claim only becomes testable at the point where it meets the judgment of its own sales organisation, and the MQL-to-SQL boundary is the sole location at which that encounter occurs — which is why it remains the least owned rather than the most measured segment of the marketing function. A company unable to present that boundary as a record has presented its growth as a narrative rather than a capability, and the multiple attached to a narrative is invariably lower than the multiple attached to a capability. The operative question is not whether the conversion rate is high, but in whose hands the decision producing that rate currently sits, and whether the same result would follow in that person’s absence.