Core offer stack

The core offer stack packages the weather-to-outcome system into customer-facing results.

Component	Customer result
Live storm intelligence	Understand the event, revisions, evidence, and confidence
Existing-customer impact monitor	Identify affected customers and installed roofs
Property priority engine	Explain which eligible properties matter first
Deployment plan	Convert a storm into zones and assignments
Field outcome capture	Record visits, inspections, evidence, and next actions
CRM connection	Preserve storm context in the existing sales system
Evidence and reports	Produce a dossier instead of a map screenshot
Outcome attribution	Connect actions to inspections, opportunities, and jobs

Priority explanation

The property priority engine preserves several distinct judgments:

Estimated exposure
        ↓
Modeled damage likelihood
        ↓
Commercial opportunity
        ↓
Contact eligibility
        ↓
Operational priority

The interface should present the recommended action first. It must retain the evidence and policy reasons behind that recommendation.

Attribution boundary

StormTrust can report operational and financial outcomes associated with an event. It should not imply that the software alone caused each downstream result.

Scope control

The stack defines the core outcome. Contract scope can limit markets, data volume, integration depth, reports, or support. Reducing scope is preferable to selling the complete offer at an unsustainable price.