Generate pre-call intelligence briefs automatically
prospect-researchskillsetup L1★96
TheCraigHewitt/skills ↗Causal-lift measurements
sales-briefing-24pp vs no-skill baselinewith-skill 60% · baseline 84%
Measured by running the task with and without this artifact, K=5, graded by deterministic checks — no LLM judging.
What it does
Generate pre-call intelligence brief with personalized context
Best for
Sales reps who need to walk into calls with specific context instead of generic questions, especially for outbound first touches where showing research is the difference between credibility and cold-calling.
Inputs
- · Company name
- · Contact name and role (optional)
- · Company website URL
- · How prospect was sourced (inbound/outbound/referral)
- · BUSINESS_CONTEXT.md (ICP, value prop, pain points)
Outputs
- · Company overview paragraph
- · 3-5 likely pain points mapped to your solution
- · 5 personalized conversation starters
- · 3-4 likely objections with response strategies
- · Qualification checklist (budget/authority/need/timeline/competition)
- · 2-3 sentence recommended approach
Preconditions
- · Company name is mandatory
- · BUSINESS_CONTEXT.md should exist in project root (defines ICP and value prop)
- · User should know what they sell
Failure modes
- · Without BUSINESS_CONTEXT.md, pain points become generic
- · Limited public information makes company overview speculative
- · Conversation starters feel forced if no trigger events found
Trust signals
- · Step-by-step workflow (Before Starting → Input → What You Generate)
- · Specific bad/good examples ("I noticed you have 47 employees" vs "significant team growth")
- · Named BANT elements (Budget, Authority, Need, Timeline)
- · Pre-call checklist forces verification before calling