Document 1
Terms of service
Customer-facing agreement governing access to the product. Acceptable use, payment terms, refund policy, data handling, limitation of liability, and IP ownership.
Terms of service · vendor agreements · IC for contractors · employment for first hires · MSA for enterprise. The full agreement set for a SaaS business growing from zero to traction. Free.
Free. No registration. No card. No catch.
What's in this stack
SaaS businesses have four distinct contract relationships: customers, vendors, employees/contractors, and enterprise clients. The stack addresses each one.
Document 1
Customer-facing agreement governing access to the product. Acceptable use, payment terms, refund policy, data handling, limitation of liability, and IP ownership.
Document 2
For infrastructure, tooling, and service vendors. Data access rights, SLAs, confidentiality, and liability for any vendor who touches customer data.
Document 3
For developers, designers, and ops contractors. IC classification language, IP assignment, confidentiality, and scope. Covers every external person building the product.
Document 4
For W-2 employees: role, compensation, confidentiality, IP assignment, and non-solicitation. Signed before day one of every hire.
Document 5
Master service agreement for enterprise and mid-market clients. SLAs, data processing, indemnification, liability caps, and security requirements. Issued with an order form or SOW.
Why this stack
Customer liability is limited by TOS. Vendor risk is governed by SLAs. Employee IP chain is covered by employment agreements. One document for all of them creates gaps in every direction.
Self-serve TOS won't close an enterprise customer. An MSA with negotiable SLA and security terms is what procurement teams need. Generate the baseline; your lawyer reviews the red-lines.
Every contractor and employee who touches the codebase needs an IP assignment. The chain is reviewed at Series A and at acquisition. Close it before growth makes it complicated.
When to generate each document
Terms of service in place before the first customer signs up. Governs every self-serve account from day one.
IC agreement or employment agreement with IP assignment. Closes the chain before anyone touches the product.
Vendor agreement for any tool or service with access to customer data. Data handling and liability included.
MSA baseline generated for enterprise procurement. Have counsel review any customer red-lines before countersigning.
How it works with BizDraft
The customer-facing and vendor-facing documents are your baseline operations layer. Get these in place before launching or onboarding any vendor.
Contractor or employee, each person building the product gets an IP assignment and confidentiality clause before touching the codebase.
Generate the MSA baseline. Send as a starting point for negotiation. Have a lawyer review the version that comes back with red-lines before countersigning.
Free. Every document. Every stage.
Draft your agreement