The Wrong Hire: Ten Mistakes Founders Make Building Their First Sales Team

A technical founder closes her first eight customers herself. Cold emails, warm intros, three-hour discovery calls she ran from a coffee shop because the office was too loud. She is not a natural salesperson, but she knows the product better than anyone alive, and that turns out to be enough.

Then she hires the first Account Executive (AE). The candidate has four years of SaaS experience, a confident close rate, and a reference from a company she recognizes. The AE joins in January with a six-month ramp. By April, the pipeline looks thin. By June, the AE hasn’t closed a single deal. By August, the AE is out.

The founder assumes she hired the wrong person. So she hires again. This time she goes more senior: someone who has managed a small team, sold a larger deal size, and spent seven years at a company with a name investors recognize. The new hire joins in November, full of energy and a structured ninety-day plan. By February, the pipeline is being built. Yet, by April, closings don’t look any better. The founder is having the same conversation she had fourteen months earlier.

Two AEs. Fourteen months. Thousands of dollars in compensation. And yet, she is back doing sales herself: closing deals, rebuilding relationships, re-explaining a product that changed twice while her sales team was trying to sell the original version. Different names and yet the same reality: she had hired the wrong profile. Twice. For the same wrong role. And the year she spent learning that was a year she could not get back.

This is not an unusual story. It is the modal story. According to OpenView, 68% of first sales hires at early-stage startups leave within eighteen months. The failure rate is not primarily about the candidates. It is about the decisions founders make before those candidates ever walk through the door.

Here are the ten most consistent mistakes — and the companies that made them publicly enough to learn from.

The most common mistake has nothing to do with who you hire. It is about timing. Most founders hire their first salesperson before they can describe, in writing, how they closed their last five deals: which objection came up in which conversation, what language made the prospect lean in, what the decision-making process looked like on the buyer's side, and where the deal almost fell apart.

If you cannot write that down, you are not ready to hand it to someone else. You are asking a stranger to reverse-engineer a process you have never articulated, against a prospect set that has never heard of your company, with no brand, no case studies, and no marketing machine generating inbound.

Mike Molinet, co-founder of Branch, described exactly this mistake in a First Round Capital interview. When Branch first began to monetize, he hired a VP of Sales and handed that person a hundred things to figure out — none of which had been codified. The hire spent their ramp writing a playbook that already existed implicitly in Molinet's head. The result was predictable. The rule of thumb from First Round's Meka Asonye is cleaner: before hiring your first salesperson, you don't need to have the exact recipe made yet. But you should have most of the ingredients in the cupboard.

The hire is not a delegation event. It is an addition to capacity — and for a longer period than most founders expect.

Some of the best-performing early-stage startups did not close a single deal without founder involvement for five years after their first commercial hire. That is not a failure of the sales organization. It is the recognition that early enterprise deals involve a level of trust, authority, and product conviction that a new hire cannot replicate in month two. The founder closes. The AE watches, assists, runs follow-up, and learns. Then the AE closes with the founder available. Then the AE closes alone.

When Figma hired Kyle Parrish as its first sales hire — at $2 million in ARR — Dylan Field and Evan Wallace stayed close to deals for far longer than the title structure would suggest. The transition was gradual and intentional. Founders who disappear from the revenue process in quarter one of a new hire's tenure are not delegating. They are abandoning. The result, consistently, is a rep who either fails or develops habits that look like sales but are not producing the revenue the model needs.

The seniority trap is seductive, especially when investors are involved. There is a VP of Sales at a well-known SaaS company who is interested in your space. They have a strong network, an impressive track record, and they negotiate their OTE with confidence. Hiring them feels like a statement of intent.

The problem is structural. A VP of Sales at a company with two hundred salespeople has not done cold outreach in years. Their skill set is management, pipeline review, and process optimization. They have always had a marketing team generating inbound, a solutions engineer for technical demos, and a legal team for contracts. Remove all of that infrastructure and their skills are not diminished — they are simply the wrong skills for the job at hand.

Branch's Molinet made this error explicitly. So did the founding team at Zenefits, which built a massive sales organization before the process, compliance infrastructure, and qualified candidate pool were in place to support it. What the early-stage company needs is not someone who can manage a sales team. It needs someone who can be the sales team — and be willing to do the blocking-and-tackling work that comes with building from zero. The right first commercial hire is typically a full-cycle Account Executive with three to seven years of experience at startups under $10 million in ARR — someone who has closed their own deals, built their own pipeline, and done it with limited resources. That is a very different profile from a VP of Sales. Do not confuse the two.

A rep who consistently hit quota selling $500,000 ACV enterprise contracts to Fortune 500 procurement teams is a different professional from a rep who can sell a $15,000 annual contract to a startup CTO. These are not just different deal sizes. They are different buyer psychologies, different sales cycles, different objection sets, and different definitions of what "value" means in a conversation.

The mistake founders make is hiring for brand-name experience rather than contextual fit. A candidate who crushed it at Salesforce selling to large financial services firms brings a set of instincts, tactics, and relationship patterns that were optimized for a very specific context. In a startup selling to a different buyer type, those instincts can actively work against them. They are pitching solutions to problems the buyer does not yet know they have. They are building relationships at levels of organizational seniority the product has not yet earned access to. They are running a motion designed for a market that is not yours.

The signal to look for is not which company they came from. It is whether they have sold, successfully, to the same buyer profile you are targeting, at a similar deal size, at a company of similar maturity. That is a precise filter, and it will cut out a lot of impressive-sounding candidates. It should. Brand-name experience is a proxy that breaks down in early-stage selling — and breaking down at the first hire is the most expensive place it can happen.

