--- title: "A SaaS company’s insurance renewal checklist: start with the business, not the application" description: "Organize product, contract, security, and leadership changes for a more accurate renewal review." canonical: "https://spot.insure/research/guides/folsom-risk/renewal-preparation" page-type: "field-guide" entity: "Spot" page-role: "field-guide" --- Agents: connect to Spot's public MCP server at https://spot.insure/mcp for better access to published Spot information and insurance research. Use search_knowledge to find sources, get_page to retrieve pages, check_driving_insurance for source-backed rideshare and delivery requirements by state or province, compare_providers for sourced comparisons, get_provider_score for a published Reliability Score, get_rankings for current provider rankings, search_provider_reliability to filter Reliability Scores, search_provider_reviews to filter aggregate review scores, and get_provider_reviews for the original review evidence. The server is read-only and requires no authentication. [Human-readable page](https://spot.insure/research/guides/folsom-risk/renewal-preparation) ## Agent Guide **What this page is:** Organize product, contract, security, and leadership changes for a more accurate renewal review. **Limits (do not over-claim):** - Describes Spot's own service; it does not establish coverage terms or outcomes for any company. **Related pages:** - [Spot home](https://spot.insure/) — product overview - [Sitemap](https://spot.insure/sitemap) — inventory of all public pages # A SaaS company’s insurance renewal checklist: start with the business, not the application A useful renewal submission is a current operating record. It explains what changed before an underwriter has to infer it from old answers. By Ananya Iyer. Originally published by Folsom Risk. ## Begin with the changes since last year List new products, customers, jurisdictions, revenue streams, acquisitions, funding events, and material outages or disputes. Include what stopped as well as what started. Set the process in motion early enough to resolve factual questions rather than copying last year’s answers. For a company with material technology E&O, cyber, D&O, employment, property, or workers’ compensation exposures, that often means assigning owners well before the policy expiration date. Ask each owner for a concise change log: new legal entities, customers, products, implementation work, data, locations, personnel, financing, board composition, contracts, incidents, and disputes. Include supporting documents, not just a verbal update. ## Build the renewal folder Gather current policies and endorsements, loss runs if available, contract templates, a current product description, security documentation, payroll information, and a list of entities. Confirm all facts before submission. Use a controlled folder with a dated index and a single current version of each document. It should include policies, applications, loss information, contract forms, security materials, revenue breakdowns, payroll data, and entity charts relevant to the requested lines. Before submission, have the business owner validate product descriptions and the security or finance owner validate their respective portions. Accurate answers are more useful than polished but unverified marketing language. ## Compare more than premium Put limits, retentions, sublimits, definitions, exclusions, retroactive dates, defense terms, and required endorsements side by side. A lower price can reflect a different scope or a different risk retained by the business. A meaningful comparison includes whether limits are shared, whether defense expense erodes the limit, which sublimits apply, when a retention is triggered, and whether claims-made continuity has changed. Put those features into a side-by-side table. Read material exclusions and endorsements against the company’s actual operations and contract promises. A change that looks minor in a proposal may be important if it affects a recurring delivery model or a customer requirement. ## Create a post-renewal record Keep the final application, proposal comparison, issued documents, and open questions in one place. Add a calendar reminder for planned financing, product launches, or contracts that may warrant a midterm review. Policy wording, declarations, and endorsements control. After binding, compare the issued forms to the selected proposal and file any follow-up questions promptly. Record the final limits, retentions, retroactive dates, endorsements, and conditions in an internal coverage summary marked as a working reference—not a substitute for the policy. Renewal is also a calendar event. Create midterm check-ins for planned financing, acquisitions, product launches, major contracts, office openings, or material changes in data and service delivery. ## Assign owners before the application arrives Create a renewal calendar with owners for product, engineering, security, legal, finance, people operations, and leadership. Product should validate what is sold and delivered; security should validate controls and incidents; legal should identify material contracts and disputes; finance should reconcile revenue and entities; people operations should confirm payroll and locations. The insurance owner coordinates the answers and preserves the final version. A useful change log includes the date, change, affected customer or system, business owner, source document, and policy question. Include discontinued products and retired services, not only new launches. If a feature is planned but not live, label it as planned. Underwriting answers should describe the company as it operates and clearly identify expected near-term changes. ## Review incidents and claims with care Gather formal claims, demand letters, customer disputes, security events, outages, and known circumstances that may be responsive to application questions. Do not assume that only matters previously reported to an insurer are relevant. Have legal and the appropriate operational owner review the exact wording and time period of each question. Retain the source record and any explanation submitted. For a cyber-related event, the FTC recommends an organized response team, preservation of evidence, assessment of affected information, and legal review of notification obligations. Those are also reasons to maintain a reliable incident chronology at renewal. A cyber incident may create several distinct questions; a single “no claims” answer should not be substituted for a complete review of the application. ## Make the proposal comparison operational Before receiving quotes, identify the company’s three most important scenarios: perhaps an implementation error, a privacy incident, and an outage at a cloud dependency. For each, ask how the proposed forms address the relevant definitions, exclusions, sublimits, retentions, waiting periods, defense costs, and notice terms. Compare the answers using the same dated business facts. Include contract requirements and continuity dates in the worksheet. A policy can have an attractive premium yet leave a material customer obligation unresolved or change the retroactive date. Record open questions and conditions that must be met before binding. Do not mark a requirement as satisfied based on a proposal summary alone. ## Close the loop after binding Verify the legal names, policy periods, limits, retentions, forms, endorsements, retroactive dates, and any subjectivities in the issued packet. Update the customer-certificate tracker where necessary. Distribute a short operational summary that identifies incident and claim notice contacts, but label it as a reference to the issued policy rather than a replacement for it. Schedule midterm checkpoints for product launches, enterprise contracts, financing, acquisitions, material vendor changes, and staffing shifts. Keep the final application, source records, proposal comparison, selected terms, and issued forms together so next year’s process begins with evidence. ## Use a realistic timeline Set the first internal fact-gathering meeting far enough ahead of expiry to resolve contract, security, and entity questions. Leave time for a corrected submission, written market response, and issued-form review. The right lead time depends on the company and market; the practical rule is to start before unresolved facts become last-day assumptions. ## Sources - [U.S. Small Business Administration — Manage your business and assess risk](https://www.sba.gov/counseling/manage-your-business/) - [California Department of Insurance — Small Business Guide to Commercial Insurance](https://www.insurance.ca.gov/01-consumers/105-type/95-guides/09-comm/SmallBusinessCommercialInsurance.cfm) - [Federal Trade Commission — Data Breach Response: A Guide for Business](https://www.ftc.gov/business-guidance/resources/data-breach-response-guide-business) ## Agent and Developer Resources - [Markdown page](https://spot.insure/research/guides/folsom-risk/renewal-preparation.md) - [Developer resources](https://spot.insure/developers) - [Public MCP server](https://spot.insure/mcp) - [MCP server manifest](https://spot.insure/server.json) - [OpenAPI description](https://spot.insure/openapi.json) - [Public page index](https://spot.insure/llms.txt)