Sales Pipeline automates the path from an identified website visitor to a cold email campaign. A webhook server receives RB2B visits and scores intent from the pages viewed, a five-layer suppression check screens each contact, and a router classifies the lead and enrolls it in an Instantly campaign.
Three more scripts cover deal intelligence: a deal resurrector that scores closed-lost HubSpot deals and drafts revival emails, a trigger prospector that watches web signals through Brave Search, and an ICP learning analyzer that studies approve and reject decisions.
What You Get
- A webhook server that scores visitor intent by page, with scores you edit for your own URLs
- A five-layer suppression pipeline you can run on a single email address
- A router that classifies leads, picks a campaign from a JSON file and enrolls them in Instantly
- A three-layer deal resurrector with time decay, contact expansion and champion tracking, with a dry-run mode
- A trigger prospector that looks for new hires, funding and agency searches
- An ICP analyzer that recommends filter changes from approve and reject history
Common Use Cases
- Turning anonymous visitor identification into reviewed cold outreach
- Checking an address against suppression layers before any email goes out
- Reviving closed-lost deals with drafted emails in a review queue
- Finding companies showing buying signals in the last week
What Makes It Unique
It joins visitor identification, suppression, routing and deal revival in one package, and each script has a clear customization point such as intent scores, agency keywords, loss reason bonuses and search queries. Deal drafts land in a review queue and the resurrector has a dry-run flag.
Under The Hood
The scripts run as Python commands. They read HubSpot, Instantly and Brave Search keys and a Postgres connection string from environment variables, then call those services over the network. The webhook and router scripts start a local HTTP server on a port you choose, and some scripts write queue and data files. A preamble at the start runs the repository’s version check and telemetry setup scripts, which log usage locally and make remote reporting opt-in.