Competitive Account Research

Competitive Account Research

Generate a comprehensive account brief by combining company enrichment, decision-maker mapping, and engagement history from Amplemarket.

Instructions

When a user asks for research on a target account, compile a multi-source intelligence brief using the following workflow.

Steps

1. Identify the target account. Extract the company name or domain from the user's request. If ambiguous, ask for clarification.

2. Enrich the company by calling mcp__claude_ai_Amplemarket__enrich_company with:

   • domain if the user provided a domain or you can infer it
   • linkedin_url if the user provided a LinkedIn company URL This returns firmographics: industry, size, type, location, description, tech stack, and more.

3. Check internal account data by calling mcp__claude_ai_Amplemarket__list_accounts with the company name or domain to find if this account already exists in the system. If found, call mcp__claude_ai_Amplemarket__get_account with the account id to retrieve:

   • Engagement stats (emails sent, opened, replied)
   • CRM data and opportunity status
   • AI-generated insights
   • Account owner and tags

4. Map key decision makers by calling mcp__claude_ai_Amplemarket__search_people with:

   • company_names or company_domains: [target company]
   • person_seniorities: ["C-Suite", "VP", "Head", "Director"]
   • full_output: true
   • page_size: 20

   Then organize results by department to identify the buying committee.

5. Identify stakeholder gaps. Based on the decision makers found, flag any missing roles that would typically be part of the buying committee for your product category (e.g., if no IT stakeholder was found, note this as a gap).

6. Compile the account brief with five sections:

   Section 1: Company Overview

   • Company name, domain, industry, size, type
   • Headquarters and other locations
   • Description and value proposition
   • Tech stack (if available)
   • Recent funding or growth signals

   Section 2: Key Decision Makers

   • Table of identified stakeholders grouped by department
   • Seniority level and LinkedIn URL for each
   • Highlight the likely economic buyer and champions

   Section 3: Engagement History (if account exists in system)

   • Email engagement metrics
   • Previous outreach attempts and responses
   • CRM opportunity status and stage
   • Account owner

   Section 4: Competitive Landscape

   • Known competitors based on industry and tech stack
   • Potential competitive positioning angles
   • Technology overlap or displacement opportunities

   Section 5: Recommended Approach

   • Suggested entry point (which stakeholder to contact first)
   • Messaging angle based on company profile and pain points
   • Multi-threading strategy across the buying committee
   • Timing considerations

Important Notes

• If list_accounts returns no results, the account is net-new. Note this and skip the engagement history section.
• Prioritize the search for decision makers in departments most relevant to the user's product.
• If the user mentions which product or solution they sell, tailor the Competitive Landscape and Recommended Approach sections accordingly.

Examples

Example 1: Domain-Based Research

User prompt: "Research this account for me: datadog.com"

What the skill does:

1. Calls mcp__claude_ai_Amplemarket__enrich_company with domain: "datadog.com".
2. Calls mcp__claude_ai_Amplemarket__list_accounts with domain: "datadog.com".
3. If account found, calls mcp__claude_ai_Amplemarket__get_account with the account ID.
4. Calls mcp__claude_ai_Amplemarket__search_people with company_domains: ["datadog.com"], person_seniorities: ["C-Suite", "VP", "Head", "Director"], full_output: true.
5. Compiles the five-section account brief.

Example output (abbreviated):

ACCOUNT BRIEF: Datadog

1. Company Overview

2. Key Decision Makers

Revenue/Sales

Engineering & Technical

Marketing

Gap identified: No IT/Security stakeholder found at Director+ level.

3. Engagement History

4. Competitive Landscape

• Direct competitors in their space: New Relic, Splunk, Dynatrace
• Tech stack may include: AWS, Kubernetes, Go
• Displacement angle: If selling complementary tooling, position as enhancing their existing stack

5. Recommended Approach

• Entry point: Jordan Lee (VP Eng), most likely technical evaluator
• Multi-thread to Alex Rivera (CRO) for budget authority
• Messaging: Focus on how your solution complements their cloud-native architecture
• Timing: Previous engagement showed interest (1 reply). Follow up on that thread

Example 2: Company Name Research

User prompt: "Give me intel on Stripe before my call tomorrow"

What the skill does:

1. Calls mcp__claude_ai_Amplemarket__enrich_company with domain: "stripe.com".
2. Checks for existing account via mcp__claude_ai_Amplemarket__list_accounts.
3. Maps decision makers via mcp__claude_ai_Amplemarket__search_people.
4. Returns a concise account brief focused on call preparation.

Example 3: Account with Specific Product Context

User prompt: "Deep dive on Shopify. We sell sales engagement software."

What the skill does:

1. Enriches Shopify and maps decision makers.
2. Focuses decision-maker search on Revenue and IT departments.
3. Tailors competitive landscape to sales engagement tools (Outreach, Salesloft, Apollo).
4. Customizes recommended approach for selling sales engagement software to an e-commerce platform company.

Troubleshooting