Ross C.

Senior Account Executive

DuploCloud

Account ExecutiveOutbound HeavyEnterpriseOn-site📍 Washington, DC
Deal Size: $75K-300K ACV
Sales Cycle: 4-8 months
Posted by Ross C.•

Overview

You're selling DuploCloud's AI DevOps platform to engineering leaders, DevOps directors, and VPs of Infrastructure at companies managing complex cloud environments. The product automates infrastructure-as-code, streamlines DevOps workflows, and helps with compliance—think of it as a layer that sits between engineers and their AWS/Azure/GCP accounts. You're based in DC, so expect a lot of government contractors, healthcare systems, and regulated financial services companies.


Role Snapshot

AspectDetails
Role TypeFull-cycle AE (prospecting to close)
Sales MotionOutbound-heavy with some inbound from content
Deal ComplexityEnterprise consultative
Sales Cycle4-8 months
Deal Size$75K-300K ACV
Quota (est.)$800K-1M annually

Company Context

Stage: Series B-ish (164 employees, no funding data available but size suggests growth stage)

Size: 164 employees

Growth: Hiring a senior AE in DC suggests geographic expansion and focus on regulated industries

Market Position: Competing in a crowded DevOps/infrastructure automation space against bigger players and open-source alternatives


GTM Reality

Pipeline Sources:

  • 30% Inbound - mostly content marketing leads (engineering blogs, webinars). Quality varies widely—some are individual contributors researching tools, not buyers
  • 60% Outbound - you're building your own pipeline through cold outreach, LinkedIn, and working your network in the DC tech scene
  • 10% Partners/Referrals - some AWS/Azure partnership plays, occasional referrals from existing customers

SDR/AE Structure: Likely self-sourcing or limited SDR support at this stage. The post mentions "roll up your sleeves" which usually means you're doing your own prospecting.

SE Support: Probably shared SE pool—technical product that requires demos and POCs, but at 164 people they won't have dedicated SEs for every AE.


Competitive Landscape

Main Competitors: Terraform Enterprise/Cloud, AWS Control Tower, Pulumi, Env0, Spacelift, plus internal DevOps teams who built their own solutions

How They Differentiate: AI-powered automation layer that's supposed to be easier than writing infrastructure-as-code from scratch. Focus on compliance and security for regulated industries. Lower learning curve than pure IaC tools.

Common Objections:

  • "We already have Terraform/our own IaC setup"
  • "Another vendor in our stack to manage"
  • "Our team can build this internally"
  • "Lock-in concerns—what happens if we outgrow you?"

Win Themes: Speed to value, compliance automation for regulated industries, reducing DevOps backlog without hiring more engineers


What You'll Actually Do

Time Breakdown

Prospecting (35%) | Active Deals (40%) | Internal/Admin (25%)

Key Activities

  • Cold Outreach: You're identifying companies with 200-2000 employees that have complex cloud infrastructure. This means LinkedIn research, finding engineering leaders, sending personalized emails about their tech stack. Most don't respond. You're trying to book 8-12 discovery calls per month.

  • Technical Discovery: Your calls are with DevOps directors, VPs of Engineering, sometimes CTOs. They're technical—they'll ask how you handle Kubernetes clusters, multi-cloud deployments, GitOps workflows. You need to speak their language or bring your SE in early. These conversations take 45-60 minutes.

  • POC Management: Deals require proof-of-concept periods where their team tests the platform on real infrastructure. You're coordinating between their engineers, your SE, and your product team. POCs often extend beyond the planned timeline. You're chasing updates and trying to create urgency.

  • Multi-Threading: You're selling to engineering, but legal needs to review vendor terms, security teams need SOC2/compliance docs, procurement negotiates pricing. You're managing 5-8 stakeholders per deal. Getting everyone aligned takes months. Many deals slip quarters because someone new enters the buying committee.


The Honest Reality

What's Hard

  • Long, unpredictable cycles: Deals that look close in month 3 suddenly go quiet for 6 weeks. Budget gets frozen, projects get reprioritized, champions leave the company. Your forecast accuracy will be terrible for your first year.

  • Technical credibility bar: You're selling to people who can code. If you can't have a coherent conversation about infrastructure automation, CI/CD pipelines, and compliance frameworks, you'll lose credibility fast. Expect to study a lot.

  • Build vs buy objections: Every prospect has engineers who think they can build this internally. You're constantly justifying why they should buy your platform instead of just using Terraform and hiring another DevOps engineer.

  • DC market specifics: Government contractors move slowly. Healthcare and finance have long security review processes. You'll wait 6+ weeks just for security questionnaires to come back. FedRAMP compliance comes up a lot—if DuploCloud doesn't have it yet, you'll lose federal deals.

What Success Looks Like

  • Closing 4-6 deals per year in the $75K-200K range
  • Building a DC network of DevOps leaders and CTOs who take your calls
  • Getting good at running technical discovery and articulating value in engineering terms
  • 50%+ of your pipeline coming from your own outbound efforts and referrals

Who You're Selling To

Primary Buyers:

  • VP Engineering / CTO (budget owner, final decision maker)
  • Director of DevOps / Platform Engineering (day-to-day user, technical evaluator)
  • CISO / Security Director (compliance approver, especially in regulated industries)

What They Care About:

  • Reducing time engineers spend on infrastructure vs. features
  • Compliance automation (SOC2, HIPAA, PCI if applicable)
  • Multi-cloud or cloud migration support
  • Not adding more complexity to their stack
  • Ability to customize and integrate with existing tools
  • Team's ability to learn and adopt the platform without months of training

Requirements

  • 5+ years full-cycle AE experience selling technical B2B software
  • Proven track record selling to engineering and technical buyers (DevOps, infrastructure, platform teams)
  • Comfortable with enterprise deal cycles (4-6+ months) and multi-stakeholder selling
  • Experience managing POCs and technical evaluations
  • Ability to learn technical concepts quickly—you don't need to code, but you need to understand cloud infrastructure, containers, IaC concepts
  • DC area presence and willingness to do in-person meetings with local prospects
  • Comfortable building your own pipeline through outbound prospecting
  • Experience in regulated industries (gov contractors, healthcare, finance) is a plus