Apply

Podcast guests

Rahul Sonwalkar

Rahul Sonwalkar is the founder and CEO of Julius AI and a guest on the Solo Founders Podcast.

Episode 7

Best Practices Make You Average

Published · 51 min

Rahul Sonwalkar is the solo founder of Julius AI, an AI data analyst. He quit Uber, survived six pivots and a Microsoft cease-and-desist, and argues that following best practices makes you average.

Transcript

Transcribed automatically, so names and words may be wrong. Each time opens the video at that moment.

0:00Rahul Sonwalkar: I have this idea in my mind and I just kind of want to go build it. And I don't want to let a co-founder be a blocker for that. I've met countless people that are really smart, really competent, and they're blocked on starting a company because they don't have a co-founder. Eight out of ten people that have co-founders and I talk to them in private. They're always kind of trying to work through some issue. Startups are a game of outliers. If you're following all the conventional wisdom and conventional advice and all the best practices, you're going to end up being very average. A big misconception with Solo founding is if I'm solo, I don't need to listen to anyone. People just will listen to me. That's not true. Ultimately, smart people, they're not gonna listen to you just because you don't need to do something. You have to convince people.

0:38Julian Weisser: What advice would you give them in that situation?

0:40Rahul Sonwalkar: The easiest way to convince people is to start moving in a direction and then show progress. The right way to do it is to be very generous with the early team in terms of equity. If a candidate is willing to take less cash or more equity, it's a big green flag. It's incredibly low friction to get started, if you want to build a company, you can get started tomorrow.

1:00Julian Weisser: Well, listen, I'm really excited to have you here. As you know, like, the goal of this is to talk about solo founding. And you've done a lot of podcasts and they're really interesting. And you talk about the history behind Julius and you as a founder. But the thing that you don't really touch on too much in any of those other conversations is the journey as a solo founder. And I think it will be really interesting for people who are either solo founding or considering being solo founders to hear about your experiences. So maybe we can just jump into it and we could talk a little bit about sort of how you came to the decision to start a company solo and what that was like.

1:33Rahul Sonwalkar: I actually worked on a company back in college. Um, that didn't work out. And it kind of stemmed from an idea I had from going to hackathons. This was just me seeing a problem and just chasing the solution to that problem, and then ultimately building something and trying to get into the hands of the users and like, it didn't work out. But what it ended up being was like, I was a solo founder, you know, I didn't realize that, but I just found a problem. And the first thing I did when I saw the problem was to try to build a solution for it. And then fast forward to like three years ago. Um, I had a few friends from college, um, that I kind of convinced to come, uh, work with me on this new idea I had. Um, and then within a few months, they told me, hey, I don't think startups are really for me. And so, um, just just through true faith, I ended up being a solo founder. Uh, you know, a few months into into my second startup journey. And, um, the decision was never to have found co-founders or not. What I was really motivated by was, hey, I have this idea in my mind, and I just kind of want to go build it. And I don't want to let having a co-founder or having no co-founder be a blocker for that.

2:47Julian Weisser: That's really interesting because I think that that happens often, right? Where people have these co-founders that they're exploring with, they maybe make a little bit of progress together, but ultimately it doesn't work out and sometimes it works out. It doesn't work out in the sense that people are still friends and everything which happened in your case. And other times, obviously you have these big implosions, but you know, when that happens and the person ends up effectively becoming a solo founder sort of by circumstance of it not working out with the other co-founders. I think there's really two paths to go, which is, you know, going and trying to find more people or saying, oh, maybe it's not meant to be, and shutting, shutting, shutting the company down or not pursuing it further. I guess the third one is, of course, the solo path. So I'm curious, like when you when you were there, when you were making that decision, I think that a lot of people probably come, you know, under similar circumstances. What advice would you give for people when that happens, when you're really excited about something your co-founder says, oh, gee, your co-founders say, oh, gee, you know, it's not really what I'm excited about anymore. Or I'm not thinking that being a startup founder is the right thing for me right now. What advice would you give them in that situation?

3:50Rahul Sonwalkar: Yeah. Well, if if anyone ends up being a solo founder, they're probably also the CEO. So I've heard this advice from Ben Horowitz and Brian Chesky and some of the other greatest founders is, you know, being a CEO is like the most lonely job ever. Even when you have co-founders, and especially when you don't have co-founders or solo founder and your CEO, that's just the loneliest thing ever. And so my advice to those people would be, look, if you have a if you have a vision or a idea in your mind that you think needs to exist and you have enough conviction, start making progress. You know, the easiest way to convince people is to start moving in a direction, and then show a progress show that you can actually, um, prove the ideas that you have in your mind by doing things and making things a reality. And so, um, what I see oftentimes would happen is if people have co-founders, they let those disagreements kind of be the end and all be all of the company and just sort of shut down the company or just be in this state of like, no progress. I think the, the, the most addictive thing about start ups is momentum and forward progress. And so I like to use the analogy of, of football. You know, in football you don't really need to score a touchdown on every play. You just need to get the first down. You need to get a few yards and advance the ball to the end zone and then score a touchdown. Um, so,

