Growth idea action plan
Figma Community comments and support contact as trust surface
Treat comments and support contact as part of the public product page, because Figma makes support details mandatory and leaves comment threads visible to every future buyer.
Why this can grow a startup
Public comments are not a nuisance to hide from. They are one of the clearest trust signals on a resource page. Figma requires support contact information when you publish, turns comments on by default, and notifies creators when feedback arrives. That creates a visible operating standard: people can see whether the creator answers real questions, fixes confusion, and stays present after launch. In crowded resource marketplaces, that can matter more than another design flourish.
Ian's take
From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.
Action plan
- Define one narrow startup segment where figma community comments and support contact as trust surface can create a measurable lift.
- Turn the tactic into one offer, page, campaign, or workflow for the Support and Brand channel.
- Use the evidence from help.figma.com to set the first version of the message, format, and audience.
- Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
- Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.
Source-backed example
Figma requires an email, website, or help center link as support contact when publishing, allows comments from Community members by default, and notifies creators about comments on their published resources.
Source: Figma Learn: Comments on Community (help.figma.com)
GrowthDex source hub: Figma Learn: Comments on Community
Last checked: 2026-05-30T22:20:00Z
Adjacent tactics in the same lane
If this page is close to your problem, these tactic pages usually belong in the same working set.
- Chrome Web Store verified publisher URL and support hub 3 shared channels
- HubSpot marketplace support email and language before scale 3 shared channels
- Help center custom domain before support links spread 2 shared channels · 1 shared stage
- Slack Marketplace public support path with 2-day SLA 2 shared channels · 1 shared stage
Related GrowthDex essays
- The Community page should teach the tool before the install creator-led growth, marketplaces, brand trust
Read GrowthDex essays
The Blog turns real growth tactics into plain-English case studies by niche, channel, and buying situation.
Why this is worth your time
GrowthDex starts with tactics that founders, marketers, and product teams have actually tried. Each essay turns the evidence into a practical move you can test without pretending one case study is a guarantee.
Ian Goh has helped grow consumer platforms across Southeast Asia, India, and MENA. His work includes scaling Tiki to 100M+ users, doubling BIGO's MENA revenue in 7 months, and increasing OYO's direct booking share across 6 Southeast Asian markets.
- Helped scale Tiki to 100M+ users.
- Doubled BIGO's MENA revenue in 7 months.
- Raised OYO's direct booking share by 50% across 6 Southeast Asian markets.
Want help turning this into a growth system?
If you want someone to pressure-test this against your real market, Ian works with founders on growth, market entry, and operator-led distribution.
Work with Ian on growth advisory