Skip to content
The $9B Startup That Wants to Create a Billion New Developers episode artwork

Apr 25, 2026 39 min

The $9B Startup That Wants to Create a Billion New Developers

from Y Combinator Startup Podcast Hosted by Y Combinator

Replit is the leading no-code app builder for consumers and enterprise, letting anyone with an idea build real, deployed software using natural language. The company just raised a $400 million Series D at a $9 billion valuation.In this episode of Founder Firesides, co-founder and CEO Amjad Masad sat down with YC's Andrew Miklas to talk about Replit's 10-year journey from browser IDE to vibe coding platform, why the people getting the most value aren't traditional developers but founders and domain experts closest to the problem, and what Agent 4 unlocks with parallel agents, built-in design, and the ability to run your entire company on Replit.

Episode details come from the podcast's RSS feed.

Embed this episode

Ready to play

The $9B Startup That Wants to Create a Billion New Developers

0:00 39:11
of matches

Transcript Auto-generated, may contain errors

Today I'm joined by Amjad Masad, the CEO and co-founder of Replit. Replit is the leading no-code app builder for consumers and enterprise. They just recently raised their Series D, a $400 million raise at a 9 billion valuation. Amjad, thank you very much for joining me and I'm excited to learn more about Replit. Thank you for having me.

Of course. Why don't you tell us a little bit about what Replit is? Yeah, so our ambition is that anyone, no matter what level of skill they have, anyone who can read and write basically, that's the skill that you need, can come in with an idea and can leave with an app that's deployed that's hosted, that's getting traffic, that's can scale. They don't have to worry about any technical aspect of building that thing. It's been a mission we're on for 10 years right now.

So initially we solved the development environment. That was the hardest thing, so setting up the development environment, then solved the deployment environment. What was left is a coding part was still very intimidating for people. September 2024, Replit became the first what's called live coding product where we abstracted away code entirely. So there's a coding agent behind the scene, but you're just interfacing with AI using natural language.

More recently with Agent 4 also design interactions. So you can write things, you can comment on things, you can drag and drop things in like a canvas. We're thinking about a lot of different modalities for how people want to interact with agents, because I don't think it's always going to be just text. I think it's something that's going to be multi-mobile, maybe video, maybe audio. But we want to create a natural place where people can express their ideas, and those ideas can turn almost magically into software.

That's real software, that's not like a toy software, real software, secure software, scalable software. One of the things that's most interesting to me about your company is that it really bridges the gap between a dev tool and not. I think it's the first dev tool I've seen, but that's not marketed towards engineers. Like can you tell me more about how you came to that decision that you were going to do that, and who is your primary user today? Yeah, so I started coding at a very, very young age, but I was always interested in the act of creation.

I was interested in entrepreneurship. I built my first business when I was 13, 14. And I always thought that the developer tools were getting in the way. It actually got in worse over time. So I started coding on basic, and you just started the basic command line interpreter, and you can just like type a little basic, and that's good.

By the time I graduated from college, like setting up a web app was like a nightmare. And so it created this desire to just build tools that are more joyful, more enriching, kind of focused on the act of creation as opposed to the accidental complexity of developer tools. And so I started building a lot of tools for myself, and eventually I built what would become the first in browser IDE. Initially it was an open source project. Later on I would also work on React and React Native.

And I approached every time I built a developer tool, I approached it with the same thing. Can you apply design sensibilities in the same way that you would work on a consumer app? And that's been successful in many ways. But ultimately when we started React, the goal was make programming accessible. Later we updated our mission to create a billion new developers.

As we progress in our mission and in solving every part of our software development life cycle, what we've noticed is a lot of developers actually like the ping. They like setting up things, and they like configuring every aspect of it. It's sort of like, there's no knock against that, but it's sort of like a craftsperson kind of liking to build their own tools. And what we've noticed is that people that are getting the most value out of our product tend to be the more tech adjacent ones. Many people, product managers have written code many years ago, but don't worry about the development environment setup.

