So I think now we are just truly seeing this unlock where people who are like really close to the problem domain expert and but have been blocked by technology barrier to sort of really express themselves are using emergency to build these things out. There's just so much focus on AI is going to replace jobs and knowledge work is going away. Like what's that going to mean for employment and civil unrest. But no one's really talking about the fact that actually if you have like some agency of interest and want to start your own business and have autonomy of your life, like you are empowering that scale. Welcome back to another episode of the like on unfortunately Gary got called to Jersey and can't be here with us today.
But we are really excited to be joined by Mccund and Madav Jha. They're twin brothers and founders of Emergent which went through IC in 7 2024. Emergence platform that lets anyone build and ship production ready software using AI agents. You guys are actually one of the fastest growing companies. I believe why he's ever funded.
I mean the statistics you were telling us were mind blowing. Do you have in eight months since launch seven million apps have been built with Emergent walk us through this like incredible growth. You're seeing actually when did that hit a real inflection point and how did that feel for you guys. So we both like twin brothers. We actually started programming in age 12.
Both of us came to US2.psd's I dropped out of the basic program joined Google and Mary went on to start the deep learning team at Amazon and we've been doing it a long time. And before this I was running a startup in India called Dunzo which was a high-profile big commerce company. Dunzo was a big company actually. It was very big and we were almost a world in India. People should think they say Dunzo it.
And I was planning a really large team of three engineers. We have been supporting deep learning field for a while and we knew inflection point is coming. One of the things that I observed when I was running this large engineering team was that software testing was the biggest bottleneck in shipping fast. So when we started looking at what we want to build in AI. What year was this?
This was 23.0. And so when we applied to YC we applied with this idea of automating software testing. That was the first idea. In fact we went to a lot of VCs with this idea. They thought it was too crazy.
And now looking back it almost looks funny. So we applied to YC with this idea and when we were building this testing agents we realized that if you can solve for verification. Which is essentially you can solve the testing part. You can actually automate all the software engineering. That was sort of key insight.
That verification is the loop which keeps agent running for a long period of time. And that's when we pivoted to looking at general coding agent as a space. And we started building general coding agent. And this seems in 2024. This is what the landscape looks like.
How big was lovable at this point? I think nobody had started. I think I was just getting started. And very early I think they haven't had just come out. So really early early.
And we looked at this benchmark called Sweetbench. Which essentially a benchmark now it's saturated. But at that point that was the benchmark where all the coding agents were getting measured on. And we took on this challenge of becoming a member of the benchmark. And we packed our standard room for a fast.
And so let's look at this benchmark. How do we crack it? That's what set the foundation for a module. And we built sort of coding agents which became world number one on Sweetbench in two months of time. And that was time when we discovered a lot of the fundamental tools about building the land building with agents.
You're intended to use of this point of a presuming engine is. Yeah, at that point we were like the only research company that's building coding agents. We were not thinking about a product. There was time when we sort of invented the multi-agent system. We invented memory.
We invented like how do we do agent-agent communication? How do you scale up their time compute? A lot of those things which were sort of coming out. We would just come up with something and see three months later. Come on in the paper.
And that's what set the foundation for us to. We had like cloud code before cloud code was a thing. A bunch of the patterns like multi-agent orchestration. How do you use different different notings. A lot of those things we sort of discovered.
I definitely want to come back to that. I'm curious to find the story. When did you pivot into becoming a tool for non-technical users? Yeah. Once we had this coding agent, we actually went to enterprise.
That was the common wisdom at that point. That hey, go to enterprise, build for enterprise. And we spent like three months trying to make our agents work in enterprise. We found that it was too slow. At the same time we were internally started using emergence platform to build internal tools and internal software.
At that point, we saw a lot of those going crazy. Bolt was going crazy. So we thought, hey, we have this really strong coding agent. How do we sort of package it and bring it out in the world. And we launched a very small beta pilot almost in June last year, 2025.
And that really took off. And since then we've been just focused on solving problem for non-consulipity. In fact, a lot of tech people use us. Today, 80% of users who are on the platform are non-technical users with zero programming knowledge and they're building apps that run real businesses on top of today. So it's almost been a great job.
And they're based around the world, right? How many countries? Yeah, so there are global audience 80%, 70% are in US, you're up, one 90 countries right now. Something that we have talked about in chat at YC internally is just how does first-mover advantage versus second-mover advantage play out in the AI world? It's only something that we've noticed, like if we look at some of our company, Lagora entered the legal AI space after Harvey, but it's growing incredibly fast.
So there was clearly, it wasn't maybe as big of a mode around being a first-mover as you traditionally think there isn't software. And you guys made that sort of pivotal, that slight change in direction into non-technical users at a time, a lot of all in bold and growing really quickly. How did you think about that? There are two different different friends that I would want to pull. One, essentially, is that I think the model, every new model generation is presenting a new opportunity of looking at the world.
Like, for example, when we started, GBP4 was the first one that we started looking at. And then the biggest problem that everybody was trying to solve was just on-parsec, like structured output format. And we thought, okay, the next model is going to solve for it. Let's not spend time on that. And I think with every new model, what's happening is that you need to start imagining the world.
And it's going to enable extremely long horizon tasks. It's going to enable multiple agents working together. And so I think one of the advantages of starting second is that you can actually learn from what is not working for the current competition. And also, I think you fundamentally start from a different starting point. Your aperture of the world is very different.
Your imagination is really big. And then we were starting, I mentioned, we realized that a lot of the users that are going to solve these apps, they wanted to actually build an app that works. And most of these were actually really optimized for front and pro typing at that point. So besides finally realizing that, what would it look like if you could actually ship things to production. And our key insight was that to automate software engineering, you will have to build a platform that replicates what best engineering can do, like code reviews, automated testing, debugging, deployment, security hosting.
So we re-imagined the entire platform from ground up saying what would an end-to-end platform look like. And the real user need was actually to ship the product, not just the front and pro typing. I think second thing is like how do you sort of get the distribution, because it comes from behind. So even if your product is really strong. And fundamentally, you'll have to enter the market with a really strong product, which is head and shoulder above what is in the market for people to take notice.
We were very confident about the product. And so a lot of focus in the early days, once we launched was on how to be sort of rapidly scaled up distribution, we built out a large influencer network. And there was our initial sort of starting point for us, like we used TikTok and Instagram. And part of this much influencer is to really spread the word out. And that sort of started the whole thing for us.
So to me, building the influencer marketing engine is like, it's like tactics to land crap. Like were you also thinking about just focusing on personas and specific types of users you wanted to go after that weren't either weren't being targeted by the ball or others or emerged with a benefit for them? I mean, our thesis was that there are a lot of users who would want to build serious applications. And that was our target audience. And a lot of our marketing, a lot of our initial messaging was around that, like a common ship real software.
What we did was a little bit broad days like marketing. But users that would come to platform that we would convert, were users who actually wanted to ship a real app on the platform. And it was that in the messaging then? It was in the messaging. So we would say, come and build real apps.
We would also use the common errors that you would see on the platform. Don't face this as an emergent. It seems like a key insight for you. Basically, you went very hardcore in terms of being maximalists in engineering from your experience having run large engineering teams with 300 engineers, having worked on deep learning teams at Amazon. You really knew how to architect the systems.
Can you maybe share a bit how you built it? One of the cons of all these other big products like local or both is just that it's difficult to get those into a fully usable. You can get to a product very quickly. But you're as you went 0 to 100% very quickly. And that takes finesse.
It's almost like that. 20% gets 80% effort like the very principal. But you did more than that. The last 20% of that engineering, the production was a lot of work. That's a lot.
And I think the last one that you mentioned is always what people neglect. That, hey, you need to make sure that not only app gets built, it also gets deployed. And this is one of the conscious reasons why we chose to build our own infra on which the agent is running. So we provide like, you know, clubs and boxes. We don't associate to like some 30 cent box wider, which was also pretty popular at that time.
So we built our own Kubernetes tech stack from ground up, the container tech stack. And one of the insights here is that if you give your agents the same in front during the build time and the same in front during the deploy time, then the sort of like, during this like deployment phase, you don't encounter those many problems, right? And the fact that we have our own infra also allows us to give like rapid feedback with the agent. So your agent is only as good as a feedback that you provide. So we built this like sort of infra agent, like sort of go build it together and from day one and to a point, right?
Like, because we focus on building like ship ID apps, which are production ready, it has which comes with backend and front end and everything. The tech stack which was also pretty unique to us. We have a Python backend server. We have a React front and server. Like most people would like typically go with like a much more like, you know, node focus, not heavy tech stack, right?
And this like server client architecture where you can have like background jobs if you want to have background queues. So we knew that users would use this app. Their amissants are going to go bigger and bigger, right? Hey, I want to run a job which can like do this or asynchronous video processing, you know, and they're going to prompt it and you want to support it from day one, right? And so it's the same tech stack on which Immulgent is built is what we expose to our end users, is what we expose to our agents, right?
On the agent side, we were very early on the multi agent architecture. So we knew that you want to be very, we got about your context management. So what you do is, hey, let the main agent that driving agent handle the main routine, but any delegated task that you want to delegate to a sub agent, be it like testing, be it like, hey, I want to do a design search or I want to do like, you know, integration search, like how do I integrate this unique API? And along the way, when you were like finding out, we were able to figure out, okay, all the trajectories that we are generating, we can kind of aggregate over time and like sort of build a long term memory for the agent, which is very unique in the sense that your agent learns not just from your own session, it learns across the sessions. This is something I would say is one variant of continual learning that people are like interested in now.
You would have noticed that people are interested in skills like people create like skills and the there's a new benchmark called skills bench, which shows like agent with skills outperform agent without skills. And interestingly, like those skills cannot be generated by agent themselves. Like if you generate those skills by agents, they don't like match up to the performance. So we were able to do it in a way where the skills get auto, you know, sort of be generated based on previous trajectories and we run it for CICD process and then add it to the long term memory. So all of that like compounds for us.
So if you're agent was struggling to do a calendar innovation three weeks ago, today it is no longer struggling thanks to the previous session where it was able to make it happen. So fascinating. So it learns on its own because I think one of the challenges of all these Vibe coding platforms is at some point the application gets so complex that if you build it very simply, you would run out of the context window for all the models because that seemed to be the bottleneck. And I think you guys architected your way out. So you kind of build a lot of what the state of the art is now, but way back a year before.
But according to the support that we basically internally use it as a replacement for code as developers. So we are so proud of that. But yet we don't want to expose that sort of power tool to our end non-technical user. And so even though we have this VS code editor, we kind of hide it because what we've noticed is that non-technical users, they even get panicked as soon as they see a diff. We had a fairly technical PM in our team and he doesn't like JSON, you know, don't show me, I get intimidated.
So building that user empathy where you have that user empathy and building that agent empathy. You also have to empathize with your agents. What does agent feel like? I mean, we only have a term called agent experience. Let me measure that out.
How is agent experience on the platform? Actually, a really important point I think people don't realize is you guys actually started out essentially as sort of Devin cursor in the actual coding agent world for engineers. You just made the choice to package it up for non-technical users. So you're sort of moving almost in the opposite direction from like a level board. You have all of the actual power.
You just need to simplify the user experience. Whereas they sort of have the start with the user experience and they're going to have to develop the power over time. Right. And I think fundamentally it's like unless you start from a starting point which sort of all of these problems along the line, the whole software development cycle, it's actually really hard to come from the other side and solve these problems because you'll make some architecture choices which are very hard to reverse. Do you have any more examples of where as you're engineering the system you just trust in the model?
Like you mentioned Jason passing but was there anything else where you like let's not invest time in that because like if it's 4.5 or what's all that? Some of them has been for example, you know, like library definition, some of the integration that we have built, like we think that next model is solving for us. Similarly, like how do you generate unit tests? Some of those things that we actually would have heavily prompted before. And the other thing that we are very conscious of is that how do we give more and more autonomy to the models as the next generation come out?
And the more time you're able to get to the models, the better they perform, initially the harness was very strict and you know, we would tighten it up and slowly what we're observing is that as this model is getting larger and larger, more efficient, the more control you get to the model, this will make the better the harness gets. If we extrapolate that out also really far out, are you worried about where that sort of leaves you as a company versus the models themselves and models get more powerful? Yeah, I think there is this underlying current right now, like in the industry that is anthropically everybody else. I mean, I think the coding aspect is only 20% of the job, right? I think in after production is really, really hard.
And I think what matters is how closely are you working with the user, how well you understand their needs. And I think as the models are going to get more and more sort of capable, I think the human desire is also going to be growing at the same rate. So I think people are going to build more complex apps on the platform. The other thing is that it is the harness will be able to extract many of these models and essentially we can use multiple foundation models together to sort of extract more. And I think we'll have to keep delivering more and more things to our users.
For example, now we're thinking about a lot of users who have built the app now want to help a distribution, now want to help with growth, now want to help with how do you manage users and things like that. And I think for us, these spectrum groups are going on that side. I agree with that. I mean, there's another graph that I was sure shared recently. It's just like the number of software engineering positions that was actually going up, right?
And I feel like at least in turning out why see you're experiencing this. It's like the more powerful the tools get, the more ideas you get and the more work you want to do and it just feels like everyone here is working like more hours and more stuff. And it's just like the rate of like software that you're expected to ship that we just going up and up and up. It's actually a hedonistic adaptation to, you know, like, hey, this is more powerful, like in the more work. Yeah.
I think there's a lot of concerns that go, this opportunity jobs will be gone. I don't think that's the case. I mean, based on everything that you're telling us and what we're experiencing. I mean, I think we're an expanding market, like we are like letting non-developers not be developers. I think that market is expanding.
We also are internally seeing like the role of combining, like a PM, a designer, engineer, like a single person is doing, you know, like we're all three together. Right. So like we have a PM who's like putting internally things and recently like we, so we are seeing this internally like now where a lot of the work that was done by like five, six people to be just done by like single engineer or single PM. YC's next batch is now taking applications. Got to start up in you.
Apply at ycombinator.com slash apply. It's never too early and filling out the app will level up your idea. Okay. Back to the video. Can we see a demo of a merchant?
Oh, yeah. Sure. Yeah. So this is how what emerging interface looks like and I'm going to like what a prompt where like because we are coming for this podcast, we thought like, you know, there should be an app which lets you practice, you know, podcast questions or maybe you're going to a job interview and you want to practice questions, right? So you can build a full stack app on emerging, you can build a mobile app.
Our prompt engine is smart enough that once you give it a prompt, it will figure out that this is talking about a mobile app. So it will figure out like the right agent to use is a mobile app builder. So even though you selected the wrong tab, it's just like, yeah, yeah, yeah, the same photo. Yeah, I got you. Right.
So while this is running, let me quickly also show you a few user apps. This is why somebody pays out of Illinois. He's a sort of other business of audio video setup that they do as manually. Right. So basically, whatever this kind of like intake form they would have taken through spreadsheet and other calls, they basically build this out without any coding background knowledge.
Right. Like, Hey, this is the kind of any setup I want. So you go and you build your room and then you get a legit sort of a form, but this is a fairly full stack up. What? And it's about that.
It's like the design is really good. Like the icons, like it just like it looks like a well designed app. We have actually spent a lot of time on design is actually good. Yeah. Like, so earlier this will be trained up between design and functionality.
Like if you're optimizing for design, like functionality would not be that strong. And so we had to figure out like how to sort of share the context in a way where design also gets better. There's another person based out of Norway. He sold his business to a PE and realized how much lawyers have to struggle with spreadsheets and other things. So he built a CRM for lawyers.
He described himself as like business developer. I like the word he used like I'm a business developer. He doesn't have programming background. So a lot of CRM related apps, we are seeing small businesses. It's your second monetization avenue.
And so like one of the unique things we mentioned is that before Asian goals of the build things, it asks you for some clarification because it wants to make sure that it understood your requirements properly. And another thing is that non technical users probably don't know the concept of API key. How do I get an open API key? So in this particular case, I can just say, hey, use emergent LLM key. So you don't have to worry about getting API key from third party.
It's also a huge example what you're saying. Because it's sort of like the ask me to question skill and call code, but you just like I've swept that away. Yes. Like build into the experience for someone who had no idea about. Absolutely.
I can be very like casually like I can say, hey, for the first one use emergent API key, that's as good defaults and then go. This is the first time I hand off the agent. And like at this point, I can just like close my laptop. We also have a mobile app. So you can like on the go keep trying to prompt agent if agent requires additional thing.
Once it's done, you see a preview of your app. So here, for example, in this case, I can practice what is my origin story. I can record what my origin story is and I can keep going to various questions. Eventually, there's a podcast preparation app. Yeah.
And then you can go ahead and revisit what answers you gave to your app. And so what we've noticed is that a lot of personal apps people use people build mobile apps, but a lot of business apps, they would go and build our web app. Right. So that's generally the trend we are seeing. The only other thing I wanted to show was this is an actual Asana clone that our team built, like one of our QA engineers built internally.
And so this is actually really much in data. I'm curious what prompted that. Like was there some feature that Asana was lacking or something he wasn't doing that made them say, hey, we should just build around. Yeah, it kind of like started off as a QA engineer's curiosity. He like his first prompt, I looked at his all jobs.
The first prompt was clone Jira. Okay. And then like he just kept going with that. And I think the other thing is we do things a little bit differently. For example, we ship like three times a day morning evening night.
Kind of like build it very customized to the way we do things like we have a QA involvement in many, many ways. And definitely like when we use Asana, it was very like even to customize it to make it to your work style. It was not easy. And we are also saving like $3,400 a month in the description. Yeah.
Yeah. Has anybody actually edited the code for this or is this 100% built with the merchant? 100% built with the merchant. And the good thing is that if I want to add a feature, I have to just go to that project and just add a feature and just start building. It's probably useful for you guys to do the platform this way because this is probably at the edge of the most complex apps people have built with the merchant.
So it allows you to test what happens when people get to a very complex app like this. In fact, a lot of the teams in Tony are not building apps using a merchant in Tony. So we have a marketing team built out of completely built on a merchant. We are now like a customer support team is building customer support software completely built on a merchant. And the power is that these are people who are close to the problem, who understand the problem really well and are able to now build these apps.
And this we are able to ship these internal apps is crazy. How far down does it go down? I'm curious, even within the company, do you have people who want their separate versions of your internal Asana? So currently everybody in the company is using this one tool right now. And it is being built collaboratively.
So like a PM can give a feature, a key way to give a feature, somebody from starting to build that out right now. How do you think there's version control, like feature planning, all this stuff develops in a while, anyone could just write a couple sentences to update the software they're using? Yeah, so there is a testing phase that is deployment phase. We have different versions maintained. And there is a primary owner of the software who actually manages this right now.
And so somebody will make a feature request, somebody will sort of build that out, and then once it's accepted, it'll go to release. It's not managed to get though. It's like your own workflow thing. So you can get up if you want to. We internally get up for our projects.
And non-technical developers outside of the merchant, they actually call GitHub GitHub. Right? So they have very limited knowledge of GitHub. And so we take care of our site, even if they don't get out. So we're talking about how you run your team.
The way you hire must be very different. I mean, you're very lean and small team. How do you hire for engineering? Yes, we actually from day one have been very conscious of the kind of thing that we want to build. And essentially we index on two things.
One is something like how good are you at problem solving. And second is ownership. We think that people who can really take ownership, you know, like index on that. And a lot of our leaders sort of hires were people like, you know, really obsessed with top 100 IT anchors. So we had this like programming on where like, I think that we must hire like top 100 IT anchors.
Right now we have like IT rank one, I rank 12, all those people working with us. And not only the issues that I was getting from them, so I, because I was able to build a really good team, we were able to get some issues from that. The focus that we have is essentially like one or two people doing work of what a company would be doing. For example, I deployment with almost matters, what we're still looking like is done by two people. Like our memory, like, we have like one of the startups solving for memory is just built by one person.
So I think like we have way more responsibility to people. And I think we are generally attracted to harder problems that they want to solve. Where is your team located? So most of the team right now is in Bangalore, in your office. We have a very small office in their self, like three to five people here.
And you guys yourselves, you're kind of like split across both countries. Can you maybe just explain how the setup works? Yeah, so I mean, I live here in a self. I've been in like, you know, in a beer for like last 10 years. Actually, the half my time in a self, half my time in Bangalore constantly jet lag.
I think you guys are probably the most successful AI company that's, it's obviously came from like, it's an Indian company, but that's got like, sniffkin presents in India. Why is that? I'm not even back to India after Google. And I always had this thought that why is there no Google or Facebook for India. Right. So like from day zero, I was thinking, you know, I saw it done.
So it was an India focus company at that time. And when I was starting the second company, I was like, hey, there has to be, you know, like, we have so much talent. We have, you know, a lot of capital available. Everything is available in there. Like why are people not building global tech for companies from India?
And that was the ambition that we started with. And in my opinion, I think it was with, you know, like just to your ambition. Like if you just mean very, if you're able to sort of really, really think global from day zero. I think now because internet is sort of fully connected to it. People can actually get understanding all this from everywhere.
Every single country has their ability to build global audience. And if you have that sort of mindset that I mentioned, I think a lot, I mean, a lot more companies coming up in India are doing the same. I'm curious to hear what it's actually like sort of on the ground running this sort of like split country company where the team is mostly in India, but the product is overwhelmingly used in the US and Western Europe is not a private Indian market at all. What is it like running this company? How would it be different if you had built a normal Silicon Valley style company that was all based here?
Intelli, we have like really, really high standards like as a global sort of product. I mean, both in hiring, both in like the way we sort of developed products. And I think our spending sort of time here also also helps. Like one of the things that we do really, really, really justly is everybody talks to a customer once a week, twice a week. Everyone in the company, right?
They talk to customer, everybody does customer support. So like, we were like a really, really small engineering team, like 12 people, and one person was always on call for customer support. It was really hard to think for us because you know, you're a really small team, you should really fast and then move, like one of your best thing is out. The customer support is really hard, but I think that really helped us build the customer empathy from zero. And I think given that like one of our distribution happens online, like, you know, like the things I'm able to learn from digital things.
And I think, but I think us building the customer empathy from zero, like talking to our users, like really helps us build the gap in terms of like what are you just want today. And it's funny because like when we launched my first like five days, I was just new to a customer support only. And most of the customer requests were coming in a different language, like French, German, and a lot of these were global. And thanks to the people who understand that, reply to that. And I think that is also helping us to build the gap there.
And we are hiring here in SF. So if anybody's interested in joining various positions like B8 research across the board, like back in engineers, front end engineers, we are hiring here in SF and in Bangalore. I was talking about regarding personal software. And what do you think applications are for SaaS in general? I think the provocative question is, is SaaS dead now?
I mean, you guys essentially killed a SaaS for yourself, but is that bad for a SaaS company? I think that the current way SaaS is existing to it needs to change. I think like I feel there are two massive events. One is more and more of these SaaS workflows are going to get consumed by an agent. Like so, like, you know, unless you're a SaaS company, if it's into like an agent first company, I think that's going to be hard to sort of survive.
And second-hand is obviously, like, you know, like people would want more and more customer software, like they can build a margin just like we built our own do it. And we're seeing a lot of these people building these internal tools, the software on that like ours. And I feel the nature of software itself is changing. I think a lot more software will become agent taken nature. A lot of people are building on emerging today.
Like roughly 20% of them are actually agent taken apps. So people are actually embedding our own emerging agent inside those apps to sort of, you know, about a bunch of the workflows. Just so interesting, that's really cool. An interesting example of the people do that. I mean, like the app that my viewers are showing, you know, the CRM for lawyers that is an agent taken app where an agent can take a workflow and then run through the process.
The software itself is not more than agent taken, like a lot of people just want to build agents that can actually just do, you know, not more of the work on so. What do you think this goes as agents horizon for tasks gets longer longer than one of the the new chart is one of the ones that was very shocking recently? Yeah, I think that's the chart of the year, I would say, like the meters exponential growth and like 4.5 was at like I think four hours and 4.6 is at 10 hours. And we're going to tell you sort of now like experimenting with agents forms where agents can actually like work for much longer horizon and multiple agents can sort of coordinate or single task. I think it's like pretty, pretty exciting.
I think by the year you'll have agents which are going for hours and maybe hundreds of agents collaborating with a single task. That's why we sort of see the future going right now. How are you building for that? People are just increasing, like we want to like get agents more autonomy, right? And so like the main thing is to make sure that the city doesn't get derailed.
So you always want to have like an overseeing agent, right? So it's like, let's say a few agents are collaborating and there's an overseeing agent as well, which is like parallely monitoring the overall task. So we are experimenting with many different architectures, right? Something even as simple as like just, you know, you would have heard of this Ralf Vigam loop kind of phenomenon, right? Like so the idea that they like just keep working the agent here, continue until it's done.
And all of that is only possible if there is a good verification loop, right? So it comes back to hey, are you able to give autonomous verification feedback to the agent? Like was the job done? So a lot of our work internally right now is in fact still going on building best verifiers. There we are actually doing some custom fine tuning as well.
So we are very careful about like not directly competing with the models in a sense that we don't like build a 4.5 alternative right away. But we do want to augment it through our custom fine tuning verification layers. So some of the fun stuff we on the research side you're doing is on that side. How do you think about some movement in the opposite direction? We talked about the models themselves, maybe getting more powerful and what does that mean for everyone building on top of them?
But how about at least some of the model companies are especially trying to build applications and only application layer themselves? If one of those companies decides like you know, cloud code for non-technical users is really valuable application to build. What implications does that have for you? I think eventually I think like do you understand your customers require a really really well? I think all the fundamentals of like sort of building are the same.
And I think for us, like as long as we focus on like really understanding users need really best, I think we'll be the best. Do you think about all the model companies is the same or the differences between them? If you look at the models themselves, like they're very different. Like for example, Opus is obviously a workhorse. Like Codex is really good in back end debugging, Geomnies really good in front end.
So I think all of these models have their own behaviors and one of the good thing for us is that we can actually utilize these spikes that model have to provide the best experience to the user. And I think eventually at least my worldview is that most of these models are going to get really, really, to get all these models to have some of the behaviors. They'll have price, price, competitiveness between them. And you can already see like, you know, like open source like maybe three to six was behind. Right. And there's enough optionality for us to sort of really build the layer on top where we really meet the user where they are and sort of support them in sort of their journey.
Who understand the customer needs really, really well and is able to build for that is going to sort of win this space. Users have built seven million apps with emerging. What are all these apps? Who are the users and what surprised you seeing what people do with it? The users who are coming to platform for us are generally people who want to build a series of people who really have a business use case that they want to automate or they have a business idea that they want to launch.
Primary users who are coming to us are small, medium business owners. They're running the business today on email, WhatsApp, spreadsheet and would have gone to a Dev Shop to sort of build a custom software. To run automate their business. They're coming to us. And if you look at the price point that you know, we're being down, it will cost you like $5,000 to build a software now.
You can build it for $5,000 completely on your own. And that is kind of, you know, like a lot that we are sort of bringing to the world right now. Second, for example, this morning I was talking to a user, Fisty, she's based off of Alaska and she built this. She's a clinical psychologist. She's also a sports sport for equestrian, the horse riding and she wanted to marry these two fields like, you know, like that.
She has all the insights on psychology side, she's on the side on horse riding side and she looks around everywhere to find out that that she can find one. She actually went to a Dev Shop. She went to a Dev Shop in Nova Scotia and I defined somebody who can build it. They were charging her a bomb. So she discovered a merchant, started building it out and she just launched her app a couple of weeks back.
It's called EP Mind on App Store. And it actually marries her in psychology and sports coaching. She has tons of views of that you think. I think that is a lot of people who would have been, who have had the idea for a long time, who are really domain expert, very close to a problem, can now go and build things up. We also have a lot of solarpreneurs, billion platform, who would have had to go and hire a technical CTO to build these apps.
And the success that we are seeing on the platform is somebody being made like, this company has raised $4 million on an ad that was built on Immersion. Really? And I need to get the permission to share more. So I think now we are just truly seeing this unlock where people who are really close to a problem are going to be explored. But have been blocked by technology barriers to sort of really express themselves are using Immersion to sort of build these things out.
And also one thing these people tell us that it's not just about money, like, I can give money to the Dev Shop, but a lot of not get lost in the translation. And I can express your idea to the developer and say, I know what I want to build. If I could just say out my, out loud myself, I would do a better job. And so the Norwegian person I was talking about, like he said that, hey, in my team, I am the only builder. I don't even bring in anybody else because I know exactly what to build.
And like, other focus on the business aspect of it. So there's like single, sort of attitude of like, I'm going to build myself, I have to do it myself. Nothing is lost in translation. That kind of agency is what people are looking forward to with these kind of platforms. Yeah, I think it's a really important story that doesn't get told enough actually is that your building is really necessary for society.
Now, there's just so much focus on AI is going to replace jobs and knowledge work is going away. Like what's that going to mean for employment and civil unrest? No one's really talking about the fact that actually, if you're at like some agency of interest and you want to start your own business and have autonomy of your life, like you are empowering that scale. Is so cool that like amount of human creativity that you're unlocking, like who would have thought that the thing that the world needs is an app that marries clinical psychology with horse right now. And in a world of limited software that I would never have been built in a world of unlimited software, you can build that and 7 million other apps that like nobody would have ever gotten to before.
Yeah, I'm looking at the niche of niche of niche. Just an extension that TrendPG wrote about a while ago, right? And so like maybe coming out of the Second World War, you had a few big companies and people built whole careers, hopefully saying IBM or whatever for a couple of decades and then retire. Then the startup wave came along and something like the world becomes higher resolution. People are like, I mean, I should start my own company or at least join a smaller company and work at multiple companies or found multiple companies.
And the next extension of that is just everybody runs their own business that's at the intersection of clinical psychology and horse riding and finds an audience and life that way. I'm excited about so many ideas coming to life. I really want to reduce this gap of an idea and reality and to enable people to express themselves and really, really have this kind of explosion of ideas, which is great for my C. I don't know how you don't have to be actually. I think it's really interesting, the whole like explosion of being able to start businesses that aren't venture fund data, that's a capital.
It's just like one person following their passions and having control over their life and it's really an uplifting message. I think just an early innings of this, right now, I think the technicians are going to grow and we'll see larger and larger projects being built on emergency. Okay, well, that's all we have time for today. Mukerna Madar, thank you so much for joining us. It was a really fascinating conversation and congratulations on all the growth and we're excited to see where things go from here.
Thank you so much for having us.