Vishal Agarwal

You're five guys and you have a Grubhub tablet at your store, right? What would happen is whenever you received an order as a restaurant owner, you would receive an email order confirmation as well, saying NOAA has placed an order with your store and this is the order.

You're five guys and you have a Grubhub tablet at your store, right? What would happen is whenever you received an order as a restaurant owner, you would receive an email order confirmation as well, saying NOAA has placed an order with your store and this is the order.

What we did was develop an email parser to scrape the information out of that email and send it to the POS systems via an API that we had with those POS systems. Again, very startup-y, stood up the solution with Heroku and Database Server, which we to this day use. The backend was built on Ruby on Rails.

What we did was develop an email parser to scrape the information out of that email and send it to the POS systems via an API that we had with those POS systems. Again, very startup-y, stood up the solution with Heroku and Database Server, which we to this day use. The backend was built on Ruby on Rails.

What we did was develop an email parser to scrape the information out of that email and send it to the POS systems via an API that we had with those POS systems. Again, very startup-y, stood up the solution with Heroku and Database Server, which we to this day use. The backend was built on Ruby on Rails.

I still remember I was at that first restaurant that we were launching with here in New York and we were testing. We weren't yet live. So we did a full three to four hour of testing and then I was on my way back and then my CTO calls me like, hey, our system just crashed. And I'm thinking, oh my God, we aren't yet live and the system is crashing.

I still remember I was at that first restaurant that we were launching with here in New York and we were testing. We weren't yet live. So we did a full three to four hour of testing and then I was on my way back and then my CTO calls me like, hey, our system just crashed. And I'm thinking, oh my God, we aren't yet live and the system is crashing.

I still remember I was at that first restaurant that we were launching with here in New York and we were testing. We weren't yet live. So we did a full three to four hour of testing and then I was on my way back and then my CTO calls me like, hey, our system just crashed. And I'm thinking, oh my God, we aren't yet live and the system is crashing.

If we start processing orders, what would happen if the system crashed then? The customers would have a major problem. Somebody would not get their food and somebody who lives in New York City and orders delivery three to four times a week. I know how important that is. The decision that I made then, I would not have made anything different even knowing what I know now, which is that's fine.

If we start processing orders, what would happen if the system crashed then? The customers would have a major problem. Somebody would not get their food and somebody who lives in New York City and orders delivery three to four times a week. I know how important that is. The decision that I made then, I would not have made anything different even knowing what I know now, which is that's fine.

If we start processing orders, what would happen if the system crashed then? The customers would have a major problem. Somebody would not get their food and somebody who lives in New York City and orders delivery three to four times a week. I know how important that is. The decision that I made then, I would not have made anything different even knowing what I know now, which is that's fine.

The system crashed. Let's keep moving. Let's build it back up and let's see why it crashed and go from there. So today we are processing over 20 million transactions a month. And I remember the time when we celebrated the run rate of 10,000 orders a month. So basically when we hit 300 orders a day, we were like, wow, we are at 10,000 transactions, right? That's what you build for.

The system crashed. Let's keep moving. Let's build it back up and let's see why it crashed and go from there. So today we are processing over 20 million transactions a month. And I remember the time when we celebrated the run rate of 10,000 orders a month. So basically when we hit 300 orders a day, we were like, wow, we are at 10,000 transactions, right? That's what you build for.

The system crashed. Let's keep moving. Let's build it back up and let's see why it crashed and go from there. So today we are processing over 20 million transactions a month. And I remember the time when we celebrated the run rate of 10,000 orders a month. So basically when we hit 300 orders a day, we were like, wow, we are at 10,000 transactions, right? That's what you build for.

You build for 10,000 and then you build for 100,000 and then you build for a million. You never build for a million as a startup. So the number of technical debts that we had to accept at that point in time, which went as far as using a generic email ID, using more open source or free software, even if they didn't come with SLAs, they were all part of the build process.

You build for 10,000 and then you build for 100,000 and then you build for a million. You never build for a million as a startup. So the number of technical debts that we had to accept at that point in time, which went as far as using a generic email ID, using more open source or free software, even if they didn't come with SLAs, they were all part of the build process.

You build for 10,000 and then you build for 100,000 and then you build for a million. You never build for a million as a startup. So the number of technical debts that we had to accept at that point in time, which went as far as using a generic email ID, using more open source or free software, even if they didn't come with SLAs, they were all part of the build process.

Our first large client that we landed was five guys, extremely proud, amazing customers. And when we started processing for them and seeing their scale, that's when the realization of, okay, we are in serious territory now that we need to relook at all of the tech that we have accumulated and make sure it doesn't impact our customers.

Our first large client that we landed was five guys, extremely proud, amazing customers. And when we started processing for them and seeing their scale, that's when the realization of, okay, we are in serious territory now that we need to relook at all of the tech that we have accumulated and make sure it doesn't impact our customers.

Our first large client that we landed was five guys, extremely proud, amazing customers. And when we started processing for them and seeing their scale, that's when the realization of, okay, we are in serious territory now that we need to relook at all of the tech that we have accumulated and make sure it doesn't impact our customers.