Mike: We had 43 videos on a page. So Google had to pull the plug in 43 times. So when you went to the Web site it said, “Waiting for video Google, waiting for video Google, waiting for video Google,” 43 times with thousands of people at the site all pinging the same thing. So it’s not that you’re crashing Google, but yes, you’ve got 1,000 people calling the same 43 videos all at the same time and all waiting for these videos to load on top of the fact that I’m a front page hack. I don’t know CSS. I don’t do DreamWeaver.
Tom: We didn’t give our in house programmer enough time.
Mike: Right. So they get everything ready for me and then I’m the guy that just goes in and dumps front page code in there ten minutes before the site is loading working on the bullets for the videos that when the site went live, like everybody’s laughing like, “My goodness. You’re talking about a 7 Figure Code. You’re going to teach us a 7 Figure Code and you can’t even create a sales page that can load on a Web site.
Tom: Yeah.
Mike: And we couldn’t get it fixed for 24 hours.
Tom: Now in retrospect, moving forward we’re going to use like Amazon servers and stuff like that. So it’s all a learning curve. And I guess, Jeff from my background of working with top professional athletes and TV stars, and things like that, as a marketer you’re doing a disservice to yourself if you don’t give yourself a self analysis afterwards. “Hey, here’s what we did right.” We pat ourselves on the back and say, “Good job.” Here’s what we should make a note of to do next time we have a big launch like this so it’s perfect.
So nobody is perfect, and that’s kind of the cool thing from the 7 Figure Code is you don’t have to have it right. You just have to get it going. You know we could have dragged it on and made sure that all of the T’s were crossed and all the I’s were dotted, but it would have taken two weeks, two months, who knows, two years before it would have been perfect.
But we picked a date. We stuck with it. We ran with it. We provided value to our marketplace. Prior to that, we established ourselves as people who can provide value and for all the people onboard.
When it’s all said and done, even more than headaches and complications and people not loading the page for a couple of hours, they still stuck with it because they knew at the end of the road, when they finally were able to get there it would be worth the wait. So all in all it worked out tremendously well. So we pat ourselves on the back. We had fun. And we also said, “Man, next time we’ve got to make sure we do this and do this and not do that and not do that.”
Mike: Yeah, we had some fights with some of our friends. We were hugging and kissing at the end, but we had very, very good friends that called us. It was like, “Well, how about…” and those type of things because our sales page wasn’t loading and stuff like that. We were getting accused for different reasons why it wasn’t loading and that wasn’t the problem. So it was all adrenaline because we hadn’t slept for two days.
Tom: Three.
Mike: Really three days. I mean it. We did not sleep. It was like we were looking at each other saying, “Do you realize we haven’t slept?”
Tom: Seventy-two hours.
Mike: And just getting ready to launch because we were in such a crunch. Outside I think it was a big success and we love it. I mean if I crash a server on my next product launch I will always look at that as I did my job right on the pre-launch. So we’re pretty happy with it.