When Should You make Your First Sales Hire? (Later Than You Think)
There's a moment in the life of nearly every growing company where the founder stares at a whiteboard, or a spreadsheet, or a ceiling at 2am, and arrives at a conclusion that feels like clarity: "I need to hire someone for this."
The "this" varies. Sometimes it's sales. Sometimes it's RevOps. Sometimes it's marketing. But the underlying feeling is always the same — I can't keep doing everything myself, I need a person dedicated to this function, and once I have that person, things will start moving.
It's one of the most intuitive decisions a founder can make. It also might be the most expensive mistake a scaling company makes, and it happens so often that it barely registers as a mistake anymore. It just gets filed under "hiring is hard" or "we made a bad hire" and the cycle starts again.
But what if the hire wasn't bad? What if the system they walked into was?
Let me walk you through what I see happen, over and over, to the point where I can almost script it before it unfolds.
A company has a product that works. Customers exist. Revenue is coming in — mostly through the founder's network, referrals, maybe some inbound. It's enough to prove there's something here, but not enough to scale on. The founder knows they need to build a real revenue function. They need pipeline. They need process. They need someone who "gets" sales or marketing or operations and can take ownership.
So they write a job description. They recruit. They interview. They hire. And they feel good about it — because they just checked a major box on the scaling checklist. They have a revenue person now. Progress.
No clearly documented ICP. No defined sales process or buyer journey. A CRM with inconsistent, outdated data. No measurement framework connecting inputs to outputs. No playbook. No enablement material beyond a product sheet and some tribal knowledge in the founder's head.
The hire walks into a vacuum.
The first few months are discovery. The new hire is smart, motivated, and trying to get their bearings. They're mapping the product, learning the market, figuring out who the customer actually is, and trying to build process from nothing. They bring frameworks from their last role because that's all they have to work with. They set up tools the way they know how. They start reaching out to prospects based on their best interpretation of who to target.
Meanwhile, the founder is watching from a distance, expecting to see momentum. They hired this person specifically so they could stop worrying about this function and focus on other things. Every week that passes without clear results feels like wasted time.
By month four or five, the hire is executing — but they're executing against their own understanding of the problem, which was assembled from fragments. They didn't get the founder's full vision because it was never documented anywhere. They didn't get a strategic framework because one didn't exist. They got a title, a laptop, and a loose mandate to "build pipeline."
The work they produce isn't bad. But it's disconnected from what the founder actually wanted, because the translation layer between the founder's brain and the hire's daily execution was never built. Sound familiar? It's the broken telephone problem from the last post — just compressed into a single relationship instead of an entire org chart.
By month seven, eight, or nine, the gap between expectations and reality has become impossible to ignore. The founder is frustrated. The hire is frustrated. Targets aren't being hit. Conversations get tense. And then comes the decision point.
Sometimes the hire gets let go. The founder calls it a performance issue and moves on. But if you actually audit what happened, the performance issue was downstream of a structural one. The person was performing inside a vacuum. They were asked to drive a car that hadn't been built yet and then blamed when it didn't go fast enough.
The financial cost of this cycle is significant. Depending on the role — VP of Sales, RevOps manager, first SDR — you're looking at salary, benefits, recruiting costs, onboarding time, and the hardest one to quantify: opportunity cost. Nine months where the revenue function was effectively stalled, not because nobody was working on it, but because the work had no architecture to build on. Conservatively, this cycle costs six figures. For senior hires, it can approach or exceed a quarter million when you add it all up.
And that's just one cycle. Most companies go through two or three before they realize the problem isn't the people they're hiring.
Sometimes, though, the outcome is worse than a clean exit. Sometimes the hire doesn't leave. They settle in. They build a small, functional-enough operation that produces just enough activity to avoid serious scrutiny. Calls are being made. Emails are going out. Pipeline exists in the CRM, though nobody's totally sure how accurate it is. Reports get generated weekly, though they don't connect to anything strategic.
On the surface, it looks like the revenue function is "handled." And because it's handled, nobody looks deeper. The founder moves on to other priorities. The structural problems underneath — the misaligned systems, the fragmented data, the absence of a unified go-to-market architecture — don't get addressed. They just get buried under a layer of mediocre but acceptable activity.
This is often more damaging long-term than the hire who leaves, because it creates a false sense of progress. The company thinks it has a revenue function. What it actually has is a person managing chaos just well enough to keep the lights on.
- Calls are being made
- Emails are going out
- Pipeline exists in the CRM
- Weekly reports are generated
- The revenue function looks "handled"
- Nobody's sure how accurate the pipeline is
- Reports don't connect to anything strategic
- Systems are misaligned and fragmented
- Structural problems are getting buried
- Chaos is being managed, not solved
I want to be really clear about something. This is not an anti-hiring argument. You need people. You need talented, dedicated people in your revenue function to grow. Every company does.
The question isn't whether to hire. It's when.
And the answer, almost always, is later than you think.
Before you hire someone to execute inside your revenue engine, you need to make sure there's an engine for them to execute inside. That means having clarity on your ICP — not just a vague sense of who your customer is, but a documented, validated, specific understanding of who you sell to, why they buy, what triggers their search, and what alternatives they consider. It means having a defined process — a buyer journey, a sales motion, a set of workflows that a new hire can step into on day one rather than inventing from scratch. It means having a technology stack that's connected, configured, and actually supporting the work rather than creating more of it. And it means having a measurement framework that ties activity to outcomes so you can tell within weeks, not months, whether things are working.
When those things are in place, a hire accelerates everything. A good rep inside a well-engineered system doesn't need six months to "figure it out." They need six weeks. Because the architecture tells them who to call, what to say, how to track it, and what success looks like. They can focus on what they were actually hired to do — sell — instead of spending their first two quarters doing systems administration and strategy work they were never equipped for.
The metaphor I keep coming back to is the fish tank. Salespeople — and revenue professionals in general — are chameleons. They grow to the size of the environment you put them in. If you drop them into a clean, well-designed, fully-equipped system and teach them how every piece works, they will surprise you with what they can do. I've seen it with people nobody would have bet on — introverts, career-changers, people who'd been labeled "average" at other companies. Put them in the right system and the output changes completely.
But if you drop them into a bowl — no architecture, no process, no tools that connect, no vision that's been translated into something executable — you'll get bowl-sized results. And you'll blame them for it, even though the constraint was never their talent. It was their environment.
No architecture. No process. No connected tools. No translated vision. Bowl-sized results — and then you blame the fish.
Clean system. Defined process. Clear ICP. Measurement framework. People surprise you with what they can do.
If you're a founder reading this and recognizing your own story in it — you're not alone and you didn't do anything wrong. The advice the market gives scaling companies is almost always "hire faster." Investors say it. Advisors say it. LinkedIn says it. And it makes intuitive sense because people are what make companies go.
But people perform inside systems. And if the system doesn't exist yet, the hire isn't the first move. It's the second.
The first move is engineering the machine they'll operate inside. Get the architecture right. Get the data flowing. Get the tools connected. Get the vision translated into workflows and playbooks and measurement frameworks that a human being can actually follow.
Then hire. And watch the difference when you do.
- ✓A documented, validated ICP — not a vague sense of who your customer is, but a specific understanding of who you sell to, why they buy, what triggers their search, and what alternatives they consider
- ✓A defined process — a buyer journey, a sales motion, a set of workflows a new hire can step into on day one rather than inventing from scratch
- ✓A technology stack that's connected, configured, and actually supporting the work rather than creating more of it
- ✓A measurement framework that ties activity to outcomes so you can tell within weeks, not months, whether things are working
This is Part 5 of a 12-part series on GTM engineering and the future of revenue architecture. Part 4: "GTM Engineering vs. Revenue Operations" is on our blog now.
See what your GTM engine is actually missing
Book a Revenue Workshop and we'll review your entire GTM motion — and hand you 200 ICP-matched target accounts before you leave.
Book Your Revenue Workshop