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

IMPORTANT: Every name below (dcos_*) is an MCP tool — invoke through the connector. Do NOT run bash or search the filesystem.

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: run Refresh Google Auth.command + Refresh Claude Extension.command, then quit Claude (Cmd+Q) and reopen
4. dcos_sfdc_sync with lookback_days: 1
5. dcos_watchlist_pipeline — confirm live ACV, stage, close date
6. dcos_user_profile — confirm persona and watchlist loaded

If dcos_cluster_health fails with HTTP 410 but CRM tools pass: Refresh Claude Extension.command only (Serverless ES — not a CRM auth issue).

If you cannot see dcos_* tools: Claude → Settings → Connectors → enable Digital Chief of Staff → Cmd+Q and reopen.

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

⚠️ MANDATORY — run before any account list output. Do not skip.

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

If live pipeline and dcos_search disagree on dollars, ALWAYS trust dcos_watchlist_pipeline.
CRM source is BigQuery RevOps certified only. Pipeline dollars from dcos_watchlist_pipeline — never dcos_search.

DCOS field lab — identify consolidation targets in my territory.

Use live CRM only (dcos_watchlist_pipeline, dcos_sfdc_query, dcos_sfdc_list_opportunities, dcos_sfdc_lookup_opportunity).
Do NOT invent ARR or account names. Do NOT use practice or fictional accounts. dcos_sfdc_query uses BigQuery SQL on the certified pipeline table.

Find accounts/opportunities that match this consolidation profile:
- Observability / monitoring spend under ~$150K ARR (or closest field in our CRM)
- Multi-vendor sprawl: 3+ tools or subscriptions where visible
- Competitive footprint includes any of: Datadog, Dynatrace, Grafana Cloud, Splunk, New Relic
- Prefer accounts where Elastic could consolidate metrics + logs + APM on one platform

Output a markdown table:

| Rank | Account | Observability ARR | Vendors / tools | Contract ARR at risk | Expansion hypothesis |
|------|---------|-------------------|-----------------|----------------------|----------------------|

List top 10, then highlight top 5. Add one sentence citing Gartner Observability MQ Leader / IT Ops #1 for my #1 account.
Ground every dollar and stage in tool output — cite which DCOS tool returned each fact.

For my #1 consolidation target from the previous list:

1. dcos_sfdc_get_account and dcos_sfdc_get_opportunity for the best open opp
2. dcos_search for any MEDDPICC notes on this account (context only — not for ARR)
3. Summarize: tool sprawl, economic buyer signal, 3-bullet discovery hook
   tied to unified Elastic platform (metrics + logs + APM).

Under 200 words — or continue in Challenge 2 DCOS Guide for slides + TCO.

Use dcos_sfdc_query with BigQuery SQL (default CRM — certified RevOps pipeline table):

SELECT account_name, opportunity_name, acv, stage_name, opportunity_close_date, opportunity_owner_name
FROM Opportunity
WHERE pipeline_reporting_disposition = 'Open Pipeline'
  AND latest_day = true
  AND acv < 150000
ORDER BY acv DESC
LIMIT 25

Show results in a table. If column names differ, use closest fields from tool output and say so.
For competitive tool sprawl (Datadog, Dynatrace, Grafana, Splunk, New Relic), supplement with dcos_search notes — do not invent vendors.

Workshop 1 Challenge 2 — my #1 consolidation account from Challenge 1.

Use DCOS only for facts (no invented ARR, vendors, or contacts):
1. dcos_sfdc_get_account for that account
2. dcos_sfdc_get_opportunity for the best open observability-related opp
3. dcos_sfdc_query or dcos_search for contacts — roles if available
4. dcos_search for notes/MEDDPICC (context only — not for dollar amounts)

Output:
- Account + opp snapshot (stage, amount, close date, owner) — cite each DCOS tool
- **Competition / sprawl** — list every vendor or tool mentioned in CRM or notes (Datadog, Dynatrace, Grafana, Prometheus, Splunk, New Relic, etc.)
- Table: | Name | Title/Role | Why talk to them | Suggested ask |

Same #1 account — using the competition list from the previous prompt.

Choose **one primary GTM motion** (Metrics Analyst deck) and defend it in 2–3 sentences:

**Displace** — SaaS incumbent renewal; connect Datadog/Grafana → auto-convert dashboards & alerts → live same day; 4× lower TCO vs Datadog.

**Consolidate** — Open-source / Prometheus-Mimir-Grafana shop; preserve PromQL and Grafana; Elastic as backend for metrics + logs + APM.

**Federated Data Sources** — Bridge when full migration is not yet approved: federated query/analysis across existing metric/log stores (keep data in place), single pane in Kibana/ES|QL, phased move to Elastic ingest later.

Then output:

## Recommended motion
(name + why for THIS account)

## 90-day steps
(numbered 5–7 steps — discovery, technical validation, pilot scope, exec readout, contract/renewal timing as relevant)

## Risks & mitigations
(3 bullets)

## Proof points to use
(map motion to: 30× queries, 6.6× storage, Gartner MQ Leader / IT Ops #1 where appropriate)

Same account — align TCO to the recommended motion above.

Build a **6-slide outline** (sprawl vs Elastic unified). Use **illustrative** dollars in the **15–40% savings** band unless CRM gives real spend — label estimates clearly.

Slide 1 — Title: account + motion (Displace / Consolidate / Federated path)
Slide 2 — Today: multi-vendor sprawl (name competitors from CRM)
Slide 3 — Hidden costs: alert fatigue, MTTR drag, ops toil
Slide 4 — Elastic: unified platform OR federated bridge → full consolidate (tie to chosen motion)
Slide 5 — TCO: annual savings %, 3-year cumulative, payback months (12–18 typical)
Slide 6 — Gartner + next exec ask

Add:

## Slide deck outline
(bullets for slides 1–6)

## TCO summary
- Annual savings:
- 3-year cumulative savings:
- Payback: … months
- Savings %: … (15–40% typical)

Same #1 account — use DCOS contacts and opp owner from prompt 1.

1. **3 next steps** tied to the chosen motion (e.g. federated POC scope, renewal TCO workshop, PromQL parity demo)
2. **Who to talk to this week** — real names from CRM; if missing, "confirm with opp owner: [name]"
3. One **internal** Elastic ask (SE, specialist, manager)

Output sections to keep in Claude for Challenge 3:

## Next steps
(numbered)

## Who to talk to
| Person | Role | This week | Owner |

## One-liner for discovery email
(6–10 sentences: pain, Gartner, TCO number, next step — Challenge 3 can expand this)