← Back to workCase study · Multi-agent automation

NEO: four agents, one approval.

A four-agent system that finds leads, drafts outreach and runs the owner's day from Slack, with a person approving every send.

4Agents

651Tests

Shown with demo data

Problem

Owner-led service businesses have to capture leads, qualify them and follow up, on top of doing the work. I built NEO at Catalyze to automate that, without letting an AI send anything on its own.

Build

01 Find · Atlas

Atlas finds leads from public sources and enriches them.

Fig. 01NEO profile editor where a rep sets pitch, industries, roles and company types · Demo data

Fig. 02One NEO lead expanded: summary, call angle, why now, and the source link · Demo data

02 Write · Hermes

Hermes drafts outreach for each lead.

Fig. 03NEO campaign detail: the shared angle and a day 0, 3, 7 and 14 cadence · Demo data

03 Approve · A person

A person approves every message, in the dashboard or in Slack. Chat can never send: that rule lives in the code, not the prompt.

Fig. 04NEO thread: a drafted first-touch email waiting for a person to approve it · Demo data

04 Send

Only approved messages go out.

05 Remember · Athena

Every action is an event on one append-only ledger, and Athena turns those events into a memory of each lead and client.

Fig. 05NEO opportunities board with leads across working, sent, replied, booked and lost · Demo data

06 Brief · Apollo

Apollo runs the owner's side in Slack: commands, approvals and a daily brief.

Results

Early users, high-ticket sales reps and business owners, told me they booked about 30% more calls in their first two weeks. The tests sit in 30 files; NEO was built from June to August 2026. A speed-to-lead flow, an instant drafted reply to inbound leads, is built and merged but not yet deployed.

My roleSole architect and engineer, building with Claude Code: 116 of 209 commits are co-authored with Claude.

StackPython · SQLite · Claude API · Firecrawl · Slack