Adam Jacob

You probably wanted it to be of a particular size, right? We could infer all that behavior. And that initial MVP was pretty cool. The bummer was that in infrastructure, something works or it doesn't, usually because it's quite specific. It's not like you can just swap one thing for another most of the time.

Usually what makes any individual application work is some specific set of infrastructure choices and configuration. And so you wind up kind of playing whack-a-mole with the constraints. You'd be like, which constraints do I need to specify in order to get the thing I already know that I want?

Usually what makes any individual application work is some specific set of infrastructure choices and configuration. And so you wind up kind of playing whack-a-mole with the constraints. You'd be like, which constraints do I need to specify in order to get the thing I already know that I want?

Usually what makes any individual application work is some specific set of infrastructure choices and configuration. And so you wind up kind of playing whack-a-mole with the constraints. You'd be like, which constraints do I need to specify in order to get the thing I already know that I want?

And then from there, I think we've probably evolved and rebuilt and redesigned the fundamental technology probably half a dozen times.

And then from there, I think we've probably evolved and rebuilt and redesigned the fundamental technology probably half a dozen times.

And then from there, I think we've probably evolved and rebuilt and redesigned the fundamental technology probably half a dozen times.

With venture-backed startups in general, there's a question always of which game really are you playing? For me, the game I want to play and what this company is designed to do, like I want to win. I want to build a product that transforms the whole industry. System Initiative has the potential to do that. Obviously, you can't say you've done it until you have.

With venture-backed startups in general, there's a question always of which game really are you playing? For me, the game I want to play and what this company is designed to do, like I want to win. I want to build a product that transforms the whole industry. System Initiative has the potential to do that. Obviously, you can't say you've done it until you have.

With venture-backed startups in general, there's a question always of which game really are you playing? For me, the game I want to play and what this company is designed to do, like I want to win. I want to build a product that transforms the whole industry. System Initiative has the potential to do that. Obviously, you can't say you've done it until you have.

So time will tell if we actually did or do. But some of the hard trade-offs you make are when your ambition is really high and you believe that something should be possible, but no one's ever built a system that works this way or had to think of it this way before.

So time will tell if we actually did or do. But some of the hard trade-offs you make are when your ambition is really high and you believe that something should be possible, but no one's ever built a system that works this way or had to think of it this way before.

So time will tell if we actually did or do. But some of the hard trade-offs you make are when your ambition is really high and you believe that something should be possible, but no one's ever built a system that works this way or had to think of it this way before.

You're constantly making trade-offs about how powerful the underlying system will be versus what you can get in front of someone immediately. We had working versions of System Initiative that could generate like Kubernetes configurations and in a pretty delightful way, but it wasn't very programmable, right?

You're constantly making trade-offs about how powerful the underlying system will be versus what you can get in front of someone immediately. We had working versions of System Initiative that could generate like Kubernetes configurations and in a pretty delightful way, but it wasn't very programmable, right?

You're constantly making trade-offs about how powerful the underlying system will be versus what you can get in front of someone immediately. We had working versions of System Initiative that could generate like Kubernetes configurations and in a pretty delightful way, but it wasn't very programmable, right?

You could use it to put together things that we put together for you, but you couldn't really make it do things that were bespoke. You have to make a decision, which is, do you bring the first thing to market where it's not very programmable, the use case is a little more constrained, and what do you learn by bringing that thing into the market?

You could use it to put together things that we put together for you, but you couldn't really make it do things that were bespoke. You have to make a decision, which is, do you bring the first thing to market where it's not very programmable, the use case is a little more constrained, and what do you learn by bringing that thing into the market?

You could use it to put together things that we put together for you, but you couldn't really make it do things that were bespoke. You have to make a decision, which is, do you bring the first thing to market where it's not very programmable, the use case is a little more constrained, and what do you learn by bringing that thing into the market?

For us, the decision was, what we want is to build a transformative product that we believe people could use across the spectrum from giant banks to small companies, and that they could use this technology to really run the entirety of their infrastructure automation, but eventually the whole of the DevOps stack. So we had to make trade-offs on how much time are you willing to spend?