
The GTM Launchpad is where we open the hood on B2B revenue - fixing structure, sharpening outbound and building pipeline that actually holds up
Running three lanes was the easy part
This week I had three outbound motions running around The SD Lab: Smartlead handling email, Lemlist working through a smaller signal-led multichannel pilot, and me still making calls through Nooks and sending the one-to-one stuff that actually needs a human brain attached to it.
You know what's funny? Running three systems is actually the easy part. Making sure they don't all decide they have a perfectly good reason to talk to the same person at the same time? That's where shit gets interesting.
Each lane can look completely reasonable inside its own little world. Smartlead can say a contact is eligible, Lemlist can surface a signal, I can have history with the person, and Nooks can hand me a call task. None of that answers the question that matters most: who owns the buyer relationship right now?
That's the problem I'm working through now: ownership. Three outbound lanes only become one revenue motion when everybody knows who gets the next move.
Where the ownership got fuzzy
Smartlead gave me the first clue. We had contacts sitting in an active HubSpot feed that looked ready to work, but some of them had already been enrolled elsewhere. We also had fresh contacts that were approved for the feed but weren't campaign recipients yet.
The point isn't memorizing our internal list states. It's that eligible, approved, enrolled and owned are not the same thing, and one tool can clear somebody for its next step without knowing another lane already has a reason to leave that person alone.
Lemlist had a different job: signal-led, multichannel outreach across email, phone and LinkedIn. The manual lane had another job entirely: high-context conversations, relationship history and moments where personal judgment matters more than automation. We even had a real commercial conversation this week that moved firmly into human-owned territory. That relationship doesn't need a cold campaign wandering back into it because another system still sees an open slot.
That's when it clicked for me: a reason to contact someone is not the same as permission for every lane to contact them.
The collision nobody puts on the dashboard
Picture one sales leader at a company you really want to work with. Smartlead says they're eligible, Lemlist sees a hiring signal, a rep remembers a previous conversation, and Nooks has a task waiting. Every one of those actions can make sense by itself.
Three channels
One relationship owner
One authorized next move
That's how I'm thinking about it now. The tools can surface opportunities, prepare work and recommend actions, but they don't each get an independent vote on the buyer. One lane owns the relationship at a time, and the other lanes have to respect that.
And if we can't answer who owns the next move? HOLD is a perfectly good decision. I'd rather pause for ten minutes than make the buyer feel like three different people from our company have never met each other.
Three lanes, one relationship owner
Smartlead owns the next email action when a prospect is current, eligible and actively assigned to that campaign. That's its job in our setup. It doesn't get to assume campaign eligibility means nobody else owns the person.
Lemlist owns the next multichannel action when an account is actively assigned to the signal-led motion. Email, phone and LinkedIn can work together there, but only while that lane actually owns the next move.
Manual outreach owns the next move when there's relationship history, a live conversation or a reason for personal judgment. Once a buyer becomes human-owned, the automated motions need to get out of the way.
When an account transfers lanes, the ownership has to transfer with it. The context, suppression and next action can't stay stranded in the old system while the buyer moves somewhere else. These are three different jobs, not three separate permission slips to hit the same person.
The handoff is where the system becomes real
The second somebody replies, a rep gets into a real conversation, or a commercial decision starts moving, that account stops being just campaign inventory. A person owns it now.
That's the handoff I'm tightening. If Smartlead keeps sending because it never heard about the conversation, or Lemlist keeps advancing because its workflow doesn't know the account moved, we didn't build one outbound motion. We built a few tools pointing at the same market and hoping they stay out of each other's way.
The buyer doesn't care which platform fired the touch. They only feel whether your company remembers them.
Where automation needs to back off
I still want AI and automation doing a ton of prep: research the account, surface history, find signals, draft the first pass, flag contradictions. Hell yes. That's useful.
What I don't want is the machine reopening a relationship because a workflow reached its next step. Once a buyer is human-owned, that needs to beat whatever automation was queued up before it. The automation should support the owner, not compete with them.
The Monday morning test
If you've got multiple outbound tools or teams touching the same market, pick one account that exists in more than one place. Don't open the activity dashboard yet. Just trace the relationship: who owns this buyer today, which lane is authorized to make the next move, and if ownership changed, did the other motions actually get the memo?
Then pick one account where nobody can answer those questions cleanly. That's probably where your next collision is hiding.
We're still learning from our own three-lane build, and I'm not pretending Smartlead, Lemlist or the manual lane suddenly cracked outbound this week. What we got was more useful right now: a clearer way to decide who owns the buyer and what happens next. It's not exactly a sexy growth hack, and that's fine. I'd rather build one outbound experience that feels thoughtful and coherent to the buyer than three machines that all look busy in their own dashboards.
Sponsored by Smartlead
Build the System Before You Scale the Sends
Look, this is actually why I'm excited about next Thursday. We've been heads-down rebuilding and running our Smartlead email lane: segmenting sales dev and sales leader audiences, working through eligible prospect inventory, reconciling suppression, tightening messaging and watching what happens once campaigns are actually live. Smartlead is one lane in the bigger outbound system and we're learning which parts hold up and which parts get messy.
This Thursday I'm getting together with the Smartlead crew for Office Hours to go deeper on the actual system behind the sends. If you're a founder, sales leader or running sales dev and you're trying to make outbound work without turning the buyer experience into chaos, come hang out. Bring questions. We'll talk targeting, segmentation, messaging, deliverability, channel orchestration, where AI actually helps and what we're learning from real campaign execution.

Thursday, November 19 · 10 AM Eastern/8 AM Arizona/7 AM Pacific
approximately 60 minutes + live Q&A
Sponsored by Smartlead, a paid SD Lab partner.
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 structure underneath pipeline so the team can actually run it
Know a founder, sales leader or operator who’d get value from this field note?

