MongoDB Software / SaaS global

MongoDB

Sales Automation

MongoDB needed to stop sales reps from spending 4 to 6 hours per account or deal cycle manually stitching together customer context from Salesforce, email, meeting transcripts, and documents before they could plan outreach or prepare for meetings.

Holly currently runs on 30 agents.
MongoDB account executives spent an average of 4 to 6 hours on administrative work, per account/deal cycle.
Reps who have used Holly have seen an approximate 95% reduction in the time it takes to research and generate outbound prospecting lists.

Reported impact

Business outcome

MongoDB cut outbound prospecting research time by about 95%, reduced meeting and outreach preparation from hours to minutes, and created a single agentic interface that is rolling out across sales, account development, commercial growth, and solutions architecture teams.

  • Productivity Improvement

Solution

MongoDB built Holly, an internal AI workspace, on Atlas Agent Engine so go-to-market teams could work from one governed system of action instead of hopping across disconnected sales tools. Atlas Agent Engine supplies the production runtime, memory, security, identity, orchestration, state, observability, and lifecycle controls for Holly's agents. Holly connects business systems including Salesforce, Google Calendar, Google Drive, Zoom, and Salesloft, then uses that context to generate account and opportunity briefs, highlight unanswered discovery questions, capture insights from meeting transcripts, and update CRM records after conversations. Rather than treating prompts as generic research requests, the workspace grounds each task in MongoDB-specific sales methodology and account context, turning fragmented prep and follow-up work into a single agent-driven workflow.

Data flow

Customer and account context from Salesforce, Google Calendar, Google Drive, Zoom, and Salesloft is brought into Holly through Atlas Agent Engine, where agents synthesize the information into meeting briefs, discovery prompts, research outputs, and CRM updates for MongoDB's sales teams.

Solution architecture

1 components · 1 layer
  1. Orchestration
    • Atlas Agent Engine Runs Holly's production agents and provides the runtime, memory, identity, security, orchestration, state, observability, and lifecycle controls behind the workspace.

Architecture clues

  • Atlas Agent Engine provides runtime, memory, security, identity, orchestration, state, observability, and lifecycle management.
  • Holly grounds responses in MongoDB-specific business context instead of using generic AI outputs.
  • MongoDB designed the architecture to scale from 30 agents to potentially thousands.
  • The workspace supports meeting preparation, transcript capture, account planning, outreach research, and Salesforce updates.

Evidence from the source

“Atlas Agent Engine provides the foundation for operating Holly's agents in production, including runtime, memory, security, identity, orchestration, state, observability, and lifecycle management.”
“Holly also connects a number of systems—including Salesforce, Google Calendar and Drive, Zoom, and Salesloft—and brings their information and capabilities into a shared workspace.”
“MongoDB account executives spent an average of 4 to 6 hours on administrative work, per account/deal cycle.”
“Powered by Atlas Agent Engine, Holly—MongoDB's internal AI workspace—cuts sales prospecting research time by 95%.”
Transparency Evidence & methodology 100/100 reference value · 89% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value100/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    2 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence89%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    4 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. MongoDB

    MongoDB customer story

    First-party
    https://www.mongodb.com/solutions/customer-case-studies/holly
    Source type
    Vendor-published customer story
    Published
    Sep 30, 2026
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

  • Published on source page Sep 30, 2026 · MongoDB · First-party
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.