2023 Investor Session Product Update

MongoDB
arc beats above · slides in the middle · loops below · scroll → 3 LOOPS
SETUP TENSION ANALYSIS EVIDENCE RESOLUTION APPENDIX
HOVER FOR DETAILS · CLICK A SLIDE FOR FULLSCREEN · STEP 5
No image bound to this slide. Wire up imgproxy to display the rendered slide JPEG.

Deck intelligence map

5
coverage by narrative range · generated from this deck JSON

Slide inventory

74
every slide · same image gating as the playbook
01
Slide 1
front_matter
03
establish_context
Open slide detailBeat · Thesis Headline
04
The chart displays steady year-over-year growth in market size.size_opportunity
Open slide detailBeat · Market Sizing
05
transition
06
The slide uses a simple bar-like diagram to represent different software categories (CRM, ERP, HRIS, etc.) and highlights the binary nature of competition.frame_problem
07
The visual uses a grid of rectangles to represent workloads, with one highlighted, connected to the text.frame_problem
08
The chart uses a simple area representation to illustrate the initial phase of a customer journey.present_framework
09
The chart uses an area shape to represent growth, emphasizing the cumulative nature of ARR.present_framework
10
The chart uses a color gradient to represent five distinct workloads, showing cumulative growth.illustrate_case
11
summarize
12
summarize
13
present_solution
Open slide detailBeat · Initiative List
14
transition
Open slide detailBeat · Initiative List
15
summarize
Open slide detailBeat · Key Messages
16
frame_problem
Open slide detailBeat · Key Messages
17
The diagram is a classic Entity-Relationship (ER) model, often used to represent the rigidity of relational schemas.frame_problem
Open slide detailBeat · Problem StatementLoop · Cost Of Inaction
18
The diagram shows a 'spaghetti' architecture of multiple databases, caching layers, and ETL pipelines.frame_problem
Open slide detailBeat · Problem StatementLoop · Cost Of Inaction
19
transition
Open slide detailBeat · Problem StatementLoop · Cost Of Inaction
20
The slide uses a simple process flow to break down the migration complexity.frame_problem
Open slide detailBeat · Problem StatementLoop · Cost Of Inaction
21
The slide uses a simple three-column layout to define the necessary components for a successful modernization strategy.present_framework
22
summarize
23
The slide uses a three-column layout to categorize migration components.present_framework
24
illustrate_case
25
present_solution
27
transition
28
present_solution
29
establish_context
30
The slide uses a diagram to illustrate the 'before' state of a typical architecture, highlighting three key pain points: developer productivity, architectural cframe_problem
31
present_solution
32
illustrate_case
33
The slide uses a split-screen layout with a dark left side for branding/announcement and a white right side for key benefits.summarize
34
prioritize
35
frame_problem
36
frame_problem
37
transition
38
Uses a 2x2 matrix framework to position MongoDB's 'Queryable Encryption' as a superior solution compared to standard databases and client-side field-level encrypresent_framework
39
The slide uses a split-screen layout with a dark left panel for the announcement and a white right panel for key benefits.summarize
40
present_solution
41
The slide uses a three-column layout to categorize strategic initiatives.present_solution
42
establish_context
43
The slide uses a simple linear flow diagram to illustrate the relationship between streaming transport, processing, and databases.present_framework
44
frame_problem
45
present_solution
46
summarize
47
front_matter
Open slide detailLoop · Why Now
48
summarize
Open slide detailLoop · Why Now
49
summarize
Open slide detailLoop · Why Now
50
establish_context
Open slide detailLoop · Why Now
51
The slide uses bubble sizes to represent growth over time, with a timeline axis at the bottom.establish_context
Open slide detailLoop · Why Now
52
summarize
Open slide detailLoop · Why Now
53
The chart uses a simple bar representation to illustrate market expansion over a 10-year period.size_opportunity
Open slide detailLoop · Why Now
54
summarize
Open slide detailLoop · Why Now
55
summarize
56
transition
Open slide detailLoop · Jobs To Be Done
57
The slide uses a 'problem-solution' framing by aligning four specific AI app needs with four corresponding MongoDB strengths.frame_problem
Open slide detailLoop · Jobs To Be Done
58
summarize
Open slide detailLoop · Jobs To Be Done
59
The slide contains no text other than the company names within the logos themselves.other
Open slide detailLoop · Jobs To Be Done
60
summarize
61
The slide uses a simple process flow diagram to explain the concept of vector embeddings.present_framework
62
The slide illustrates the concept of vector embeddings in machine learning.present_framework
63
The slide uses visual grouping to represent data classification.present_framework
64
present_solution
65
The diagram illustrates a RAG (Retrieval-Augmented Generation) architecture.present_framework
66
summarize
67
The diagram depicts a RAG (Retrieval-Augmented Generation) architecture.present_framework
68
summarize
69
summarize
70
The slide uses a simple process flow to break down the migration complexity.frame_problem
71
summarize
72
transition
73
present_solution
74
summarize