Don't worry about the deployment setup. Then designers, designers who have ideas but are often blocked or bottlenecked by engineers, and they want to be able to build their own ideas. And later on as we later on AI, the product got better, entrepreneurs. When I talk to these people, it reminded me of myself. Those are people with ideas, with passion, with fire in them.

But they're getting ham strong by just the need to learn to become technical. So at some point in 2023, we just made it an explicit goal of like we're not going after developers. They're still developers. If you walk around replicas today, it looks like a DevTools company. We're building for creators, right?

But they're not the traditional type of developers. They're the new generation of developers that are coming up right now because of AI. And AI native developers that are creating software without having to worry about every component of the system. It's so interesting hearing you say this because it sort of reminds me, I learned to program on VB6. And to me, that's a real, you know, this idea of the tools opening up and making it possible for people that couldn't code.

I learned to code in VB6. And I see sort of a very similar thing that you're exploring with this. Yeah, VB6 was better than setting up React and Webpack. 100%. I remember the transition.

Yes. It got worse over time, which is like, not many things gave worse in life. But programming got worse. And I was like, I'm not going to say it to bring it back, make programming great again. It's so interesting.

Tell me about what people are building today in Revly. Yeah. I mean, there's a few different categories. There's personal software, there's enterprise software, and then there's like entrepreneurs building products. One of the apps that I really liked recently was talking to a physical therapist and her husband.

And she is a physical therapist that's built up so much deep knowledge in a subsection of physical therapy that is like around Fasha and Fasha release. And she has all these different methodologies and ways of tracking the progress for her client and she wanted to build an app that is very sophisticated. Like being able to take scans of your body, being able to scan your range of motion and to track that on a 3D representation of your body. And they spent hundreds of thousands of dollars offshoring to developers around the world. And eventually they were frustrated by the entire process, took matters into their hands, built it on Revly.

And when I saw that, it was like one of the best health deck apps I've ever seen. And they're not. Yeah, because the domain experts now actually build the product. Yeah, people who are closest to the problem can build up the products they need. You know, I talked to a founder the other day that's building a SaaS solution for people who maintain pools.

Like, and he grew up in a household where their family business is a pool business. And so it's like, there's so much software to build in the world. I also met a founder yesterday who's building software for sports clubs. And he was showing me pictures of the software they're using today, which is MS-DOS based software. And so here in Silicon Valley, we look around and we're like, oh, what else is left to build?

But there's so many walks of life. There's so many things that are kind of a blind spot for us. And so suddenly when anyone can make software, a lot of parts of the economy is just going to improve. And that's like, I think, a beautiful thing. And a lot of wealth creation is going to happen pro-activity gain as well.

Personal software is also really cool. Like, you know, it talks to a lot of families that build, like, you know, healthcare software, like there's like a mom in Korea that builds software that helps manage their air condition for her kid. A lot of people build personal, like, you know, healthcare software, like tracking physical activity or ingesting data from all their wearables and doing something with it. A lot of software for families, like a mom built, like a short hero software iPad that's like on the wall that shows the kids how they're ranking on their tours. And then there's the enterprise use case.

And in enterprise, it tends to be two different use cases. One is product development. So companies want to move a lot faster on product development. Everyone now is feeling the pressure of AI. We need to move faster, faster, faster, faster.

And they're realizing that it doesn't fall just on their engineers. The product people can have built software. The designers can build software. We hear from clients, like one of my favorite stories, like whoop is a client of ours. And they told us like the amount of ideas they can try has grown by an order of magnitude, right?

Like they used to, you know, get like a hundred ideas but are able to only try five of them. But now they can try to 50, right? So your companies become a lot more prolific. They can release a lot of new features, create new business lines, new products. And then there's like internal tools and, you know, line of business applications.