5:18Rahul Sonwalkar: you know, if you have a co-founder, if you if you're talking to people about co-founding, really the the most important thing you can do is, look, you have a vision. You have an idea. Start making progress. Start finding proof points or start invalidating things that you think shouldn't don't exist. Um, and all that is just more ammo, right? Gives you more conviction. Um, convinces your founding team, your your co-founders, or, you know, future people that want to come work with you to come work with you. One of the things that I see people, um, especially new founders when they're trying to turn off the company. One of their biggest blockers is. Hey, I have this idea, or there's this space I'm really excited about, and I want to go build something in that space. But I'm looking for a co-founder and I've met people, you know, six months later and they're still looking for a co-founder, and maybe they have changed the space that they're exploring. Maybe they did some co-founder work trials. Um, and I feel like that's a giant waste of time. Um, because if you really believe something should exist, um, and, you know, with AI, even if you're non-technical, you can start building a prototype, you can start talking to customers. You can start like doing some sales, some marketing, some initial validation. There's so much progress you can make without a co-founder. Um, and that doesn't mean that you should not look for a co-founder, but really just start making progress. Um, and as you make progress, as you get more momentum, it becomes a lot easier to attract people to come work with you, whether that's a founding team, whether that's a co-founder, whether that's investors. Um, but without any of that, when you're starting with a blank slate, the space of exploration is kind of infinite. And so what a lot of these co-founders trial or conversations kind of end up being is, hey, what space are you excited about? Let's first align on the space. And okay, cool. We're aligned on a space to explore. Okay cool. Let's align on a problem. Okay cool. We have a problem okay. Let's align on a solution. And then the moment one of those things there's a misalignment. Things just kind of blow up. And so I feel like that should not be a blocker when you're starting a company.

7:27Julian Weisser: Yeah. It's funny because it feels like it's one of these beliefs that people have about startups. Maybe it's a sort of a truism or something that people think that think is just is required, right? I think that people have these maybe false beliefs about how you should do things, or maybe it's generalized advice. Um, and maybe there's some there's some merits to the generalized advice, but I think that it that ultimately just generally puts you sort of towards the average. Right. I'm curious, like how you think about generalized advice and maybe how that frame applies to solo founding?

8:04Rahul Sonwalkar: Absolutely. Well, you know, in general, like startups are a game of outliers. And so, uh, every great company is, um, is an outlier in some sense. You know, Figma, for example, they took forever to launch and they took forever to make revenue. Um, and on the other hand, you have cursors or all these other other products that are just making revenue within the first few weeks of launching and have instant PMF. And so it's a game of outliers. And so if you're following all the conventional wisdom and conventional advice and all the all the best practices, you're going to end up being very average. And so each great startup, um, ends up kind of violating a few of the conventional wisdom startup rules. Right. A rippling, for example, where we're going to build a compound startup, We're not going to start with just payroll. We're gonna start with payroll insurance and like, laptop management and and HR software and all these things bundled into one. And that's very different from like start with the MVP and minimal viable product that barely works, right. And so I think all great companies end up violating 1 or 2 core principles of building companies. And so oftentimes you realize that as you're building a company and when you're new, you get a ton of advice. Advice is free. And oftentimes when people are giving you advice or giving you an advice from their perspective like, hey, this is what I wish I did, right? Your scenario might be completely different. Your problems could be completely different than the person who's giving you advice. And so if you end up following all this advice, you end up distracting yourselves with with things that don't matter. And so kind of like in the journey of every founder, when you're like a few months in, you realize, okay, I got to start getting really good at saying no or pushing back on advice and like, hey, let me cook. Right. As long as you're doing the ethical things and working hard and, um, being genuine. Like people will people will not take offense to that. You say no to advice. And so ultimately, you know, you have to find what are the few pieces of advice you're going to live by. And then what are the what are the things you're going to ignore and continue down your path? And I think in general, if you have a great co-founder that you have a perfect alignment with, and that's a superpower. But I feel like eight out of ten people that have co-founders, when I talk to them in private, they they're always kind of trying to work through some issue. And in their head, they're pretty clear about the direction they should take the company in. But then their biggest blocker is I have to align with my co-founder, especially in the early days when things are kind of like up in the air, you don't know what the product you're going to build or whether you're going to pivot next month or whether you're going to reposition the company. And so having a great co-founder, you just like. Perfectly aligned with is is a superpower. But most people I talk to don't have that. And that means should you, should you let finding a great co-founder be a blocker? Not necessarily. Get started. Start making progress and see if you meet awesome people along the way and bring them on onto your founding team. Um, and yeah.

11:17Julian Weisser: It seems like

11:20Julian Weisser: choosing to be solo or being solo by default ultimately has a bunch of implications for how you run the company, or how you think about things like hiring. I'm curious. You know, how that's played out for you with Julius?

