No-Code Insights for Startups and Enterprises with Abhishek Nayak, Co-founder of Appsmith

Inside Outside Innovation

On this week's episode of Inside Outside Innovation, we sit down with Abhishek Nayak, Co-founder and CEO of Appsmith. Abhisek and I talk about the rise of no-code tools and some of the misconceptions and opportunities that no-code can bring to startups and enterprises alike. Let's get started.

Inside Outside Innovation is a podcast to help the new innovators navigate what's next. Each week, we'll give you a front row seat into what it takes to learn, grow, and thrive in today's world of accelerating change and uncertainty. Join us as we explore, engage, and experiment with the best and the brightest innovators, entrepreneurs, and pioneering businesses. It's time to get started.

Interview Transcript with Abhishek Nayak, Co-founder and CEO of Appsmith

Brian Ardinger: Welcome to another episode of Inside Outside Innovation. I'm your host, Brian Ardinger. And as always, we have another amazing guest. Today we have Abhishek Nayak. He is the CEO and Co-founder of a company called Appsmith. Welcome to the show.

Abhishek Nayak: Thanks Brian. Really excited to be here.

Brian Ardinger: I heard about Appsmith as we talk more and more about this no-code low-code space, that's developing in the startup and in the enterprise world. And Appsmith is an open-source framework that makes it easy to build and maintain internal custom business tools. No code for the enterprise if I'm correct.

Abhishek Nayak: Yeah, exactly. Think of us like WordPress, but for building internal user facing applications.

Brian Ardinger: I'd love to dig into how this got started, this rise of no-code technologies and that. Making it easier for the non-traditional technical person to build and create faster and that. So maybe let's take a step back and tell us a little bit of your journey of how you became a founder and specifically around, how did you decide to build a no-code app platform?

Abhishek Nayak: Been an entrepreneur for a better part of the previous decade. Appsmith is actually my third startup. My first startup was in the space of offline logistics. We were doing cash and delivery. So, we had around 150 plus people. Lots of custom software built internally to manage them. And to run the business.

My second startup was in the space of AI, where we were trying to automate customer support. And we used to have 10 plus customers and use to automate support requests for them. That again, we were building a lot of custom applications to train the data. Look at how a particular board or a particular model is performing. And just run all sorts of experiments and processes. That was my second startup.

And all of these startups, I had the same co-founder and CTO Arpit Mohan. And he actually got sick and tired of building all these tools. Our second startup didn't work that well. Our first one got acquired. Second one didn't work that well, and we had to shut it.

But he actually started tinkering with the idea of building UI builder but for backend entrepreneurs. Because he was a backend engineer and he really disliked dealing with HTML/CSS. So, he started working on this side project. And this is why he was working at a different job.

And during this period, when he was working on a different job, I was working as an EIR at Excel partners. So, I was an entrepreneur in residence where my job was to meet new startups, talk to them about how to run their business. And just understand if it makes sense for Excel to invest in it. While at the same time, I was also looking at other ideas that I could start out with.

Now I couldn't find anything interesting. But I was helping my friend Arpit figure out if his idea for an open-source project had any legs. And during that process of helping him out, I started interviewing some of these startups that I was meeting on everyday basis.

And I realized that almost every single startup had this problem. That they need to build a lot of custom business applications, maybe to run customer support or expose some data to the sales team. Have a way for the marketing team to maybe generate coupons. Or maybe look up some customer data.

And they never had engineering bandwidth to build what they needed. And that was a problem, right? That's when I started telling Arpit, hey, maybe this can actually be a business. Maybe you just don't need to think of it as a side project. Maybe we should start a business together and do this like a startup.

That's how it actually got started. It was my co-founder's idea because he hated HTML CSS. And then we started working together to build this out as a company. We also have a third co-founder Nikhil who heads product. And he again has been an engineer for a really long time. But he's a front-end engineer and he was just sick and tired of doing the same thing over and over again.

So even though he has skills in HTML CSS, and he loves working on front end, he just disliked the repetitive nature that these internal apps generally have. And that's why he was excited about this idea.

Brian Ardinger: I love the story. Because you often hear entrepreneurs’ stories start with a pain or an itch that they have to scratch. And it sounds like that's exactly where you guys started. And it seems like the timing was perfect for this type of new tool. Because it's getting easier and cheaper to use multiple different tools and open APIs, et cetera, to make it easier to build and scale and test and try things than ever before. Talk a little bit about the early traction you got when you started the company and some of the early things you learned.

Abhishek Nayak: So, the first six months of app Smith was just building the product out. And we actually started pitching it to users and convincing them to use it. But nobody actually converted. Nobody wanted to use it. And that's when we began to question is the product quality low? Do we not have enough features or what's happening here?

When we started digging in deeper, we just realized that the standard style developers have for a product like this is really high. And we just had to go back and improve the quality. And add a lot more features to the product. For it to be ready.

So, after our first launch which failed, you know, we had this pivotal moment where we had to decide, should we start building this for a different audience. Because developers don't seem to like this. Or should we just continue to follow our vision and get this right?

So, I'm glad that we actually decided to continue following a vision, but just improve the quality and add lot more features. Because when he lost a year later, you know, one and a half years have gone by, since we actually started, it instantly took off. Like within the first week, I remember we had about 30 plus teams using us.

And the only thing that we had done was write a blog post announcing that this is live. We did not actually do any sort of sales or any sort of cold outreach to get the users. And we honestly weren't putting in that much effort because we launched, expecting completely failure. Because that's what we had experienced, you know, like a year ago when we had tried to launch. But this time we were pleasantly taken aback by the reaction the market had.

And that's when we realized that a product like this just takes a ...