MongoDB Software / SaaS France

Modjo

Sales Automation

Modjo's Atlas-backed conversational-intelligence platform was hitting 100% CPU saturation because inefficient connection handling, unclosed sessions, and large requests were driving performance bottlenecks and unnecessary infrastructure cost.

100% CPU saturation
75% reduction in monthly MongoDB Atlas costs
Currently serving over 400 sales organizations
Within a few hours, CPU usage dropped from 100% to 20%

Reported impact

Business outcome

After minor code changes, Modjo cut CPU usage from 100% to 20%, reduced query targeting from 40,000 to 1, downsized its Atlas cluster from M60 to M30, and lowered monthly Atlas costs by 75%.

  • Cost Reduction
  • Productivity Improvement
  • Scalability

Solution

Modjo uses MongoDB Atlas as the operational database behind its conversational-intelligence platform, which ingests customer-call data from Zoom, Skype, and Google Meet and runs separate transcription and speaker-identification pipelines. Atlas stores orchestration state, logging, and next-step decisions; writes reach Atlas through a custom API built on AWS Lambda and API Gateway while downstream services read directly. As load grew, inefficient connection management, unclosed sessions, and large per-request datasets drove 100% CPU saturation on an oversized cluster. MongoDB Professional Services first reworked schema and indexing, then traced persistent hot spots to per-operation client creation and leaked sessions, guiding code changes that reused a single client and explicitly closed sessions after retrieval.

Data flow

Conversation data from Zoom, Skype, and Google Meet feeds Modjo's transcription and speaker-identification pipelines. Orchestrator services write task states and next-step decisions through AWS Lambda and API Gateway to MongoDB Atlas, while downstream services read Atlas directly to drive analytics and the end-user application.

Solution architecture

2 components · 2 layers
  1. Storage
    • MongoDB Atlas Stores orchestration state, logs, and workflow metadata for Modjo's conversational-intelligence pipelines.
  2. Orchestration
    • MongoDB Professional Services Diagnosed the workload, validated schema changes, and guided the connection and session fixes that resolved the CPU bottleneck.

Architecture clues

  • MongoDB Atlas stores orchestrator state, logging task statuses, and next-step decisions.
  • Separate transcription and speaker-identification pipelines process conversation data.
  • The fix reused a single MongoDB client and explicitly closed database sessions after reads.
  • Writes to Atlas go through a custom API built on Lambda and API Gateway, while reads are direct.

Evidence from the source

Modjo’s solution is designed to process calls using two data science pipelines; one for transcription and one for speaker identification.
Within a few hours, CPU usage dropped from 100% to 20%
Writes to the database are performed via a custom API (Lambda + API Gateway), while reads are direct.
resulted in a 75% reduction in monthly MongoDB Atlas costs
Transparency Evidence & methodology 100/100 reference value · 92% confidence · 2 sources

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
    5 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence92%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability23/25
    11 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 transparency9/10
    2 source references 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

    Modjo customer story

    First-party
    https://www.mongodb.com/solutions/customer-case-studies/modjo
    Source type
    Vendor-published customer story
    Published
    Sep 8, 2025
    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
  2. Modjo

    Legal information

    First-party
    https://www.modjo.ai/en/legals/legal-information

    The legal notice lists "Head office address: 59 Avenue Sainte-Foy, 92200 Neuilly sur Seine," placing the headquarters in France.

    Source type
    Official company website
    Supports
    • Region

Date evidence

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