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

A few months ago I started working with a SaaS company whose outbound motion wasn't producing what leadership needed. There was one SDR, activity was inconsistent and meetings weren't predictable. The easiest conclusion would've been pretty simple: the rep needs to perform better. If that doesn't happen, maybe we need another SDR.

Except the deeper I got into the operation, the less convinced I became that the rep was actually the biggest constraint.

There were issues with workflow, data, dialing infrastructure, account prioritization, coaching, management, ownership, inspection and AE alignment. There were pieces of an outbound motion everywhere, but there wasn't yet a complete system around the person being asked to produce.

So instead of immediately adding another person we started changing the environment around the one we already had.

Eventually the numbers started changing with it.

Earlier in the engagement, connect rates were somewhere around 3–4%.

After changing the dialing environment and working through the motion, a recent stretch produced 1,795 dials, 133 connects, 44 conversations, four meetings and a 7.41% connect rate.

Put that into simpler math. At a 4% connect rate, 500 dials creates roughly 20 live connects. At 7.41% those same 500 attempts create roughly 37.

That's around 85% more live connects without adding another rep.

Same person
Same company
Same market
Different environment

That doesn't mean we've proven the entire outbound model and it definitely doesn't mean the answer is to immediately hire five SDRs.

It means we learned something important about the system

when we improved the environment, the environment responded

I spent a good portion of this week working with leadership on what the next twelve months of this outbound organization could look like. Hiring naturally became part of that conversation but I kept finding myself coming back to a question that I think a lot of growing revenue teams skip.

What exactly have we proven enough to scale?

There's a dangerous sentence inside growing sales organizations

“We just need more reps”

Maybe you do

But before adding another salary I'd want to understand what we're actually asking that person to scale.

If the current motion has bad data, weak messaging, low connect rates, unclear territories, poor account coverage, inconsistent management or a process that mostly exists inside someone's head, another SDR inherits all of it.

More people don't automatically make the system better.

Sometimes they simply increase the number of people experiencing the same constraint.

I've watched organizations hire SDR #2 because SDR #1 wasn't producing. Then SDR #2 doesn't produce either so eventually they hire a manager. Before long you've got three salaries investigating what may have been the same broken process all along.

Headcount isn't a GTM strategy

It's capacity

Capacity becomes valuable once you understand what you need more capacity doing.

This is where I think sales organizations get themselves into trouble. We naturally assume performance problems are people problems because people are the easiest variable to see. The rep isn't booking enough meetings, the manager isn't coaching enough or the AE isn't converting enough.

Sometimes that's exactly what's happening.

Other times the environment is making the outcome nearly impossible.

Can the rep consistently access the right accounts?
Can they reach enough people?
Does the data support the activity level you're expecting?
Does the messaging create conversations?
Can those conversations become meetings?
Do those meetings become legitimate opportunities?
Is somebody actually responsible for inspecting that entire system every week?

Until those answers start becoming predictable adding another person isn't really scaling a motion.

You're scaling assumptions

I had a two-hour working session with the SDR this week where we reviewed calls, worked through Trellus, talked about follow-up and looked at how his workflow has evolved over the last few months.

Something has clearly changed

One or two meetings in a week isn't some crazy event anymore. It's becoming increasingly normal so I asked him what that felt like compared to where we were roughly twelve weeks ago.

His answer stuck with me

I'm paraphrasing but essentially he said he always knew he could do the job. They had just struggled to find a system that allowed him to do it.

I've thought about that several times since because sometimes we're coaching the person when we should be inspecting the environment around the person.

That doesn't mean accountability disappears. People still have to execute.

Standards, activity, skill and coaching all matter but there's a difference between holding someone accountable to perform inside a functioning system and expecting someone to compensate indefinitely for a broken one.

Good reps can overcome friction for a while

They shouldn't have to become the operating system

This became especially relevant while I was building the twelve-month outbound roadmap with leadership this week.

Sales plans love calendars.

