Docs/Operations/Deal Pipeline
Operations

Deal Pipeline.

A kanban purpose-built for bank-FinTech partnerships. Eight named stages reflecting the actual lifecycle of an institutional deal, activity logging at every transition, stage-velocity analytics, automated compliance checkpoints, and tight coupling to the rest of the platform — Connections for messaging, Intelligence reports for analysis, CORTEX for health monitoring.

Why 8 stages
Generic CRM pipelines (Lead → Qualified → Closed) hide the specific choke points that kill bank-FinTech deals: pilot-review, compliance review, contract. Each of these often takes 30-60 days and needs its own stage — otherwise a deal "stuck in Negotiation" for three months looks like one-color kanban card instead of the three distinct problems it actually is.

The eight stages

  1. Discovery — initial conversations, mutual interest, scoping the opportunity. Typical duration: 7–21 days.
  2. Due diligence — KYB refresh, security review, preliminary legal. Typical: 14–42 days. Compliance checkpoint fires here.
  3. Pilot scoping — defining success criteria, timeline, integration plan. Typical: 14–30 days. Playbook generation recommended here.
  4. Pilot — running live with restricted scope. Typical: 60–120 days.
  5. Pilot review — scorecard against success criteria, go / no-go decision. Typical: 7–21 days.
  6. Contract — commercial terms, legal, signature. Typical: 21–60 days. Second compliance checkpoint.
  7. Launch — live in production, volume ramp. Typical: 14–30 days before transitioning to steady state.
  8. Won / Lost — closed state. Won deals continue to be monitored under CORTEX Early Warning; Lost deals feed PRISM's feedback layer for improving future matching.

What each deal tracks

A deal card in the Pipeline is considerably richer than a typical CRM opportunity:

Stage + time in stage
Current stage, days in this stage, total days open; stuck-deal flag at 14+ days without activity
Financial
Expected revenue + probability + weighted value; pulled from linked ROI Projection when available
Ownership
Owner on your side + counterparty lead on their side + backup contacts for each
Linked intelligence
Fit Analysis, ROI Projection, Playbook generated for this deal (click through to the source)
Activity timeline
Calls, emails, meetings, documents — with timestamp, actor, and summary
Next action
Specific task + due date + owner. Auto-suggested at stage transitions.
Compliance flags
Any outstanding KYB refresh, missing consent, or unresolved SHIELD alert affecting either party
Partnership type
BaaS / API / co-brand / white-label / referral — drives compliance review template and checkpoints

Activity logging

Every meaningful action against a deal is logged — not just stage changes, but the operational artifacts that regulatory examinations tend to ask about later:

Pipeline analytics

The Pipeline analytics view surfaces:

Automated compliance checkpoints

Transitions into certain stages automatically fire compliance checks:

Each checkpoint is surfaced to the owner with a specific set of actions. Until each item is marked complete or explicitly waived (with a reason), the stage transition is blocked. This replaces the "oh we forgot to check X" failure mode with explicit gating.

Integration with the rest of TECH

Compliance
Every deal's activity timeline, stage transitions, and linked documents are retained for seven years (Enterprise) or six years (Professional/Starter) under the FINRA 4511 + BSA recordkeeping retention model. The compliance export includes the full deal history for every deal — Won, Lost, or in-progress — for the retention window.

API surface

GET /connections/pipeline/
All deals grouped by stage + summary stats
POST /connections/pipeline/
Create a new deal
GET /connections/pipeline/<id>/
Full deal detail with activity timeline
PATCH /connections/pipeline/<id>/
Update deal attributes (owner, amount, probability, next action)
POST /connections/pipeline/<id>/move/
Transition to another stage — runs compliance checkpoints
POST /connections/pipeline/<id>/activities/add/
Log an activity (call, meeting, email, document)
Your weekly operating rhythm

Open Pipeline and walk the board.

Best practice: Monday morning review, stage-by-stage, flag every stuck deal, commit to one concrete action per flagged card before closing the tab.

Open Pipeline →