How WeatherIt Fits into Your Offering

WeatherIt is designed to complement your business, not complicate it.

The Integration Model

flowchart TB
    subgraph YourBusiness["Your Business"]
        A["Your Booking<br/>Process"]
        B["Your Cancellation<br/>Policy"]
        C["Your Refund<br/>Terms"]
    end

    subgraph WeatherIt["WeatherIt (Separate)"]
        D["Weather<br/>Coverage"]
        E["Trigger<br/>Conditions"]
        F["Automatic<br/>Payouts"]
    end

    A -.->|"Optional<br/>Add-on"| D

    style A fill:#e1f5ff
    style B fill:#e1f5ff
    style C fill:#e1f5ff
    style D fill:#e8f5e9
    style E fill:#e8f5e9
    style F fill:#e8f5e9

Design Principles

Principle	What It Means
Optional	Customers choose whether to add coverage
Additive	Enhances your offering without disruption
Separated	Distinct from your refund or cancellation policies

What You're NOT Doing

Important Distinction
By offering WeatherIt, you are not:

Promising refunds

Guaranteeing weather outcomes

Changing your existing terms

You are offering access to an independent insurance product that sits alongside your core offering.

Why This Distinction Matters

Stakeholder	Why Separation Matters
Customers	Clear understanding of what's covered and by whom
Staff	Confidence in what to say and what not to promise
Compliance	Regulatory requirements are met
Your Business	Your policies remain unchanged

flowchart LR
    A[Clear<br/>Separation] --> B[Customer<br/>Clarity]
    A --> C[Staff<br/>Confidence]
    A --> D[Regulatory<br/>Compliance]

    style A fill:#f3e5f5
    style B fill:#e8f5e9
    style C fill:#e8f5e9
    style D fill:#e8f5e9

WeatherIt sits alongside your offering — it doesn't replace or change anything you already do.