Hiring Your First Sales Rep

The first sales hire is one of the highest-leverage decisions a founder makes, and one of the most frequently botched.

Not because founders lack judgment. Because the decision happens at the worst possible moment: when the founder is deep in deals, the pipeline is finally moving, and the pressure to hand something off is at its peak. Urgency is the enemy of good hiring. And in this hire, urgency is almost always present.

I've seen this play out enough times to know that the failure mode is rarely the candidate. It's the conditions the candidate walks into, a motion that was never made explicit, expectations that were never articulated, and a definition of success that existed only in the founder's head.

The question isn't just who to hire. It's whether you're ready to hire anyone at all.

(01) The timing problem

Most founders hire their first sales rep either too early or too late. The window where the hire actually works is narrower than it looks.

Too early means hiring before the motion is repeatable, before you've closed enough deals to know why they closed, before the ICP is pressure-tested, before there's a discovery process that someone else can follow. A rep hired into that environment isn't underperforming. They're operating without a map in territory the founder hasn't fully charted yet.

Too late means the founder is so embedded in the pipeline that there's no bandwidth left to onboard anyone properly. The hire arrives, gets a few handshakes and a Notion doc, and is expected to perform, while the founder disappears back into the deals they haven't handed off yet.

The right moment to hire is when you can describe your sales motion clearly enough that someone else could execute it, and when you have the time to show them how.

That moment is usually earlier than founders think on the motion side, and later than they think on the bandwidth side. If both conditions aren't met, the hire will struggle regardless of how good they are.

(02) Who you're actually looking for

The profile that works at this stage is not the profile that works at Series B. That distinction matters more than most job descriptions reflect.

Early-stage sales requires a specific type: someone who can build without infrastructure, tolerate ambiguity without losing discipline, and operate without a playbook, while helping to write one. That profile is not common. And it is almost never found in candidates who come from large, well-resourced sales organizations where process was already in place when they arrived.

The instinct to hire someone from a known, high-performing sales culture is understandable. The assumption is that the culture will transfer. It rarely does. What transfers is the expectation of support structures that don't exist yet.

What to prioritize instead:

1. 01

   Evidence of building, not just executing: Has this person ever had to create something from scratch: a territory, a segment, a process? Execution in a built environment is a different skill from construction. You need the latter. Look for specifics: what did they build, what broke, what did they change.

2. 02

   Intellectual curiosity about the customer: The best early-stage reps are genuinely interested in why customers buy, not just in closing them. They ask questions that go past the deal. They bring back signal from the market. In a stage where your ICP is still being refined, that curiosity is a functional asset, not a soft skill.

3. 03

   Comfort with feedback loops that don't yet exist: In an established sales org, performance is measured constantly. At early stage, the tooling is partial, the CRM is incomplete, and the metrics are still being defined. A rep who needs a fully instrumented environment to know how they're doing will flounder. Ask them how they self-evaluate when the data is sparse.

4. 04

   Low ego, high standards: The founder will still be better at selling the product for a while. That's a difficult dynamic for someone who was a top performer at their last company. The right hire understands this, learns from it, and doesn't resent it. What you want is someone who wants to earn the autonomy, not someone who expects it on arrival.

(03) Setting them up to succeed

The hire doesn't fail in the interview. It fails in the first ninety days, when the gap between what was promised and what actually exists becomes visible.

Before the first rep starts, three things need to exist in written form: a clear ICP with the criteria that define a qualified account, a discovery framework with the questions that consistently surface real pain, and an honest account of where the motion currently breaks down. That last one is the hardest, and the most important. A new rep who knows where the edges are can navigate them. One who discovers them by failing in front of customers loses confidence faster than any coaching can recover.

The first thirty days should be structured around observation, not performance. Shadow calls, recorded deals, conversations with existing customers about why they bought. The founder's job in this period is not to delegate. It's to transfer context. That's a different thing, and it takes more time.

Ramping a first sales rep is not a handoff. It's a knowledge transfer that happens to end in handoff. Treat it that way and the hire works. Treat it as a delegation event and you'll be refilling the role in six months.

Most hiring mistakes at this stage aren't about the person. They're about the conditions. Get the conditions right, and the right person will find their footing.

Hire for the stage you're in, not the stage you're projecting. Build the system first. Then bring in the person to run it.