What your agent reads.
- name
- first-sales-hire
- description
- The first sales hire at a cybersecurity company: when to hand off founder-led sales, and whether the first AE, head of sales or VP of Sales must have sold security or sold to CISOs. Use when a founder is testing whether the sale transfers to a stranger, choosing between a founding seller and a sales leader, screening platform-vendor résumés against motion fit, weighing a sales engineer as the first commercial hire, planning the search, ramp and runway, handling a re-traded offer, reading a new hire's arrival number and pipeline deletion, or reading a failed first sales hire. Not sales-team design, quotas, opener and closer roles or comp plans (see sales-comp-and-structure); not which founder is CEO or whether you need a GTM co-founder (see who-is-ceo); not the founder-led motion, design partners or practitioner channels themselves (see early-gtm-motion); not where security talent looks or what hire-one equity is worth (see security-talent-and-comp); not pricing or the discount ask (see cyber-pricing).
- title
- The first sales hire
- question
- When do I hand off founder-led sales — and must the first AE have sold security?
- subtitle
- The thought arrives about a year before the hire should. That gap is where companies get lost.
- summary
- You hire the first seller to convert demand you have already proven, never to find it, and you hire a seller before you hire anyone to manage sellers. Screen for the sales motion they have run rather than the logos on their résumé, plan the search from the day you decide rather than the day they start, and budget for doing it twice.
- group
- company
- verified
- 2026-09-09
- order
- 60
1016 / 1024 characters
This is the top of the SKILL.md file, exactly as it downloads. Your agent reads the description field to decide when to load this skill. The rest of this page is for you.
You are probably too early. That is close to a law: the thought of a first sales hire usually arrives a year before the hire should. The move from founder-led selling to a professional sales organization is the trap nearly every company walks into, and it is set with reasonable-sounding advice. The rule that comes before all of it is simple. Stay founder-led until the sales motion repeats without improvisation. Everything here is about the day it does. The hire is harder in security than in most software because the sale runs through a security review of you, a proof of concept on production data, and a change queue you do not control, and a seller who has never carried a deal through those three does not know what they are ramping into.
Hand off the calendar, never the question.
You hire the first seller to convert demand you have already proven, never to find it. "You have a sales problem, so hire a VP of Sales" is the most common advice a struggling founder receives, and it is the most expensive way to avoid asking whether anyone wants the product. We have watched it run its course more than once. Hired into a demand problem, an experienced leader cleans up the pipeline, makes the forecast look professional, puts credible names on a plan, and the plan still misses. It costs a year, a large package, and their confidence, and you arrive back at the same question. Boards and founders read no revenue as a sales-execution problem because that diagnosis is actionable and the other one is existential.
So the test is what you are handing over. If it is a calendar you can no longer cover, hire. If it is a pipeline that will not close, do not. A new round is not a reason either. The pressure arrives from the board as a question about why the money is not being deployed, and the answer is that a sales organization can scale a motion and cannot discover one.
Hire out of necessity. The signal is your back breaking under the load: you are losing deals you could have won because you cannot get to them. Wanting it off your plate is not that.
And be clear what you are not doing. You are not handing off sales. You will be the most senior salesperson in your company with no sellers, with ten, and with a hundred, and a founder who hires in order to stop selling has misread the job in a way the hire will not fix.
Hire a seller, not a leader.
You hire someone to run the motion before you hire anyone to manage people running it. A leader brought in before two sellers have worked the motion is management bought for a thing nobody has done twice, and their first request will be the two sellers. The job description most founders write is the player-coach VP who sells and builds the team, because it looks like one hire solving two problems. It is a seller's job hidden inside a leader's package, priced for management while the first year's work is carrying a bag. The first hire reports to you.
Run the transfer test before the search.
You prove the motion can be transferred to a stranger, which is harder than repeating it yourself, because deals from your network close on borrowed credibility and a new hire has none. There are five checks.
One deal closed cold, from a source that did not already trust you or your investors. Early security deals run almost entirely on borrowed trust, so the cold close comes later here than in most software. At least one loss recorded, because security deals slip rather than lose, and a pipeline with no forced no cannot be handed to anyone. The signer named, meaning which function pays and from which budget line, which is often not the CISO. The pitch unchanged for two quarters, because if it moved recently the sale is still an argument only the founder can improvise, and a rep will invent their own and then mislead you about why deals died. And your own calendar as the reason, full and slipping, rather than hope or a term sheet.
A count of customers is a floor, not the test. Design-partner logos and pipelines with no losses count toward a total and toward nothing else.
Hire for the motion, not the logo.
You screen for the sales motion, not the industry. First sales hires in security are screened on whether they have sold security and which brands are on the résumé. Motion fit predicts outcomes. Pedigree does not, and it costs a premium. Someone who scaled a direct enterprise product will not automatically run a partner-led motion, and a marketing-minded leader will keep the funnel visibly busy and still miss, which in security is the standard disguise, because a calendar full of CISO demos looks exactly like progress. Hitting quota at a company that already had product-market fit is mostly a product of that fit. Ask what they closed before the brand carried them.
Screen on your price point, your cycle length, and the function that signs. The first commercial hire is also not always a closer. Where the hard part of your sale is the technical evaluation, the transferable work is the validation rather than the argument, and a sales engineer hired first lets you keep control of the pitch while shedding the volume. If most of your hours sit in evaluation rather than persuasion, the job you were about to post is the wrong one.
Fluency can be taught and restraint cannot. This market is small and talkative, and because deals slip rather than lose, the seller you want is the one who records the no. Run every finalist against your hardest logged objection and watch whether they make something up.
Plan from the decision date.
You budget the search, the ramp, and at least one failure as the normal case. A hire planned from its start date is already late. Plan from the date you decided: the search, the courtship, a candidate who walks away, a second candidate, a notice period, and the ramp. That sequence does not compress under pressure, and for a leadership seat the better part of a year between deciding and producing is normal. Plan it that way and the case for doing it yourself for two more quarters often gets stronger.
Expect to fill the seat more than once. Senior operators price a behind-plan company's risk into their package, so the companies that need one most hire at the highest price from the shallowest end of the pool. A signed offer is not a hire, and a candidate who reopens an agreed offer is showing you how they will behave in a deal. Ask what they are optimizing for. Sellers rarely tolerate a gap on their record, and some join a small company to close one rather than to build something, planning the next move from the first week. That candidate interviews well, ramps politely, and leaves in the first hard quarter. Keep every runner-up warm. In our portfolio the person who could not move earlier in the search is repeatedly the one who works out later.
On a role you have never run yourself, a retained search firm costs less than the failed hire it prevents. Remember what you are interviewing. Sellers interview more often than anyone else you will ever hire, and they are practised at it — a candidate who reads the room, mirrors your language and closes you at the end of the hour has demonstrated one thing, which is that they can do it for an hour. Panel interviews pass senior sellers that back-channel references would have caught. Use your investors' network for the back-channels, because the people who watched this candidate work are not on the reference list.
Price the ramp and the air pocket.
You model the hire as producing nothing during a ramp that the buyer sets, not the rep. A security seller's ramp is bounded by the buyer's evaluation cycle, the proof of concept, the security review, and the change queue, and no learning curve shortens that.
Expect the inherited pipeline to be deleted, and welcome it. The new hire inherits design-partner logos and deals that slipped, and the correct number is smaller. Their arrival number came out of the courtship, from that unscrubbed pipeline, and the danger is not that it is optimistic. It is that it becomes the company plan and gets told to the board as real. They will also arrive with a hiring plan of their own, which is a spending decision before it is a capacity decision. Agree the gate for it in the offer conversation, not after the first miss. Run the plan with zero new revenue and their cost in it, and pause the next hire at the first soft quarter.
You stay in. Keep the technical-evaluation deals and the stuck ones. One hire, one variable, one baseline. Expect the first request to be a discount, and say no.
Read a failure as a diagnosis.
You read a first failure as a finding about the sale, not as a screening error. Sales is the easiest function to measure and the hardest to explain: the number is unambiguous and its causes are not, a hot market, an inherited pipeline, your brand, one good champion, or the person. Name which one you think moved it before you decide anything, and check the same list next quarter.
On a leadership hire the earliest sign is recruiting. If they cannot hire beneath themselves in the first quarter, that is the signal, and what a wrong leader costs is the team they built, which takes longer to unwind than the hire did, because the people you remove did nothing wrong.
If one failed hire returns you to founder-led selling, the sale was not yet transferable. Fix the motion before you buy another leader. A second failure is about the role: its decision rights, its counterpart, a founder still running it personally. A third occupant failing the same way is not a screening error, and continuing to hire is how founders avoid the finding. In a sales seat, the constant across all of them is you.
Working the question.
- Name what you are handing over: the calendar, or the pipeline that will not close. If it is the second, stop.
- Run the transfer test: a cold close, a recorded no, the signer and budget line named, the pitch unchanged for two quarters, your calendar as the reason.
- List the stages your last three closed deals passed, and mark the ones you carried yourself. The stage you cannot hand over is the boundary of the job.
- Decide the seat before the profile: a seller rather than a leader, a closer or a sales engineer depending on where the hours were spent.
- Screen for motion and buyer fit, require a deal carried through at least three of your stages, and run each finalist against your hardest logged objection.
- Plan from the decision date. Put a search firm or someone who has hired the role in the loop, hold cash for one failure, and keep every runner-up warm.
- Before the offer, model the hire producing nothing through the ramp, and agree the gate on their own hiring plan.
- In the first ninety days, stay in the technical deals, let them delete the inherited pipeline, refuse the first discount request, and watch whether they can recruit.
Working with an agent.
Give your agent your last three closed deals, with the dates and the hours you spent at each stage. Ask it where your time actually went, into evaluation or into persuasion. If most of it went into evaluation, the job you were about to post is the wrong one.
Install the skill.
You are reading the skill itself — this page and the download are the same files. Unzip it into ~/.claude/skills/ (or a project’s .claude/skills/) and Claude Code loads it when the question comes up; so does any agent that reads Agent Skills.
mkdir -p ~/.claude/skills && cd ~/.claude/skills && curl -sLO https://techoperators.com/skills/first-sales-hire.zip && unzip -oq first-sales-hire.zip && rm first-sales-hire.zipfirst-sales-hire/SKILL.md
No terminal? Download first-sales-hire.zip and drop into your assistant’s project files.
