What is a pipeline? Search, signals and your browser in one place

A pipeline is your whole lead-gen journey on one canvas: sources on the left, emails at the end. Here is what each part does, and why one canvas beats five tools.

Watch: A pipeline assembling

A pipeline is your whole lead generation journey drawn on one canvas. Sources on the left: your searches, the signal watch, even your browser. Steps in the middle: verify, dedupe, wait, branch. Emails at the end, sent from your own mailbox. One picture, one switch, one place to look. This post explains each part in plain terms.

The sources: where leads come from

A pipeline can drink from four taps, together or separately:

• A search. The UK Companies House register, filtered by SIC code, area, age, and extras like the poor-website filter. One bulk search covers everything that matches today.
• The signal watch. The always-on part. It checks the register every day and delivers new matches as they appear: a fresh incorporation, an approaching filing deadline, a site graded poor. This is what keeps a pipeline full without you re-running anything. See buying signals.
• Your browser. The Chrome extension identifies any UK company as you browse. One click saves it into the pipeline, same as a searched lead.
• A webhook. Other tools can POST leads in: a form, a Zap, your own backend.

Whatever the tap, every lead is the same shape: the Companies House record, the director's name, a verified website and a verified email. 1 credit = 1 lead. A company we cannot verify never arrives and never charges.

The middle: the steps that protect you

Between source and send, the pipeline does the careful work:

• Enrich fills the record from our verified cache.
• Verify checks the address accepts mail, so bounces never reach your mailbox.
• Skip already-contacted dedupes against everyone you have ever emailed.
• Wait and branch steps shape the journey: a reply goes one way, silence goes another, and AI triage sorts interested from not interested.
• Webhooks go out and come back, so your CRM or Zapier can join in mid-journey (the round-trip).

The end: emails from your own mailbox

Every pipeline ends in emails, because that is the point. Your intro, a wait, one chaser. Sent from your own Google or Microsoft mailbox, inside its warm-up allowance, in UK business hours, with a one-click unsubscribe on every message. A reply stops that lead's journey instantly and lands with you.

Who draws the picture

Two doors. Let the AI build it: a two-minute chat with your AI lead-gen employee, which reads your website, asks two or three easy questions, and drafts the whole canvas, including the emails. Or build it by hand, block by block. Both doors end in drafts. Drafts only: nothing sends until you say so.

Why one canvas beats five tools

The old way spread this journey across a data provider, a spreadsheet, a verifier, a sending tool and Zapier. Every seam lost data and hid failures. On one canvas:

• The record you found is the record you send to. Nothing goes stale in a CSV.
• One suppression list guards every send. A removal request sticks everywhere.
• One warm-up allowance guards your mailbox, however many pipelines you run.
• When something needs a human, it parks in Needs attention and tells you. No silent stops.

The full argument, including where Zapier still earns its keep, is in Zapier vs built-in automation.

See one running

The fastest way to understand a pipeline is to watch one being built. Start free with 25 leads, take the AI door, and you will have a drafted pipeline in front of you in about two minutes. Read the drafts, change what you like, flip the switch.