Meeting Prep

Automated pre-meeting research briefs with company intelligence, stakeholder mapping, and talking point generation. This skill eliminates the 20-30 minutes reps spend researching before calls by generating comprehensive briefs in seconds.

When to Use This Skill

Use this skill when the user:

• Has an upcoming meeting and needs a research brief on the company and attendees
• Wants to identify key stakeholders at a target account and understand their likely priorities
• Needs talking points tailored to a specific buyer persona and meeting context
• Wants to understand a prospect's competitive landscape before a call
• Is preparing for a QBR, executive briefing, or high-stakes demo

What This Skill Does

Gather the meeting context: company name, attendee names and titles, meeting purpose, and deal stage. At minimum you need a company name. If attendee information is available, use it to generate role-specific talking points.

Build the meeting brief in this structure:

Company Overview: Size, industry, funding stage, revenue (if public), headquarters, and recent trajectory (growing, contracting, pivoting). Keep this to 3-4 sentences — the rep needs context, not a Wikipedia entry.

Recent Signals: News from the last 90 days that creates conversation hooks — funding rounds, executive hires, product launches, earnings results, layoffs, or acquisitions. Prioritize signals that connect to the value you sell. If no recent signals are found, say so explicitly rather than padding with irrelevant information.

Stakeholder Map: For each known attendee, provide their title, likely priorities based on role, probable objections, and suggested talking points. If attendees are unknown, generate a likely meeting roster based on the deal stage and company size, and note that it is inferred.

Competitive Context: Which competitors are likely in the evaluation, based on the prospect's industry, size, and tech stack. For each competitor, provide one positioning statement.

Risk Flags: Surface anything that could derail the meeting — recent layoffs suggesting budget cuts, a new CTO who may re-evaluate vendor decisions, a competitor who recently closed a major customer in the same vertical.

Recommended Talking Points: 5-7 talking points ordered by priority, each tied to a specific prospect signal or stakeholder concern.

Anti-Pattern: "The Generic Brief" A meeting brief that could apply to any prospect in the same industry is useless. "Enterprise SaaS companies typically care about scalability and integration" is not a meeting brief — it is a truism. Every point in the brief should reference something specific to this company: a named executive, a dated event, a concrete metric. If you cannot find specific signals, flag the gap and suggest questions the rep should ask to fill it.

Anti-Pattern: "Information Overload" A 3-page brief that the rep skims for 30 seconds defeats the purpose. The brief should be scannable in under 2 minutes. Use bullet points, bold key names and numbers, and front-load the most actionable intelligence. Details belong in an appendix section, not in the main brief.

When the user provides a calendar invite or meeting link, extract attendee information and meeting context to auto-populate the brief. When only a company name is provided, generate the company-level intelligence and note which sections need attendee information to complete.

Example Prompts

• "Prepare a meeting brief for my call with Acme Corp's VP of Revenue Operations"
• "What should I know before meeting with a Series B fintech company?"
• "Map the stakeholders at Datadog and identify who I should be talking to"
• "Generate talking points for a demo with a prospect evaluating us against Gong"