Campaign Manager

Outbound runs across tools that do not see each other. A cold-email platform marks a lead hot, the conversation moves to the founder's Gmail, and the platform never learns the lead replied, so its state goes stale and the CRM inherits a status nobody trusts. Retargeting on LinkedIn is not tied back to the campaign that produced the lead, and a signup or payment in the product is not tied to either. Answering simple questions, like which hot leads went cold this week or which campaign produced a paying customer, means reconciling five tools by hand.

Every source writes into one MongoDB ledger: a leads collection with one document per human carrying every identifier learned about them, and an append-only events collection where each fact has a dedupe key, so re-running a sync or replaying a webhook is harmless. Identity resolution tries provider ids, then email, then canonical LinkedIn URL, and merges leads that turn out to be the same person. Email messages keep their RFC headers so a Gmail reply can be stitched to a campaign thread before the lead's address is even known.

A status engine recomputes each lead after every ingest and on a periodic sweep, purely from events; a human override is itself an event. Attribution records last touch, first touch, and the assist chain for signups, payments, and meetings. HubSpot receives a mapped deal stage and a timeline note explaining each change, and human stage moves made in HubSpot are read back as overrides.

Thirteen scheduled jobs run in-process with APScheduler in a fixed order so downstream jobs see the freshest ledger. Each has cursors, bounded retries, and timeouts; a failing integration never blocks the others, and a dry-run flag logs every outbound write instead of sending it.

Prospecting is a separate guarded pipeline: search, screen on free data, pay to find emails only for survivors, screen again, pause for review, then push. Screening fails closed and records every reason. AI features (reply drafts assembled from switchable context sections, a read-only tool-using Ask agent, and a self-learning knowledge base) are gated so nothing is sent or promoted to the drafter without a person approving it.