From Outbound to Channel Partnerships: Your Burning Sales Questions Answered by SaaStr CEO and Founder Jason Lemkin

If your outbound emails are starting to feel like yelling into a void (a void that replies with “unsubscribe”),
you’re not imagining it. The B2B buying world didn’t just changeit got a software update, forgot to tell you,
and now your old “spray-and-pray” sequence is basically a fax machine.

In a closing AMA at SaaStr Annual, SaaStr CEO and founder Jason Lemkin tackled the questions founders and revenue leaders
obsess over at 2:00 a.m.: Is outbound dead? What do you do when sales slow? How do channel partnerships actually work
(and why do they feel like a secret level in a video game)? And when should you make those first scary executive hires?

Let’s break down the most practical takeawaysplus add some real-world, battle-tested patterns you can apply whether you’re
a founder-led sales team at $20K MRR or a scaling org trying to stop losing deals to “the partner ecosystem.”

The State of SaaS: What the Crowd Tells You (Even When the Market Won’t)

One underrated signal for “how SaaS is doing” is who actually shows up in the room when money, time, and attention are scarce.
At SaaStr Annual, Lemkin highlighted a shift in the mix: more founders/CEOs and more senior operators (CRO/CMO types),
while venture attendance fell significantly compared to prior years.

Translation: operators are still building. Buyers still have problems. But the easy-money halo isn’t doing your pipeline any favors.
In this environment, fundamentals winclear positioning, real value, and distribution advantages you can defend.

Burning Question #1: Is Outbound Sales Dead?

Lemkin’s answer is spicy and useful: classic outbound is close to deadthe old playbook of dumping a database
into a tool and blasting generic messaging is toast. Not “slightly less effective.” Toast.

What’s actually dead (and why)

• Generic emails at scale: buyers are drowning in automated outreachoften AI-generatedand they can smell it.
• “Cadence solves everything” thinking: if the message is wrong, doing it 7 times is not a strategyit’s cardio.
• Feature-less pitching: if your product doesn’t have a compelling “why now,” outbound just speeds up rejection.

What works now: outbound that earns attention

Modern outbound isn’t about volume first. It’s about relevance firstthen consistency. Here’s the approach that aligns with
Lemkin’s advice and what top teams practice today:

1. Start with a “10x feature” (or don’t press send yet).
   You need a reason someone should change behavior. “We’re slightly better” rarely survives an inbox.
   A 10x feature can be speed, cost, reliability, risk reduction, compliance, or a uniquely strong workflow.
2. Target 100 “must-have” accounts, not 10,000 “maybe” accounts.
   Build a list where the problem is obvious. If you can’t explain the fit in one sentence, your prospect won’t either.
3. Send fewer emailsmake them specific.
   The winning email reads like you wrote it on purpose. Reference a real trigger (job change, product launch, public roadmap,
   hiring pattern, tech stack, customer reviews, pricing shift, regulatory deadline, etc.).
4. Offer a tiny next step.
   Don’t ask for “30 minutes to discuss synergies.” Ask for something smaller: “Worth a 10-minute sanity check?” or
   “Want the 1-page benchmark?” The goal is a reply, not a TED Talk.

A practical outbound template that doesn’t sound like a template

(Yes, the irony is noted.)

• Line 1: Proof you did your homework (one sentence).
• Line 2: A sharp hypothesis about a pain or goal.
• Line 3: Your “10x feature” mapped to that hypothesis.
• Line 4: A low-friction ask (or a value asset).

Example (keep it human):
“Noticed you’re hiring 6 implementation roles this quarterusually a sign onboarding demand is rising fast.
If time-to-value is getting squeezed, we’ve helped teams cut onboarding cycle time by standardizing the workflow
across customer segments. Want a quick benchmark for companies at your stage?”

That’s not magic. It’s relevance. And relevance is the new scale.

Burning Question #2: When Sales Slow, How Do You Keep the Team Motivated (and Moving)?

A sales slowdown can make a team do weird things. Product blames marketing. Marketing blames sales. Sales blames “the leads.”
And the founder starts pricing in emotions instead of strategy.

Lemkin’s advice is deceptively simple: don’t chase the shiny penny. If you’ve got something working,
a slowdown doesn’t automatically mean you need a new motion. It may mean you need tighter execution, clearer priorities,
and a goal the team can see.

3 ways to stabilize momentum without pretending it’s 2021 again