An Account Executive closes deals. A Business Development Representative — or Sales Development Representative — creates the pipeline that AEs close. These are not different intensities of the same job. They are different jobs entirely, requiring different skills, different personalities, different compensation structures, and different management rhythms.

AEs are measured on revenue closed. BDRs are measured on qualified meetings booked and pipeline generated. An AE who spends their day doing cold outreach is an AE who is not closing. A BDR who is asked to own the full cycle from first email to signed contract is a BDR who will close less than an experienced AE and generate fewer meetings than a focused BDR. Both are forms of lost leverage.

The mistake founders make — particularly those without sales backgrounds — is hiring an AE and expecting them to generate their own pipeline through outbound prospecting. This is a structural mismatch that compounds quickly. AEs who are asked to do both tend to default to prospecting activity because it feels productive, while the more uncomfortable work of pushing deals to close gets deferred. Companies running this model tend to see pipelines that look full on paper and do not convert. If your first hire is an AE, make sure the pipeline they are closing is already warm — from founder-led outreach, from inbound, from your network. If the pipeline does not exist yet, you need a BDR first, not an AE, or you need a founder who is still generating pipeline themselves.

The candidate who is primarily focused on OTE, accelerators, and commission structure is not the right first sales hire. This is not about compensation — early-stage salespeople need to be paid fairly, and comp structures that do not reflect the risk of the role will not attract good candidates. The issue is motivation.

Early-stage sales is structurally brutal. There is no brand. There are no case studies. Every prospect conversation begins with convincing someone that the company exists and that the product works. Objections come constantly, and the answers are not always in a script. The sales process changes frequently as the product evolves. A candidate who is there for the comp structure will not push through the specific friction of that environment. A candidate who believes in the problem the product solves — who understands why the company exists before they understand what they will earn — will.

First Round Capital describes this as the difference between a missionary and a mercenary, and it is the single most useful frame for evaluating early-stage sales candidates. The missionary sells because they believe what they are selling matters. The mercenary sells because the number is right. Both can be excellent salespeople. Only one of them is built for the first eighteen months of a startup's commercial existence.

The founders who transition out of sales most successfully do not simply stop selling. They document what they were doing — and then teach someone to do it.

What that documentation contains matters. Not a Notion page with bullet points about the company's value proposition. The actual artifact: a recording of the five most successful discovery calls, with annotations. The objection map — the twelve objections that appear most frequently, in the order they typically appear, with the responses that worked and the ones that did not. The ICP written with enough specificity that the new hire can disqualify a prospect on a ten-minute call. The pricing logic explained so that the first hire can have that conversation without the founder in the room.

Sam Taylor, who built sales at Loom after serving as Dropbox's first enterprise sales rep and first sales leader at Quip, is explicit about this: before you make your first sales hire, take inventory of what you are articulating around value and vision, capture the way in which customers are finding success, and put it in a format that can be delivered credibly by someone who was not there for the founding. The hire cannot inherit institutional knowledge that was never externalized. If it exists only in the founder's memory, it will not transfer. The playbook is the product of the handoff. Build it before you need it.

The standard advice from SaaStr's Jason Lemkin — hire two reps at the same time — is counterintuitive to cost-conscious founders and correct for a structural reason that is easy to miss.

With one rep, you have no control group. If the rep misses quota, you cannot determine whether the problem is the rep, the market, the process, or the product. You have one data point and no way to triangulate. You will spend months trying to diagnose a failure that might have been visible in weeks if you had a comparison.

With two reps, patterns emerge. If both miss, the problem is the system. If one hits and one does not, the problem is the person — and you have evidence of what the successful execution looks like. Hiring two reps also creates a competitive dynamic that tends to bring out better performance from both. The cost of the second rep is not the cost of the salary. It is the cost of faster, more accurate learning about whether your go-to-market motion works at all.

The first sales hire is not only a revenue function. In a company with fewer than twenty employees, the person who is talking to the most prospects every day is holding the most product intelligence in the company. What objections come up before the demo? What competitor is mentioned most frequently? What feature does almost every prospect ask about that is not on the roadmap? What does the prospect say in the second call that they did not say in the first?

When Figma hired Kyle Parrish, he and the founders treated early customer conversations as a product research function as much as a revenue function. The sales organization was explicitly product-obsessed — Parrish wanted every sales hire to be someone who could also be a product designer, knowing the practical reality was that they could not, but insisting on the mindset. Discovery calls fed directly back to the product team. The sales motion and the product roadmap evolved together.

Founders who hire a sales rep and separate them from the product conversation are throwing away the most direct signal they have. The rep is not just there to close. They are there to listen in a way that the product team, once past the founder-customer conversation stage, usually cannot.

The final mistake runs in the opposite direction from most of the ones above. Having absorbed all the advice about fit, timing, seniority, and profile, some founders over-engineer the search and wait for a candidate who satisfies every criterion simultaneously.

That candidate does not exist in the available pool at the moment you need them, at the salary you can offer, in the role that can be defined precisely only after someone has been in it for sixty days.

The practical approach is to define the bottleneck. If the problem is pipeline, you need someone who can generate outbound. If the problem is conversion, you need someone who can close. If the problem is both, you need either a full-cycle rep who can manage both adequately or to acknowledge that you are the pipeline engine for now and the hire is the closing engine. Hire for the actual bottleneck, set expectations accordingly, and accept that the first commercial hire is as much a learning exercise as a revenue exercise. The hire who teaches you what the role actually needs is worth more than six months of searching for the hire who theoretically fills a perfectly specified role.

The right question is not: who is the best salesperson I can find? It is: who is the right person for the specific motion I am running, against the specific buyer I am selling to, at the specific moment in the company's development where I am right now?

That question is harder to answer. It is also the one that matters.