In an investment committee session, the sequence of questions put to a founder tends to run in a predictable order: what the product does, how it differs from the alternatives, and, last, why the customer will abandon whatever is currently installed. The answers to the first two questions are typically detailed, quantified, and technically defensible. The answer to the third, even inside a deck prepared with the same care throughout, is noticeably shorter and rests on a heavier load of assumption, resolving in most cases back into the product itself — the customer will switch because the solution is evidently better. Measured against the analytical density of everything preceding it, that resolution reads as a break in the chain of reasoning rather than a conclusion drawn from it.
The same pattern shows up in the record of customer meetings. In technical sessions with the engineering team the buyer side is engaged, often enthusiastic; questions during the demonstration deepen, a pilot is requested, and the pilot generally concludes with the technical result the founder expected. What follows the pilot, however, stretches across several times the timeline anticipated, ending either deferred into a budget cycle or blocked behind the renewal date of an incumbent supplier agreement. The founder usually attributes the outcome to weakness in the sales team or to conservatism on the buyer’s side, notwithstanding that at no point in the process was the performance of the product itself in dispute.
The mechanism operating here is innovator bias — the founder’s treatment of novelty as sufficient grounds for adoption — and it draws on two distinct cognitive layers. The first is the asymmetry created by time spent on the problem: to a mind that has held the problem for years, the value of the solution is self-evident, precisely because that mind knows in detail the price paid in the solution’s absence. The second is that the founder’s own switching cost is zero; the founder is the single participant in the transaction who never has to install the product, learn it, wire it into existing processes, or carry it through an internal approval. Combined, these two layers render the distance between the value of the product and the cost of moving to it systematically invisible.
It is worth noting that the tendency is functional under specific conditions, since at the outset the only asset a founder holds is conviction that an unproven thesis is correct. Absent market signal, absent reference customers, and absent any basis for comparison, disproportionate confidence in the product’s value is what holds the team together, attracts capital, and keeps decision velocity high. The difficulty lies not in the presence of that confidence but in its persistence after the conditions change: once the first ten customers have closed, a sales organisation has been built, and the growth target is set by the commercial cycle rather than by engineering throughput, the same confidence ceases to function as a resource and begins to function as an obstacle to measurement.
The institutional consequence surfaces earliest in the length of the sales cycle. A growth assumption grounded in technical superiority treats cycle length as a function of product attributes, whereas the variables that actually determine it sit on the buyer’s side — how many approval tiers must be cleared, when the termination window opens in the incumbent contract, which internal team’s annual plan the integration must enter, how long the information security review will run. None of these shorten through product improvement; they shorten only through redesign of the selling process itself. As the cycle extends, the distance between sales cost paid upfront and revenue collected downstream widens, and the company finds itself financing not its product but its own working capital.
The second cost accumulates in revenue quality. Where adoption friction goes unpriced, contracts tend to close on one of two concessions: price, or scope — bespoke integration, a development commitment written into the agreement, an extended pilot period, a service level undertaking broader than the standard. These concessions never aggregate into a single line on the income statement; they disperse as a few points of erosion in gross margin, as engineering time drifting toward customer-specific work, and as a maintenance burden growing faster than the customer count. The answer to the repeatability question asked in the next financing round is held, in its entirety, in the sum of those dispersed items.
The third cost, and the most expensive in valuation terms, is founder dependency. The assumption that the product sells itself resolves in practice into a structure in which the founder sells the product, because what overcomes buyer hesitation is not the feature set but the founder’s persuasive standing in the room, the authority to make commitments on the spot, and the capacity to reframe the problem in the buyer’s own vocabulary. At the diligence table this structure becomes directly legible through three measures: the share of total contracts in which the founder participated directly, the difference in conversion rate between meetings the founder attended and those attended by the team, and average time to close per sales representative. Read together, they express the question the acquirer is actually asking — how much of this revenue stream remains in place once the founder leaves the table.
The answer gets priced through one of two mechanisms. Either the multiple is marked down directly, or a portion of consideration is shifted past closing into an earn-out conditioned on founder retention and on sales targets, with the representations and warranties package widened, the escrow percentage raised, and key-person commitments elevated into a separate article of the agreement. None of this constitutes a judgement on product quality; all of it is a pricing of the risk that the source of revenue has not been institutionalised. To the extent that the company’s own narrative keeps the product at the centre, the pricing will strike the founder as unfair — although the acquirer is buying not the product but whether the product’s salability is independent of any single person.
The mechanism that neutralises this tendency is not personal awareness but recording discipline, and it comprises four components. First, loss reasons captured against a standard taxonomy and maintained independently of the sales function; where price, timing, integration burden, internal approval blockage, and incumbent relationship are not tagged separately, every loss is written to price and the wrong corrective follows. Second, adoption friction measured before the proposal is issued: how many systems the buyer must replace, how many users must be trained, and how many internal approvals must be cleared, recorded numerically at proposal stage. Third, the conversion rate between pilot and purchase tracked as a distinct series, since a pilot programme with a high technical success rate and a low conversion rate is a signal about the purchasing process, not about the product. Fourth, the counter-argument role institutionalised — a person, holding no share of the commission, tasked before each significant proposal with writing the strongest available case for the buyer to decline.
BEIREK carries this intervention by reconstructing the architecture of the purchase decision itself. The technical claim of the product and the decision process of the buyer are treated as two separate layers; for the second layer, the approval chain within the buying institution, the budget calendar, the renewal windows in incumbent supplier agreements, and the identity of the internal risk owner are mapped, and that map is held in a single record for each opportunity. The loss-reason taxonomy is then seated on top of that map, so that a review conducted three months later can separate losses attributable to price from those attributable to switching cost and from those attributable to nothing more than calendar.
The second line of work is the translation of the same record into the language of investment readiness. Sales lines with founder involvement and without it are reported separately; time to close per representative and pilot-to-purchase conversion are tracked on a quarterly rhythm in a single format, so that when the diligence table raises these questions the answer is a series consistent backward through time rather than an explanation assembled in the moment. The existence of that series is frequently more determinative than the figures within it, given that evidence of founder-independent repeatability lies not in one strong quarter but in the institutionalisation of the measurement itself.
The assumption that innovation sells itself is not, on inspection, a product claim at all; it is an implicit distribution claim — the claim that the buyer’s switching cost is negligible relative to the difference the product creates. That claim is a testable proposition in exactly the way the technical claim is, and until tested it remains the most expensive assumption on the company’s books. The question worth putting to a founder is therefore not whether the product is good enough, but on whose desk, today, the strongest case for the buyer to say no is written down.