How to Hire Your First AE (And Why Most Founders Get It Wrong)

Most founders hire their first AE six months too early and then blame the hire when it doesn’t work.

The timing problem is almost never about the person. It’s about what you’re asking them to walk into. If you haven’t documented your sales process, if you can’t describe your ICP in a way that would let someone else find prospects, if every deal you’ve ever closed has had you at the centre of it — you’re not hiring an AE. You’re hiring someone to watch you work and hoping they can reverse-engineer it.

That’s not a job spec. That’s an unfair situation.

---

The Core Mistake: Hiring Before the Process Exists

Here’s what typically happens. The founder is overwhelmed. They’ve got a pipeline, they’re closing deals, but they can’t do everything. So they hire an AE to “take sales off my plate.” The AE starts, gets a few weeks of onboarding, and then… struggles. Deals stall. Nothing closes without the founder getting involved. After four or five months, the founder decides the AE isn’t good enough and either manages them out or quietly sidelines them.

The problem isn’t the AE. The problem is that there was no process to hand over.

What the founder calls “taking sales off my plate” is actually “taking sales off my plate without me first documenting how I do it.” Those are completely different things. The first is reasonable. The second is setting someone up to fail.

Before you hire an AE, you need to be able to write down your sales process from first contact to close. Not in bullet points. In detail. What happens at each stage, what questions get asked, what a good discovery call looks like, what the typical objections are and how you handle them, what makes a deal worth pursuing, what makes it a waste of time. If you can’t do that, you’re not ready to hire.

---

The Profile Mistake: Builder vs Executor

Once you’ve decided you’re ready to hire, the next mistake is getting the profile wrong.

There are broadly two types of AE. There’s the builder — someone who is comfortable in ambiguity, can work with incomplete information, helps develop the process as they go, and has done this before at an early-stage company. And there’s the executor — someone who excels inside a well-defined process, can follow a playbook, is highly consistent, and performs best when the infrastructure exists.

Builders are harder to find, more expensive, and often frustrating to manage. They push back. They want to do things their way. They don’t always follow the playbook because there isn’t a playbook yet.

Executors are easier to manage but will struggle and underperform if the playbook doesn’t exist. You’ll watch them flounder and conclude they’re weak, when actually they just needed the scaffolding you said you’d provide and didn’t.

The question is not which type is better. The question is which type you actually need. At seed stage, with no documented process and a fairly undefined sales motion, you need a builder. Possibly painful, but necessary. At growth stage, with a clear playbook and established pipeline, you want an executor who will run it consistently and at scale.

Most founders hire an executor when they need a builder, because executors interview better. They’re polished, they have structured answers, they quote their quota attainment percentages. Builders are often messier in interviews. Don’t mistake the polish for competence.

---

Writing the Job Spec

Your job spec is where you set expectations, attract the right person, and repel the wrong ones.

Most AE job specs at startups are generic. “We’re looking for a hungry, driven sales professional to join our fast-growing team.” That attracts everyone and filters out no one.

A good job spec for an early-stage AE should be specific about:

The stage you’re at. How much ARR, how many customers, what the product does, what the market looks like. Don’t hide that you’re early. The right person wants to know that.

What they’ll be walking into. Is there an existing pipeline? Are there warm leads? Is there marketing support? Be honest. If there’s no inbound, say so. If there are 50 open opportunities, say so.

What the first 90 days look like in reality. Not “you’ll hit the ground running.” Actual milestones. What do you expect them to have achieved by day 30, 60, 90.

The OTE and the split. Don’t hide the comp structure. State the base, the OTE, the quota, and the commission rate. Candidates who won’t engage without this information waste everyone’s time. Candidates who ask the right questions about it are often the ones worth hiring.

---

The 30/60/90 Day Ramp Plan

Hiring without a ramp plan is how you end up with confused, underperforming AEs and a growing conviction that “good salespeople are impossible to find.”

Here’s a realistic structure:

Days 1–30: Foundation. No selling. Pure learning. The AE should understand the product deeply enough to demo it without help. They should have read every closed-won deal note in the CRM. They should have listened to recordings of your best calls. They should have done a mock discovery call with you and received detailed feedback. By day 30, they should be able to articulate why customers bought, what problems the product solves, and who it’s not right for.

Days 31–60: Accompanied selling. The AE starts running calls, but you’re still present — initially leading, then shadowing, then stepping back. They’re building their own pipeline in parallel. Target for day 60: at least two self-sourced discovery calls completed, one proposal sent. They should also be contributing to improving the sales materials based on what they’re seeing.

Days 61–90: Independent selling. They’re running their own deals, with regular check-ins. You’re reviewing calls, not attending them. Target for day 90: at least one deal in late stage that they’ve managed independently. The question at day 90 is not “have they closed?” — deals take time. The question is “are they running a credible process?”

---

Red Flags in the Interview Process

A few things worth watching for when you’re interviewing AEs:

They can’t describe a recent loss clearly. Good salespeople learn from deals they lose. If someone can only talk about wins, they’re either not reflective enough or not honest enough. Either is a problem.

They blame the product, the leads, or the process for past failures. There’s always context, but a pattern of externalising failure is a warning sign. You want someone who takes ownership.

They’re vague about their actual quota and attainment. “I was top of the leaderboard” is not a number. Push for specifics: what was the quota, what did you close, over what period. If they can’t give you a straight answer, that tells you something.

They don’t ask about your sales process, your CRM setup, or what support is in place. An experienced AE who has done this before knows that infrastructure matters. If they’re not asking, they either haven’t done it at a real company, or they’re not thinking critically about the role.

---

What Success Looks Like at 6 Months

By month six, a good first AE should have closed at least two deals independently. Not “the founder helped a bit.” Independently — they sourced the opportunity, ran the process, handled the objections, and got the contract signed.

If that hasn’t happened, the question to ask is honest and uncomfortable: is the AE the problem, or is the process still founder-dependent? If the AE is still deferring to you at every critical juncture, if they don’t feel confident handling a commercial conversation without you, if customers are asking for you to be on calls — that’s not an AE problem. That’s a process problem.

A fully independent AE is the proof of concept that your sales function can scale. One person closing without the founder is the evidence that two people could. Then five. The first hire is the hardest and the most important.

For a detailed playbook on reducing your involvement in deals, the founder extraction playbook covers the specific steps. And if you’re not sure your process is actually documented well enough to hand over, how to build a sales process is the right starting point before you write a single job spec.