One person, three tools, a team's worth of outbound

An agency we reviewed runs almost all of its outbound on three tools and one part-time person. No SDR team, no ten-tool stack, and the pipeline does not depend on anyone remembering to do the boring parts.

This post takes that stack apart far enough that you could hand it to someone on your team and have them build the same thing: what each tool does, the exact columns in the working table, what the person's 45 minutes a day look like, what it costs, and where it breaks. The names and numbers are rounded to protect the agency, but the setup is real.

What does the three-tool outbound stack look like?#

The stack has two layers. Tools carry the repeatable work, and one person carries the judgment.

That split is the whole idea. Every piece of work that repeats the same way every time went to a tool. Every piece of work that needs a human reading the situation stayed with the human.

What is a buying signal, in plain words?#

A buying signal is a public event that says a company might need you right now. You do not guess who to contact. You wait for the moment.

The signals this agency watches, with what each one means:

The signal tool watches for these events across thousands of companies and drops the matches into a list. That is its entire job.

What does the outbound Clay table look like?#

Everything meets in one Clay table. One row per person, and the columns are the process:

If a row is missing a verified email or a real fact, it does not move forward. Those two columns are the quality gate.

What does the daily 45-minute outbound routine look like?#

About 45 minutes, in the same order every day:

1. Open the table and read the new signal rows from overnight. Drop the ones that are not a real fit. This is the most important 10 minutes of the day.
2. For every row that survived, read the one research fact and write the first line by hand. One or two sentences, no template.
3. Send. The rest of the message after the first line IS a template, and that is fine - the first line carries the reply rate.
4. Read every reply. Book the interested ones, answer the questions, mark the rest.

Notice what is missing: no list building, no email hunting, no copying between tools. The machine did all of that before the person sat down.

What makes a first line work?#

The pattern is simple: name the signal, connect it to the problem you solve. Two invented examples of the shape:

• "Saw you are hiring a second ops manager - usually that means the reporting load has outgrown the team."
• "Congrats on the new funding. The next 12 months of scaling usually breaks whatever CRM process exists today."

The reader can tell in one sentence that a human looked at their company. That is the entire trick, and it is why this line stays human while everything around it is automated.

How do the pieces actually plug together?#

The connections, in order, so you can hand this to whoever sets up your tools:

1. The signal tool watches its sources and pushes every match into the Clay table automatically - a webhook or native integration, set up once. New signals appear as new rows overnight.
2. Inside Clay, columns run left to right on each new row: pull the right person from Sales Navigator, find the work email, verify it. The verification column is a gate - rows that fail never reach the writing stage.
3. Another column fetches the one research fact: the hiring post, the funding note, the platform change, written into the row next to the verified email.
4. The person works inside that one table. They read, drop the bad fits, and type the first line into the first-line column.
5. Approved rows sync to the sending tool, which merges the hand-written first line with the template body and sends on a schedule. Replies land in one inbox the person reads every day.

When we build this for clients, the same wiring gets one addition: an approval step before anything sends, so a human click - not a sync - is what puts a message in front of a prospect.

What does this cost compared to hiring an SDR?#

The bigger saving is quieter. Nothing in this stack walks out the door with an employee, because the process lives in the tools, the table, and one written playbook - skills that live in one head are a risk you can remove.

Where does a three-tool outbound stack break?#

It breaks at volume and at neglect. One part-time person can hold judgment over a few hundred contacts a month; past that, replies start waiting too long and quality slips.

It also breaks if nobody checks the data underneath. A signal tool reading stale company data sends you after the wrong accounts, which is why the label check we describe in automation's real job applies here too.

How do you copy this outbound stack?#

One step a day, one working week:

1. Monday: List every tool your outbound touches today and the single job each one does. Where two tools share a job, plan to cut one.
2. Tuesday: Pick the two or three signals from the table above that fit your buyer, and set up a signal tool to watch for them.
3. Wednesday: Build the table with the six columns above. Do not add more columns yet.
4. Thursday: Write the playbook page: what counts as a fit, the first-line pattern, and the daily 45-minute order of work.
5. Friday: Run the first batch of ten by hand, end to end. What annoyed you is what you tune next week.

If the workflow you want to hand over is not outbound, the same split works anywhere: tools on the repeatable layer, a person on judgment. The four ways to buy that setup compares your options, and the systems we build follow the same rule.