11:34Rahul Sonwalkar: Yeah, you have to hire much sooner than other companies that have co-founders. Um, and that's number one. When you're starting off, you have to find smart people to come work with you. And I think in general, the the recipe for building a great startup is, you know, find a problem that's really big. Um, and a lot of people have and there's they're willing to pay for it and then build a great product that solves the problem and then hire the smartest people you know. When you have a co-founder, you can kind of delay a couple of those things. Um, but ultimately, the recipe is the same whether you're solo or you have co-founders. Um, when you're solo, you still have to, you know, convince people. A big misconception with solo founder Solo founding is, hey, I can if I'm solo, I don't need to listen to anyone. People just will listen to me and I'll tell people what to do, and they'll just do what I say. And because I control most of the company. And, um, that's not that's not true. You know, ultimately smart people, they're not gonna listen to you just because you told them to do something. You have to convince people and to get the best work out of people, they have to be excited about the thing that they're working on. It shouldn't just be, I'm doing this because the founder told me to do it. It's like I'm doing this because. Hell, yeah. This should exist. Like, this makes so much sense. And doing that over and over for, like, every feature and every, um, every part of the product and every part of the, you know, whatever the customer is facing. Getting that, um, get people excited about that is work, right? Um, why should smart people come work for you if you're just a just an asshole, you know.

13:13Julian Weisser: Be ultra good at convincing. You have to essentially offset that.

13:16Rahul Sonwalkar: Yeah, essentially offset that. Exactly. Um, and you have to essentially offset that and be altogether convincing because you're going to convince somebody and then like, shift your focus onto something else, and you have to put the faith in that person, that okay, now that I've convinced this person that they're going to go execute and convince other people on the team to go execute on that. Um, so you have to find people that are multipliers. So the way I think about hiring is find people that you can put a lot of faith into, because you're going to focus on one part of the company for some time, and then shift your focus to another part of the company, and then you have to put the faith into the people, um, to go execute in that direction. Right. So when you come back like next week or like a few days later, a few hours later, like there's progress and you have to find people who will sort of multiply you in, not just you delegate a task and they go execute the task and then they wait for the next instruction. They just sort of like take a direction and just kind of go execute in that direction. So people you can put a lot of faith into, and then people who are ideally better at you than the function that they're responsible for. So pretty much every engineer, Julius, is better than, better than me. I used to be an engineer before this, and one of my things was, I need to be the worst coder on the team. Um, um, everyone that does like growth stuff, they have to be better at me than than I grow than me. And so if you find people that are better than you, then convince them to come work with you. Um, and put a lot of faith into their work. Because when you have a co-founder, you can kind of, like, split the company functions into two. Right. As a CEO, you can do sales and marketing and maybe product and engineering can be your CTO. Um, and if you have three co-founders, you can even split it even even more. But as a solo founder, you kind of have to put a ton of faith into into your founding team now. I think, um,

15:23Rahul Sonwalkar: a lot of times when solo founders think about building teams, they think about, you know, hey, I have doubled equity because I don't have to split the equity with the co-founder. I think I think the right way to do it is to be very generous with the early team in terms of equity, um, because they're taking on meaningful risk when they're coming and building the company with you. And What you have is you don't have the burden of having to align co-founders on major decisions every step of the way, but you still have to find smart people to come work with you. So should the right thing to do there is to be generous with equity.

16:00Julian Weisser: I'm really curious if you have any specific advice around that, or if you've talked to other solo founders and gotten their feedback about this, because I think that, um, we can talk about this more later, but I think that there's this really interesting thing when you actually look at the numbers at a high level, it's very surprising how solo founded companies don't seem to do much different in terms of equity grants. But then when I actually talked to solo founders like you or founders like Paul, or a deal like you actually see that that at these more forward thinking, solo founded companies, they're using this as a huge opportunity, right? Because, you know, you may have raised less than other companies at that point, but you're generally if you're if you're if you're evaluating two opportunities, you're both excited about both companies, they've raised the same amount of money. And once a solo founded company, they can give you a lot more equity, potentially, than a company that has three co-founders already where they might, for very obvious reasons, feel like there's a less equity to go around. So I'm curious if you've heard anything or had more to share about that just for people who are solo founding, because maybe, maybe this is a good precedent to set, you know, for for people to understand this.

17:13Rahul Sonwalkar: Absolutely. Well, in general, people having more equity in your company is good because that means to have more skin in the game, right? You're, um, oftentimes, you know, founders conflate, you know, equity being like the most valuable resource. But like, hey, I'm never I don't want anyone to have any equity. And so you have to find the right balance. Right. If a candidate is willing to take less cash for more equity.

17:42Julian Weisser: It's a good sign.