There's a lot of sales automations that are happening to these companies. Any role inside a company that's dealing with a lot of data flow, for example, can give revops that are the nexus of a lot of different data flow from their CRM, from their data people, from GONG, from, and they want to be able to do things with this data. And typically they're kind of bottlenecked by other engineering resources or the different sass tools that they want to buy. The problem with sass is you onboard a new sass tool that creates a new side-over data that you can't really program. So now they're taking matters of their own hands and building things like, you know, quote configurators and being able to save the company hundreds of sass tools, not many of those are sass tools and things like that.

How are you finding these users? Like how do you market to them? How do you get them to try it out? And then I assume for enterprises it's got to be a very complicated sales cycle, like, you know, getting into the company. Like how does all that work?

Well, the cool thing about the world we're in right now, and it's very similar to developers, you know, I think the insight a lot of YC Dev Tool companies has had, like, you know, Stripe, you know, PagerDuty, you, you, developers were empowered to be able to make decisions to bring software into the company at some point, like in the last couple of decades, right? That shift is happening outside of development right now where the product manager, the designer, the operations manager is empowered to bring software. So the consumer use case, the personal use case is often overlapping with the work use case in that people are playing with these tools on the weekend. So they're building their own personal apps. And I'm like, oh, well, the moment you understand that you can solve a problem with code, it changes in mind.

Like almost there's like a neurological shift where you start looking at the world differently, where you go around and you're like, oh, I can solve this. I can fix this. I remember that when I looked at it. Yeah, exactly. And now that shift is happening in a huge part of the population.

And so it's the, you know, PLG play, I think, still the gold standard, just make a product that's really good that people want to recommend to their friends and make it easy to refer others, you know, build or for a program to all that stuff. And then on the sales side, a lot of it is very kind of sales assisted. So someone brings it to work. We talk to them. They're the champion.

We help them. It's like, okay, what do you need to convince your boss in order to bring this to work? Let's work with them to do a hackathon, to bring, create more champions inside the company. Let's work with you. Let's teach you leadership about AI.

So a lot of what our sales people are doing is evangelism, is education. So it's a different kind of sales motion, I think, than the previous one. So have enterprise sales that's more top down where a company comes to us. We're like, hey, we're trying all the different vibe-going tools. We heard it's a bit of our business.

Can you help us kind of evaluate replic? Are we going to that? And, and they're, we're often winning because replic has built a history of just like security, on compliance, all of that basic enterprise stuff you still, you still have to do. Let's talk about sort of what, what the limits are today of what you can do with a product like replic. Like what, what kind of systems can you build in replic?

And what do you still need to have sort of traditional software engineering approaches to? I can confidently say to any entrepreneur out there that you can build a SaaS product, a consumer product, like an automation product on replic comfortably. If you want to build like a new cloud platform, or you want to build like a new machine learning system, that's not exactly what we're focused on today. Some people still figure it out. Replic is a versatile tool.

We give you a virtual machine. We give you a general purpose agent. And if you have some technology, you can bring that and you can build sophisticated things. But if you want to build things entirely vibe-coded without worrying about technical details, we have so many examples on our website and what we talk about in our marketing. We, you know, there's so many success stories now that I can't confidently tell an entrepreneur with no technical knowledge that they can build a piece of software.

So there's a lot of consumer apps. There are a lot of, there are a lot of vertical SaaS products. There are people that are starting like replic native agencies. I was talking to someone from Iceland yesterday and he was telling me they're getting so much business because they're 60 to 70% cheaper and more effective than traditional agencies and they're all vicoting on replic. So they get a client that client wants an application.

Not everyone knows that they can build the application themselves. So they're going in. It's probably a period of time and they're able to make a lot of money that way. You know, the internal tools, automations, those tend to be kind of fairly simple programs like you're building an internal org chart. You're building a CPU system like a quote configurator where it's like pulling from hopspot or salesforce.

We have a lot of MCP integrations that allows to do that. How do those integrations work? Have you gone through and built integrations to all? Yes, yes. We spend a lot of time partnering with companies, building those integrations.

