Sorry. There’s something I didn’t tell you.

This will be the hardest keynote I've ever given my whole life. If you're a sympathy crier, I'm warning you right now. Yeah. What made you want to share this? I don't want to share this. That's why I just want to get through this one keynote. I just need to get through this one. Then there are some more technical.

I can talk about compensation models and marketing all day.

Economics, let's go. Even philosophy I'd be okay with, but this one's tough. The untold turnaround. In 2024, I traveled to over 30 struggling businesses in North America, and most of you have seen the show on YouTube, post on Facebook, etc. And it was great. We go out and travel to these businesses that are struggling and we spend one day with the owner, usually actually a few hours, trying to turn around their company, and we call them back, usually six weeks later, and see if any changes have been made inside the business, if they made any improvements. I admire the business owners that even allow us to come on the show and apply to come on the turnaround show. And the reason is because I'm publicly showing their weakest moments in their business. I'm publicly asking their employees about their failures. I'm asking them about their personal issues, the debts that they have, the struggles that they face, and the problem that we as business owners encounter every day. But yeah, I'm asking them to put it on a public stage and throwing cameras in their face and microphones on their T shirt. And many times in the comments you might have seen people will get vicious.

Talking about people when they cry, when they have tears or when they go through struggles and they mock their decisions and things that they've done in their company to get in a really bad spot. And it kind of annoys me because I'm allow these people are publicly allowing me me to come in and talk to them at their lowest moment in business, when they feel like giving up. And the last resort is you to call me. One turnaround episode last year was ongoing the entire year. None of the thumbnails you've seen so far or the 30 that I've shared publicly. We've never released the video because the turnaround isn't actually over yet. Today I will share the beginning of that story and on Saturday, another speaker will share the other half. And this is the story of the untold turnaround. I hope there's no sympathy criers cause I'm gonna cry.

I just wanna get to this keynote, dude.

This is the hardest one.

The start of it was three years ago, January 2022, landscape summit, which this event used to be called Landscape Summit, specifically for lawn care and landscapers. In the Q and A session at this event in Ferndale, Washington, I was asked if I would ever start a CRM and start a software business. And at the time I said I don't want to start a CRM. I don't have any plans to start a CRM. A CRM by the way, is a customer relationship management tool. Think jobber, copilot, service, autopilot, lmn, et cetera. But I said, hey, no, I don't want to start that. I knew the struggles. I knew enough people in software to know that that was extremely difficult. So fast forward a month or two later, time going on, and I started to realize that robotics was not going to be the thing that separated the noobs from the pros in this industry. In the United states, there's over 600,000 landscaping companies.

The vast majority of profits will go to the top 10%. And what I see the top 10% doing over the next several years is embracing software. Now as time went on in 2022, I started getting frustrated because we were starting to scale up Augusta Lawn Care and the franchises and all the locations and we started having a lot of issues with scaling it up internally at command center as well as just issues that I knew would be easily solved in terms of deposit thresholds, credit card requirements on file, etc. So sorry, getting frustrated with it. I started seeing it affecting cash flow, different aspects of the owner's locations. And the question started to haunt me like where did the founder led companies go into in software when it came to lawn care? In the lawn care and landscaping industry, a good friend of mine had recently sold out his stake as co founder in another company that I had previously been using. And even more recently, the founder of lmn, Mark Bradley, has sold out his position in lmn. And I see this as a massive loss to the industry. And the reason for that is because once the founder has left, you can consistently see these companies flounder. They do not innovate, they do not push the envelope and they stop investing in their product. And because of that, our industry falls behind. And I genuinely believe that the lawn care, landscaping and home Service industry is five to 10 years behind when it comes to software. And so I said, where are the founder led companies? There's no one pushing the envelope here and willing to invest in your amount of money over the next 10 years to catch us up. So in summer 2022, I had talked to a friend for a couple years and I've been helping him with his business already and kind of trying to help him get the business more established. And I acquired the code base from Lawn Pro. LawnPro is still in operation today. And I said, hey, look like, I think we can improve this. There's all these different aspects that are good inside the current database and I think these are the improvements that if made, would be able to massively improve the industry. And so basically I gave away a minority position of the company in order to be able to take the code base and run with it. And I didn't tell anyone about this. This was 100%. Not a single soul knew about what was going on behind the scenes and the negotiations and the attorneys and everything that we were getting involved here. In July of 2022, there was a day when the current, the CRM that we were using previously went down for six hours. And I remember the hate and the vitriol that was cast upon them on Facebook and on groups. I remember we had to let everyone go from command center. I was like, you can't do anything. You can't log in. It's embarrassing to take a phone call.