17:42Rahul Sonwalkar: That's a great sign. Exactly. It's a it's a big green flag. It's like, okay. This person is willing to take less cash. Um, and they want more equity instead. It's like, okay, this person wants more skin in the game. They want more upside and in general. So when we make offers, sometimes we'll like present to options, which is hey, here's a higher cash option. And then here's a higher equity option. And sometimes we'll have candidates that will they'll say, hey, can we go even lower on the cash and get more? Can I have a little bit more equity than the higher equity option. And in general that's good. I've I'm not sure what the data says yet, but anecdotally I have uh, the solo founders I've talked to like Paul and others. Um, what I've noticed is they are more comfortable, you know, giving equity to to early team, especially if their contributions in the early days end up being more than what they were originally hired for. So the first engineer you probably hired might end up basically being the de facto CTO, right? They'll probably end up going and building things. Yet you didn't even ask for or like there's a major outage and they'll like drop everything and go fix that outage. And so those people you want to make sure you end up rewarding, um, over time, um, when they are filling in shoes that they weren't necessarily hired for, but they're just like treating this as their own baby, right? And so you want to bring on people that treat your company as, as their baby. You know, they care deeply about it. And when people care deeply about something, you know, one thing that's going to happen is they're going to have opinions about how something should be done. And when you're sole a founder, that's something you're signing up for. Is is, hey, people are going to have opinions about this company. Um, and I have to be really good at hearing their opinions and communicating what direction we're going to go in. And just because I'm a solo founder doesn't mean I can just tell them what to do, because the smart people will leave. So people thinking all the time, you know, thinking about your company, thinking about how to make it better, how to make the product better is good. You should reward those people with more equity. Uh, because equity is good. It gives them more skin in the game. And you have plenty to give out a solo founder.

20:06Julian Weisser: Yeah, I think there's something that's quite different between co-founders and solo founders when it comes to culture. And when you have, let's say that you have, you know, there's two co-founders or there's three co-founders that are startup. Um, that second person and the relationship with the first or those second two people in the relationship with the first, they they kind of ultimately create a culture, you know, with just that small group, just the founders would. You're a solo founder, though. I feel like when you add that first person, it's it's much different than adding the first person when you have co-founders already. right? Because culture, I think, is often best thought of as the way that people relate to each other and in their environment. And if you're solo, that you don't really have a culture yet, you have sort of the, the, the inputs that would inform a culture once another person comes into the fold. So I'm curious how you've thought about culture and what you've learned about culture when you've brought on people and sort of built out an organization?

21:07Rahul Sonwalkar: Yeah. Um, culture is really important. And you're right, when you're a solo founder and when you're like two people, the other person is 50% of the company. When you're three people, you saw the founder. The team is like 66% of the company. And so they're going to have a lot of influence on how the culture gets formed in the early days. And it's true, like whatever your culture is, when you're 3 or 4 people, that's going to end up being the culture when you're 20 people or bigger. I like to think about what Mark Zuckerberg said, um, About building his early leadership team at Facebook, and one of the advice he got from Peter Thiel was, you know, Mark, you should make people that you like spending time with, you know, your core executive team. Um, and that's kind of how I think about recruiting and culture in the early days to is, man, I'm going to spend 14 hour days sometimes, um, just in the office. I might as well work with people that I look up to and like hanging out with, uh, because if I'm going to spend that long in, in the office five days, six days a week with somebody, I might as well work with people I like hanging out with. Um, and I learn from and they like hanging out with me. So ultimately, like, what you want to end up doing is finding those people that you like hanging out with. Um, you learn from, um, it depends on your company culture, how you want the culture to be. But if you kind of end up finding those people, then the culture that gets set in the early days oftentimes will be a an extension of who you are as a person. Um, as opposed to if you find people that are very different than you, um, you know, and you don't enjoy spending as much time with, but it's more like a practical marriage as opposed to like a, you know, marriage out of love. You, you you will have this culture that's very different than who you are as a founder.

23:06Julian Weisser: How do you think people would describe Julius as culture?

23:10Rahul Sonwalkar: We're very like hacker oriented. So, um, the early culture that, you know, I used to go hackathons back in college, and I like to go from idea to like something, live within a day or two at max. And so it's a lot of people in the company, you know, they have idea like go build it feature in Julius, um, go make it live in the product even when it's like not fully tested or working and see how people use it and then use that to inform like whether we should continue building it or iterating on it. And so a lot of the culture is just like tinkering and hacking on different features and different ideas, as opposed to here's a central roadmap in the company, and this is the exact thing that we're going to work on. Um, it's very fluid. Luckily enough, it lends itself perfectly to like the AI stuff that's happening, right? The models are constantly evolving, there's new capabilities that are getting smarter, and so things that weren't possible a few months ago couldn't have been conceived a few months ago, are now possible with the latest models. And so like this constant tinkering and like building and and like hacking on different features and ideas is kind of like what the culture is. And another part of the culture is in general, people just like are always just making jokes in the office. There's like some pranks going on. Um, or, um, people make fun of me all the time in the office, you know, they'll and and so I'm totally okay with people like making jokes about me and, you know, so there's this culture of like, hey, it's okay to, you know, say whatever about Rahul. He's not going to take it personally. And so it makes everything very lighthearted. Um, so there's like, you know, we don't have a meme stand in slack, but there's like any there could be memes in any channel.

24:48Julian Weisser: Yeah. There doesn't need to be a memes channel.

24:50Rahul Sonwalkar: There's there's no HR approved, you know, memes channel. There's just memes. You know, there's infra debate going on, and the means will just pop up about Marcel or about coffee and so on. And so that's just like who I am as a person. Like, if you, if you and I were having a serious discussion, there would be sometimes we're all just like, go off on a tangent and just start making jokes about something. And that's just like who I am as a person. And so that's kind of like what the culture ended up being in the company.

