top of page

Resources

IP Basics for Founders

Pink Oyster Mushrooms

Related Posts

Frame 37.jpg

17.11.26

Resources

IP Basics for Founders

Frame 37.jpg

29.9.26

Resources

Swiss Transparency Register

Frame 37.jpg

24.9.26

Resources

Founder Separation Checklist

Frame 37.jpg

24.9.26

Insights

Founder Breakups in Startups 

Frame 37.jpg

21.9.26

Insights

Who Could Buy Your Startup, and Are They Serious?

Frame 37.jpg

1.9.26

Insights

When Is the Right Time to Sell Your Startup?

Frame 37.jpg

7.8.26

Success Stories

Riverkin: Securing Non-dilutive Funding to Accelerate Hydropower Market Entry

Frame 37.jpg

23.6.26

Insights

Selling a Company: What Actually Decides the Deal

Frame 37.jpg

15.6.26

News

Alfred Welcomes Dorian Ebneter to Our Business Consulting Team

Subscribe to The Source

Sign up now to receive periodical Alfred updates, resources and insights, direct to your mailbox

cta.jpeg

Ready to take your vision to the next level?

Email us at info@alfred.ch or schedule a free introductory call to discuss how we can support you.
13 minutes ago
7 min read

"Your IP is crucial." You’ve heard it a thousand times, but what does it actually mean for your day-to-day? Is it just a legal checkbox, or is it the literal floor your startup is built on?


In this guide, we’re stripping away the legal jargon to give you a direct, no-nonsense overview of what Intellectual Property (IP) is, how to own it, and why messing this up is the fastest way to kill a VC deal.


1. The 4 Asset Classes of IP


IP is an umbrella term for "intangible assets produced by human creativity". For a startup, these intangible assets usually fall into 4 main asset classes. Here is how the asset classes work and what you need to do to secure them:


  • Copyright: protects original creative content made by a person (”works of authorship”), e.g. books, music, films, photographs, artwork and software.

    • In tech, this is primarily your source code, but also includes UI design, manuals, and marketing copy.

    • Requirement: protection is automatic the moment the work is created. The work is officially created as soon as it is recorded in a sufficiently permanent form (e.g. written down, filmed, photographed, digital file, recorded audio). An idea as such, with no permanent form, is not protected. But, the good news, you don't have to register copyrights, but you must be able to prove who wrote it and when. In other words, copyrights protect the original expression on a medium, not the underlying idea itself.


  • Trademarks: protects your brand identity, e.g. your company name, brand name, logo and slogans.

    • Requirement: protection requires registration with a national and/or international trademark office (like the USPTO or IPI). It’s not enough to just own the .com. Trademark protection is territorial, meaning that it only applies in the country where you have registered a trademark.


  • Patents: protect new and inventive products, processes or technical solutions (e.g., a new hardware sensor or a unique algorithm).

    • Requirement: protection requires a formal application with the relevant national patent office and the patent must be granted. The product, process or technical solution must be new, involve an inventive step (meaning its not obvious to a skilled person) and be capable of practical or industrial application. A mere idea is not patentable.

    • Pro tip: Do not publicly disclose your tech before filing, or you lose the right to patent it. Disclosing it to third parties may destroy its feature of being “new” (have NDAs, don’t post it in ChatGPT/Claude, etc.).


  • Trade Secrets: protect confidential business information that provides a competitive advantage, e.g. formulas, processes, methods, customer lists and business strategies.an example of a very famous trade secret, the Coca-Cola formula.

    • Requirement: protection does not require registration, it applies once the information is secret, has commercial value because it is secret and is protected through reasonable confidentiality measures. These measures may include limiting access, using passwords, marking documents as confidential, and entering into non-disclosure agreements. Protection lasts as long as you keep it secret. If it becomes public, is independently developed, or is lawfully reverse-engineered, trade secret protection generally cannot prevent its use. In other words, trade secrets protect valuable confidential information against unlawful acquisition, use, or disclosure—not against someone discovering the same information independently.


  • Domain Names: secure your online address, e.g. yourcompany.com or yourbrand.ch.

    • Requirement: you must register the domain through a domain registrar and renew it to keep it. Registration covers only that exact domain: owning the .com does not automatically secure the .ch or other extensions. It does not grant trademark protection, and your domain must respect existing third-party rights.


2. The "Fugazi" Factor: did we create IP and who owns it?


Founders spend endless nights building products, writing code, creating decks, and refining ideas together with their employees, with advisors, with friends or with old professors. But here’s the uncomfortable question: Who came up with what and who actually owns all of this at the end? If your answer to this question is unclear, that’s a problem.


From day one, all IP should clearly land in one place: your startup. Think of the company as the container that holds everything of value.


This applies to everyone involved:

  • founders,

  • employees,

  • freelancers and agencies,

  • interns,

  • advisors and board members,

  • old professors,

  • friends, etc.


By default, the IP stays with the individual who created it. Special statutory rules in employment relationships automatically assign computer codes, inventions and design created in the performance of contractual duties directly to the employer (aka your startup). These statutory rules, however, neither provide a comprehensive allocation of all IP rights of your employees to your startup, nor cover non-employees (e.g. freelancer, board members, friends).


