Skip to content
Sales
Skill

/sales-prep

You generate comprehensive meeting preparation briefs that give salespeople everything they need before walking into a prospect meeting. The brief combines company research, attendee intelligence, competitive context, and tactical preparation into a single actionable document.

BOOST
From plugin
ai-sales-team-claude
1.4k13 skills5 agents
Install
$ npx -y skills add zubair-trabzada/ai-sales-team-claude --skill sales-prep --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/sales-prep

Context preview

The summary Claude sees to decide when to auto-load this skill.

You generate comprehensive meeting preparation briefs that give salespeople everything they need before walking into a prospect meeting. The brief combines company research, attendee intelligence, competitive context, and tactical preparation into a single actionable document.

SKILL.md

sales-prep.SKILL.md

Meeting Preparation Brief

You generate comprehensive meeting preparation briefs that give salespeople everything they need before walking into a prospect meeting. The brief combines company research, attendee intelligence, competitive context, and tactical preparation into a single actionable document.

Invocation

/sales prep <url>

Where `<url>` is the prospect company's website URL. Optionally, the user may also provide:

  • Names of meeting attendees
  • Meeting date and time
  • Meeting purpose or agenda
  • Your product/service being discussed

Step 1: Research Phase

Execute the following research tasks. Use WebFetch to gather data from each source. Run as many fetches in parallel as possible to minimize preparation time.

1.1 Company Research

Fetch the prospect's website and extract:

  • **Homepage**: Company description, value proposition, key messaging, target market
  • **About page**: Founding story, mission, team size, office locations, company values
  • **Product/Services pages**: What they sell, pricing model (if public), key features
  • **Blog/News page**: Recent announcements, content themes, thought leadership topics
  • **Careers page**: Open roles (indicates growth areas, team gaps, technology choices, budget allocation)
  • **Case studies/Testimonials page**: Their customers, results they highlight, industries they serve

Additionally, search for:

  • Recent press coverage or news mentions (use WebSearch with "[Company Name] news [current year]")
  • Recent funding rounds or financial events (use WebSearch with "[Company Name] funding OR acquisition OR IPO")
  • Company LinkedIn page activity (recent posts, follower count, engagement patterns)

1.2 Attendee Research

If attendee names are provided, research each person:

  • **LinkedIn profile**: Current title, tenure at company, career history, education, shared connections
  • **Recent LinkedIn posts**: Topics they write about, what they engage with, their professional interests
  • **Conference talks or podcasts**: Have they spoken publicly? What topics?
  • **Published articles or quotes**: Any media appearances or thought leadership?

For each attendee, build a profile that includes:

  • Communication style prediction based on their role and seniority (detail-oriented, big-picture, data-driven, relationship-focused)
  • Personal interests or anchors for rapport building (alma mater, hobbies mentioned in posts, causes they support)
  • Likely priorities based on their role (what KPIs they care about, what keeps them up at night)

If no attendee names are provided, attempt to identify likely meeting participants based on:

  • The company's leadership page
  • The deal stage and meeting purpose (discovery call = VP/Director level, technical demo = engineering leads, contract negotiation = procurement/finance)

1.3 Competitive Landscape

Determine what tools, services, or solutions the prospect currently uses:

  • **Website technology**: Check for known tool scripts, meta tags, integration badges, "powered by" footers
  • **Job postings**: Search their careers page and job boards for tool-specific requirements (e.g., "Experience with Salesforce" in a job description)
  • **Partner/Integration pages**: Do they list technology partners?
  • **Social mentions**: Has the company or its employees posted about specific tools?

For each identified competitor/current solution:

  • Note what the prospect uses it for
  • Identify your key advantages over that solution
  • Identify topics to avoid (do not bash their current vendor)

1.4 Industry Context

Research the prospect's industry:

  • Use WebSearch to find 2-3 recent industry trends or challenges relevant to their space
  • Identify any regulatory changes, market shifts, or competitive pressures affecting their industry
  • Look for industry-specific pain points that your solution addresses

---

Step 2: Build the Meeting Brief

Compile all research into the following sections. Every section must contain specific, actionable information — never generic filler.

Section 1: Cheat Sheet (Quick Reference Card)

This goes at the TOP of the document. It is a condensed one-page reference with the 5 most important things to remember going into this meeting.

Format:

## CHEAT SHEET — [Company Name] Meeting

1. [Most important thing to know about this prospect — one sentence]
2. [Key pain point or opportunity to focus the conversation on]
3. [The most important attendee and what motivates them]
4. [Current solution they use and your biggest advantage over it]
5. [The ONE outcome to aim for in this meeting]

**Opening line**: "[Specific, personalized conversation starter]"
**Key question to ask**: "[The single most important discovery question]"
**Trap to avoid**: "[One thing NOT to say or do in this meeting]"

Section 2: Company Snapshot

Write ONE paragraph (4-6 sentences) that gives a complete picture of the company. Include:

  • What they do and who they serve
  • Company size (employees, revenue if known, funding stage)
  • Growth trajectory (hiring signals, expansion indicators, recent announcements)
  • Key business model details relevant to the sales conversation

Follow with a quick-reference table:

| Field | Detail | |-------|--------| | Company | [Name] | | Website | [URL] | | Industry | [Industry] | | Founded | [Year] | | Employees | [Count or estimate] | | Revenue | [Estimate or range] | | Funding | [Stage and amount if known] | | Headquarters | [Location] | | Key Products | [List] | | Target Market | [Who they sell to] |

Section 3: Attendee Profiles

For EACH attendee, create a profile block:

### [Full Name] — [Title]

**Background**: [2-3 sentences on career history, how long at company, previous roles]
**Recent Activity**: [What they've posted, shared, or spoken about recently]
**Communication Style**: [Prediction: detail-oriented / big-picture / data-driven / relationship-focused]
**Likely Priorities**: [What this person cares about based on their role — specific KPI
Read more
Ships withai-sales-team-claude

AI-powered sales team for Claude Code. Research prospects, qualify leads (BANT + MEDDIC), find decision makers, generate outreach sequences, prepare for meetings, write proposals, and produce PDF pipeline reports — 14 skills, 5 parallel agents.

Get the whole plugin
Stats
1,408
Stars
365
Forks
Quiet
Maintenance
Python
Language
MIT
License
6mo ago
Last commit
7mo ago
Created
17h ago
Added

Repo: zubair-trabzada/ai-sales-team-claude

Other skills on ai-sales-team-claude.