Hey,
Figma has changed how I work. Not a little, but fundamentally. And that's not because it's prettier than Photoshop. It's because it makes collaboration actually possible.
For teams that take design seriously, Figma has become almost indispensable. Here's how I use it.
Why Figma is different
With Photoshop or Illustrator, you work with files. You make a version, save it, send it by email. The client makes notes, sends the file back. You make a new version. And so on.
With Figma, you work in the cloud. There are no files being sent back and forth. There's a link. The client opens the link and sees the design. They can leave comments. You can change things live while they watch.
That sounds like a small thing. It's not. It changes everything.
The workflow that works
Step one: I set up a new project in Figma. Clear structure, clear naming. Nothing's more annoying than a Figma project where nobody can find anything.
Step two: I build a design system. Colors, fonts, components. Everything that gets reused is defined once. After that, never created by hand again.
Step three: I design the pages. Using components from the system. When I make a change to a button, the button changes everywhere. Not manually, automatically.
Step four: I share the link with the client. They can comment directly in the design. No phone calls, no email ping-pong. They click on a spot and write what they think.
Step five: I implement the changes. The client sees it in real-time if they want. Or they check in later.
Step six: developer handoff. The developer can pull out all the spacing, colors, fonts themselves. No more writing specifications by hand.
Design systems that pay off
A design system is a collection of reusable components. Buttons, input fields, cards, navigation. Built once, used everywhere.
That saves an incredible amount of time. Not on the first project, but on every one after. When the client wants a new section on the website, I build it from existing components. In hours, not days.
For SMBs, a full design system isn't always worth it. The effort is high, and if the website only has five pages, it doesn't pay off.
But a basic system almost always pays off. Colors, fonts, a few fundamental components. That's set up in two hours and saves time on every project.
Collaboration with clients
The biggest advantage of Figma is collaboration. Clients can see designs without installing software. They can comment without understanding design tools.
I send a link, the client opens it in the browser, done. They see exactly what I see. No version confusion, no compatibility issues.
Comments are placed directly in the design. The client clicks on a spot and writes about it. I see exactly what's meant. No "that thing up there on the right, no, not that one, the other one."
That saves coordination time. Massively. What used to take three feedback rounds is now done in one.
Collaboration with developers
Developer handoff is where Figma really shines.
Before, I used to write specifications. Spacing in pixels, color codes in hex, font sizes in points. Hours of work, and the developer still had questions.
Now the developer inspects the design themselves. They click on an element and see all the values. CSS code is automatically generated. They copy, paste, done.
It doesn't always work perfectly. Sometimes the generated code doesn't fit. But it's a starting point. Better than nothing, much better than manual specs.
What Figma costs
The basic version is free. For individuals or small teams, that's often enough.
The Professional version costs $15 per person per month. That's the sweet spot for most. Unlimited projects, unlimited history, team features.
For larger teams there's the Organization version for $45 per person. With admin features, SSO, and everything enterprises need.
For SMB projects, I usually use the Professional version. I don't pass the costs on to the client, that's part of my infrastructure.
The limits of Figma
Figma isn't a jack of all trades.
For complex image editing, you still need Photoshop. Figma can crop images and add filters, but for serious retouching it's not enough.
For print design, Figma is unsuitable. It thinks in pixels, not millimeters. It doesn't understand bleed margins, no CMYK colors. For flyers and brochures, I stick with InDesign.
For complex illustrations, Illustrator is better. Figma can do vectors, but not as well. For a logo it's enough, for a complex illustration it's not.
The actual point
Figma isn't a tool, it's a workflow. It changes how design projects run. Faster, more collaborative, more transparent.
For teams that need to work together, it's almost indispensable. Designers and developers, agency and client, internal and external. Everyone works in the same environment, everyone sees the same thing.
That's not just more efficient. It's also more pleasant. Fewer misunderstandings, less frustration, better results.
Cheers,
Rafael