How to Hire Your First SDR: A Founder’s Guide

Hiring your first SDR is one of those decisions that looks small on the org chart and turns out to be enormous in practice. Done well, you build a pipeline engine that compounds. Done poorly, you spend $80K on a 22-year-old who quits in five months, you blame yourself, and you put the next SDR hire off by a year while you try to figure out what went wrong.

Most founders make the same two or three mistakes with their first SDR hire. This post walks through how to avoid them — calibrated for seed and Series A SaaS companies hiring their first dedicated outbound rep.

When is the right time to hire your first SDR?

The honest answer is: later than most founders think, and earlier than most procrastinators wait.

Hire too early — when you’re still figuring out ICP, messaging, and what closes — and the SDR fails because there’s no proven motion to scale. They make 80 calls a day and book zero meetings because nobody wants what you’re selling yet, or wants it but at a different price, or needs different framing. The SDR will rationally conclude they’re bad at their job and either burn out or quit. Neither of these is their fault.

Hire too late — after you’ve been founder-selling for two years and the calendar is choking the company — and you’ve already left meaningful revenue on the table. Worse, you’ve built dependencies on yourself that the org will need to unwind.

The right signal that you’re ready to hire your first SDR is one of these:

• You’ve personally booked and closed 10+ deals through outbound activity, and you can describe the playbook well enough that someone else could follow it
• You have a defined ICP, message-market fit on at least one segment, and pricing that doesn’t shift every quarter
• You can articulate “if I had 20 more qualified discovery calls per month, we’d close X more deals” with reasonable confidence
• Your CEO or VP Sales is spending more than 30% of their week on outbound activity

If you check three of those four boxes, hire. If you only check one, you’re hiring too early.

What kind of SDR actually fits an early-stage company

This is where most founders make their first big mistake.

They look at successful SaaS companies — Outreach, Gong, HubSpot — and they think “I want an SDR like the ones at those companies.” So they go hire a 26-year-old who’s been an SDR for three years at a 500-person org, paying them top-of-market comp, expecting them to import the playbook.

This almost always fails. Here’s why:

Big-company SDRs are specialists. They learned how to execute one specific motion — usually inbound qualification of demo requests, or outbound on highly defined ICP lists with proven messaging. At an early-stage company you need a generalist who can do outbound research, write messaging, run experiments, manage their own list, talk to product about feedback, and contribute to messaging iteration. The big-company SDR is great at executing within a structure. They’re not great at building one.

Early-stage chaos breaks them. When they arrive and find no enrichment tooling, no enablement library, no SDR manager, no SDR peers, no defined ICP playbook, and a CEO who’s distracted with fundraising — they don’t perform. Not because they’re bad, but because they’re calibrated for a structured environment that doesn’t exist yet.

They expect career progression that doesn’t exist. At a 500-person SDR org, the SDR → AE path is well-defined and happens in 18-24 months. At your 12-person company, you may not be ready to promote them in 18 months. Tell them this honestly, or they’ll resent it later.

The right first-SDR profile for an early-stage company looks different:

• 1-2 years of SDR experience at most, ideally at a small company or in their first SDR role at a mid-sized one
• Demonstrable hustle outside structured environments — built something, ran a side project, succeeded at something where the playbook wasn’t handed to them
• Strong writing skills, because at an early-stage company they’ll be writing their own sequences
• Comfortable with ambiguity — they should be visibly excited about a less-structured role, not anxious about it
• Real curiosity about your product/market — not generic “I love SaaS”

The 5 screening questions that actually work

Standard SDR interview questions (“walk me through your outbound process,” “what’s your meeting set rate”) give you compliance answers. Here’s what to ask instead:

1. “Walk me through how you researched the last prospect you booked a meeting with. What did you find? How did you use it?”

What you’re listening for: depth of research, specificity, and ability to connect insight to outreach. A great SDR will describe spending 15-20 minutes on a single prospect — reading their LinkedIn, their company news, recent funding, hiring patterns — and synthesizing that into an opener that doesn’t sound like template spam. A weak SDR will describe “I looked at their LinkedIn and saw they were a VP.”

2. “Show me an email sequence you wrote. Read me the subject line and first line of email one.”

What you’re listening for: their actual writing. Strong SDRs have written enough cold outreach that they can recite their best sequences from memory. They can also explain why each line is structured the way it is. If they can’t or won’t share specific writing, they’re either lying about their experience or they’ve never actually written their own sequences.

3. “Tell me about a quarter where you missed quota. What did you change in the next quarter?”

What you’re listening for: honesty, self-awareness, and adaptability. Top SDRs miss quota sometimes. The ones worth hiring talk about it openly, identify specifically what they changed, and demonstrate learning. SDRs who claim they’ve never missed quota are either lying or have only worked at organizations where the bar was too low to be meaningful.

4. “Why do you want to be an SDR at an early-stage company specifically?”

What you’re listening for: a genuine answer that distinguishes early-stage from later-stage. Strong candidates talk about wanting to build the playbook rather than execute one. They mention wanting closer access to product feedback loops, broader scope, faster promotion paths. Weak candidates give generic “I love startups” answers, or worse, can’t articulate why they’re applying to your specific company.

