You have a three-minute screen recording of a conference attendee pane. A thousand people scrolled past.

No API. The app doesn't have one.

No scrapable HTML. The app's an iPad build.

No export. You asked. They said no.

Just pixels.

This situation comes up more than you'd think. Webinar attendee panes. Closed portals. Cvent rosters. CrowdCompass. Any directory somebody could only capture visually. And every time, the instinct is the same: ship the video to a vision model, ask for a spreadsheet, move on.

That instinct is wrong by about 40 percentage points.

The pixels-only rule

If the only copy of the list you can get is a video or a screenshot — no API, no web page you can scrape, no export button — you can't just hand the whole video to a vision model and hope. You have to break the video into pictures of one person at a time and read them one at a time.

That's the whole rule. Everything below it is why.

Why handing the whole video to a vision model fails

Show any vision model (Claude, Gemini, GPT-5) a single frame of the video — a screen with 25 rows of contact data on it — and ask for the whole list as a spreadsheet.

You'll get about 58% accuracy.

This is measured, not guessed. The model's attention thins out over a long list. And Gemini specifically will invent plausible-sounding fake companies — labeling someone "Dallas Fire & Rescue" when they actually work at an ambulance service three states away. The output reads like the real thing. It isn't.

The worst part: you can't spot the fake rows by eyeballing the spreadsheet. They look exactly like the real ones. The only way to catch them is to compare a sample back to the original video — and if you knew to do that, you'd already be halfway to the fix.

The fix: read one person at a time

Cut each row out of the frame as its own little picture. Read those little pictures one at a time instead of handing the whole frame over at once. Accuracy jumps to 99%.

The tradeoff is compute — you're now reading a thousand small pictures instead of thirty big ones — but you can run a bunch of Claude agents in parallel, so the wall-clock time is about the same. Ten minutes either way.

Why it works: when a model is looking at 25 rows at once, its attention is spread thin. When it's looking at one row in isolation, its attention is dense. A single row on screen has nowhere to drift.

Who Gets This

Most people run the video through Gemini, accept the 58%, and ship garbage lists. The move is a boring one-row-at-a-time pipeline that's been tuned on real runs.

• Free: the pixels-only rule, why reading the whole frame fails, and why Gemini in particular invents fake companies.

• $50/mo (most readers start here): the seven-step build, the exact thresholds that work, the de-duplication gotcha that breaks every first attempt, the agent-dispatch pattern, the audit step you can't skip.

• $2,499/yr: Every tool I ship. Edge Copilot is how you talk to all of it through Claude Code. Current tools: Edge Copilot, AutoClaygent, Agent 7, Who to Target and What to Say, Blueprint Cloud, Technology Finder, Video List Extractor. Whatever ships next is included. Plus all 3 courses + weekly office hours.

Read more

Your customers already told you why they buy. And why they churn. And when they started shopping your competitor.

It's all in the calls. Hundreds of them. Sitting in Gong.

Nobody reads them all. The VP of CS watches a clip here and there. RevOps skims the AI summaries. But the insight that matters — the pattern across all the calls — stays buried.

I built something that digs it out. It's called Blueprint Swarm, and I just open-sourced it.

Why a Swarm?

Here's the thing about call data: the gold is in the aggregate.

One call tells you one customer's story. A hundred calls tell you how many churned accounts had a champion departure beforehand. How many days in advance the warning signals appeared. Which product gaps keep showing up across unrelated accounts.

Those patterns don't emerge from reading 5 calls. Or 50. They emerge from reading all of them — and counting.

A single analyst? Tapped out by call 30. Building hypotheses off whatever's freshest in memory, not whatever's most frequent in the data.

A swarm of AI agents? Each one reads a batch independently. A synthesis agent finds the cross-cutting patterns. An auditor verifies every quote. The aggregate emerges.

The S.W.A.R.M. Method

Every run follows five phases:

Scan

Profile your data directory. Auto-detect formats — Gong JSON, Chorus exports, Salesforce CSV, HubSpot CSV, raw transcripts, PDFs. Tell you exactly what analysis is possible with what you have.

Weigh

Based on your data, recommend the right analysis: churn intelligence, win patterns, competitive intel, product gaps, playbook extraction. You pick what matters most.

Audit

Before launching a single agent, test the extraction approach on 3-4 sample records. Right in front of you. Validate output quality before spending tokens on 200 records. Most people skip this step. Don't.

Run

Waves of 6-10 agents running concurrently. Sonnet for extraction — each reads a pre-prepared batch file, analyzes every record, writes structured output. No searching, no exploring. Read. Think. Write. When all analysts finish, an Opus auditor runs a 7-point quality check.

Merge

Synthesis agent deduplicates findings across all batches, scores confidence (HIGH = 3+ independent batches confirmed it), and generates three outputs: JSON for your systems, Markdown for Slack, interactive HTML playbook with source-tagged quotes.

The Agents

Six of them. Each with a job.

The churn analyst reconstructs why accounts left. Chronologically. With warning signals, lead times, and specific intervention points. Not "they churned because of product issues." The full timeline: when did support tickets spike? When did the champion stop showing up to calls? What feature gap was raised and never addressed?

The win analyst does the inverse. What actually closed the deal? Which pain resonated? Who championed it internally and what did they say?

The pattern extractor pulls structured data from every record — pain points, competitor mentions, product gaps, buying signals.

The synthesis agent finds the cross-cutting patterns. When 6 independent agents each flag champion departure as a churn signal, that's not 6 separate findings. It's one high-confidence finding, independently verified. The synthesis agent deduplicates and scores.

The auditor runs on Opus. Spot-checks 20 random quotes against source transcripts. If a quote was paraphrased — flagged. Fabricated — critical failure, score drops to zero. If quality falls below 7/10, results don't proceed to Merge. Non-negotiable.

The classifier categorizes every record before the analysts touch it.

It Runs Overnight

Got a big dataset? Start it in tmux. A watchdog script monitors for rate limits. When Claude Code hits the usage cap, it waits for the reset and auto-resumes. State saves after every wave. Nothing is lost.

Go to sleep. Wake up to a completed analysis.

The Methodology Matters More Than the Tool

This isn't a summarizer.

Every agent follows Blueprint GTM methodology:

Pain-qualified segmentation. The agents don't classify by firmographics. They classify by pain — what specific situation made this customer need you right now?

Specificity breeds trust. The standard isn't "many customers mentioned competitors." It's the exact count, percentage, and context — traced to specific calls. Generalities breed skepticism.

Source-tagged everything. Account name, call date, speaker role, verbatim quote. Every finding has a provenance trail.

Remove the methodology and you have a summarizer. Keep it and you have customer intelligence.

Why Give This Away?

The hard part was never the tool. It was figuring out what to look for.

Most teams already have hundreds of recorded calls. They just aren't extracting intelligence from them systematically. Blueprint Swarm makes the extraction trivial. The methodology is what makes the output actionable.

Try It

git clone https://github.com/SantaJordan/blueprint-swarm

Put your data in a directory. Open Claude Code. Run `/blueprint-swarm /path/to/your/data`. Answer a couple questions about what you want to learn. Watch agents work.

You need Claude Code. That's it. No API keys. No infrastructure.

Your customers have been telling you everything. Start listening at scale.