Floodbase

Name: Floodbase
Brand: Floodbase

We use satellites and AI to track floods in near real-time anywhere on Earth to insure risk and save lives.

Est 2015|Valuation $50M|Raised $24.7M|13 Ref Customers

LinkedIn 7K|Website|FTEs 27|HQ Brooklyn, New York, US

Published Sep 25, 2026

01Common complaints

If the purchaser requires indemnity-style precision at the asset level and cannot tolerate basis risk; traditional insurance or sensor-at-location parametric approaches may be more appropriate.
If procurement mandates publicly documented enterprise compliance (SOC 2, ISO 27001, SSO/SCIM) and Floodbase cannot provide the requested documentation during due diligence.
If the primary need is a broad climate risk platform covering multi-peril transition and physical risk scenarios; Floodbase is focused on flood monitoring and parametric enablement.
If guaranteed building-level depth estimates are required universally and immediately in all geographies; other providers with different sensor or modeling approaches may be preferable.
If independently audited model performance metrics (accuracy, false positive/negative rates, latency) are required prior to purchase and these are not available publicly.

- If the purchaser requires indemnity-style precision at the asset level and cannot tolerate basis risk; traditional insurance or sensor-at-location parametric approaches may be more appropriate. - If procurement mandates publicly documented enterprise compliance (SOC 2, ISO 27001, SSO/SCIM) and Floodbase cannot provide the requested documentation during due diligence. - If the primary need is a broad climate risk platform covering multi-peril transition and physical risk scenarios; Floodbase is focused on flood monitoring and parametric enablement. - If guaranteed building-level depth estimates are required universally and immediately in all geographies; other providers with different sensor or modeling approaches may be preferable. - If independently audited model performance metrics (accuracy, false positive/negative rates, latency) are required prior to purchase and these are not available publicly.

Deal disqualifiers (poor fit)

Buyers that require full indemnity loss adjustment tied strictly to site-level property damage and cannot accept basis risk.
Procurement processes that require publicly documented SOC 2/ISO evidence and the vendor cannot provide such documentation during due diligence.
Buyers that require self-serve SaaS pricing and trials.

Vendor-acknowledged limitations

Public pages reviewed did not include a dedicated limitations or status page.

Likely limitations (based on product category and available evidence)

Basis risk is inherent in index products: payout triggers may not match localized damage or exposure at a specific site.
Data latency and resolution trade-offs vary by geography, sensor availability, and atmospheric conditions; optical sensors are limited by cloud cover and time of day, which vendors may supplement with SAR sources.
Integration maturity is unclear externally: claims of API access and easy integration require technical validation via sample data and integration tests.
Security and compliance transparency gaps in public documentation may slow enterprise procurement.

- Basis risk is inherent in index products: payout triggers may not match localized damage or exposure at a specific site. - Data latency and resolution trade-offs vary by geography, sensor availability, and atmospheric conditions; optical sensors are limited by cloud cover and time of day, which vendors may supplement with SAR sources. - Integration maturity is unclear externally: claims of API access and easy integration require technical validation via sample data and integration tests. - Security and compliance transparency gaps in public documentation may slow enterprise procurement.

Roadmap signals

The company has announced enhancements to continuous flood mapping and new data products and partnerships; details should be validated in conversations with the vendor and by reviewing technical release notes.

02Why they buy

Supported by public evidence and partner materials:

End-to-end parametric workflow support (index design → threshold setting → continuous monitoring → trigger adjudication) is described in product materials and partner announcements.
Public-sector use cases (humanitarian and municipal examples) indicate operational applications beyond insurance product sales.
Partnership and accelerator participation (such as Lloyd’s Lab) and public announcements with brokers and re/insurers indicate integration with insurance-industry processes.

Caveat: Several claimed advantages (for example, broad uninterrupted coverage or highest reliability) are difficult to verify independently based on publicly available materials.

Supported by public evidence and partner materials: - End-to-end parametric workflow support (index design → threshold setting → continuous monitoring → trigger adjudication) is described in product materials and partner announcements. - Public-sector use cases (humanitarian and municipal examples) indicate operational applications beyond insurance product sales. - Partnership and accelerator participation (such as Lloyd’s Lab) and public announcements with brokers and re/insurers indicate integration with insurance-industry processes. Caveat: Several claimed advantages (for example, broad uninterrupted coverage or highest reliability) are difficult to verify independently based on publicly available materials.

