Account Executive

Overview

You sell Glean's AI search and knowledge management platform to companies with 500-10,000+ employees. Your buyers are typically IT leaders, CIOs, heads of knowledge management, or productivity tools owners who are trying to solve information silos and improve employee efficiency. You're selling in an emerging category where many prospects don't have budget allocated yet and need education on what AI-powered workplace search actually does versus traditional search.

Role Snapshot

Company Context

Stage: Late-stage venture backed (Series D+)

Size: ~1,500 employees

Growth: Aggressive hiring mode, expanding GTM team rapidly based on post language about "keeping up with momentum"

Market Position: Category creator in AI-powered workplace search - competing against traditional enterprise search (Elastic, Coveo) and newer AI tools while also creating new budget category

GTM Reality

Pipeline Sources:

• 40% Inbound - Mix of website demos, content downloads, and word-of-mouth referrals. Quality varies - some are tire-kickers exploring AI tools, others are genuine projects with budget
• 35% Outbound - You're doing account-based prospecting into target accounts, often multi-threading to find the right champion. Expect a lot of education calls with people who don't know they have a search problem
• 25% Expansion/Referrals - Existing customer base is growing, generating some net-new opportunities through referrals and case studies

SDR/AE Structure: Dedicated SDRs for inbound leads and target account prospecting. You'll still need to self-source 30-40% of your pipeline, especially for strategic accounts.

SE Support: Shared Solutions Engineer pool. You get SE support for qualified demos and technical deep-dives, but you handle initial discovery and product overviews solo.

Competitive Landscape

Main Competitors:

• Traditional enterprise search (Elastic, Coveo, Microsoft SharePoint search)
• Point solutions (Notion AI, Confluence, internal wikis)
• "Do nothing" - many orgs don't realize how bad their search problem is

How They Differentiate: AI-native search that understands context and connects across all work apps (Slack, Google Drive, Confluence, etc.). The pitch is unified knowledge discovery versus siloed search within individual tools.

Common Objections:

• "We already have search" (they're comparing to basic search, not understanding the AI component)
• Security and data access concerns (you're indexing everything)
• "We need to see ROI" (hard to quantify productivity gains from better search)
• "Not in this year's budget" (new category = no allocated budget)

Win Themes:

• Concrete time savings ("employees spend 2 hours/day searching for information")
• Cross-app knowledge discovery (reduces tool switching)
• AI assistant functionality (not just search, but answers)
• Executive champion who personally feels the pain of information overload

What You'll Actually Do

Time Breakdown

Active Deals (40%) | Prospecting/Qualifying (30%) | Internal/Admin (30%)

Key Activities

• Discovery Calls: You spend a lot of time diagnosing information management pain - talking to IT, end users, department heads about how they currently search, what breaks, and where knowledge gets lost. Many prospects don't articulate the problem well initially.
• Multi-Threading: Deals require buy-in from IT (security, integration), budget owner (often CIO or COO), and end users (who need to adopt it). You're constantly scheduling calls with different stakeholders and keeping everyone aligned.
• Navigating Security Reviews: Every deal involves detailed security questionnaires, data access discussions, and compliance reviews. You'll coordinate between your SE, security team, and their IT/security team. This adds 4-8 weeks to most cycles.
• Building Business Cases: Prospects need to justify the spend. You're pulling together ROI calculators, usage data from similar customers, and time-savings analyses. Lots of spreadsheet work and custom deck creation.
• Demos and Proof of Concepts: Initial demos are straightforward, but qualified opportunities often require a POC with their actual data. You manage POC scope, timelines, success criteria, and check-ins. POCs take 2-4 weeks and can make or break deals.
• Outbound Account Research: For self-sourced pipeline, you're researching target companies, identifying knowledge-intensive teams (engineering, customer support, professional services), finding champions on LinkedIn, and crafting personalized outreach.

The Honest Reality

What's Hard

• You're often creating budget where none existed. Finance and IT teams push back because "search" sounds like a nice-to-have, not mission-critical. Deals slip quarters waiting for budget approval.
• The category is new enough that you spend considerable time educating prospects on what AI search actually means. Some buyers confuse it with chatbots or basic keyword search.
• Technical evaluation cycles are long. Security reviews, IT architecture discussions, integration scoping - all add time. You'll have deals you think are closing in Q2 that actually close in Q4.
• Multi-stakeholder alignment is messy. IT loves it, end users are lukewarm. Or end users want it, IT has security concerns. Getting everyone on the same page takes work.
• The product is evolving quickly (AI moves fast). Features you demoed last month might work differently now, or new capabilities launched that change your pitch. You need to stay current.
• At hypergrowth companies, internal processes are immature. You might not have clear answers on packaging, deployment options, or contractual edge cases. Expect ambiguity.

What Success Looks Like

• You close 8-12 deals per year at $80-100K ACV each, hitting $900K-1M quota
• Your POC-to-close rate is 60%+ (well-qualified POCs should convert)
• Average sales cycle is 4-5 months (faster is better but don't sacrifice deal quality)
• You maintain 3-4x pipeline coverage (you need $3-4M in pipeline to hit $1M quota)
• Customer references come back to you - successful deployments lead to expansion and referrals

Who You're Selling To

Primary Buyers:

• CIO / VP of IT (budget owner, cares about ROI and employee productivity)
• Head of Knowledge Management / Chief of Staff (process owner, cares about information accessibility)
• VP Engineering / Head of R&D (user champion in knowledge-intensive orgs)

What They Care About:

• Employee time savings and productivity gains (the ROI story)
• Security, compliance, and data governance (who can access what)
• Integration with existing tech stack (Google Workspace, Microsoft 365, Slack, etc.)
• User adoption and change management (will people actually use it?)
• Scalability and performance (works for 1K employees? 10K?)

Requirements

• 3-5 years of B2B SaaS sales experience, ideally selling to IT or productivity tool buyers
• Track record of consultative selling - you need to diagnose problems, not just pitch features
• Comfortable with technical conversations (APIs, SSO, data security, cloud architecture)
• Experience managing 3-6 month sales cycles with multiple stakeholders
• Self-starter mentality - the company is growing fast, processes aren't fully baked, you need to figure things out
• Willingness to do outbound prospecting and build your own pipeline, not just work warm inbound leads
• Ability to handle ambiguity and rapid change (product evolves, GTM strategy shifts, quotas adjust)