And now there's what's happening with the skills called revolution where companies are putting out skills and MCPs and we just vet them and integrating into the product. So as you're talking to replic, you're like, I don't want to integrate Stripe. So we already built a set of skills and sometimes code and things like that. We'll search the database, we'll bring all that in and now it's in context. The agent is like, it's sort of like Neo in the matrix where you download a new skill and you're like, oh, I know how to fly a helicopter now.

So it's so cool to see the agent. It's like, oh, let me search the set of skills that I have and suddenly it knows how to do that. But we spend a lot of time just making sure they're secure and they're safe. That makes sense, yeah. Having built a dev tool community, how is that different?

How do you build this sort of like groundswell of support to pull yourself into those organizations? Is it different than how you would have done it traditionally? It's a little different in that you need to show what's possible. I think with developers, with more traditional CS trained developers, they know what's possible. They'll read your docs, they'll figure out what's possible, their own hackernews all the time, and they'll generally kind of are much more resourceful in knowing what's possible.

With Reply, there's a lot of education that needs to be done. So we have like a DevRel team, but they're not the traditional DevRel, they're more like educators. They're like going and spending a lot of time just teaching people what's possible. Our documentation I think is a lot simpler than your typical dev tool documentation. So you have to be really good at content.

You know, Stripe got popular for this being really good on documentation. So with, if you're building a DevTools for non-developers, you have to go above and beyond on content. You have to produce a lot of video content as well. Also the agent itself needs to be imbued with characteristics that is able to talk to non-developers and tell them what's possible and be a brainstorming partner. So this is why we also moved from purely just prompting to also a canvas and more visual interface so that people can explore things more easily.

We have buttons as well as create different variations of this. So we're adding a lot of different shortcuts just to show people what's possible. On the enterprise side, when we go and we talk to leaders, we're like, reserve any judgment. We pay for a template. We're going to come in, bring the group that's most excited about AI and we're going to do a hackathon.

How do you see someone? How are you like, yes, this is going to be the person who's going to be so excited to use it? We think a lot about that because typically when you think about ICPs, you're thinking about, oh, that someone who's went to school for this degree or someone who's a product manager or something, which is still true, you can do that. But oftentimes because we're able to sell the sales department's marketing product design, the set of traits that we think makes it like the champion, the person who's most excited about a template, who's going to spread inside the organization, who's going to build, who's going to do the education evangelism, they tend to be very entrepreneurial. They're the kind of person that could start their own company, but they're able to be very influential internally.

They're kind of like what YC talks about, like PDSAs, like resourceful, someone who's not going to get blocked, who's going to figure out what other AI tool I need to integrate, what can I go learn or to figure it out. So that entrepreneurial kind of founder mindset, I think is very important. I mean, while we're on the topic of YC, I'd love to hear about your experience here. How did YC influence, how were uplits started and when it became? The main realization from YC is how much you can get done in three months.

So when we came in and Sam stood, he was still running a Sam stood in front of the batch and said, for the next three months, tell your friends, you're going to be missing. You're not going to be able to help them move. You'll come back into their lives later, but for the next three months, you need to be hyper focused on this company and you're going to be able to achieve great things if you really go intensely into it. When we did YC, we had the whiteboard and a countdown to Demoday and a number of just a very simple list of things we need to achieve. And every day we wake up, we erase that number and we change it to the countdown.

When it got into YC, it was still a REPL. That's the name. It was still just a command line with you just type a little bit code and run it. We actually don't YC. We already had web development, we had the initial aspect of hosting, we had code intelligence, we had so many sort of IDE features, it's got a lot more feature complete just in three months.

And that is an empowering thing, what we're talking about with programming, just the fact that, oh, you can be so intensely focused and you can work so hard and achieve so much in three months. And now, every agent release, it's not three months, it's more like four weeks where we bring everyone, because some people still kind of remote our other offices, bring everyone to the office, we provide breakfast, lunch and dinner, coffee 24-7, and we're just going to hit this very ambitious school. And that's the YC mentality. Another thing is the compound growth, especially when you're spinning up a new product or a new initiative. This idea of where PG came up with a number seven, but like 70% a week of growth, is a very good way to bootstrap a new product line.

