<- AI Systems Dossier
ENTRY NO. 04Sales Technology / GTM EngineeringLive deliveryAgentic Workflows / Browser AutomationLIVE

Scoutbound

Identity · Agentic workflow

Agentic prospecting workflow — website inspection, structured extraction, ICP scoring, and CRM-ready export

Agentic Workflows / Browser Automation
Problem

Manual tab-by-tab website inspection — no reproducible research methodology.

System Flow
7 stages · click to inspect
->
->
->
->
->
->
Click any stage to inspect
Signature Module · Agentic workflow

Replay workflow

Agentic Workflows / Browser Automation

Step through one company workflow: browser inspection, extraction, scoring, reasoning, and CRM-ready export.

Workflow Trace · acme-corp.com● live
INPUTdomain: acme-corp.com · pre-flight ✓
INSPHomepage + About + Careers· 52s
Full JS render · Playwright Chromium
EXTR7/8 fields extracted · conf: HIGH
Category: "Revenue operations SaaS"
Signal: hiring RevOps engineer ★
↓ ICP rubric · 5 dimensions· 1.2s
SCORE82 / 100 · STRONG FIT
OUT→ HubSpot · 91% completeness· 2m 14s total

Business Impact

Outcomes
Before

Research method: Manual tab-by-tab web inspection

->
After

Research method: Playwright browser agent per company

The full prospect research workflow — from company list to enriched, scored, CRM-ready profiles — runs automatically. Key metrics are prototype benchmarks from controlled evaluation: 4× speed improvement, 83% extraction consistency, 71% lead relevance precision, 91% CRM field completeness. These are not yet measured against tracked production outcomes.

Faster prospect research
91%
CRM field completeness
83%
Extraction consistency

Engineering Evaluation

Nightly eval
83%
Extraction Consistency
71%
Lead Relevance Precision
91%
CRM Handoff Completeness
94%
Workflow Completion Rate
Headline business result
Faster prospect research

Why This Is Hard

4 engineering challenges
Challenge · 01

JavaScript-heavy SPAs break naive HTTP scraping

Playwright's full Chromium rendering captures JavaScript-executed content. Pages relying on authentication walls or heavy AJAX are flagged as partial-extraction, with a manual-review recommendation included in the export.

Challenge · 02

Extraction schema drift

company websites have wildly different HTML structures. LLM-based extraction handles structural variation, but confidence calibration is critical: fields with LLM confidence below threshold are flagged in the review_needed column rather than silently included in the CRM export.

Challenge · 03

Workflow timeout and partial failure handling

a 90-second per-company timeout prevents runaway browser sessions. Partial results (some pages inspected, not all) are saved per company; the export includes an extraction completeness score per record so users know what was captured vs what needs manual review.

Challenge · 04

ICP scoring consistency across a batch

GPT-4o-mini scoring was inconsistent on similar companies when prompted per-company. Stabilised by generating the scoring rubric once at workflow start (not per company) and applying it identically across all companies in the batch.

Engineering Depth

5 topics · click to expand

Playwright runs in async mode with configurable concurrency (default: 3 parallel browser contexts per run). Each context handles one company: homepage + About + up to 2 additional pages. A Redis-backed task queue manages company dispatch. Per-page timeout: 30s. Per-company timeout: 90s. Failed pages retry once with a longer wait (45s). Partial results are preserved for companies where at least one page succeeded.

Key numbers
2m14sAvg workflow completion
83%Extraction consistency
Built withAgentic WorkflowsBrowser AutomationStructured ExtractionICP ScoringCRM