Business Development Representative (BDR)

Overview

You run targeted outbound campaigns into strategic enterprise accounts—think Fortune 1000, large financial services firms, healthcare systems, manufacturing conglomerates. Unlike SDRs who work volume-based prospecting, you're assigned 50-100 named accounts and your job is to multi-thread into them: map the org chart, find multiple stakeholders (CISO, IT Director, Business Unit leaders), and orchestrate introductions for your aligned AE. You're building account plans, not just hitting dial metrics.

Role Snapshot

Company Context

Stage: Late-stage private (likely Series F+, multi-billion valuation)

Size: 3,285 employees globally

Growth: New VP of Global Sales Development building out both SDR and BDR functions—emphasis on enterprise/strategic accounts

Market Position: Competing head-to-head with Zscaler and Palo Alto for large enterprise SASE deals. Netskope is recognized by Gartner/Forrester but needs to displace entrenched incumbents.

GTM Reality

Pipeline Sources:

• 30% Inbound/Warm - Some accounts have engaged with marketing (webinar, analyst report download) or had past conversations. You're following up and re-engaging dormant opps.
• 65% Outbound - You're building relationships from scratch in accounts that may not know Netskope exists
• 5% Executive Referrals - Occasionally your AE or RVP will open a door via their network and you execute the follow-up

SDR/AE Structure: You're paired 1:1 or 1:2 with Enterprise AEs. You work together on account strategy—they may ask you to target specific personas or divisions within a large account.

SE Support: SEs join qualified meetings, but you're also coordinating with SEs on custom research/deck tailoring for strategic accounts.

Competitive Landscape

Main Competitors: Zscaler (biggest), Palo Alto Networks Prisma SASE, Cisco (legacy VPN/firewall replacement), Cloudflare

How They Differentiate: Netskope emphasizes data-centric security (better DLP/CASB than Zscaler), inline vs API approach, and granular policy controls. In large enterprises, they position as "the platform security teams can actually manage."

Common Objections: "We standardized on Zscaler 2 years ago", "Too risky to rip and replace mid-contract", "Need 6-month POC to validate", "Budget locked until next fiscal year"

Win Themes: Security incidents creating urgency (breaches, audits), M&A integration requiring stack consolidation, cloud migration projects, dissatisfaction with current vendor (performance, support, complexity)

What You'll Actually Do

Time Breakdown

Account Research (25%) | Multi-Channel Outreach (35%) | Internal Collaboration (25%) | Meetings/Demos (15%)

Key Activities

• Account Mapping: Use LinkedIn Sales Navigator, ZoomInfo, 6sense to build org charts of your named accounts. Identify the CISO, security directors, cloud architects, business unit CIOs. Map reporting structures and find champions.
• Multi-Threading Outreach: Instead of spray-and-pray emails, you're running coordinated campaigns: call the CISO, email the Director, LinkedIn message the architect, send a personalized video to the VP—all in the same week. Goal is to create multiple entry points.
• AE Partnership: Weekly (or daily) syncs with your aligned AE on account strategy. They'll say "We need to get into XYZ Bank's retail division" and you build the plan. You're also joining some of their discovery calls to understand what resonates.
• Executive Plays: Occasionally your RVP or CRO will set up a dinner or executive briefing with a target account. You handle all the pre-work: research the attendees, prep talk tracks, coordinate logistics, and execute follow-up.

The Honest Reality

What's Hard

• Slow feedback loops: You're working 50 accounts. Some won't engage for 6 months. You plant seeds, send value (analyst reports, security frameworks), and wait. It's not instant gratification like SDR volume metrics.
• Politics and complexity: Large enterprises have 5-10 stakeholders in a security decision. You find a champion in IT, but then Finance, Legal, and Compliance get involved. Your contact ghosts because they're navigating internal politics you can't see.
• Incumbent inertia: These accounts spent $5M+ on Zscaler or Palo Alto over 3 years. Even if Netskope is better, the switching cost (technical migration, retraining, contract termination) is massive. You're often planting seeds for 2025 budget cycles.
• High bar for "qualified": Your AE won't accept a meeting with a random analyst who has no budget authority. You need to book with decision-makers or confirmed technical evaluators. That means more rejection and longer prospecting cycles.

What Success Looks Like

• 8-15 qualified meetings per month with director+ level stakeholders who have active projects or budget
• 3-5 of your meetings convert to Stage 2 opportunities (technical evaluation or POC) within 60 days
• Top performers become account strategists—AEs rely on them to map the buying committee, prep for executive calls, and navigate deal blockers
• Multi-year impact: You book a meeting in Q1 that becomes a $2M deal in Q4. Recognition comes when the deal closes, not when you book the meeting.

Who You're Selling To

Primary Buyers:

• CISO / VP of Infosec (ultimate budget owner, risk owner—hardest to reach)
• Director of Security Operations / Cloud Security Lead (technical evaluator, day-to-day operator)
• Enterprise Architect / Head of Infrastructure (integration and performance gatekeeper)
• Business Unit CIOs (in large orgs, individual divisions may have their own security budgets)

What They Care About:

• Risk reduction: Board is asking about zero-trust strategy, ransomware protection, third-party risk. They need to show progress.
• Consolidation: Security team is managing 40+ tools. Leadership wants to reduce vendors and simplify operations.
• Cloud-first strategy: Legacy VPNs don't work for remote workforce or cloud apps. They need modern architecture.
• Proof: Not buying on a sales pitch—need POC, reference calls with similar companies, detailed security architecture review.
• Total cost of ownership: $1M+ decisions require business case, ROI model, multi-year cost comparison.

Requirements

• 2-4 years in B2B SaaS sales or sales development (preferably enterprise software, cybersecurity, or infrastructure)
• Account-based selling experience: You've worked strategic accounts, not just volume prospecting
• Executive communication skills: Comfortable researching and reaching out to VP/C-level personas with tailored messaging
• Collaboration with AEs: You've worked closely with quota-carrying reps and understand deal strategy, not just meeting setting
• Persistence and patience: Some of your best accounts won't engage for 3-6 months. You need to stay organized and not give up.
• Technical curiosity: You don't need to be an engineer, but you should understand enterprise IT concepts (VPNs, firewalls, cloud security, SASE) enough to have credible conversations.