Episode 25
B2B Software, No Technical Co-Founder
Published · 1 hr 8 min
John Glasgow is the anti-pattern founder: non-technical, 36 when he started, a newborn at home during Y Combinator, and solo after his co-founder left within weeks. After 15 years in corporate finance at Adobe, Fidelity, and Invoice2go, he built Campfire, the AI-native ERP fast-growing companies use to replace legacy systems. This is one of the most tactical conversations we've recorded.
What John talks about
Pick a question to ask it of this episode. Answers come from the transcript.
Transcript
Transcribed automatically, so names and words may be wrong. Each time opens the video at that moment.
0:00John Glasgow: You should have a co-founder if you're non-technical was always the pitch to people like me. Now, I don't think that's true with the ability to write code with AI. Now anybody can be a solo founder. Why large companies move so slow as the sheer amount of cohesion and coordination required to do anything at all at a small level. Co-founders have that too.
0:18Julian Weisser: What's the barricade for being a solo founder?
0:21John Glasgow: The odds of success as a founder are so low. You need every single tailwind you can get because the expected value is zero.
0:28Julian Weisser: So it's 2023. You find a co-founder, you fly with an idea. You get into YC and then you end up being solo. Sort of after going all in.
0:37John Glasgow: You might have a debate with your co-founder on is that a good use of time? When you're a solo founder, you have so much clarity of what to do next and where to go.
0:45Julian Weisser: 66% of companies fail because of co-founder breakups. Being a solo founder, you don't have that risk.
0:51John Glasgow: There's no better way to do it than just solo.
0:55Julian Weisser: A great place to start off would be to talk about how you actually came to start a company with your brother, who's also a, you know, a founder and is running a series B company now. So I'm curious what that experience was like. First, how you decided you wanted to start a company together?
1:10John Glasgow: Yeah, it's a great question. First, thanks for having me on the show. Um, my brother and I, and it brings up this classic, like nature versus nurture because we're identical twin brothers and we grew up in San Jose, so maybe that's the nature piece of, like, Apple was down the street, like Intel was there, like tech was kind of everywhere in the 90s growing up. But ultimately we even had like a iPod accessory online store in high school. And you could buy like iPod cases and like step out of class, take a customer support call. So we were always a little entrepreneurial. And again, maybe it's a bit of the nature and nurture there. But then yeah, right. When we both graduated college, we both went to school in San Diego. We decided to start a company which looks a lot like what Pinterest ended up being, uh, around social shopping and social kind of aggregation and urban social around pictures. And I learned a lot in that experience. But I think my biggest takeaway was needed to get a lot of life skills and needed to really find a category that had some unique insights, like my ability to help people shop or do something they're ultimately found. I didn't have anything unique to me, but being a co-founder with him, I mean, we were living together as well. And so there was like a we would wake up, um, and we would walk over to our kind of computers, and then we would work all day and we would walk back to bed. And it was just literally some days we didn't leave the room at all. And so having a co-founder and, and building with him, um, and this was almost 20 years ago now. And so then just went on to have a finance career for, uh, called 15 a little 15 years between then and starting campfire. Uh, it was, uh, it was quite a journey until I became a second time founder.
2:58Julian Weisser: When you guys started out working together, I think it was just really useful because people are listening. They're thinking about, should I have a co-founder? You know, if I have, if I have a co-founder, who should it be? And, you know, traditionally they say go and work with somebody that you've worked with previously or somebody that you know really well. Siblings are not as common, but there's somebody that in theory, you know pretty well. What was it? Was it sort of just an organic thing that kind of said, hey, we're both interested in something. We're going to start a company together. What was the actual the actual origin of of deciding to work together, and how did you actually sort of align on that, or was it just sort of an organic thing?
3:32John Glasgow: Yeah, we really want to start a company together. And so we just worked through a lot of ideas together and a lot of late nights prototyping and iterating and obviously way before vibe coding. And the speed of code is much different back then. But yeah, we just we're like, hey, we really want to do this together. This is like an active decision. And so all the ideas kind of came out of us working on together him and more on the technical side, me and more on the business side, and that was really the focus at the time for that one.
3:56Julian Weisser: Now, the company that you ended up working on, you said, is sort of like something that that kind of is like modern day Pinterest. But for quite a while it was early. In a lot of ways. Um, can you share a little bit more about how you ended up deciding to work on that idea together? Like, was there one person who was really driving the idea search? Were you all working on it together? Because I think that ultimately, sometimes when you look at co-founders, there's one person who's kind of like the idea sort of originator and the other person who's really excited to just work on something that maybe have momentum or, you know, can have a really big sort of opportunity to do something good in the world. So I'm curious, kind of like how that actually played out between the two of you.
4:37John Glasgow: Yeah, it's a great question. We would. I mean, we obviously would go shopping together because we lived together for close and would like, look online because, you know, classic guy like, I don't like going to the store and like shopping for clothes and trying everything on. And so like when I was just shopping online, I remember like being on the Nordstrom website and there was just like, I don't know, like 100 pages of shoes and like 99 of the pages were like, these are the worst shoes in the world. Like, who would ever buy these? And it felt like the long tail of the catalog, like nobody wanted to look at. And there's a lot of like, noise in online catalogs. And then you would go on to Amazon and God forbid, you look for clothes on Amazon. It's even longer tail of of things people don't want. And so then it was like, well, how do we surface? Anybody kind of think of where Pinterest is today? How do we surface things that are actually like people want to see or shoes people want to see or clothes someone might want to buy? And then could you build like a collection of items that you would want to buy? So then when you're browsing Macy's or Nordstrom or any website you can like, save an item and you can build a little catalog of of clothes or things you'd want to buy. But then other people could look at other clothes that are popular and they can, like, skip all of the noise and just like its signal. And then, you know, fashion is very subjective, of course, but then the ability to see what maybe more fashionable people are buying or looking at or finding some website you had never heard of and finding some great attire, and that was really driven by both of us, maybe because we were identical twins, but we had the same shopping challenge on browsing for shoes and clothes that, um, we just, you know, thought there was a lot of wading through terrible clothing. And so how do we how do we solve that and help others surface, uh, high quality gear?
6:24Julian Weisser: Now, ultimately, you know, it didn't work out. You ended up not continuing working on it. What was the. I think that there's a there's a thing that everybody talks about is like, how do you come up with the idea? I think that the thing that most people don't talk about is like how to actually decide we should not work on this anymore, and maybe we shouldn't even be working on a company together anymore. And I'd love for you to share a little bit about what that realization was like. Maybe in hindsight, maybe what you would have done differently. Yeah, I think it would be really interesting for people to hear that.
6:51John Glasgow: Yeah. Well, I think, um, look, consumer is incredibly hard. And having now gone through Y Combinator, you know, at least when I went through it in 2023, it was very hard to get funded for consumer. And and I think like in hindsight, I see why it ends up being incredibly binary of either or Facebook or we have no revenue at all and we don't go anywhere. Um, you know, having gone on and working at a place like Adobe and seeing B2B, like you can get to a million in annual revenue and B2B, there's like paths to like, so. Sorry. Social consumer is is incredibly challenging category. I think that was the insight in hindsight. And we had this two sided marketplace of we had to go we had to we had have a network effect. So we ended up like paying people to like shop and browse and help populate it. And then we ended up like trying to onboard merchants to help kind of support us because some of them would block like some linking or they would like weren't supportive of it at the time. And so then it was for us, it was like really hard to jumpstart it, particularly because we didn't have a lot of funding. And we have a lot of time because, you know, funding buys you time. And, um, my, my wife was actually early at Pinterest, so she still gives me a hard time about, uh, about that one. But, uh, that was the big insight for me was obviously in the social consumer, but I think also, um, B2B um, and then I would just say like, what is your right to I mean, we all shop, everybody in the world shops to some degree. So I didn't have anything unique there. And so, you know, the second time around it was more of like, where was there something unique in a category that I had some experience that I felt could have more of a repeatable motion, which to me was B2B.
8:37Most people think that starting a company without a co-founder is a bad idea. We believe the opposite that solo founding will become the default way. Great companies get started. And that's why we built the Solo Founders Program, where solo founders spend three months in San Francisco building solo together. Our alumni say it's like having co-founders, but getting to make their own decisions. And for cohorts in, we're starting to see just how much solo founders can accomplish. One secured a formal partnership with a major US government institution just five months after incorporation. Another hit 20,000 GitHub stars and 3 million downloads, and a third got to 2 million ARR before making a single hire. The demand for the program continues to grow. Our first cohort got 1000 applications for six spots. Our fourth cohort got 4500 for ten, and today we were officially opening applications for cohort five. We'll select about a dozen founders. I'll work closely with each of them and will invest $100,000 in every company. We kick off September 10th. If you're building solo or you're ready to start, apply at solofounders.com.
9:46Julian Weisser: You almost said the phrase right to when, and I think it's a really important phrase and an important idea. Could you share a little bit more about sort of what you've learned about that phrase and what it means, and how founders should think about that?
9:58John Glasgow: Yeah, it it really comes down to like campfire were where finance software for corporate finance teams. I had a 15 year corporate finance career before founding campfire and so right to win. You know, I a lot of the YC founders before me, um, they've they've got some unique insight or they've they felt the pain. I think that's always a good one. But the right to win might end up being you've got engineering prowess in a category that others don't, and maybe you don't actually have you maybe you've not felt the pain, but there's something that you can do differently. When founders tell me, like, I'm going to outwork everybody. I mean, we're all doing, you know, 800 hours a week. So that's not a right to win, but it's going to be more of like, do you have unique going to go to market? Do you have some something that, you know, access to some celebrity network? Do you have something that you can use, um, to win the market. And so again, for me that was like felt the pain as a customer and lived the category and been in the category for a while. The second time around, the first time around. And hindsight, there wasn't a right to it.
11:07Julian Weisser: So the the really interesting part about all this is you decide to stop working on the first company, and then you work for 15 years on something else, like on a bunch of different companies, before you actually start your second company. A lot of times, you know, people just try and jump right to the next startup or have a very sort of limited period in between and kind of just jump back in. I think it's because they feel like they like the idea of being a founder. They want to be a founder. It didn't work out. In your case. You really, like spent a great amount of time, developing a lot of experiences that would lend itself to building a great company. Can you share a little bit more about. Was there any pressure to, you know, go and try and find another company idea? What was what was it like at the at the end of the first company? And the thing that kind of like kept you working on, you know, non founder things that eventually led to you becoming a founder for the second time and much, much more successfully.
12:04John Glasgow: Yeah. Well we had raised a little bit for the first company, the shopping one. We'd raised some seed funding through our grad money together because we'd just graduated college, and we went through all of it and was, um, I'm fortunate that I can live with my parents. And so I moved back home in San Jose and they were like, you know, we'll always have a roof over your head. But ultimately, like, I had no money to my name. I mean, my literally my bank account was entirely empty. I have a vivid memory of because I lived back at home. You know, all my high school friends were in the area. I went to go buy like chicken nuggets or something with them, and I had like $4 in my account and the nuggets were like $5. And I called my dad. I'm like, dad, can you like, transfer like $5 into my account? Um, and so I think the reason not to start a second company was like, I was so poor, I needed money. Um, and so I went and got a finance job, and I just graduated for the finance degree, uh, you know, less than a year prior. But this was 2010, right after 2009 financial crisis. And so getting any sort of finance job was almost impossible. And so I just like anybody that would hire me, um, and then I just went and worked and kind of built a little bit of a savings and was able to move out and moved to San Francisco once I could afford rent in San Francisco, and then just kept putting one foot in front of the other and kept building a career. And I always thought about being a founder again, but I never had this, like, strong pull or something of like, wow. I feel like that's something I could be really special at. Like, I never had that specific thought. And so I just kept going on in my career. But I would say the founder experience still allowed me to think very differently in the workplace, even in a large, you know, finance organization that I kind of operated like a founder, even if I wasn't one within a large company. Um, and that was like, like an ownership mindset of the business and being really thoughtful with company resources and like, really like putting in long hours and really, really having high conviction in the work that I did, even if I was, you know, one of tens of thousands of employees. So it was still a great experience and helpful. But it wasn't like, oh, I'm just going to keep working on this and subsequently keep launching ideas. I at that point, I just moved on.
14:23Julian Weisser: If you're at a relatively early stage startup, you're likely to have coworkers who are former founders. Um, and oftentimes people look at that as a really positive thing when they're hiring, as they want to try and hire people who have that agency or whatever that that people say about founders. Right. And I'm curious sort of, did you come across any people like that when you're working with these larger organizations? What was that like? Um, what maybe say a little bit more about what you learned, um, working at larger organizations that maybe went on to help you when it came to actually serving them as as customers?
15:01John Glasgow: Yeah, I would say, um, I worked out a couple of large public companies, one of them being like Adobe, the largest company I've ever worked at. Uh, I worked at Fidelity Investments, which is private, but it's still, uh, equally large organization, and I think deeply understanding, um, to your point. And like, when you learn how to sell back to them, but also partner with them also just doing anything with them, building integration with them, learning the tectonic shifts and how people work within a very large organization like I at Adobe, we spent a lot of time working with AWS, and the easiest way to get a deal done with AWS was actually being the connective glue across AWS itself. Like, it's easier for you to connect the teams and for them to connect the teams. Um, one insight at Adobe you can't just slack a coworker at Adobe you've never worked with. Like you'd get a warm intro to somebody else at Adobe within Adobe. I mean, you need a warm intro, otherwise they won't respond. And so I think just like deeply understanding procurement buying cycles, I learned about innovation budgets at Adobe. Like we had money that ultimately was like always up for just like being thrown at like ideas, like an AI idea, which would kind of be thrown at now or just like very low, um, very low procurement overhead on the purchasing decision. And so then kind of like finding ways to sell into things like that to win, like a pilot. Um, those were some of the big insights. And then also, just like when it's such a multi-threaded sale, finding your way to power and budget owners and what that looks like and asking the questions was really helpful on how I could go back and work with them.
16:42Julian Weisser: And were you on the other side of some of those transactions when you were inside of these larger organizations, you actually saw it, or is it more that you were sort of witnessing it and hearing about it? What what was the actual kind of experience that you gained from being inside on the other side of the table?
16:55John Glasgow: Yeah, I mean, I would say, um, I was on the corporate finance team at Adobe and just very actionable. Uh, I was like doing a lot of the vendor review as the buyer from a finance perspective and doing all of the a lot of the math for like, whether we were to buy software or not. And so literally being the finance person behind the buyer. So some, you know, product leader, someone would want to buy a large piece of software from a finance perspective, I would support them on that decision. And um, and so seeing how all that was done Was this a very tactical example for the software purchasing journey?
17:29Julian Weisser: It's great because, you know, a lot of founders are either former product leaders or former engineers, and they are the people who use the products at, you know, at these companies, but they usually aren't the person who's actually helping to, like, get through the work, the work like or purchase approval process. And I think that that's really interesting. Is there something that maybe you would you could share with folks who are kind of thinking about, like navigating those types of sales processes, things that maybe are not obvious things like I think the the whole idea. I think a lot of people, they'd be shocked that, you know, teammates need to get introductions to each other at Adobe. Are there other things like that that people should be aware of when it comes to working with these large organizations?
18:14John Glasgow: I mean, there's a lot of a lot of things to think about. I think even building a champion. And they will help you answer all of these questions for you so they will tell you, here's the right person and here's how you get through procurement here. And here's how you answer security questions. So I think finding the person for that specific organization that's going to like get the deal done and really navigate all of that is critical. Otherwise you're never going to get a deal done. But they also need to be the right individual that has like some level of power authority. Otherwise they may be giving you guidance at just like fundamentally wrong, even if they're trying to be helpful. So that's the easiest way to solve it. If you have none of this experience at all, is find someone that will get you there. The other one would be like there's often budget approvals, like anything over 100,000 might need to go up to a VP. And so maybe you solve for nine, you know, 95 K because then you can go in at the director level and you don't need to get up to a VP at large companies. The further up you need to go, the less likely you're going to go put in the ask. And so then whether it's asking your champion these questions like how do we get it done? What is the thresholds? Because maybe you're willing to give a little bit on price to just to make sure it gets done. But then there's also like big budgeting cycles. And so annual planning is often in the fall. And if you have a large piece of software purchasing it, if it's a large budget, you need to actually likely get approved in the fall in the budget, or you need to be replacing someone else's budget. And so if you're like now in the air, things have shifted a little bit. And like budgets have gone out the window and everything's moving around. But traditionally it was educating them on why they need some incremental piece of software that was out of budget. In the middle of a budget cycle is incredibly hard to do. And so I think these are the things that, you know, and I come from finance. I was part of the budgeting cycle. I was setting the budgets, um, that I like, painfully learned on the other side. And so now when we go back, the campfire is typically a budget replacement. So we're, clean. They're on like a clean swap on like a one for one. But sometimes we are incremental and there's there's learnings there.
20:28Julian Weisser: I think there's something really interesting about sort of these these thresholds for budgets. There's this older founder that I know who sells to governments. And one thing that he's gotten really good at is understanding what it takes to get in the door. So you could just be just under the threshold. That creates a lot more sort of scrutiny or a lot more friction. But then oftentimes the renewal process is actually a much smoother, even if the renewal is at a higher rate. So I'm curious, um, you know, how you actually sort of suss that out, like in your experience in your field, how do you suss that out when you're trying to find out what is that actual threshold? Is it through a champion? Is it through um, through just actually having a like a sort of a blunt conversation of it? What have you what have you learned over the years?
21:12John Glasgow: Yeah. Government. I think there's a little bit of a cheat code, if I recall, because they have to like publicly share like RFPs and like criteria. And even I think a lot of the salaries are online. So just just because that level of transparency similar with nonprofits, there's a lot of like they publish a lot of data online. So I think like if you're not using that, particularly with Claude, you can ask Claude to go through these databases and have it answer questions for you. On the private sector side, I do think it still comes down to finding the champion, because enterprises are not homogenous and you might need to like. But I think the one thing to be very careful of is if you are cross department or cross function or cross personnel, anything that was ever cross personnel in a large organization, which is like you sell to engineering and you sell to like a product leader, but they have a separate PNL and then who owns who's gonna because then you get into they almost operate like independent organizations And then getting them to like share the budget or one wants more than the other. They're always going to say like, well, you want this more than me. Why don't you take the whole number if you want it that bad, and then you get stuck and then the deal breaks. So narrowing stakeholders as narrow as possible, even across continents or across geos, they'll have a different PNL. They'll have the Europe engineering team, and the American engineering team is often rolling up to a separate PNL, a separate leader. And so you want to avoid all of that. So start super narrow to your point about staying below thresholds, and then build that champion to guide you through. And, um, and then really just lining up those, those budget cycles. But you honestly also need like the stars to align. You need a little bit of luck. You know, if somebody leaves then the whole, you know, your nine month, uh, I was working on a deal for nine months and it fell apart because somebody left and they was over. And so stuff like that happens too. So then like compressing the deal cycle can be incredibly valuable to increasing win rates.
23:21Julian Weisser: You have to know when the deal where you are in the dual cycle and where you are in their budget cycle. Because if you're trying to compress it, but it doesn't fit with their window, might not work. Yes. There's also something really interesting you said about, like who actually owns the budget or who, you know, which organization if they're going to be splitting it. Um, I've seen some companies in the past where they're sort of the exploration phase. They get to a point where they have a prototype that's being used sort of for free inside of a company, and then they find out that, oh, they love the product, but actually it's the it's customer success team that's using it. But the sales team controls the budget. And they just realize this isn't actually a really good thing for them to actually be building, because it's going to be really hard to sell into, into the company if it's not actually being used by the people who have the actual, like, checkbook. Um, I'd be really curious to hear a little bit about kind of what made you realize that it was the time personally or, and or business wise to go and start campfire because, um, 15 years, like, I imagine you could have, you could have gone a little bit less or you could have gone much longer, you know, working in this, in these incredible companies and doing all this great work and, and learning more about the industry. What was the thing that ultimately got you to say that was the right time for you to start a company?
24:40John Glasgow: Yeah, I went from a very large organization in Adobe, and then I went to 100 employee series C company, and I found that I really enjoyed it a lot more. And I kind of like really missed like an it's like agency and ownership and accountability. And you feel like the harder you work like, you know, it was a 90 employee company, like I was more than 1% of the company. And so my ability to have like impact, you know, more than 1% output. So the harder I worked, it was like directly you could see it, like directly see it into the business where like, yes, a large company there is that. But maybe, maybe one fraction of a of a percent. Um, and so I think I really enjoyed that. And it brought me back to like, gosh, you know, like, how small do I want to go? The old being a founder, particularly a solo founder, is the ultimate bet on yourself. It's literally like, I believe I can do something when the expected value is zero. I can like take something here and go bet on myself. And instead of just over 1% of the organization or 100% organization and do something, um, and, and really just build something meaningful. And so I think that was a moment for me of like, gosh, maybe I'll just go back all the way to the beginning. And it came out of, um, so I started to kind of have the entrepreneurial bug, but then it came out of like really feeling the pain of the product of this category. And I would get. So I'm like deeply passionate about my work and I just get like so, like so frustrated with the software and, and with the, the companies, these legacy ERPs that I would just come home and just like, you know, tell, uh, tell my wife like, man, this category is like, really broken. It's like really painful. And so I started to think of like, man, this is kind of crazy, but, um, maybe I'll think about starting my own. And so I applied to, to Y Combinator of like, here's this, like deep pain and frustration I have and I think I can solve it. And here's why. Um, and the timing was literally terrible. Um, my first daughter was two weeks old, um, and got into a Y Combinator with a two week old. And I talked to my wife and I'm like, you know, I was working at a big company at the time because we we, the Hunter employee company, got acquired by a big company. So we went from like Adobe Big to series C, where I really enjoyed. And we got acquired by big a public company build out. Com and so I was like back in the big company, I was like, maybe I go all the way back to to founder and here's some like Deep Pain and Y Combinator. It was like ready to kind of kick things off, you know with their 500 K in funding. And so that was the genesis of campfire.
27:33Julian Weisser: That's super cool. And at some point around that time you had a co-founder for a campfire. Briefly. So can you share a little bit about what that was like, how you decided to work with somebody at that time? And then we could talk a little bit about that, and then we can of course discuss sort of what happened since.
27:48John Glasgow: Yeah. So I'm non-technical just on the finance, you know, hence the commentary around like finance background. And so the technical co-founder and so we were building together and this is summer of 2023. And so obviously, you know vibe coatings come a long way. Um but I think yeah, it was definitely brief. And it was an acknowledgment that like the the passion for this category was mine and like the pain was mine. And so, you know, ended up going solo, uh, quite quickly and was really just like, gosh, I'm solo. What do I do now? And for the solo founders out there, I mean, just huge shout out because pre product market fit, you're wandering in the wilderness. And I would come home and my wife would just be like like physically picking me up off the floor. Um because you don't you don't know like you're running as fast as you can in the wilderness and you don't even know if you're running the right direction. And that's like the pre pre product market fit. And I had such high conviction in this idea. But it was probably a year and a half before it was. Well it was two full years before we found product market fit. And so there was a lot of like investors were saying, like, hey, are you sure this is a good idea? Or like, why do you think about something new? And like, everyone in my wife's batch had either taken off or pivoted, but me, I was the only one I hadn't taken off. I was still working on the same idea. And, you know, I think it was like if I did not have this deep pain, I think back to the shopping one, like maybe I would have continued on as poor as I was, maybe I would have continued on if I really felt this pain in a deep, passionate way for 15 years, maybe I would have kind of continued on and built a Pinterest. But ultimately this was my ability to just power through and have that level of conviction that carried me through this running in the wilderness, nowhere to go. But ultimately, like customers just started to respond. And then it kind of found the trail in the wilderness, and then it just found a direction to run.
29:56Julian Weisser: Yeah, I think I think Ben Silverman, uh, the lure of that is he literally had like, physical pin boards. Like when he was growing up, he was like obsessed with, like actually pinning things to physical boards and like, there was a real there was a real connection to it. And what you're doing now is obviously there's a real connection to the 15 years of experience you had after your first company. Just to really quickly, though, talk about the the co-founder situation with with campfire, even though it was brief, I think it's really instructional because a lot of people have a similar situation. They start off, they think that they need a co-founder, they end up working with someone, and sometimes it's the co-founder. Situation just doesn't work out. Like there's actual acrimony sometimes, you know, it's just it's just not a fit or the timing is not right. Um, you know, I'm really curious. This was like a nights and weekend sort of thing you're working on is you hadn't left your job. You were still employed, I believe, when you when you were working on this idea before you got funding for it. So what was sort of what was that like? How did you decide to start working on somebody and start toying around with the ideas? I think there are a lot of people. Maybe they're not. If they're listening to this, maybe they're not thinking about trying to find a technical co-founder, but they are maybe working at a job and thinking about, hey, should I be like, tooling around with like, an idea that I'm really passionate about? So what was that like? What was going on then?
31:13John Glasgow: Yeah, well, with Y Combinator, I had applied with just an idea. So I think and this was before the vibe coding. So I think it was literally like, here's this idea, here's why I think it can be solved now, and here's why I think I'm the person to do it. And they're like, you got in. So we really started writing code like after it all started. And, you know, I left and Y Combinator was like, okay, it starts tomorrow. So you kind of quit and you quickly get started on on the company and incorporating and writing code. I think if I start the company today, I as a non-technical or as a technical, you know, write the full app and really just like get a lot of feedback. And I think maybe with the shopping app, we asked a lot of friends for feedback. And I think everybody says, this is cool and I. Yes, of course I would use it. And then like they would not use it. And so I think the like I was able to talk to some peers in finance, but the biggest unlock was just cold outbound to people that I did not know at all. And if they take the meeting, like I vividly remember week one, I'd quit and I did a cold app onto this guy and I'm like, hey, like if you're open to like giving me some feedback on this idea, I was just showing them like Excel files at the time because again, this was before like engineering is now. And he's like, I'm happy to. He was working in corporate finance. He's like, I'm happy to meet with you for an hour a week and just help you, give you feedback. He asked for nothing in exchange. He's like, this pain is so acute for me that I'm willing to give my, like, incredibly valuable time to just help you solve this pain that I have. And just like people that you don't know at all. Being willing to just, like, commit. Like, I didn't even ask. He proactively offered this to me. It was like, wow, I think there's something special here. And so I spent the whole summer meeting with the guy weekly, and he just every time, every week we showed him a more advanced version. He'd give some feedback and and then ended up being a paying customer. And so I think the, you know, AI called outbound or just doing some LinkedIn outbound, um, I think you if your employee you do want to be careful about IP ownership. Like commentary is very critical of like, hey, let's have a clean break because then if you do take off, there's like unclear IP. So I would the vibe coding era, given everyone can have a side hustle, be very careful about employment and IP ownership on your existing employment contract. But ultimately, if you're going to raise money from institutional capital, they're going to expect you to be full time most of the time, or they will at least like the check is contingent on you leaving. So then incorporate and then kind of like have a clean break on the on the IP and writing the code. But you can ideate, you can do some cold just, you know, outbound. You can hear from some folks on if there's some value here. And then if you fill a pull or you just it's a pain you personally feel. There's no pull at all. Just go for it.
34:20Julian Weisser: So it's it's 2023. You find a co-founder, you apply with an idea, you get in to YC, you start working on the actual like product, building it out. You realize that maybe it's not working for the co-founders so that that ends up sort of being you end up being sold those sort of after after like going all then, uh, after quitting your job and then you start to have this outbound where you're messaging people and they're resonating with it. And, you know, a great sign. This one guy in particular says, this is such a big problem for me. I'm going to spend a lot of time with you on it. Um, that's a really good sign. Do you? We talked earlier about right to. When do you think that part of the reason that you got the reception that you did from that guy was because of, you know, your background and because of your ability to articulate because you had the background that you did. Like, I'm curious how you think Right to Win sort of fits in with, uh, early customer conversations or even pre product, sort of like prospective customer conversations.
35:24John Glasgow: Yeah, it was definitely both. So when I'm talking to them, it was always like, hey, I'm a fellow finance peer and I have this pain. If you have a two like let's chat. And they're always like yes, like, of course I have this pain. And we'd hop on a call and we would talk about all of the whether it's board reporting or whether it's like, you know, for a fundraise or just like monthly, you know, RR reporting, I was able to just go deep to their level and they're like, eh, this guy gets it. And B he's lived the pain I have and see he's just like passionate about solving it. Because many of our early customers were like, look, your product is so rudimentary, it's not really usable, but it just seems like you're going to figure it out. You deeply understand the problem, you know, and and some of that was just going and meeting them in person. But a lot of it was just like, I am you. And and I felt the pain with you. And I've been a customer of these tools just like you. So I lean into that very hard in the early days, because the product was not where it needed to be for someone. Not like arm's length to be like, oh my God, this is way better. And I think the other one was a lot of the building was just for myself, so I knew exactly where the like the three biggest pain points were and just narrowly focused on those. And then I guess the last thing I'll add is that comment I made about conviction. When everyone's telling you to move on, when even your investors are telling you to rethink this decision when the whole YC batch is kind of moved on from their original idea, but you and otherwise they've all taken off. That was really like that. Edge was like, no, I do need to keep going here, which is the last thing I'll call out.
37:01Julian Weisser: Do you think that a lot of people who end up moving on from their ideas, do you think that most of them are is the result of they hadn't actually found something that was really sort of their right to win and that they had like a really meaningful insight. And if I, you know, prior to working on solo founders, I co-founded this thing called On Deck and ODF, and we helped so many people start companies and find co-founders. And it always felt like if there was this process of kind of going from idea to idea to idea, eventually the idea that worked out of the maybe two, three, four, sometimes 5 or 6 ideas. It was always like this process of kind of actually figuring out who you are as a person. Um, and what actually you have is an insight that's unique to you or gives you an advantage. Um, and it feels like almost all all of the pivots, uh, could have been sort of short circuited or sort of like, gotten to faster. Had that sort of been the thing that people were maybe a little bit more discerning about?
38:02John Glasgow: Yeah. One fascinating insight I had for my batch was a lot of people tried to start companies entirely unrelated to what they do. Like in a prior life or even their like degree, and then ended up landing on the idea that was related to what they did. And so I think, exactly as you're saying, they like, they almost run away from their own, but then they like circle full back. And then they had some unique insight that they ended up discovering was actually, like incredibly valuable, that they can be the unique person to go solve that problem. And so I think exactly as you're describing, again, no unique shopping insight for me. Um, someone maybe knows something about shopping and could still go build a Pinterest. I'm not saying you can't. But for me, there was incredible value, as I noted by having that.
38:48Julian Weisser: It also seems like there's some there's some aspect of, um, you know, the more experience you have, like in life or working on something consistently, you have an opportunity to maybe gain an edge. I think about, um, there are obviously some incredible founders who kind of are outsiders to an industry, and they break and they learn as they go. And that's awesome. And I think that we'll continue to see more of that. But it also seems like there are so many great companies that are started by people who did spend, you know, ten, 15, 20 years in an industry before realizing that it was time to go and start maybe the first or second company that was really derived from this insight that they had. Do you have any thoughts about, you know, about companies that are sort of based off of maybe more than just like, uh, limited, limited sort of early insights, maybe from an internship or, you know, being at a job for a year or two. I'm curious, like what you've learned, what you've seen of other people who've maybe been like. You know, in an industry for a while before actually going and building their own company.
39:49John Glasgow: Yeah. In terms of like, folks that knew nothing about a category, is that more of. Yeah, I.
39:54Julian Weisser: Mean, more more like you spent 15 years and and you not only. The proof is in the fact that you message people. They resonated super strongly with what you were saying. Um, you had the ability to, to know what a problem was that they would actually light up about and they'd say, does this, you know, I experienced this problem. Does it? Is it something that you experience? And a lot of them, it seemed like when you reached out they said yes. Um, I'm just curious what you, what you've seen from other founder friends doesn't need to be solo founders, of course. Um, who who maybe had longer experience in an industry that drove them to, you know, actually end up finding something similar to what you're doing with campfire, where they have that pretty early resonance, you know, before they they don't need to necessarily pivot to, you know, 3 or 4 different things before finding it.
40:42John Glasgow: Yeah. Um, I'm trying to think of a specific example, because there was a lot of pivoting, uh, amongst my founder friends, but there were some that, like, just went straight after a single thing, and it was similar to me. It was like, hey, I deeply felt this pain. And I think that's maybe the one. The one call it I'll Give, which was like they had they lived it or they felt it before, like maybe they had built an internal app at a larger company that solved this one problem. And now they're going to go like solve it for the masses because they're able to do it in a unique or special way for another organization. And outside. How do I like commercialize this almost in like an academic kind of way, where like IP gets developed within an organization, you can like go ahead and commercialize. Yeah, it's the only thing that comes to mind. I think though, that like, um, there are some founders that could probably go into any category and be successful. So I, you know, I think to be a founder, you need a little you need to be a little bit crazy. And I always tell because founders will call me and say, should I pivot? And, you know, I'll take calls in the car. Um, and
41:49John Glasgow: I tell them, like, don't listen to, oh, I didn't get funding or oh, someone told me it was a bad idea, like, because you have to be crazy to be a founder. Don't listen to anybody but customers. And and if the you know, and if you haven't found the customer attraction yet, why should you keep going? And that's something only you can answer for yourself, particularly as a solo founder. So don't look for external validation because it often will never come. I mean, I love the Brian Chesky story where he was just like maniacally focused on, you know, Airbnb. And it was just like a deep passion of his. And every investor was saying, no, he was funding it with like, cereal boxes he was selling. And and I think because he spoke to our batch and shared the story and it was like, wow, you know, this is this is a level of conviction it takes to be a founder, because even if you are pivoting or not pivoting, um, it is a roller coaster. And maybe, you know, I talk to founders that say we hit 100 million ARR and we had to we had to like, rebuild the business at 100 million or at a billion, and particularly in the AI era. So there's always going to be these like ups and downs, premium pre product market fit, post product market fit. Um that to keep going you need to like um you need to just like find the inner um the inner um you the, the one other big insight was Y Combinator uh, told us in the last day, the number one reason you all will, um, if anyone here fails, it's not because you run out of money. It's because you. Burnout. Burnout? Some number one reason for shutting down. And so don't burn out. And so taking care of yourself. But also it's easy to burn out when you are running in the wilderness and you don't know where to go because it's just exhausting of like, you, you're kind of back where you started and you see the same tree that that's a cause for burnout. So I think being able to persevere and convict through avoiding the burnout and celebrating the wins is something that I've always done.
43:55Julian Weisser: One of the one of the things we noticed over, like the last eight years of helping people sort of find co-founders and then go solo, um, is that people run out of hope before they run out of money, typically. Exactly. Um, and oftentimes the reason for that is usually like one of the co-founders runs out of hope faster than the other. And they, you know, in the best of times, found co-founders, pushed each other up and sort of pull each other up. Um, the worst of times, they pull each other down. Um, it creates like a really tough cycle to get out of. And then ultimately, that's one of the main reasons that companies fail. You know, I think it's like 66% of companies fail because of co-founder breakups. Um, being a solo founder, you don't have that risk of. Of the company dying because of co-founder implosion. But there's different ways to run out of hope. Um, and one thing that, um, that's really interesting about your story is, you know, you you had a brother who you started a company with. Um, you're really close still, obviously, you're both founders at a at a relatively similar stage. Um, he's been somebody who you spend a lot of time with and get a lot of feedback from, um, and support from and, and I think also, uh, your wife, you've you said recently that you describe her as almost like a co-founder, even though she's not full time at the company. So maybe you could share a little bit about both of those two relationships and what they mean to you, uh, from the business perspective and the personal, too. Um, and then we could talk also about sort of like broader how you think about support as a solo founder.
45:28John Glasgow: Yeah. Well, the number one piece of founder advice that I hear from from successful founders is for a mentor. Find another founder that's like just ahead of you. And I was fortunate that my brother's company is a few years older than campfire, so I kind of had that perfect built in described like perfect mentor for me as a founder. And it's likely because they just solved all the problems you're going through now. And then, of course, pay it forward and help someone else. And so that's why I try and help folks, um, you know, that are just behind me in their journey and help them skip some mistakes. And so he continues to be incredibly valuable, whether it was our our series A, I mean, we were talking every single day for long periods of time through the series A fundraise. The seed round was like very simple and structured. The the series A, there's just a lot of moving pieces on and it's a different you know, it was our first priced round. And so I think um, a lot of help there. Um obviously having two daughters and coming home to to my wife every night. Um, getting a lot of, like, talking about burnout, like they are what kind of refills me and like, if there is, like, a tough day, a tough week, like coming home. I think just finding your happy place as a founder is incredibly important. And like, no phone, no screen and like at least 15 minutes a day of just like, what makes you happy, what fills you up, that's like, not work related. Um, and that's just for your mental health. And that goes, you know, that I think just all people in the workplace, but particularly as a founder, as a solo founder, because to your point, you're not going to get it from a peer at work. You're not going to get it from someone else. I think as a solo founder, you often need to like, bounce ideas off of someone you deeply trust, and they may not have any unique insight at all, but your ability to just, like, articulate it. And almost in a therapy like the best, therapists don't give you any advice, they just kind of ask you questions and you like self help. You just self answer your way to the right answer. I think even just having somebody like a parent or a roommate or a friend or for me, a twin brother and a partner, um, can help you through those incredibly tough times. Um, and also through the really good times. And, um, and so they both have been instrumental in their own ways.
47:51Julian Weisser: You know, there's, um, I think that in a lot of ways there's, uh, sort of a fascination or obsession with, uh, young founders. Um, there's even, like, memes about how founders should be single and they shouldn't be in relationships. Um, I think I think it's really, um, I think it's like, actually, like, pretty destructive, uh, to, like, have these, these ideas that, like, you can't build a company with a family, but could you, could you share a little bit more about kind of what you've learned about that, uh, through this process of building a company? I guess, like, if I'm, if I'm getting the sort of the order of operations. Right. Your first company, you weren't married, and you got married into a relationship and got married during the time that you were working in finance. And then, you know, when you were starting this company, you were having your first kids. So could you share a little bit about what you've learned through that and the things that have been great about it, the things that have been maybe challenging if you're open to sharing that as well?
48:45John Glasgow: Yeah. No. Happy to share. I mean, I do get founders asking me and say they have delayed marriage and children to be a founder, and they say, I didn't know it would be feasible on what you're doing. I would say like ruthless prioritization, just like as any time as a founder. But, you know, on weekends I don't play video games or go play tennis or anything. It's like there's campfire and there's family. And again, like family kind of is my my hobby or my, my, my time away from the company for lack of a better term there. And so, um, you just need to, like, focus. I work incredibly long hours on campfire. Um, you know, I try and see the kids either in the morning or a minimum at night. I could call it, like, once a day at a minimum. Um, and then it just comes down to how do I like. So when the kids go for a nap, I'll go work when they go to bed. You know, even on a Saturday night, they go to bed around seven. You know, I often kind of start working again. I work before they get up at seven. So it's really like, how do you find time to get the work done? Um, is going to be important particularly, you know, if you're, um, maybe it's not. It could be like a side job to pay for your. I mean, there's other obligations beyond family you may have. And so just ruthless prioritization is my, um, is my big area of feedback. The other one is to your point, someone published a chart that said the average age of founders has been plummeting in the last like five years. And they showed a chart of like, you know, series B founders. And I was like, off the page. I was like, yeah, I started comparing like 36 and the thing went up to 35. And um, and so, yeah, like old non-technical founder, um, you know, solo can't, you know, I particularly pre AI coding couldn't write a line of code. It's like the anti-pattern for like the the common founder today. But don't, don't feel you need to put life off because I think that does contribute to burnout. You know I think like oh I need to you know, like a like athletes like you know LeBron James got, you know, married young and he's still like they you have to find a way to prioritize life. And you can still be world class at something. But it does come down to prioritization.
51:06Julian Weisser: The other thing, um, you know, about sort of having a partner who doesn't work on the company full time or what have you is, is that they are sometimes people who are building companies. They want to kind of try and keep some separation between home and away. I'm curious, you've said that, you know, your wife is, like, incredibly instrumental in helping you think through decisions. Um, how have you navigated that? Like, how has that been for you? Obviously, it's a personal it's a personal decision between two people. But I'm curious kind of what you've learned from that, sort of your philosophy or the philosophy that you do have around sort of collaborating together and your life, but also in the business?
51:46John Glasgow: Yeah. I think someone that, to your point, is removed from the company, but is like a deeply trusted person for you is incredibly valuable. And that could be like that founder just ahead of you that you deeply trust. And you know, I have both, as I noted. But when I go to her, it'd be like, here is just something that like, I'm really wrestling with. And it could even be to handle a situation in the workplace or an HR item. Um, and her just having a different perspective as a woman as well. Um, I think there's and she, she came more of the technical path. She was most recently within an engineering organization. And so when I work with engineers, um, you know, I just going to her and like, as a non engineer, I think it can, you know, for founders be hard to work with engineers because you're like, why isn't this done yet? And engineers are like, oh my God, this person is so annoying. They've never written code and it's obvious. And so I think even just like going to her and like, how do I work with engineers in a thoughtful way. Um, and, and things like that. You can, you can really, you can really lean on them for but also it's just like I had a tough day and, and I think, well, you know, this individual and me and my, for me and my wife like helping me kind of just think, zoom out, think through all the goodness of the day. I mean, even last night, she was like, you brought up a lot of negative things from the day, but I she she has access to my calendar. She's like I saw a lot of big wins on the calendar too. And so I think even, um, that was that was helpful. I think that was like the wind in the sails that I needed that day. Um, because again, burnout is real. And so having someone to help you through those, those burnout moments is critical.
53:33Julian Weisser: So you, you with campfire, you know, you pretty quickly ended up becoming a solo founder, um, when you were thinking about bringing on teammates, what's the philosophy that you have? What's the thing that you that you've learned? Um, maybe if you do things differently, sort of now, given kind of what you've experienced, uh, because I think that ultimately, if you're a solo founder, especially if you don't have the technical background, you could build the product necessarily all on your own. Um, it changes a lot of the dynamics around early team. Yes.
54:04John Glasgow: Yeah. So first hire was definitely engineering. And so when I did recruit engineers, I really focused for folks that that had like a founder mindset. And so maybe they were like working on a startup idea. Or maybe they had been a founder. In my case, the first two engineers were both of those. Uh, one was a exited founder that was then kind of at the, uh, organization. And then the other one was like working on ideas, but both of them, one of them deeply cared about the category, the ERP category. The other one was like just looking for like a huge problem to go tackle something that was just like gnarly. That was kind of like unsexy. For their second company, they wanted to be super early at one. One thing that was not obvious to me at the time, a lot of engineers want to join after product market fit. Otherwise they're like, I might as well just go be a founder. Yeah, I.
54:56Julian Weisser: Think that's especially true.
54:58John Glasgow: Now. Yeah, yeah. And so then it's like, why join you as you're offering neither. And so I think it was really just selling almost like it's, you know, just classic sales pitch. You just really got to sell hard, almost like an investor On why you think that you're on to something special. You're the you're the one to bet on. And that's a big part of those early hires is selling them super, super hard. And so I had our we had some seed investors. So seed investors would kind of here's why we think this is, you know, the team which was just me at the time to bet on, um, here's why the problems unique if they didn't fully believe in the problem. And as a solo founder lead on Lean on Your Community, maybe you have a mentor or a teacher, or maybe you have a, um, you know, someone that you've already sold to your first customer, have them talked to this prospective employee and say why they bought the software and help you sell and win.
55:52Julian Weisser: That's cool. You know, it's it's interesting how infrequently, um, founders, especially first time founders, think to have their investors help close hires. Um, they ask for referrals often. Um, and some investors can be really good at that. But I think that where investors really can shine is actually saying, hey, I put a lot of money and, you know, my reputation on investing in this company. Here's why I think it's a really good one. Here's here's why you should be excited about it, too. I think that that's under under undervalued and underutilized.
56:24John Glasgow: Yeah. As a solo found I mean we would I remember we did a team. We had a big company that was hesitant to buy because we were so small and they wanted to see a team slide. And I was like, every we had a design contractor, we had a marketing contractor. I was putting like I had all of our advisors, which is like our investors. And someone I gave equity was on there. You've really got a lien on your call it your tribe as a solo founder and look bigger, but also tap them when they can be helpful. You just could not be afraid to tap your your tribe to be successful.
56:58Julian Weisser: I mean, this has been awesome. We've covered a lot of ground. You usually try and close this out by asking two kind of customary questions. The first one is, why you shouldn't be a solo founder of the Barricades for solo founding. And then we'll discuss that for a couple of minutes, and then we'll we'll pivot it and we'll talk about the case for solo founding. But what's the bear case for? For being a solo founder if you if you have one.
57:22John Glasgow: Yeah. I would say it's the odds of success as a founder are so low. I feel you need every single tailwind you can get because the expected value is zero. Being to building something of a value, a meaningful business. And so a co-founder can just increase the odds of punching through of the unique insight of that big customer win. Um, and someone to to bounce ideas off of when you're running around in the wilderness and like, we have no idea where to go. Um, that would be to me just in hindsight here. Um, the biggest reasons is it's, uh, it is incredibly lonely.
58:04Julian Weisser: Yeah, Yeah. It's, um, it's really interesting because, um, I think that, like, in many ways, it is incredibly ideal to have a co-founder, if this co-founder, um, really helps you, like and complements you, um, you're aligned on sort of what everybody wants, and you have a really good sense of what your values are and all of these things. And, you know, there are companies where the co-founders met through things that we've worked on with ODF seven years ago. They've been working on a company for seven years. They didn't know each other previously. It's amazing. Right? And they have these incredible relationship. Um, but I think that, you know, the big risk is that for all of those great, uh, scenarios and things you're describing, the biggest risk is just that, you know, oftentimes people don't end up having that happen, and it ends up being the thing that kind of causes the company to go poorly. Um, so it's this really interesting dynamic where I do I do agree with you that if you have if you have that if you have an obvious person to build a company with or you find somebody who just you just really realize, like, this is this is right. I would say like, I'm you know, I'm not saying that people shouldn't shouldn't work with that person. I just think that one, they shouldn't let that be the gate from getting started. If they have an insight, they have something in your case, like campfire. Um, it would have been a shame had you not found that person and then not ended up sort of like continuing on because you had such a strong insight into what it is that you care about, what it is that you see in the world that that needs fixing. Um, and I think that that's the biggest issue right now is that there's still so many people who look at the world and they see something that they have an insight in, and yet they don't pursue it because they think that they need to have a co-founder, and they think that there's this sort of gate for them. And I think that hopefully what we're doing isn't discouraging people from finding having great co-founders, but is encouraging people to not let a co-founder be a thing that prevents them from actually going and making something that's important.
60:00John Glasgow: I completely agree.
60:02Julian Weisser: So let's let's talk about the case for solo founding. What's the case in your opinion for solo founding from your experience doing it?
60:09John Glasgow: I mean, it is the ultimate bet on yourself. And so if you're going to be a founder, you got to believe in yourself. And so this is the biggest way to do it. But I think the biggest realization I had when I went solo was incredible clarity of vision and what to do next. And there is no like there's no tension at all unless it's within yourself. And so I think like when you're running in the wilderness and there's a lot of frustration on pre pre PMF, it's very frustrating part of the journey. I mean people raise hordes and hordes of money and still can't find PMF. Like money can't solve PMF like there's just nothing you can do. And so when you have a solo founder, it's like one CEO of Just incredible. Because even if it's like a CEO CTO relationship, ultimately there's still kind of like two likely equal people as a co-founder when you're solo. I had so, so much clarity of what to do next and where to go. And even when it was like, you know, we were really not finding PMF and a co-founder often would have said, hey, let's move on, because the idea ultimately was mine. And so I was the one that had this pain and conviction, the ability to just power through that. But also we did a lot of micro pivoting. Like brought in some engineers where like pivoting within like size of company a little bit. The same idea about like size of company or like, you know, certain areas a little bit. And my ability to just like rapidly get through, like it tightened the path to product market fit a lot because I was able to just like run incredibly tight experiments, incredible velocity on decision making because you don't need to like, you think about why large companies move so slow as the sheer amount of cohesion and coordination required to do anything at all at a small level. Co-founders have that too. You got to pitch them why we're going to do X or what you're going to. Should we go to the conference to try and find a customer? You might have a debate with your co-founder on. Is that a good use of time when you're a solo founder? You know, when when people joined the company, it was like, John is the clear leader here. His vision. We are we are executing on and and but also like I lived and died by the wins and losses too. And so then it kind of goes back to your ability to ruthlessly focus in specific ways and pivot in ways, because you need to talk to anybody about it, convince anybody, any of it. Um, and with the ability to write code with AI now, I think anybody can be a solo founder, you know, arguably more than any time in history, particularly if you're non-technical. I think it was always you should have a co-founder if you're non-technical was always the pitch to people like me. Now, I don't think that's true.
63:00Julian Weisser: Maybe just the last, the last thing because it just begs the question. Like, say, can you say more about the non-technical builder who has an Insight solo founding with AI now? Like what, what what, what have you? What have you learned as sort of a non-technical solo founder and
63:19Julian Weisser: about sort of like getting started and we can talk about the AI component of it. But I think there really is this aspect of distribution is so important now. Understanding customers is so important. Software isn't commoditized by any means, but, um, it is not necessarily as big of A as it once was. Like having a technical co-founder isn't as big of a gate as it once was. So can you share a little bit more about sort of the non-technical? Uh, very like insightful, industry insightful founder going solo.
63:52John Glasgow: When there's a lot of work on prototyping and iterating an idea. There's a lot of code being thrown away, and there's there's a lot of back and forth of like, like I would be scoping in a spreadsheet for the engineer and then they would like look at the spreadsheet and then they would like and I'm like, no, like that's not exactly what I wanted. Um, and you could argue there's like more thoughtful ways to do that. But as a finance person, that was kind of my that was my figma. Now, like even today, I will ship fully functional prototypes and clicks and actually connected to our back end in GitHub. Um, and I still have not learned engineering at all, but my ability to then go to engineering. Now we have, you know, north of 100 employees, my ability to just share, like clear visions and clickable prototypes that are fully functional connected, our back end is very real. I think engineering like you absolutely need engineers at scale, but pre product market fit when scalability is not important when like, you know, SOC two is probably not a thing for you yet for the first customer, maybe it is, but many times it's not. Um, and just the iterating of, you know, my comment about meeting weekly with somebody, your ability to just like, chat with it and meet with them again next week. And even if it's like daily or hourly meetings with them, you could iterate at that level of speed and incredible, uh, clarity of vision, because it's you and essentially the engineer fuzed together. You're just chatting with it and it's yes, maybe it's not perfect on the first one, but like, you can just rapidly prototype, but I think the other one is you can kind of come up with stuff that's a little crazy, like, I'll go to engineering now and like, here's kind of a crazy idea and it's fully functional and I've already run it by ten customers that, you know. Otherwise, like, would I go to them of like, hey, can you spend the next two weeks shipping this kind of wild idea? You'd probably just say like, that's dumb. That doesn't make sense to go spend two weeks on it. But when it's me, just like one shotting something on a on a prompt. Um, so the the bar is so low that your ability to prototype or come up with wild ideas like I in 2023, we would work on one idea at a time, and I think that still makes sense. But with you can run ten prompts concurrently. Building tools like you could probably parallel multiple ideas at a time now in ways you couldn't. You know, when I was in a pre product market fit. And so your ability to just iterate almost at scale, I think is unprecedented now and get paying customers, um, with no engineers. Now, once you need scalable code, you do need engineers. And I think there's a lot of we have you know, we're rapidly engineering is the fastest growing team at campfire. So you obviously need engineers. But I think that that very early days, the solo founder, it's incredibly pure and vision and just vibing and showing and finding those early customers. There's no better way to do it than just solo.
66:52Julian Weisser: Cool. This has been amazing. Thank you so much for being a part of this.
66:54John Glasgow: Thank you so much for having me.
66:56If you enjoyed this conversation, we would love it. If you can share solo founders with everyone you know, particularly people who are considering starting companies solo or who are already doing it. You know, the entire goal of what we do is to normalize solo founder and encourage more people to solo founded, instead of to end up with co-founders of convenience, if you'd like. And we'd really appreciate it. You can go. Leave a review on Apple. You can go give us a thumbs up. You can subscribe on the YouTube channel. Anything helps. And of course, if you are starting a company or considering starting a company, you should go look at the Solo Founders Program. We work together with you in San Francisco alongside a bunch of other solo founders. The idea is it's much better to be solo together than to be solo alone. I'll spend a lot of time helping you, and we also invest $100,000 in your company. So if you're excited to learn more about that, go check out Solo Founders Program.


