>>Mm. Joining me is Aaron Suzuki, founder and CEO of Prowess. >>Aaron. Welcome. Thank you. Thanks so much for having me. >>Absolutely. Thanks for joining us. So let's dive right in. Tell us about prowess. >>Progress has been around for quite a while. We've been serving the technology industry from the very beginning, almost 20 years. We've always been able to bridge the gap between the story of the product and what it actually does. And a lot of times, there's a pretty fundamental disconnect between what engineering says and what marketing wants to claim. And so this is sort of how we got down this road of getting into testing and validation of products such as we do today quite quite extensively. And >>that's really what we're focusing on right now is this idea of your independence as a lab. And in this particular case, uh, it's a series of tests that you've done for, uh, you know, using Dell hardware combined with Broadcom cards. So talk a little more about that. About that the concept of independence and what that means. >>Yeah. You know, it's important to us that we stay vendor, agnostic, platform agnostic. Um, and there are a lot of things happening concurrently in the industry. A lot of people want to get a lot of work done really fast, and most customers are not sort of vendor exclusive. In fact, we're not sure we know of any. We always try to keep this objective point of view. That is to say that we don't allow our customers to buy results when we're doing quantitative testing. We really are out there trying to come up with a story or a narrative, and that really seemed to be The missing link in all of this is that there are the quantitative houses that do traditional benchmark testing on one side and then system integrators and kind of on the other extreme agencies. That would really do the narrative and the system integrator side build out a solution, but they wouldn't be able to tell you how it would perform. And so reconciling those two things really became challenging. So having a source that would be able to give you that insight that goes beyond just transactions, um, you know, per whatever unit of time and finding some of these metrics in between that we're more relevant to people's jobs. Where was really the inspiration for creating this unique practise that we call prowess? Labs? >>So, Erin, when I think about performance testing, uh, it's very easy to think of it from the perspective that it's a bunch of hardware slapped together in Iraq. You get some engineers, scientists to run some tests. Why prowess? What? What do you specifically bring to the table? That's meaningful? >>Performance testing is usually done in one of two ways, predominantly one way. It's a very academic approach, which says this specific benchmark test run this specific way gives us X. Another approach is more narrative in nature and more demonstrative. And there's this huge gap in between, and that's really what prowess labs exist to fulfil. >>So, Erin, give us an idea of the scale of prowess. How many of these projects have you worked on? How many how many customers have you worked with over >>over time? Um, we do this work with most of the leading global hardware and software manufacturers and a select number of emerging providers as well. So for us, you know, year to year dozens of projects of varying scope and scale. Various projects also running kind of programmatic form where we're kind of iterating constantly throughout the year. Um, so it's It's really a lot of fun for our team members to to do this. And some of them have been doing it for 10 or 12 years in continuity. >>Erin, Thanks for joining us to talk about practise today. >>My pleasure. Thanks for having me. Mhm. Yeah.