Erin Maksimow

Business Development Representative (BDR)

Salesforce

BDROutbound HeavyConsultativeOn-site📍 McLean, VA
Deal Size: N/A (feeds AE pipeline of $50K-500K+ ACVs)
Sales Cycle: N/A (BDR books meetings, doesn't close deals)
Posted by Erin Maksimow

Overview

You cold call and email government agency contacts and federal contractors to book discovery meetings for Salesforce AEs. You're selling the #1 CRM platform, which means high name recognition but also means prospects have already heard the pitch or are already using it. Most of your day is outbound prospecting in a quota-driven environment.


Role Snapshot

AspectDetails
Role TypeOutbound BDR (meeting setter)
Sales MotionOutbound-heavy (70-80% cold outreach)
Deal ComplexityN/A (you book meetings, don't close deals)
Sales CycleN/A (you hand off after qualification)
Deal SizeN/A (AEs close $50K-500K+ deals)
Quota (est.)15-25 qualified meetings per month

Company Context

Stage: Public (NYSE: CRM)

Size: 87,725 employees globally

Growth: Mature company, steady hiring in BDR roles as feeder for AE pipeline

Market Position: Market leader in CRM, competing on platform capabilities and ecosystem, not market education


GTM Reality

Pipeline Sources:

  • 20-30% Inbound - Marketing events, webinars, website form fills (highly variable quality, often existing customers or tire-kickers)
  • 70-80% Outbound - Cold calling, email sequences, LinkedIn outreach to assigned territory/accounts
  • <5% Referrals - Occasionally from existing customers or partners

BDR/AE Structure: Dedicated BDR team feeding a pod of 4-6 AEs. You don't carry deals yourself.

SE Support: SEs support AEs after handoff, not BDRs.


Competitive Landscape

Main Competitors: Microsoft Dynamics 365, Oracle, SAP, ServiceNow (depending on use case)

How They Differentiate: AppExchange ecosystem, Einstein AI, deep integration capabilities, established government compliance (FedRAMP, etc.)

Common Objections: "We already use Salesforce", "Too expensive", "We're locked into Microsoft/Oracle ecosystem", "Implementation takes too long"

Win Themes: Platform vs point solution, ecosystem lock-in, proven at scale in government


What You'll Actually Do

Time Breakdown

Cold calling/emailing (50%) | Research/list building (20%) | Follow-ups (15%) | Internal meetings/training (15%)

Key Activities

  • Cold calling: 50-70 dials per day to government IT directors, program managers, contracting officers. Most don't pick up. You leave voicemails and immediately follow with email.
  • Email sequences: Managing 5-10 email touches per prospect across multiple accounts. A/B testing subject lines. Most don't respond.
  • Account research: Looking up org charts on LinkedIn, finding the right contacts in agencies (not always listed publicly), researching recent contracts or initiatives.
  • Qualification calls: When someone responds, you run a 15-20 min discovery to determine if they're a real opportunity (budget, timeline, pain, authority). You need to hit specific BANT criteria or AEs send it back.
  • CRM hygiene: Logging every call, email, and meeting in Salesforce. Leadership tracks activity metrics closely.
  • Team syncs: Daily standups, weekly pipeline reviews, monthly 1:1s with your manager. There's a lot of coaching and role-playing.

The Honest Reality

What's Hard

  • High rejection rate: 90%+ of your calls go to voicemail or get ignored. When people do pick up, many brush you off quickly. Government contacts are especially hard to reach.
  • Quota pressure: You're measured weekly on meetings booked and pipeline generated. If you have a bad week, everyone knows. There's a leaderboard.
  • Repetitive work: You say essentially the same pitch 60 times a day. The calls start blending together.
  • Government procurement cycles: Even when you book a meeting, deals often stall for 6-12 months due to budget cycles, approval processes, or contract vehicles. You don't benefit from those deals closing since you've moved on.
  • AE feedback loop: Some AEs will tell you a meeting wasn't qualified enough and it doesn't count toward quota. You have to defend your qualification.
  • Name recognition cuts both ways: Everyone knows Salesforce, which means many have already evaluated it, are already customers, or have formed opinions. You're often re-pitching.

What Success Looks Like

  • Hit your monthly meeting quota consistently (15-25 qualified meetings)
  • Generate $X pipeline for your AE pod (tracked but not always within your control)
  • Get promoted to AE within 12-24 months (this team promoted 23 BDRs last year, which is real)
  • Develop a prospecting system that works: knowing which touches convert, which objections to handle, which accounts to prioritize

Who You're Selling To

Primary Buyers:

  • IT Directors/CIOs at federal agencies, state/local government
  • Program managers overseeing citizen services or internal operations
  • Digital transformation leads
  • Federal contractors and systems integrators who deploy Salesforce

What They Care About:

  • FedRAMP compliance and security certifications
  • Integration with existing government systems
  • Citizen experience improvements or internal process efficiency
  • Total cost of ownership (licensing, implementation, training)
  • Vendor track record with government entities

Requirements

  • Bachelor's degree (Salesforce tends to require this for BDR roles)
  • Ability to work onsite in McLean, VA (not remote)
  • Willingness to make 50-70+ calls per day and handle constant rejection
  • Coachability - this is a heavily managed role with daily feedback
  • Comfort with CRM/sales tools (Salesforce, Outreach/SalesLoft, LinkedIn Sales Navigator, ZoomInfo)
  • Goal: promote to AE within 12-24 months (you need to show consistent quota attainment)
  • No prior tech sales experience required, but they want "grit, curiosity, and a get it done attitude" (translation: they want people who won't quit after a few bad weeks)