The Four Keys to IC Love
Credibility, build-with-users, go where they already are, and radical transparency.
- Difficulty
- Moderate
- Time to result
- ~months to results
- Steps
- 4
- Confidence
- 93%
Step one of Figma's motion — getting individual contributors to love you — decomposes into four concrete workstreams that Figma ran from stealth onward and still runs at scale. They are not sequential phases so much as four things you must be doing at once, and they work because they compound into a relationship the IC will risk their own reputation on.
Origin
Articulated by Claire Butler as her retrospective decomposition of what Figma actually did in 2015-2016 with a team of ten and no marketing budget.
Core principles
- 01Credibility with a technical audience comes from technical substance, never from marketing language.
- 02Users who see their feedback shipped feel ownership of your product.
- 03Early on, they will not come to your space — you must go to theirs.
- 04Transparency is cheap when things go well and load-bearing when they don't.
How to run it
- 1
Establish credibility with technical depth
Publish content your target practitioners could not have written themselves — deep engineering and craft explanations of how you built the product and why you made specific design decisions.
Pro tip Get your engineers and designers to write it, not your marketers; hire a practitioner-advocate as your first marketing hire.
Watch out Quality over quantity — Figma published roughly ten posts in six months.
- 2
Build the product with your users
Talk directly to every early user. Put engineers on live support, debug with users in real time, ship their fixes, and then tell them you shipped it.
Pro tip Telling a user 'we fixed the thing you asked for' converts them from user to co-owner of the product.
Watch out None of this scales — do it anyway in the early days, then scale it via a dedicated advocate role.
- 3
Pick the one channel where they already are
Find the pre-existing community for your IC audience and go all-in on it rather than building your own space they must come to. For Figma this was the design community on Twitter — one channel, focused.
Pro tip Passive following is the point: a channel lets them follow you for a year before switching tools, building confidence over time.
Watch out Do not build a Slack community or forum early — they don't know you and don't care about you yet.
- 4
Be transparent, especially when it hurts
Publish public postmortems for outages with the real technical cause. Don't hide behind the brand handle — have named humans, including the CTO and founder, answer users directly.
Pro tip Real people, not brand accounts, are what build the relationship.
Watch out This gets harder, not easier, at scale — that is exactly when the temptation to hide behind the brand peaks.
In the wild
In the early days Figma installed Intercom and everyone — Dylan, Claire, engineers — sat in it all day. A user would report a bug in chat and an engineer would QA it live with them and immediately fix it.
→ Users felt personal ownership of the tool ('I asked them to do this, they did it'), which converted early users into passionate advocates.
On the day the Adobe acquisition was announced, Figma initially just retweeted Dylan. Rajiv on the team argued they had to talk to users directly and not hide behind the brand. The next day they held an open Twitter Space with Dylan, Sho, Rajiv and Tom where users could ask anything.
→ Butler cites this as the moment sentiment began to turn and users gave Figma a chance — transparency held at the highest-stakes possible moment.
Common mistakes
Marketing at a technical audience
Designers and engineers have an extremely high BS meter. Buzzwords like efficiency and collaboration make them tune out; they want to hear how the technical features actually work.
Spreading across every channel at once
As the only marketer you cannot do everything. Figma focused on exactly one channel where the audience already lived, and won it.
Talking about your differentiator instead of their work
Nobody wants to talk about collaboration. They want the tool to work. Lead with the craft of the tool; the collaboration is what makes them stay, not what makes them try.
Is it for you?
Best for
A first or only marketing hire at a pre-launch or early-stage technical product who has to decide where to spend limited cycles
Not ideal for
Companies with a non-technical, low-engagement user base or a genuine top-down enterprise sale
From the transcript
“designers don't want to hear from marketers they don't want to be marketed to”
“and so like that was one example we all did support back in that day and the engineers would talk talk to users directly get…”
“in the early days especially like they're not going to come to your space like they don't know you they don't care about you”
“we did a public postmortem and we always do that if something happens or something goes wrong”
From the episode
An inside look at Figma’s unique GTM motion
Claire Butler (first GTM hire)