sales-account-intelligence

Bangun intelijen akun yang siap penjualan untuk perusahaan, prospek, pelanggan, mitra, dan pembeli target. Gunakan saat pengguna meminta persiapan penjualan, ringkasan akun,…

npx skills add https://github.com/tavily-ai/use-case-skills --skill sales-account-intelligence

Sales Account Intelligence

Workflow

Use search and extract to produce fast, useful sales account context with cited sources; use map or crawl only when a known company site needs scoped navigation. Keep this skill focused on research planning, query construction, source selection, and sales-ready synthesis; execution mechanics should come from companion endpoint skills.

Treat the guidance below as base guidance; adapt it to the user's request when appropriate.

  • Define the account, audience, sales motion, geography, and meeting or outreach goal.
  • Split research into short subqueries under 400 characters: company overview, recent news, products, customers, leadership, funding/financials, hiring, partnerships, pain points, and relevant initiatives.
  • Use search for discovery, then filter by source quality before extracting.
  • Extract the strongest sources: official website, newsroom, product pages, customer stories, investor/press pages, credible news, job postings, and relevant executive profiles.
  • Use site navigation when the company site is large and useful pages are hard to find.
  • Collect scoped site sections only when the user needs broad coverage of customers, case studies, news, products, solutions, or careers.

Research Budget

  • Start with a small focused search set: account overview, recent triggers, product/initiative context, and buyer/pain-point evidence.
  • Extract only the strongest sources before drafting the brief.
  • Add more searches only for named gaps that block the brief, such as missing trigger events or missing official product context.
  • Do not use map until search finds the company domain and there is a specific buried page type to locate.
  • Do not use crawl for first-pass account prep unless the user explicitly asks for a site scan.

Capability Guidance

  • Use search for most account briefs, meeting prep, outreach research, and trigger-event checks.
  • Use extract on selected official pages, newsroom posts, customer stories, credible news, job postings, and executive profiles.
  • Use map when the company domain is known but important pages are buried.
  • Use crawl for account site scans only after narrowing to sections that support the sales goal.
  • Use research only when the user asks for a deep strategic account report.

Query And Source Guidance

  • Include company name, aliases, product names, executive names, industry terms, geography, and the sales motion in separate subqueries.
  • For trigger events, use explicit recency language and search for funding, hiring, partnerships, launches, expansion, regulation, incidents, and leadership changes.
  • Prioritize official company pages, newsroom posts, customer stories, product pages, investor or press pages, credible news, job postings, and relevant executive profiles.
  • Treat LinkedIn-style profile snippets, unsourced lists, and old syndicated pages as lower confidence.
  • Report failed or inaccessible sources when they affect trigger events, official pages, customer evidence, or buyer context.

Output Template

Use this markdown structure and keep it practical:

# Account Brief: <company>

## Account Snapshot
- What they do:
- Size/market/geography:
- Relevant products or business lines:

## Trigger Events
- <event>: <why it matters> ([source](URL))

## Business Priorities And Likely Pain Points
- Priority:
- Evidence:
- Sales relevance:

## Buyer And Executive Context
- Person/team:
- Relevant context:
- Confidence:

## Outreach Angles
- Angle:
- Supporting evidence:
- Discovery question:

## Source Gaps
- <missing or uncertain item>

Keep claims practical. Do not invent budget, intent, internal priorities, or buyer names when sources do not support them.

Lebih banyak skill dari tavily-ai

academic-scientific-research
tavily-ai
Temukan, saring, dan sintesis makalah akademis, literatur ilmiah, laporan teknis, pracetak, publikasi klinis atau biomedis, dan bukti seputar…
crawl
tavily-ai
Ekstrak dan simpan konten situs web sebagai file markdown untuk akses dan analisis offline. Mendukung kedalaman crawl yang dapat dikonfigurasi (1-5 level), batas luas, dan batas halaman untuk menyeimbangkan cakupan dengan kinerja. Termasuk pemfilteran jalur melalui pola regex untuk fokus pada bagian tertentu dan mengecualikan konten yang tidak relevan. Menawarkan dua mode: ekstraksi halaman penuh untuk pengumpulan data, atau pemotongan semantik dengan instruksi bahasa alami untuk memasukkan hasil ke dalam konteks LLM. Menyediakan API Peta pendamping untuk URL...
extract
tavily-ai
Ekstrak konten bersih dari URL tertentu menggunakan API ekstraksi Tavily. Mendukung hingga 20 URL per permintaan dengan peringkat ulang berbasis kueri opsional untuk fokus pada potongan konten yang relevan. Dua mode ekstraksi: dasar untuk ekstraksi teks cepat, lanjutan untuk halaman yang dirender JavaScript dan data terstruktur. Otentikasi OAuth otomatis melalui browser pada saat pertama kali dijalankan, atau konfigurasi kunci API manual di pengaturan. Mengembalikan format markdown atau teks biasa dengan URL gambar opsional dan batas waktu yang dapat dikonfigurasi hingga 60 detik.
investment-research-briefs
tavily-ai
Buat ringkasan riset investasi yang ringkas, memo perusahaan, gambaran sektor, pembaruan pemantauan portofolio, ringkasan laba/berita, ringkasan risiko dan katalis,…
product-competitor-intelligence
tavily-ai
Riset produk pesaing, SKU, harga, kemasan, positioning, perbandingan fitur, katalog produk, halaman kategori, daftar pengecer, marketplace…
research
tavily-ai
We need to translate the given English text into Bahasa Indonesia. The instruction says to preserve product names, protocol names, URLs, numbers, and technical terms. The name "research" is to be preserved if it appears in the source text, but we are not to include the name unless it appears. The source text does not contain the word "research" as a standalone name? Actually it starts with "Comprehensive research on any topic..." so "research" is part of the text. But the instruction says "Do not include the name unless it appears in the source text." So we keep it as is. Also preserve "Tavily MCP server", "OAuth", etc. Translate the rest naturally. Let me translate: "Comprehensive research on any topic with automatic source gathering, analysis, and citations." -> "Riset komprehensif tentang topik apa pun dengan pengumpulan sumber, analisis, dan kutipan otomatis." "Conducts multi-source web research with explicit citations, ideal for comparisons, current events, market analysis, and detailed reports
search
tavily-ai
Pencarian web dengan hasil yang dioptimalkan untuk LLM, penilaian relevansi, dan penyaringan fleksibel. Mendukung empat mode kedalaman pencarian (ultra-cepat, cepat, dasar, lanjutan) dengan pengaturan latensi dan tradeoff relevansi yang dapat dikonfigurasi. Termasuk penyaringan domain, batasan rentang waktu, rentang tanggal, penguatan negara, dan ekstraksi konten mentah. Mengembalikan hasil dengan judul, URL, cuplikan konten, dan skor relevansi; hasil gambar opsional dan favicon. Otentikasi OAuth otomatis melalui server Tavily MCP atau konfigurasi kunci API;...
tavily-best-practices
tavily-ai
API pencarian web untuk LLM dengan akses data real-time, ekstraksi konten, perayapan situs, dan riset bertenaga AI. Lima metode inti: search() untuk hasil web, extract() untuk konten URL, crawl() untuk ekstraksi seluruh situs, map() untuk penemuan URL, dan research() untuk sintesis AI ujung-ke-ujung. Mendukung SDK Python dan JavaScript dengan klien asinkron untuk kueri paralel dan kedalaman pencarian yang dapat dikonfigurasi (ultra-cepat/cepat/dasar/lanjutan). Metode crawl menerima instruksi semantik untuk memfokuskan ekstraksi pada...