And it's not, it's not, it's not working.

And I remember thinking, these are going to be my problems if I do this. And then Liz came to me the exact same day without us talking and said, you know, in the future, if we do this, this is going to be our problems. October 2022 since down now in Bellingham at Landscape Summit we announced that, hey, I'm going to launch a. Launch a CRM. Over the past one to two years, there has been very little innovation and leadership in the CRM world for service based businesses. Now I have gone on record saying that I had no plans of starting a CRM. And at the time I that was true. Over the past 12 months, as I've tried many software systems, looking for the best alternative for Augusta lawn care and trialing many of them, getting to know the founders, getting to know the tech developers, and looking at the actual tech stack behind these products, I realized there was no other choice but to start my own. And it is for that reason today I'm very happy to announce that starting In February of 2023, CoPilot CRM.com will become available for all of us to use. We took the code base from Lawn Pro in summer 2022 and spent the next six to eight months rewrapping it improving several aspects of it and rebranding it to Copilot. On February 2023, we launched Copilot CRM. And that was almost two years ago next month. Now in 2023, we just hit the ground running immediately. I started investing in the engineering side of things and, and getting more engineers. Previously the code base had four engineers working on it and so immediately more than doubled that and then tried to triple that throughout 2023. By doing so, we had this massive ramp up of the amount of features that we were pumping out. Cool. And then in December 2023, Augusta Lawn Care moved in. And so about 150 locations moved into Copilot in December 2023. And at this point, we were firing in all cylinders. Everything was going incredible. We had basically just eclipsed actually getting into profitability, which is insane for a startup and a tech company that is pouring money into something like this. Everything, if you talk to me, then we were going to conquer the world. We had just done a launch at last year's Landscape Summit and it displayed deposit thresholds and card on file crimes. And we were hyped in January 2024. So a year ago this month we tripled the number of members inside of Copilot.

And then we entered into bugh.

BUGH was not fun. We had so many bugs coming in. It went from 5 to 10, which is a very manageable amount of bugs. And in every software there's going to be bugs. But the threshold of pain that you're willing to endure is basically how much can I then allocate towards innovation and creating new features. So you're always balancing this out.

And we went from that number to.

50.

And then 80 and then 120 and.

Then 150 and.

Then 180 and then 200 and then 220 and then 240 bugs reported and documented inside the system.

And everything was breaking. This one's tough.

First off, because I'm sharing personal videos that I made that I didn't think I was gonna share with everyone.

That's tough. But more importantly, right now it's like Copilot just like debilitating.

At least once a day, I think I want to quit.

Just painful. Like literally just like you look at someone will say something on Facebook or whatever and just like daggers because it's true stuff. We're messing up such a. It's so fragile right now.

And like I'm not sleeping.

I don't need to do in a lot of the areas.

But I can't get in really nice. Do a lot of engineering and doing what I can in terms of like leading the team etc, but.

It'S exhausting.

It is, it is. Every time I see I can feel this wave of like anxiety every single time I open up and see a message or something goes on or I get an alert, something going bad. Today there, Today there's over 50 bugs in psychopod.

And that's after like two, two, two weeks of just solid fighting bugs.

Stop development, stop the roadmap and we're just fighting bucks.

We are losing members.

Going back into bur.

All of the destinations using it, every single location is using copilot.

