Building your first cybersecurity sales team
By Thiago Vieira11 min readUpdated
TL;DR
The founder must close the first customers before trying to delegate a sales motion nobody understands. Build your cybersecurity sales team around demonstrated bottlenecks, a teachable playbook, and onboarding that protects technical credibility.
In this guide
- 1. Close the first customers yourself
- 2. Hire when the bottleneck is execution
- 3. Hire capabilities in the right order
- 4. Choose builders before narrow specialists
- 5. Define the job and its incentives
- 6. Make the first 90 days a coached progression
- 7. Manage for evidence before expanding
- Common mistakes
- Frequently asked questions
1. Close the first customers yourself
Your first cybersecurity sales team starts with you. Closing the first customers forces the founder to connect a security problem with a buyer, budget, buying process, and defensible promise. You can delegate scheduling or research early, but not the responsibility for discovering why someone actually signs. A salesperson cannot repair an unclear market by delivering the same pitch more often.
For an email security product, the original pitch might focus on detection quality. Real conversations may reveal that the buyer cares more about investigation workload, deployment permissions, or coexistence with an existing gateway. For an MDR service, coverage boundaries and escalation ownership may decide the purchase. Those findings change the product and operating model, not just the sales script.
Capture the decision, not just the meeting notes
- Record the trigger, current workaround, business consequence, and person who owns the problem.
- Separate the technical evaluator, budget owner, procurement contact, and final approver.
- Document objections, promised evidence, evaluation conditions, and the buyer's next committed action.
- After a win or loss, ask what actually determined the decision and update the playbook.
Founder-led does not mean founder-only forever. Invite a future hire to observe calls and practice parts of discovery. Keep responsibility for pricing, scope, and commitments until the motion can be taught. Your goal is not to become the permanent closer for every deal; it is to make commercial judgment visible enough that another person can learn it.
2. Hire when the bottleneck is execution
Make the first sales hire when you have credible evidence that a defined type of customer buys for a recognizable reason, through a process you can describe. You do not need a perfect forecast. You do need more than an enthusiastic pilot, a friendly introduction, or a founder relationship that nobody else can reproduce. Write down what transfers and what still depends on you.
Look for work being delayed despite a clear next step: qualified conversations not followed up, suitable accounts left untouched, or evaluations waiting for coordination. Then check whether you have enough management time and financial runway to support recruitment, ramp, and a slower-than-hoped learning period. Do not fund the role using revenue that assumes immediate productivity.
Before opening the role
- Define the ICP, buying trigger, disqualifiers, and first use case.
- Show examples of real wins, losses, and stalled opportunities.
- Document discovery, demonstration, evaluation, pricing, and handoff practices.
- Name the founder responsible for weekly coaching and deal review.
- Explain the specific bottleneck this hire should remove.
- Confirm that product delivery and customer support can absorb additional customers.
Build the underlying process with the cybersecurity sales funnel guide. If the bottleneck is weak product fit or missing security evidence, solve that first. Adding outreach capacity to an unconvincing offer produces more objections, not a reliable growth engine.
3. Hire capabilities in the right order
There is no universal org chart for a cyber startup. The default is founder-led selling, followed by a hands-on commercial generalist, with technical and customer capabilities added as complexity demands. A founder who closes well but cannot prospect may need a different first hire from a technical founder who generates interest but struggles to advance a buying decision.
| Role | Primary responsibility | When to add it |
|---|---|---|
| SDR/BDR | Research accounts, start conversations, qualify initial fit, and hand over context. SDR often denotes inbound and BDR outbound, but labels vary. | When the ICP, messaging, qualification rules, and follow-up ownership are teachable. |
| AE/closer | Own discovery, stakeholder alignment, commercial progression, negotiation, and closing. | Often the first commercial generalist when founder-led opportunities follow a recognizable path. |
| Sales engineer/solutions engineer | Validate technical fit, run credible demonstrations, design evaluations, and explain integrations and constraints. | Earlier when technical evaluation repeatedly consumes scarce founder or engineering capacity. |
| Customer success | Coordinate adoption, value realization, renewal readiness, and customer feedback with delivery and support. | When onboarding and ongoing adoption require explicit ownership beyond the founding team. |
| Channel/partner manager | Recruit, enable, and manage suitable partners, account rules, and joint opportunities. | After partner demand and a workable partner proposition exist, unless partners are the core route to market. |
A sensible direct-sales sequence is founder, full-cycle AE, SDR/BDR once outreach is repeatable, then further specialization. Add a sales engineer earlier for integration-heavy products and customer success earlier for demanding onboarding. Customer outcomes need an owner from the first contract even when there is no dedicated hire. For an MSSP-led route, partner capability may precede direct prospecting.
Do not confuse commercial ownership with technical authority. An AE can coordinate a POC or POV without being qualified to approve an architecture or promise a detection capability. Establish who may answer security questionnaires, approve contractual claims, authorize discounts, and commit engineering time before the first independent sales call.
4. Choose builders before narrow specialists
An early generalist should research an account, run discovery, maintain the CRM, coordinate technical help, and ask for a commercial decision. They need curiosity and disciplined follow-through more than a famous employer. Generalist does not mean expert in every security domain. It means recognizing a knowledge boundary, involving the right person, and retaining ownership of the next step.
Specialize when a recurring workload requires depth and there is enough of that work to justify a dedicated owner. Repeated integration design may justify a solutions engineer. Consistent outbound execution against a proven segment may justify an SDR/BDR. Do not split one uncertain job into several narrow jobs and assume the handoffs will create a functioning system.
Use realistic work samples
- Ask the candidate to prepare discovery for a fictional SOC team replacing a manual workflow.
- Role-play a CISO who challenges evidence, deployment risk, and incident responsibilities.
- Have them write a follow-up that distinguishes verified capabilities from unanswered questions.
- Review how they prioritize a small fictional pipeline and explain why they would disqualify an opportunity.
Assess judgment rather than rehearsed terminology. A candidate who admits uncertainty and proposes a sound validation step is safer than one who confidently invents a control. Keep exercises proportionate, use fictional information, and do not ask candidates to generate unpaid prospecting work. Read more about selling to CISOs when designing the interview.
5. Define the job and its incentives
Before discussing commission, define what the person controls. Base pay compensates ongoing responsibilities; variable pay rewards explicitly defined outcomes. OTE means on-target earnings: base plus variable compensation at the stated level of target attainment. It is not guaranteed income, and an attractive OTE does not make an unsupported target credible.
Ramp is the learning and productivity period before full expectations apply. Explain training, access to opportunities, target treatment, and any temporary compensation arrangements in writing. Design expectations around your observed sales cycle, available pipeline, delivery capacity, and deal economics. Where history is thin, disclose the uncertainty instead of presenting a planning assumption as a proven benchmark.
Specify what earns commission, when it is earned and paid, how credit is shared, and how cancellations, refunds, multi-year contracts, partner involvement, and employment changes are handled. Get appropriate local legal and payroll advice. An SDR/BDR should not be rewarded solely for meetings that the AE cannot use; define acceptance and quality criteria together.
Minimum role and playbook brief
Customer and trigger: [ICP and reason to act] Owned outcome: [what this role is accountable for] Qualification: [fit, problem, buying process, next commitment] Evidence: [approved claims, demo assets, evaluation criteria] Boundaries: [technical, pricing, contractual approvals] Handoffs: [recipient, required context, acceptance rule] Compensation: [base, variable, OTE assumptions, crediting] Ramp: [learning milestones and review dates]
6. Make the first 90 days a coached progression
Onboarding is a transfer of judgment, not a product slide marathon. Give the hire access to approved materials, relevant systems, and safely handled customer context. Set weekly coaching sessions before their start date. Progress through observed capability rather than assuming the calendar alone makes someone ready to lead an evaluation or discuss a contract.
Days 1 to 30: understand and demonstrate
- Learn the ICP, buying triggers, product limits, pricing logic, and disqualification rules.
- Shadow discovery, demonstrations, technical reviews, and customer onboarding.
- Review won and lost deals, including procurement and security-review obstacles.
- Practice explaining data flows, permissions, deployment, and escalation without inventing claims.
- Complete a mock discovery, follow-up, and CRM opportunity review with founder feedback.
Days 31 to 60: execute with supervision
- Own a defined account set or a bounded group of opportunities.
- Lead discovery while the founder observes and debriefs.
- Run demonstrations within approved scope and bring technical questions to the right owner.
- Agree written POC or POV success criteria, responsibilities, and a decision process.
- Keep next steps, stakeholder roles, risks, and handoffs current in the CRM.
Days 61 to 90: own the motion and improve it
- Manage suitable opportunities end to end within explicit approval boundaries.
- Explain pipeline movement using buyer evidence rather than confidence alone.
- Complete a customer handoff covering scope, promised outcomes, and unresolved risks.
- Propose playbook changes based on actual objections and evaluation results.
- Review readiness, support gaps, compensation assumptions, and the next development priorities.
A long enterprise buying cycle may not produce a closed deal during onboarding. Assess whether the hire identifies real problems, reaches relevant stakeholders, secures meaningful commitments, and disqualifies weak opportunities. Conversely, a quick inherited deal is not proof that they can build pipeline. Judge the work in context and document what remains untested.
7. Manage for evidence before expanding
Run a weekly deal review around buyer behavior: what changed, what evidence supports the stage, who must act next, and what could stop the purchase. Separate coaching from administrative inspection. When an AE struggles, inspect account quality, messaging, technical support, and founder responsiveness before deciding that effort or talent is the only explanation.
Measure your own baseline. Track qualified opportunities by source, stage progression, time spent waiting, evaluation outcomes, and handoff problems. Compare similar cohorts and investigate individual losses rather than importing someone else's conversion benchmark. Add the next role only when a recurring constraint is visible and the existing team knows how that role will help.
Cybertech Acceleration supports solo and early-team cyber founders through a November to March program, with a €3,000 fee and no equity. Explore the program if you need to structure the commercial work before hiring. For help deciding which capability should come next, contact the team with your current sales process and the bottleneck you can demonstrate.
Common mistakes
Hiring a big-company VP of Sales too early
A leader used to established pipeline, brand recognition, and specialist teams may not want or know how to build from zero. Hire for the current job: hands-on selling, documentation, experimentation, and coaching. Add executive leadership when there is a real organization and a repeatable motion to lead.
Hiring without a repeatable playbook
A collection of founder anecdotes is not a transferable process. Document the customer, trigger, discovery questions, evidence, evaluation, and decision path. Keep improving the playbook with the hire, but do not make discovering the entire business an unspoken quota requirement.
Scaling meetings before qualification
An SDR/BDR can create activity while the founder remains buried in unsuitable demonstrations. Define accepted opportunities, required context, and disqualifiers before expanding prospecting. Review rejected handoffs together so the role learns what genuine buying potential looks like.
Selling beyond technical or delivery reality
Promises about integrations, response coverage, compliance, or evidence can create obligations the company cannot meet. Give sales an approved claims library and a clear escalation route. Keep a visible record of commitments through the customer handoff.
Treating the first hire as a founder replacement
The founder still owns market learning, positioning, and difficult product trade-offs. Stay involved in coaching and selected customer conversations. Delegate a defined motion, not every unresolved commercial decision.
Frequently asked questions
Does the founder really need to close the first customers?
Yes, the founder should own the first commercial decisions and learn directly from real purchases. Advisers or sellers can help, but the founder must understand why customers buy and what the company has promised. There is no universal customer count that proves readiness to delegate.
Should I hire an SDR/BDR or an AE first?
Hire for the demonstrated constraint. An SDR/BDR can help when the founder closes effectively and prospecting is already teachable. A full-cycle AE is often more useful when opportunities exist but discovery, coordination, and commercial follow-through consume the founder's time.
When do we need a sales engineer?
Add one when technical evaluation repeatedly blocks progress or consumes engineering capacity needed for delivery. The role should translate requirements into a credible validation plan, not simply operate a polished demo. The founder or technical team must still define product and security boundaries.
How should we set OTE without much sales history?
Start with explicit assumptions about pipeline, sales cycle, deal economics, and what the role controls. Explain how targets and ramp were constructed and when they will be reviewed. Have the written compensation terms checked for the relevant jurisdiction.
Can partners replace the first sales hire?
Partners can be the primary route to market when they have a clear reason and practical ability to sell your offer. They still need enablement, technical support, account rules, and a commercial owner. A partner agreement alone does not establish demand.
What should count as success after 90 days?
Look for demonstrated competence in discovery, accurate qualification, responsible claims, reliable follow-up, and documented buyer progress. Compare commercial outcomes with the opportunities available and the actual buying cycle. Use the review to decide what the hire can own independently and what support remains necessary.