Startup legal basics every founder should know (updated 2026)
Most founders hit their first legal crisis around month six. Not because they did something obviously wrong. Because they did something everyone else does: they built first and figured out the legal stuff later.
I've made that mistake. Twice. And I've watched founders inside the Devlyn.ai and Laracopilot communities make it in ways that cost them equity, IP ownership, and in two cases, their entire company.
The startup legal basics every founder should know are not complicated. They're just boring. Which is why most people skip them until it's expensive not to.
This guide covers what actually matters: entity structure, IP assignment, equity mechanics, the contracts you need on day one, and the common mistakes that blow up cap tables and co-founder relationships years into the journey.
The startup legal basics for founders are not a one-time checklist. They're the foundation your company stands on. Get them right early, and everything else compounds. Get them wrong, and you'll spend money you don't have fixing problems you didn't know you created.
Why founders get legal wrong from the start
The default founder logic goes like this: "I'm not making money yet. Legal fees are expensive. I'll sort it out when I raise."
That logic breaks down the moment you have a co-founder, a paying customer, or a line of code that matters.
I was building a SaaS side project in 2022 with a friend. We agreed on a 50/50 split verbally. We built for four months. We brought in our first paying user. Then my co-founder left for a full-time job. We hadn't signed anything. We had no vesting schedule, no operating agreement, nothing. It took three months of uncomfortable conversations and a mediator to untangle what should have been a two-page co-founder agreement.
The cost of delay is not a flat fee
The typical founder mentality is: "legal costs money, I'll delay." The reality is that every day you delay without proper structure, you're accruing liability. A verbal equity agreement costs $0 now and potentially $50,000 to unwind later. An unregistered trademark costs nothing today and costs your brand tomorrow.
The founders who win at this start with a $1,500 incorporation and $500 of template agreements. Not $20,000 of lawyers. Just the right documents in the right order.
Choosing the right entity structure
The entity question is simpler than lawyers make it sound. For most US-market SaaS founders, the answer is a Delaware C-Corp. Not an LLC. Not an S-Corp. Not a sole proprietorship.
Here's why C-Corp is the default:
- VCs and institutional investors require it. They cannot hold equity in an LLC under their fund structures.
- Delaware law is the most established, most founder-friendly corporate law in the world. Judges and lawyers know it.
- Stock options (ISO/NSO) require a corporation, not an LLC.
- Dual-class share structures (if you ever want them) are cleaner in C-Corp land.
If you're building a bootstrapped lifestyle business with no intention of raising, an LLC in your home state is fine. But if there's any chance you'll raise venture money, take it seriously and start with a Delaware C-Corp.
When LLC actually makes sense
Two scenarios where I'd pick LLC over C-Corp: consulting businesses with no equity components, and real estate or asset-heavy businesses where pass-through taxation matters more than equity structure. For software, for SaaS, for anything with investors on the horizon, skip the LLC debate.
Offshore founders: you still need a US entity
I'm based in India. Laracopilot is incorporated in the US as a Delaware C-Corp. If you're building for the US market, raising from US investors, or selling to US customers, a US entity is not optional. It signals seriousness and removes friction from every future transaction.
Getting a US entity as an offshore founder is easier now than it's ever been. Stripe Atlas, Firstbase, and similar services let you incorporate a Delaware C-Corp remotely for $500 or less. There's no excuse to skip it.
IP ownership: the mistake that kills acquisitions
Here's the IP mistake that actually ends companies: a developer writes code before they sign an IP assignment agreement, and then leaves. Now that person owns a portion of your codebase. When you go to sell your company, the acquirer's lawyers find it, and the deal either dies or reprices by millions.
Every person who touches your product must sign an IP assignment agreement before they write a single line of code. Co-founders, contractors, early employees, everyone. This is non-negotiable.
The IP assignment agreement does one thing: it says that anything created in connection with the company belongs to the company, not the person who created it. Courts do not assume this automatically. You need the paperwork.
What to include in IP assignment agreements
- Assignment of all IP created during the engagement
- Work-for-hire clause (belt and suspenders)
- Non-compete clause (where legally enforceable in your jurisdiction)
- Confidentiality provisions
- Prior inventions disclosure (so contractors can carve out what they owned before)
The prior inventions disclosure matters. If a contractor is bringing something they built before they worked with you, they need to disclose it upfront. If they don't, and you build on top of it, you have an ownership ambiguity problem.
Trademarks: register sooner than you think
Most founders register their trademark after they've grown. That's backwards. A trademark is first-filed in most jurisdictions, which means someone can register your brand name before you do if you wait too long.
I registered the Laracopilot trademark before we launched publicly. It cost less than $500 in filing fees. One competitor had already filed a similar name in two classes when we checked. We got ours in first for our primary class.
If you're serious about your brand, file a trademark application in the US within the first six months. You can use a service like Trow & Rahal or just file directly with the USPTO for around $350 per class.
Ready to build your startup the right way? Subscribe to the weekly growth newsletter for founder playbooks, legal templates, and lessons from building Devlyn.ai and Laracopilot.
Equity and vesting: the math that matters
Most co-founder relationships fail not because of personality conflicts, but because of equity mechanics. Specifically: someone receives equity with no vesting, contributes for six months, then leaves with 30% of the cap table.
The standard vesting schedule is four years with a one-year cliff. That means: nothing vests until you've been at the company for a full year. Then 25% vests at month 12, and the remaining 75% vests monthly over the following 36 months.
The cliff protects you from the co-founder who loses interest at month three but still owns a third of your company.
What most founders get wrong about vesting
They apply it to co-founders but not to themselves. As a founder, you should also have vesting on your own shares, because investors will require it anyway. If you don't set it up now, investors will reset your vesting when they come in, and you'll be starting your clock over at a lower ownership percentage.
Set up founder vesting at incorporation, with a reasonable acceleration clause for acquisitions. Double-trigger acceleration (where you need both an acquisition and a termination to vest fully) is the standard investor-friendly approach.
Meet Marcus, who skipped co-founder vesting
Marcus launched a fintech startup in 2023 with two co-founders. They agreed on a 33/33/34 split. No vesting. By month eight, one co-founder had moved to London and was contributing maybe two hours a week. He still owned 33% of the cap table. When Marcus went to raise a pre-seed round, the lead investor's first question was: "Why does someone contributing two hours a week own a third of your company?" The deal terms shifted significantly.
Marcus spent $8,000 in legal fees renegotiating the cap table structure. A $200 co-founder agreement with standard vesting would have solved it on day one.
The contracts you need before month three
You don't need a 50-page contract for everything. But you do need specific documents early.
Co-founder agreement: Covers equity, vesting, roles, decision-making authority, what happens if someone leaves, and IP ownership. Use a template from Clerky or Y Combinator's free documents. Have a lawyer review it for $500-$800.
IP assignment agreement: As covered above, required for every contributor before they start.
Customer agreements / Terms of Service: The moment you have a paying customer, you need ToS. Not a contract. A ToS covers scope, payment, limitation of liability, and IP ownership of deliverables. Without it, a customer can claim ownership of what you built for them.
Privacy Policy: Required by law in most jurisdictions if you collect any personal data. If you have users in California (CCPA), Europe (GDPR), or Canada (PIPEDA), a Privacy Policy is not optional.
Contractor/Freelancer agreements: Every contractor needs a written agreement before they start. Include scope, payment terms, IP assignment, and confidentiality.
What you can skip early
You don't need a formal employment handbook until you have five or more employees. You don't need a full shareholder agreement until you raise your seed round. You don't need a board charter until you have a board. Start lean and add structure as the company earns it.
For founders building with Devlyn.ai engineers on a technical project, our team handles the NDAs and IP assignment paperwork as part of the engagement setup. That's one less legal headache when you're moving fast. You can learn more at Devlyn.ai.
The cap table: keep it clean or pay later
A clean cap table means: few shareholders, simple share classes, no dead equity (people who left but still own shares).
The companies that get acquired cleanly have simple cap tables. The companies that die in due diligence have complicated ones: five share classes, vesting schedules with no documentation, convertible notes from 2019 that nobody remembered, and three former employees who own shares but can't be reached.
Convertible notes and SAFEs
If you're raising pre-seed capital, the standard instrument is a SAFE (Simple Agreement for Future Equity), not a convertible note. Y Combinator created the SAFE and it's now the industry default. It's simpler, cheaper to execute, and doesn't accrue interest.
Use the standard YC post-money SAFE. Don't customize it. Every custom term you add creates complexity, slows down the round, and costs you in legal fees. Investors who've seen hundreds of SAFEs know when something has been modified, and they'll price that risk.
Sarah's cap table disaster
Sarah raised $200,000 on three different convertible notes over 18 months, each with different discount rates and valuation caps. When she went to raise her seed round, the lead investor ran the conversion math and found the cap table would be 40% owned by note holders before she issued a single share to new investors. The deal fell apart. She had to go back to all three note holders and renegotiate, which took four months.
The fix: use one standard SAFE instrument at the start. If you need to raise from multiple angels, use the same SAFE document with the same terms for every investor in the round.
Startup legal basics checklist for 2026
Use this before you go further:
- Incorporate as a Delaware C-Corp (or equivalent for your market)
- Issue founder shares with four-year vesting, one-year cliff
- Have every co-founder, contractor, and early employee sign an IP assignment agreement before contributing
- File a trademark application for your brand name within six months of launch
- Set up a basic ToS, Privacy Policy, and contractor agreement template before you have your first customer
- Use a SAFE (not convertible note) for any pre-seed raises
- Keep your cap table in Carta or a similar tool from day one
None of these require a $500/hour lawyer. Most can be done with Clerky, Stripe Atlas, or Y Combinator's free document library. Spend $1,500 to $3,000 early, and you'll avoid spending $30,000 to $150,000 fixing it later.
Conclusion
The startup legal basics every founder needs are not sophisticated. They're basic structures that protect what you're building. Entity, IP, equity, and contracts. That's it.
The founders who get this right treat legal as infrastructure, not overhead. They set it up once, maintain it consistently, and then stop thinking about it, because the foundation is solid.
If you're building a SaaS, get incorporated, get the IP assignments signed, and get your co-founder vesting in place before you write your next line of code. Everything else, including hiring, fundraising, and scaling, gets easier when the legal foundation is clean.
I write about building companies, SaaS growth, and what actually works at the founder level every week. Join the newsletter at alpeshnakrani.com/newsletter for actionable content, not recycled advice.
If you're building a technical product and need a senior development team that understands founder constraints, Devlyn.ai is built for exactly that. Senior-only engineers, no vendor lock-in, and a team that ships.
Alpesh Nakrani is VP of Growth at Devlyn.ai and Laracopilot. He writes about SaaS growth, founder strategy, and AI-enabled development at alpeshnakrani.com.