In order to confidently say, all different types of IP rights belong to your startup, you need written, explicit IP assignment declarations from all the individuals you included in working on your startup (this can be done in stand-alone IP assignment declarations or proper state-of-the-art IP clauses in an employment agreement, advisor agreement, freelancer agreement etc.).


How to move IP to your company:

  • Founder Contribution: Even before incorporation, sign a simple IP Transfer Agreement that moves everything you’ve built pre-incorporation as a founder to the company.


  • IP Assignment Clauses for Employees: Every employment contract and founder agreement must have a "Present Assignment" clause. It should say: "I hereby assign all rights, title, and interest in any IP created..."


  • IP Assignment Clauses for External Help: Contractors, interns, and agencies don't automatically give you the IP just because you paid them. You must have a written agreement stating that the work is a "work made for hire" or explicitly assigning the IP to you.


The "Academic" Trap:

If you are an ETH spin-off or stemming from a university lab, be careful. Universities often have "IP Bylaws" that claim ownership of anything created using their resources. You may need a formal License Agreement or a Buy-out to move that IP from the lab to your startup.


3. Commercial Agreements: Don't Give Away the Farm


When you sign your first big customer, they may send you a contract saying they "own all deliverables". Red flag - if your “deliverables” include your core technology, reusable tools or future improvements. Define exactly what the customer receives and which rights your business retains.


  • SaaS Models: You are providing a service, not selling the code. Your contract should preserve your ownership of the platform, underlying code and improvements to your technology, including those developed during the customer project. The customer receives access to and a license to use the software, but you must retain ownership of all your existing technology and any "Improvements, Enhancements, and Feedback".


  • Standard Hardware: You sell the physical product, while your startup retains ownership of the underlying hardware IP, including its designs, technical drawings and proprietary technology. Any embedded software is licensed to the customer for use with the product. Your terms should clearly distinguish ownership of the physical product from ownership of the underlying IP and define the customer’s rights to use the embedded software.


  • Custom Hardware: Distinguish Background IP—technology, software, designs, tools and know-how developed before or independently of the project—from Foreground IP, meaning results created during the project. These labels do not determine ownership by themselves. Agree who owns each category of results, including customer-specific designs and improvements to your core technology. If the customer receives ownership of particular results, preserve your ability to reuse agreed generic components and know-how. Give the customer the rights needed to use any Background IP embedded in those results.


  • Joint Developments: Working together does not automatically mean everything is jointly owned. Agree in advance how to allocate results created by each party and results created jointly. A practical approach is for each party to retain its Background IP, with ownership of new results allocated by technology or contribution and appropriate licences granted to the other party. Joint ownership should be a deliberate choice: it can make future licensing, investment or a sale more complicated. If you agree to Joint IP, “we own it together” is not enough. Specify who may use it, modify it, license it to third parties, transfer their interest and enforce the rights. Agree who controls patent filings, pays protection and maintenance costs, receives licensing revenue, and what happens if the relationship ends or the parties disagree.


The commercial goal: Give the customer sufficient rights to benefit from the deal while preserving your ability to develop, reuse and commercialise your technology.


4. Why This Matters


IP isn't a theoretical legal problem; it’s a valuation problem.


For example, when an investor does Due Diligence, they look for "holes" in your IP bucket.


If a former co-founder left without signing an IP assignment, or if you used a university lab without a license, you have a "Cloud on Title". Investors dislike this. It can:


  1. Lower your valuation: They’ll price in the risk of a future lawsuit.

  2. Kill the deal: If the core tech isn't owned by the company, there is nothing for them to invest in.


Or, if you do not own or have sufficient rights to use the IP your business relies on:


  • your ability to develop and commercialize your product may be restricted;

  • competitors or former collaborators may assert rights that prevent you from using key technology, content or branding.


5. The Tax "Heads-Up"


IP has a dollar value. If you create IP in a Swiss subsidiary but then decide to move it to a US Holding company later when the company is worth $50M, the tax authorities might view that as a "sale" and hit you with a massive tax bill.


The Golden Rule: Place your IP in the right "container" (the entity where it will live long-term) as early as possible, before the value skyrockets.


6. Final Thoughts


IP won’t build your product for you—but without it, you may not actually own what you’re building. Getting the basics right early is usually simple, relatively cheap, and tremendously reduces risk later on. And if something feels unclear, it probably is.


Don't wait for the due diligence report to find out you have a leak. Whether you're navigating a university spin-off or drafting your first employment contracts, reach out to us to make sure your foundation is rock solid.


The Team

Thierry Barbey, Founding Partner (Legal) & CEO
Thierry Barbey, Founding Partner (Legal) & CEO
Audrey Benzow, Senior Associate (Legal)
Audrey Benzow, Senior Associate (Legal)
Thomas van Gammeren, Associate (Legal)
Thomas van Gammeren, Associate (Legal)


Comments


Commenting on this post isn't available anymore. Contact the site owner for more info.
bottom of page