25:17Julian Weisser: The sort of tinkering and, and sort of DIY aspect of all this seems extremely beneficial for kind of what you're working on. But I also know that you went through six ideas, something like that, before you got to what you're building with Julius today. Maybe you could share a little bit more about that, because I'm guessing you were doing that mostly solo through those ideas, if not the entire time. And I think that it would be really interesting for people to hear just, you know, what that actually was like, how you knew one to move on to another idea. Um, it just I think that very often we hear the story of, oh, there's one pivot. And then and then we find this amazing thing people, people know about pivoting, obviously, and they sort of glamorize pivoting, maybe. But I think that six is is actually not a crazy number. I've heard a lot of people over the years who've gone through similar journeys where they're pulling threads or they're hopping to new ideas. So I'm just curious what that was like for you, and particularly if you were doing it solo.

26:19Rahul Sonwalkar: Yeah, the first few were definitely solo. Um, you know, before I started even started the company, um, I spent like half of Covid building different mobile apps. You know, I got really into podcasting and listening to podcasts, and during Covid. It was just so lonely. You know, you could barely hear any humans talk. You're in your apartment all day and so listen to podcasts all the time. And I was building different ideas in that space. And my, my plan was, hey, once something starts working, I'm going to go all in on that idea. And after about a year of doing that, I realized, man, nothing's really working. And I'm kind of just tired of waiting for something to work. So I'm just going to quit my job and just go all in and do it.

27:01Julian Weisser: So this is all this is all sort of pretty. Quitting your job. You spend about a year sort of working on this stuff part time.

27:08Rahul Sonwalkar: Yeah. Um, and but then and then the six pivots happened after that. Got it. So when I started, the actually started the company, I was seeing GitHub copilot kind of like starting to work, and it was helping me as a, as a programmer. And I wanted to see if it could help people write queries and analyze data. I didn't know what that was going to look like. Uh, but this was like the loose direction I wanted to explore, and it took six pivots from that. Like lose direction and a lot of improvement in model capabilities to arrive at Julius and along the way. You know, the hardest pivot once you have started a company is the first pivot because you have told everybody you're going to work on this idea and it's going to work, and you've told your friends, your family, your former colleagues, um, your, your, you know, girlfriend or your boyfriend. And then a few months in, you realize, oh, it's kind of not working. Um, and shit, I gotta, I gotta, I gotta pivot now. But I've told everyone that I'm going to work on this thing, and, man, I don't want to go to this Thanksgiving dinner and, like, tell people I, I, I'm working on a different idea now. It's going to be kind of embarrassing. Um, so the first pivot is the hardest. But once you get past the first pivot, when you when you're a formal company, then you're kind of free to fail again. And what you want to do is, you know, keep exploring, iterating until you like, feel a pull. And then the moment you feel a pull, you double down. Now, I've talked to solo founder friends that are still pivoting. And because they're completely solo, what's what has kind of happened is they don't have much of a accountability. Mhm. Um, and so at the slightest friction or sign of trouble they're like okay it's not going to work. Let me go find something else. Turns out every great idea, there's a ton of friction to make it work. You know you're pushing a rock uphill. Uh, and then and then when you hit PM, it feels like kind of all rolling downhill. Yeah. But. So I think having people around you as, like a founding team or like a co-founder, I think builds up some accountability. Like, you know, we're not going to pivot at the first sign in trouble because we have invested so much time and energy and mental focus into doing the first launch. And so I think, you know, when I brought on a, you know, a couple of my friends to be part of the founding team that actually ended up building a lot of accountability in me to, like, not give up on the or like, go back to the whiteboard at the first sign of friction and to kind of like, continue exploring. Um, and ultimately, like when you're pivoting in a direction, the good thing is all the learning is compound, right? Even if you build and launch something and doesn't get users or you get you get few users, but they don't retain, that's all learning that you can then apply to the next iteration of of the idea. And so kind of having a direction, having like a couple people that can hold you accountable is is good.

30:11Julian Weisser: What was the thing that kind of got you to wants to focus on that direction? Because I think that that was one of the things that maybe when I was listening to prior conversations you've recorded with folks, it sounded a lot more like, hey, you know, I tried a bunch of different things, but I don't think that you ever shared as much about the through line Through all of those ideas. And what was the thing that kind of inspired that? And the reason I asked is because I think that oftentimes people, when they're trying to figure out what it is that they want to work on, sometimes they just start with anything. But it seems like you started with this, this premise that you wanted to explore, and then you kind of just almost it's funny because I think that your, your, your logo is like a bust, right, of Julius Caesar. And it's, it's, it's like revealing the, the sculpture in the marble, right where you're chipping away at the marble block and you're kind of finding this, this thing underneath, but it doesn't necessarily look or present properly for a while until you actually kind of reveal the sculpture. So I'm curious what that was like, how you thought about kind of what you wanted to pursue and what advice you might have for people there in terms of finding that general area to sort of direction to go in.

