The Airtable SDR Machine: How We Wired It All Together

For most of 2024, our outbound process looked like this: a spreadsheet, a VA copying leads into an email tool, and me wondering why nothing was converting. We were doing the work. We just had no visibility into what was happening between the first touch and the reply.

Then I rebuilt the whole thing inside Airtable. Not because Airtable is magic. Because it gave me a single place to see every lead, every status, every action taken, and every result, without opening five different tabs.

Here is exactly how we wired it together and what changed when we did.

Why Airtable and Not a Traditional CRM

I have used HubSpot. I have used Close. I have used a half dozen tools that promise to simplify outbound and then require a full-time admin to keep updated.

The problem with most CRMs is that they are built for closing, not for prospecting. The pipeline stages assume you already have a conversation. We needed something that tracked leads from raw list all the way through to booked call, with automation at each step and a live view of where things were breaking down.

Airtable is a database first. That means I can structure it exactly the way my process works, not the way some product manager at Salesforce imagined outbound would work in 2018.

The Table Structure

We run three core tables in our Airtable base.

Leads: Every prospect starts here. Name, company, role, industry, email, LinkedIn URL, source (where we scraped or pulled them from), and a status field that moves them through the funnel. This is the master record. Nothing gets added to the outreach sequence until it clears through here.

Sequences: Each lead gets linked to a sequence. The sequence table tracks which touchpoints have gone out, which are pending, and the send dates. We run a 5-touch sequence on average: day 1, day 3, day 7, day 14, day 21. Airtable automations trigger a flag when a touchpoint is due.

Replies and Outcomes: When someone responds, it gets logged here. Positive, negative, not now, bounce, unsubscribe. This is where we pull our data from when we are reviewing what is working. The reply rate by sequence, by industry, by hook, by touch number.

The Automation Layer

Airtable automations handle the connective tissue. When a lead status changes to “approved for outreach,” an automation fires and creates the sequence record automatically. When a touchpoint date hits, a Slack alert goes to whoever is managing sends that day.

We connect Airtable to Instantly via Zapier. Instantly handles the actual sending. Airtable handles the logic, the tracking, and the decision layer. Instantly is just the delivery mechanism. Keeping those jobs separate was one of the better decisions we made.

The other piece that changed everything: a lookup field that pulls the last reply date and last touch date back onto the lead record. That means I can open the master leads view and immediately see which leads have gone cold, which are mid-sequence, and which are waiting on a follow-up. No clicking into individual records. No guessing.

What Lobito Feeds Into It

Lobito, the bot in my Wolf Pack responsible for daily lead scraping, drops new attorney leads directly into Airtable via the API. Every morning, fresh leads appear in the intake queue. A status field defaults to “pending review.” My team or I do a quick filter pass, approve the clean ones, reject the duplicates, and the sequence automation fires from there.

Before this setup, leads were sitting in a spreadsheet for three to five days before anyone touched them. Now the average time from lead scraped to first touch is under 24 hours. That alone changed our contact rate.

The eNZeTi Parallel

Building this system taught me something that applies directly to what I do at eNZeTi: the bottleneck is almost never the person. It is the gap between what the person needs to do and the information they have available to do it.

Our outbound process was not broken because the people running it were bad at their jobs. It was broken because they had no real-time visibility into what was happening. Once I gave them a single clean view of the data, a clear status system, and automation that handled the repetitive triggers, the whole thing clicked.

The same logic applies to a law firm intake coordinator. They are not losing cases because they are bad at their job. They are losing cases because they have no support in the moment the conversation gets hard. No data. No prompts. No coaching. That is the gap eNZeTi closes.

The Three Views I Live In

Airtable lets you create unlimited filtered views of the same base. Here are the three I open every day:

Pending Review: All leads that have not been approved or rejected yet. This is my morning triage. Usually takes ten minutes.

Due Today: Every touchpoint that needs to go out today, sorted by lead quality score. We prioritize the higher-fit leads on every touch cycle.

Replies This Week: Every lead that has responded, sorted by date. This is where we catch positive replies that need a human hand-off. Automation can push leads to sequence. It cannot replace the conversation when someone actually responds.

What Changed After 30 Days

Our reply rate improved. Our follow-through on sequences went from spotty to consistent. But the real change was visibility. I knew for the first time exactly where every lead was, how many touches had gone out, and what percentage of leads were converting at each stage.

When you can see the machine, you can fix the machine. When you are working from a spreadsheet with no status tracking, you are just hoping.

We found that our reply rate dropped sharply after touch three for most sequences. Before Airtable, we never knew that. We assumed people just were not interested. After we saw the data, we rewrote touch four with a different angle and our response rate on late-sequence leads doubled.

That is what a real system does. It does not just organize your work. It tells you what is actually happening so you can make a decision.

The Stack, Plainly

Here is everything wired together, no fluff:

• Airtable: master database, lead tracking, sequence logic, outcome logging
• Lobito (custom bot): daily lead scraping, API push to Airtable
• Zapier: trigger bridge between Airtable and Instantly
• Instantly: email sending, deliverability, inbox rotation
• Slack: daily alerts when touchpoints are due or replies come in

That is it. Five tools. Everything else is inside Airtable itself through formulas and automations.

The Lesson I Keep Coming Back To

The goal of building this machine was never to remove humans from the process. We still review every lead. A human still handles every positive reply. The system handles the parts that do not require judgment so that the parts that do require judgment actually get attention.

That is how I think about automation in general. You are not replacing the person. You are clearing the noise so the person can do the work that actually matters. That is the same belief I built eNZeTi on, and it is the same belief behind every system I build for my own business.

If you are running outbound from a spreadsheet right now, the problem is not your offer and it is not your copy. The problem is you cannot see what is happening. Build the machine first. Then optimize it.