Portfolio project

Dead Lead Reactivation

Automated follow-ups with human handoff

  • 31 of 44Leads flagged eligible, each with a visible reason
  • 25Weekly batch cap, adjustable so volume can be raised gradually
  • 1 replyTest reply sorted as Interested and sent to Slack with full context

Portfolio project, realistic test data. See all results

Every sales team has a graveyard of leads that went quiet after a demo, a proposal or a pricing conversation. They are the cheapest pipeline a business has, because they already know the product, yet they rarely get followed up. Doing it by hand is slow and inconsistent, and doing it carelessly is worse: emailing someone who opted out, writing to the same person twice because they’re in the list twice or sending an automated reply to someone who just said “yes, let’s talk” damages trust and can break email rules.

What is needed is not a mass mailer. It is a system that decides who is safe to contact, writes something specific to each lead and gets out of the way the moment a human should take over.

Stack
Zapier (including AI by Zapier) · Google Sheets · Gmail · Slack
Scope
Solo build: data design, three-Zap architecture, AI-written outreach, reply handling and debugging across queueing, outreach and reply detection. Zapier features used: Schedule, Looping, Delay, Formatter, Filter, Paths and AI by Zapier
Context
Portfolio project for a fictional business (GrowthForge, a B2B software brand)

Dead Lead Reactivation

What I Built

Three connected automations (Zaps) sharing one Google Sheet. Every dormant lead goes through the same eligibility check, waits in the same queue and follows the same follow-up path:

Fixed rulesStep that uses AI!Alert if it fails Hands off to the next stepReads or writes shared data
Google SheetThe shared data store. Formulas decide who is safe to contact, track each lead’s status and hold the weekly limit.
Zap 1: Weekly queue and first emailEvery Monday it picks eligible leads up to the weekly limit, has the AI write a personal first message from the sheet’s facts and sends it.
Zap 2: Daily follow-upsEvery day it finds leads that are due, then sends Touch 2, sends Touch 3 or puts the lead on hold for 180 days.
Zap 3: Reply handlerWhen a reply arrives it matches it to a lead and marks the lead as replied. Then the AI sorts the reply.
InterestedA person is alerted in Slack with the lead’s details and takes over. The AI never answers.
Not nowThe lead is paused for 60 days.
UnsubscribeThe lead is opted out for good.
OtherPosted to Slack for a person to review.
Rule 1: A person takes overAn interested reply alerts a person in Slack. The AI never answers it.
Rule 2: A reply stops the sequenceReplied leads are no longer due for a follow-up, so the daily Zap skips them.
Error handlingAny step that fails posts the lead and the error to a Slack channel. The Interested alert also has a backup email, because Rule 1 depends on it.
Fig. 1 · How the three Zaps and the shared Google Sheet work together, from eligibility to reply handling.

Here’s a walkthrough of the system in action:

  1. Decides who is eligible, inside the sheet

    The sheet’s formulas mark each lead as eligible or not. Leads with no email, a badly formatted email, a duplicate email, activity in the last 90 days, an opt-out, a closed-won deal or three earlier contacts are all excluded, each with a visible reason.

  2. Sends a limited weekly batch, starting with Touch 1

    Every Monday a scheduled Zap drafts a first message from the lead’s product interest, last conversation and stated objection, sends it and logs the contact (a “touch”). The batch size is one adjustable cell in the sheet (default 25).

  3. Sends follow-ups from a daily check

    Each day it reads the latest data instead of waiting in the background, so a reply or an edit can’t leave an outdated follow-up queued. Each lead gets Touch 2, Touch 3 or a Sunset (held back for 180 days).

  4. Handles replies and hands off to a human

    Replies go to a special reply address, and a Gmail label sends each one to a third Zap that sorts it as Interested, Not now, Unsubscribe or Other. Interested replies trigger a Slack alert, and the AI never answers them.

Dead Lead Reactivation

Engineering Highlights

Select a heading to read the detail. Select it again to close it.

A person takes over the moment a lead is interested, and any reply stops further automated messages to that lead. Both rules are built into how the Zaps work, not left to instructions the AI might ignore.

