Available For Work

Web-to-Figma: From 1K USD Monthly to 1K USD Daily
Results at a Glance
Total Users | Platform Users | Community Files | Revenue Growth |
50,000+ | 150K+ | 1K+ | 35% |
The Situation
Web-to-Figma converts any website into a fully editable Figma file, solving a real problem for designers who previously had to recreate components manually whenever they found something inspiring on the internet. When I joined in May 2024, the product had around 100K total users, 4,000 to 5,000 weekly views on Figma Community with 200 files, and approximately 1K USD in monthly revenue.
The dominant player in the space was HTML-to-Design, already well established in the Figma Community with a large following. The goal was clear: grow our presence in the community, attract the right users, and turn Figma Community into a sustainable acquisition engine.
The Challenge
Competing directly against an established market leader in the same channel
Limited team resources -- growth had to come from consistent execution, not budget
Community files needed to be high quality and click-worthy to stand out
No existing playbook -- the Figma Community strategy had to be built from scratch
The Strategy
The insight was simple: designers discover tools through the community files they actually use. Instead of trying to out-market HTML-to-Design, we would out-publish them with better, more targeted content.
I built a daily research and publishing system around three principles:
Quality over everything
Every website I selected had to meet a simple criterion: beautiful, modern, and click-worthy. I personally reviewed and shortlisted 10 websites daily from across the internet, then converted each one into an editable Figma file using our tool. No shortcuts, no low-effort uploads.
Niche targeting
Rather than uploading random websites, I mapped out the highest-demand niches in the designer community: ecommerce, AI agent interfaces, portfolio sites, AI startup websites. Every file was tagged and named to match what designers were actually searching for inside Figma Community.
Volume with consistency
200 files per month, every month. That consistency compounded over time -- more files meant more discoverability, more comments, more appreciation posts, and more users discovering the plugin embedded in each file.
What Happened
Uploaded 1,200+ unique community files in under 6 months
Weekly views on Figma Community grew from 4,000 to 5,000 to 10,000+ per week
Total platform users crossed 150,000 -- up from under 100,000 when I started
Monthly revenue transformed from approximately 1K USD per month to 1K USD per day
35% overall revenue growth driven entirely through organic community presence
Why It Worked
Designers inside Figma Community were not looking for ads -- they were looking for useful files. Every file we published was genuinely useful, which meant every view converted at a higher rate than any paid channel could. Users would open a file, use it, see the Web-to-Figma plugin in action, and convert naturally.
The competitive advantage over HTML-to-Design was not quality alone -- it was the volume of niche-specific files. We owned the AI website niche, the ecommerce niche, the portfolio niche. That specialization made our files rank higher in community search results.
What I Would Do Differently
Start tracking file-level analytics earlier to identify which niches converted best, then double down on those specific categories
Build a waitlist or newsletter for Figma Community followers to create a direct channel for product updates and new launches
Key Takeaway
Consistent, high-quality content in the right channel beats paid acquisition. 1,200 community files built over 6 months created a compounding acquisition engine that grew daily revenue by 30x -- without spending a single penny on ads.

