# CRM and opportunities

Product design

This page describes the product model and requirements. Examples illustrate the model, not a guaranteed API or completed feature. Check the [application contracts](/stormtrust/apps/) and [dataset inventory](/stormtrust/product/platform-and-data/datasets-and-source-contracts/) for implemented scope. Use [operations guides](/stormtrust/engineering/operations/) for runnable procedures.

StormTrust supports enough relationship state to close the weather-to-outcome loop. It does not require every tenant to abandon an existing CRM.

## Leads

A lead represents an early actionable relationship among a person, property, business, event, and tenant.

## Contacts

A contact distinguishes the person or organization, property relationship, source, consent, and permitted communication channels.

## Opportunities

An opportunity represents potential commercial value. It may include property, contact, event, stage, owner, expected value, probability, source, and external CRM identity.

## Activities

Activities may include calls, email, text messages, visits, notes, inspections, meetings, and status changes.

## External CRM systems

StormTrust may integrate with contractor and general-purpose systems through adapters or APIs. Candidate systems include JobNimbus, HubSpot, Salesforce, and AccuLynx.

Exact supported integrations remain roadmap decisions. External systems may remain the final sales system of record.