Script runner — calling Edward Nelson

The locked EUK booker script. Bookers qualify and capture the profile; they do not book demos — a strong profile books a next-day Tom callback.

Call feedback — Marie, call with Edward Nelson

The agent-training Rubric scores how the agent delivered the call; Agent Feedback turns it into coaching. This scores the agent. It is a different tool from Investor Profiling, which scores the prospect's suitability from the answers (on the Prospect screen).

Closer list

Live records, ranked. Committed deals are pinned at the top for visibility; per the sort key they drop off the active work-order once closed — the order to work is the non-Committed rows below them. A T1 who has gone quiet sinks below a T2 who just named an amount.

Pipeline tracker

The read-only published pipeline view. Refreshes on change and daily.

CRM board — Pipedrive deal stages

The funnel structure (Unlock Investor Funnel + EUK Reports). Stage = where the deal sits. Suitability tier and readiness state are overlays on a deal, not stages. Deals move through Proposal → Committed → Win on the rotten-day + dated-next-action discipline; two active people are still being backfilled into the CRM (the leak the system catches).

Proposed Pipedrive structure

The whole target on one screen: where leads come in, the two pipelines and their stages, what is stamped on every deal, when each scoring instrument fires, and how it publishes. This is the To-Be the W0/W1 runbook builds toward.

Transcript → scored → up to you

How a raw call becomes a ranked prospect on your list. Three instruments read the transcript; one sort key decides the order you see. The detail lives in closer-loop-spec-V1; this is the picture of it.

CRM As-Is / To-Be

The CRM as it is today (live read, 25 Jun, read-only) against the target. The plan passed review but is on HOLD-before-write: the connection does not flip until the Tranche 0 gate is green and D4 is resolved. Nothing here changes Pipedrive.

System map

Based on Werner's map. Solid arrows are material flows; dashed are information flows; red nodes are the three faults the design fixes.

flowchart TB
  subgraph EV["Evidence (transcripts)"]
    AC["Aircall
calls + dispositions"]
    GEM["Gemini
demo notes"]
    FF["Fireflies
internal meetings"]
  end
  subgraph SRC["Source + funnel"]
    LP["Lead Pool
Supabase"]
    TOM["Tom
cold calls"]
    PD["Pipedrive
CRM of record"]
    EUK["EUK Report
Distribution"]
  end
  subgraph SC["Scoring"]
    RUB["Rubric"]
    PROF["Investor Profiling"]
    SIG["Signalz"]
  end
  subgraph VW["Published view"]
    DM["data.md"]
    SITE["gated tracker"]
  end
  LP -->|"channel 1 agent-outbound"| AC
  AC -->|first contact| PD
  TOM -->|"channel 2 tom-outbound"| PD
  EUK -.->|"channel 3 euk-email, same person"| PD
  AC -.->|disposition| PD
  GEM -.->|demo outcome| PD
  AC --> RUB
  AC --> PROF
  GEM --> SIG
  PROF -.->|tier| PD
  SIG -.->|state + readiness| DM
  PD -->|hand-maintained| DM
  DM --> SITE
  PD -.->|"FAULT 2 won never returns"| WON{{"phantom: Ian Chance"}}
  PD -.->|"FAULT 1 no forward pull"| STALL{{"Demo pile-up"}}
  DM -.->|"FAULT 3 staleness"| SITE
  classDef fault fill:#3a1d1d,stroke:#ef4444,color:#f3a3a0;
  class WON,STALL fault;
      

Data sources and tools

The seven sources, where each lives, and its read/write edge into the canonical record.

Schema

Pipedrive is the canonical record. Two segmentation axes kept distinct: Channel (who works it) and Lead Origin (where it came from).

erDiagram
  PERSON ||--o{ DEAL : has
  DEAL ||--o{ ACTIVITY : owes
  PERSON ||--o{ AIRCALLCALL : received
  LEAD ||--|| PERSON : becomes
  DEAL ||--o| SCORE : "scored by"
  DEAL ||--|| CONTACTRECORD : "published as"
  PERSON {
    string match_key "email then phoneE164 then name+org"
    int id PK
    enum channel "agent / tom / euk-email"
    enum lead_origin "euk-survey / tom-network"
    enum relationship_depth "personal / grouped"
  }
  DEAL {
    int id PK
    int person_id FK
    enum stage "Intro to Win or Lost"
    enum segment "hnw / uhnw / family-office (wealth band only)"
    enum suitability_tier "T1-T4 / unscored (own field)"
    int signalz_readiness "latest value only"
    bool eis_eligible "gate before EIS promotion"
  }
  ACTIVITY {
    int id PK
    string subject "next action"
    date due_date
    string owner
  }
  SCORE {
    enum kind "suitability / readiness"
    int value
    array signals "cite-bound"
  }
  CONTACTRECORD {
    string tier
    string state
    int readiness
  }
      

Interactions

How the sync jobs move data. Every write is idempotent on ext_key: search first, update if found, create only if absent.

sequenceDiagram
  autonumber
  participant Cron
  participant Sync as Sync service
  participant AC as Aircall API
  participant PD as Pipedrive
  Cron->>Sync: POST /sync/aircall-ingest
  Sync->>AC: GET /calls?from=lastrun
  AC-->>Sync: calls + tags
  loop each call
    Sync->>PD: GET /persons/search (dedup)
    Sync->>PD: PUT /deals/{id} (tags, stage?)
    Sync->>PD: POST /activities (dated next action)
  end
  Sync-->>Cron: 207 partial
      

sequenceDiagram
  autonumber
  participant Trig as Deal change
  participant Sync as Sync service
  participant PD as Pipedrive
  participant CF as Cloudflare Pages
  Trig->>Sync: POST /sync/publish
  Sync->>PD: GET deals + scores
  Sync->>Sync: build data.json
  Sync->>CF: wrangler pages deploy
  Sync->>Sync: sha256 parity check
  Sync-->>Trig: deployed_url
      

Endpoints

12 of 13 edges in contract. The write path (E5-E10) is gated on the scoped Pipedrive token. One gap: Gemini transcripts not API-reachable.