DCOS Guide — Build TCO Model

Copy each block → paste into Claude Desktop. Use your #1 account + competition from Challenge 1. Live CRM via DCOS only.

After you know the competition — pick a motion

Displace — Datadog, Dynatrace, New Relic, Splunk SaaS at renewal. Connect → convert dashboards/alerts → Elastic backend; 4× TCO, same-day migration story.

Consolidate — Prometheus / Mimir / Grafana sprawl. Keep PromQL and dashboards; Elastic is the unified metrics + logs + APM backend (zero dashboard rewrites).

Federated Data Sources — Cannot rip-and-replace yet (dual-run, compliance, or data must stay in place). Query and analyze metrics/logs where they live through Elastic connectors and federated views; unify in Kibana/ES|QL while you plan full ingest.

Before you start

1. CRM + competition check

Run first

Challenge 2 — Build TCO — my #1 consolidation account from Challenge 1.

Use DCOS only for facts (no invented ARR, vendors, or contacts). dcos_sfdc_query uses BigQuery SQL (default CRM):
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 |

2. Displace vs Consolidate vs Federated Data Sources

Pick the play

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)

3. TCO + slide deck (CFO story)

Main exercise

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)

4. Next steps & who to talk to

Finish in Claude

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)