A recurring scene appears in fast-growing companies: at a stage where headcount has multiplied within a short window, ten recent joiners asked separately how work is prioritized, at what threshold a client request is declined, or below what margin a proposal will not be signed, give materially different answers. None of the answers is wrong; each faithfully reflects the practice of the senior colleague alongside whom that person spent an initial period. Founders and founding teams typically read these divergences as a discipline problem, seeking the remedy in retelling the story more often, convening more frequently, and pulling more people into the same room. What is being observed, however, is not a failure of discipline but the simultaneous operation of several local norms inside a single organization.
A second observation surfaces on the financial side, generally a few quarters later. Of engagements taken on under the same contract template, the same pricing logic, and comparable technical scope, the first delivers the targeted margin, while similar work handed to a second and third team in the same period closes appreciably below plan. The contract is identical, the supplier list is identical, and even the client profile is comparable; the only variable that differs is the number of hours the delivering team has spent working directly with the founding group. What is notable here is not the magnitude of the deviation but the difficulty of attributing it to any single line item, since the loss has accumulated across dozens of small decisions rather than concentrating in one place.
The name for this pattern is scaling-culture failure — the inability to carry a culture that worked in a small team through a period of growth — and its mechanism has little to do with the erosion of values that is commonly assumed. Culture is not the set of principles a company hangs on a wall; it is an implicit coordination technology that allows the majority of decisions to be made without explicit negotiation. In a team of seven, that technology is remarkably efficient: everyone heard the same client conversation and saw the cost of the same mistake in the same week, so the cost of writing down the rationale for a decision exceeds the benefit of having written it. Not writing is not negligence here but a rational choice; the problem lies not in the choice itself but in its persistence after the condition that made it rational has disappeared.
That condition disappears where two curves intersect. On one side, the number of pairwise relationships through which shared context must be established grows far faster than headcount; on the other, the channel through which tacit knowledge travels — learning by working beside a senior colleague, sitting in the same meeting, correcting the same error together — does not even grow linearly, since the number of senior people is fixed and each has a practical ceiling on how many colleagues can be accompanied at once. From the moment hiring velocity exceeds that ceiling, a portion of new joiners learns the culture not from the founding source but from a colleague who arrived six months earlier, which is to say from a copy of a copy. Detail is inevitably lost at every link of that chain, and what is typically lost is not the rule itself but the exception knowledge governing the conditions under which the rule is suspended.
What forms at this point is not a vacuum, and it is for precisely that reason difficult to manage. When an unwritten norm weakens, lawlessness does not take its place; each sub-team institutionalizes its own leader's interpretation as the legitimate norm. While the company continues to appear from the outside as a single legal entity, several companies operate inside it, diverging in pricing discipline, quality thresholds, authority to commit to clients, and behavior after an error. A founder who intervenes at this stage to correct individual decisions closes the deviation in the short term while aggravating the underlying condition over the medium term, since every intervention confirms that the second line holds no effective decision rights and narrows the transmission channel further.
The institutional counterpart of this mechanism is highly visible to a party sitting on the review side of the table. Among the findings most frequently recorded in diligence is that decision authority, distributed on the formal organization chart, is concentrated in a single person in practice; and the evidence for it is sought not in management representations but in the distribution of approval records, the revision history of proposals, and whose signature client correspondence carries. The reviewing party is not making an assessment of management style at that point but an assessment of transferability, attempting to estimate what portion of current performance would remain in place should the founder reduce involvement over the next three years. The greater the uncertainty attaching to that estimate, the more protectively the transaction structure is built.
The financial footprint of the transmission gap appears under no culture heading in any trial balance; it disperses across line items that look unrelated to one another. Rework and correction costs are buried directly in project cost and are usually classified as non-standard consumables or overtime. Attrition concentrates between the twelfth and eighteenth months of hiring cohorts — the window typically observed in organizations where implicit norms remain unwritten, since that interval is when a joiner's own interpretation first collides seriously with the organization's operative one. On the commercial side, the effect emerges in cycle length and proposal discounting, because in conversations the founder does not attend, a team uncertain about the boundary of its commitment authority either behaves too cautiously or commits beyond its mandate.
The translation of these findings into valuation language does not converge on a single heading. Where founder dependency is identified, the typical outcome is less a reduction in headline price than a deferral of consideration and its conditioning: a higher earn-out proportion, a wider escrow, key-person undertakings extended in duration, and operational continuity items added to the scope of representations and warranties. On the credit side, the same finding surfaces as covenant provisions tying key personnel changes to notification requirements and as additional reporting obligations. The implicit thesis is identical at both tables: what determines a company's multiple is usually not performance itself but the demonstrability that such performance is reproducible independently of the founder.
The mechanism that neutralizes this tendency is institutional architecture rather than individual awareness, and it comprises four separable components. First, keeping the decision record at the moment of proposal rather than the moment of approval: unless it is written which option was eliminated and on what grounds, what gets transmitted is not a decision but only an outcome, and an outcome carries no knowledge that is reproducible in a new context. Second, tying authority to thresholds rather than to persons: once measurable thresholds are defined across value, duration, margin deviation, and client commitment, the second line's mandate ceases to depend on the founder's availability on a given day. Third, writing the refusal criteria explicitly, since what genuinely carries an organization's culture is not what it does but what it declines to do despite the apparent attractiveness, together with the reasoning. Fourth, tying hiring velocity to transmission capacity: where the size of each cohort is not bounded by the senior capacity actually available to accompany it, the gap opens inevitably.
BEIREK's intervention in this problem operates not by establishing a culture program but by making the decision architecture visible. In the project and portfolio management engagements we undertake, the first layer we install is a decision record capturing the rationale at the moment of proposal, paired with an authority matrix anchored to thresholds for value, duration, scope change, and margin deviation; where these two operate together, the framework legitimating a second-line decision ceases to be a matter of debate. On top of that sits a fixed-cadence review at the close of each delivery cycle that locates the source of deviation in the decision point rather than in the individual, along with a structured pre-mortem run before entering the next engagement. These records serve a secondary function as well: when a transaction or financing process begins, the material evidencing transferability need not be assembled retrospectively, because it already exists.
The sequence of the intervention matters, and this is the point most frequently skipped in practice. Where authority thresholds are distributed before a decision record is in place, the result is not distributed authority but scattered decisions whose rationale cannot be traced; the founder's reflex to reclaim control then strengthens, and the process returns to where it began. Conversely, where a decision record is established on its own without any distribution of authority, it produces only a documentation burden and is effectively abandoned within a few months. Where both components are installed in the same quarter, each referencing the other, the transmission channel begins to detach from the physical presence of a senior individual, and the tension between growth rate and cultural continuity becomes, for the first time, a manageable variable.
What is lost during growth is rarely a company's values; what is lost is the exception knowledge concerning how those values apply to specific decisions, and absent documentation, such knowledge travels only through time spent together. The question worth asking of a company in a scaling phase is therefore not whether the culture has been preserved, but whether the rationale behind today's decisions could be reproduced by someone else when the person who made them is not in the room.
Sources note: this analysis draws on patterns observed in diligence and delivery reviews rather than on any single engagement.