--- title: "Know-How Ownership: Does What the Company Knows Actually Belong to the Company?" description: "Know-how ownership means technical knowledge has been bound to the legal entity both contractually and operationally, evidenced by assignment clauses, dated written records, access controls, and person-independent repeatability. Where those four are absent, an investor prices the knowledge as staff dependency rather than as a company asset, and that judgment enters the deal as discount, earn-out, or key-person condition." url: https://www.beirek.com/en/blog/know-how-ownership-due-diligence canonical: https://www.beirek.com/en/blog/know-how-ownership-due-diligence published: 2026-07-03 modified: 2026-07-03 category: "Intellectual Property" category_url: https://www.beirek.com/en/blog/category/intellectual-property language: en-US reading_time_minutes: 8 publisher: BEIREK LLC publisher_url: https://www.beirek.com license: "© BEIREK LLC — citation with attribution and link permitted" keywords: ["know-how ownership","trade secret protection","intellectual property due diligence","key person dependency","valuation discount","process documentation","IP assignment clauses"] topics: ["Know-how and trade secrets","Intellectual property due diligence","Business valuation and deal structuring","Founder and key-person dependency","Process documentation and institutional memory"] alternate_language_url: https://www.beirek.com/tr/blog/know-how-ownership-due-diligence --- # Know-How Ownership: Does What the Company Knows Actually Belong to the Company? > **In short:** Know-how ownership means technical knowledge has been bound to the legal entity both contractually and operationally, evidenced by assignment clauses, dated written records, access controls, and person-independent repeatability. Where those four are absent, an investor prices the knowledge as staff dependency rather than as a company asset, and that judgment enters the deal as discount, earn-out, or key-person condition. *A company's most valuable technical knowledge rarely appears in any registry; it sits in the heads of a few people, inside a few files, and in the repetition of a few habits. The review table does not question whether that knowledge exists — it questions whether it has been made inseparable from the company, and the uncertainty of the answer reaches the price directly.* --- When a due diligence session reaches the intellectual property heading, the file placed on the table typically consists of registrations: trademark certificates, patent applications where any exist, domain records, license agreements. Once that file has been walked through, the next question — where the production parameters, tooling design choices, pricing logic, or commissioning sequence that make the product different from a competitor's are actually written down — is commonly met with a brief pause, followed by a name. The production manager knows. The founding partner knows. The technician of twelve years knows. That answer is technically accurate, and commercially it has been sufficient, since a meaningful share of the company's current margin is the product of precisely that knowledge. Read from the review table, however, the same answer does not establish that an asset exists; it establishes that the asset does not sit inside the company. A second pattern, visible in the same meeting, is subtler. The company states that its technical knowledge has been written down and shares a folder containing work instructions, quality control forms, and machine setting tables. The documents are present, some of them signed. Yet when the revision dates on those documents are compared against the parameters actually running on the line, the gap tends to spread across several years and several product generations. What is written is no longer what is practiced, and what is practiced is written nowhere. That separation between the documented layer and the operating layer makes visible the question a know-how review is genuinely asking: not whether the knowledge exists, but whether it has been rendered inseparable from the enterprise that depends on it. The mechanism beneath that separation is organizational as much as it is cognitive. Technical knowledge becomes tacit in proportion to how often it is used; a person who has performed an operation enough times pushes most of the steps required to explain it below the threshold of conscious attention, leaving only the outcome available for inspection. The person carrying the knowledge does not experience it as something requiring explanation, because to that person it is self-evident, and the cost of explaining it is immediate and visible while the cost of not explaining it is distributed across years and invoiced to no one. This asymmetry makes the failure to record rational at every individual moment. The difficulty lies not in the shortcut itself but in its persistence after the conditions change — when the company grows, when a second facility opens, when a share transfer comes onto the agenda. The second layer of the mechanism is legal, and it attracts far less attention. A patent or a trademark is a right whose holder is defined at the moment of registration; know-how, by definition, is unregistered, and its protection rests entirely on confidentiality and contract. Ownership can therefore be evidenced only indirectly: through service-invention and assignment clauses in employment agreements, through provisions in subcontractor and design-office contracts binding the output to the company, through confidentiality undertakings signed with advisors, and through access authorization records in the underlying systems. Where any link in that chain is empty — where, for example, the freelance engineer who designed the critical tooling stands in nothing more than an invoicing relationship with the company — the claim that the parameter belongs to the entity becomes difficult to defend the moment a counterparty contests it. The third layer concerns measurement, and it is the one most often never built at all. The contribution of know-how to operating results is, in principle, a traceable quantity: the differential in scrap rate, the first-pass yield, the commissioning duration, the cost of rework, the cycle time of tender preparation. Where those indicators are maintained, technical accumulation stops being an abstract claim to superiority and attaches instead to an observable performance difference. Where they are not maintained, the company's account of its own capability remains at the level of an unverifiable narrative and is recorded at the review table as an assertion rather than as evidence. The distance between assertion and evidence determines, fairly directly, how broadly the representations and warranties will be drafted after signing. The consequence for price is immediate. In a company where know-how ownership has not been established, the buyer locates the source of the acquired margin not in the legal entity but in a handful of employment relationships, which means that part of the consideration is being paid for an asset the buyer will not control after closing. The market tends to manage that exposure by distributing it through the structure rather than by taking a single line-item reduction on price: a portion of the consideration is deferred into an earn-out with key-personnel retention as a trigger, the renewal of employment agreements with assignment provisions is imposed as a condition precedent, a separate heading covering know-how is added to the representations and warranties, and the escrow proportion is raised accordingly. Each of these items functions, from the seller's perspective, as a lengthening of the conversion timetable and a conditioning of collectability. The second channel of cost is quieter and typically surfaces not at the transaction table but during post-closing integration. Where know-how has not been captured, an acquirer wishing to establish a second facility, relocate production to another geography, or move a line to two shifts can do so only by physically dispatching the people who carry the knowledge. The scalability claim breaks at exactly that point: what the investor has purchased is not a repeatable capability but a practice whose repetition requires the same individual every time. Valuation multiples are, for this reason, considerably more sensitive to whether present profitability can be shown to be reproducible independently of the founder than to the level of that profitability itself, and where the demonstration cannot be made, the applied multiple tends to settle visibly below that of a comparable operator with similar margins whose processes have been committed to writing. The ownership dimension sits between those two channels. To own know-how institutionally is for someone to be answerable for it: who decides which knowledge counts as critical, on whom the obligation to update records falls, who runs the handover protocol when an experienced operator leaves, who approves what may be shared with which supplier. Where those questions are left unanswered, the area is left without an owner, and unowned areas revert predictably to the founders; to the extent that the founder remains the decision point, the founder also becomes the sole repository of institutional memory. When a material share of the questions asked during a review is redirected toward a single individual, the finding does not appear anywhere on the organizational chart, but it appears directly in the price. What neutralizes this tendency is workflow design rather than individual discipline. Record-keeping framed as a separate documentation project fails predictably, since it is positioned as a burden sitting outside the real work and is the first thing abandoned in a demanding quarter. Structures that hold are those in which the moment of producing knowledge and the moment of recording it are merged: the final parameter set captured as part of the commissioning approval flow, the root cause and applied correction held in the same record that closes a customer complaint, the acceptance criteria written into an annex of the supplier agreement when a source is changed. Under that design, no one writes an additional document, because the document is itself the condition on which the work is deemed complete. BEIREK's intervention in this area runs along three lines, and the sequence matters. The first is scope determination: the knowledge items actually generating the margin are separated out through structured interviews with technical personnel and direct process observation, distinguishing what is critical from what is merely general, since an attempt to record everything produces the same outcome as recording nothing. The second is closing the legal chain: employment agreements, subcontractor and consultancy contracts, design-office relationships, and supplier disclosures are reviewed, the links that fail to bind ownership to the company are identified, and they are remedied before they can become conditions precedent imposed by a counterparty. The third is operating the recording rhythm: a fixed review interval is established for parameter and decision records, a named owner is assigned to each critical item, and currency of the record is tracked as an auditable indicator. What these three lines produce is not an archive but a chain of evidence. The party sitting at the review table does not expect to be persuaded that technical capability exists; that much can already be inferred from the financial statements. What is being sought is a verifiable trace showing that the capability changes hands together with the company, that it remains in place when individuals depart, and that it can be reproduced at a second facility. Where that trace exists, know-how becomes, for the first time, something that can be discussed as an asset line. Where it does not, the same accumulation continues to be read differently on the two sides of the table: as a claimed advantage on the seller's side and as a priced risk on the buyer's. The most discriminating question that can be asked about a company's technical knowledge is not how deep that knowledge runs, but how many weeks of production performance would come under threat if the person carrying it did not appear tomorrow. Where that question can be answered with a number, know-how ownership has been established; where it can be answered only with a name, it has not, and the difference between the two is, at the transaction table, the price itself. ## Key Points - Because know-how is not a registrable right, ownership can be demonstrated only indirectly — through the contractual chain, access records, and dated internal documentation — and in the absence of that chain the knowledge is treated as belonging to individuals rather than to the entity. - The review table is not seeking proof that technical competence exists; it is seeking evidence that the same result can be reproduced without the person who first produced it. - Undocumented practice is not accepted as verifiable, and institutional memory that resides only in individual recollection is priced as an asset unlikely to survive a change of control. - Know-how left without a named owner reliably reverts to the founders, and that dependency surfaces in valuation as a discount, an earn-out trigger, or a retention undertaking. - The structural answer to know-how ownership is not an archive but a workflow in which recording the knowledge is a condition of completing the work that produced it. ## Questions ### Can know-how be registered like a patent, and if not, how is ownership proven? Know-how is not a registrable right; its protection rests on confidentiality and contract. Ownership is therefore shown indirectly: assignment and service-invention clauses in employment agreements, provisions in subcontractor and design-office contracts binding output to the company, confidentiality undertakings, access authorization records in operating systems, and dated, approved internal documentation of the knowledge itself. Where one link in that chain is empty, the claim that the knowledge belongs to the entity weakens as soon as it is contested. ### What exactly is examined on know-how during a due diligence process? The review proceeds along six directions: whether critical knowledge is defined within the company at all, whether it is supported by current and approved documentation, whether what is written is actually practiced in operations, whether its contribution is tracked through indicators such as scrap rate and commissioning duration, whether each critical item has a named owner with decision authority, and whether the same result can be demonstrably reproduced without the person who first produced it. ### How does undocumented know-how affect the valuation of a company? The effect usually appears not as a single price reduction but as a redistribution through the deal structure. Part of the consideration is deferred into an earn-out with key-personnel retention as a trigger, renewal of agreements with assignment provisions is imposed as a condition precedent, a separate heading is added to the representations and warranties, and the escrow proportion rises. Because the scalability claim also weakens, the applied multiple tends to settle below that of comparable operators with documented processes. ### A process documentation project keeps stalling before completion — what usually explains that? When documentation is framed as a project standing outside the core work, it is positioned as an added burden and is typically abandoned during the first demanding period. Designs that hold merge the moment knowledge is produced with the moment it is recorded: the final parameter set forming part of the commissioning approval flow, root-cause analysis residing in the record that closes a complaint, acceptance criteria written into the supplier contract annex. Under that arrangement the record is not a separate document but the condition of completion. --- Source: https://www.beirek.com/en/blog/know-how-ownership-due-diligence Publisher: BEIREK LLC — https://www.beirek.com