Map leadership decisions, customer commitments, systems and data, workforce, and the operating package across a startup's coverage questions.
Use this page to separate leadership decisions, customer commitments, systems and data, and the basic operating package. That structure makes a contract-driven request easier to compare with the company’s actual stage and activities.
Use the D&O hub for questions about decisions made while directing the company.
Use cyber for network, data, vendor, and incident-response questions.
Use the requirements guide to translate a customer’s insurance clause into policies, evidence, and endorsement requests.
These guides connect the coverage decisions below; use the questions to drill into a specific rule.
A technology company’s insurance requirements usually come from a customer contract, office lease, hiring rules, or investor checklist. This guide explains what those documents can request, what a certificate proves, and how to check the policy behind it. For liability exposures and claims, see pleasedontsue.us.
Read the guide →A startup’s insurance priorities change at clear moments: the first hire, enterprise contract, lease, or outside board member. This guide explains what each milestone can require, what proof to provide, and how to read the documents before signing. For liability exposures and claims, see pleasedontsue.us.
Read the guide →No question page is tagged to this industry yet. Use the coverage map above or browse coverage lines for the published library.
General liability, E&O, D&O, and employment practices questions live on our sister publication: Startups on Please Don't Sue Us.