Frameworks and analysis for seed-to-Series A founders building enterprise-ready companies. Written by lawyers, for founders.
IP ownership is clean in a pure SaaS model. It breaks down the moment professional services enter the picture. Here's how to protect your core IP while giving customers what they reasonably expect to own.
An AUP defines what customers can and can't do with your service. Done well, it protects your platform without creating friction for legitimate use. Done poorly, it's either unenforceable or makes customers uncomfortable signing.
Termination provisions are the section nobody thinks about at signing and everybody fights about at exit. Here's what to get right before the relationship ends.
Your billing terms govern how you charge, when you charge, and what happens when customers don't pay. The most important principle: your terms need to match how your business actually charges customers.
Enterprise procurement teams have a playbook for the liability clause. They know which asks look reasonable on the surface but materially expand your exposure. Here's how to recognize and respond to each one.
Your Terms of Service is the most important document in your customer contracting stack. Here's what every section does, why it matters, and how to think about the balance between protection and friction.
Most insurance content for SaaS founders comes from brokers. This comes from the other side — managing risk across a PE-backed software portfolio and seeing how policies perform when something goes wrong.
You've built enterprise pipeline. The champion loves the product. Then the security questionnaire lands. Here's why SOC 2 is non-negotiable and how to think about getting it right.
Most founders think of legal documents as a cost center. That framing costs you deals. A well-structured legal stack accelerates enterprise sales cycles — here's how.
The right approach isn't choosing between lawyers and tools. It's using each where they're strongest. Here's the framework.
Untailored legal documents don't cause problems on day one. They cause problems at the worst possible time: during enterprise procurement, in litigation, or during M&A due diligence.
Your customer-facing contractual framework has four components. Here's what each one does, why it exists, and when it becomes necessary.