September we hire another SDR
October we launch a new vertical
November we add another AE
January we expand the team

It looks beautiful on a slide

But what actually happened between September 30th and October 1st that suddenly made the business ready for another $80K–$120K of headcount?

Usually nothing

The calendar changed

That's not a GTM signal

So I've started thinking about these roadmaps differently

Instead of saying “we'll hire SDR #3 in November” what if the roadmap said “we'll add capacity once the existing motion consistently produces X held meetings at Y conversion rate with enough account coverage and management capacity to support another rep”?

Now the business has to earn the hire

The same thinking applies beyond headcount. Don't launch another vertical because Q4 started.

Prove the existing motion and understand what you've learned from it. Don't add another tool because the annual planning deck says it's time to optimize the tech stack. Identify the constraint the tool is supposed to remove first.

Dates can tell you when to inspect the system

Gates should tell you when to scale it

This week I also spent a lot of time working backward from the business instead of forward from SDR activity.

That's an important distinction

The question wasn't “how many calls should an SDR make?” It became “what does the business actually need outbound to contribute?”

Using the working model we built a $6M ARR goal could require roughly $15M in total pipeline. If outbound is expected to contribute around 30% of that number the SDR organization needs to create approximately $4.5M in pipeline.

From there we could work backward through the actual funnel

Depending on the assumptions we use that could mean roughly 90–118 accepted opportunities per year which could require somewhere around 257–338 held meetings. Spread across the year we're looking at roughly 21–28 held meetings per month team-wide.

With two productive SDRs that lands somewhere around 11–14 held meetings per SDR each month.

Now we can have an intelligent capacity conversation

Maybe two SDRs can support the number
Maybe we eventually need three
Maybe conversion improves and the team needs fewer meetings
Maybe ACV changes
Maybe outbound's contribution target changes
Maybe six months from now the system exposes a completely different constraint

Those are variables we can actually operate

It's a much better conversation than saying “three SDRs feels about right”

That's not strategy

That's vibes with payroll attached

Another client conversation this week brought me right back to the same lesson from a completely different market.

This founder operates in automotive and wants to eventually reach roughly 15 new deals per month. Instead of debating whether outbound could theoretically get him there, we started working backward.

At roughly a 25% close rate, 15 deals might require around 60 proposals. Creating 60 legitimate proposals could require somewhere around 120–150 real sales conversations. Depending on how the funnel performs generating that conversation volume could ultimately require something like 10,000–15,000 monthly dials.

Now we have something testable

But I still didn't tell him to go hire a bunch of BDRs

We talked about building a 90-day progression instead

First, fix the foundation: CRM, lifecycle stages, pipeline, segmentation, ICP, reporting and process. Then activate outbound against specific segments and start learning.

Which personas respond?
Which messages create conversations?
Who takes meetings?
Where do those meetings convert?
Where do they die?

Once we have that evidence we can optimize what works and build the operating system around it.

Then we decide what deserves more people

Bodies should be the multiplier, not the experiment

I think there's a larger GTM lesson buried in everything I watched this week.

Last week's issue was about separating data from story. Observe what happened before deciding why it happened.

This week feels like the natural next step because once we finally have evidence there's another temptation waiting for us: scaling the first thing that moves.

One campaign books three meetings and suddenly we want to double the budget. One rep has a monster month and we start planning four hires. One vertical responds and somebody wants to build an entire team around it.

Evidence isn't automatically proof.

A result tells you something happened. Your next job is understanding why it happened and whether it can happen again.

Can another rep reproduce it? Can another account list reproduce it? Does it survive another month? Does it still work when volume increases? Does downstream conversion hold? Can management support it? Do the unit economics still make sense?

That's the difference between discovering something that works and building an operating system around it.

The goal isn't to avoid making bets. Businesses have to make bets

The goal is to increase the size of the bet as the evidence gets stronger

Build enough to test
Test enough to learn
Learn enough to repeat
Repeat enough to scale

Before approving your next SDR hire there's one question I'd bring into the leadership meeting