31:22Rahul Sonwalkar: I love that I've never actually thought about it as like, you know, taking a piece of marble and you're kind of building chiseling the sculpture. It kind of doesn't look good until it's like the final product. But. But that's beautiful. I think I might use that again. Um, but I think that's the perfect kind of like metaphor for building a company. You know, you you look at, like one of my favorite things to do is go to, go to archive in an archive and like, look up websites of the products that we admire today.

31:51Julian Weisser: On the Wayback.

31:51Rahul Sonwalkar: Machine, on the Wayback Machine. Exactly. And like Figma back in the day or, um, like Zapier back in the day, or like, you know, OpenAI first website, like they, you know, it it looks so it looks like anyone's heck of a project. And I think that's kind of awesome, you know, because all, all great things start as, like, something very basic or, uh, simple looking. You don't have to be perfect from the start. And so you need to have conviction in something. And the, the way you know, it evolves could change. So for example, um, you know, the cursor guys who were doing AutoCAD. And then there's Michael has this like old Hacker News post about, you know, cursor as like an email autocomplete tool. And email is so different than coding. Um, but you know that's so, so they kind of like spend some time in even figuring out what direction they want to build in. They knew AI was going to be transformational. They didn't know like what their calling was. And so everyone sort of has like slightly different paths to how they get to a place. For me, it was I was an engineer at Uber, and so I was obsessed with like, you know, like, uh, data in like, um, how can data and data science help people? And I was seeing programs like, you know, programing get really, really good with tools like copilot. This is pre ChatGPT. And I was I wanted to see if they could help people analyze data. Right. I thought data is like the, you know, the bare bones of every business decision out there. And if you can help people analyze data, um, in plain English, that's awesome. I started with like, logistics data because I was in this like local minima at Uber, uh, after doing stuff in like in that space for like three months, I realized, man, it's nearly impossible to convince a logistics company to adopt AI and, like, use AI to analyze data. But what we're building seems promising. There's something here. And maybe, like, we just need to build a general tool. And so we build this thing called Excel Copilot, which was like a copilot would help you write Excel formulas. Um, and we got this seasoned desist from Microsoft, and they're like, hey, guys, you're calling your thing Excel and Copilot. That's double bad. Like, both of our both are our trademarks. And so you guys got to shut down right now. But the early usage on that thing gave us more conviction. Okay. There's something with like, people analyzing data with natural language. And then so some of the next things we launched was, okay, what if we query every single data point about the US census and make it really easy to like, analyze that data with plain English and AI will just like write SQL and write queries and do the analysis for you. Cool. Okay, let's go build census GP2. Com and so we build that launch as a demo open source the code. Um, and a ton of people use that on the first day. You know, you can ask all these questions like, hey, what is the gender ratio for different neighborhoods in SF? And people love asking that stuff. Um, and so we build that, we launched that. And um, a lot of users first day, nobody uses second day because it's not a, it's not a problem. People have people don't have questions about the US census.

35:07Julian Weisser: I didn't think to play with.

35:08Rahul Sonwalkar: Yeah, yeah, it's a fun thing to play with. But we that gave us some more conviction that, okay, the technology kind of works and people are curious about data, but not the census data. And so we kept iterating in that direction. And it took us another four months and a couple of more launches where we just tried more public datasets until we realized, okay, the people, the thing people actually care about is their own data. Especially if you want people that use it daily or weekly. It's people that use work data. Um, and so we we build that, you know, bring it on data, analyze it, launch it and launch it. And then that became Julius. So it's not a straight line. It's a lot of, you know, um, kind of like having a direction or Northstar kind of exploring in that and um, and kind of like taking learnings at each step and deciding what to do next. Um, and that's, that's how we average Julius. I guess we started just like a block of marble. And I've been chiseling away, hopefully, like in the next five years, we have a nice looking bust of Julius Caesar. You know?

36:16Julian Weisser: That's amazing. Well, you already have it on the on the logo on the website, so, uh, so that's great. I think that something that I'd be very curious to hear is kind of how you think about, um, how you think about that. We talked about this before we started recording, like, convincing. You talked a little bit about it since. But this idea of how you've had to convince people of different things over your time as a solo founder, and I think that ultimately, uh, you know, it often is the CEO who has to do the convincing. But but generally you have you have split more things across co-founders generally when you have them. So I'm curious, like how convincing people has been a part of your journey and sort of how you think that might have been different had you had other people on your co-founding team?

37:04Rahul Sonwalkar: Yeah. Um, so,

