firecrawl-lead-research
Produce pre-meeting lead intelligence briefs with Firecrawl. Use when the user needs company research, person research, recent news, talking points, pain points, or outreach preparation before a sales call, partnership meeting, investor conversation, or customer interview.
What this skill does
# Firecrawl Lead Research Use this to create a concise, actionable pre-meeting brief. ## Onboarding Interview Infer the company, person, meeting context, and desired brief depth from context. If the company is clear, proceed immediately. Ask at most 1-3 concise questions only if blocked, such as the company/person to research or the meeting context. ## Firecrawl Collection Plan Use Firecrawl search and scrape to gather: - company website, about, product, pricing, careers, team, and customer pages - recent news, funding, launches, hiring, partnerships, and press - public person profiles, talks, posts, interviews, and role/background - relevant industry context and likely business challenges ## Parallel Work If appropriate, use sub-agents or equivalent parallel task runners: - Company Profile researcher - Recent News and Activity researcher - Person researcher - Industry/Pain Point researcher Each researcher should return source URLs and only evidence-backed claims. ## Final Deliverable ```markdown # Lead Brief: [Company] ## Company Overview [What they do, stage/size signals, products, customers] ## Recent Activity [News, launches, funding, hiring, partnerships] ## Key People [Relevant people and public background] ## Talking Points [5-7 specific conversation starters] ## Likely Pain Points [Evidence-backed hypotheses] ## Outreach Angle [Suggested positioning or next step] ## Sources [URLs used] ## Rerun Inputs workflow: firecrawl-lead-research company: [name/url] person: [optional] context: [meeting context] ``` ## Quality Bar - Keep it concise and useful before a meeting. - Do not fabricate personal details. - Clearly separate facts from inferred pain points.
Related in Sales & CRM
process-mapper
IncludedUse when a BizOps lead, COO, or process-improvement owner needs to document an end-to-end business process (procurement, employee onboarding, incident handoff, customer-onboarding, claims adjudication) in BPMN-style notation, measure cycle times by stage, surface where work spends most of its time waiting vs. being worked, and quantify the gap between processing time and total elapsed time. Pairs Lean / Six Sigma / Theory-of-Constraints canon with deterministic stdlib-only Python tools to produce a process map, a ranked bottleneck list (with severity + root-cause hypothesis), and a cycle-time analysis (P50, P90, value-add ratio, Little's-Law throughput). Distinct from sales-pipeline, system-reliability (SLO), and strategic-OKR work — this is tactical process documentation for internal operations.
payment-integration
IncludedIntegrate payments with SePay (VietQR), Polar, Stripe, Paddle (MoR subscriptions), Creem.io (licensing). Checkout, webhooks, subscriptions, QR codes, multi-provider orders.
customer-success-manager
IncludedMonitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success
sales-engineer
IncludedAnalyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.
customer-success-manager
IncludedMonitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success
sales-engineer
IncludedAnalyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.