BDR - State and Local Government (West)

Overview

You prospect into state and local government agencies across the Western US to generate pipeline for Adobe's Digital Experience Platform (AEP) sales team. Your targets are IT directors, digital service leads, and department heads at agencies like DMVs, public health departments, parks & rec, and city governments. You're trying to get them interested in modernizing constituent-facing digital experiences (websites, portals, mobile apps) using Adobe's enterprise marketing and web content management tools.

Role Snapshot

Company Context

Stage: Public (NASDAQ: ADBE), $19B+ annual revenue

Size: 41,000+ employees globally

Growth: Mature but still expanding in public sector; government is a strategic growth vertical

Market Position: Leader in creative tools, strong position in digital experience/marketing automation competing against Sitecore, Acquia, Salesforce Marketing Cloud

GTM Reality

Pipeline Sources:

• 70% Outbound - You're cold calling agencies from target account lists, researching budget cycles and RFP calendars
• 20% Event/Webinar Follow-up - Adobe runs government-focused events; you work warm leads from attendee lists
• 10% Inbound - Occasional web form fills from .gov domains, usually very early stage research

SDR/AE Structure: Dedicated BDR team supporting Public Sector AEs. You hand off qualified opps, AE takes discovery through close.

SE Support: AEs have dedicated Solutions Consultants for demos and technical validation. You don't typically involve them until after handoff.

Competitive Landscape

Main Competitors: Sitecore, Acquia/Drupal, Salesforce Marketing Cloud, OpenText, occasional open-source implementations

How They Differentiate: Adobe has brand recognition and integration across Creative Cloud + Document Cloud + Experience Cloud. Positioning is "end-to-end" digital experience vs point solutions.

Common Objections:

• "We already have a CMS" (WordPress, Drupal)
• "That's expensive for our budget cycle"
• "We need to go through formal procurement/RFP process"
• "Security/compliance review will take 6 months"

Win Themes: Integration with existing Adobe tools many agencies already use, scalability, accessibility compliance (WCAG), constituent experience improvements (shorter wait times, better self-service)

What You'll Actually Do

Time Breakdown

Cold Outreach (50%) | Research/List Building (25%) | Internal Syncs (15%) | Follow-ups (10%)

Key Activities

• Cold Calling Government Offices: You're making 40-50 calls/day to agency switchboards, asking for IT directors or digital service leads. Lots of gatekeepers, voicemails, and "send an email to this procurement address." Maybe 2-3 actual conversations per day.

• Email Campaigns: You work templated sequences but personalize with agency-specific references (recent news, budget announcements, constituent pain points you found). Government email filters are aggressive; open rates are low.

• Research & List Building: You dig through agency websites, budget documents, RFP databases (GovWin, SAM.gov) to find agencies with digital transformation initiatives or expiring contracts. You're looking for signals they have money and a project.

• Meeting Qualification Calls: When someone bites, you run a 15-20 minute discovery to confirm budget authority, timeline, and whether they're actually evaluating solutions (vs just gathering info). You're trying to determine if it's worth your AE's time.

The Honest Reality

What's Hard

• Government Moves Slowly: People don't respond quickly. Budget cycles are annual. Even "urgent" projects take months to get procurement approval. You'll have prospects go dark for 8 weeks and resurface saying "we're still interested."

• Gatekeepers Everywhere: You rarely get through to decision-makers on first try. Receptionists won't transfer you without knowing what vendor you're with. Emails go to generic inboxes. You'll leave 10+ voicemails before getting a callback.

• Everyone Wants to Compare Options: Government buyers need to show due diligence. Even if they like Adobe, they'll tell you they're evaluating 3-4 vendors and probably need to issue an RFP. Your job is to get Adobe included, but it's rarely a short conversation.

• Rejection is Constant: Most calls go nowhere. Most emails get ignored. You need thick skin and discipline to keep dialing when you've had 30 straight voicemails.

What Success Looks Like

• 8-12 qualified meetings per month that your manager and the AE agree are real opportunities (not tire-kickers)
• 30-40% of your meetings convert to pipeline opportunities the AE accepts and works
• You identify budget cycles and timing so AEs can plan their forecasts around when deals might actually close

Who You're Selling To

Primary Buyers:

• IT Directors / CIOs at state/county/city agencies
• Digital Service Directors / Chief Digital Officers
• Department-level leaders (Health & Human Services, Transportation, etc.) with constituent-facing digital needs
• Procurement officers (you need to navigate them, but they're not economic buyers)

What They Care About:

• Constituent Experience: Can residents renew licenses online? File permits? Access services without calling or visiting in person?
• Accessibility Compliance: WCAG 2.1 AA compliance is often legally required
• Security/FedRAMP: Government data security requirements, existing vendor approval lists
• Budget Certainty: They need predictable multi-year costs for procurement approval
• Existing Infrastructure: What integrates with their current systems (often legacy and painful)

Requirements

• 1-2 years in tech sales or BDR role (government experience helpful but not required; they'll train on public sector nuances)
• Comfort with cold calling and rejection - this is a grind, you need resilience
• Research skills - you have to dig through government websites, budget docs, and procurement databases to find good targets
• Understanding of enterprise sales - government deals are complex, multi-stakeholder, and slow; you need patience
• Location: West Coast or able to work from Tysons, VA office