03Field reports

Important constraint: limited third-party product reviews

Floodbase is a specialized B2B platform (insurance + geospatial analytics) and has little to no presence on major software review platforms, which limits routine review-platform sentiment analysis.

This section draws on vendor-published testimonials, case studies, employee sentiment sources, and partner announcements.

Vendor-published testimonials (paraphrased)

An executive at a wholesale insurance broker stated that partnering with Floodbase enabled development of products that pay out based on the magnitude of flooding.
A representative from a major humanitarian agency noted that Floodbase’s flood intelligence supported faster detection and response capabilities that had not previously been available.
A humanitarian program contact reported that recurring reporting helped prioritize response activities for specific areas.

These statements are taken from vendor-provided case materials and public partner announcements.

- An executive at a wholesale insurance broker stated that partnering with Floodbase enabled development of products that pay out based on the magnitude of flooding. - A representative from a major humanitarian agency noted that Floodbase’s flood intelligence supported faster detection and response capabilities that had not previously been available. - A humanitarian program contact reported that recurring reporting helped prioritize response activities for specific areas. These statements are taken from vendor-provided case materials and public partner announcements.

Employee sentiment and other critical signals

Employee reviews describe the company as offering ownership and growth opportunities and a mission-focused culture, while also noting organizational growing pains such as periods of disorganization and occasional misalignment between sales and technical teams. These comments reflect a limited sample of employee feedback and should be treated as indicative rather than definitive.

Why customers choose Floodbase (inferred)

Common selection drivers based on public materials include:

Automation of monitoring and trigger workflows that aim to shorten time to payout compared with traditional adjustment processes.
A data coverage approach that uses multiple observation sources rather than relying solely on localized hydrologic models.
Support for parametric structures that can address non-traditional loss types such as business interruption and disaster response costs.
Credibility signals from partner relationships and participation in insurance innovation programs.

Common selection drivers based on public materials include: - Automation of monitoring and trigger workflows that aim to shorten time to payout compared with traditional adjustment processes. - A data coverage approach that uses multiple observation sources rather than relying solely on localized hydrologic models. - Support for parametric structures that can address non-traditional loss types such as business interruption and disaster response costs. - Credibility signals from partner relationships and participation in insurance innovation programs.

Why some customers might not buy or might leave (inferred)

Potential reasons include:

Lack of publicly documented security and compliance evidence, which can slow procurement.
Basis risk concerns inherent in index-based (parametric) products: payouts may not match site-specific losses.
A preference for sensor-at-location triggers that measure depth at an insured site rather than area-based observed extents.
A need for transparent, independently validated model performance metrics beyond vendor case materials.

Potential reasons include: - Lack of publicly documented security and compliance evidence, which can slow procurement. - Basis risk concerns inherent in index-based (parametric) products: payouts may not match site-specific losses. - A preference for sensor-at-location triggers that measure depth at an insured site rather than area-based observed extents. - A need for transparent, independently validated model performance metrics beyond vendor case materials.

Case Study 1: Emergency flood response in a Central African country

Claimed impact (vendor case study):

Large numbers of at-risk individuals were relocated and many people received redirected aid.
Substantial emergency aid was distributed.

Implementation details (as described):

Near real-time flood data delivered through a localized portal.
Alerts and impact analytics distributed via messaging channels and hotlines.
Use of high-resolution satellites for event verification.

Critical evaluation:

These outcomes are reported in a vendor-authored case study and lack full methodological transparency. Attribution is complex because humanitarian responses involve multiple inputs; the vendor likely contributed to situational awareness, but counterfactual impacts are not rigorously quantified in the public materials.

Claimed impact (vendor case study): - Large numbers of at-risk individuals were relocated and many people received redirected aid. - Substantial emergency aid was distributed. Implementation details (as described): - Near real-time flood data delivered through a localized portal. - Alerts and impact analytics distributed via messaging channels and hotlines. - Use of high-resolution satellites for event verification. Critical evaluation: - These outcomes are reported in a vendor-authored case study and lack full methodological transparency. Attribution is complex because humanitarian responses involve multiple inputs; the vendor likely contributed to situational awareness, but counterfactual impacts are not rigorously quantified in the public materials.

Case Study 2: Flood monitoring in a Northeast African country

Claimed impact (vendor case study):

