This website uses cookies

Read our Privacy policy and Terms of use for more information.

The GTM Launchpad is where we open the hood on B2B revenue - fixing structure, sharpening outbound and building pipeline that actually holds up

Wednesday afternoon, I got the kind of update you want after spending months rebuilding an outbound motion.

An experienced rep on a client team I’ve been working with had reached the meeting goal we’d been working toward. Outbound was contributing again, the rep was producing consistently and the motion looked very different from where we started.

When we talked through what felt different, it wasn’t some magical new cold-call opener or one piece of messaging that suddenly changed everything. There was a system behind the work now. Less chaos, clearer places to look and a better understanding of what was supposed to happen next.

I remember sitting there thinking, hell yeah. This is working!

For a few hours, I was ready to call that the proof.

By Friday, that felt incomplete

because the most interesting thing that happened this week wasn’t the result itself.

It was who started solving the problems around it.

The manager was the signal

Earlier in the week, we were reviewing calls with the person who is beginning to own the first-line management layer internally.

Something in the activity data didn’t make sense. The dashboard showed connects, and if you stopped there, the obvious diagnosis would’ve been some version of: the reps need to convert better.

Maybe the opener needs work, maybe discovery is weak, maybe they aren’t controlling the conversation well enough but before we coached any of that we had to make sure the denominator was even real.

Once we looked underneath it, some of those nominal connects weren’t meaningful buyer conversations at all.

There were gatekeepers, routing and phone-system interactions, wrong people and calls where the rep never had enough conversational surface area to do anything useful.

That’s not a small distinction. You can’t coach discovery on a conversation that never happened and you probably shouldn’t dump a bunch of rep feedback on top of a measurement problem just because the dashboard put both events in the same bucket.

Bad data can wear a coaching costume

We talked about this last week from the verification side. What caught my attention this time was different.

I wasn’t the first person making the distinction anymore.

The internal manager was looking at the evidence, separating an operating problem from a coaching problem and beginning to coach from what had actually happened.

That was the moment I kept thinking about after the session.

The handoff shows up in boring little decisions

The same thing kept happening in smaller moments.

A rep raised an edge-case prospecting question. A month ago, it would’ve been easy for that to turn into another working session with me. We could open the system, build another view, debate segmentation and somehow turn one weird record into 45 minutes of infrastructure work.

Instead, the internal manager simplified the decision, pointed the rep toward the cleanest existing path and kept the team moving.

Later, we talked about potentially getting everyone together for a longer live prospecting block. His first concern was whether we were about to eat into too much actual selling time.

Good! That’s what I want the manager worried about.

There’s a point where protecting production matters more than adding another training session. A manager has to know what deserves escalation, what deserves coaching and what simply needs a quick decision so everybody can get back to work.

None of those moments are especially sexy but that’s kind of why they mattered.

The role was starting to show up in the decisions, not the title.

At some point, more help becomes interference

This was the part that changed my thinking by the end of the week.

When you spend months helping rebuild an outbound motion, there is always another thing you could improve.

Another workflow, another call to review, another sequence to tweak, another play to build even another session you could put on the calendar.

For a while, that work is necessary.

Then eventually the only useful test left is letting the thing run.

That was basically the leadership conversation this week. We weren’t sitting there asking what giant piece of the outbound machine was still missing.

The machine was there

Now we needed to find out whether the people inside the company could operate it.

So Friday morning I intentionally kept the team session short. I didn’t want another workshop and I definitely didn’t want to rebuild myself into the answer path again.

If something materially stops the team from prospecting, surface it. If it doesn’t, keep selling.

Let the reps generate evidence
Let the manager inspect it
Let leadership manage through that manager

and let me get further away from the normal workflow.

That’s where the definition of “working” changed for me.

One experienced rep producing proved that the motion could create an outcome.

It didn’t prove that the organization owned the motion yet.

I’m testing another version of this inside The SD Lab right now.

This week I got back into Smartlead and started rebuilding my own scaled cold email motion after spending much less time around it this year.

I used the platform pretty heavily last year across my own outbound and outsourced lead-gen work. Then I pulled back while seemingly every founder and sales leader started asking some version of the same question: is cold email dead?

I don’t think one-to-one email is the interesting test. We already know a thoughtful email to the right person can work.

Scale is where things get messy.

So I grabbed two fresh sending domains and six mailboxes, and I’m using The SD Lab as the experiment through Q4. The goal isn’t to find out how much infrastructure I can turn on. I want to see what happens when the account universe is tighter, the reason for reaching out is better and the infrastructure is healthy before I add volume.

Basically, I want the underlying idea to earn scale.

Smartlead has changed quite a bit since I was using it heavily too, so I’ll share what I find as the motion starts producing real evidence again.

If you’re already thinking about your 2027 outbound stack, you can check out Smartlead here

The proof changed

By Friday, I realized I had been looking at two different tests.

The first was whether somebody could win inside the rebuilt motion.

That matters. Without production, none of this is worth much.

But the second test is harder.

Can another operator step into the same motion and know what work to do?

Can the manager look at a weird number and figure out whether they’re dealing with bad data, bad process or bad execution before they start coaching?

Can leadership stay above the team instead of bypassing the manager every time something gets uncomfortable?

and if the person who built the system disappears for a week, does the thing keep moving?

That is what I mean by transfer.

I think a lot of outbound rebuilds get declared finished somewhere between those two stages.

The strongest rep starts producing. The dashboard looks better. Everybody breathes a little easier.

Meanwhile every strange decision still finds its way back to the founder, VP or consultant who designed the thing.

That doesn’t mean the rebuild failed.

It just means the result and the transfer are two different milestones.

I almost judged the week on the first one.

Now I’m watching the second.

THE MONDAY INSPECTION

If you’re looking at your own outbound org this morning, there are a few places I’d look under the hood.

Where does production still depend on one person simply knowing what to do?

When a dashboard number looks wrong, who figures out what actually happened before somebody starts coaching the rep?

When the team hits friction, who decides whether the system needs to change or everybody just needs to keep selling?

and if the person who designed your current motion disappeared for a week what would break first?

I don’t think the goal is to have perfect answers to all of those. We don’t yet either.

That’s why this next phase is interesting.

A handoff isn’t one meeting where everyone agrees the playbook is finished. You see it happening when fewer normal decisions have to travel back to the person who built the thing.

One rep winning showed us the motion could work.

The next operators and the internal manager are what will tell us whether the org can actually own it.

That’s the test now

Have a great Monday 🤙

Thanks for reading. See you again next week at 8 am MST!

- Tom Slocum ✌️

If your outbound motion feels busy but fragile, that’s the work I do inside The SD Lab.

I help B2B founders and sales leaders build the targeting, messaging, process, coaching and inspection underneath qualified pipeline so the team can actually run it.

Know a founder, sales leader or operator who’d get value from this field note?

FORWARD TO A FRIEND 👉 Click Here

Reply

Avatar

or to participate