Resources for insight and
inspiration
Guides
Insights
Employment Agreements vs. Independent Contractor Agreements: What Founders Should Know
Startups often rely on both employees and independent contractors. But these are legally distinct relationships - and using the wrong type of agreement can create serious legal and financial risks. Misclassification can lead to tax penalties, lawsuits, and regulatory violations, especially in strict states like California and New York.
Offer Letters for Startups: What Founders Need to Know
Hiring your first employees is an exciting milestone. But it’s not enough to agree on salary with a handshake. A clear, well-drafted offer letter sets expectations, outlines key terms, and helps reduce the risk of misunderstandings later.
Fired or Quit? Why It Matters Legally for Your Startup
When someone leaves your company, founders often want to just “move on” - but whether the departure was voluntary or involuntary has lasting legal and financial consequences. From unemployment claims to final pay rules, the details matter.
FAQs
Open allNo. A BAA is only part of compliance. You must also implement security, privacy, and breach response programs that meet HIPAA standards.
Any business that handles Protected Health Information (PHI) on behalf of a healthcare provider, insurer, or related entity is required to have a BAA.
Yes. In many settlements, both parties agree to release each other from claims, creating a clean break for both sides.
Yes. Federal law requires review and revocation periods in certain situations, especially for employees over 40. This ensures the agreement is fair and enforceable.
Not always. Courts require the agreement to be clear, voluntary, and compliant with state-specific laws. Some claims, like wage or workers’ compensation rights, may not be waived.
It protects your startup by having another party waive their right to bring certain legal claims against you.
Focus on intellectual property rights, payment terms, liability limits, and termination clauses, as these areas create the most potential risk.
Templates are a good starting point, but every deal has unique risks. Having counsel customize terms ensures your startup is protected.
Yes. Vendor agreements protect you when purchasing services, while customer agreements protect you when selling or licensing your own products.
A sales agreement transfers ownership of goods or services, while a licensing agreement grants permission to use intellectual property without transferring ownership.
These agreements clearly define who owns the work product, whether ownership transfers to the customer, or if your startup retains certain rights. This clarity helps prevent disputes later.
Yes, but it is less efficient. Without an MSA, every project must include all legal terms, which can slow down deals and create inconsistencies.
Not always, but if you plan to work with a customer or vendor on more than one project, an MSA saves significant time and prevents repeated negotiation.
An MSA sets the overall legal terms of the relationship, while an SOW outlines the specifics of an individual project.
No. Only institutional investors that need it for compliance, not angel investors or most venture funds without ERISA LPs.
Generally, no. It’s considered a standard compliance document, though founders can negotiate limits on inspection frequency or reporting burdens.
No. It typically provides inspection rights, reporting access, and sometimes observer rights—but no formal voting authority.
Because funds with ERISA or pension fund LPs must show they are “managing” investments to avoid regulatory restrictions.
Bylaws may provide some protection, but stand-alone indemnification agreements are stronger and more enforceable, offering tailored protection for each director or officer.
The indemnification agreement provides contractual protection, while D&O insurance provides financial backing. Together, they form a two-layer shield.