Figma Plugin Development
Make the boring designer work go away
Designers don't lose their day to "designing". They lose it to exporting assets in four sizes, syncing tokens, hunting down which component is actually in the design system, and copy-pasting copy from a translation sheet.
A good plugin makes that pain go away.
Sounds familiar?
- Your designers do the same 5-click ritual a hundred times a week
- Design tokens in Figma and tokens in code stop matching every quarter
- You need Figma to talk to a CMS, an internal API, or a content source, and there's no off-the-shelf bridge
What you get
- A plugin that fits your team's specific workflow, not a generic tool retrofitted
- Hours per designer, per week, given back, on the boring stuff
- Optional: an OAuth integration to your internal systems, so Figma sees what your product sees
How I work
I shadow the workflow first. Most plugin requests start as "we want a button that does X", and end up being a different problem once I've watched the team for a day. So I watch first, build second.
From real projects
A design team of 150+ people in the automotive space works with five of my plugins every day: metadata management backed by an OAuth-secured database, design releases with rollbacks, responsive design generation from Figma's variable system, color-scheme export as code-ready JSON, and a translation plugin that generates screens in multiple languages while checking for text overflow and line breaks.
How pricing works
No hourly rates, no price list. We start with a conversation about the problem, and what solving it is worth to your business. You then get a fixed-price proposal in three scopes (lean, full, premium), so you can balance scope and budget yourself.
I've shipped 5 production plugins for design teams in the automotive space, including OAuth-integrated ones connecting Figma to internal services.