5. “If I gave you our product and our ICP today, what would your first week look like? Be specific.”

What you’re listening for: structured thinking, prioritization, and SDR craftsmanship. Strong answers include: spending day one understanding the product deeply (taking demos as if they were a buyer), day two studying recent closed-won and closed-lost deals, day three building target account lists, day four writing sequences in their own voice, day five testing. Weak answers default to “I’d start prospecting immediately.” Prospecting immediately is what amateurs do.

Compensation — what the market actually pays

SDR compensation has flattened in the last 12 months but the band remains meaningful. Current market for first-SDR hires at early-stage SaaS companies:

• Base salary: $50K–$70K USD ($60K–$85K CAD)
• OTE: $75K–$95K USD ($90K–$115K CAD), typically with 70/30 base/variable
• Variable structure: Most commonly tied to meetings set + meetings held + downstream pipeline that closes, weighted 50/30/20 or similar
• Equity: 0.05%–0.2% for the first SDR — meaningful for early hires, scaled to fully diluted

The mistake founders make at the comp negotiation: optimizing for base salary savings. An SDR making $50K base will quit for the first $65K offer. A few thousand dollars of base salary is the cheapest insurance you can buy against early attrition. Pay market rate.

The bigger lever is variable comp structure. Pay aggressively on meetings that hold AND on deals that close downstream — even six months later. This aligns the SDR with quality, not just volume. Spam outreach goes up dramatically when SDRs are paid only on meetings set.

Ramp expectations — what’s realistic

SDR ramp is faster than AE ramp but it’s still not instant. Realistic timeline for the first SDR at an early-stage company:

• Day 1–14: Product immersion, ICP study, closed-won and closed-lost review, shadowing your demos, drafting first sequences
• Day 15–30: First sequences launched, low-volume outreach (50-100 contacts/day max), focus on quality and feedback loops
• Day 30–60: First booked meetings, weekly iteration on subject lines / opening lines / sequence flow, A/B testing
• Day 60–90: Higher volume (150-200 contacts/day), consistent meeting booking cadence, first held meetings converting
• Day 90–120: Predictable meeting booking, first downstream deals close from their pipeline, formal performance review

If your SDR isn’t booking meetings reliably by day 60, the issue is usually one of: ICP is wrong, messaging isn’t working, your product isn’t ready for outbound, or you hired the wrong person. Diagnose carefully before defaulting to the last option.

The three mistakes founders make most

Mistake 1: Treating the SDR as a fully autonomous function.

Founders hire an SDR and expect them to figure everything out independently. This works for veteran SDRs at structured companies. It doesn’t work for early-stage SDRs without infrastructure. Plan to spend 4-6 hours per week with your first SDR for the first three months — reviewing sequences, joining their calls, debriefing wins and losses, iterating messaging. If you can’t commit that time, you’re not ready to hire one.

Mistake 2: Using the SDR as a calendar-booker for your own sales activity.

The SDR books meetings on your calendar, you show up, you close deals, repeat. This works for a quarter. Then the SDR realizes they’re an administrative function, not a sales development professional, and quits. Treat the SDR as someone learning a craft, not as your scheduling assistant.

Mistake 3: Hiring one SDR instead of two.

Counterintuitive but real: hiring two SDRs at the same time outperforms hiring one. Why? Because SDR is a lonely role at small companies, and isolation kills morale. Two SDRs can compare notes, push each other, share patterns. The marginal cost of the second hire is much lower than the cost of the first SDR quitting from isolation. If your budget permits, hire in pairs.

How to actually attract good candidates

Compensation matters but it’s not the whole story. The best SDR candidates at early-stage companies are choosing between multiple offers. What makes them choose yours over another:

A defined career path. Write down the SDR-to-AE timeline (typical: 18-24 months at strong performance) and commit to it in the offer. Candidates who choose you over a faster-promoting competitor are often choosing for the right reasons — they trust the company, they like the product, they want broader scope.

Direct CEO/founder access. First SDRs at early-stage companies should have direct access to the founder and product team. Sell this in the interview process. It’s a real differentiator vs. larger companies where SDRs are 4 layers removed from leadership.

Real equity. Equity at a 12-person company is meaningfully different than equity at a 500-person company. Explain the math honestly — what 0.1% means at different exit scenarios. Candidates who understand this and are excited about it are aligned for the right reasons.

A genuine product they believe in. The best SDRs choose products they’d buy themselves if they were in the buyer persona. If your SDR candidate doesn’t naturally describe your product with enthusiasm by their second interview, they’re not going to be effective on the phones.

One more thing: don’t hire from your network’s network alone

Most founders hire their first SDR through referrals — a friend of a friend, someone in their LinkedIn network. This works occasionally but more often produces mediocre hires because your network’s network is small and selection-biased.

Run a real search. Post the role publicly. Source actively from LinkedIn. Reach out to SDRs at companies one stage ahead of yours. Talk to 8-12 candidates before making an offer, not 3.

The cost of a bad SDR hire is at minimum $40K (base salary for 6 months) plus the opportunity cost of an unfilled SDR seat for that period. The cost of running a real search is maybe 10 extra hours of your time. The math is obvious.