You can see some of the improvements we're making for individuals at https://releases.figma.com/

We haven't been marketing these as heavily given they are mostly smaller improvements / bug fixes.

Hi Pol, you're right that large teams using Figma is a growing portion of our revenue. That said, individuals and small teams make up the bulk of our customer base. While we have a team staffed and working hard on improving the orgs product, the bulk of our product development efforts right now are going towards fixing component bugs, improving performance, maintaining quality + adding new individual functionality to the product.

Hey Brian, can confirm our pricing for orgs is $45 / editor. I'll reach out to you over email about the sales experience you had to learn more.

Hear you on PDF export. Have you tried https://spectrum.chat/?t=8c2ca793-3372-4e45-8f2d-91fe01ede73c ? I haven't explored it much yet but some users seem to like it. Built on Figma's API.

Darren, this is how I work too. (Might also share when stuck on something / looking for early feedback / want to check in with team)

Hey Marcel, you're right in that we will be using a decent portion of this fundraise to develop the sales / marketing side of the organization + generally try to grow awareness. But that's not at the expense of the product or customer; we're continuing to invest most heavily in eng / design / support. This is a super competitive market and we will lose if we fall behind on the customer experience or our customers can be more productive elsewhere.

On "lock in" there are a few initiatives wrapping up in next few months that will make it easier to get data out of the product. We believe that we will have less adoption if we pursue aggressive data lock in strategies / that is ultimately bad for our business.

Hey Ray, there's an unfortunate DNS issue which is making it show up as parked for some folks. Should be fixed soon.

Hey Darrell, what computer are you on? Any examples of bad performance you can share with us? If yes, could you email us at support@figma.com and mention this comment thread?

Usually people tell us Figma is fast, but there are lots of edge cases to optimize. So if you have a test case you can share with us that is consistently slow, then our team can figure out what's going on and optimize.

We are obsessed with making Figma a buttery smooth experience! Thanks for any help you can provide!

The first designs of Figma were created in Photoshop / Illustrator / code in August, 2013. We used a mix of Figma / Photoshop until early 2014 at which point we made it a rule for ourselves to only make new designs in Figma.

This was pretty tough at first; it definitely slowed us down due to the immaturity of the tool at the time. I remember some days when we accidentally broke the build or changed our file format and our team's designer went home early for the day.

We didn't launch our closed beta until December, 2015, so we had almost two years experience shipping improvements, establishing a solid QA process and refining the product for our own use cases / the needs of alpha testers by then.

While initially painful, dogfooding early in our product's lifecycle helped us prioritize the right things and create processes to keep the quality of the product high. It also helped us debug some pretty crazy issues and made us more comfortable suggesting the tool for real work in the beta phase.

Hey, Cristian! Check out Figma's native app sometime! https://www.figma.com/downloads