Sales and Customer Conversations

How WeatherIt is presented in conversations shapes customer expectations and outcomes.

How to Present WeatherIt

flowchart TB
    subgraph Presentation["Always Present As"]
        direction TB
        A["Optional"]
        B["Independent of<br/>Partner Policies"]
        C["Trigger-based<br/>& Objective"]
    end

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

Presentation	Why It Matters
Optional	Customer choice is fundamental
Independent of partner policies	Separate from refunds/cancellations
Trigger-based and objective	Rules-based, not subjective

Language to Avoid

Subjective Language Creates Problems
Avoid language that sets subjective expectations about weather or outcomes.

Avoid Saying	Why
"Protection if the weather is bad"	"Bad" is subjective
"Ruined", "terrible weather", "washout"	Creates subjective expectations
"Alternative to a refund"	WeatherIt is not a refund replacement

Recommended Language

flowchart LR
    subgraph Recommended["Say Instead"]
        direction TB
        A["Pays when specific<br/>rainfall criteria are met"]
        B["Based on<br/>objective data"]
        C["Automatic and<br/>rules-based"]
    end

    style A fill:#e1f5ff
    style B fill:#e1f5ff
    style C fill:#e1f5ff

Recommended Language	What It Communicates
"WeatherIt pays when specific rainfall criteria are met"	Objective trigger
"Coverage is based on objective data"	No subjective judgement
"Outcomes are automatic and rules-based"	Predictable process

Who This Protects

Mutual Protection
Clear, objective language protects both customers and partners.

flowchart LR
    A[Clear<br/>Language] --> B[Customers Protected<br/>from Misunderstanding]
    A --> C[Partners Protected<br/>from Disputes]

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

Objective language sets accurate expectations—protecting both customers and partners.