So we're constantly going back to the YC basics and doing that, all that we learned here. Tell me about how did YC change your life? A few ways. One is before we got into YC, we couldn't raise all that much money. We raised maybe $500,000 and VCs did not want to meet us.

The doors were not really open for us. After YC, you immediately first of all, then we got introduced to a lot of VCs. And then we were lucky because we got rejected from YC three or four times and then we got invited to do YC because Paul and Sam saw us on Hacker News. And so we got a direct relationship with Paul and Sam and then at the end I was like, I want an intro to Mark and Dreezum. And you can still ask the partners here, they'll try a lot to get you into it.

I was bold enough to ask for that. And so they all went ahead breakfast at his house and pitched a rutlet and it immediately ended up bleeding our seat around. My network just expanded tremendously after getting into YC. And I don't think we would have been as successful without YC. Perhaps we would have quit if we were going to get a fundraise.

So it gave our company life. Yeah. For us it was very similar. We were complete outsiders. And I think having somebody sort of welcome you in made an enormous difference.

So you guys just announced Agent 4. So what is that like the fourth major revision of your product? Yeah. So we kind of an act of trying to predict the future. And based on what we've seen at the time, we thought that broadly the AI capabilities have massive step changes twice a year.

So if you think about 2025, there was a likelihood that it would happen in early 2025 and then there was the autonomous revolution that happened in late 2025 with Opus 4.6 that led to open claw and things like that. But I can tell you the same thing happened in 2024, mid-2024, clawed came out and clawed on it for the first time it could generate a lot of code, supposed to be like TP3.5, which has that laziness component. And then late 2024, we started seeing initial signs of the labs kind of doing long horizon reasoning. And so that observation, we went online a roadmap to AI capabilities.

And so every six months, we released a new agent version. And it's an act of predicting what's possible. It's also pushing the edge of what's possible. So for example, Agent 3 was the most autonomous agent on the market. We knew that autonomy was coming.

And we're like, OK, we want to be able to run the agent for like two, three, four hours. People should be able to put in a big prompt, go to launch, come back and see the software fully built. And so what do we need to do to update our platform? For example, we had to rewrite everything on the back end to have these long-running containers in the background doing work. Well, the user is not a part of the computer.

And so we did all of that work. And although autonomy didn't arrive until maybe true autonomy until November and December, Replit agents had demonstrated where the world is headed by September. So with Agent 4, there were a few things. One, parallel agents. We thought that was finally potentially possible to do parallel agents.

The thing that sucks about autonomy is that you can put in a big prompt, and you're kind of sitting back and just like watching it work. What do you do next? OK, so that question, what do you do next? Should we be able to design? Should we be able to kick off other types of work?

Should we be able to chat with your agent and plan for other things? And so we wanted a more asynchronous nature to the product. So we started building towards a multi-agent architecture and a parallel agent architecture. We had to solve merge conflicts and so many things to make that work. Also as the agent is building, we want to also unblock you from designing.

So we also had a more asynchronous design agent. And we're like, what is the best interface for that? So we designed this canvas. So now we have built-in design capability inside Replit to be able to explore the next page you're going to build, or the next feature we're going to build while the agent is building. And then once you're ready, you'll kick that off into another thread.

And it starts. So people are now sitting in front of Replit, and I'm just experiencing the state of flow. Because agents are slowly that's fine, but they can work in the background. And finally, teamwork. Once you solve parallel agents, you've also solved teamwork.

Because every time someone jumps into the session, you can start it in Todlingu, you can fork in Todlingu VM for them, and they can work in parallel to you. And also because the orchestrator knows how to subdivide tasks, you can also prompt in the same chat window and we'll figure out how to make all that work. And because we had the canvas, it was such a joy to just see other cursors and people. The product just becomes a lot more live. So all these components became agent four.