What constraint is this person actually solving?

If the answer is “we need more meetings” go one layer deeper.

Why aren't you generating enough meetings today?

Maybe there isn't enough activity
Maybe reps can't reach anyone
Maybe conversation-to-meeting conversion is weak
Maybe the data is bad, the account pool is too small, the messaging isn't landing or the manager already has more people than they can properly support

Each of those problems requires a different response.

If your real constraint is a 2% connect rate, another SDR doesn't solve it. They experience the same 2% connect rate.

If the constraint is weak meeting conversion, another SDR simply creates more poorly converted conversations.

But if the existing SDR is genuinely at capacity, the funnel works, conversion is healthy, there's enough market available, management can support another person and the math says additional activity should produce additional pipeline?

Beautiful

Hire

That's capacity solving a capacity problem

If you're thinking about adding SDR headcount right now I'd love to pressure test the math with you.

It doesn't need to become some giant strategy engagement. We can open the hood, look at the funnel you have today, find where the actual constraint lives and figure out whether another rep would solve it or simply inherit it.

Sometimes you absolutely need another SDR

Sometimes you need to fix the machine the first SDR is already sitting inside

Those are two very different investments

👉 Open the hood with me

Week 17 of my own Operating System somehow taught me a similar lesson outside of sales.

Monday morning my car wouldn't start. Roadside assistance jumped it and I drove to AutoZone where they tested the battery and told me it had failed. A replacement would've been around $215.

I called Kia because I thought the warranty might cover it. It didn't. Their replacement would've been closer to $350 installed.

Old me could've reacted immediately

Car won't start
Battery failed
Buy battery
Problem solved

Instead I kept collecting information

I took the car to Kia. They tested everything and eventually told me the car was completely fine. It's a hybrid with a lithium battery and a reset system I didn't know existed. They showed me how it worked, handed me the keys and sent me home.

Total cost: $0

Apparently last week's newsletter wanted a sequel

But something else happened throughout the rest of the week that I've been thinking about even more.

I stopped treating everything that was open like something that required my attention.

There were proposals open, sponsor conversations open, partnership discussions open, client decisions open and plenty of opportunities that hadn't reached a conclusion yet.

Normally I can mentally turn every one of those into work.

Follow up, check in, send something, move something, create some kind of motion so I can feel like I'm advancing it.

This week I started asking a different question

Whose move is it?

If I sent the proposal and the buyer is reviewing it, there isn't necessarily a task.

If I sent the media kit and the sponsor is discussing it internally, there isn't necessarily a task.

If the client has the deck and we're already scheduled to review it, there isn't necessarily a task.

Something can be unresolved without requiring my attention.

That distinction freed up an incredible amount of mental space this week.

Instead of manufacturing work around things I couldn't move, I worked ahead. I finished next week's podcast episode before leaving for Denver, including all eight clips, captions, stories, promo assets and the rollout. I finished the Denver strategy deck, started a new sponsorship push, handled the client work and protected the family schedule.

There was still chaos around me
There was still financial pressure
There were still plenty of unknowns

The week just didn't feel chaotic

Seventeen weeks ago I thought building an Operating System would help me control more. I'm starting to think it's actually teaching me something much more useful.

It's teaching me what deserves control

A good operating system doesn't eliminate chaos. It keeps chaos from deciding what you work on next.

Maybe that's true for revenue organizations too.

You don't scale because growth feels urgent. You don't hire because the calendar says it's time. You don't add complexity because there's pressure to move faster.

You inspect what's actually happening, identify the constraint and prove the next move.

Then you earn the right to scale it

What are you thinking about scaling right now that you haven't completely proven yet?

Maybe it's a channel, a rep, a territory, a campaign or an entire team.

Hit reply and let me know what you're seeing

I read every one

Thanks for spending a few minutes with me this Monday. I'm headed to Denver this week to spend a few days inside one of these exact GTM systems so I'm sure I'll come back with plenty more from the field.

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