Claude Skill

account-research

Build a complete account sheet before a meeting - company, people, news, tech, pains, and talking angles. Use before any important prospect or client interaction.

LLM Mart · 0 points · 0 views 26 listing impressions 0 install-command copies
Virus-scanned Reviewed automatically before listing.

Full trust report

Download navinspire-ia-navin-navin_skills_account-research-e9c73a3.zip · 1 KB
Part of navinspire-ia/navin — 182 skills

Install

skills CLI npx skills add https://github.com/Navinspire-ia/navin/tree/main/navin/skills/account-research
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install navinspire-ia-navin@llmmart
Git git clone https://github.com/Navinspire-ia/navin.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole navinspire-ia/navin collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Account Research

Walk into every meeting knowing more about their context than they expect. Timebox research; separate facts from hypotheses.

When to use

  • Before discovery calls, demos, or strategic meetings
  • Deep-dive on a single target account

When not to use

  • Bulk list building (lead-prospector)
  • Presenting hypotheses as facts to the prospect

The account sheet

## Account - <Company> (<date>)
### Company
- What they do (their words) - size, geography, structure
- Business model & who THEIR clients are
- Recent news: funding, projects, expansions, incidents (URL + date)
### People (per attendee)
- Role, tenure, background, recent public statements
- Likely personal win from this project
### Signals
- Tech stack hints (site, job postings)
- Hiring patterns → priorities
- Public tenders / projects when relevant
### Hypotheses (to verify in meeting)
- Top 3 likely pains with evidence
- Budget/timing signals
### Angles
- Openers & smart questions
- Relevant references/cases of ours
- Risks (incumbent? bad history?)

Sources

web_fetch site (about, news, careers) · web_search news + hiring · public profiles · reviews · tender platforms · entity-research · buying-signals.

Workflow

  1. Timebox: 15 min routine / 45 min big meeting / half-day strategic.
  2. Fill the sheet; tag every claim with source URL or unverified.
  3. Store sales/accounts/<company>/research.md; brief top 5 points in chat.
  4. After the meeting: update via discovery notes - the sheet lives.

Rules

  • Public sources only.
  • Hypotheses are for the meeting to test - never sell them as facts.
  • Prefer recent evidence (<90 days) for timing claims.

Anti-patterns

  • Wall of unstructured browser notes
  • Invented org charts
Files (navin)
  • SKILL.md 2 KB
    ---
    name: account-research
    description: Build a complete account sheet before a meeting - company, people, news, tech, pains, and talking angles. Use before any important prospect or client interaction.
    metadata: {"navin":{"emoji":"🗺️","category":"sales"}}
    ---
    
    # Account Research
    
    Walk into every meeting knowing more about their context than they expect. Timebox research; separate facts from hypotheses.
    
    ## When to use
    
    - Before discovery calls, demos, or strategic meetings
    - Deep-dive on a single target account
    
    ## When not to use
    
    - Bulk list building (`lead-prospector`)
    - Presenting hypotheses as facts to the prospect
    
    ## The account sheet
    
    ```markdown
    ## Account - <Company> (<date>)
    ### Company
    - What they do (their words) - size, geography, structure
    - Business model & who THEIR clients are
    - Recent news: funding, projects, expansions, incidents (URL + date)
    ### People (per attendee)
    - Role, tenure, background, recent public statements
    - Likely personal win from this project
    ### Signals
    - Tech stack hints (site, job postings)
    - Hiring patterns → priorities
    - Public tenders / projects when relevant
    ### Hypotheses (to verify in meeting)
    - Top 3 likely pains with evidence
    - Budget/timing signals
    ### Angles
    - Openers & smart questions
    - Relevant references/cases of ours
    - Risks (incumbent? bad history?)
    ```
    
    ## Sources
    
    `web_fetch` site (about, news, careers) · `web_search` news + hiring · public profiles · reviews · tender platforms · `entity-research` · `buying-signals`.
    
    ## Workflow
    
    1. Timebox: 15 min routine / 45 min big meeting / half-day strategic.
    2. Fill the sheet; tag every claim with source URL or `unverified`.
    3. Store `sales/accounts/<company>/research.md`; brief top 5 points in chat.
    4. After the meeting: update via discovery notes - the sheet lives.
    
    ## Rules
    
    - Public sources only.
    - Hypotheses are for the meeting to test - never sell them as facts.
    - Prefer recent evidence (<90 days) for timing claims.
    
    ## Anti-patterns
    
    - Wall of unstructured browser notes
    - Invented org charts
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.

Related