Oh, final one, I forgot. We wanted it so that when you make a mobile app, when you make a website, when you make a video, all of that should have the context of your project. Previously on Replit, and now every other tool, it's basically a different tool for a website, different tool for a mobile app. So now with Replit, you build a really cool web app. So maybe I need an app.

You can just say, make a mobile app. Like, generate a mobile app, and lay it out on the canvas. When you hit deploy, it deploys your web app to the web. It deploys your app to test flight or Android, whatever it is. So now you can run your entire company on Replit.

What kind of skills do people need to develop to be able to make the most of products like yours? What do people need to practice that? In your mind, is it good at prompting? Or is it more that the system is going to get better at just understanding whatever it is you're asking it to do? I actually think we're headed to a post-sponsing world.

And you even sense that in the open cloud and all the derivatives. And the way people are using it, they're more giving it high level goals, like optimize marketing funnel, things like that. So prompting will be there. It's like a layers of skills. Prompting will be there whenever you want to do more interactive type work.

But also, you should be able to give your agent high level commands. So I think perhaps, Agent 5, or maybe sooner, you should be able to tell Replit every day, build me, assess company, and try to market it and see what works and make me some revenue. You should be able to give it a title. I think we're almost there in order to be able to do that. So what kind of skills do you need?

Understanding what is possible is going to be important. So playing with these tools, having just like playful mindsets, of adopting these tools, playing around with it, being plugged in is super important. At some point, I think it was kind of a drawback or a flaw to be someone who's constantly reading news or being online. But actually, now it's very important to know what's happening, what's coming down the line. I think not giving up is important.

The thing that you try to do today, the day I cannot do, try it again and month. And I tell some Replit users, if whatever you're trying to build, Replit can be built today, try it in a couple of weeks. It might be able to build it. And so that mindset of I'm going to keep trying is important. ID generation is still going to be important.

Obviously, we're going to get to a point where AI is going to be really good at helping you generate ideas. But being generative, just constantly thinking about problems you want to solve, and being creative and thinking about what does the world need right now. And being generative is important because, let's say you're a small-time entrepreneur, peer-level type of entrepreneur, or this guy is very famous on Twitter who builds these products. Oftentimes, the products go through cycles. We build a product that is really good for that moment.

And you can generate a couple million dollars, but then that product is no longer irrelevant. So you need to be generative and creative in order to continuously do that. And you can make millions of dollars doing that. If you were starting Replit today, what would you do differently? I mean, I made a lot of mistakes along the way.

So if I was starting Replit today, I'd probably hope not to make it a mistake. So culture is very important. At some point, we screwed that up, and we had to do a reset and layoff and all of that stuff. I think being really honest with yourself about product market fit is very important. It's very easy to dilute yourself.

Any kind of user is an amazing achievement. Getting any money from users is also an amazing achievement. You should celebrate every one of those moments. But true product market fit is entirely different. It's an explosive thing.

And so being honest about that, because we've had periods of like, oh, it looks like that successful. Maybe it's working. And you keep going down that path. But in reality, you should have changed directions a little earlier. It works.

It really works. In terms of AI development, AI technology, what is something that you are waiting for? Where you're like, this is going to unlock so much. I've been waiting for computer use models to get better. They're slowly getting better.

They're like one of the things that is actually kind of disappointing. It's surprising to me that it's so hard to build them. You think it would be the easiest thing in the world to get data for. Do you have a sense of why that is? Well, language is a lot easier.

Which also much more can be compressed down into high-dimensional space a lot easier than video feeds. But still, if we can make progress on self-driving, surely we can make progress on moving them out and clicking on things. So I think it's a little bit of a mystery. That being said, coding in coding agents turned to be a workaround and hack. Because a lot of things that you could do in front of the computer, you could do with code, including scripting and Excel sheet.

