The tracker Intruder uses to connect product metrics to business results

There's there's a whole bunch of product metrics that we track, and those product metrics do contribute to our our top level revenue number, in in kind of different ways. So, there was we can talk about revenue quite a lot, but in the product design, like, engineering team, we're we're we're focusing pretty heavily on kind of product driven metrics that help us understand how we're solving the problems that our customers have. And, like, at Intruder, like you mentioned, we're a external vulnerability management and attack surface management solution. So part of what we're trying to do, the core thing we're trying to do is help people find risk that exists in their internet facing systems and then fix that risk. Because if we're not helping them find it and then fix it, like, what are we really trying? So that was our North Star. Right? Anything that's a high or critical occurrence, that stuff's that gonna lead to a breach. We wanna know for sure that we're trending in the right direction. So, that's that's what we wanna see move. We wanna see that, like, moving to the top, like, continue upwards ideally exponentially. That would be wonderful. But, yeah, that's our North Star. So so we It is it is in your shot. Right? That's what you're telling me. This is just Yes. Exactly. That's exactly right. Yeah. Absolutely. Yeah. And then there's a bunch of different ways you can get to solving, like, finding and fixing critical and high, vulnerabilities within, within an external attack surface. And and the drivers that go into that, again, I sat down with Keith, who's our head of product design, and we tried to work out, like, what are the key drivers that we have? And I think if we go over to the left hand side one, which I think is probably the kind of the first one is, like, if we're finding critical vulnerabilities, one of the drivers for that is making sure that the vulnerabilities we're detecting aren't garbage. Like, they need to be legitimate vulnerabilities that we're finding. So we have a driver for that. And then we drill down into the kinds of things that we can control that contribute to whether, we're finding the right number of of vulnerabilities. So like the number of checks we have across our platform, we can start to see if if we have more checks for more vulnerabilities, we're gonna find more true vulnerabilities, and then we're gonna help people be able to fix them. So you start to see this relationship flow all the way to the top of the graph. And we can set, like, objectives if we want to in the in this, scenario, but, actually, I tend not to, like, have objectives here. This really for me is trying to understand at a top level when across the the product whether all of the levers and all of the components as we flow are moving in the right direction. So if I see something start to drop and go in the wrong direction, then there's something that we can discuss in the product and then design team to to move that forward.