Your BD Pipeline Is A Good First Autonomous Agent

An end-to-end BD pipeline that runs itself on a weekly cron: it sources leads, researches them, drafts the outreach, and emails me the two or three things to do this week. Sourcing → research → draft → nudge, with a lightweight CRM to run it from. One rule holds everywhere: the system researches and drafts; a human always sends.

Why this is worth five minutes of a GTM room’s time: almost every agent demo shows one primitive at a time — here’s tool use, here’s a cron, here’s memory. That leaves you knowing the parts and not the shape. BD is a workflow everyone in this room already has opinions about, which makes it a good place to see the whole surface area doing real work at once. The demo is a guided tour of that: I trace one target end to end, and name the primitive earning its keep at each step.

The tour, following one company through the system:
It gets found. The Opportunity Radar treats my ICP as a graph rather than a list. It starts from private-equity sponsors active in my space and walks outward — a locked sub-agent maps each fund’s portfolio in parallel threads, and qualified portfolio companies auto-feed the pipeline. The frontier of unvisited sponsors lives in a memory store, so the walk resumes each Monday instead of cold-starting. Ownership structure is what makes a buyer resemble my last buyer, so the graph edge qualifies better than a keyword match.
It gets carded. The Radar pushes the target into my CRM over MCP — the CRM is itself an MCP server, so the agents and I drive the same pipeline through the same tools.
It gets researched. A graded session produces a seven-section pre-call brief off the live web. The run ships with a rubric; the platform scores the deliverable and sends the agent back to revise before I see it. The verdict lands on the card.
It gets formatted. Skills load the output contract on demand — including a bundled validate_blocks.py the agent runs against its own draft so the CRM can parse the people and portfolio blocks.
It gets drafted. A nightly cron drafts outreach from a compiled brand pack. Secrets come from a vault injected at egress — the agents never see a key.
It stops. The draft sits at the gate. Nothing sends. Pipeline status is never machine-written.

What I’ll show live: the Monday-morning board with fit scores and grader verdicts that arrived without me; one target’s drawer opened — why-now, signals, key people, dossier, draft; the sweep receipt showing what the Radar covered and where it stopped; a rubric and the revision it forced; and the eval scorecard where a prompt change shows up as a delta against a pinned baseline.