The reason Excel sheet agents got better is because coding got better. The reason some conversations are starting to work is because they could call APIs and they could, so coding turned out to be a bit of a hack or workaround computer use agents. But there's still a lot of software in the world that's very likely to software that computer use agents would be really good at. Also when you're creating a vibescoting platform like Replet, you want to be able to test the apps that you are making. And you want to be able to be discerning as well, things that are functionally right but also you actually are not very well.

You want to be able to give the user feedback on that. But the models are not very good at that. So we spend a lot of time. It's a taste question I think. So we spend a lot of time prompting and augmenting computer use models in order to make them good at testing because Replet has a testing agent.

So that's one that I think will unlock a lot of different capabilities once we get to computer use agents. I think it's become a buzzword but like continual learning. The way we're hacking around it right now is we're writing to files. The agent will learn some kind of scale and write a scale MD file or something like that. But true learning on the job has not been unlocked yet.

So for us to be able to deploy an agent inside an organization and for that agent just continues to get better for that org itself is such a powerful thing. But that just still seems far away. I think one of the common things I'm hearing here is we already have today with Replet like agents to build software and you talked about how we're increasing the abstraction until finally you can just say, hey, I want a company that just makes money. How is this going to work? What does that leave left for people?

And what does the company of the future look like if it's all just agents all the way down? I think the company of the future is made of builders and salespeople broadly. Sales will change and sales will be more like, let's help companies transform. Let's use the technology that we're building here to help companies transform. So salespeople are more like, I mentioned earlier, more like evangelists, more like educators.

But I don't think that part is going to go away because a lot of other companies will want to talk to someone, will want to learn from someone, right? That's how a lot of people learn. And they trust other humans. So the sales probably part is one of the more defensible jobs. Interesting.

And then builders, there's always more to automate. I think our job will continue to get higher and higher level. I mean, that's already the case that with computers, we became a lot more high levels. Computers were literally humans, right? There was a bunch of people doing computations.

Tables of numbers. And then we're like, you take that entire room and you put it in a box, that's computer. And now there's my job as the operator of the computer to use a computer for productive use. And there was a lot of still manual work in order to make that computer do interesting things. And so we have a lot of software.

And now we have an agent that's using that computer to use different layers of abstractions. I don't know when you have a fully autonomous company. Maybe at some point there's certain styles of companies that could be fully autonomous. But I think you need business generalists that understand customers, understand what people need, understand the economy, understand what the world's had to understand. AI, technology, have some vision.

And you want to give them. So here's like the abstract vision of a future company. It's like almost everyone is a founder. They wake up in the morning and they think how can I make the company more successful? How can I make the company make more revenue?

And then they go around the company finding problems to solve and then creating or deputizing agents in order to go solve these problems. We're already seeing that. We actually have a team, like a vibecoding and residency med-replant. And they have a very vague mission, unlike a product team or sales team, which is very clear. Go around the company, make it better.

So they went to the support team and was like, okay, you're using Zendax and all these other tools. What are the main problems? We're like, well, we don't have a good way to prioritize our support queue. For example, there are customers that are paying much more than other customers and there are customers that have more urgent tickets. And so they built a way to visualize that and create more priority queues.

And they spent some time with the support team and the CSAT score starting up. And then they go around and they charge our team. What are the problems? Well, onboarding is a problem. There's no place for people to know all the benefits and everything that we have.

Well, let's build an HR and turn on HR platform. So they do that. And I think that kind of role is more where the future is headed and more and more people inside a company will be more generalist entrepreneurs that are trying to make a business accessible. Well, thank you very much for joining me. Pleasure to have you here at YC.

I appreciate it. Thank you.

Frequently asked questions

How long is this episode of Y Combinator Startup Podcast?

This episode is 39 minutes long.

When was this Y Combinator Startup Podcast episode published?

This episode was published on April 25, 2026.

Is there a transcript available for this episode?

Yes, a full transcript is available for this episode. You can read the complete transcript on the episode page.

Can I download this Y Combinator Startup Podcast episode?

Yes. Use the download control on the episode player to save the publisher-provided media file.