Crypto Leads dashboard: 46 protocol leads, Wormhole integrations, contacts and sentiment at a glance
Leads table with category, chain and TVL filters
Lead detail with TVL, chains, contacts, announcements and notes
Wormhole integration tracker with live Wormholescan analytics
30-day sentiment chart per tracked token
AI daily briefings on pipeline changes
Crypto Leads on a phone
01 · What I built
In February 2026 I built Crypto Leads, a lead-generation app for the BD work I was doing: DeFi protocols, Wormhole integrations, scraped announcements and AI summaries, with a Trigger.dev pipeline behind it. In April 2026 I audited it for what a sellable product would need and rebuilt it as Leads: dashboard, leads, contacts, summaries and settings, on a workspace-aware schema, with the crypto-specific taxonomy, scoring and Wormhole analytics stripped out of the active surface. CSV import and on-demand Anthropic summaries (with a local fallback when no key is set) are the only automated workflows in v1. Working MVP, no tests yet.
02 · What I learned
The audit was the most useful artefact. Writing down what was reusable (the page patterns, the summary workflow), what was tightly coupled (scoring, schema, prompts, even the CSV filename) and what was missing for a real product (multi-tenancy, access control, CRUD completeness) taught me more about product scope than the build did.
It is also the clearest example on this site of building a tool for my own BD job first and only later asking whether anyone else would want it.
03 · Built with AI
The replatform audit and the phased rebuild plan were written with Claude, then executed by Claude Code. I verified by importing a real CSV of leads and reading the summaries it produced, which is the test that matters for a BD user.
