Sumo Logic just raised $326 million in an upsized IPO. Here's the first ever pitch deck it used to bring investors on board.

Sumo Logic
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 1
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

24
every slide · same image gating as the playbook
01
Slide 1
front_matter
02
transition
03
summarize
05
The slide uses a pie chart to show market segmentation by sub-sector.size_opportunity
Open slide detailBeat · Market SizeLoop · Benchmark Gap
06
Data sourced from a 2008 Forrester survey.establish_context
07
frame_problem
Open slide detailBeat · ProblemLoop · Cost Of Inaction
08
The slide uses a numbered list format overlaid on a downward-pointing arrow graphic.present_solution
Open slide detailBeat · Solution
09
The slide uses a simple layout to map target customers to specific functional use cases.decompose_segments
10
The slide uses a layered architecture diagram to illustrate data flow from sources to business outcomes.present_solution
11
The diagram uses numbered callouts (1-6) to indicate the sequence or components of the platform architecture.present_solution
12
The diagram uses a layered approach to represent the data pipeline.establish_context
13
The slide uses a process flow diagram to show how data moves from a collector to a correlation engine, with a list of pain points alongside.frame_problem
14
The slide uses a numbered list (1, 3) to denote stages in a process flow, though stage 2 is missing.present_solution
15
The diagram shows a split path for data between a database and a log store, leading to a correlation engine, which creates fragmentation.frame_problem
16
The slide uses a layered architecture diagram to explain the technical stack.present_solution
17
The slide uses a process flow diagram to highlight technical and human bottlenecks in log management.frame_problem
18
The slide uses numbered callouts (2, 4, 5, 6) to highlight specific components of the architecture.present_solution
19
The slide uses a numbered list format to map technical features to business outcomes.present_solution
20
The slide uses a vertical comparison framework to highlight the limitations of legacy/on-premise approaches versus the company's cloud-native model.compare_peers
Open slide detailBeat · Competition
21
plan_implementation
22
The table compares internal unit economics against competitor deal sizes (AlertLogic, ArcSight).analyze_data
Open slide detailBeat · Business ModelLoop · Quick Win Big Bet
23
The roadmap uses a matrix structure to map product capabilities against release phases.plan_implementation
24
summarize