1. Pick a stretch goal that’s likely attainable.
   Teams need a target that feels real. “Triple ARR” is inspiring… until it isn’t.
2. Make progress visible.
   Lemkin shared a founder story of literally moving a “superhero” up a revenue curve every week. Corny? Maybe. Effective? Absolutely.
   Humans work better when they can see progress.
3. Stay on course long enough to learn.
   If you have 50 enterprise customers, the path to 100 often existsif you don’t constantly reset the playbook.
   Improve messaging, tighten qualification, sharpen onboarding, and increase expansion motion discipline.

In slowdown moments, your job is to reduce noise. Protect the core motion, remove distractions, and make wins measurableeven small ones.

Burning Question #3: How Important Are Channel Partnerships for Sales and Revenue?

If outbound is “earning attention,” channel partnerships are “borrowing attention”and doing it at scale.
Lemkin’s warning is blunt: founders often learn direct sales first, then get smoked when competitors figure out partners.

Why? Because partners don’t just bring leads. They bring trust, implementation capacity, and “recommended vendor” status.
In many categoriesespecially as you move upmarketthe partner ecosystem becomes a deciding factor in deals you never even knew existed.

The uncomfortable truth: you can get boxed out

Large consultancies and systems integrators don’t recommend five tools per category. They tend to standardize.
If your competitor becomes “the default,” you’re suddenly competing against momentum, not features.

What “channel partnerships” actually includes

• Agencies & implementers: they configure your product and influence tool choice.
• Referral partners: they introduce you, you close.
• Resellers: they sell and sometimes support the customer.
• Technology alliances: integrations + co-marketing + shared accounts.
• Marketplaces: distribution through a platform ecosystem (and sometimes procurement shortcuts).

When to start building partners (hint: earlier than feels comfortable)

You don’t need a massive partner department to start. But you do need intention.
The earlier you begin recruiting the right partner types, the sooner you create “pull” you don’t have to buy with ads or brute-force outbound.

The channel playbook: how to do it without turning it into chaos

1. Define the partner value prop (for them, not you).
   Partners care about revenue, retention, differentiation, and delivery. Your program should make their business better.
2. Pick one motion to start.
   Referral-only? Co-sell with agencies? Integration-led with shared accounts? Don’t launch five partner types at once.
3. Build enablement assets that save time.
   Think: implementation guides, pitch decks, ROI calculators, customer case studies, demo scripts, and a simple “who this is for” page.
4. Create clean lead flow and deal protection.
   Nothing kills partner trust like channel conflict. Use deal registration, clear rules, and fast approvals.
5. Incentivize the behavior you want.
   Rewards can be margin, referral fees, marketing development funds (MDF), training, priority support, roadmap access, or co-branded demand gen.

A concrete example: agency-led partners for a SaaS company

Let’s say you sell finance automation software. Your best channel might be fractional CFO firms and implementation consultancies.
Your program could look like this:

• Partner promise: “We help you deliver outcomes faster and create a recurring services package.”
• Offer: referral fee + co-branded onboarding playbooks + partner-only office hours.
• Process: partner registers a deal → you confirm no conflict → you co-sell or they refer → partner implements → customer renews.
• Metric: partner-sourced pipeline, activation rate (signed partners who actually refer), win rate, and expansion within partner accounts.

Done right, this becomes a flywheel: partners bring you qualified customers, your product makes partners look good, and both sides get more business.

Burning Question #4: When Should Founders Make Their First Executive Hires?

This is where founders either build a machineor accidentally hire a title.
Lemkin shared a sequence many SaaS companies follow:

• VP Marketing can come earlier than you think (even around early-stage revenue levels) if they can create predictable pipeline.
• VP Sales is often best hired once you have at least two reps consistently hitting quotaso there’s a repeatable motion to scale.
• VP Product timing varies, but waiting too long can stall customer learning and roadmap discipline.

The deeper point: great executives scale what already works. If nothing works yet, you don’t need a “VP of Sales.”
You need proofpositioning, ICP, messaging, and a motion that converts without heroics.

Outbound to Channel: A 90-Day Transition Plan That Won’t Break Your Team

You don’t “switch” from outbound to channel like flipping a light switch. You layer them. Outbound creates signal; channel creates leverage.
Here’s a simple, founder-friendly rollout.

Days 1–14: Fix outbound fundamentals (so partners don’t inherit a mess)

