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

Thursday afternoon I was looking through an SDR’s activity with one of my clients when something didn’t make sense.

About a month ago, we moved the rep from manually dialing inside Gong into Nooks. Before that change, some days might produce 10 or 15 calls and a 500 call week felt productive. Thirty days later he’d generated 1,411 dials, 109 connects, 37 conversations and three meetings. His connect rate had climbed to nearly 8% and we were starting to have much better conversations about where the next constraint might be.

Then I looked at this week

Nothing

At least that’s what the data appeared to show

I couldn’t see any dialing activity from the rep. My client checked internally and couldn’t see anything either. There were plenty of stories we could’ve created from that information. Maybe he stopped working, maybe something happened, maybe adoption slipped or after a strong month he simply took his foot off the gas.

The problem was we didn’t actually know any of that

All we knew was what the dashboard showed us. So instead of turning incomplete information into a conclusion, I surfaced what I found, my client checked his side and we agreed to figure out what was actually happening.

Data first. Story second

I wrote those four words down afterward because I realized how often this exact pattern had shown up throughout my week. Not just inside sales teams but inside businesses, conversations with friends and my own head.

Something happens and we don’t have all the information yet so our brain fills in the missing pieces and before long we’re making decisions based on a story we created instead of the reality sitting in front of us.

I think revenue teams do this constantly

I’m starting to wonder how many problems we create simply because we explain things too early

Pipeline drops and someone says the reps aren’t prospecting hard enough. Connect rates fall and someone decides cold calling doesn’t work anymore. Meetings decline and marketing thinks the messaging is stale. A deal slips and the rep says procurement is holding everything up.

Those explanations might be completely accurate but there’s an important difference between saying “Pipeline declined 18%” and “Pipeline declined 18% because the reps aren’t prospecting enough.”

The first is an observation

The second is a hypothesis

Inside a lot of organizations, those two things become interchangeable almost immediately. Once that happens everything downstream starts changing. Managers coach differently, campaigns get rewritten, tools get purchased, reps get pressured and strategies get abandoned.

Sometimes entire GTM motions get rebuilt around an explanation nobody actually validated.

I’ve done this too.

For years, one of the questions hanging around outbound has been whether certain motions, markets or organizations are simply harder to penetrate through cold outreach. One of my clients had some of those questions when we started working together. Could outbound really work here? Would people answer? Could an SDR consistently create conversations? Would investing more deeply into the motion actually produce anything?

We didn’t need another opinion about it.

We needed enough activity to find out.

Now we’re beginning to have that evidence. The same rep who was manually dialing and connecting around 4% is now connecting around 8%. We’re generating conversations, meetings are happening and we’re looking at hiring another SDR while discussing what the outbound organization could look like over the next twelve months.

During my conversation with them this week we started talking about some of the assumptions that existed before we began.

A lot of them simply haven’t survived contact with the data.

We busted the myths.

Not because I had a better argument but because we ran the experiment.

I had another conversation Friday that brought the whole thing together.

A friend called me because he’s thinking deeply about where business, sales and marketing are heading as AI becomes more prevalent. His thesis is interesting. Maybe the pendulum starts swinging harder toward human connection. More face-to-face interaction, more community, more in-person events and more experiences that become increasingly valuable precisely because everything else is becoming easier to automate.

I think there’s something there so we started whiteboarding what doubling down on that could look like.

Then I stopped.

I realized we were about to do the exact thing we’d been talking about.

We had a theory. It was a pretty compelling theory, actually, but it was still a theory.

I reminded him of something he’d said to me over lunch recently: Why does everything have to be zero or one hundred?

Believing human connection will become more valuable doesn’t mean you need to completely change the strategy tomorrow. Run something. Create an asset, host a small event or test a new format. Put a version of the idea in front of the market and watch what happens.

If people respond, do more. If they don’t, figure out why. Maybe the thesis is right, maybe it’s partially right, maybe the market takes it somewhere neither of us expected.

Either way, now you’re learning from reality instead of endlessly debating what reality might become.

That conversation stuck with me because I think operators sometimes confuse conviction with certainty.

You need conviction to try something.

You don’t need certainty to start.

You definitely don’t need to bet the entire company before you’ve collected enough evidence to know whether the idea deserves a bigger bet.

I saw another version of this during a conversation with an early-stage founder this week.

He’s building a product and thinking through how to create his first outbound motion. Like most founders at that stage, there are a hundred things he could build before going to market

infrastructure, processes, automations, tools, sequences and reporting etc

You can spend months creating an incredibly sophisticated machine before discovering whether anybody actually wants what the machine produces.

Our conversation kept coming back to something much simpler.

Build enough infrastructure to start learning.

Get some data. Start prospecting. Get people into trials and talk to them. Find out why they signed up, where they get stuck, what they expected, what they’re willing to pay for and what they actually need.

Then build from there.

By the end of the conversation, he essentially articulated the point himself. Spending all day building things nobody has asked for isn’t nearly as useful as getting trials, feedback and paying customers.

That’s the operating system.

Planning absolutely matters but eventually the market needs a vote.

I think a lot of organizations delay that vote because thinking feels safer than testing.

You can argue about a theory forever.

Reality tends to answer faster.

Unfortunately, I got a much more personal version of this lesson on Wednesday.

I received an automated email from our property management company about our rent balance. The language was aggressive. There was a deadline that afternoon and a warning about “further action” if the balance wasn’t handled.

My anxiety immediately grabbed the missing information and started writing the rest of the story.

