# Hermes Sales Pipeline

Standalone project: wire the Factronics USA **sales pipeline** to the **Hermes agent fleet**, so a deal changing stage becomes a first-class trigger for owner tasks, client sends (draft-only), branded documents, and a generated solution presentation.

## Project folder

```
Hermes_Sales_Pipeline/
  README.md                                  this index
  docs/
    specs/2026-09-24-sales-pipeline-hermes-design.md   approved design spec
    plans/                                   implementation plans (writing-plans output)
  reference/                                 captures, slide inventory, raw notes
```

## Status

- 2026-09-24: brainstorming complete, design spec approved, all sub-project implementation plans written. Next: internal review, then build (starting P1).

## Documents

| Type | File |
|---|---|
| Plain-language explainer | `Hermes_Sales_Pipeline_Explained.html` |
| Design spec | `docs/specs/2026-09-24-sales-pipeline-hermes-design.md` |
| P1 plan | `docs/plans/2026-09-24-p1-bridge-routing.md` |
| P2 plan | `docs/plans/2026-09-24-p2-owner-tasks-reminders.md` |
| P3 plan | `docs/plans/2026-09-24-p3-writeback-policy.md` |
| P4 plan | `docs/plans/2026-09-24-p4-presentation-generator.md` |
| P5 plan | `docs/plans/2026-09-24-p5-form-processes.md` |
| P6 plan | `docs/plans/2026-09-24-p6-unified-visibility.md` |

## Locked decisions (see spec section 3)

- Platform-agnostic: a stage transition is the trigger; HubSpot / GHL / n8n are executors.
- All seven stages spawn a Hermes task.
- Reuse existing Hermes domains; no new profile.
- Demo Van initiative out of scope this run.
- Presentation: master deck (Linx + Anritsu only), prospect logo + accent colors, strip editing rails, output editable Google Slides + PDF.
- Client sends are draft-only and human-approved; CEO copied on owner emails.

## Seven stages and current stage IDs

| # | Stage | dealstage |
|---|---|---|
| 1 | Calificar | `appointmentscheduled` |
| 2 | Proyecto Viable | `qualifiedtobuy` |
| 3 | Presentación de Solución | `presentationscheduled` |
| 4 | Negociación/Revisión | `decisionmakerboughtin` |
| 5 | Expectativa de Cierre | `contractsent` |
| 6 | Ganado | `closedwon` |
| 7 | Perdido | `closedlost` |

## Build order

1. SP1 Bridge and routing (foundation)
2. SP2 Owner tasks, reminder engine, template library
3. SP5 Close/PO Details intake, Loss Reason
4. SP4 Presentation generator
5. SP5 Quote/Negotiation Details, QB Estimate
6. SP3 Writeback policy, SP6 Unified visibility

## Related repos

- `Coordenadas-co/factronics-hermes-fleet` (branch `audit/icm-contract-fidelity`)
- `Coordenadas-co/factronics-hermes`
- `Coordenadas-co/Knowledge-Base-Hermes-Factronics`
- `Coordenadas-co/Gateway-QB`
- `Coordenadas-co/Factronics-control-panel`