And literally a week later everything broke up. Just messed up in the moment.

When you make the video, you're just doing it to document it. This is the first time I've gone through like so partly going through hell this past year. I knew that we would come out of it and I knew that I would want it documented. So I did, I made videos. But in the moment you're not thrilled about it. You'll see like even when I show the video, like I just turn it off sometimes.

Just like, oh this is so stupid.

Because in the moment you're not. But I also wish I would have had more videos back when I was sleeping in the closet. I wish I would have had more videos of me working out in the field for 12 hours and then going to school for four hours and then getting up a few hours later to do it again. Like I wish I had that documented. And everyone says that like Alex says the same thing. So like when I was going through hell, I'm like, I'm gonna document it.

So stupid. Emails broke, texting broke.

Merge tags broke, Sequence automations broke, push notifications broke, iOS broke, Android broke, the native version of the app broken.

In, app alerts was broken. Literally every single piece of the software. Absolute joke.

I do believe that we will turn things around. I have no doubt. Especially the past couple weeks. Made a bunch of really good changes. I fired some lower left debt, lower level devs. I'm doing everything I possibly can.

And that's the only solace I have, everything I possibly can. And so I'll show those videos tonight.

And like hopefully the goal in doing that is not I feel people feel bad for me. It's none of that is the matter of they have felt that same way and they are not alone. And if they have any respect for me in the fact that they travel across the country to be here to listen to what I'm talking about. I would hope that they also realize that even I went through those same things this year.

Took the family on a vacation, the entire extended family, all the nieces and nephews. I worked for the vast majority of the day and night.

I'd say maybe 50% of the day I would work here and there taking meetings, etc maybe 60% and then once they went to bed, I would work all night, five or six hours at least. We were there for four days in Mexico. It was an awesome trip. Loved it. Worked every single minute almost. And if I wasn't working, I was thinking about it.

But it so bad dude.

Just like reliving like I remember like.

So vividly like not sleeping and like, like it's torturous and like. Yeah.

So right now.

Every day I want to quit.

Every single day I have my head, I open my head in my hands and just say this hurts.

Because something new will break, the servers will break, something will break. And every single day I will disappoint the people that I love the most.

So do I think I'll turn around 100%? Do I think in a year I'll probably watch this video and laugh at myself? Probably. But this is hell. This is hell.

And so this was that Mexico trip. This is the social media version of what most of us tell that was we took four or five days in Mexico, had the privilege of taking everyone down there.

Had a really nice place right in.

The water and I did not think about anything besides issues in the business. I scheduled all my engineering meetings throughout the night because we had teams around the world and were working literally 24 7. I was rebuilding the engineering team as a non technical co founder trying to figure things out.

And yeah, it didn't get any better.

So it's just a. After 3am.

And the site's download.

I contacted Dustin. I basically said like throw money at this thing, we need to fix this no matter what. So.

I said if there's a button here for a million dollars, I just push it. If we get to fix this problem.

Crazy. We don't even know. I sit down right now.

Oh.

So painful.

Again. If we don't have a stuff in like 20, 30 minutes, this whole thing is just.

Everyone starts waking up right around 4am Eastern when everyone starts hitting the API.

Oh man.

Oh so dumb.

What are we doing folks? Goodness gracious.

Don't worry, it gets worse.

I think it'll end good. Like I think it'll be motivational at the end but the first 25 minutes.

Reliving all that stuff, dude.

And then in spring 2024, people started posting about it. And if you're in the crowd, I'm not trying to blast you, okay? I just asked the support team to.

Get me a few screenshots of comments about me.

So I'm not gonna read them. You can see on the screen, good times. Let's not make this too much. All right? So these are on Facebook, public posts. These were inside the member group, People saying things about me, the CRM, etc. I did not capture these or keep these. I just asked the support team. Parker can be my. My witness to go grab these for me. But, yeah, I know almost all these people, by the way. And the thing is.

They were right in every single one.