Duplicates, missing emails, bad addresses and opt-outs are caught by the sheet’s formulas. I first tried Zapier Tables, found it couldn’t remove duplicates the same way and moved back to Google Sheets: I picked the tool whose limits fit the job instead of forcing the job into the tool.

Each outgoing email carries a reply address with a tag added to it, and a Gmail filter labels anything sent to that address. The known tradeoff: a reply is only matched if it comes from the exact email address stored in the sheet.

Every step that could send a wrong email or miss a hot lead reports problems to a dedicated Slack channel. The Interested-reply alert also has a backup email, because the handoff to a person is the rule the whole system depends on.

Dead Lead Reactivation

Results

This is a portfolio project on a fictional business: the results below are illustrative of how the system behaves on realistic test data, not measurements from live usage.

What each claim rests on

Each row matches a claim from What I Built or Engineering Highlights with the test behind it. Tested on a 44-lead sheet, with the other checks made while building. Rows run from the strongest evidence to the weakest.

  • Data quality checks live in the spreadsheet itself

    Of 44 leads screened, 31 were flagged eligible and 13 were excluded, each with a visible reason in the sheet.

    Tested on 44 leads
  • A human takes over when a lead is interested

    A test reply of “Yes, I’d like to talk this week” was sorted as Interested and posted to #interested-leads with the lead’s name, company, owner and deal value.

    Shown in one test
  • A capped weekly batch

    The weekly Zap ran and marked the first batch as Queued, staying within the cap set on the settings tab (default 25).

    Shown in one test
  • A reply stops further messages

    A reply stopping further messages was tested while building and worked as designed.

    Tested during the build
  • Touch 2, Touch 3 and Sunset follow-ups

    The daily follow-up Zap was tested while building and worked as designed.

    Tested during the build
  • Replies are sorted and routed

    Not now, Unsubscribe and Other replies were also tested while building and were handled as designed. The Interested reply above is the one shown in detail.

    Tested during the build
  • Planning for things to go wrong

    The Slack error alerts and the backup email for the Interested-reply alert were tested while building and worked as designed.

    Tested during the build

Limits: Only the Interested reply and the 44-lead screening are shown in detail. The checks marked “Tested during the build” are summarized from testing done while building, without numbers.

The numbers

Eligibility screening:
31/44
flagged eligible (70%), each with a visible reason
Weekly batch cap:
25
adjustable, so volume can be raised gradually
Reply sorting test:
1
test reply was correctly sorted as Interested and sent to Slack

The weekly Zap ran successfully and marked the first batch as Queued, staying within the cap on the settings tab. A test reply of “Yes, I’d like to talk this week” produced a Slack alert in #interested-leads with the lead’s name, company, owner and deal value, so a person could pick it up with full context. Every lead’s status, touch count and exclusion reason is visible in one sheet.

How this helps your business

What you get from a system like this.

  • Nothing contacted that shouldn’t be

    The sheet’s eligibility rules exclude opted-out, duplicate, badly formatted or already-closed leads before any message goes out.

  • Capped, controllable outreach

    One adjustable cell sets the weekly batch size, so volume can be raised gradually instead of blasting the whole list at once.

  • Personalized without extra work

    Each follow-up is drafted from the lead’s own product interest, last conversation and stated objection.

  • Reply triggers instant handoff

    An Interested reply posts straight to Slack with the lead’s context, and the AI never responds to it.

  • Follow-ups on a steady schedule

    Touch 2, Touch 3 or a 180-day Sunset runs from a daily Zap that always reads the latest data, so a reply can’t leave an outdated follow-up queued.

  • Full visibility

    Every lead’s status, touch count and exclusion reason lives in one sheet.

  • Fails safely

    Steps that could send a wrong email or miss a hot lead are covered by an error alert in Slack, with a backup email for the Interested-reply alert.

  • Built to respect opt-outs and limits

    Opt-outs, duplicate contacts and repeat contacts beyond the limit are blocked by how the system is built, not left to the AI’s judgment.

Let’s find what your process is letting slip.

Book a free 30-minute call. We’ll look at one process that’s costing you time, leads or money and where it breaks down today.

Book a call