• Clarify ICP and the “10x feature.”
• Rewrite messaging around outcomes, not features.
• Build a list of 100 best-fit accounts and run high-touch outbound experiments.
• Document what converts (subject lines, triggers, personas, objections).

Days 15–45: Launch a partner pilot (small, specific, measurable)

• Choose one partner type (e.g., agencies, consultants, tech alliance).
• Recruit 10–20 partners who already serve your ICP.
• Create a partner kit: 1-pager, demo script, pricing/packaging guidance, implementation notes, and referral rules.
• Set deal registration rules to avoid channel conflict from day one.

Days 46–90: Build the mini-brand and operational rhythm

• Run monthly partner webinars and office hours.
• Highlight partner wins publicly (recognition is an incentive).
• Co-market with partners using a repeatable campaign template.
• Track activation rate: how many signed partners actually source or influence pipeline?

The goal by day 90 isn’t “channel dominance.” It’s proof of motion: partners that activate, deals that register cleanly, and wins you can replicate.

Common Mistakes That Make Outbound and Channel Fail (Even With a Great Product)

Outbound mistakes

• Sending “value” that’s really a pitch in disguise. Buyers can tell.
• Over-automating too early. Scale what worksdon’t automate what’s broken.
• Weak ICP discipline. If your best prospects aren’t obvious, your messaging won’t be either.

Channel mistakes

• No partner value prop. “Please refer us” is not a program.
• Channel conflict. If partners fear you’ll steal deals, they stop bringing you deals.
• Neglect. A partner program isn’t “set it and forget it.” Attention is part of the incentive.

Conclusion: The New Sales Advantage Is Distribution You Don’t Rent

Outbound isn’t deadit’s just done being ignored. The path forward is slower, smarter, and more specific:
high-touch outreach that earns replies, paired with channel partnerships that earn trust at scale.

If you take only three ideas from Lemkin’s AMA, take these:
(1) stop spamming and start being useful,
(2) build visible momentum when sales slow,
and (3) invest in partners early so you don’t get boxed out later.

Field Notes: 3 Composite “Experiences” From the Outbound-to-Channel Transition (About )

These are composite, anonymized scenarios based on common patterns in SaaS go-to-marketnot one specific company.

Experience #1: The Outbound Reset That Doubled Replies Without “Scaling” Anything

A seed-stage SaaS team told themselves outbound was “dead” because their reply rate cratered after they added automation.
When we looked closer, the problem wasn’t outboundit was lazy targeting plus generic messaging.
They were emailing 2,000 companies that could possibly use the product, instead of 100 companies that clearly needed it.
The fix was humbling: they cut volume by 80%, rebuilt their ICP, and rewrote the first line of every email to reference a real trigger.
They also stopped asking for “a call” and started offering a simple benchmark relevant to the prospect’s role.

The result wasn’t overnight magic, but it was measurable: replies went up, meetings became higher quality,
and the team stopped burning weeks “tuning sequences.” The big lesson: outbound isn’t about sending moreit’s about guessing less.

Experience #2: The Partner Program That Failed Until They Made It About the Partner

A Series A founder launched a “partner program” that was basically a landing page and a hope.
The pitch to agencies was: “Refer us and we’ll pay you.” Agencies didn’t bitebecause referrals weren’t their bottleneck.
Their bottleneck was delivery and differentiation. They needed a way to package services, implement faster, and retain customers longer.
Once the company repositioned the program as “a services accelerator,” everything changed.

They built an implementation playbook, trained partners in a short certification, and created a co-marketed “launch package”
agencies could sell as a fixed-price service. The referral fee became the cherry on top, not the cake.
Partners started bringing deals because the program improved their margins and reduced their risk.
The big lesson: if the partner doesn’t win, you don’t winno matter how generous the commission looks on a spreadsheet.

Experience #3: Avoiding the “Boxed Out” Moment With Deal Registration and Clear Rules

Another team had the worst partner problem: channel conflict.
Partners would introduce accounts, and then the internal sales teamunder pressurewould “just help close it.”
Partners felt robbed, stopped sending leads, and quietly shifted attention to a competitor.
The recovery required operational adulthood: deal registration, response SLAs, and written rules about ownership.

They implemented a simple system: partner registers deal → internal team approves within 48 hours → partner gets protection and visibility.
For co-sell deals, they defined roles (partner leads discovery, vendor leads product deep dive, both align on mutual close plan).
The big lesson: partners don’t need perfection, but they do need predictability. Trust is built in process, not promises.