When a due diligence session reaches the intellectual property heading, the first question posed by the reviewing side is seldom about patent portfolios or trademark registrations; it is something far plainer — where are the executed instruments establishing that the work product of the people who wrote this product, designed it and built its methods has passed to the company. The reaction observed in the room when that question lands is a recurring pattern rather than an isolated event: what arrives is not a document folder but an explanation, to the effect that employment agreements contain a clause, that everyone signs it, and that the work was produced for the company in any case. The explanation is frequently accurate. A review, however, tests not accuracy but demonstrability, and the distance between the two opens precisely here. The question a company has typically never put to itself is not what it owns, but how it would show what it owns.
The mechanism underlying this gap is not negligence; it is a sequencing choice that is entirely rational under the conditions in which it is made. In the early period, everything the company produces is produced around one table by the same handful of people, and the question of where ownership sits is not a practical question, because the people creating the work and the people claiming it are the same people. During that same period the perceived cost of collecting signatures — introducing legal distance into a relationship built on trust, incurring counsel fees, imposing procedure on a team still forming — exceeds its perceived benefit. The difficulty lies not in the shortcut itself but in the shortcut persisting after the condition that justified it has dissolved: as the team grows, as freelancers enter the workflow, and as the company delivers its first contracted product, ownership becomes a practical question, yet because no signing reflex was ever institutionalised, what accumulates instead is a backlog requiring retroactive remediation.
A second layer of the mechanism concerns scope, in that the instrument which does exist usually reaches less far than assumed. A standard assignment clause embedded in an employment agreement ordinarily carries only work product created after the commencement of employment and within the scope of the role as defined. That definition fractures in three places: the initial codebase and design created by founders before the entity was incorporated, side tools built by an employee outside the role definition but using company resources, and — most commonly of all — everything produced by freelancers, agencies and consultants with whom no employment relationship exists at all. In many jurisdictions, ownership of contractor work product remains with the creator unless an express written assignment has been executed; the fact that an invoice was issued and paid does not, on its own, move title. The company assumes ownership follows payment, whereas the legal position treats ownership as following execution.
What the reviewing side is actually doing under this heading is not reading a policy text but attempting to close a chain. The object of the exercise is an overlap between two lists — the people who contributed to the creation of the product and of core processes, and the executed assignment instruments on file — with every name appearing on the first list and absent from the second recorded as an open item requiring resolution. In a well-constructed structure the answer to the question is therefore located at file level rather than delivered verbally: who signed, on what date, covering what scope, under which version of the form, where the instrument is stored, and who has access to it. Accessibility functions as a quality indicator alongside existence, since a signature sitting in a box but not retrievable within three days is treated, on a data room calendar, as a signature that does not exist.
What the implementation dimension measures is whether execution is an exceptional event or an embedded step in a standing workflow. Between an assignment executed as an inseparable part of the first-day document set within the onboarding package, and one circulated in bulk once a financing process has commenced, there may be no difference in legal validity; from a review perspective, however, the two carry entirely distinct signals. Retroactively collected signatures produce visible date clustering, and once date clustering appears the questions change immediately: who declined or failed to sign, how many departed employees could not be reached, and whether the work product created by those unreachable contributors still sits inside the shipping product. Obtaining a retroactive signature from a former employee is an order of magnitude harder than obtaining one from a current employee, and in practice it frequently converts into a negotiation with a price attached.
Measurement is generally the weakest link under this heading, largely because few companies regard IP assignments as a measurable domain at all. The relevant metric is nonetheless extremely simple, consisting of the ratio between two counts: the total number of active and former contributors to the product and to core processes, and the number of those contributors covered by an executed assignment. Where that ratio is reported on a regular cadence, scope exposure is not a surprise but a known and declining balance; where it is not reported, the magnitude of the exposure is discovered for the first time during review, which is to say at the moment of lowest negotiating leverage. The same measurement becomes considerably more informative when maintained alongside a third-party component inventory, since open source licence obligations and employee assignments are two faces of a single question — who holds rights in the shipped product.
What the ownership dimension seeks is a name, and that name should not be a founder's. Absent a designated party deciding which version of the assignment form governs, which schedule attaches to a new contractor engagement, and what happens when an employee submits an invention disclosure falling outside the role definition, those decisions are not made at all — they are deferred. Ownerless territory manifests here not as visible delay but as silent accumulation: each new hire and each new agency engagement enlarges the balance slightly, and no stage of the process generates an alarm. The reviewing side asks for the responsible party for precisely this reason; where the answer is the founder's name, the heading is recorded under founder dependency, and that entry migrates out of the intellectual property section into the governance section, where it feeds a considerably broader discount discussion.
The channel through which the deficiency reaches valuation rarely runs through the multiple, contrary to common assumption; an IP gap that halts a transaction outright generally arises only where the gap sits in the core of the product itself. Typical transmission occurs at three points: a remediation obligation added to the conditions precedent list, requiring the seller to collect retroactive signatures before closing; an expansion in the scope and survival period of the intellectual property representations and warranties; and an upward adjustment to the escrow percentage backing those warranties. Taken together, the three alter the cash the seller actually receives and the timing of that cash without touching the headline price. A further channel operates on a longer horizon: where the acquirer's own insurers or lenders identify the same exposure independently, post-closing integration milestones become tied to its remediation, with the practical consequence that the founder's earn-out trigger is attached to work substantially outside the founder's control.
The mechanism that neutralises this tendency is not individual vigilance but a recording discipline embedded in the workflow itself, and a functioning structure comprises four separable components. The first is a contributor inventory holding every person who has contributed to the product or to core processes — employee, contractor, agency, consultant, founder — on a single list, independent of employment status. The second is a mapping register linking each row of that inventory to an executed assignment and rendering unmatched rows visible rather than latent. The third is a form of instrument that expressly addresses the pre-contract period, work product created outside the role definition, and the licensing of pre-existing rights carried in by the contributor. The fourth is a gate that makes execution a completion condition of the hiring and contractor onboarding flows, such that system access is not granted before the instrument is signed.
BEIREK's intervention under this heading begins not with the delivery of a policy text but with the establishment of a rhythm in which those four components operate. The contributor inventory is reconstructed by cross-reading repository contribution history, payroll records, procurement and invoice records, and the contract archive; rows in that inventory without a matching instrument are then classified by difficulty of closure — currently employed, departed but reachable, unreachable — with a distinct remediation path defined for each class. The exposure balance is subsequently installed as a standing line in management reporting, so that by the time a transaction calendar begins, the balance is not a finding discovered during diligence but a figure demonstrably declining over preceding months. The decisive point is that the rhythm attaches to the hiring and procurement flows rather than to the founder's memory; the intervention succeeds only where a new contractor cannot begin work unsigned while the founder is out of the room.
Continuity is tested at exactly that point: whether the structure produces the same outcome once the person who built it withdraws from the process. Cleaning an intellectual property chain once is sufficient to carry a company past a specific moment of review; if the same company reopens the chain six months later upon engaging three new agencies, the cleanup was an event rather than a capacity. Distinguishing between the two is precisely what the reviewing side is attempting, and the method employed is usually blunt — the file is requested for the three most recently hired individuals and the two most recently engaged contractors. Those five documents carry more information than a thousand pages of policy, since they demonstrate whether the structure operates today rather than whether it operated at some point in the past.
What determines a company's valuation is frequently not the magnitude of the value it creates but whether that value can be shown, independent of the founder, to belong to the company; intellectual property assignments are the plainest, cheapest and most consistently neglected instrument of that demonstration. The ratio between the cost of obtaining a signature and the cost of its absence at the closing table is sharper here than in any other line item of institutional readiness. The operative question is therefore narrow: if the list of people currently contributing to the product were drawn up today, how many rows would carry an executed instrument beside them, and who inside the company knows what that ratio is.