An In-Depth Analysis of IP Contribution and Valuation Clauses in the Software Industry
Editor’s Note: In the software startup space, “technology-based contribution” (contributing technology as capital) has become one of the most common forms of capital contribution. A programmer brings code they developed to an investor, and the two hit it off immediately — the founder contributes the code at a valuation of RMB 10 million for a 60% stake, while the investor puts in RMB 5 million in cash for a 40% stake. Yet once due diligence goes deep, the investor falls silent: is this pile of code really worth RMB 10 million? How much belongs to the company and how much to the individual? If the code has “hidden defects,” who bears the risk? These are exactly the questions this article unpacks one by one.
I. Case Introduction: A “Breakup” Triggered by Code Valuation
In 2024, in the Series A financing of an AI startup, the founder Zhang San (pseudonym) contributed a set of SaaS product code “80% developed” as technology capital. An appraisal institution issued a report valuing it at RMB 12 million, on which basis Zhang San held 60% of the company’s equity. The investor contributed RMB 8 million in cash for a 40% stake.
However, within three months of closing, problems surfaced one after another: first, the product’s core module had serious performance defects requiring substantial rework; second, the code made extensive use of a certain GPL open-source component, creating compliance risk; third, when Zhang San left his former employer, some of the code he developed bore a high degree of similarity to that employer’s works made for hire, and the former employer had already sent a lawyer’s letter asserting its rights.
The investor demanded that Zhang San bear the supplementary contribution liability for the inadequate contribution, and the conflict escalated. Ultimately, the case ended with Zhang San transferring his equity to the investor at a discount and exiting the company. This case exposes a series of core legal issues in technology-based contribution in the software industry.
II. Statutory Interpretation: The Legal Framework for Technology-Based Contribution
(1) Article 48 of the Company Law: Core Rules on Non-Monetary Contribution
Company Law of the People’s Republic of China, Article 48
A shareholder may contribute capital in currency or in non-monetary property such as tangible assets, intellectual property, land-use rights, equity, and creditor’s rights that can be valued in currency and lawfully transferred; provided that property which laws or administrative regulations prohibit from being contributed as capital is excluded.
The non-monetary property contributed as capital shall be appraised and verified, and shall not be over- or under-valued. Where laws or administrative regulations provide for appraised valuation, such provisions shall prevail.
The newly revised Company Law (effective July 1, 2024) explicitly lists “intellectual property” as a lawful form of contribution and expands the categories of non-monetary contributions (adding “equity” and “creditor’s rights”). As an object protected by copyright, software code constitutes intellectual property that can be lawfully transferred and thus may serve as contribution. However, it must satisfy two core requirements: first, “it can be valued in currency,” and second, “it can be lawfully transferred.”
(2) Article 18 of the Copyright Law: The “Minefield” of Work-for-Hire Ownership
Copyright Law of the People’s Republic of China, Article 18
A work created by a natural person in fulfillment of the tasks assigned by a legal person or unincorporated organization is a work made for hire. Except as provided in paragraph 2 of this Article, the copyright is enjoyed by the author, but the legal person or unincorporated organization has the right of priority use within the scope of its business. …
Where a work made for hire falls under any of the following circumstances, the author enjoys the right of authorship, while the other rights of copyright are enjoyed by the legal person or unincorporated organization, which may reward the author:
(1) a work created principally with the material and technical resources of the legal person or unincorporated organization and for which that organization is responsible … computer software …
This is the most easily overlooked “time bomb” in technology-based contribution in the software industry. Under this provision, computer software is a “special work made for hire” — if it is created principally using the former employer’s material and technical resources, the copyright belongs to the former employer and the author enjoys only the right of authorship. This means that if a founder contributes, shortly after leaving, code highly similar to the former employer’s, the former employer can fully assert its rights, leaving a material defect in the contributed asset.
(3) Regulations on the Protection of Computer Software: Special Rules on Software Copyright Contribution
Regulations on the Protection of Computer Software, Article 8
The software copyright owner enjoys the following rights:
(1) right of publication; (2) right of authorship; (3) right of modification; … (6) right of rental; (7) right of communication through information networks; (8) right of translation; (9) other rights that should be enjoyed by the software copyright owner.
The software copyright owner may license others to exercise his software copyright and is entitled to remuneration.
The software copyright owner may assign all or part of his software copyright and is entitled to remuneration.
The software copyright owner may assign his copyright in accordance with the law. Contributing software copyright as capital is, in essence, transferring the proprietary economic rights in the copyright to the company in exchange for the corresponding equity consideration. Note that the personal rights in copyright (such as the right of authorship and the right of publication) are inalienable due to their personal nature and cannot serve as the object of contribution, but their use may be authorized by contract.
III. Practical Points: Four Core Issues in Technology-Based Contribution
(1) Valuation Methods for Technology-Based Contribution: What Is the Code Really Worth?
In practice, software intellectual property is mainly valued by three methods:
| Valuation Method | Applicable Scenario | Limitation |
|---|---|---|
| Cost Approach | Based on the development cost of the code, including labor cost and equipment investment | Cannot reflect the market value of the code and is prone to overvaluation |
| Income Approach | Discounts the future economic benefits the code can generate | Relies on future revenue forecasts; early-stage projects face great uncertainty |
| Market Approach | References transactions of comparable technology assets | Few comparable transactions in software; market benchmarks are hard to find |
Lawyer Lin’s Recommendation: For early-stage software projects, a dual assessment using the “cost approach plus income approach” is recommended, with a more conservative valuation as the basis for contribution. Meanwhile, the shareholders’ agreement may provide for a valuation adjustment mechanism (VAM) — that is, if it is later proven that the actual value of the contributed asset is significantly lower than the appraised value, the technology contributor must make up the difference in cash or equity. This resembles an “anti-dilution clause” in the investment context but protects the other shareholders’ interests in reverse.
(2) Warranty Against Defects in the Code: Must the Founder Be “Liable for Life”?
The “warranty against defects” in technology-based contribution means the contributor must warrant that the code contributed is free from title defects and quality defects. Specifically:
1. Warranty against title defects: The contributor must warrant that it enjoys complete, undisputed copyright in the contributed code and that no third-party claim exists. This mainly includes: the code is not a work made for hire (or written waiver from the former employer has been obtained), does not infringe any third-party patent or copyright, and is not subject to any pledge or encumbrance.
2. Warranty against quality defects: The code must run normally and achieve basic functions in the agreed environment. Note, however, that software “quality” is highly subjective — “runs slowly” or “poor architecture” is often a commercial judgment rather than a legal defect. Therefore, it is advisable to specify the technical specification as an appendix to the contribution agreement, concretizing the quality standard.
(3) Linking Performance-Based VAM to Technology Contribution: A New Model
In recent years, an innovative practice has emerged: linking the valuation of technology contribution to key business metrics after the product launches. For example:
- DAU (daily active users) reaches X ten-thousand within 6 months of launch
- The product’s core functions pass third-party security testing
- Customer renewal rate reaches above XX%
If the targets are not met, the technology contributor’s equity will be adjusted by a certain ratio, or supplementary cash contribution will be required. This arrangement directly links “how much the code is worth” with “how well the code works,” which is closer to the reality of startups than a mere asset appraisal.
Note, however: The validity of performance-based VAM clauses remains somewhat disputed in judicial practice. Especially against the backdrop of the five-year paid-in capital system for registered capital introduced by the revised Company Law, the contribution obligation is a statutory duty that cannot be entirely circumvented by a VAM arrangement among shareholders. It is advisable to retain a fallback clause for supplementary contribution in case of inadequate contribution alongside the VAM.
(4) Evidence Guide on Ownership of Works Made for Hire vs. Personal Works
For a technical founder who starts a business after leaving a former employer, proving the code is a “personal work” rather than a “work made for hire” is crucial. It is advisable to build an evidence chain along the following dimensions:
| Evidence Dimension | Key Points to Prove |
|---|---|
| Timing Proof | Git commit history, code logs, and departure certificate — proving the main development was completed after leaving |
| Device Independence | Developed independently on a personal computer with a personal software license, without using the former employer’s equipment |
| Business Difference | The new code is substantially different from the former employer’s product in technical route and business scenario |
| Prior Disclosure | Truthfully disclose the employment history and non-compete status with the former employer during financing due diligence |
IV. Risk Warning: Five “Hidden Pitfalls” in Technology-Based Contribution
Risk 1: An “inflated” appraisal report
Some appraisal institutions, to please clients, issue reports that seriously depart from true value. Under Article 252 of the Company Law, those who contribute capital at an inflated valuation shall be ordered by the company registration authority to make corrections and be fined. More seriously, other shareholders or creditors may claim that the technology contributor bears supplementary liability within the inflated range.
Risk 2: Incomplete code handover
The technology contributor only transfers the executable code but not (or deliberately retains) the source code, architecture documents, deployment manuals, and other key technical materials, leaving the company practically unable to maintain and iterate the product independently. Such a “one-shot deal” contribution essentially means the contributor retains technical control over the company.
Risk 3: Open-source component contamination
The code embeds components under “copyleft” open-source licenses such as GPL and AGPL, exposing the company to the legal risk of being forced to disclose all source code. If the investor fails to detect this during due diligence, the subsequent compliance remediation cost may far exceed the valuation of the technology contribution itself.
Risk 4: Unclear delineation of IP ownership
The founder is simultaneously a shareholder or advisor to multiple companies, and some code may be shared among several entities, blurring IP ownership. Once the company grows, such “legacy issues” become a fatal obstacle before going public.
Risk 5: Value difference between the appraisal date and the closing date
From completion of the appraisal to the actual contribution closing may span several months. For a rapidly iterating software product, the code may have changed materially during this period (version updates, feature additions/removals), so that the code contributed no longer matches the code appraised.
V. Action Recommendations: A Practical Checklist for Founders and Investors
For Technical Founders:
- Isolate IP before leaving: Sign a clear departure agreement with the former employer confirming the IP ownership status at the time of departure. If necessary, obtain a non-assertion letter from the former employer.
- Maintain complete development records: Use a personal Git repository to preserve the full commit history, design documents, and meeting minutes, ensuring the creative process and timing of the code can be proven.
- Complete an open-source compliance audit before contribution: Use professional tools to scan the open-source components in the code and their license types, and address the replacement or compliance of “strong copyleft” components such as GPL in advance.
- Choose a qualified, legitimate appraisal institution: Do not, for convenience or cost, choose an institution that “issues reports fast.” A solid appraisal report is an important defense against future liability.
- Accept a reasonable valuation adjustment mechanism: Rather than insist on an inflated valuation, accept phased vesting or a performance-based VAM arrangement, which instead demonstrates the founder’s confidence and good faith.
For Investors:
- Front-load technical due diligence: Launch technical due diligence — including code security audit, open-source compliance scan, and IP ownership check — before signing the term sheet, not just before closing.
- Add special technology-contribution clauses to the shareholders’ agreement: including the scope of warranty and recourse mechanism, valuation adjustment mechanism, code delivery checklist and acceptance criteria, and the supplementary contribution arrangement for inadequate contribution.
- Require representations and warranties from the technology contributor: specific statements on IP ownership, open-source compliance, and non-compete involved in the technology contribution. Misrepresentation constitutes a breach and may serve as a trigger for exit.
- Watch the founder’s non-compete status: Review the labor contract and non-compete agreement between the founder and the former employer, and assess whether the founding activity may trigger litigation risk.
- Establish code escrow and backup mechanisms: Immediately after contribution, place the code into the company-managed Git repository and set up multi-person access with differentiated permissions to prevent the technology contributor from unilaterally controlling the code.
Conclusion
Contributing software code as technology capital is a common path for startup financing in the software industry and the core arena where founders and investors bargain over interests. The valuation of the code bears not only on how much equity the founder gets, but directly on the adequacy of the company’s capital and the rights and safety of other shareholders.
A good technology-contribution clause does not let one side take all the advantage, but enables both to obtain reasonable protection within the legal framework — the founder can realize the technology’s value and the investor can confidently put in capital. Behind this lie solid due diligence, professional appraisal, and clear contractual arrangements.
Disclaimer: This article represents only the author’s personal views and does not constitute legal opinion or investment advice in any form. For specific legal issues, please consult a professional lawyer.
Lawyer Kevin Jun Lin
Senior Corporate Lawyer · Industry Legal Practice Expert
Contact Phone: 18938871445
Further Reading
If you need professional support in shareholders’ agreements, investment term review, or shareholder disputes, please contact Lawyer Kevin Jun Lin (Shenzhen Corporate Lawyer) for one-on-one consultation.
Leave a Reply