And although if you would have looked at, say, in Instagram or social media, you would have seen the Mexico trip, etc. For many of us here, there is an untold turnaround happening.

And you don't show that part of your life. Maybe one out of a thousand, maybe one out of a hundred thousand people that watch my videos actually ever apply. Do we ever actually see the depths.

Of the despair that you're going through?

My mistakes can affect them. That's the challenging part with a brand.

And community is you make yourself vulnerable.

To the mistakes of others. And so I'm human, and especially when we're trying to make things happen and make changes and improve the systems, I'm.

Going to mess up sometimes.

So I hope I can reverse course.

And improve and course correct and get better feedback loops to make sure that doesn't happen.

But ultimately, me making mistake of something like Copilot affects them, so that's also a liability. Enjoying a franchise or any community or entering a relationship or starting a family, like, there's liabilities and risks involved.

So. But, yeah, like, I'm not gonna hide it. Like, yeah, I messed up big time. So hopefully it, like, yeah, yeah, don't.

Worry, it got worse.

But I wanted to directly address currently, what we are going through and during the stage at Copilot and just answer as many questions I possibly can by communication. I know over the past couple weeks, I have not been in the Facebook group very much, and that's because I've been having my head down, making sure that structurally, I can do everything I possibly can inside of the business to make sure that these bugs and these issues are resolved. And we continue to work towards our roadmap. We have decided to wait on the release of new features. We have a lot of work already completed. Completed on things like the waiting list, digital signatures on, on estimates, chemical applications, etc.

We have a lot of that work.

Completed and we were planning to beta test that and then release it into production March 1. We are going to delay that for now. I expect that to be at least two to three weeks, but that is an indefinite period of time because we must stabilize the system and we are making a lot of changes internally both in the team, how we do our code development, how we do quality assurance and testing, et cetera. And I understand that that doesn't solve the acute pain that it is causing in your business and the pain that is anticipated if you enter in your spring rush with a faulty system. I know that for the vast majority of our users the amount of dependency on the Software will more than 4x after March 1st. For the vast majority of our users.

Due to, due to the fact that.

We enter spring rush.

This is across all home services, not.

Just the green industry. Spring is the time that we get most of our leads. We are extremely busy and we can't have these bugs and these paper cuts and these failures on the software's end. I 100% understand that this is causing business pain and we must fix those problems first before we do new features, et cetera.

I know that I in the past.

Had said, said that we would have the chemicals done by March 1. However, there is more pain being caused than the positive benefits that would be brought on by that use case. If you are a chemical applicator that was fully anticipating that by March 1st you'd be on the system, we will happily refund you any sort of any fees whatsoever. And I know that that is not a trend that I want to continue in the future of promising things. And then it gets a month and then two months, then a year and years down the road. I hate that. It's not something that I want to be known for copilot. But understand that right now we must focus on the bugs, the stability of the system, etc.

Yeah, that was a little humble pie. That was a video too and I did not look at the comments because I'm sure I got flamed. All right, so I think this is the last one of the last videos. But we just started having like say sorry. It was eventually just like I felt so out of control. We're pushing all the deadlines and this, this video, if you notice the last video, same shirt as the video that we're about to play, the last shirt was inside out.

All right.

Wasn't really clicking, firing all Cylinders.

Let's go ahead and see this one time.

