The Success Architect
Success doesn’t happen by accident — it’s designed, built, and reinforced brick-by-brick. On The Success Architect, builder and business strategist, Jake Lewendal brings a craftsman’s mindset to personal growth, wealth, and high-performance leadership.
With raw honesty and practical frameworks, Jake breaks down the systems, habits, and decision-making principles that separate the overwhelmed from the unstoppable. From building multi-million-dollar companies to coaching ambitious people, Jake’s philosophy is simple: success is a structure, and every person can learn to build it.
Each episode blends actionable strategy with real-world conversations featuring high-impact, career-driven entrepreneurs and operators who are building lives of purpose, discipline, and momentum.
This is for the ones who build. The ones who take responsibility. The ones who know they’re meant for more — and are ready to architect a life of depth, strength, and true success.
The Success Architect
The Seat: Stop Working to Be Needed
Use Left/Right to seek, Home/End to jump to start or end. Hold shift to jump forward or backward.
Momentum hit eight figures in three years, and then it stopped growing. Jake spent a long time looking for the reason before realizing the ceiling was him.
In this episode, Jake gets honest about how the same habits that build a company can end up capping it. He talks about the founder’s instinct to fill every hole, why “it’s faster if I just do it” works until it doesn’t, and the uncomfortable truth that the person who loves putting out fires has a quiet interest in the fires continuing.
He also walks through the practical side: using EOS/Traction accountability charts, building roles before names, and why a wrong name in a seat is worse than an empty one. Whether you’re a founder, a division leader, or anyone who’s become the go-to person for everything, this one is about learning to step out of the way and let your team actually lead.
Stop working to be needed. Start working to be worth having.
Welcome to the Success Architect, where we don't just build homes, we build legacies. I'm your host, Jake Lewendolf, custom home builder and coach. Each week, I sit down with builders and entrepreneurs who are ready to 10x their business, their health, and their mindset. This is where blueprints become breakthroughs. Let's get to work. The bottleneck was me. We hit eight figures in three years. And then we stopped. For a long time I looked everywhere for the reason, and finally I figured out it was me. Everybody on Instagram, everybody on podcasts, all the people you talk to, they talk a big game about what it takes to grow a company. But unless you have a really good coach or on the alternative, almost nobody talks about what it takes to get out of its way and let it grow. The exact thing that made me good enough to build a company is exactly what capped it out after about three years. And most of the time, this is where every founder starts. At the start of this company momentum in 2020, it was just me. Admin, bookkeeping, job status, back end operations, front-end operations, conversing with the client, conversing with the subs, doing the scheduling, absolutely all of it. And then I had my first hire, and he crushed it. The two of us sorted out who had what, and we moved forward and we both drove like crazy. But that line basically defined an era. Like whenever there was a hole to be filled, I filled it. And that's the deal as a founder. And it worked. It actually worked for call it for four years. A year after we hit eight figures. And at that size, that is the right answer. That's not a lack of discipline, that's the right answer. Whenever there was a hole, I filled it, and that's what we do. Nobody tells us, though, that there's an expiration date on that notion and that strategy. And that's what I want to talk to you guys about today. For me, it turned because the company started to get big enough that filling every hole meant something different than it used to. It got harder and harder. It basically meant that every single decision had to run through me. And I was the bottleneck on those decisions, which for a little while was okay. But as we got bigger and as we got more people on the team, it started to become very difficult. On site, as an example, somebody's got a question about a specific piece of the house. I had to know absolutely everything. I had to answer it and they had to call me. Even if there was someone on site who would actually who is supposed to answer the question, everything still had to route through me. Literal definition of a bottleneck. Same with the money, same with the administration, same with where the checks go, same with the taxes, same with everything. And that's the whole idea. That is when my business started to stall out. It stopped scaling, it stopped growing. We hit an absolute ceiling, and the sad and very difficult thing for me to understand was that that ceiling was me. I was the reason that we grew fast, and I was also the reason that we stopped growing. Same guy, same behavior. It just switched from somehow being the engine to all of a sudden being the ceiling. The interesting part for me, and most leaders and founders that I know, is that they say, look, it's a simple calculation of time. It's faster for me to do it myself than to teach it, which unfortunately is very, very true until the day that it's not. And that's the part where you hit that ceiling. And it's a really hard one to beat into your head. For me, it actually took a couple years, which is really sad that it took that long, but that's the truth of it. And the truth, the other truth of it, though, is that in order to break it, the only reason it broke is because there was enough pain. It got painful enough for me that I started feeling the burnout. I started to fall behind on the questions that needed to be answered, and the real bottleneck started to show. The interesting piece about this is this is not just a founder thing. This can happen to anybody. I personally know senior PMs at companies with 500 employees, and they have an identical issue. They have a division that they run, and it's easier for them to just do the work instead of teach someone to do the work, because that takes more time. And so they continue to run their division just like I was running it and be the bottleneck. But here's the deal. The truth is that the work you are best at is usually the work you're using to avoid the work that is actually yours. Let me say that again. The work you're best at is usually the work you're using to avoid the work that is actually yours. And the shitty thing is it feels like productivity the entire time you're doing it. So what is the solution and what is the pivot to removing yourself as the bottleneck? And I'm going to talk about multiple points in this section. The first one is something very simple. Something I subscribe to is traction or EOS. And there's a lot of different names, coaches, authors who talk about this system, but it's basically an operating system for a small business. And when I say small business, I can't remember what's actually included in what's defined as a small business in the US, but I think it's anything under like 100 or 50 million, something like that. So a good chunk of us. The first thing is building an accountability chart, defining roles, and actually delegating and implementing those roles. And granted, I can say this is the easy part because technically it is the easy part, but it's not that easy. You actually have to take the time as a founder to go in and define all this stuff, put your head down and do it, and then properly delegate it and implement it, which means you also have to have the right people. But that's a conversation for another podcast. The hardest part and the thing I want to talk about today is the willingness to not be needed. And this is a mindset shift. For a founder, for an entrepreneur like a senior PM running a massive division, everybody gives the exact same advice that I just gave about an accountability chart or an org chart. But very few coaches actually talk about what it costs a founder or a team leader to force themselves to be optional. Building the role, handing it off, delegating it. Though it's not easy, that is the easy part. It's just work. You put your head down, you make it happen. The harder part is being okay not being needed. And that's the part that I want to be very clear about because almost nobody warns us about this. The truth is for me, like I get a high off of solving a problem. I get a high off of being the guy who can fix it. And I know that's not unusual. I have people in my company who love this feeling. I know other people who have this feeling. I know other founders who have this feeling. But the sad thing is that this is ego. And the way to move out of this bottleneck and this potential for burnout and the potential to have your company scale is to remove the ego. The thing that I have to fight every day is that this is my company, but I'm literally working myself out of a job every single day that I do this correctly. At some point, if I have done my job correctly, I will not be needed anymore. The sad part is that for a long time, still a little bit today, but not as much, I still had ego. I still wanted to be needed. So even though in some positions I had removed myself and handed it over, I couldn't handle not being needed anymore. So I inserted myself. I would check in to make sure people were doing right, doing it right. I would micromanage them. I would give feedback when feedback was not actually necessary. But here's the nasty cycle and a picture to understand. Being the guy who puts out fires requires there to actually be fires to put out. And this is really shitty, especially with someone who's trying to grow a company or scale a company, because what it means is that if there's fires every week, then I get to put them out. But what it also means is if there's fires every week, something upstream, something in the system, something in the delegation is actually manufacturing those fires. And it might actually be me. We have to remember that the fixer has a quiet interest in the dysfunction continuing, because then you get to continue being the fixer. And that's just fucked up. Now, for guys, especially, let's let's apply this to marriage just to try to get the point across and make sure that we're all understanding this right. Because being a fixer is something that most of us guys are really great at. And it works for a little while. Like when you're dating, being a fixer for your new girlfriend or your fiance usually is fantastic. But once you've worked yourself into the relationship and you know each other better and you're looking to create a deeper connection, most married men know that problem solving only carries us so far. That instinct to fix things actually creates a situation where we're not present and we're not listening and we are not allowing our wife to just talk and we try to fix it. This is what's happening in the business. The last thing, and I hope it's obvious, but I'm gonna state it anyway, is that running 100 miles an hour and fixing every single issue, and then when there's nothing left to fix, you're probably in your unconscious going and creating some fucking dysfunction so that you have more shit to fix, it burns you out. And not only does it burn you out, it insults everyone around you. And that is the worst part. By micromanaging, by not trusting the people around me, I am teaching them that I don't actually trust them. And I'm insulting their intelligence, I'm insulting the work that they do. That one actually gets me a little emotional because it's something I still find myself doing just a little bit. And it's kind of shitty. And it's something that I work on every single day. Just remember from this that if you are the guy who puts out fires, you need fires to put out. And when there aren't fires to put out, sadly, I personally know people who will actually go create fires and so that they can put them out and feel good about it. The sad thing is that they don't even know they're doing it. For me, I got tired of being the fastest guy running. It wasn't just burning me out, but it was telling everyone around me who I cared about that I didn't trust them to touch the ball. Everything that we talk about on this podcast usually leads back to some sort of leadership in how we all want to get better at leadership. And problem solving is not leadership. Yes, problem solving is a skill that many leaders need, but it is not leading. Problem solving is just that solving problems. Leading is delegating, empowering, trusting. Solving is a single task. And just like I've talked about in other episodes, problem solving leads to some instant gratification, but leading usually does not. And this is where we must learn to be patient. Personally, when I come across something that I think maybe needs fixing, I've started to try to pause. Just like when I need to say no, instead of yes, I pause and I ask myself whether the situation actually needs me or if I need the situation. Again, solving problems isn't leading. It's just solving problems. And I promise you, solving problems is not running a company. Leading is. I want to dive a little bit more into the premise here and the solution so that you guys can walk away with a bit of a reframe and a way to actually kind of work on this situation for you. So I want to look at a metaphor. I played soccer as a kid, traveling soccer, high school soccer, all that jazz. And the interesting thing here is that if every guy could do the same or does the same job on the soccer field or on a football field or in any other sport, then the team's not going to be successful. Basically, the fastest guy on the field, like if you've got an MVP, can still lose you the game if he's in the wrong spot. And the shitty thing is that he's gonna lose it running full speed and looking like he's kicking ass and being an MVP. And that's why it's so hard to figure it out. And that's why so many of us continue on this path for so damn long. In soccer, there's 11 people on the pitch. Most teams, of course, have an MVP, just like I said. And the tough part is that sometimes you can put him in the wrong position, or you can rely on him to carry the entire team. And unfortunately, both are fatal and both look fine for a little while while they're happening, until you run into an opponent who is far better than you are. And again, like I talked about, this guy was me for a long, long time. What changed my mind was running into a stagnant revenue number, hitting the ceiling, getting stuck while still running 100 miles an hour. And then as I tried to hand off things in order to scale, I would micromanage. And everyone else on the team did not feel trusted. They didn't actually get delegated to, they actually didn't get to do their job. And usually that math ends up in an argument, ends up in burnout, ends up in a stagnant company. So how do we fix this? Going back to the EOS traction model, I wholeheartedly believe in accountability charts. And here's the way that I do it. First off, the easiest way is to look at your current accountability chart. And if you don't have one, create one. Literally, you just get out a piece of paper and a pencil and start writing one. And if you don't know what it looks like, Google it and write down what your current accountability chart looks like. And it might look like shit if you're at the beginning of the company or you don't even know what an accountability chart looks like. But my guess is by writing this down, you're going to get a lot of aha moments really fucking fast. The next piece that I personally like to do is I look at my goal for what I want in the next 12 to 18 months for my revenue and my profit. And I do a new accountability chart for what it's going to take to run at that level. And that is where the magic happens. That's where you start to find the issues of how do I move from this to that? And unfortunately, it's usually really uncomfortable and it's very tough. And the thing that I can tell you right now is make sure you do not put names in this accountability chart. The one you have currently and the new one. You have to start this with roles only, not the person. Most of us, because of how we start a company with just us, and then we add one or two employees and we start dividing things up, each of us turns into like a jack of all trades. But the problem is, is that that is not scalable as we've talked about. Everyone is a bottleneck. So by doing this accountability chart, you now have to divide those roles up. And that's why you cannot start with people's names. You have to start with the role. And the any coach that I've ever had in EOS or anything with executive coaching has talked about that roles are not built from people. People are put into roles. And that is exactly how the operating system has to work. And if you guys, if anyone would like an understanding of how to do a proper accountability chart, how to create roles, how to build this out, please just reach out through social media, email, like anything. And I'll be more than happy to help because this is usually the starting point of being able to figure out how you can scale to the next place that you want to go. And the starting point to removing yourself and anyone else in the company. Like I said, it's not just the founder. It could be a division leader. It could be a site leader, it could be an office leader, it could be anything. And this is the place to start to remove that bottleneck. The thing to remember is that an accountability chart is a long play. It's not going to be instant gratification, and it's probably actually going to be a lot of pain in the short term. But what I can tell you is that once you have that role set in your accountability chart, having the wrong name in that box is a horrific thing. An empty box on an accountability chart is information that you can use in order to solve that issue by finding the right person to fill that role. A wrong name in that box is a lie that you are telling yourself that you're going to make decisions off of for an entire year and it's going to lead you astray. The hardest part of this accountability chart, when it comes down to it, is the human piece of it. And this is where we have to slow down. If we go back to me being the bottleneck, I didn't stay in the seat on the accountability chart because it was the best use of me. I stayed because I already knew how to be good at it. But the next seat in the accountability chart that I needed to step into in order to scale was me becoming somebody I hadn't met yet. And that is hard. And that is something that you have to grapple with for everyone on your team. What this means stepping into those new seats, especially as the guy who was the bottleneck, is you have to leave the thing that you're excellent at, and you have to walk into the room, and you need to be okay doing something that you have not proven. You have to be okay doing something that you're not absolutely proficient at, but you know you can do. Again, I said earlier, making the chart is actually very easy. But moving people on it is extremely hard. And that is where that's where you earn. That is the toughest part. For those people listening who maybe are an entrepreneur or an entrepreneur who maybe know that they are in the wrong seat, are starting to get that feeling. We can talk about the emotional piece of that. Like being good at something feeds us mentally and emotionally in a way that occupying a seat on a chart does not, correct? But in order for a company to scale, in order for the organism to grow, sometimes we have to do the uncomfortable thing and we have to move and we have to try out something new. And that might mean moving into a role that we are not 100% comfortable with, but that we are okay growing into. That is the hardest part. Putting a good man in the wrong seat isn't loyalty. It's just a very, very slow way of failing that person. And that upfront conversation of moving someone out of a specific seat is extremely hard, but that is the long-term play in order to scale. Here's where I've landed, and I want to give it to you straight because it took me years to get here. I don't want to be needed anymore. I want to be worth having. And sometimes like this can sound like the same thing, and I promise you they're not. Being needed means the place falls apart without me. And I personally used to wear that like a badge. I also personally know other people in many companies who currently wear that like a badge. Being worth having means it runs and it runs really well, but the people still want me in the room, and that's where I want to be. Remember that one of these, the guy wearing the badge, is the bottleneck. The guy who people still want in the room is the leader. Whether you're a founder of a company, you're an employee somewhere inside of a company, I want to challenge you with the same thing that I had to challenge myself with. Stop working to be needed. Start working to be worth having. And then go find out what you're actually capable of when you're not the one holding it all up. Thanks for tuning in to the Success Architect. If today's episode helped you lay a stronger foundation for your business or your life, subscribe and share it with someone ready to do the same with theirs. You can follow me, Jake Lewendahl, on social for daily tips on health, wealth, and building success at last. Until next time, keep designing, keep building, and keep leveling up.