Intellectual property

Own whatyou build.

Make sure the company’s ownership story matches the product it is building.

01 / THE PROBLEM

The company uses the work. But does it own the rights?

Code and creative work do not necessarily belong to a company simply because it paid for them. Trace contributions, earlier work, and third-party licenses. Written assignments and appropriate licenses help connect the product to the entity.

+02 / COMMON FRICTION

Small gaps.Bigger questions.

01Code written before incorporation

02Unsigned contractor assignments

03Untracked third-party licenses

04Pre-existing IP left undefined

03 / HOW ETHAN CAN HELP

Understand the business.
Then the documents.

Start with your objective and the documents already in place. Identify the decisions that need attention, discuss practical options, and coordinate the work needed to move forward.

+04 / WHAT THE SERVICE MAY INCLUDE

The workbehind the next step.

Founder IP assignment
Contractor IP assignment
Employee invention assignment
Software ownership and licensing
Confidentiality and pre-existing IP

The scope is agreed for each engagement. Some questions may require coordination with tax, employment, or other specialist advisers.

05 / WHERE IT FITS

FORM↗BUILD↗HIRE↗RAISE↗

07 / WHEN YOU MAY NEED THIS

Bringing pre-incorporation code into the company?↗Engaging an outside development team?↗

+FOUNDER FAQ

Good questions.Clearer next steps.

General information only.
Not legal or tax advice.

Who owns code written before incorporation?

Ownership depends on authorship, employment, prior agreements, and other facts. Incorporation alone does not transfer earlier code; identify the rights and document an appropriate assignment or license.

Who owns code created by a contractor?

Payment alone does not necessarily transfer copyright. Work-made-for-hire rules are limited. Review a written assignment, licenses, and any pre-existing or third-party code.

+FROM PRODUCT TO BUSINESS