Employment status
Whether the engineer was an employee, independent contractor, volunteer, or founder can affect who owns the work and what compensation rights may exist.
Short Answer
In general, a software engineer who builds a startup MVP alone may have rights related to compensation, ownership of the code, equity, credit, and contract enforcement, but the exact rights depend heavily on the facts. In California, the biggest issues are usually whether the engineer was an employee or contractor, whether there was a written agreement about ownership, whether the work was done within the scope of employment, and whether any promises about pay or equity were made.
If the engineer was hired to create the MVP, the startup may claim ownership of the work under an agreement, a work-made-for-hire arrangement, or other intellectual property terms. If there was no clear contract, ownership can become more complicated, and the facts surrounding who paid for the work, who directed it, and how the parties behaved matter a lot. In general, simply being the person who wrote the code does not always mean the engineer automatically owns the finished product.
The engineer may also have rights if the startup failed to pay promised wages, consulting fees, bonuses, or equity-related compensation. Even if the startup owns the code, payment issues can still exist separately. Likewise, if the startup promised a role, founder status, or stock or options, the terms of that promise may matter if they were specific enough and supported by evidence.
At the same time, there are common risks. A startup may argue that all work belonged to the company, that any outside contributions were assigned away, or that the engineer was working as part of a team agreement rather than as an independent owner. Confidentiality obligations and invention-assignment clauses can also affect what rights the engineer has after the MVP is built.
Because these disputes often turn on written agreements, messages, company formation documents, payment records, and the exact timeline, it is usually important to review the documents before drawing any conclusion. In California, state law and contract principles may matter, but rules can differ in other states.
If the situation involves unpaid compensation, disputed ownership of software, founder equity, or a demand to hand over code or credentials, it may be wise to speak with a California lawyer who handles employment, business, or intellectual property disputes. This page is general information only and is not legal advice.
What This Question Usually Means
This question usually means the engineer built a minimum viable product, or MVP, on their own for a startup idea and now wants to know what they can legally claim. The concern may be ownership of the source code, whether the engineer is owed money, whether they are entitled to equity or founder status, and whether the startup can keep using the product without further permission. It may also involve whether the engineer can keep using the code, show it in a portfolio, or reuse parts of it elsewhere. Often, the real issue is not one single right, but several overlapping issues involving contracts, employment status, and intellectual property.
General Legal Rule
In general, a person who creates software may have some rights in the code they wrote, but those rights can be transferred, limited, or overridden by agreements, employment relationships, and intellectual property rules. If the engineer was an employee, contractor, or cofounder, the startup may claim ownership or a license depending on the terms and the surrounding facts. If there is no written agreement, courts and lawyers often look to payment records, emails, offer letters, equity documents, company records, and how the parties acted. California law can be especially important, but the result depends on the specific documents and facts.
Key Factors
Written agreements
Offer letters, consulting agreements, founder agreements, IP assignment clauses, and equity documents may define ownership, pay, confidentiality, and rights to use the code.
Scope of the work
If the MVP was built as part of assigned work for the startup, the startup often has stronger arguments that it owns or controls the product.
Payment and equity promises
Promises about salary, consulting fees, stock, options, or founder shares may create separate rights if they were specific and can be proven.
Use of company resources
If the engineer used company money, equipment, data, or time, that may affect ownership and compensation arguments.
Confidentiality and trade secrets
Access to confidential business information or trade secrets can limit what the engineer may do with the code or related materials afterward.
Formation and ownership of the startup
Whether the startup was already formed, who incorporated it, and how shares or rights were allocated may matter a great deal.
When to Talk to a Lawyer
It is often a good idea to talk to a California lawyer if the startup claims it owns your code, refuses to pay you, disputes promised equity, asks you to transfer repositories or sign documents, or threatens legal action. A lawyer may also be helpful if the MVP involved sensitive code, trade secrets, or unclear cofounder arrangements. Because these issues can involve employment law, business law, and intellectual property law at the same time, a qualified attorney can help sort out which rules may apply. This page is not a substitute for legal advice, and no attorney-client relationship is created by reading it.
Find California Lawyers
Browse lawyer profiles in California before deciding who to contact about your situation.
Find California LawyersQuestions to Ask an Attorney
- Was I likely an employee, contractor, founder, or something else under California law?
- Do any of my emails or documents suggest that I assigned the code to the startup?
- Could I have a claim for unpaid wages, consulting fees, or other compensation?
- Do the equity promises I received look specific enough to matter legally?
- What evidence should I preserve before I contact the startup again?
- Are there confidentiality, trade secret, or invention-assignment concerns I should know about?
- What risks are there if I continue using or sharing the code?
- Would a demand letter, negotiation, or other non-court approach make sense first?
Documents and Evidence
Emails and text messages
These can show who requested the MVP, what was promised, and whether ownership or equity was discussed.
Contracts and offer letters
These may define your role, payment terms, ownership rights, and any assignment obligations.
Founder or incorporation documents
These can help show who owned the startup, who had authority, and how equity may have been allocated.
Invoices and payment records
These can support claims about unpaid compensation or partial payment.
Code repository history
Version history may help show authorship, timing, contributions, and whether the code was transferred to a company repository.
Screenshots of promises or approvals
These may help preserve informal statements about salary, stock, or ownership before messages are deleted.
Confidentiality or invention-assignment agreements
These documents may affect whether the startup can claim the code or restrict later use.
Legal Disclaimer
This page is for general legal information only and is not legal advice. It does not create an attorney-client relationship. Laws and procedures may change and may vary by jurisdiction. You should talk to a qualified attorney licensed in your jurisdiction about your specific situation.
Community Replies
Users and attorneys can reply here with general information, experience, or attorney commentary.
Members can post a User Comment. Verified attorneys can also post an Attorney Commentary.