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

There is a massive difference between diagnosing a GTM problem from the outside and sitting inside the room where the decisions are actually being made.

This week I flew to Denver and spent two days onsite with a B2B SaaS client.

I went in knowing the numbers, I knew the outbound motion, I knew the people, I had been on the Zoom calls, in the strategy sessions, reviewing the process, coaching the team and helping build the system.

But being there changed the picture

Because dashboards show you activity, CRM reports show you outcomes, Slack shows you conversations, Zoom shows you meetings

The room shows you the truth

The client is an inbound-led B2B SaaS business trying to create a stronger outbound muscle.

That sounds simple when you put it on a slide: build the list, enrich the contacts, create the messaging, call the accounts, book meetings, generate pipeline.

But when you're physically sitting with leadership, RevOps, BDRs and the people who have lived through the company's previous attempts at outbound you start seeing the invisible layer.

You hear the hesitation when someone says “we've tried this before.” You see the tension when the conversation shifts toward increasing outbound's share of pipeline. You understand why a clean recommendation on paper can feel risky to the people who have to own the result.

That context matters

During the onsite we were looking at a business that had finished the previous quarter below several key revenue and pipeline targets.

At the same time the business still had real strengths: a healthy new logo close rate, strong retention and a clear growth target ahead.

So the issue wasn't “outbound is broken”

The issue was much more nuanced

How do you build a reliable outbound channel inside a company whose muscle memory, confidence and operating model have historically been built around inbound?

You don't answer that by yelling “more dials”

One of the biggest lessons from the week had nothing to do with tooling or copy. It was about resistance.

When you're remote, resistance can look like disagreement. In the room you can usually see what it actually is.

Sometimes it's scar tissue
Sometimes it's uncertainty
Sometimes somebody is protecting a system that used to work
Sometimes they're worried the new strategy creates expectations their team isn't ready to carry

and sometimes they just need to see that the plan is more thoughtful than “Hey let's crank outbound to 30% and hope”

That's why good GTM consulting isn't just knowing what should happen

It's understanding what has to become true for the organization to believe it can happen

We also turned the outbound workflow into something the team could actually run without guessing.

The operating lane became

LinkedIn Sales Navigator → Wiza → Salesforce → Clay → Gong → Trellus → call list

Not because tech stacks are sexy. They're not. Nobody has ever tucked their kid into bed and whispered “one day you'll have immaculate enrichment logic” 😂

The point wasn't the stack. It was removing ambiguity.

Where do accounts come from? Who enriches them? What happens when data is missing? Which persona gets called first? What owns the next action?

Those sound like small questions until a rep has to answer them 50 times a day. That's where outbound motions quietly slow down.

We narrowed the primary phone persona toward VP-level Engineering and Product leadership and gave the team a cleaner path from account selection to dial.

Less ambiguity
More execution

Another thing from the week stuck with me.

One outbound effort we reviewed had generated thousands of dials and hundreds of conversations — but very few meetings relative to all that activity.

You can debate every conversion point in that funnel, but the larger lesson is universal:

You can have a mountain of activity and still not have an outbound system

A real system lets you see the conversion points, find the leak and coach the actual constraint instead of telling the team to “do more.”

That's the gap I see constantly in B2B teams. They don't necessarily lack effort. They lack a motion they can inspect.

The coolest part of the onsite wasn't a breakthrough slide or some genius line I delivered.

It was all the little things you can only pick up when you're there.

Who asks the first question? Who goes quiet when a certain topic comes up? Which idea gets repeated later without prompting? Where leadership and operators use different words for the same problem. Which process people nod at but clearly don't trust. What the team talks about over lunch, walking between rooms or after the formal agenda is over.

That is GTM data too and leaders miss a ton of it when they only manage through dashboards.

You don't need to fly to Denver every week but you probably need to spend more time where the work actually happens.

Sit in a prospecting block
Listen to five cold calls without multitasking
Watch how a rep builds a list
Follow one account from targeting through first touch
Ask a BDR where the process feels stupid
Ask an AE which meetings they immediately know are real
Ask RevOps where reps constantly work around the system

Then compare what you hear to what the dashboard says

That's where the good stuff is

and if you're trying to rebuild a GTM motion the “why” is usually where the real work starts

This trip reinforced something I already believed but probably didn't appreciate enough

The closer you get to the work, the clearer the work becomes

That's true for consultants. It's true for founders. It's true for CROs, VPs, managers and RevOps.

Sometimes the next GTM breakthrough isn't another strategy deck

Sometimes you just need to get in the room

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

- Tom Slocum ✌️

If this issue felt familiar - lots of activity, unclear conversion points, reps working around the process that's the work I do inside The SD Lab.

I work directly with B2B founders and sales leaders to inspect the motion, find what's actually breaking and build an outbound system the team can own after I leave.

No giant strategy deck. No “just do more.” We get close to the work and fix what the dashboard can't explain.

If you think your team needs that kind of outside set of eyes let's talk

Book a 20 min Pipeline Diagnostic
No pitch. Just alignment