37:07Rahul Sonwalkar: you know, I guess the premise is you have to kind of convince people, you have to convince the first investor to give you money, and you have to convince the first customer to use your product. Um, you have to convince the first founding employee joint. Come work with you and you have to do that over and over. You know, when you're raising money, you're doing, you know, trying to get users and customers and you're trying to get people to come work with you. Convincing is a core part of the job. And having been on this journey for three years now, I think if there's one thing that I've done the last three years I'm probably going to keep doing forever is convince people to do things. Um, and I think the only thing you get that makes you good at convincing is trying to convince people like it's, you know, the more reps you get, the better you get at it. But a great starting point, I think, is having deep conviction in the thing you're trying to convince people off. It's really hard to convince anyone if you don't actually truly believe in in the thing. Um, in a sort of like, just delusional level of of belief in the thing that, hey, I think this, this thing has a slim chance of working, but I think it's gonna work. And here's why I think it's gonna work. And here's, I think, all the things that need to go right for it to work. And I think here's why. Um, we are the right people to go build this thing. Um, here's why. We have an unfair advantage and here's why I think the timing is right. And so having that deep conviction in the thing you're trying to convince people of is, I think the core prerequisite. And then the other is, you know, just more reps. Um, kind of I don't know if you've seen The Wolf of Wall Street, Jordan Belfort, you know, you know, there's this, um, you know, at the end and there's this ending scene like, you know, sell me this pen. Um, I feel like that's that's not really what it what building startups or doing sales is like, you know, you're not trying to sell a pen to anyone. I don't think Sam Altman can sell me a pen. Salomon could convince me of AGI, and he can convince me to, you know, like that, that, you know, there's going to be a major scientific breakthrough with AI models in the next, you know, 12 to 18 months, because that's the thing that he deeply believes in. And so I think, you know, in terms of convincing the the just having deep belief in and in the thing that you're trying to convince people of is really important. Now, you want your message to be simple enough that your team can adopt that message and then carry it forward. So, you know, let's say you're recruiting an engineer as a solo founder, you can do all the interviews. You can do the first screen or the last screen or maybe one of the runs, but then your team is going to end up doing some of the other rounds. And at each step of the round, you have to convince the candidate. It's kind of like a mutual fit evaluation. You're trying to see if this person is good enough, smart enough to come work with you, but then if they're smart enough, they're probably going to have a lot of other options, you know, to convince them to pick you over all other options. And so you want your team to get really good and doing the convincing too. And so when you have co-founders, you know, sometimes that's kind of like, uh, that responsibility is less on you because they can also do a lot of the convincing. Um, but when you have a founding team or like your own team as solo founder, you want to make sure that you're empowering them with that message. They understand how to convince people they deeply believe in it, too, and then give them the reps so that they can get good at it and kind of like pass that message forward.

40:51Julian Weisser: It's often talked about how, oh, solo founders, they have 100% ownership. And obviously that's not true. You know, as soon as you start to have investors and you start to bring on people, in fact want to be probably more generous with your equity. Um, and I'm curious, uh, you know, I think that while the 100% ownership thing is a bit of a is a bit of a mirage. I think that one thing that's that's very interesting about solo founder companies is authorship. And it feels like In some ways, there's less ambiguity around sort of who the author is, especially when the company is getting started and that sort of sole authorship in the beginning can cause for be cause for very interesting decisions and important decisions to be made about sort of culture and about hiring and about product focus. And I'm curious just if you have any thoughts about authorship and what that means to you.

41:44Rahul Sonwalkar: What does authorship.

41:46Julian Weisser: Essentially think about, like an author of a book? Right. There are people there are so many people involved in making a book. Right. But if you go to a bookstore and almost all of the books on the shelves have one author, yeah, but they have incredible teams involved at actually making it. So I'm curious how you think about, like, that aspect of startups versus people in many ways, like authorship is much more collaborative. If you have co-founders and you kind of have a book with multiple authors. In that regard, I'm curious how you think about that.

42:16Rahul Sonwalkar: Yeah, I think, um, when you're, you have to be very generous with equity. But I think you have to also be very generous with authorship and giving credit where it's due. Um, I'll say this. I, you know, Julius wouldn't be possible without the people that have come and built this company with me. Um, and I think they deserve an equal credit, if not more. You know, um, there's certain decisions in the company where I

42:44Rahul Sonwalkar: probably shouldn't have any, any authority to make the decisions, for example, like our infrastructure. Right. Like we're trying to figure out, hey, do we stay on GCP or do we go to AWS and like those decisions? I'm maybe two years ago, maybe I could like have a strong opinion on that. But at this point, um, I have put a lot of faith into the Inferno team that we have hired and built to be able to make that decision. And if they need me to come be an unblock or tie breaker, I'm happy to do that for them. But that's where like, I'm putting a ton of faith into that team to be able to make that decision. And so in terms of authorship, you know, we wouldn't be able to build the best infrastructure for data analysis for AI with our infer team. It's just they deserve the full credit for that. Our product engineering team really good. They're they're obsessed with like, you know, building useful things with AI when it comes to data analysis and data science. And my goal is to just bring the best people and then give them the most, you know, agency and power to go do things, um, and then celebrate them when they go get some, get the company some wins. Right. That means, you know, when we're launching a new feature, oftentimes our engineers are the ones doing the product launches. Um, and they'll be in the video and they'll talk about it, or they will talk about the kind of like journey of building that feature on their own Twitter or on their on the on LinkedIn profiles. And it's sort of like people kind of want to be part of history, right? People kind of want they don't want to. You don't want people that are kind of just want to do the 95 and just go home and and relax. Um, especially in the early days, you want people that truly feel like, hey, this is their baby. And and you don't want, you don't want, you know, one person to be the father of all success and success, as many fathers. And so I think you're equally important to, you know, equity ownership is sharing credit and kind of like empowering your team so that they feel the agency that I have, I have a part in, like building this thing and I, um, I, I'm like one of the founding fathers of this thing.