Thousands of individuals received assistance following flooding using flood maps.
High-resolution flood extents and impact statistics were delivered rapidly.
Multiple communities were inspected for flood risk using risk analytics.

Critical evaluation:

Delivery speed is an operational metric of interest. Buyers should ask for typical resolution, accuracy thresholds, and source attribution (public vs commercial satellite tasking) to evaluate the consistency of such delivery times across multiple events.

Claimed impact (vendor case study): - Thousands of individuals received assistance following flooding using flood maps. - High-resolution flood extents and impact statistics were delivered rapidly. - Multiple communities were inspected for flood risk using risk analytics. Critical evaluation: - Delivery speed is an operational metric of interest. Buyers should ask for typical resolution, accuracy thresholds, and source attribution (public vs commercial satellite tasking) to evaluate the consistency of such delivery times across multiple events.

Case Study 3: A municipal parametric flood insurance program example in California

The vendor has described municipal parametric programs and provided a hypothetical example estimating eligibility for historical events under a parametric design. Such hypothetical calculations are useful for feasibility assessments but depend on chosen index and threshold design, and should not be treated as audited historical payouts.

04Best fit

Company sizes

Likely best fit:

Mid-market to enterprise insurers/reinsurers and brokers (often business units of larger groups).
Government agencies and national/state emergency management organizations.
Municipalities and counties of sufficient scale to justify parametric cover designs.

Industries / verticals

Insurance (P&C, specialty, parametric)
Public sector emergency response
Agriculture (crop and land loss)
Municipal infrastructure and public finance
Commercial real estate and facilities with flood-related business interruption exposure

Roles and personas

Insurance: Parametric program leads, catastrophe risk modelers, underwriting leadership, claims operations, product managers, and actuarial teams
Brokerage: Alternative risk and parametric practice leads
Public sector: Emergency management directors, GIS leads, and resilience officers

Qualification criteria (good fit)

The buyer needs faster liquidity or parametric payout structures.
The buyer has portfolio-scale or large-area exposure where traditional adjustment is slow or costly.
The buyer accepts parametric basis risk and has governance in place for index design.

05The pitch

What the product does (core value proposition)

design parametric flood insurance indices and triggers,
monitor active policies for trigger events,
certify and validate triggers to support faster payouts,
support claims triage and event response with flood extent and severity layers.

The platform is positioned to provide coverage for flood-related losses that are not typically addressed by traditional property flood insurance (for example, business interruption, disaster response costs, and crop/land impacts) using parametric structures intended to pay out without conventional loss adjustment.

The company’s go-to-market approach focuses on enterprise partnerships with carriers, brokers, and public-sector programs rather than a self-serve SaaS route.

Floodbase is a B2B flood intelligence and parametric insurance enablement platform. It provides near real-time and historical flood data derived from satellites and other sensors/data sources that insurers, reinsurers, brokers, governments, and large organizations use to: - design parametric flood insurance indices and triggers, - monitor active policies for trigger events, - certify and validate triggers to support faster payouts, - support claims triage and event response with flood extent and severity layers. The platform is positioned to provide coverage for flood-related losses that are not typically addressed by traditional property flood insurance (for example, business interruption, disaster response costs, and crop/land impacts) using parametric structures intended to pay out without conventional loss adjustment. The company’s go-to-market approach focuses on enterprise partnerships with carriers, brokers, and public-sector programs rather than a self-serve SaaS route.

Target market and market positioning

Floodbase targets:

Insurance ecosystem: carriers, reinsurers, MGAs, wholesale brokers, and structuring teams working on parametric solutions.
Public sector / humanitarian: agencies needing rapid flood mapping and impact analytics for response.
Large corporates: as insureds within broker-led parametric programs.

Positioning emphasizes parametric flood products and observed-fact flood mapping at scale, with claims of continuous monitoring and rapid operational utility. Independent verification of broad coverage claims is limited in publicly available sources.

Floodbase targets: - Insurance ecosystem: carriers, reinsurers, MGAs, wholesale brokers, and structuring teams working on parametric solutions. - Public sector / humanitarian: agencies needing rapid flood mapping and impact analytics for response. - Large corporates: as insureds within broker-led parametric programs. Positioning emphasizes parametric flood products and observed-fact flood mapping at scale, with claims of continuous monitoring and rapid operational utility. Independent verification of broad coverage claims is limited in publicly available sources.

Get a comprehensive analysis of Floodbase including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →