How to Build Out Your SDR Function with Sam Blond, Partner at Founders Fund and Host of SaaStr CRO Confidential

If you have ever watched a startup hire three SDRs, buy five shiny sales tools, launch twelve sequences, and then act shocked when the calendar stays emptier than the office snack drawer on Friday afternoon, welcome. You are among friends.

Building an SDR function sounds simple on paper: hire reps, book meetings, feed pipeline, celebrate revenue. In real life, it is more like assembling a race car while still learning where the brakes are. That is why Sam Blond’s advice stands out. His framework is refreshingly unglamorous, highly practical, and a lot more useful than the usual “just scale outbound” sermon. The big idea is not to build an SDR team because it looks sophisticated. You build one when your company has earned the right to do it.

This matters because a strong SDR function can do two jobs at once. First, it creates more top-of-funnel demand and helps account executives focus on closing. Second, it becomes a training ground for future AEs and future sales leaders. Done right, the SDR team is not just a meeting factory. It is a talent engine, a pipeline engine, and a discipline engine all rolled into one very caffeinated department.

Why an SDR Function Exists in the First Place

An SDR, or sales development representative, owns top-of-funnel work: prospecting, qualifying leads, opening conversations, and booking meetings for the next stage of the sales process. In many SaaS organizations, SDRs sit between marketing and closing reps, turning raw interest and cold targets into qualified pipeline.

That role sounds narrow, but the impact is broad. A great SDR function improves lead qualification, increases outreach consistency, sharpens account targeting, and gives your sales org a repeatable way to generate opportunities. It also forces the company to answer hard questions: Who is your ideal customer? Which pain points actually convert? What messaging gets replies? Which accounts deserve human attention instead of automated wishful thinking?

In other words, the SDR team does not just create activity. It exposes whether your go-to-market motion is real or mostly PowerPoint.

Sam Blond’s First Rule: Do Not Hire SDRs Too Early

This is the part founders often skip because hiring SDRs feels like “building a real sales machine.” Sam Blond’s view is far less romantic. He argues that founders should not introduce an SDR function until two conditions are true: outbound already works at some level, and someone can actively manage the SDRs.

1. Prove outbound before you specialize it

If your existing team cannot source opportunities through outbound, adding junior reps will not magically solve the problem. It usually just creates more noise, more dashboards, and more sad Monday pipeline reviews. Before you hire SDRs, your founders or AEs should already know how to generate meetings through outbound. That means there is at least a baseline process, a credible message, and some evidence that the target market responds.

Sam Blond has emphasized that AEs should keep doing their own outbound even after an SDR team exists. That is a huge mindset shift. Many companies treat SDRs as a permission slip for AEs to stop prospecting. Blond treats outbound as a permanent sales muscle. The AE should close revenue, yes, but they should also know how to source it. Otherwise, the SDR function becomes a disconnected side quest instead of a revenue partner.

2. Make sure someone can actually coach the team

New SDRs do not thrive on vibes. They need call reviews, messaging feedback, account guidance, prioritization, and fast correction. If nobody has time to coach them, you are not hiring pipeline generation. You are hiring confusion.

This is why a founder-led sales motion with one overwhelmed founder and one AE is usually too early for a dedicated SDR team. If nobody can monitor list quality, improve talk tracks, or explain why one meeting counts and another does not, the reps will optimize for the only thing they control: volume. Congratulations, you have invented spam.

When It Is Time, Who Should You Hire First?

Blond’s answer is wonderfully practical: either hire an SDR leader you trust, or hire two SDRs at the same time. Not one lonely rep floating in organizational limbo like the last sock in a dryer.

Why two reps? Because one rep gives you anecdotes. Two reps start to give you patterns. You can compare performance, messaging, ramp speed, and behavior. You can spot whether a problem lives in the rep, the process, the market, or the handoff. With one rep, every result becomes an emotional debate. With two, you can start acting like adults with data.

Blond also recommends solving for some experience in your earliest hires. Yes, SDR is often an entry-level role. No, your first SDR hires should not be learning sales, prospecting, positioning, prioritization, and emotional resilience all at once while also inventing your outbound motion from scratch. Early hires should have some SDR experience, or you should hire a manager who is willing to act like an individual contributor while building the function.

Another underrated move is hiring from trusted networks. In a world obsessed with process, this sounds almost old-fashioned. It is also smart. Early SDR hires shape culture, standards, pace, and expectations. Trusted operators from prior teams or strong referrals from people who know your environment can dramatically reduce ramp risk.

Build the SDR Operating System Before You Chase Scale

Once you make the first hires, the next job is not “more activity.” The next job is building a repeatable operating system. This is where many SDR teams either become sharp and efficient or descend into sequence-shaped chaos.

Define the ideal customer profile

Your SDR function needs a clear ICP, not a motivational poster that says “mid-market companies.” Get specific. Which industries convert best? Which sub-verticals respond faster? Which buyer personas have urgency, authority, and budget? Which geographies perform best? What company signals suggest actual pain instead of polite curiosity?

The better your targeting, the less your SDR org depends on heroics. Great teams do not win by sending more messages to worse-fit accounts. They win by being more precise about who deserves effort.

Create account prioritization rules

Blond’s framework points toward prescriptive targeting. That means SDRs should not be guessing which accounts to pursue based on instinct, boredom, or whichever logo looks cool on LinkedIn. Define named accounts, segment tiers, and buying signals. Use website visits, product usage, investor networks, customer referrals, intent data, job changes, and relevant trigger events to decide who gets attention first.

Signal-based outreach beats generic list blasting because it gives the rep a reason to reach out now, not just a name to email eventually.

Clarify the AE-SDR handoff

One of the fastest ways to poison an SDR team is a fuzzy definition of a qualified opportunity. If SDRs are rewarded for meetings and AEs quietly believe half those meetings are junk, you have created a cold war with calendars.

Set clear qualification criteria. Agree on what counts as a meaningful meeting. Document required discovery details. Make sure the AE sees context, not just a meeting invite and a prayer. Alignment here matters more than most tech-stack debates.

Use a tech stack that supports judgment, not replaces it

A modern SDR function benefits from CRM discipline, sales engagement tools, conversation intelligence, contact data, and analytics. But tools should reduce manual work and improve prioritization. They should not become an excuse to automate bad strategy faster.

The best setup is boring in the best way: clean CRM data, thoughtful sequencing, visible activity history, coaching from call recordings, and dashboards that show whether effort is turning into qualified pipeline and revenue. Fancy automation without message-market fit is just expensive turbulence.

How to Measure SDR Performance Without Lying to Yourself

Sam Blond lays out a sequencing logic that is especially useful for early-stage SaaS teams. In the beginning, measure opportunity creation. Later, move closer to revenue.

Start with opportunities

At the beginning, your biggest constraint is usually not too much pipeline quality. It is not enough pipeline, period. Early-stage companies often lack the historical data to know which segments, personas, and messages lead to the best closed-won outcomes. So early compensation and performance measurement often should reward quantity at the qualified-opportunity level.

That does not mean rewarding garbage meetings. It means acknowledging reality: when a market is still being mapped, top-of-funnel volume teaches you faster than over-optimizing for downstream perfection on day one.

Graduate toward revenue

Over time, the company learns. You discover which opportunities convert, which personas stall, and which accounts buy for real. Once those patterns become visible, keeping SDR incentives too far up-funnel can backfire. Reps may chase weak demos, argue for credit on shaky meetings, or flood the calendar without improving outcomes.

That is the moment to shift some measurement toward closed revenue or revenue influence. Quality matters more as your motion matures. Mature SDR teams are not admired because they book a lot of calls. They are admired because they source deals that close.

How to Scale the Team Without Setting Money on Fire

Here is a classic mistake: pipeline feels light, so leadership assumes the answer is more SDR headcount. Blond strongly pushes back on this. The first question is not whether your SDR-to-AE ratio looks pretty on a benchmark chart. The first question is whether the existing team is effective.

Before scaling, ask:

• What percentage of new pipeline comes from SDRs?
• What percentage of new revenue comes from SDR-sourced opportunities?
• How does SDR efficiency compare with AE outbound, marketing, partnerships, and other channels?
• Are conversion rates healthy enough to justify adding more people?
• Would additional reps improve output, or just spread the same broken process across more seats?

If the numbers are weak, scaling usually makes them worse. More reps on a weak system typically means lower efficiency, more management overhead, and more pressure to hit activity metrics that do not matter. The better move is to improve targeting, coaching, messaging, qualification, and alignment first. Then scale once the current team proves the model.

Modern Outbound Trends Sam Blond’s Advice Still Supports

One of the strongest parts of Blond’s playbook is his rejection of lazy “spray and pray” outbound. That style of outreach is fading because buyers are tired, inboxes are crowded, and generic personalization is now detectable from outer space.

Instead, build around four smarter principles:

Leverage networks

Warm paths still outperform cold guesses. Use founder relationships, investor introductions, customer referrals, employee networks, and relevant community ties. A network-aware SDR team creates better response rates without sounding like it was assembled by a template robot.

Offer something valuable

Value can be insight, relevance, a useful point of view, a tailored observation, or a genuinely thoughtful gesture. The key is giving the buyer a reason to care. “Just bumping this up” is not value. It is a cry for help.

Pair outbound with brand

Outbound works better when the market has heard of you. Brand awareness, customer advocacy, category positioning, events, and content all make SDR outreach warmer. The best SDR messages do not introduce a company from absolute zero; they capitalize on familiarity that marketing and product have helped create.

Use signals, not just lists

Website visits, intent data, job changes, funding events, hiring trends, content engagement, and product interactions all create better timing. The SDR function of today is part researcher, part communicator, part prioritization machine. The job is not to contact everyone. The job is to contact the right people for the right reasons at the right moment.

Common Mistakes That Quietly Kill an SDR Function

• Hiring SDRs before outbound has shown any signs of life
• Letting AEs completely stop prospecting
• Using one SDR as an experiment instead of creating a real function
• Rewarding booked meetings without agreeing on what “qualified” means
• Scaling headcount before improving conversion rates
• Confusing more automation with better strategy
• Treating the SDR org as a disposable meeting machine instead of a talent bench

The healthiest SDR teams are not built on hustle alone. They are built on targeting, coaching, alignment, measurement, and patience. Boring? Maybe. Profitable? Usually.

Operator Experiences from the SDR Trenches

In real companies, building an SDR function rarely feels like a smooth rollout. It feels more like learning to cook during a dinner party: everyone is hungry, the smoke alarm is emotionally involved, and somebody keeps asking when the main course will be ready. That is exactly why Sam Blond’s advice lands so well with operators. It matches what teams experience once the theory meets the sales floor.

One common experience is that early SDR teams expose weak positioning faster than leadership expects. On day one, everyone says the messaging is clear. On day ten, reps start getting confused replies, polite ghosting, and prospects who ask, “So what exactly do you do?” That is not an SDR problem. That is a company clarity problem wearing a headset. Teams that improve quickly treat SDR feedback as market intelligence, not as an excuse to lecture reps about “working harder.”

Another pattern is that the first SDR manager matters more than almost any dashboard. The best early leaders are part coach, part editor, part data detective, and part therapist. They listen to calls, tighten messaging, set standards, and protect the team from random executive opinions disguised as strategy. The wrong manager, meanwhile, can create a culture where reps chase volume, hide weak meetings, and learn that activity is safer than judgment.

There is also the emotional reality of the role. SDR work is repetitive, visible, and rejection-heavy. Even talented reps can have rough weeks where nothing lands. The teams that stay productive usually do three things well: they celebrate learning, they keep coaching tight, and they give reps a believable path forward. That path might be promotion to AE, more ownership in named accounts, or specialization by segment. Without that future, the role starts to feel transactional, and turnover rises fast.

Experienced operators also learn that AE-SDR trust is fragile. If AEs think SDRs are tossing weak meetings over the wall, resentment builds. If SDRs think AEs are gatekeeping credit or dismissing real effort, they stop collaborating. The fix is not motivational posters about teamwork. The fix is shared definitions, shared feedback, and shared numbers. When both sides can see what converts, arguments shrink and coaching improves.

Finally, there is the scaling lesson nearly every company learns the hard way: adding headcount never fixes ambiguity. It amplifies it. If account selection is fuzzy, more reps create more confusion. If messaging is mediocre, more reps spread mediocrity faster. If coaching is weak, more reps simply increase the number of people being poorly trained at once. The best revenue leaders treat early SDR success as something to prove, not something to assume. They slow down just long enough to build the machine correctly. Then, when they finally add fuel, the thing actually moves.

That is the real beauty of Sam Blond’s framework. It is not anti-growth. It is anti-delusion. Build the motion, teach the motion, measure the motion, and only then scale the motion. It is less flashy than announcing a “world-class outbound engine” on LinkedIn, but it tends to produce something even better: revenue.

Final Thoughts

If you want to build out your SDR function the smart way, start with a simple question: have we earned specialization yet? If the answer is no, keep founders and AEs close to outbound. If the answer is yes, hire carefully, coach aggressively, define quality clearly, and scale only when the numbers deserve it.

Sam Blond’s framework is powerful because it respects sequence. First prove outbound. Then add structure. Then measure what matters. Then scale. Companies that skip that order usually buy a lot of software and call it strategy. Companies that follow it build a repeatable pipeline engine and a stronger sales bench at the same time.

That is not just good SDR design. That is good go-to-market design.