How does Pry address finance collaboration challenges, while expanding its adoption and number of seats within a company?

So finance teams are using Excel, and it's a nightmare. It’s really not a good process. It’s not fun. It’s just not great. And they don’t have that Figma-for-finance experience, which is what they really want to have. And that's what we're trying to build in Pry. In fact, we launched a feature around this, where users can share pages and they can customize these pages. So your head of sales can see just the head of sales payroll or the head of sales budget, and your head of product sees only the product budget.

That in Excel would take a lot longer. Somebody will have to split those out, send them to the sales manager or product manager, who will then fill them out -- and they might fill out wrong -- and then send them back, and then reconcile. That's the current process, and it's really terrible. The problem is a lot of times what they do is they create their own model in a different format some other way and say, “Why can't this work?” And it's like, “Well, it can't work, because you didn't give me the right model.” It's a communication breakdown a lot of times. But it doesn't need to be that way.

We've got a feature that basically does it in-app. When you send it to your head of sales, they cannot possibly break your formulas. They can only make changes. That's a feature I wanted for a long time. Back at inDinero, I was running these quarterly budget meetings, and I was the one matching everything together, sending it out, and negotiating with each of the department heads. And I just thought to myself, “Man, I would save so much time, so much work, if there was a product to do this.” And now I'm building it.

So, absolutely, “Figma for finance” was one of the taglines we used. We don't yet have the multiplayer support that’s really cool with Figma -- like seeing the cursors of other folks -- but that's a cool thing on our roadmap to look into.