Figma's roadmap is hiding in its Community tab

Figma's blog tells you what Figma wants you to think about. Its Community tab tells you what Figma is actually building.

That gap is the whole point of a teardown. Announcements are written by people whose job is to shape a narrative. The other surfaces — the ones maintained by engineers, recruiters, lawyers, and support staff — are written by people whose job is to be correct. Correct is more useful than compelling.

Figma is a good subject for this because it has an unusually wide public footprint, and because since going public in mid-2025 it acquired a category of surface most of its competitors don't have. Here's what four of those surfaces give up.

The Community tab is a product-strategy document

Figma Community hosts plugins, widgets, templates, and published files. Most of it is third-party. A slice of it is not — Figma publishes its own plugins and widgets there, and that slice is the interesting one.

When a company builds something first-party into a marketplace it otherwise leaves to the ecosystem, it's telling you one of two things: this capability matters enough to own, or the third-party version wasn't good enough and the gap was costing them. Either way it's a statement about direction that predates any announcement. First-party plugins are cheap to ship and easy to walk back, which is exactly why they show up before the roadmap does.

The third-party side has its own signal, and it's the inverse. Look at what the ecosystem builds repeatedly. Five different plugins solving the same workflow problem means the product doesn't solve it, users need it solved, and there's a queue of evidence sitting in public that it should be. That queue is a decent predictor of what gets absorbed into the core product later — the same pain-mining logic that works on a competitor's community forum, just with install counts attached instead of upvotes.

Watch which categories Figma promotes on the Community landing surface, too. Editorial placement costs nothing to change and reveals what the company currently wants adopted.

Release notes tell you cadence, not just features

Everyone reads a changelog for the features. The features are the least interesting part.

Read it for rhythm instead. How often does Figma ship? Which product lines get entries every week and which go quiet for two months? A surface that was shipping steadily and then stops usually means the team behind it got moved, not that the product got finished. A surface that suddenly triples its entry rate means someone got headcount.

Figma's product line has widened a lot — design, FigJam, Dev Mode, and the newer additions from recent Config cycles. That width is what makes the changelog readable as an org chart. When one line goes dark while another accelerates, you're watching a resource allocation decision that nobody will ever put in a press release. Changelogs leak roadmaps mostly through this kind of negative space — through what stopped, not what shipped.

The other thing worth tracking: how entries are worded. Language that shifts from "we've added" to "generally available" means a beta closed. Language that quietly drops a feature name means something got deprecated without a deprecation notice.

The IPO handed you a surface nobody volunteers

Figma listed publicly in 2025. For a competitive analyst, that's the single biggest change in its surface area — bigger than any product launch.

Public companies file. Quarterly reports, annual reports, earnings calls with analyst Q&A. These documents exist because the law requires them, not because marketing wanted them, and they contain the kind of thing no private company will ever tell you: revenue concentration, segment performance, named risks, and management's own account of what's working. The risk factors section in particular is a company writing down, under legal obligation, what it is most afraid of.

Earnings calls add something rarer still. Analysts ask unscripted questions, and executives answer them in real time. It is the only surface where a competitor's leadership is regularly asked things they'd prefer not to discuss and has to say something anyway.

Most B2B SaaS competitors are private and give you none of this. When one of yours goes public, your intel program should change shape that quarter. It rarely does.

Careers, and the limits of all of it

The last surface is hiring. Figma's open roles tell you where the investment is going about two quarters before the product does — a team gets funded, then staffed, then ships. Job postings are a leading indicator precisely because they're written before the thing exists.

But here's the honest part, and it applies to this whole teardown: none of these surfaces mean anything on a single reading.

A snapshot of Figma's Community tab today is trivia. The change between this month's and last month's is intelligence. Same for the changelog cadence, same for the careers page, same for what the risk factors said last quarter versus this one. Every signal in this post is a derivative — it only exists if you have two points to compare, and human memory is a terrible place to store the first one. That's the failure mode that kills most intel programs: not that nobody looked, but that nobody could remember precisely enough to notice the diff.

This is the specific and unglamorous thing Seeto does. It watches public surfaces continuously and turns the differences into discrete change events, so the comparison isn't something you have to reconstruct from memory or an old screenshot. It doesn't read the earnings call for you, doesn't summarize what the diff means, and doesn't replace the judgment that turns "this page changed" into "this matters." It makes sure the change is on the record when you go looking. The reading is still yours — as it was in the Notion teardown, the interpretation is the part that can't be automated.

Figma is the easy case. It's public, it's prolific, and it maintains more surfaces than most companies have. Your actual competitor is probably quieter than that.

Quieter doesn't mean silent. It means you have to be more disciplined about the few surfaces they do maintain.