Purpose before disclosure
Both parties should understand why information is requested, how it will be evaluated and who will receive it before valuable knowledge is shared.
A practical conversation framework for founders and established companies before ideas, technology, time and trust are placed at risk.
Corporate–startup partnerships combine different resources, cultures, timelines and levels of negotiating power. Those differences can create innovation—but also misunderstanding and unnecessary risk.
The standard is designed to help both sides ask important questions early. It is not a contract, certification or substitute for independent legal advice. It is a shared starting point for a more transparent commercial conversation.
Each principle should be discussed before a pilot, investment, source-code review, data exchange or other material commitment.
Both parties should understand why information is requested, how it will be evaluated and who will receive it before valuable knowledge is shared.
Products, code, data, customer relationships and intellectual property brought into the relationship remain clearly identified and owned by the contributing party unless otherwise agreed in writing.
The parties should agree how jointly created intellectual property, improvements, insights and commercial opportunities will be owned or licensed before development begins.
Each side should identify who can approve scope, budgets, technical access, continuation and termination—so neither party is trapped in an endless process.
Pilots should have defined deliverables, dependencies, success measures and response times that reflect the resources and constraints of both organisations.
Payment, market access, data, expertise, references or other benefits should be described honestly. Exposure alone should not disguise unpaid commercial work.
Any exclusivity should have a clear purpose, narrow scope and defined duration. It should not prevent a startup from financing or operating its business without fair compensation.
Confidentiality obligations should be proportionate, understandable and mutual where appropriate, without blocking either party from using knowledge it already possessed.
The agreement should explain what happens to access, data, materials, licences, unfinished work and public references if the partnership stops.
Neither party should use the other’s code, materials, brand, data or confidential contribution outside the agreed purpose without documented permission.
Use the principles to prepare questions, identify gaps and decide what must be clarified before sharing valuable information or accepting restrictions.
Use them to design transparent engagement models, set realistic expectations and demonstrate that your organisation is prepared to work responsibly with smaller companies.
Use the framework in accelerators, investment processes and partnership programmes to create a common language before individual agreements are drafted.
Corporate Startup Partnership will refine these principles as we learn from founders, corporations, investors and advisors. Supporting the standard does not certify a company or guarantee the outcome of a particular partnership.
Have experience that could improve it? Share your perspective privately. Please do not send source code, trade secrets or sensitive personal data.