Articles

How to Build an Automated Prospecting Pipeline (From Scratch)

Ibby SyedIbby Syed, Founder, Cotera
7 min readFebruary 18, 2026

How to Build an Automated Prospecting Pipeline From Scratch

Building an Automated Prospecting Pipeline

Last March, I inherited a pipeline that ran on vibes. Our "system" was an SDR named Jake who kept a spreadsheet of companies he thought looked promising, emailed whoever showed up first on LinkedIn, and logged maybe a third of his activity to HubSpot. Jake was good at his job — genuinely talented at reading people. But when he took two weeks off for his wedding, the pipeline went completely dark. Nobody knew which accounts he'd been working. Nobody could find his spreadsheet. Turns out it was a local file on his desktop named "leads_final_v3_REAL.xlsx".

That experience broke something in my brain. I spent the next six weeks building an automated prospecting pipeline that didn't depend on any single person's memory, desktop files, or willingness to update a CRM. Not a tool purchase — an actual system with architecture, data flow, scoring logic, and maintenance schedules.

Here's how I'd build it again from zero.

The Architecture: Four Stages, Four Handoffs

Most people think about prospecting automation as "buy a tool, turn it on." That's like thinking about software architecture as "buy a server, deploy code." The tool is the least interesting part. The architecture is everything.

Your automated prospecting pipeline needs four distinct stages, and each stage has one job:

  • Source — Where raw company and contact data enters the system. Apollo, LinkedIn Sales Nav, Crunchbase, whatever your data providers are. The key constraint: define your ICP filters tightly enough that this stage produces hundreds of records, not tens of thousands.
  • Enrich — Where raw records become useful. Company news, hiring activity, tech stack, social posts, funding rounds. This is what separates a prospect list from a phone book. I cannot overstate how many teams skip this step and then wonder why their outreach sounds generic.
  • Score — Where you rank who to talk to first. Not a binary qualified/unqualified gate. A weighted score that accounts for fit, timing signals, and engagement.
  • Route — Where scored leads land in the right rep's queue inside your CRM, deduplicated, tagged, and ready to work.

Each handoff between stages should be automated. If a human has to copy data from stage one to stage two, you don't have a pipeline. You have a to-do list with extra steps.

Data Flow: Getting the Plumbing Right

The mistake I made on my first attempt was treating each stage as a separate project. I set up Apollo searches, then separately configured enrichment, then built scoring in a spreadsheet, then manually imported to HubSpot. Four disconnected processes pretending to be a pipeline.

What actually works: chain them. One trigger pulls a batch of ICP-matched companies from your source, immediately passes them through enrichment, runs the scoring model, and pushes qualified leads into your CRM. One flow. No human in the loop until a rep picks up a scored lead and decides what to say.

The Apollo to HubSpot Pipeline Builder is what we use for the source-to-CRM chain now. It searches Apollo for companies matching your ICP, enriches the contacts, checks for duplicates already in HubSpot, and creates the records. The whole source-enrich-route chain in one pass. Before this, the handoff between Apollo and HubSpot was where leads went to sit in purgatory for days.

For the enrichment layer specifically, lead enrichment fills in the gaps that your source data always has — company financials, social profiles, tech stack, buying signals that your reps actually need for personalization. Without this data, your pipeline produces contacts. With it, your pipeline produces context.

Building a Scoring Model That Isn't Just Guessing

Here's where most teams get sloppy. They'll build a gorgeous automated pipeline and then score leads by gut feel. Or worse — they'll use a single dimension like company size as a proxy for "good lead."

Your scoring model needs three categories of signals, weighted differently:

Fit signals (40% of score): Does this company match your ICP on the dimensions that actually predict closed deals? Not the ones that feel important — the ones you've validated against your last 20 wins. For us, that's employee count (100-2,000), industry (B2B SaaS or fintech), and whether they use Salesforce or HubSpot. We figured this out by looking at what our best customers had in common, not by guessing.

Timing signals (35% of score): Is something happening at this company right now that makes them more likely to buy? New VP of Sales hired in the last 90 days. Series B announced. Job postings for roles your product replaces. A timing signal converts a "someday" lead into a "this quarter" lead.

Engagement signals (25% of score): Have they interacted with you at all? Website visits, content downloads, webinar attendance, replied to a previous email. This category starts at zero for cold prospects and accumulates over time.

The HubSpot Lead Scoring Report generates scoring analysis from your existing HubSpot data, which is where I'd start. Run it against your closed-won deals from the last two quarters. See which signals actually correlated with revenue. I was shocked to find that company headcount growth rate predicted close rate better than absolute company size for our product. I would never have guessed that without looking at the data.

Prospecting Pipeline Data Flow

Maintenance: The Part Everyone Forgets

Building the pipeline took me six weeks. Keeping it accurate is an ongoing job that never ends. Here's what breaks if you ignore it.

Data decay will eat your pipeline alive. B2B contact data goes stale at roughly 2-3% per month. After six months of neglect, one in five records is wrong. People leave companies. Companies rebrand. Email domains change. I schedule a monthly re-enrichment pass on any contact that hasn't been touched in 90 days. Sounds excessive until you see your bounce rates after skipping it twice.

Your ICP drifts. The companies that were perfect prospects a year ago might not be today. Markets shift. Your product changes. Your pricing moves upmarket or downmarket. Quarterly, I pull our last 10 closed-won deals and compare them to the ICP filters feeding the pipeline. If there's a mismatch, the filters need updating. Last quarter I discovered we'd been filtering for companies with 50+ employees but our last eight wins were all 200+. The pipeline was surfacing leads we'd stopped closing.

Scoring weights go stale. That timing signal that was gold six months ago — "just raised a Series B" — might stop predicting wins if the market changes. Recalibrate your scoring model quarterly against actual outcomes. It takes an afternoon. Skipping it means your reps spend weeks chasing leads the model says are hot but reality says are lukewarm.

Why Use an Agent for This

I built our first version of this pipeline with Zapier, three API connections, and a Google Sheet that served as a makeshift scoring engine. It worked, technically. It also broke every time Apollo updated their API, took four hours to debug when something went wrong, and couldn't handle edge cases like "this person is already in HubSpot but at a different company now."

An agent collapses all four stages — source, enrich, score, route — into a single intelligent flow. It doesn't just move data between tools. It makes judgment calls at each handoff. Should this contact replace the stale record or create a new one? Is this hiring signal relevant to our product or unrelated? Does this lead score high enough to warrant immediate routing or should it sit in nurture?

The difference between a Zapier chain and an agent is the difference between a conveyor belt and a colleague. The conveyor belt moves things forward. The colleague thinks about whether they should.

The Short Version

An automated prospecting pipeline is four stages: source, enrich, score, route. Build them as one connected flow, not four separate tools. Weight your scoring model against real closed-won data, not assumptions. Maintain the whole thing monthly or watch your data rot. The teams that treat their pipeline like infrastructure — monitoring it, updating it, stress-testing it — are the ones where reps actually trust the leads in their queue.

Jake still works here, by the way. He still has great instincts. He just doesn't keep them in a spreadsheet on his desktop anymore.


Try These Agents

For people who think busywork is boring

Build your first agent in minutes with no complex engineering, just typing out instructions.