And so I just want to be honest about the timeline. I do believe it'll be one or two more months of bug hell. I think it will be two to three months before stabilization. And we are considering stabilization at a certain number of bugs in our system. There will always be bugs, but we believe we can get it down significantly back to what it was last year and that would be 80% reduction of what we currently have in terms of bugs. And I do believe that towards the end of those two to three months, we will be able to start releasing features that are 60 to 70% done. And that includes the wait list that includes chemical applications, signatures and estimates and a lot of features on the dispatch board, etc. That we have literally 60 to 70% completed prior to four weeks ago. Stopping the development of that. I know I'm not in the Facebook group every single day, responding when people tag me or making comments, et cetera. I can only take so many inputs in a day and right now being reactive on my part is like very, very would be a poor use of my time. I'm in with the team every single day trying to make improvements and help all 700 users of Copilot. And so as much as I very much like being one on one and addressing people's comments and concerns and emails one on one, I'm just not doing that right now. I do believe my time focused on the entire code base, the team making sure that leadership is in place and problems are being solved is the best use of my time. That being said, someone had asked me an email, they said, are you like taking down note of people that are saying negative stuff right now? I'm not. First off, I'm not seeing it really if it's. If someone's saying something in the Facebook group or some people have made some videos about me and stuff like that on YouTube and things and it's fine. I deserve every bit of the frustration being given to me right now and I deserve any of the criticism at this point. As a leader of any organization, you or I will get the brunt of the praise as well as when someone. When things go wrong. And so we are in a very low low. And so I will get the brunt of that and I deserve all that frustration. And if someone needs to leave Copilot because the spring rush is coming up and they're like, hey, I need to make. I can't wait another couple months. I need to be able to have these things more Ironed out. I understand, and I apologize. I didn't. I. If I would have anticipated this going into 2024, I would have been more clear and honest about that. I did not anticipate this at all. I didn't think that what happened in December, January, with us increasing so many members would have this kind of impact. And I thought we would be able to fix it in a couple weeks. I. Genu, genuinely did believe that.

No, the product needs to get improved. It needs to get fixed. Dude, Everyone, yes, they deserve apology. They just want the stinking thing to work. The issues I was having.

Got to a point to where I just didn't want to use the software. I didn't want to be in it. I dreaded having to, you know, go in copilot and do what I had to do. I eventually ended up reaching out to Mike Andes personally. Kind of like, listed all the. All the things, you know, like, hey, if I'm paying you 250 bucks a month and I can. I'm still having these issues, like, that's. That's not right with me. And so we've done a better job of stabilizing things. There's still a little bit more to go in the next couple months. I think that will, you know, that will evidence itself over the next couple months. But.

Whether that's healing for me, I don't know, dude. I don't even think about it.

This is just more like, painful thinking about this again, because, like, this is stuff that I thought was not. I thought, like, it was in the past, like, it was done. All right, so spring 2024, I came to the realization that this was going to take way longer than anticipated and. And cost 10 times, if not 20 times more than I anticipated. And one of the. One of the actually lowest parts was actually in May, I was flying out of Alberta from a turnaround, and I was in the airport, and all our flights were getting canceled. I was the media team. I think it was actually just Terrell at the time, and flights were getting delayed and everything. And I got this text message and basically was like, hey, Mike should really just turn around his own business. And I was like, you're right. He probably should. The challenging part was I could actually not do the work required. If it was just a matter of, like, hey, you need to put your head down and get something done, I would have been doing it. I would have been, like, on whatever was required to just keep working. I could not fix these problems. And so in summer 2024, I realized there's a massive skill gap of the amount of users that were inside the system and the code base that the fragility of it and what kind of skill, from an engineering perspective was actually required to be able to bridge this gap. In summer 2024, we decided, hey, this is, this is not a quick fix. This is a restructuring of millions and millions of lines of code. In that I realized because of the investment that was going to be required, I need to buy out my partner. When the business was at its worst point, we were bleeding cash, we were losing members, I was funding it all myself. I said, in order to be able to turn this thing around, to take millions of dollars and I, I will have to buy out my partner. And so the minority partner that I had at the very beginning, that came over from the previous code base, I paid him ungodly amounts of money to make sure that I owned 100% of the company and could make the investments required to turn things around. And that was very, very difficult. Personally, I could like there was a huge investment just to get that cash and make this bet. This is the biggest bet I've ever made on my personal self because at the very lowest moment, I had to go all in from a cash perspective to be able to make sure I own 100% of the company and then could reinvest back into the business. So then we started restructuring the engineering team, restructuring how this was all going to work and how the API works in the back end, etc. In summer 2024, that's when Josh, who you'll hear from on Saturday, Josh Kahl made a big gamble on us, big gamble on me. More specifically, he had been working with us part time as a consultant in his. While he was working his other job previously at ActiveCampaign, which is a massive company that has over 200 million in revenue, very established and had a fantastic career. And Josh made a bet and I don't know necessarily why, he can maybe tell you on Saturday because I've never asked that question, but he decided to come join full time and that was what we needed. It was.

