The 3 Hires That Define Your Revenue Trajectory (and How AI Changes Who You Hire)

I've built sales orgs from zero four times. At CareerBuilder I went from 0 to 240 sellers. At Groupon I went from 0 to 400+ sellers across 23 markets. At SpringCM I founded the BD org from scratch. At Prokeep I rebuilt the sales function, expanded pipeline significantly, and restructured the team toward upmarket growth.

Every time, the revenue trajectory was determined before we hit the wall - determined by which people we put in which seats early. Not the reps. The three foundational hires that shape everything else.

I have gotten these right. I have gotten them spectacularly wrong (which is more than I can say for some teams I've managed). Here's what I've learned either way.

Hire 1: The First Sales Leader

What "great" looked like before AI: Someone who had done the job at your stage and segment. They could walk in, assess territory, set quotas, hire reps, and run a pipeline review without a manual. They brought a playbook from their last company and adapted it. The key signal: they had personally sold the type of deal you need them to sell.

What "great" looks like now: Everything above plus one new requirement. They need to be able to design workflows, not just execute them. This sounds abstract so let me be specific: in the first 90 days, your first sales leader should be able to map the full SDR-to-close workflow, identify which steps could be automated, build at least a prototype of one automation, and measure its impact. If they've never done anything like that, they're going to hire their way through problems that should be designed through. Hiring is slow and expensive. Design is fast and cheap.

Red flags that didn't used to matter: They talk about AI tools they use but can't describe what those tools actually do in their workflow. They say "we'll get our tech stack sorted" without having a specific opinion on what that means. They've never personally built anything - not a spreadsheet model, not a sequence, not a workflow automation. In a world where the tools are this accessible, a senior sales leader who has never built anything is telling you something about how they think. Every sales leader I talk to says they're "using AI." When I ask how, 90% say "we have a Gong license." That's like saying you're a chef because you own a microwave.

The new interview question: "Walk me through an AI tool you've actually built or customized. Not one you've bought - one you've configured or built for a specific purpose." The answer tells you immediately whether they're an architect or an order-taker.

I asked this question of a candidate last year. He paused, then described a custom GPT he'd built to coach his reps on MEDDPICC - reps could paste deal notes and get immediate qualification feedback. He'd iterated on it over three months. He could tell me exactly what it got wrong and what he'd done to fix it. I made an offer before the interview was over.

The terrible hire story: I hired a sales leader at a previous company - I won't say which - who had an exceptional track record on paper. Right stage, right segment, three strong references. What I didn't assess well enough was whether they could think systematically about process. They hired great individual reps. They could not design a scalable process to save their life. Every problem was solved by adding a human. Six months in, we had 40% more headcount and the same output. The problem wasn't effort - they worked incredibly hard. The problem was that they didn't have the mental model to see the system. We parted ways. It cost us almost a year.

I spent $50K on a sales enablement platform at that same company that my team used exactly twice. Both times were to show the vendor we were using it before the renewal call. That hire and that platform are spiritually connected.

Hire 2: The First RevOps Hire

What "great" looked like before AI: Systems fluency. Salesforce admin, data hygiene, reporting, process documentation. The person who kept the machine running. Analytical enough to build dashboards, organized enough to run weekly forecast calls, patient enough to manage the CRM migrations nobody else wanted to touch.

What "great" looks like now: Everything above plus the ability to serve as the AI infrastructure architect for the revenue org. This person needs to evaluate, integrate, and maintain AI tools across the sales workflow. They need to know enough about prompt engineering to configure AI tools well, enough about data architecture to make sure the AI has clean inputs, and enough about change management to get reps to actually use the new workflows.

This is a different profile than the classic RevOps hire. The person who was great at Salesforce admin in 2022 may or may not have developed the additional skills this role now requires. Assess this explicitly.

Red flags: They talk about AI in terms of tools they're evaluating rather than tools they've deployed. They see their job as maintaining existing systems rather than continuously improving them. They can't tell you which steps in the current workflow are candidates for automation. Buying a $200K revenue intelligence platform and not changing your process is like buying a Peloton and hanging laundry on it - and the RevOps person who enabled that purchase owns part of that outcome.

How AI changes the math: One exceptional RevOps hire with strong AI tool fluency can do what used to require two people. They can build automated workflows, maintain data quality, run reporting, and configure AI tools - the leverage per person is dramatically higher when they know how to build. This means you should hold out longer and pay more for the right person.

Hire 3: The First Enablement Lead

What "great" looked like before AI: A curriculum designer with sales experience. They'd been in the field, understood what reps actually needed, and could build training content that transferred to real deals. The best enablement leads I've worked with were former reps who couldn't stop teaching - they found the coaching part more satisfying than the closing part.

What "great" looks like now: Same profile plus the ability to build AI-assisted coaching systems. The shift in enablement is from synchronous training (deliver a workshop, hope it sticks) to always-on coaching (the rep has an AI tool they can use before every call, during every deal review, when they're stuck on an objection at 9 PM). Building those tools - designing the prompts, iterating based on what reps actually find useful, measuring impact - is now core enablement work.

The annual Sales Kickoff: three days, $400K budget, a motivational speaker who once climbed a mountain, and the same top performers winning the same awards. Pipeline impact: zero. The enablement lead who can replace that model with tools that actually travel into the field with reps is worth their weight in closed deals.

The question that sorts this out: "Describe a coaching intervention you've designed that didn't require your direct involvement to deliver." Before AI, good answers to this question were rare. Now it's table stakes. An enablement lead who can only teach synchronously is going to be overwhelmed as the team scales.

How AI Changes the Math on Which Hire Comes First

Traditional sequencing: sales leader first, then reps, then RevOps once there are enough reps to need it, then enablement when you're big enough to have a training problem.

The new calculus: if AI tools can replace 35–40% of what a rep used to do manually, you need fewer reps for the same output. Which means you need RevOps and enablement sooner, to support a smaller, higher-caliber team with better infrastructure.

The companies that are getting this right are hiring their RevOps person at rep headcount of 4–5 instead of 10–12. They're building AI infrastructure early instead of bolting it on later. The ones doing it wrong are hiring more reps to solve a process problem, then wondering why the same process problems show up at larger scale.

The wrong hires in the wrong sequence don't just slow you down. They shape the culture, the habits, and the ceiling. By the time you realize the first sales leader couldn't design their way out of a spreadsheet, you've got 15 reps who learned to solve every problem by escalating to a human. That culture doesn't flush out quickly.

Get the three right. Get them in the right order. The rest is execution.

If you're building a revenue org and want a second opinion on sequencing, joepeck.ai has details on fractional CRO work - the kind of engagement where this sequencing question is usually the first conversation.