Example prompts by persona

Copy into Claude Desktop after install. DCOS pulls Salesforce + your watchlist, researches the web, and formats output for your role. Replace bracketed placeholders with real account and opp names.

SDR · Prospecting & discovery

Research an account before outbound

Pre-qualify I, M, C — trigger events, ICP fit, and discovery questions mapped to Elastic Observability, Search, and Security.

Claude prompt — account research

Run dcos_user_profile, then dcos_sfdc_sync.

I'm an SDR researching [Account Name] before my first conversation with the [Observability | Search | Security] team.

1. dcos_search — prior notes, industry, and any existing Elastic footprint
2. Jina — past 30 days: earnings, layoffs/hiring, cloud migration, breach/SOC news, GenAI initiatives
3. dcos_sfdc_query — open tasks, recent activities, and related contacts if in CRM

Output:
## Trigger events (ranked)
## ICP fit — Observability / Search / Security (1–5 each with evidence)
## Discovery questions (8–10)
   - 3 for Observability (OTel, tool sprawl, MTTR, log volume)
   - 3 for Search / GenAI (RAG, vector, customer-facing search)
   - 3 for Security (SIEM, endpoint, alert fatigue, consolidation vs Splunk)
## Outbound hook (2 sentences, no EB claims)
## MEDDPIC pre-qual: I, M, C only — gaps to validate on the call

Do not invent ACV, stage, or contacts not in CRM.

Claude prompt — post-call follow-up

I just spoke with [Title] at [Account] about [pain theme].

Summarize MEDDPIC pre-qual (I, M, C). Draft a follow-up email that ties their pain to Elastic [Observability | Search | Security].
Suggest the right AE/SA handoff and dcos_add_note with source: sdr_discovery.
Solution Architect · Tech win tracking

1-2-3 weekly tech-win update

Standard SA format for deal reviews, Slack updates, and StratTrack notes — path to tech win, last week, this week.

Claude prompt — generate 1-2-3

Run dcos_user_profile and dcos_sfdc_sync.

Produce a Solution Architect 1-2-3 update for opportunity [Opp Name] at [Account].

Use dcos_sfdc_get_opportunity, dcos_search (MEDDPIC + technical blockers), and Jina for competitive context.

Format exactly:

[Today's date] - [My initials]

1. THE PATH TO TECH WIN IS...
[One paragraph: decision criteria, architecture outcome, competitive angle, $ metrics tied to D and M in MEDDPIC]

2. LAST WEEK. I...
[Past tense bullets: workshops, PoC progress, criteria validated, EB/technical buyer meetings]

3. THIS WEEK. I...
[Forward actions with owners: waiting-on names, deliverables, close blockers]

Rules:
- Ground $ amounts and dates from CRM only
- Name Elastic products (Observability/OTel, Security/SIEM, Search/vector)
- End with one technical risk + mitigation
- dcos_add_note with the 1-2-3 text (source: sa_123)

Claude prompt — PoC / eval brief

SA technical brief for [Account] — eval stage.

Build decision criteria matrix (customer requirements vs Elastic vs [Competitor]).
PoC scope: success metrics, timeline, data sources, out-of-scope.
Blocker list with owner (SA/AE/customer) and resolution path.
Use dcos_search for prior architecture notes.
Account Executive · Deal coach

Call prep and MEDDPIC coaching

Scorecard, talk track, and next action from live pipeline — never invent CRM fields.

Claude prompt — deal coach

Run dcos_user_profile and dcos_sfdc_sync.

Coach me on [Account] — opportunity [Opp Name], close date [from CRM].

Output:
## MEDDPIC scorecard (0–3 per letter with evidence from dcos_sfdc_get_opportunity + dcos_search)
## Weakest letter + why it matters now
## Talk track for my next call (3 bullets)
## Discovery questions to close gaps (5)
## Competitive positioning vs [Competitor if known]
## One next action — owner, date, success criteria

dcos_add_note with material MEDDPIC changes (source: ae_coach).

Claude prompt — multi-threading plan

For [Opp Name] at [Account]: map known contacts from CRM and notes.
Who is missing for E and C in MEDDPIC? Suggest 3 personas to engage (EB, champion, technical buyer).
Draft intro ask for my champion to open a door.
Area VP · Territory pulse

Leadership briefs and rep handoffs

Territory rollup — heat map, talking points, one action per rep. Ideal for morning routines or Monday staff meetings.

Claude prompt — morning brief

Run dcos_user_profile and dcos_sfdc_sync.

Produce my AVP Executive Daily Brief for [Quarter].

1. dcos_sfdc_list_opportunities — open pipeline on my watchlist
2. Per account: dcos_search + Jina (qdr:w) for material changes
3. Jina — Elastic/competitive news + my region from profile
4. Compare to prior dcos_search notes — MEDDPIC deltas only

Output (plain English, scannable — like an executive morning brief):

# Executive Daily Brief — {territory}
**Updated:** {date/time}

## What matters today
## What to watch
## What this means for me
## Today's game plan
## Your priority actions today
## Sales + executive implications
## Deals at risk today
## Territory snapshot
## High-priority setups
## World / macro
## Markets
## {Region} — local context
## Elastic
## Rep handoffs

dcos_add_note summarizing territory changes (source: avp_brief).

Claude prompt — QBR prep

QBR prep for [Rep Name]'s patch.

Roll up: commit vs best case, deals at risk (weakest E or P), coaching theme for the quarter.
3 questions I should ask in the 1:1 based on MEDDPIC gaps in their top 5 opps.
Customer Architect · Expansion & health

Customer health and expansion plays

Existing customers — adoption signals, expansion use cases, and reference potential.

Claude prompt — customer brief

Run dcos_user_profile and dcos_sfdc_sync.

Customer Architect brief for [Account] (status: customer).

Filter watchlist for status: customer. Use dcos_search for deployment notes, support themes, expansion history.
Jina — customer news, earnings, engineering initiatives (past 90 days).

Output:
## Health signals (usage/adoption themes from notes — trend ↑/↓/→)
## Expansion opportunities (use case → Elastic product → impact)
## Risk signals (layoffs, competitor POC, leadership change)
## Reference / advocacy potential (1–5 + rationale)
## Recommended actions (CA, AE, SA) with dates

Reframe MEDDPIC for expansion: new M, E for expansion BU, I in adjacent team, C for next product line.

Claude prompt — QBR with customer

Prepare a Customer Architect QBR deck outline for [Account].

Sections: value delivered (metrics from notes), adoption roadmap, expansion plays (Observability → Security cross-sell),
open support themes, and 3 questions for their VP sponsor.