Anand Kulkarni

When we talk about the MVP, we're really talking about two generations of this company, right? Yeah. Era one was building to collect data and helping people build Greenfield software so that we could collect data that we needed. That era was the first five years of the business. We built the whole stack in Python directly with Django on the back, At the time, it was a view on the front.

When we talk about the MVP, we're really talking about two generations of this company, right? Yeah. Era one was building to collect data and helping people build Greenfield software so that we could collect data that we needed. That era was the first five years of the business. We built the whole stack in Python directly with Django on the back, At the time, it was a view on the front.

The MVP itself, really V0 of that tool. We built that thing in a couple of weeks for the barest of bare bones version that would just transact and let you minimally place orders, match them up and capture the information we needed. Eventually, we flipped a bunch of the core tech into the modernization engine.

The MVP itself, really V0 of that tool. We built that thing in a couple of weeks for the barest of bare bones version that would just transact and let you minimally place orders, match them up and capture the information we needed. Eventually, we flipped a bunch of the core tech into the modernization engine.

The MVP itself, really V0 of that tool. We built that thing in a couple of weeks for the barest of bare bones version that would just transact and let you minimally place orders, match them up and capture the information we needed. Eventually, we flipped a bunch of the core tech into the modernization engine.

The modernization engine itself, we built over the course of 12 months to get that core machinery built. And it emerged from the pieces of what we had before being reconfigured in. So our core LLMs stayed the same. The core requirements factor changed from being one where we would capture that data on the outside to one where we would make that data available for customer use.

The modernization engine itself, we built over the course of 12 months to get that core machinery built. And it emerged from the pieces of what we had before being reconfigured in. So our core LLMs stayed the same. The core requirements factor changed from being one where we would capture that data on the outside to one where we would make that data available for customer use.

The modernization engine itself, we built over the course of 12 months to get that core machinery built. And it emerged from the pieces of what we had before being reconfigured in. So our core LLMs stayed the same. The core requirements factor changed from being one where we would capture that data on the outside to one where we would make that data available for customer use.

We've always built software in-house. Django is our framework of choice. Nowadays, we use React. The ultimate machinery, of course, under the hood, we switched long ago from using PyTorch and our own methodology to being able to run on top of Azure and Azure OpenAI as our main AI backend.

We've always built software in-house. Django is our framework of choice. Nowadays, we use React. The ultimate machinery, of course, under the hood, we switched long ago from using PyTorch and our own methodology to being able to run on top of Azure and Azure OpenAI as our main AI backend.

We've always built software in-house. Django is our framework of choice. Nowadays, we use React. The ultimate machinery, of course, under the hood, we switched long ago from using PyTorch and our own methodology to being able to run on top of Azure and Azure OpenAI as our main AI backend.

I'm a technical founder. Even though as CEO and entrepreneur, you don't have to be the technologist, because I happen to be a technologist, I have opinions about the system. We built the early version of the platform on Django. I had an early choice, I remember, between building on Django and building serverless, which was brand new at the time as a methodology.

I'm a technical founder. Even though as CEO and entrepreneur, you don't have to be the technologist, because I happen to be a technologist, I have opinions about the system. We built the early version of the platform on Django. I had an early choice, I remember, between building on Django and building serverless, which was brand new at the time as a methodology.

I'm a technical founder. Even though as CEO and entrepreneur, you don't have to be the technologist, because I happen to be a technologist, I have opinions about the system. We built the early version of the platform on Django. I had an early choice, I remember, between building on Django and building serverless, which was brand new at the time as a methodology.

But first I tried serverless, and I spent a week... Wasting my time trying to teach myself serverless while building the MVP. I remember thinking, what a dumb decision. At the time, I was just so disappointed. I was like, I can't make this work. I can't believe it.

But first I tried serverless, and I spent a week... Wasting my time trying to teach myself serverless while building the MVP. I remember thinking, what a dumb decision. At the time, I was just so disappointed. I was like, I can't make this work. I can't believe it.

But first I tried serverless, and I spent a week... Wasting my time trying to teach myself serverless while building the MVP. I remember thinking, what a dumb decision. At the time, I was just so disappointed. I was like, I can't make this work. I can't believe it.

But then I realized repeatedly how happy I was that I had simply chosen Django because I knew the system well and because Django is easy to build quickly. Of course, now we do things that are architecturally far more complex than that. But that simple choice we made early on let us go very quickly in a lot of places very early.

But then I realized repeatedly how happy I was that I had simply chosen Django because I knew the system well and because Django is easy to build quickly. Of course, now we do things that are architecturally far more complex than that. But that simple choice we made early on let us go very quickly in a lot of places very early.

But then I realized repeatedly how happy I was that I had simply chosen Django because I knew the system well and because Django is easy to build quickly. Of course, now we do things that are architecturally far more complex than that. But that simple choice we made early on let us go very quickly in a lot of places very early.