What does further action mean? Are they starting something? Should I immediately send part of the money? Do I move money from somewhere else? Am I about to screw this up again?

For a few minutes my brain had built an entire future from one email.

Then I caught myself.

I’d already been communicating with the property manager so I followed up and waited. Eventually she responded. They had noted the account and knew when I expected to make the payment. There were still things I needed to handle but the situation wasn’t the catastrophe my brain had created from the incomplete information.

Nothing about the original email had changed.

My information had

That distinction mattered because the first story would’ve caused me to scramble. The additional data allowed me to operate.

Sitting there afterward I couldn’t ignore how similar that was to what I’d just watched happen inside the businesses around me. Human beings hate information gaps so we fill them. Sales leaders do it with dashboards, Founders do it with markets, reps do it with buyers and apparently I do it with automated property management emails.

The danger isn’t creating a hypothesis.

We need hypotheses to operate.

The danger is forgetting that it’s a hypothesis.

What’s interesting is that last week’s issue was about the gap between demand and revenue.

This week some of the money finally moved. $4,310 landed across different parts of the business, A client officially extended our work through August for another $7,500, a Cheer company became a client and other opportunities stayed alive too.

The Authentication client relationship was probably the part I appreciated most.

A few months ago, I came in to run an SDR Summit. Now leadership and I are talking about the twelve-month outbound roadmap, future org design, hiring progression, KPIs, tooling, coaching, Denver planning and what the SDR organization needs to become next.

That’s teaching me something about my own business too.

I’ve had theories about what The SD Lab should become.

A consulting company.
A training business.
Lead generation.
Revenue Rebuild.

Maybe some combination of all of them.

Instead of forcing an identity onto it I’m trying to pay closer attention to what the work keeps telling me.

The places where I seem to create the most value aren’t when I drop in, deliver six workshops and disappear. It’s when I get inside the operation, work alongside leadership, coach the reps, look at the data, help hire, pressure-test strategy, fix the process and stay close enough to see whether the systems we build actually work.

Maybe embedded partnerships become a much bigger part of The SD Lab.

I don’t know yet.

That’s kind of the point.

I don’t need to turn an emerging pattern into a permanent conclusion before I have enough evidence.

I can keep running the experiment.

There’s a simple question I’d bring into your next leadership meeting.

Pick one thing everyone currently believes about the business.

Maybe it’s that your reps need more activity, your market doesn’t respond to outbound, the messaging isn’t working, you need another SDR or buyers in your category prefer email.

Then strip the explanation away.

What do we actually know?

Not what do we believe.
Not what seems obvious.
Not what happened at your last company.

What evidence do we actually have?

You may discover the conclusion is completely right. Great! Now you can operate with more confidence.

You might also discover that somewhere along the way, a hypothesis quietly became a fact without anybody noticing.

Those are the assumptions worth inspecting.

If there’s something inside your revenue system that everyone has an explanation for but nobody has really inspected, let’s chop it up.

It doesn’t need to become some formal sales call. We can open the hood, look at what the system is actually telling you and separate the data from the story around it.

Sometimes you don’t need another strategy.

You just need to figure out whether you’re solving something that’s actually happening.

👉 Open the hood with me

Week 16 of my own Operating System wasn’t perfect.

Money is still tighter than I want it to be. A couple of deals I would love to have closed still haven’t. A client payment still needs to process. There are plenty of things across The SD Lab, Cheer Media and Cheer Dads that I can’t control.

Something felt different this week though.

I didn’t pressure an opportunity that asked for more time or send another five emails to a deal that went quiet. I didn’t chase a partner because his proposal wasn’t ready when I expected it. I didn’t turn one scary email into an emergency. When an SDR dashboard showed something concerning, I didn’t turn the missing data into an accusation.

I communicated, collected information, made the next appropriate move and kept operating.

Sixteen weeks ago I probably would’ve described this Operating System mostly in terms of productivity: commitments, routines, priorities and getting the right things done.

I don’t think that’s what it’s becoming anymore.

It’s changing the space between something happening and how I respond to it.

Pressure can be real without requiring panic. A problem can be real without my first explanation being correct. An opportunity can be exciting without requiring me to immediately reorganize everything around it. Uncertainty can exist without needing to be eliminated by Friday afternoon.

Maybe that’s the lesson I’ve been circling all week.

Data first. Story second

I can’t always control what happens next but I can stop inventing the answer before it does.

I can encounter pressure without becoming pressure.

What’s one thing your organization currently treats as fact that might actually still be a theory?

Hit reply and let me know.

I read every one.

Thanks for spending a few minutes with me this Monday. I’ll be back next week with another field report from inside the trenches.

Have a great week 🤙

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

- Tom Slocum ✌️

If your outbound motion feels busy…

…but fragile

If your CRM looks full…

…but forecasting still feels shaky

If your team works hard…

…but pipeline doesn’t feel predictable

That’s what I fix

I work with founders and sales leaders in B2B (Series A–B, 5–20+ reps) who need structure before scale

Not more activity
Not more tools
Structure

Here’s how we do it:

This is the core engagement.

A hands-on rebuild of your outbound foundation so pipeline becomes structured, measurable and owned by the team not held together by heroics.

Inside 45 days we:

Best for:

When you don’t need a full rebuild just a sharp correction

Designed for fast clarity and immediate execution lift

Our private Slack community for reps and leaders building outbound in the real world.

Free and paid tiers available

If you’re reading this thinking, “Does this apply to us?”

It probably does

Book a 20 min Pipeline Diagnostic
No pitch. Just alignment