One Developer Got Thousands of Users Before His App Launched
Naveen Naidoo, a solo developer and entrepreneur-in-residence at Every, built Monologue, an AI-powered text-to-speech app that reached 1,000 daily active users and $2,000 MRR before its public launch. The episode explores his journey from failed startups to finding product-market fit, his technical stack using AI coding tools, and how he competed against well-funded competitors with just himself and AI assistance.
- Solo developers can now compete with $50M+ funded companies by leveraging AI coding tools effectively
- Building for yourself first creates the strongest product-market fit signal - internal usage drove Monologue's success
- The 'ship fast, iterate quickly' approach beats perfectionism - Naveen released his first version in just 2 days
- Bundle strategies work better for AI tools than standalone pricing, reducing customer acquisition friction
- AI coding assistants like Claude and GPT-5 can handle complex technical problems that previously required hiring specialists
"We built an AI app that had 1000 daily active users and 2000 in MRR before it even launched"
"I can do anything. Right now I'm in that zone where if user customer has some kind of problem, we can solve it"
"Because of AI, he was able to build an incredibly polished, incredibly sticky and compelling AI app in just a few months"
"It types what you meant to say"
"Immediate Churn"
We built an AI app that had 1000 daily active users and 2000 in MRR before it even launched. It's called Monologue and it's a text to speech app built by every entrepreneur in residence, Naveen Naidoo. Naveen built Monologue by himself end to end and we just launched it yesterday and it's one of the fastest growing and stickiest AI products we've ever built. Naveen and Monologue are so compelling because he's a single engineer competing with companies that have raised over $50 million and have hundreds of employees. And because of AI, he was able to build an incredibly polished, incredibly sticky and compelling AI app in just a few months. So I brought Naveen onto the show along with every COO Brandon gel to talk about Monologue and talk about his journey because Monologue is something of an overnight success, but it took Naveen a long time to get there. So we talk about Naveen's entrepreneurial journey, we talk about how he joined every and the time he spent iterating and shipping on new ideas before he found Monologue and then we talk about the stack he uses to build and ship production grade apps by himself as a solo AI developer. Naveen is incredible and if you really want to understand what is possible if you use AI tools well, this is the episode to watch. Let's dive in. Naveen and Brandon, welcome to the show.
0:00
Hey Dan. Hey Brandon.
1:31
It's really good to have you.
1:35
Yeah, I'm really happy. This is like first time recording a podcast for me and that to doing it like you know Dan, which I've been following for past five years. So dream come true here for me.
1:37
Oh that makes me so happy. I'm glad, I'm glad this could be your first podcast for a lot of different reasons and just so happy to have been working with you for the last year or so. So for people who don't know, you are an EIR at every and you are the GM of Monologue, which is a smart dictation app which we are launching publicly very soon. By the time this episode is out, I believe Monologue will be fully publicly released. It's currently in beta and it's like it's such a cool product. It's so well made. It's a product that everyone uses internally. You've done an incredible job with it. You've built it completely by yourself and it's already over a thousand dollars a month in recurring revenue. It's a thousand MRR without us even launching it. So it's just it's just growing. It's so cool. How does that feel?
1:50
It just like feels I'm first of all like really grateful just to like you know work with every because the thousand MRR thing. I think if you're normal indie hacker just reaching that milestone just just takes you years upon years just here for me having this, every audience having you and every team behind is just like I think dream team for me. And obviously like product needs to work. Everything needs to like you need to solve a proper problem there. But yeah, I'm really like excited nervous. Everything is happening at the same time.
2:37
I love that. And we also have Brandon here. Brandon is now the COO of every. The last time you were on this podcast you were only the head studio. How does it feel?
3:14
Feels great. I'm. I'm yeah I'm echoing what Naveen said. Dream come true with the dream team.
3:24
I love it.
3:32
Building dream products.
3:32
So I want to start, I want to talk about a little bit about your journey to Monologue. But before we do that Naveen can you just like demo us Monologue so people who are listening and watching can get a sense for like the thing that you built?
3:35
Yes. Let me share my screen first. I'll talk about writing an email and we can get into Monologue visuals and other stuff as well. Let's say I want to write an email to Kiran. Kiran is a GM of Quora and he's a wind user of Monologue. Monologue sits on your laptop on your screen here and I'm using my hotkey which is right side option and I'm double tapping it which is going to be hands free mode. Hey Kiran, how is it going? Can we meet up tomorrow around 8am actually make it 9am and if that doesn't work maybe you can check my availability here. Thank you Naveen. So I just tapped right side option key again and here the cool thing is the Kiran name it understands I'm talking to Kiran. It's good. And then here it fixed. I mentioned about saying 8am but I later self corrected and made it 9am and then here there's something weird happening like how did this link got attached here? So that is because in Monologue we have instructions where here I mentioned my calendar schedule link so it just understands you really well. So you can just write with zero edits. So this is just one of the examples but you can take this add it to when you're talking to LLMs when you're talking to other use cases as well.
3:48
Yeah it's really Cool. So yeah, for people who are listening, basically all he did was he talked into his computer mic and what monologue did is it transcribed it into a really well formatted email that included his calendar link and took out ums and ahs and self corrected certain things that he corrected. And it has like, it's honestly become the default way that pretty much all of us do work at every very quickly, which is really cool. It's similar in a lot of ways to Whisper Flow or Super Whisper, which is something we can talk about as part of this. I think the thing that the way that we've been talking about it, which I really love, is it types what you meant to say and that whole thing has been like really, really cool. What I want to ask though is you have this really polished product. It's growing week over week. People are using it all the time. I think there's someone who used it over a thousand times last week or something like that. It's pretty crazy how good it is. But you are actually in the. Even though you were working with us for a while, you were in the wilderness for a long time. So you became an eir. I think we had our first conversation, you said about a year ago, almost exactly a year. And it took you from then until now to like find this and have it be like ready to launch. So what was that like? Like what was it like coming into every. And what was it like kind of like going through the wilderness. And how did you get here?
5:20
So yeah, it took me some time to get here. Maybe quick intro journey would be. I quit my job around 2023, right after I think ChatGPT API got released.
6:51
Good time to quit your job.
7:05
Y so there's this pending loom or something big is happening in the industry. Kind of a feeling. You can see. ChatGPT I think got released in December 2022 and they released an API in March 2023. I like vividly remember that because that's like one of the pivotal moments for me. So yeah, like I quit my job.
7:08
How did you get the conviction to quit your job in that moment?
7:32
Not really. So what happened is in my previous company, I didn't get the conviction. I am like really nervous. Like I didn't know what I was doing. So in my previous, like I had this deal with my boss, previous boss saying, okay, I'm going to work three days a week with you and rest of the four days, let me figure out what I want to do with my life or like what I want to do. Next. And he's like more than happy to give me like he's paying me full time salary. He paid me full time salary during that three months period. But I still only worked for three days and rest of the four days I just like kept on like, you know what to do. And only then I think CHARGPT API got released, right? So I started hacking products around the same time I released this app called Friday GPT. So it like that's my first time hitting some, some random stranger giving me money to buy an app. So that made a big difference. And I'm like, okay, I had to do this.
7:39
How did that feel?
8:33
That is like, you know, I never met that guy. I don't even know who he is right now. But that's a really great feeling that okay, I can earn something of my own just from this pure like the idea is just in my mind. I thought about that, I made it executed and someone paid for it. That's like eye opening for me. And I thought, okay, I had to do this full time, right? So I just quit and then started my own company, came back to India actually before I used to live in Japan. So I like made pretty big changes around 2023. And yeah, after that I started my company and I started working on multiple bunch of products. And one of the biggest mistakes I made during that time is I just worked on one product for six months or something I didn't even release. So it's just like sitting on my laptop. So that's called send wisely. And like what product was it again? It's an email marketing tool like similar to kit.com.
8:35
okay, this is like the cardinal thing. I've never even seen this product that you built.
9:39
I didn't even talk to anyone about that because I'm like really ashamed that I built that in my like, you know, just on my sitting every day sitting, going to coffee shop or something, building that. And I never showed anyone. I didn't do anything at all with it. I just like kept on building, kept on adding features and that made me like, you know, technically I'm like able to just play around with tech stuff but never really actually went into business. Okay, I have to sell it, I have to market this. I never thought about all that stuff. But later on, okay, whatever is done is done. Let me just start again from scratch. So I again went back to the drawing board. I made a Mac app and here this time I had a goal. I have to release this Mac app in one week. So I built it. I Posted it on Reddit and then a lot of people wanted have the similar kind of problem and then they also wanted it. It's kind of like wrapper, chatgpt wrapper. But the thing is you can select a test text and hit a hotkey and you can run a prompt on top of it. So that's just idea is very simple. So like a lot of people are going back and forth in charge and doing the same thing, right? Maybe fix grammar or some other thing. So selected text.
9:44
It's the funny thing is that's such a good idea. You know like that, that idea there are, I mean ed. Edmar different, you know. Eir every team member messaged me yesterday saying that there's a company that like wants to talk to us and it's a. They do $30 million out of Brazil and it's just a ChatGPT wrapper. You can ask the same exact questions that you asked ChatGPT but also in this tool and they do 30 million ARR. So that idea very well could have been your idea.
11:06
Like what, what?
11:36
And I know it, I know people bought it. So what, what caused you to sort of lose steam on it?
11:37
Yeah, so it, it, it did like really great job for me. Like at least with the confidence I, at one point I even reached 5k per month. I'm like that, that like Mac app is making 5k. That's like due peak chargpt like you know, rapper season. So I'm making ton of money and getting good eyeballs on it. But one mistake I made is user have to bring their own API key for it. So it's a very niche product and it's a one time fee. So if user have to pay at the time $39 or $29, I don't exactly remember. So that's a niche product and kind of like after that I don't know what to do. So I started, okay, let me build another Mac app so that I can bring in more revenue. So I built another Mac app called Screen Time plus. And then slowly like I started hacking lot of side projects and stuff but nothing really like okay, this is going to be my next five years. It's just I'm making some random apps and the only thing that I got really good at or compounding wise is I'm able to build apps really fast and then only build that one single core feature and like post it on Reddit, post it on X, get eyeballs, convert them to sales. But I don't really have any solid business plan. Of, okay, how can I take this to next level? And that's when I met you guys like, and joined spir.
11:44
That's really interesting. You're saying so many things that feel very familiar from my own journey. And, and I'm just like, this is why I love working with you. Like, that's why you're awesome. Like, just things that, like lessons that I learned too along the way. Like for example, one of the things you said is that you just negotiated with your, with your boss to like take four days, like only work three days a week, rather than like having to quit your job all at once. Like, I think there's this sort of feeling that, oh, you have to do startups in a certain way and you have to be all in from the very beginning. But there's, there's a lot to be said for like stepping, like putting your toe in the water and like, you know, shipping, ship, learning to ship apps, like, while you still have a job, so you have more, more Runway and less pressure. Another thing you said that I, that I, I really resonate with is, well, one is working on something for like a long period of time and then not shipping it and then realizing that was bad and then really forcing yourself to be like, okay, I'm going to ship every, I'm going to ship something in one week. I'm going to all these different apps. And I think that's a really good part of the, of the learning experience is just like go from nothing to an app that you're trying to sell instead of like being off in your cave, like hacking away on something that like no one, no one actually wants. Yeah. So I definitely vibe with that.
13:10
Yeah, like, that's a big, I think like bulb turning on moment for me, which is, oh, I can just do things like just have a small idea, just code it up. Release doesn't have to be like, a lot of features have to be there or billing has to be there. I just figured it on the way. So like, that's a big, I think, mental shift for me so that during
14:22
that time I was, I was thinking about how I wonder if people when they work on something that's like they haven't shared with anybody, a lot of times it's for a product that they themselves can't immediately use and don't actually like, immediately use themselves versus if it's something that they actually use themselves, they're excited to share it with people. And that's kind of a good indicator. And it's honestly the way that we build products is we won't build anything that we don't use all the time. It's just sort of like a rule, an unwritten rule that we now have because it'll never launch, I guess, is what we're learning.
14:47
Yeah. And it's the best way to know that the product you're building is good, because if we use it and then we get the rest of the team to use it, we're pretty sure that the audience is going to like it. And that's just a really cool loop. And I think we're in this. We're in this unique time where the game board has been reset because of AI. So there's all these new opportunities to do new stuff that you can just look for problems that you have personally. And if you have that problem, there's a good chance that other people have it and that it hasn't been solved yet, which is really, really cool.
15:27
That's kind of a good segue. Kind of a good segue to, like, how monologue came about, too. Because my Naveen, correct me if I'm wrong, but my understanding is we were built. We were launching tldr.
15:58
No. Okay, let me give. Give you a quick timeline maybe. Yeah. Just to refresh. So I joined last year, October. So that's the last quarter of last year. And I started working on tldr. It's kind of like synthetic podcast generation for. From your meetings. Slack discord. It just turns everything and converts into a beautiful, like, podcast that you can listen tldr.
16:14
Those were the days. Yep.
16:39
I still get. I still get pitches for people to do that. I'm like, we tried. Doesn't work.
16:42
We launched it, like, right before Christmas on this, like, crazy, chaotic schedule where we launched, like, four things in a row. Yeah, actually, it did fairly well, but there was.
16:48
I don't know.
16:56
It was. Yeah. Anyway. Interesting.
16:56
Yeah. Maybe we positioned it the wrong way. I don't want to accuse anybody of
16:58
positioning it the wrong way, but me and Brandon had a big fight before it came out. And he was. I'll say for the record, he was correct about how we should position it. I went a little galaxy brain. But anyway, I don't think it would have worked either way.
17:01
So for me, like, from my side, what happened really is. I think it didn't really sync well with our every. Every audience. No one, to be honest, I think I worked that for 10 weeks internally. No one really used. Like, no one is listening to those podcasts. No one is reading those meeting notes and stuff. So and even when we released it, I think as every like we have this every audience. Right. So they also like, okay, this is cool but I'm not going to use this obviously like kind of a vibe we got.
17:18
Yeah.
17:44
So after that I took some time off, like two weeks. I didn't touch my laptop. I'm like, you know, I continuously worked on 10 weeks for the, on this product and I did the same mistake like I previously did one year ago, which is just working on something which I didn't like put it out fast, real fast. So coming back after the holidays I made myself okay, I'm going to release one experiment per week. I remember Brandon having a KPI as well for that quarter where experiments from studios, like number of experiments from studios and that really helped me also. Okay, I'm not going to worry about creating products and stuff. I'm going to just think about creating as many experiments as possible. So after that I did Kairos. A lot of every audience might remember Kairos. They love it.
17:44
People love that.
18:34
Yeah, yeah. So it's a AI book reading app. And even before launching we got to know, oh, this doesn't really have commercial success because you have to actually sell the books within the app to make any kind of money. If not, how are you going to make money? Like people are not going to pay you $20 on top of already buying books. So that didn't work out but people loved it. People love the article. I still get like emails and messages saying they like it and they kind of like try to include that into their reading habits. And after that I started working on Grammarly alternative. That is because I'm like from India
18:35
and oh my God, I forgot all of these.
19:14
You guys, you remember it now?
19:19
Oh yeah, now I do. It's all coinbase.
19:21
Yeah, I black that out from my brain.
19:23
Yeah. So after that I did that experiment where, you know, I'm from India. My English is not that great when I'm writing so I use Grammarly a lot but Grammarly is really slow. It's shitty to be honest. Someone has to make a better product here. So I asked around the team. Kiran is paying for it, Yash is paying for it. So I'm paying for it. Why not? Why can't I take this up? So I took that up. I actually first started with iOS app. So within one week I released the iOS app. We even emailed some of early adopters, we put up a form, it's going well. But the energy of that app like to be like overall usage is Good. It's going in the right direction. It's just that energy around this idea is not that great because okay, this is already like you're solving like 20 years old problem kind of, you know, thing people are not really excited to
19:27
like your energy or the. Or user's energy. Which one?
20:22
Everyone's energy. I would say.
20:26
It didn't feel like a creative act. It just felt like we were like solving very specific problems.
20:28
Yeah.
20:35
I wasn't sure how we were going to like make something mind blowing there.
20:36
Yeah. So that's the same thing.
20:39
But I remember thinking this is such a good idea.
20:41
Yeah. We released an iOS app. I think at one point we got like to around 200 users using it, using the keyboard, actually changing their own default keyboard. And we also have a Mac app where it highlights the corrections and you can correct it. So technically we invested a lot of stuff in there, but it just didn't feel like people are like adopting it that fast. That high. Yeah. So during, during that time. So what happened is I am like pretty low. I am like not motivated to work on Android. I. I just want some, some new fresh ideas. So on the side I didn't tell anyone on the site. I just made the jotle like at that time. That's a working name of Monologue. So I just made that app for myself and I just started using it.
20:45
Why did you make it? Like what, like what was the thing where you're like, oh, I just want to like mess around with this. I don't want anyone. But this is kind of fun.
21:36
Yeah. Like when I joined EIR program like with every one of the ideas is whisper flow alternative but better. Like that's one of the things it's on my.
21:44
Like I was on the list.
21:55
Too bad you didn't put that higher on the list.
21:56
I don't think, I don't think we were ready for it. I have comments on this. But you keep going with the timeline.
21:59
Yeah. Yeah. So what happened is. Yeah, I have that idea. It's like itching me, you know. And other thing. Edmer, one of the users of Underwrite and he's also ear. So he mentioned I want this voice to text in keyboard. Can you do that? And I got a similar kind of request from other users and I also want that and other thing is the one of the previous apps I talked about Friday GPT it has that feature but I already know users are actually like using voice and how they are like it's helping them a lot. So I talked with couple of users. And the thing is it's not great product like two years ago that I built. It's not really great product. So I just okay, let me make a really great product with all the things I learned because now I feel like I'm really confident with my technical skills, product skills. So I just like thrown away everything and just started the code from scratch. I am like just looking at my commit history. Are you interested in looking history?
22:06
Sure, yeah, absolutely. Let me okay, quick break from the episode. Your home just became smart thanks to Alexa, the sponsor of this episode. Amazon just released Alexa and Alexa with a state of the art AI architecture. It's a state of the art language model packed into an Alexa so it can access thousands of services and devices. I have one, Amazon was kind enough to ship me one. And here are a couple things you'll see if you start using Alexa. First of all, it's really intuitive to talk to. It feels a lot more like talking to a frontier language model than the old robotic Alexa or series. You can talk to Alexa like a real person. It'll keep track of your train of thought and it even personalizes itself to you. It has a memory bank. So if you tell it once that you want to try the new Thai place downtown, for example, in Brooklyn, one of my favorite Thai places is called Souk. It'll remember that next time you're looking to book a dinner reservation. And by the way, you can actually use it to do that. So one of the cool things about Alexa is it can take action on your behalf. So you can ask it to book a reservation for that thai restaurant on OpenTable. You can also ask it for music recommendations or to help plan your day and add stuff to your calendar. It even has smart home features so you can ask it to dim your lights or turn on the heat without getting out of bed. Alexa early access is rolling out now and it's free to use it during the early access phase. If you want to try it, you can use the link in the description to request early access. And now back to the episode.
23:10
So officially it's called Lecnal Monlock Mac app, but. I started it in April I believe.
24:35
So for people who are listening, basically Naveen is paging through his commit history and what's really interesting about this is okay, so you started working on this app in April, it's now September, so it really has not been a long time and you are one person and this is like a beautiful production ready app that you've done everything for that like hundreds or Maybe thousands of people are using every day. It's. It's pretty cool.
24:51
Yeah. So I think it's just a compounding.
25:19
Right.
25:22
If anyone out there who is like looking to like start or create a startup or create a product and stuff, one thing I would say is just keep on building. Keep on like creating as many experiments as possible. Because once you hit that one great idea, you can just release it in two days. You can see that commit history. Right.
25:22
Describe what we're seeing on the commit history.
25:44
I started my initial commit here is April 15th, and I did a bunch of changes, bunch of things on April 17th. I have V1.0.1.
25:46
Wow.
26:00
In two days I released it.
26:01
There's something that I just saw that's interesting in there. You have a commit in there for Auto Enter, which I think is like one of people's favorite features of monologue, where you can speak into monologue and it automatically will process what you say, fix it, and then automatically paste it and click Enter, which if you are a developer, allows you to really stay in flow because you can just speak and you don't need to use your keyboard at all. I use it for, on Discord, I use it in messages, I use it in warp. Um, and that was. I think I saw that on the 11th. Or was that the 17th that you committed that?
26:06
Yeah, 17 here.
26:45
Okay. So it's, it's like, it's one of the most important differentiating features and it's one of the first things you built. And it, to me, it just is a nice. It just tells me, okay, you just need like one killer feature to really convince yourself and see if people really want to use what you're building. And then a lot of the work that you've done is like polish and fixing bugs and adding things here or there. But like a lot of the product was there the day that you launched it. So you can have like a simple product that works super well. But that last 20% is like so hard.
26:47
Yeah, 100%. So at that time, what I'm doing is on 15th, I built that and I started using Jottel at that time to build Jotter. You know, I've been dog footing. Like the auto enter thing came because why am I always hitting enter? Why can't jotle do that for me? So I just added that. So kind of like all the features that first two days that you see is around that.
27:22
That's the beautiful thing about building for yourself is you know that that's what you want. And also it's the beautiful thing about building inside of a company like every. Because you've just been like flooded with people saying like, I need this or this isn't working or whatever. And so you have this like really, really high fidelity feedback loop all the time. Of good feedback.
27:50
Yes, a hundred percent. So after that, what happened? Like two days I pushed it on 18th. We have the show and tell on Fridays. So I think that's one of the like fun meetings. We usually like, we have ton of high signal feedback. We get high signal feedback there. So I did the demo of Android. I'm like, pretty, you know, like not that feeling great about the progress I'm making with Android. And then at the end, like maybe five minutes or 10 minutes remaining, I demoed this app like I've been like working past two days on this and like Kieran got really excited about this. I. I don't remember like everyone else like to. I just remember Kiran's reaction because Kieran also has his own Python script, like some crappy version of it. He mentioned he uses his Local Whisper thing. So. And Kiran got excited, I got excited. So I just released the app to Kiran, like I think right there, I just sent him the bill directly. And the next feature he asked is I need local Whisper models because he likes Local Whisper models. So I just added that feature for Kira and slowly Nitesh started using. Alex started using Branded, like that everyone started using. Everyone started giving me feedback and then it just like, like, yeah, off to races. That's it.
28:08
Yeah.
29:29
This was really exciting time. And I'm laughing to myself because I remember, I remember feeling I'm going to go back to sort of like why we felt like we're going to do this and this is like an easy decision, but I wanted to like a quick anecdote. I remember we like created a Discord channel and Kieran hit a bug where like it wasn't working for him. And he sent you a message that I honestly will never forget. He said Immediate Churn with a screenshot and classic Kieran. Yeah, I love him.
29:29
He's like, yeah, he pushes you really hard.
30:04
He just, he said Immediate Churn. And I just looked at that and I was like, holy shit, he's right. This is Immediate Turn. And just saying it so bluntly, I think. And that's sort of, you know, a version of the feedback that you get from everybody here. I think has made it like a pretty bulletproof product. But yeah, I'll never forget Immediate Churn.
30:06
That's funny. I went on a hat yeah, go for it.
30:26
I mean, I take Kiran's feedback real seriously because I think he's like the top 1%, 10% users where, you know, if they hit a bug, you immediately turn. If I keep Kiran happy, I'm going to keep, like, a ton of people happy.
30:30
I just. I just submitted a PR on Quora, which he denied. So, like, I know the. The bar for Kieran is pretty high. He was like, this is Vibe coded. I was like, you're right, it is.
30:49
Which is crazy because he's the number one Vibe coder. He's just like. He's wielded it so well and now he thinks he's the one coding.
31:01
I think this is an interesting product for me too, because it is the first product that we've incubated inside of every. That I have not either built the first version of or been intimately involved in the building of. It was the first product where I was just off doing other stuff and I just saw a bunch of people talking on Discord about this. At the time it was called jotl, and then we renamed it Monologue. And I was like, I guess I'll try it. And I tried it and I was like, whoa, this is good. And that was like, the coolest. That is the coolest feeling ever. I have to say, to just feel like we're making awesome stuff. And I just, like, had nothing to do with it. So it was just really fun to watch that happen.
31:10
I want to talk real quick about, like, the, like, the strategy behind it. So there was. There was obviously, like, Naveen, you built the first version of it. And I remember in that show and Tell, I was. I had sort of an unlock and was like, we need to do this. But the reason that I felt like we needed to do it, even though it felt kind of wrong, because, like, there were other companies that were already existed that were doing this. And typically all the products that we've built have been like, net new products. It was very hard to come to get over the idea that we weren't going to build something new. We were just going to try to take in a concept that already existed and make it better. But the reason that, like, I got so comfortable with that and actually reached out to Dan and was like, dude, we have to do this immediately. And you were like, maybe. And then you used it and you were like, I'm totally in, was I realized that people subscribe to every because they want it to be the last. They want to be super up to speed on. On AI and they want to use our individual products, but what we want for them is that it's their last subscription that they have outside of a ChatGPT or cloud. So they have a ChatGPT subscription and in every subscription. And I realized voiced very, very good. Voice dictation is one of the main tools that people are using. And we're actually doing subscribers a disservice if we don't include this as a part of their bundle. We just need to figure out a way to do it that feels right to us and, and sort of like levels up the whole industry.
31:46
Yeah.
33:19
Which, you know, you started this in April. We're recording this September 10th. I think we've done that over the past many months. It's taken a long time to get it to be like really, really good.
33:20
Yeah, I think that was my hesitation too is like I wanted to only release this if we felt like it felt like in every product. Like it felt like hours instead of just, you know, we just vibe coded something and it's like kind of a shitty thing. And I really do feel that way. Like you're, you're an absolute craftsman. Naveen. It's a, it's a beautiful product.
33:30
Thank you. I appreciate that. So, yeah, I too had that in mind. Like because when, even when I presenting that I remember I know this is like already existing product. Like I'm just, I just made it for myself. Like don't like you know, be this is my baby. Don't be harsh kind of where I'm presenting it. But once, you know, like Brandon talked about this, like, don't worry about like copycats like being that like, you know, because we have already done off every audience. If no one else is subscribing, you're going to anyway get these every subscribers who are going to like use it. So just focus on every subscribers. But don't worry too much about like external like you being competing with that initial period. So that actually made me little bit, you know, okay, I can actually make this work because I can just focus on every audience. Let's try to like, you know, make a really good app. So that put me at ease because I don't want to like people to think like I'm just copying something totally.
33:50
And this is the first time that I felt like the bundle strategy that we've been pushing for a long time it's like starting to like really work. So for you who you don't know, with every. You pay one price, you get access to the. All the writing that we do and all the software that we make. And it makes so much more sense to build Monologue in the context of a bundle because, you know, when you're. If you're comparing, okay, I can buy one app or I can buy a subscription and get like a bunch of apps, plus like really good writing about AI. It makes that the value is great. Calculus. Yeah, that calculus makes a lot. Makes a lot more sense. And it's just been. It's been really interesting to watch that happen because I didn't even think that this. We would be building something like Monologue as part of this strategy, but it just seems to work.
34:55
Yeah, yeah. And that strategy really helped the way Monologue right now it is because what happened is April is done. Maybe I can show like initial periods because the uncertainty.
35:46
Yeah, show us the usage.
35:58
And yeah, so the usage here is that like I keep track of two things, which is the number of words that are getting dictated and number of times the, you know, monologue got activated. So initial time. I just walk you through that initial period. Right. 17th, 18th, like April. And then I gave access. I started adding like analytics the following week because people have been using it a lot internally. And here you can see this is not my usage. I removed my usage because I do a bunch of testing. Right. That initial period. So this is somewhere like we got 130 users per day. Slowly it went to 150. 200, like 300. 350. End of like. Yeah.
36:00
This is the number of times that somebody clicked the button to start dictating.
36:46
Yes.
36:50
Okay, cool.
36:51
Yeah.
36:52
And for people who are listening, like, yeah, it's just a smoothly. It's a graph that is smoothly going up. And this is a usage graph, which is very hard to do. I mean, obviously it's a little jagged for like weekends and stuff. But I think it's really important to say we work on a lot of products. We've all built a lot of products over our lives and seeing something that just like smoothly goes up in usage is extremely rare.
36:53
Yeah. Here you can see the week over week graph. Like, which is like initial week, we got 230. But slowly, end of May, we are hitting around 1500. 1500 users per week usages.
37:21
Per week usage. Okay, got it.
37:35
I think we are hitting around 2718. These are all internal users. Yeah, this is all. Every internal. If you want. Maybe we might have to blur out the emails here.
37:37
This is only to June, right?
37:49
Yeah. Show us the full graph.
37:51
Let me yet to date. We might have to blur out the emails.
37:56
Oh, wow, look at this. Even better. Yeah.
38:03
Trying to be hitting 7,000 usages per day.
38:08
Yeah. I mean, this is crazy, like, per day. This isn't even linear.
38:11
There's no landing page for this product.
38:15
Naveen, show us the landing page.
38:18
This is the landing page. So this is.
38:21
So for people who are listening, it literally just says monologue and then download and then it says, please don't use this because it's a public beta and it has a little made by every sticker at the bottom. So yeah, that's. That's crazy. And it makes me very confident in this, in this product and people are okay.
38:23
So the other thing that's crazy too is there are a bunch of competitors. A lot of them have raised millions of dollars.
38:41
Yeah.
38:50
Like, we have a competitor, Whisper Flow, that's raised like $50 million. We have invested in this product. Less than $20,000 in one person. Veen is building this product alone. Yeah. We should talk like a little bit about, like, how we have supported you with a bunch of other like, people to like really make this super artful. But I just think that that's crazy. And it's one of the. It's one of the most obvious proof points to me that we just live in a different world. And raising $50 million to do something is not only unnecessary, it puts you in such a corner. We have already built something that is successful, period, because we can build really quick. Naveen's really talented and we haven't invested a stupid amount of money into it. And it doesn't need to be a billion dollar outcome. It could be like, I mean, at this point this will be a multimillion dollar outcome.
38:51
And
39:48
I feel like we have that in the bag. And that's really special to like build from that place because you're building from your front foot instead of like trying to dig yourself out of a hole.
39:50
Totally.
39:58
It means we get to like make art, which is worth talking about because this is a very, very artful, kind of like teenage engineering style product.
39:59
Can you demo the welcome screen? Do you have that set up?
40:08
Yes.
40:11
I know Naveen is so proud of the onboarding because he has a button that's easily accessible to reset the onboarding.
40:14
I just want people to like, yeah, just go through the onboarding again. So just to set some context around. Okay. Like, what happened is you. I think end of June, Brandon and I, like sat down in one of our calls and like, okay, this is working. People are actually using it, but UI looks shit. Like UX is shit. Like we are just like not happy with the way things are. So we immediately bought like Lucas. So Lucas is our head of like creative lead. Yes. So I think having Lucas on a project like this just from start. Yes. I think made ton of like, you know, decisions, whatever decisions that you are seeing within the product happen. So Lucas brought that Lucas energy, every synergy into this monologue from the start. That's why the way it works, it is working right now. So let me show you quick things.
40:22
I remember when Naveen and I had this one on one I said this app needs to do three things. It needs to work really well. It needs to look like teenage engineering or something like that. It needs to look really different.
41:24
What's teenage Engineering? For people who don't know, Teenage engineering
41:37
is a hardware company that makes beautiful recording devices, music making devices, computer cases. They just have a very cool aesthetic. It needs to look kind of like teenage engineering. It needs to look different and it needs to be a part of the every bundle. And if we do those three things, this product will work. And that seems to be happening right now. And the way that you execute it on the design side is just out of control to me.
41:40
So 100 like this is one of our inspirations and Lucas like worked and gave us this monophone. We never thought of monophone at all like initially. I remember Jottel being just a blob of text, like just radiating and like Lucas came up with this monophone idea where, okay, you have to feel like you're talking to something. So that's why.
42:11
Yeah.
42:36
Anyway, let me show you like the onboarding. Awesome. Yeah. So this is the onboarding where you see the like sound and animation. Maybe Brandon can talk more about the sound and everything that.
42:36
Yeah, I just gotta say I love it. And like we just have so many people reach out being like, that was awesome. Just from just downloading the app and starting it. Like I had someone who's has a fairly big Twitter audience that messaged me being like, this is the first time I've gotten emotional using software in many years. And I was like, yeah, we've done. We did it. We did it.
43:03
I think, I don't know, we just had such a strong perspective of like we want the mod. Well, we didn't even know Lucas actually came up with the idea. The word for monophone. So he was like, this is. The monophone design was really special. We knew we wanted sound to be really cool.
43:23
He also came up with the name Monologue.
43:37
Yeah, he did.
43:39
He did come up with the Name too. Yeah, we wanted like this. We wanted sounds to be a part of it. So we have like this really cool intro sound that my friend Jake Sheriff made. We brought in a designer to do the app design and the landing page design, which is the first time we've ever done that. We've always done Apple and landing page design internally. This time we brought somebody else from the outside. And he's great and he's amazing. And like, Lucas did creative direction, he did actual design, and it was like a very special combination. And then we brought in a guy to do animations. So it was just like. Also in the middle of this process, I learned that Naveen is like top. 0. 0. 0.0002% in India at math and science for, you know, whatever cohort you are of that test.
43:39
And.
44:27
And I. I learned in this process he's also very good at managing other people. Which rare combination. A very rare combination.
44:29
Thank you. I don't know what to say. So I think it's just like, I feel like I'm in a video game, you know, collecting all these skills so that I can build this monologue. So I think in my previous job I was managing people, so, yeah, I collected that skill. And later when I'm working it just like everything came together nicely here.
44:37
And yeah, for people who are watching, I think there's probably a lot of people who are like, wow, this is awesome. I want to start doing this too. Can you tell us a little bit about your workflow? What tools are you using? How are you using AI in your workflow? All that kind of stuff?
45:01
Yes. So for the initial stages, the 0 to 1, it's really, really important for you to just keep it. Just go one single feature and use AI, obviously. And one of the key things I used initially at that time, I remember Winsurf, it just feels like ages ago. So I was using.
45:16
I know.
45:39
What is that again? Yeah, I even like. It feels like a year ago, like when I said Windsurf, but I'm using. I was using Windsurf a lot during that time. And I think Windsurf is one of the first IDEs to introduce this agentic coding as well. I remember. So my code base has been getting a lot, so Windsurf and right now my tech stack looks cloud code a lot. Like, most of the code that's in Monologue is done by Claude code. And then recently I've been using codecs a lot. So let me show you. Codecs.
45:40
Yeah, show us. Yeah, we've never actually Shown codecs on this show except for the. We've shown the web version because we had the guy who launched it inside of OpenAI on the show for the launch but we've not gone there in a while. So. Yeah, tell us about how you're using codecs.
46:18
Yeah, let me show you the codecs. Like I think around May time, May 18 they released it and I initially got like some errors but 18th you can see how many tasks I'm like giving it to Codex.
46:35
Basically like every day you have a task, you're just scrolling through a list of tasks for people who are listening and yeah, every day you have a little task you're kicking off of Codex or maybe looks like multiple tasks a day. A lot. There's a lot.
46:49
Yeah. It all depends on my mood as well. Like if I'm in that mood of okay, today I will be in a manager mode and let me just give bunch of tasks to all these AIs and like review it. But if I'm in active development mode I'm going to just like use Codex. Let me.
47:02
But now it looks like you skipped a month. So why did you not use it for a month?
47:19
Crowd code like that made a big difference for me I think. Yeah, I think what happened is I was using this with. I don't remember the models to like I think 0103, I think it's O3.
47:23
It's a fine tuned O3. Yeah, yeah.
47:38
O3. Yes. I think during that time it was. It's really great. And after that Opus 4.1 got released and I'm just like completely moved to cloud code and now I'm back to again codecs cli. So actually like yeah, here you can see. Turn up. I'm not. You can see I'm using codecs. Actually like today I just developed this like I'm working on this monologue speed test website and I just made a plan and within the plan. Yeah, within the plan we have these phases. Phase one, phase two, phase three and I'm just implementing these phases. Phase three. Yeah. So I'm just using codecs a lot where GPT5 high end medium is so good.
47:40
Interesting. Yeah. Tell us about why like why'd you switch? Why do you think it's better one?
48:35
I think 4.1. It's just like, I think I got like with cloud code it just says like you are absolutely correct. Absolutely right. And it doesn't like push back on my like whenever I'm trying to, you know, get some proper feedback on my implementation. Here, for example, I actually used monologue to dump this. Here you can see like. And it gave me.
48:41
And he's just highlighting a bunch of. A bunch of texts where he's asking questions about. About his code base.
49:07
Yeah. And it gave me a really great plan. I think planning is really, really good compared to Claude code here. What happens with planning and even with the code? One thing I observed is it's actually. I have a video as well recorded where I compared cloud code versus codec. Like not codecs, but GPT5 high or medium? One thing I clearly observed is Codex X works on what you asked. It doesn't go into some. Like his own creator.
49:13
It's much more precise.
49:44
Yeah, much more precise. And the code it generates feels like some senior engineer wrote instead of Claude code. It kind of feels like some junior engineer wrote. I know it's a big statement, but it just feels like with ton of comments, with ton of like the logic it writes. It's much more like not well thought out. But if you look at Codex code.
49:46
Yeah, yeah, I think you're right. It. GPT5 code does feel like if I want a precise change and I want to be confident that it's doing the right thing, I can use GPT5 and it'll do it well. It's got that precision thing. I think of cloud code as being high in industriousness. It's just going to do a bunch of stuff which is actually helpful in certain circumstances. For example, I wanted to commit some code to Quora. I needed to get my repo running locally. And cloud code is just really good for that because it's just going to keep banging its head against the wall until it figures it out. It's very industrious and GPT5 will be like, well, I can't do this because I'm, you know, whatever. There's like 15 precise things that it. That it thinks are wrong, you know, and then you have to go through each one with it and. Yeah, so I've been. I've been liking. I've been liking Codex as well. I'm curious. I've heard that a lot of these models are not that good at writing Swift. So what has been your experience?
50:08
Even during unwrite development, which is the Grammarly alternative that I was working on, it's technically complex, meaning you have to show this red squiggly lines on top of any app. So that's a very highly technical challenge. Like you can't just use some external library to build that out. So I, during That time I was using O1 a lot and O1 is really really good. O1 and O3 mini. I remember being really really good at writing Swift code and writing highly technical like complex apps. So I always have a soft corner just for O series models, the thinking models first shift because it has that extra like intelligence when compared to any other model on the market. So I'm just like use that a lot and so if you compare Claude code is really good at implementing the features. Like you can just give it. It does that work and it's good at swift. Actually Opus 4.5 is really good at Swift. I, I use it like you can see that and but code GPT5 high like 5 high. I recently we experiencing hotkey works like that's a very complicated bug because you have to like go into niche like you know, CG event which is written by Nuxt in 1980s. Like that's the code that is still being run on Mac. Right. And it, it has like very, very like bare minimum documentation. But GPT5 high is so good at ripping through all this complex code. So I think that's one of the biggest unlock for me why I didn't hire or like get help from other developer.
51:12
It's just so crazy thinking about like before this stuff existed, like solving that problem would be you might like hire somebody for like a year to solve that. It'd be like a $200,000 problem.
52:57
Yeah.
53:09
And now it's just not.
53:11
It's so.
53:15
It's kind of. To me, it almost makes me sad to say because like there's been so much blood lost over people, you know, in sweat expelled to solve these problems. And now it's like we live in a world where we, where we're like, nah, that's not a problem.
53:16
Yeah, yeah. Like before I used to like, you know, be very scared of these kind of technical problems. Now I'm like, okay, I have GPT5, I don't have to worry.
53:33
You got your partner.
53:42
Yeah, I got my partner. I have Opus 4.5. Those are my like team members. I'm going to like, you know, delegate those tasks to them. So I think that gave me really big confidence post. Okay. I can do anything I want.
53:44
I love that. All right, so we're about to launch Monologue one. That's out. It may actually already be launched. What are your hopes for it? Where do you hope to be in a year? What would be a success for you?
53:58
For me, internal goal we have is in one year we want to hit 1 million arrow for Monologue.
54:12
By the way every as a whole just hit 1 million or like a little bit more than 1 million like recently. So that's a big goal. But I honestly I think we can do it. I definitely think we can do it.
54:21
Yeah. So that's like biggest goal Is to hit 1 million ARR. But that's a big goal in one year if we do it like that would be crazy but at least for like year quarter for me is like release the iOS app. That's like one thing. We are getting lot of requests around and I want to release that iOS app. It's also technically challenging because Apple doesn't make it easy for us developers so we have to somehow find loopholes,OS and then end of this year reach 10k m. So that's my goal.
54:29
Great. I love it.
55:08
Oh you're definitely going to do that. Yeah, definitely.
55:09
Brandon's looking at the strength graph right now.
55:13
I'm looking at the numbers. I think you're going to do that.
55:15
Yeah. One of the like really cool thing is you know every audience just like kind of amplifies it a lot. So yeah, it's crazy and I just love the way we are building because I think it's distribution first. So Dan did like really hard work from last seven years and I'm just like coming in and yeah, just in
55:20
the content mind for yeah five and a half years. Yeah, it's paying off.
55:46
Yeah, paying off now so well.
55:52
Naveen, I'm psyched for you. I feel so honored that we get to work with you and that we get to launch Monologue. I think it's going to be amazing and I can't wait to see what comes next.
55:56
Thank you. Thank you. Same here. I'm just like every day waking up. I'm just grateful that I have this team and I have AI and I can do anything. Right now I'm in that zone where if user customer has some kind of problem, we can solve it.
56:05
I love it.
56:26
What a way to end.
56:26
Yeah, absolutely.
56:27
I can do anything. Awesome man.
56:28
Awesome. See ya.
56:30
See ya.
56:32
Oh my gosh folks, you absolutely positively have to smash that like button and subscribe to AI and I. Why? Because this show is the epitome of awesomeness. It's like finding a treasure chest in your backyard. But instead of gold, it's filled with pure, unadulterated knowledge. Bombs About Chat GPT Every episode is a roller coaster of emotions, insights and laughter that will leave you on the edge of your seat craving for more. It's not just a show. It's a journey into the future with Dan Shipper as the captain of the spaceship. So do yourself a favor, hit like Smash, subscribe and strap in for the ride of your life. And now, without any further ado, let me just say, Dan, I'm absolutely, hopelessly in love with you.
56:40