DCOS Guide — Velocity Metrics

Workshop 2 of 3 · Copy each block → paste into Claude Desktop (Digital Chief of Staff enabled).

Install DCOS Velocity scorecard CSV
Challenge 1: Run prompts 1 → 2 → 3 in order. CRM via DCOS (**BigQuery RevOps**, elastic-edm-prod). Auth fix: Refresh Google Auth.command + Refresh Claude Extension.command. Pick your #1 stalled or at-risk opp for Challenge 2.

Velocity signals to look for

1. Readiness check

Run first
You are connected to the Digital Chief of Staff (DCOS) MCP extension in Claude Desktop.

IMPORTANT: Every dcos_* name is an MCP tool — invoke through the connector. Do NOT run bash.

Run a DCOS readiness check. Execute every step and report pass/fail:

1. dcos_cluster_health
2. dcos_ensure_indices
3. dcos_sfdc_auth_status
   If auth fails: Refresh Google Auth.command + Refresh Claude Extension.command → quit Claude (Cmd+Q) → reopen
4. dcos_sfdc_sync with lookback_days: 1
5. dcos_watchlist_pipeline — confirm ACV, stage, close date
6. dcos_user_profile — confirm watchlist loaded

If dcos_cluster_health HTTP 410 but CRM passes: Refresh Claude Extension.command only.

If all pass: "✓ DCOS ready — Elasticsearch, CRM, and watchlist OK."

2. CRM authority block

Before velocity scorecard
⚠️ MANDATORY — run before velocity scorecard output. Do not skip.

1. dcos_sfdc_auth_status
2. dcos_sfdc_sync with lookback_days: 7
3. dcos_watchlist_pipeline — ALL pipeline numbers (ACV, stage, close date, owner, last activity if available)
4. dcos_search — MEDDPIC / activity context only; NEVER for ACV/stage/close date

If pipeline and dcos_search disagree on dollars, ALWAYS trust dcos_watchlist_pipeline.

3. Pipeline velocity scorecard

Challenge 1 main exercise
Workshop 2 — Velocity Metrics: map velocity signals across my active pipeline.

Use live CRM only (dcos_watchlist_pipeline, dcos_sfdc_list_opportunities, dcos_sfdc_query, dcos_sfdc_lookup_opportunity).
Do NOT invent ACV, stages, or activity dates. dcos_sfdc_query = BigQuery SQL on RevOps certified tables.

For my open observability-related opportunities (Stage 2+ preferred), output a markdown table:

| Account | Opp | Stage | ACV | Days in stage | Last activity (days ago) | Velocity signal | Why |
|---------|-----|-------|-----|---------------|--------------------------|-----------------|-----|

Velocity signal = one of: **Accelerating**, **On track**, **At risk**, **Stalled**

Rules (cite CRM fields):
- **Stalled** if days in stage > 60 OR no logged activity in 21+ days
- **At risk** if close date slipped in last 30 days OR single-threaded (only one contact engaged)
- **Accelerating** if stage advanced in last 30 days AND activity in last 14 days

Sort by risk (Stalled first). Highlight top 5 at-risk deals.
Pick **#1 opp** for Challenge 2 (best candidate for a deal-momentum narrative).
Ground every row in DCOS tool output — cite which tool returned each fact.

4. #1 opp deep dive

Optional — Challenge 2 has full narrative
For my #1 at-risk or stalled opp from the velocity scorecard:

Use DCOS (dcos_sfdc_lookup_opportunity, dcos_sfdc_get_opportunity, dcos_sfdc_get_account, dcos_search for notes/MEDDPICC):
- Last 3 meaningful activities (date + type)
- Champion vs economic buyer coverage (contacts engaged)
- Blockers mentioned in notes (if any)
- One sentence: what changed since last forecast?

Keep it factual — no invented stakeholders.