It was an answer to prayer. It was at my lowest moment that I could not turn this thing around.

And whenever I watch the turnaround applications because people submit videos all the time and talk about what they're going through, I think about this moment for me and I needed help.

And the humility to be able to.

Recognize you can't do this on your own. Mike is obviously a big reason I joined Copilot when he was telling the untold story. He was asking or wasn't sure why I joined Copilot 1. Obviously Mike, you know, he has a really incredibly bold vision, very sincere, ton of transparency. He was very open with me about the books, about the struggles of the business and he has a very clear mission to say sincerely, help small business owners build the American dream. And Josh made a big gamble leading me a big company. But more importantly put his reputation on the line and started to go to bat for us for engineers, knowing that that was really the deficit in the team. And these are not quick hires. This is not like hey, come interview and we'll hire you tomorrow. These are 6 and 12 and 18 month processes of courting these people and bringing them from very well paying jobs and publicly traded companies to try to join the team.

Over the course of the next few months, we start retooling the support and onboarding. This is the only thing I could really do. I cannot change the code base.

I cannot do code. And I did a little bit of code way back in my college days, but not enough to be able to fix these problems. And so at the peak in February, you can see our churn was 11% every month. And that means that every single month 11% of our customers were leaving. If you run the math on that, in nine months you will have zero customers problem. No matter how many customers you will add to this, you will never be able to grow this business. Over the course though, over the next several months, because I was able to start focusing on other aspects besides the code and the engineering side, I was able to focus on things like the customer and the member roadmap. There's something I could do, I could actually focus on this. How do we actually get people to use the system and use the software? The same way that when a customer accepts an estimate that is not the end of your journey with them. There should be an on onboarding process. How do we actually get them to get more of our products and services that they use? So I created this, the member roadmap really started to dig into this. But just because those low, those lowest moments had kind of gone through does not necessarily mean a turnaround was done. All of the hiring engineers that we are now bringing on board, I was starting to realize the impact financially what this is going to do to me personally.

Budget from engineering tech and product stp.

So we're ballooning our expenses massively. We're hiring a bunch of people. It is awesome, super good, but gotta pay the bills and we're probably gonna double spend here. So for every dollar we make we will probably lose $2. Sounds like a great budget. Never lost as much money in the business.

Kind of reminds me a little bit.

When we started the franchise but at that time we were losing maybe 20 cents for every dollar. Now we're losing 100% of a dollar every time we spend a dollar. That's just.

So gotta make sure you can afford it. It's already ballooned to six figure losses. Probably double now. So gotta figure out a way to figure it. Like to pay for this though we get more users but and hopefully we can by spring. Like as we go into the off season things are much more reliable. We haven't had any crazy incidents, etc. But I don't really blame people not wanting to join. It's been 10 months since we last released a meaningful feature.

And yeah now it's a matter of can we hold our breath long enough to get out of this. Just financially gonna be a big big spend here. So what killed me was having to buy out Patrick from a cash perspective that just, just kind of tapped me out this year. So then we got October, November, December, January, February. We got six months here and so we can get our stuff together and then show just how much of the back end has actually improved and changed. So try to just tonight figuring out the budget but then also figuring out what's the path here. How are we getting back on track? How do we actually tell the story to users and win their trust back? So here we go.

