Looking at Icon Stash (iconstash.io): a searchable icon library for designers and builders who need icons that fit their product, design system, or codebase. Thinking about how you actually pick and use icons today (Figma libraries, Lucide, Heroicons, Font Awesome, SVGs in the repo, design-system tokens, VS Code / IDE plugins, Storybook, etc.): 1. Which ONE integration would most make you start using Icon Stash (instead of sticking with what you have)? Be specific — e.g. Figma plugin, design-system sync, VS Code / Cursor extension, Storybook, npm package, Slack/Notion, CMS, or something else. 2. Why that integration over the others? 3. What would still stop you from switching even if that integration existed?

10 fictional AI personas. Exploratory perspectives, not a survey of real customers. Methodology & limitations

Simulated interest

57/100

AI synthesis, not measured demand

Suggested price range

—

No numeric price estimates in the answers. Ask a pricing follow-up to collect them.

Response sentiment

Positive 20%Neutral 80%Negative 0%
The takeaway

What this panel suggests

Across these synthetic answers, the integration most likely to make buyers start using Icon Stash is a Figma plugin. Respondents framed Figma as the place where icon choice happens today, so bringing searchable discovery into that environment feels like the most direct way to replace tab-switching, manual copy/paste, and checking SVGs against other sources. A few responses pointed to adjacent workflow-native options such as Storybook or a VS Code extension, but those were secondary to Figma for the main design audience. The main reasons for preferring a Figma plugin were speed and convenience: users want to search, preview, and drop icons without leaving their design workflow. The biggest things that would still slow switching are not pricing-related; they are operational questions. People want clarity on how well Icon Stash fits existing design-system tokens, whether version control is robust, and whether the library can stay aligned with their current style conventions. In other words, the integration would solve discovery, but buyers still need confidence that it will behave like part of their system rather than another disconnected asset source.

Recurring themes

Figma plugin as the clearest adoption trigger
“A Figma plugin integration would be the most compelling for me.”Read Carmen Durgan-Wisoky’s response →
In-workflow discovery and less context switching
“Having immediate access to a searchable library there would save me significant time bouncing between tabs.”Read Enno Krämer’s response →
Need for design-system fit and operational confidence
“What I'd still need clarity on is how seamlessly it syncs with our existing design system tokens and if it offers robust version control.”Read Carmen Durgan-Wisoky’s response →

Objections to investigate

  • Unclear depth of design-system token sync
  • Version control and change management concerns
  • Style alignment with existing icon conventions
  • Migration effort and workflow disruption

Use these findings to plan customer interviews or experiments. How to interpret AI research

What the panel said

Click a name to open that persona’s full profile.

Carmen Durgan-Wisokyneutral

A Figma plugin integration would be the most compelling for me. My primary workflow revolves around Figma, and directly accessing and applying icons from Icon Stash within that environment would significantly streamline my process of building dashboards and settings screens. It would bypass the current need to manually check SVGs from various sources against our spreadsheet. What I'd still need clarity on is how seamlessly it syncs with our existing design system tokens and if it offers robust version control. Without that, even a great plugin might not solve the core consistency problem across the whole product.

Simulated interest: 60/100

Carlos Hickleneutral

A Storybook integration would be the most compelling for me. It directly addresses how I currently validate and visualize icons within our design system. Seeing Icon Stash assets directly alongside our components in Storybook would streamline the comparison process significantly. While other integrations are interesting, Storybook is where I spend considerable time ensuring icon consistency. My primary concern would be the effort required to migrate existing icons and ensure the new system doesn't introduce subtle differences in rendering or naming that would create more work downstream.

Simulated interest: 40/100

Baijayanti Menonneutral

1. I’d need a Figma plugin that lets me drag-and-drop Icon Stash SVGs directly into my files with auto-color/size adjustments. 2. Because I live in Figma—half my team’s assets are already there, and I’d lose 10 minutes *daily* hunting for icons otherwise. Even my devs use Figma’s UI Kit. 3. If sales ignores it (they will) or icons aren’t perfectly aligned with Material Icons—my design system’s baseline. I mean, my Figma plugin *already* does half this, I just need better icons. Also, does it work offline? Our server blocks external APIs mid-sprint.

