Figma
Featuring Dylan Field, Evan Wallace
Adobe owned design software for decades. When Dylan Field and Evan Wallace founded Figma in 2012, they did not try to out-Photoshop Photoshop. They bet design should work like a Google Doc: browser-based, real-time, multiplayer. At the time, files were saved locally, emailed as attachments, and opened by one person at a time. Figma spread laterally through teams until developers and PMs who were never the target customers lived in it daily, and Adobe eventually moved to buy it for roughly $20 billion.
This case sharpens how a challenger picks its point of attack against an entrenched incumbent. Feature parity is a losing game; the real opening is somewhere else entirely. Open the app to identify the most painful, most collaborative moment in your customer's workflow, and decide whether to own it.
Frequently asked questions
What is the Figma vs Adobe case study about?
The Figma case is about how a challenger beats an entrenched incumbent by changing the point of attack instead of chasing feature parity. Adobe owned design software for decades, but when Dylan Field and Evan Wallace founded Figma in 2012, they did not try to out-Photoshop Photoshop. They bet design should work like a Google Doc: browser-based, real-time, and multiplayer.
How much did Adobe agree to pay to acquire Figma?
Adobe moved to buy Figma for roughly $20 billion. Figma had spread laterally through teams until developers and product managers who were never the original target customers lived in it daily. That collaborative footprint is what made it worth so much to the incumbent.
Why did Figma's browser-based, multiplayer approach work against Adobe?
It worked because Figma attacked the most painful, collaborative moment in the design workflow rather than competing on raw features. At the time, files were saved locally, emailed as attachments, and opened by one person at a time. Real-time multiplayer editing in the browser made that pain disappear and pulled in whole teams.
What can founders learn from the Figma case study?
The lesson is that feature parity against an incumbent is a losing game; the real opening is the most painful, most collaborative moment in your customer's workflow. Identify that moment and decide whether to own it. CaseBook turns this into a move you apply to your own company, with an AI coach that reads your answer.