Use when preparing for any important meeting, call, pitch, or interview where you need to research a company or person beforehand. Triggers on: "prep for my meeting with", "brief me on [company/name]", "I have a call with", "meeting prep", "research [company] before I meet them", "who am I meeting", "investor call prep", "sales call prep", "client call tomorrow", "partner meeting", "interview at [company]". Always invoke when a person's name, company URL, or meeting description is provided alongside an upcoming meeting.
Research any company + person before a meeting, synthesize the intel, and output a beautiful single-page HTML brief you can open in your browser and reference during the call.
Core principle: Great meetings are won in the prep, not the room. The goal isn't more information — it's the right information, organized by what you need to know first.
Before starting, collect:
If the user gives a partial request ("prep for my call with Acme tomorrow"), infer what you can and ask only for what's truly missing.
read-website-fast MCP — used by agents to read URLs. If not installed, fall back to WebFetch and WebSearch tools. Install: github.com/pskl/read-website-fastsuperpowers:dispatching-parallel-agents — for running the 3 research agents concurrently. If not available, run sequentially.Run these 3 agents in parallel using superpowers:dispatching-parallel-agents:
"[company name]" news site:techcrunch.com OR site:reuters.com (last 6 months)[company name] funding OR acquisition OR launch OR layoffs 2025 OR 2026[name] [company] site:linkedin.com"[name]" "[company]" interview OR talk OR article OR podcastreferences/meeting-types.md → find the relevant meeting type section[company name] competitors and [company name] vs [competitor][company name] [your company/product] (any prior relationship?)After all 3 complete (sequential):
Synthesize into this JSON structure, then call the script:
{
"person": {
"name": "Sarah Chen",
"role": "VP of Sales",
"background": "10 years in SaaS sales, previously at Salesforce",
"cares_about": "Pipeline velocity and rep productivity",
"hook": "She gave a talk on outbound in 2024 — you can reference it"
},
"company": {
"name": "Acme Corp",
"url": "https://acme.com",
"snapshot": ["B2B SaaS, 200-person company", "Series B $40M in Jan 2026", "Serves mid-market retail", "Hiring 10 AEs — signals expansion"]
},
"meeting": {
"type": "sales",
"date": "2026-04-10",
"why_it_matters": "They just raised and are scaling fast. You solve exactly the bottleneck they're hiring around."
},
"openers": [
"I saw your January raise — congrats. What's changed in your pipeline process since then?",
"You spoke at OutboundConf last year about rep ramp time — we're seeing the same problem everywhere.",
"Your CTO's recent post about tooling consolidation caught my eye — that's exactly what we help with."
],
"questions": [
"Where's the biggest drop-off in your current pipeline — top, middle, or close?",
"What does your current stack look like for [relevant category]?",
"What would a win look like from your side in the next 90 days?"
],
"watch_out": [
"They just switched CRM providers — may have integration fatigue",
"Budget cycles reset in Q3 — don't push for immediate commitment"
]
}
Meeting type values: sales | investor | interview | partnership | client | other
python3 scripts/generate_brief.py --json data.json --output meeting-brief-sarah-chen-2026-04-10.html
# Windows: start meeting-brief-*.html
# Mac/Linux: open meeting-brief-*.html
The JSON above maps to these 7 rendered sections:
| # | Section | What Goes Here |
|---|---|---|
| 1 | Header | Person name + role, company + meeting type badge, date |
| 2 | Company Snapshot | 4-5 bullets: what they do, size/stage, customers, 1 recent milestone |
| 3 | Person Intel | 2-line career summary, what they care about, any shared hook |
| 4 | Why This Meeting Matters | 2-3 sentences: what they want, what you want, where alignment is |
| 5 | 5 Conversation Openers | Each tied to something specific and real from the research |
| 6 | 3 Questions to Ask | Designed to uncover what you actually need to know |
| 7 | Watch Out For | 1-2 sensitivities or friction points to navigate |
Before delivering the brief, verify all of these:
If any gate fails: run another research pass on that specific section. Do not deliver incomplete briefs.
references/meeting-types.md — What to prioritize by meeting type (investor, sales, interview, partner, client)references/research-sources.md — Where to find intel for different types of people and companiesscripts/generate_brief.py — Generates the HTML brief from structured JSON data. Stdlib-only, zero pip installs. Run python3 scripts/generate_brief.py --help for usage.