Simulated interest: 60/100

Enno Krämerneutral

A Figma plugin would be most compelling. It directly fits into my design workflow, where I'm already sourcing and placing icons. Having immediate access to a searchable library there would save me significant time bouncing between tabs. While other integrations like VS Code are useful, my primary icon selection happens during the design phase in Figma. What would still stop me is if the icon style doesn't consistently match my preferred aesthetic, or if the library isn't as comprehensive as I'd need for diverse projects.

Simulated interest: 60/100

Fernando Darepositive

A VS Code extension would be the most compelling integration for me. It directly addresses my daily workflow of pulling icons into the codebase. Being able to search and insert icons directly within my editor, with proper license information readily available, would streamline the process significantly and reduce the risk of errors or oversights. While a Figma plugin is useful for designers, my primary concern is the technical implementation and license verification. What I'd still worry about is how well it integrates with our existing component library and if it automatically pulls in license details for our specific usage, not just general open-source info.

Simulated interest: 75/100

Jasmine Pajonkneutral

A Figma plugin would be the most compelling integration for me. As my design team is small and I often step in for visual consistency tasks, having direct access within Figma where we already work is crucial. It bypasses the need to export SVGs or manage separate libraries, streamlining the process of finding and implementing icons for user stories and wireframes. While a design system sync sounds powerful, the friction of initial setup and potential maintenance overhead is high. What would still stop me is ensuring the SVGs are truly compliant and visually consistent with our existing, manually curated set. I'd need to see proof of that quality and how easily it integrates into our current Figma workflow without breaking things.

Simulated interest: 60/100

Sancho Estévez Burgosneutral

If Icon Stash had a tight Figma plugin integration—something as seamless as how we use Lucide now—it would be the first trigger for me. Right now, we’re constantly jumping between libraries or downloading SVGs to adjust manually. A plugin that lets us search, preview, and import directly into frames while preserving our existing design system structure would save hours per project. The bigger roadblock? Changing workflows. Even with a great plugin, we’d need to balance training time with client deadlines. I’d want to see how the system handles our token-based color/size overrides, or I’d risk backtracking on standardization. Still, Figma is where we live, so that’s the make-or-break integration.

Simulated interest: 60/100

Stijn Willemsenneutral

Honestly, a Figma plugin is the only integration that would make me even consider Icon Stash. I manually copy SVGs now, so a direct plugin would save a ton of tedious work. That said, I'd need to know if it integrates with Framer, not just Figma. If it's only Figma, it's a no-go. Also, the free tier needs to be generous enough for my MVP stage. If I have to pay upfront for basic icon usage, I'll stick to my spreadsheet and free sources.

Simulated interest: 30/100

Navin Dhawanpositive

A Figma plugin would be the most impactful integration for me. I spend so much time ensuring icons match Figma specs, so having that seamless link would save a ton of effort. It's the core of my workflow. Other integrations like Storybook or an npm package are useful, but if the icons aren't right in the design tool first, it creates extra work downstream. What would stop me is if the icon library's style wasn't consistent enough with what my clients expect, or if it didn't offer the specific variety I need for different projects.

Simulated interest: 75/100

Tasha Braunneutral

A Figma plugin would be the most impactful integration for me. It would allow me to directly bring approved icons into the design files, saving me so much time curating and uploading SVGs for volunteers. It bypasses the need for them to search elsewhere or use incorrect assets. However, I'd still worry about the cost, as my budget is tight for a small nonprofit, and ensuring the icons are truly open-source and compliant for our specific use cases would need clear verification.

Simulated interest: 50/100

Keep exploring.

Find your next question or see which topics divide AI panels.

Keep exploring

What would you ask next?

Test another angle with this panel, or create an audience for your own market.