← Back to library
SalesWorkflow

Get a briefing on 40 conference attendees in five minutes

Claire Morrison of Technically Curious had an event coming up where she knew none of the 40 attendees. Rather than an evening on LinkedIn, she handed Claude Code the names; it researched them in parallel through her logged-in browser via Chrome MCP and produced a participant briefing in about five minutes. Her co-author uses the same idea before prospect calls.

  • OutcomeWalk into an event knowing who everyone is: hand over a name list and get one document summarizing each person's role, background and talking points.
  • SetupMinutes
  • LevelIntermediate
  • CreditClaire Morrison
View original
Works with
Claude Code

Published Oct 23, 2026Updated Oct 23, 2026AI dry run on sample input: passed Oct 23, 2026Source verified Oct 23, 2026

When should you use it?

  • You have an attendee or meeting list
  • You want talking points before you arrive
  • You use LinkedIn in your own browser

Not for: Collecting personal data for resale; Events whose attendee lists are confidential

What do you need, and what do you get?

You need

  • A list of names and companies
  • Claude Code connected to your Chrome
  • Optional search and scraping tools

You get

  • One briefing document
  • A short profile per person
  • Suggested conversation openers

How does it work, step by step?

  1. Paste the listGive names, companies and the event context.
  2. Research in parallelLet the agent open profiles in your signed-in browser and gather public details.
  3. Add email contextFor prospects, have it include anything from existing threads with their team.
  4. Compile one documentGroup people sensibly and keep each profile brief.
  5. Review before the eventSkim and correct anything that looks off.

The prompt

Our own prompt, inspired by Claire Morrison and written to work in Claude Code. Values in lime are placeholders.

Prompt0 variables
Here is the attendee list for [event]: [names and companies]. Using my signed-in Chrome, look up each person's current role, company, recent public posts and one or two relevant talking points for me as [my role]. Put everything in one document grouped by [company type]. Mark any match you are unsure of. Do not connect, follow or message anyone.

Inspired by Claire Morrison: Have Claude Browse The Web For You. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • Profiles can belong to someone with the same name; check photos or companies.
  • Heavy automated browsing may trip site limits.

Our take

Claire Morrison of Technically Curious had an event where she knew none of the forty attendees. Rather than an evening clicking LinkedIn profiles, she handed Claude Code the names; it researched them in parallel through her logged-in browser via Chrome MCP and produced a participant briefing in about five minutes. Her co-author uses the same idea before prospect calls. Keep the brief to public professional information and resist adding personal details that are irrelevant to a work conversation. Ask the agent to mark low-confidence matches so you do not greet the wrong person by the wrong job title. After the event, the same document is a ready start for follow-up notes. Do not store sensitive inferences, and delete or archive briefings you no longer need. Prefer sources the person chose to publish. Never let the agent send connection requests or messages on your behalf during research. Skim every card before you walk into the room.

Where the time goes back: An evening of profile clicking becomes a short review of one document.

FAQ

How long did it take?
Around five minutes for 40 people, versus an evening by hand.
What else do they use browsing for?
Building prospect lists from exhibitor pages, checking their own HTML output and booking travel in a company system.

Source and credit

Inspired by Claire Morrison. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
Have Claude Browse The Web For You
Creator
Claire Morrison
Published on
technicallycurious.substack.com (Substack)
Original date
Mar 16, 2026
License
Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
Originally for
Claude Code
AI dry run
Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails.
Verified
Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.

Are you the creator? Claim or correct this page.

More in Sales

All 59 Sales playbooks →

Related playbooks

SalesWorkflow✓ AI dry run

Audit an outbound campaign before it launches

Before an outbound campaign goes live, an agent checks inboxes, email validity, recipient email providers, copy, settings, AI variables and spintax, and fixes what it can.

Credit: Dan Rosenthal (@dan__rosenthal)

An afternoon+
SalesWorkflow✓ AI dry run

Run a cold-email reply desk from one written charter

Hand positive cold-email replies to a single-purpose agent that follows a written charter, answers within minutes, books the call and updates the CRM, asking you only about odd cases.

Credit: Max Pidvalnyi (@marioleads)

An afternoon+