Figma Just Filed for IPO and the Numbers Are Unbelievable!

Video ID: f2Hq3XemPBE

YouTube URL: https://www.youtube.com/watch?v=f2Hq3XemPBE

Added At: 23-07-25 11:17:20

Processed: No

Sentiment: -

Categories: Business

Tags: ipo, software, design, sas

Summary

No summary

Transcript

Figma just filed for IPO and the numbers
they revealed are crazy. We're talking
$821 million in revenue last year
growing at 46% annually with a whopping
91% gross margins. That means for every
$100 they make, they keep $91 after
basic costs. And it doesn't stop there.
With about 18% operating margin, they're
sitting on about $1.5 billion in cash
with zero debt. It's insane because
we're talking about a software company
that makes design tools, not some clunky
enterprise solutions. But how how does a
design app make the kind of money most
companies can only dream of? Well, it's
because software doesn't scale like
physical products. Imagine it like this.
If you're selling chairs, every new
customer means building and shipping a
new chair. But with SAS, it's different.
You only need to build it once. Then
whether you have 1,000 users or 10
million, the cost barely changes. And
that's what gives SAS such high margins.
Once you have enough of a user base, the
margins become very high. And Figma is
the perfect example. But even with all
that baked in efficiency, Figma had some
smart product decisions too. Like
instead of stopping at just one design
tool, they started layering other
products on top of it. Like they added
Fig Jam for whiteboarding, dev mode for
engineers, and slides for creating
internal decks. Now, if you think about
it, that's pure genius because this way
Figma is able to increase its revenue by
increasing its revenue per user, not
necessarily by adding new users. And the
numbers show about 76% of Figma
customers now use two or more of their
products, leading to a whopping 132% net
dollar retention. Basically, it's the
amount of money you're making from your
existing customers. And this is what
Peak SAS looks like. Figma worked
because they figured out real-time
collaboration in the browser itself,
something no one else had done