The Bottom-Up Fit Checklist
Four market conditions plus one leadership condition that decide whether an IC-led motion will work.
- Difficulty
- Easy
- Time to result
- ~days to results
- Steps
- 5
- Confidence
- 88%
Butler is explicit that the Figma motion is not universal. She names the conditions that make it much more likely to work: a technical IC audience who cares deeply about their craft, who get standalone value from the tool, who already have a community you can reach them in, and whose role naturally connects them to many other people in the org. On the team side, you need an executive who genuinely believes in the model and will defend it against metrics pressure.
Origin
Claire Butler's own prerequisites analysis, formed while trying to replicate Figma's motion for new products (FigJam, Dev Mode) with new audiences, where she found the assumptions did not all carry over.
Core principles
- 01Craft obsession is the fuel: designers and engineers care about their tools; most professionals don't.
- 02Single-player value must exist so the IC can build confidence alone before risking advocacy.
- 03An existing community is a distribution channel you don't have to build.
- 04The IC must be structurally collaborative for them to be a super-spreader.
- 05Structural advantages coexist with real disadvantages — Figma also had to convince designers to abandon their tools and to work collaboratively, both of which they hated.
How to run it
- 1
Test for a technical, craft-obsessed audience
Ask whether your ICs care deeply about their tools and want to learn the craft in the best way possible. Designers and engineers do; many roles are indifferent about switching tools.
Pro tip The tell is time-in-tool: eight hours a day breeds deep passion about the tool itself.
Watch out If your audience would shrug at being moved from one tool to another, the love-driven motion will not fire.
- 2
Test for standalone single-player value
Confirm the IC gets significant value alone, without collaborators. That is what lets them learn it, build confidence, and only then spread it.
Pro tip It also gives you something to talk about that isn't collaboration — because nobody wants to talk about collaboration.
Watch out Products useless alone (e.g. a chat tool with one user) cannot run this playbook unmodified.
- 3
Test for an existing community
Check whether your target audience already gathers somewhere and shares best practices — a channel you can enter rather than construct.
Watch out No community means you must build attention from zero, dramatically increasing the cost.
- 4
Test for connection points inside the org
Verify that the IC's role naturally puts them in contact with many other people, so spreading is a byproduct of doing their job.
Pro tip Designers need comments and feedback from PMs, engineers and stakeholders — collaboration is structurally built into their work.
- 5
Test for a believing executive
Confirm you have a leader who believes in the model and can trust intuition and signal over immediate metrics — and will protect the motion as the company scales and top-down pressure arrives.
Pro tip Butler calls this the single most important prerequisite; at Figma it was Dylan Field.
Watch out Without executive belief, the motion dies the first time someone asks for its ROI attribution.
In the wild
The motion looks inevitable in hindsight, but Figma had to convince designers to switch tools (very hard) and to work collaboratively at all — when Figma launched on Designer News, the first response was effectively 'if this is the future of design, I'm changing careers,' because designers wanted to work alone and present when ready.
→ The bottom-up motion had to overcome a cultural shift, not just a product comparison — evidence that structural fit is necessary but not sufficient.
Butler explicitly tested her own prerequisites when Figma launched new products for new audiences — FigJam for a broader audience and Dev Mode for developers — asking whether the same IC-led motion would carry over.
→ She concluded there are no absolute requirements but clear enablers, and treats the checklist as a likelihood test rather than a gate.
Common mistakes
Assuming any B2B SaaS can run this playbook
The motion depends on craft-obsessed technical ICs who get standalone value and already congregate somewhere. Missing those, the same tactics produce nothing.
Attributing Figma's success purely to structural advantages
People forget the disadvantages — tool-switching inertia and outright cultural hostility to collaborative design. Fit does not remove the work.
Is it for you?
Best for
Founders and GTM leaders deciding whether to bet on a bottom-up, IC-led motion or a traditional top-down enterprise sale
Not ideal for
Teams that have already validated a bottom-up motion and simply need execution tactics
From the transcript
“it really helps if people are Technical and have this technical audience of people who really care about the craft”
“another thing that helps is that you have a community that exists within the”
“that core I see audience has a lot of connection points within the organization like designers are so collaborative”
“the most important thing there is that you have an executive and a leader who believes in”
From the episode
An inside look at Figma’s unique GTM motion
Claire Butler (first GTM hire)