So then in December 2024 we got the bugs down by about 80%. We're not there yet but we are on our way. I want to recon go back and look at the hardest year of my career and what did I mess up on and what did I learn. Hopefully you can take these learnings and these lessons and not make the stupid mistakes I did. So first off, what I messed up on, I got stuck in growth mode. Growth creates chaos. Heard me say before, growth sucks cash but growth also creates chaos in the business. And I got stuck in growth mode. I kept growing. We literally tripled in a matter of just 30 to 60 days. I also messed up on being cheap. I didn't surround myself prior with people that had the similar goals as I did. So I started to spend over $12,000 a month between personal coaching as well as getting inside a group of people that were all doing SaaS software as a service. People that were like minded, that were ahead of me in the game, that were at the same size or above me, what I messed up on, every problem seemed like the end of the world. There was multiple times I went more than 48 hours without sleep multiple times. And it wasn't a matter of me working hard. So that's just. I'm alwaysn't like some great hero. This was anxiety not allowing you to sleep. This is your heart racing and feeling like no matter what you do, even if you did fall asleep, you'd never wake up rested. That's what this felt like. I didn't share my goals with my team. It's a big mistake. And it doubled the time that it took for me to bring on key team members that did help us turn around the business. I would just share the goals and what is the mission of the company and what's the end result? What does this look like in 10 years actually giving them a roadmap for that, actually shared it instead of being so conservative and not wanting to share everyone else. What I had in terms of planning, what I messed up on, I moved too quickly. What I learned from that is listen, test, iterate, get feedback, repeat, then launch. And I just kept launching stuff. I kept going and going. I was just going so fast. Instead of just listening to members, listening to customer feedback, listening to people around me testing these things, iterating on those incrementally getting feedback again and repeating that cycle over and over and over again. The reason I need a VP of product like Josh is because that's all they do, is they talk to people, they iterate, they get feedback and they just keep going through this cycle. And to me, as a founder, as a CEO, as an entrepreneur, that slows me down. What I learned is that one good change in the business every six weeks, you will do just fine. I would argue one good change every quarter, your business will be fantastic in a matter of just a couple years. And so instead of trying to pound things out, I'm talking about features here. But think about in your own business, you're going to leave this weekend with 100 different things you want to be doing in the business and you're going to hear all the keynotes and all the talks and you're going to talk to five other people and all these brilliant ideas. And if you just do one of them in six weeks, it's the main one, it's the one that you know you should be doing, but you're not. The one major domino in the business if it would topple, would change the trajectory of the business forever.

So my Entire thought process around business completely changed. Instead of being so fast and focusing on the pivot and the innovation, just focus on doing it better. You cut grass, just do it better. You talk to customers, just do it better. You do sales calls, just do it better. You don't need anything new. You don't need anything flashy. You don't need to leave this conference and go change your business model or implement some crazy new marketing scheme. You just need to take what you're doing right now and do it better. And none of us want to hear that, because the people that do that aren't in this room. Entrepreneurs will go, we want to do next the next shiny thing. And you're going to get 10,000 ideas, and only one of them needs to happen.

What I learned is that culture fit when it comes to employees and team members, culture fit is 101. Having experience is 201. It's the next level. Ideally, someone has experience, been there, done that, 301, and expect to pay accordingly. When you start bringing on the level of people, we need to turn around the business. I had never paid that in my entire life. And I had made less on my tax, personal tax return than some of their salaries. What I learned is you're going to have to let small fires burn. Prioritize and execute. As Jocko says, focus on what you can control. I had to realize I could not fix the code base. I needed to have people in place that could. And then I need to focus on what I could focus on. The member experience, the onboarding process, other aspects of the business that I could actually control. And what I also learned throughout this entire process is that in war, you gotta turn off the noise. And what that turned out to be was me leaving over 30 groups, WhatsApp groups, Facebook groups, personal stuff, just shedding everything. And it happened over the course of one week. And Dr. Kashi said, you need to get quiet. You have too many inputs. You need to get very, very quiet. People do deserve to know what happened on my end because I left groups, I left like, I just cut everything out as part of, like, when there's chaos, it's like in a time of war, you've got to get quiet. You got to regroup, and then you got to get violent. And that's what happened. That's how we were able to fix it. Hire whoever you need, untapp the budget.