44:48Julian Weisser: So Paul from Browserbase was just talking about this. He was talking about this idea of not just building a brand around browser base, but also helping other people sort of lift themselves up and get credit in more visibility for what they're doing. And, you know, in their case, they've got sort of the the icon, the B icon next to all their teammates on, on X. And um, and you're talking a little bit about how some of the product launches might actually be done publicly by teammates. I'm curious what advice you might give to founders who are wanting to really give that ability for people to develop their reputations, which helps build the reputation of the company? Right. Because the company isn't just the founders, it's all of the people who are doing all this amazing work. So what, what, what recommendations or what have you done with Julius? That's been good to help lift up all of the people and make sure that they're able to not just be seen for their work, but also be seen as these incredible people that, you know, potential teammates might want to join and work with.

45:56Rahul Sonwalkar: Absolutely. I think, you know, when you're a founder, the company becomes your identity and you kind of want to let that happen with the team as well. You want. You want to let the team, um, let them make the company their identity. So you'd be surprised people actually like doing that, because that gives them a sense of ownership, and it kind of like a sense of shared mission that, okay, this company is is me and I'm this company. Um, and and just that's just like another form of, like, skin in the game, right? Then the success of the company depends on, like, their personal brand. And a lot of their personal brand is built with the company's brand. And so that means, you know, you can, you know, little things like, you know, my friend Adi at OpenAI, he'll like, go do live customer support for people, um, on Twitter, uh, when they have issues with API. And he's just an engineer there. But OpenAI's incredible job where, you know, OpenAI has nothing without its people, where if people kind of see OpenAI, if you if you work at it as like a core part of your personal brand, and that's just like incredible skin in the game where you think of the company as your baby and you want to succeed. And as the company brand grows, it kind of uplifts your personal brand. And and I think that's kind of magical.

47:15Julian Weisser: Awesome. Well, thank you so much for doing this. This is great. Is there any question that you think we should have been talking about around solo founding? Or maybe actually, maybe this is a good way to close it? I would love it if you could maybe give first sort of the bear case for being a solo founder. Um, and then and then after that we can get to sort of like the positives, but maybe we can start there. What's what's the reason that somebody shouldn't be a solo founder?

47:42Rahul Sonwalkar: You should not be a solo founder if you

47:46Rahul Sonwalkar: don't like convincing people and you just want to go on your path and and you just want people to listen to you without any convincing, um, terrible idea to be a solo founder. I need to be a founder. Period. You also not be a solo founder because it's incredibly lonely. The the the lows are just the loneliest. You know, you don't have somebody who can really empathize with you. You'll have found your friends who will. Who will have gone through similar stuff. And they will, you know, offer you some, like, empathy. But really, no one's feeling exactly what you're feeling. So, um, you know, being a founder is lonely. Being a solo founder is incredibly lonely. And oftentimes you will burn out when you aren't able to multiply yourself like your company needs your help. The founder help on. But let's say recruiting and marketing and product. And there's only one thing you can focus on at a time that's going to burn you out. And so for all these reasons, like solo founding is kind of hard and like, I don't recommend it to a lot of people if you think those things aren't aren't what you're excited about, that's great.

49:02Julian Weisser: That's a that's a real stuff. That's that's all extremely accurate. And it mirrors some of the things that other people have said. Uh, now I think it would be great to hear sort of after we've kind of started with the negatives. What's the what's the case for solo founding?

49:18Rahul Sonwalkar: The case for solo founding is. Um, it's incredibly low friction to get started. If you want to build a company, you can get started tomorrow, right? Go build a first prototype. You can go talk to users. Try to onboard your first customers. Try to get your first investors. You're not blocked by having to find a second person to come. Be a co-founder. You don't have to waste time on like co-founder matching and trials and and then aligning on every step of the way in the early days where everything is just kind of up in the air, right? You don't even know if it's going to work or not. Uh, you don't even know if you have to scratch the whole thing and start over. Um, and so it's incredibly low friction to get started. The second bull case for being being a solo founder is there's going to be critical times in your company when you have to make super critical decisions that could change

50:19Rahul Sonwalkar: the trajectory of the company. You know, it could be, you know, a pivot. It could be a direction. It could be, you know, a key hire. And when you have deep conviction in something, you can just go make the decision and not have to spend a bunch of time aligning 2 or 3 people who could be major blockers, that decision. And so those two are, I think, great, bold cases for why solo founding I think is is awesome. You know, I've, I've met countless people that are really smart, really competent, and they're blocked on starting a company because they don't have a co-founder. Um, in some ways, I think that's kind of I think it's so often it's kind of stigmatized. And I hope like this, the work that you're doing, um, kind of destigmatize this solo founding.

51:08Julian Weisser: That's awesome man. Well, thank you so much for doing this.

51:10Rahul Sonwalkar: Of course.

If you're already solo, you're early.

Whether you're solo founding now or still exploring, stay in the loop.

© 2026 Solo Founders. All rights reserved.

Privacy PolicyTermsSan Francisco, California