(CASE STUDY · 02)

FIGCOMS

Product Design
UX | UI
Art Direction
Motion & 3D

Figcoms is a workflow platform built on a simple idea: Figma comments are powerful, but the work around them is broken. Instead of pulling teams out of Figma, Figcoms extends it - turning scattered comments into a structured, syncable workflow that lives where the work already happens.

ROLE: Brand & Product Design
TIMELINE: 4 Months
YEAR: 2025
TEAM: Co-Founder

(MY ROLE)

Co-founded Figcoms and designed the product: the board, the four states, and the flow between them.
Replaced the first control set with an emoji-based status system once it started adding complexity instead of removing it.
Built the identity, the motion language and the landing page in parallel with the app.

(WHY IT EXISTS): Out of work with the design and dev teams at Elementor and Salesforce. Everyone comments inside Figma; past ten frames nobody can tell what is waiting, working, in review or done.
(THE FIRST VERSION DID TOO MUCH): The early controls turned every comment into a form. They were cut for four states and an emoji.
(AFTER LAUNCH): Two people, four months. #33 on Product Hunt the day it shipped, and used on real projects since.

Process

01
Research & Context
We mapped how teams actually use Figma comments today. The pain pointed to ownership, priority, and continuity - not to Figma itself.
02
Concept & Flow
The core mechanic became “one link, instant clarity.” Paste a Figma URL, get an organized workspace built around four states every team already speaks.
03
UX/UI & Interaction
Soft cards, generous whitespace, and a typographic hierarchy that lets the comment lead. Emoji-based status changes replaced heavy controls.
04
System & Experience
Identity, motion language, and landing page were built in parallel with the app so marketing and product speak one sentence.

How It Works

Paste a Figma link. Every comment becomes a task with an owner and a status, and every change syncs back - what the team sees here is what they see in the file.

The Board

The interface had to look like a workflow tool without feeling like one. A Kanban-style flow across Backlog → Working → In Review → Done, stress-tested on real projects before any pixel was drawn.