# Commercialization Roadmap

Target: make PolyWeather a sustainable paid weather-intelligence product.

---

## 1. Product Positioning

PolyWeather is not a generic weather app.  
It is a decision-support layer for temperature-settlement markets:

- observation-first (METAR/MGM),
- settlement-aware probability modeling (DEB + mu/buckets),
- market mapping (Polymarket read-only) for actionable edge detection.

---

## 2. Business Overview Diagram

```mermaid
flowchart TD
    A["PolyWeather Monetization"]

    subgraph P["Product"]
        P1["Telegram Signal Channel"]
        P2["Web Dashboard"]
        P3["VIP Bundle"]
    end

    subgraph R["Pricing"]
        R1["Entry 1 USD"]
        R2["Dashboard 5 USD"]
        R3["Bundle 5.5 USD"]
    end

    subgraph AC["Access Control"]
        AC1["Manual activation (P1)"]
        AC2["Wallet/USDC detection (P2)"]
        AC3["Entitlement middleware"]
    end

    subgraph G["Growth"]
        G1["Accuracy reports"]
        G2["Retention analytics"]
        G3["User preference center"]
    end

    A --> P
    A --> R
    A --> AC
    A --> G
```

---

## 3. Packaging and Pricing

| Tier             | Price        | Value                                     |
| :--------------- | :----------- | :---------------------------------------- |
| Telegram Channel | $1 / month   | Low-noise proactive signal feed           |
| Web Dashboard    | $5 / month   | Full multi-model context + reconciliation |
| VIP Bundle       | $5.5 / month | Dashboard + signal stream                 |

Payment direction:

- Currency: Polygon USDC
- Phasing: manual activation first, then automated entitlement sync

---

## 4. Execution Phases

```mermaid
graph LR
    P1[Phase 1 Manual Beta] --> P2[Phase 2 Payment Automation]
    P2 --> P3[Phase 3 Growth and B2B]
```

### Phase 1: Manual Beta

- Keep paid channel small, optimize signal quality first.
- Manual payment confirmation + manual entitlement grant.
- Invite-gated dashboard while access control hardens.

### Phase 2: Payment Automation

- Detect wallet payment events (USDC).
- Auto-issue/refresh entitlement.
- Enforce route-level and API-level access guards.

### Phase 3: Growth and Expansion

- Self-serve billing and subscription panel.
- Operator analytics and feature usage telemetry.
- Optional B2B API package for quant teams.

---

## 5. Technical Dependencies for Revenue

| Dependency           | Why it matters                                                   |
| :------------------- | :--------------------------------------------------------------- |
| Entitlement guard    | Prevents unpaid dashboard/API access                             |
| Subscriber store     | Persistent paid user state                                       |
| Audit trail          | Explains why each alert fired                                    |
| Observability        | Detects degradation before churn                                 |
| Frontend performance | Impacts conversion and retention (Speed Insights now integrated) |

---

## 6. Immediate Commercial Priorities

1. Finish robust entitlement middleware in frontend and backend.
2. Persist subscriber/payment state in managed DB.
3. Publish transparent monthly accuracy and signal-quality reports.
4. Add support playbooks for false-alert and stale-data incidents.

---

Last Updated: `2026-03-11`