Umaimah Khan

The other thing, and this kind of touches into how we're talking about roadmap, is obviously we built very critical infrastructure. Building a team that had the experience to know what they were building was also very important. because this is a product that requires a lot of trust and understanding.

The other thing, and this kind of touches into how we're talking about roadmap, is obviously we built very critical infrastructure. Building a team that had the experience to know what they were building was also very important. because this is a product that requires a lot of trust and understanding.

So having a balance of those two things keeps the pace of execution going, but also the experience of having seen things before.

So having a balance of those two things keeps the pace of execution going, but also the experience of having seen things before.

So having a balance of those two things keeps the pace of execution going, but also the experience of having seen things before.

It's a balance. And I would say from day one, there was this notion of scale in mind. And at the same time, like recognizing when you're making one way decisions versus two way decisions. There are things you do early on, especially on the engineering side that like could be construed as tech debt. But you have to make those calls so that you can get to the next milestone.

It's a balance. And I would say from day one, there was this notion of scale in mind. And at the same time, like recognizing when you're making one way decisions versus two way decisions. There are things you do early on, especially on the engineering side that like could be construed as tech debt. But you have to make those calls so that you can get to the next milestone.

It's a balance. And I would say from day one, there was this notion of scale in mind. And at the same time, like recognizing when you're making one way decisions versus two way decisions. There are things you do early on, especially on the engineering side that like could be construed as tech debt. But you have to make those calls so that you can get to the next milestone.

There is like a small bucket of decisions, I think, architecturally that matter a lot, and it's very important to get them right from day one. So in our case, if you look at how Access products have been built in the past, none of them have really been built for hyperscale or complexity. They're not really built to have flexible data models.

There is like a small bucket of decisions, I think, architecturally that matter a lot, and it's very important to get them right from day one. So in our case, if you look at how Access products have been built in the past, none of them have really been built for hyperscale or complexity. They're not really built to have flexible data models.

There is like a small bucket of decisions, I think, architecturally that matter a lot, and it's very important to get them right from day one. So in our case, if you look at how Access products have been built in the past, none of them have really been built for hyperscale or complexity. They're not really built to have flexible data models.

This idea of context or being able to be flexible between role-based access control or attribute-based access control, it's quite difficult. And then the other thing is there's latency on all these things, whether it's requesting access or knowing who has access in real time. There's just not been systems that have been built from the ground up.

This idea of context or being able to be flexible between role-based access control or attribute-based access control, it's quite difficult. And then the other thing is there's latency on all these things, whether it's requesting access or knowing who has access in real time. There's just not been systems that have been built from the ground up.

This idea of context or being able to be flexible between role-based access control or attribute-based access control, it's quite difficult. And then the other thing is there's latency on all these things, whether it's requesting access or knowing who has access in real time. There's just not been systems that have been built from the ground up.

And some of that is just as a result of the fact that some of these companies and products are from a different era. But this idea of being built for scale was always like very top of mind and being able to be flexible enough on the data model. And that's where it's worth like putting in the investment. That's how we think about it, like from day one. And so that's where we didn't compromise.

And some of that is just as a result of the fact that some of these companies and products are from a different era. But this idea of being built for scale was always like very top of mind and being able to be flexible enough on the data model. And that's where it's worth like putting in the investment. That's how we think about it, like from day one. And so that's where we didn't compromise.

And some of that is just as a result of the fact that some of these companies and products are from a different era. But this idea of being built for scale was always like very top of mind and being able to be flexible enough on the data model. And that's where it's worth like putting in the investment. That's how we think about it, like from day one. And so that's where we didn't compromise.

On the rest of the stuff, it's very case by case. Sometimes it's better to have something done than have something perfect. And you make that call by, again, understanding what your core strengths are as a product. Our core strengths are reliability, accuracy, speed, and data. So that's where we wouldn't compromise architecturally and continue to make the investment to improve.

On the rest of the stuff, it's very case by case. Sometimes it's better to have something done than have something perfect. And you make that call by, again, understanding what your core strengths are as a product. Our core strengths are reliability, accuracy, speed, and data. So that's where we wouldn't compromise architecturally and continue to make the investment to improve.

On the rest of the stuff, it's very case by case. Sometimes it's better to have something done than have something perfect. And you make that call by, again, understanding what your core strengths are as a product. Our core strengths are reliability, accuracy, speed, and data. So that's where we wouldn't compromise architecturally and continue to make the investment to improve.