The $4,000 Prototype That Launched a Multi-Million Dollar Company | #24 Starting Up Podcast

Speaker A: Starting a business is hard. Betting on yourself is hard. Do you know what else is hard? Working for someone else and jobs that you hate for incremental wages while hanging on to the hope that by age 65 you're going to be able to retire and do all the things that you wanted to do while you spend the best years of your life making someone else rich. That's hard. Welcome to Starting up the podcast where we're choosing the hard that gets us where we want to go faster so we can live life on on our terms. I'm your host Jay Sensi. I am a non technical founder who bootstrapped the software company from idea to multi million dollar ARR, sold it to private equity in an eight figure exit and retired at 40. All without a coding background, without outside capital, and without leaving my day job. Each episode I'm going to be sharing the real story behind how I did it. The wins, the mistakes, and the playbook that you can use to start, grow and sell a company of your own. This is starting up. Let's get into it. 33 minutes. That's how long it took. Uh, between the moment a vendor told me he couldn't take my project and the moment an email arrived in my inbox that changed the entire trajectory of my company. You might think you know how vendor shopping goes. You send out your spec, you get some quotes, and you pick one nice and linear. But sometimes fate throws you a curveball. Sometimes the vendor that you weren't even looking for turns out to be the one who changes everything. Today on starting up, how an unexpected email, a $4,000 prototype, and a phone call taken from a shopping mall launched a multi million dollar company. Last episode I walked you through the chaos of vendor shopping quotes from $800 to $80,000 big range, roughly a, uh, dozen firms. And none of which really kind of gave me the warm and fuzzies a gut feeling that said keep looking. Today I'm going to tell you what happened when I listened to that gut feeling. Because just when I thought I was going to have to settle for one of the vendors on my shortlist, a totally unexpected avenue came in from left field. One of the vendors I had reached out to early in my search had gone kind of quiet. I done a pre proposal phone call with him. I sent them the spec and then crickets. Several vendors had ghosted me. So, you know, I kind of just assumed that this guy was off the list. And then on January 8, 2013, I received an email from him. He explained that he would not be able to take on the project himself. But he did ask me if he could forward my information and my requirements to a programming company that he worked with. I said sure, why not? What did I have to lose? 33 minutes later exactly, I received an email from that programming company. It was from a guy named Dave who ran a company called Grind Flow Management. They were a web development firm based outside of Washington D.C. dave and I linked up for a phone call. And I remember leaving that call with a good gut feeling, which was something on the contrary of what I had been experiencing up until that point. Something about the conversation was different. Dave seemed to listen different. He asked what I thought were smart questions. He didn't talk to me or make me feel stupid for having a two page spec. He kind of understood where I was coming from and what I was trying to build. And you know, the guy just kind of seemed genuinely interested in helping me get there. But the biggest difference was Dave's proposed approach. You see, every other vendor that I had spoken with was quoting out the full build of a complete software platform. Uh, 20 pages of scope, months of development, some of them five figures at ah, minimum. Other than maybe the $800, uh, lowball offer, all or nothing. But Dave suggested something different. Something that in hindsight was kind of brilliant. You know, Dave, instead of going for the gusto and going all in and incurring a ton of cost, Dave actually proposed a much smaller initial investment to build what he was calling at the time a proof of concept. Kind of like, uh, an alpha prototype. These were again, terms to me at the time, didn't make any sense, didn't really know what they were, but, you know, went along with it. Uh, the concept was it was going to be a pretty kind of bare bones yet functional version of my college roomie. Not the finished product, not something that I could sell to clients, but something real enough that I could show to prospective customers and really gauge their interest and whether this was a viable purchase for them before I would commit then five figures to build the full production ready platform. His proposal, which I actually still have a copy of and uh, look at once in a while, was to deliver a single instance alpha prototype of my college roomie for $4,000. Four grand to take my two page spec and turn it into something that I could actually put in front of people. Of all the vendors I had spoken with, Dave really left me with the best impression. I felt like I was talking to somebody who had my back, who had my best interest in mind. And I also Had a pretty high level of confidence that Dave's team could deliver what I needed to take the project from idea into reality. I actually remember exactly where I was when I got that call. I was living in Orlando at the time. I was in the mall of Millennia in Florida. And I was walking through the mall, phone in hand and nerves firing. Uh, Dave called me, um, and wanted to check in on the proposal, see how things had, uh, had been going, you know, what my decision was going to be if I was. If I was ready to make a decision. And, uh, in that moment, I let Dave know the great news that I had selected Grind Flow to be my development partner. And, and that I would be signing the contract to begin development. We were going to build us some software. Now, I want to pause here, because this moment just. It doesn't get enough attention. I think in startup stories, you know, most people talk about the idea. Uh, most people talk about the funding, the launch, the customers, the growth, the eventual exit if you get there. But most people don't talk enough about the moment that you actually commit. While seemingly, maybe insignificant at the time, you know, this was really a major milestone in my startup journey because it was the first step in actually executing. Prior to signing that development contract. Everything was just an idea in a dream. The spec was just a plan. The market research was just data. The voice of the customer sessions were conversations. None of it was really real yet. But committing to a company to build the prototype, handing over some cash to do that, that was action. And action is what makes the world move. The best founders, in my opinion, are not the ones with the best ideas. I've said this lots of times. If you've watched some of the previous episodes, there are millions and millions of people walking around with awesome ideas right now. Ideas for apps, for platforms, for services, for products, for AI platforms. Brilliant ideas that will never, ever, ever see the light of day. The best founders are the ones who can take that idea and execute on it, because execution is where the magic happens. And execution begins with the commitment. A moment where you say, I'm doing this, and then you back it up with money, time, and your signature. That moment, for me, happened in a shopping mall in Orlando, Florida. And it some, you know, at the time felt like stepping off a cliff. Both terrifying and exhilarating at the same time. So if you're sitting on an idea right now and you're waiting for the perfect moment, you're waiting till everything is lined up and all the risks are mitigated and. And all the questions are answered. I hate to break it to you, but that moment's never coming. At some point you've got to commit, you got to shit and get off the pot. You got to make something happen. You're going to have to sign something, pay something, build something, do something. Because the gap between dreaming and doing is oftentimes just a decision. So make the decision. M I'd like to talk about why Dave's approach was a lot smarter than what the others were proposing. I think Dave saw the long game. I think Dave saw a first time founder who didn't really know much about the software business, didn't know much about the development process, uh, had a little bit of money and uh, instead of the approach that some of the other vendors had taken in terms of, let's see how much of this guy's money we can get and go build everything. You know, they probably had good intentions, but ultimately sales are sales. You're trying to get the, you're trying to get as much money as possible. I think Dave's approach was a bit different in terms of saying, let me see if I can save this guy some money, help him get off the starting line. And if this thing starts to go somewhere, you know, Dave would be positioned properly to then take on the development. And that's kind of what happened, right? Every other vendor wanted to build the whole thing, the complete platform, all the features, production ready. And that's a big investment, right? Both in time and in risk. You know, if I had committed $20,000, $30,000, $40,000 to a full build and the market didn't respond, uh, at that point I would have burned out my entire budget on product and I would have had a product that nobody wanted. Dave's alpha prototype approach kind of de. Risked the process for me. Now, yeah, in 2013, to me, $4,000 was a lot of money. And you know, to a lot of people it still is. But man, I'd rather waste four than 40. And for four grand I got something functional, something real, something that worked, something that wasn't a figma, something, uh, something that I could put on a laptop screen. I could show it to a housing director and say, this is what we built. What do you think? And that to me was a lot more powerful than a PowerPoint or a verbal pitch. It was something people could see, it was something they could click on. It was something they can react to. And what's important about that is that their reactions tell you whether or not you're on the right track before you invest the other $16,000 or $20,000 or $30,000 or whatever it's going to be. You know, uh, I sometimes think about it this way. Sometimes I think about it this way. You know, if I had shown the prototype to say 10 housing professionals and all 10 of them said this is cool, but I would never pay for it, maybe I would have lost out on four grand instead of 20 or 30 or more. That's a bad day, but not a catastrophe. But if those 10 professionals got excited, they started asking, when would it be ready, how much would it cost, whether they could be the first one to use it, then I'd have some real validation, uh, not just verbal engagement from a phone call, actually real tangible. I can see this and I want it validation. And that's exactly what the prototype gave me. For $4,000, I was given a way to test my assumptions with a real product instead of just a pitch deck. Now I think it's also fair to point out, uh, something important about Dave and grindflow. Eventually I did outgrow them. As Campus Kaizen scaled and the products became more complex, I did need development partners with larger teams, uh, more specialized capabilities. And that's natural. I think it's a good problem to have, you know, so I think it's important to remember that if you're going to outsource your development and you're going to pick a vendor and you've got a vendor that, you know, gives you the good gut feeling, just understand that you may not finish with that same vendor. Right. I think this goes for a lot of partners that you might work with in your, in your business. Not every partner that you start with is going to be the partner that you finish with. But Dave got me started. He took my sometimes laughable two page spec and turned it into something real. And more than that, he did it in a way that protected me from over committing too much money early. And that's something I'll always be grateful for. The relationship mattered as much as the technical capability. Dave and his team cared about my success, not just his invoice. That's the kind of partner that you want in the early days. So before I wrap up the vendor shopping arc, uh, I want to share my broader philosophy on outsourcing development. Because it's a question that a lot of non technical founders I think wrestle with. You know, what I've seen both in personal experience and in talking to other founders or advising other startup founders, is that outsourcing your development initially is often the easiest and most Cost effective way to get your product off the ground. I actually kept my development outsourced for the entire duration of my ownership of Campus Kaizen. It just worked for me. I didn't need to manage a full team of full time developers, deal with hiring, dealing with retention, uh, maintaining office space for an engineering team. Call me lucky, but I found development partners who delivered quality work and a budget. That worked for me. And then I just focused what I was good at. Selling strategy, customer relationships. Now you always have the option to bring development in house as you scale. And some founders like that, right? They start outsource and then they hire a team later on. There's pros and cons, right? Having your own engineering team gives you more control, maybe sometimes faster iteration and potentially maybe it lowers your cost at scale. But here's the reality. For most bootstrapping founders, hiring developers requires big salaries. Six figures minimum. The good ones approaching 180, 200 plus depending on when you're watching this, maybe it's up to 3, 350. All right? Development salaries are not cheap. I know I couldn't do it, but I don't know too many early stage founders that can afford that. Whereas outsourcing lets you get a product built for kind of the fraction of hiring even one full time developer. So my advice is if you can't code, you're not planning to code. You want to build a, uh, technology product, outsource to get started, prove the concept, generate some revenue and then if it makes sense, then you can consider bringing in developers in house. But I wouldn't let the question of build team versus outsource paralyze you. Just get the damn product built. The how matters a lot less than the uh, who did it and how you got it done. Just execute. Nothing real is going to happen. And then until work on the product begins. Next episode on Starting Up. Don't quit your day job. I'm going to share how I built a multi million dollar company while working full time for somebody else. And why keeping that safety net was one of the smartest decisions that I ever made. If you're getting value from Starting up, please subscribe. Share with other founders and aspiring founders. New episodes drop every Monday. My book Starting up will cover everything that we've discussed and more. Subscribers will get early access when it launches and a link in the show notes is there for you to sign up for my newsletter and be the first to know when the book drops. That's it for today. As always, I'm Jay Sensi. Keep starting up.