Web Process Consulting | Recurring

Chris LaFay: It.

Gavin Taylor: Hey. Hey.

Chris LaFay: Good morning, sir.

Gavin Taylor: Good morning. Are you back?

Chris LaFay: I am. I got back from Arizona and I. I'm going to. What is it called? Going to New York on Wednesday. Thus. And thus ends my, my, like back to back travel. That was not intentional, by the way. My. I was on a meeting like right before this and Chrome crashed out on me not once, but twice. So I am restarting my computer right now because you just sometimes just got to restart your computer.

Gavin Taylor: So.

Chris LaFay: There's not restarting. I would really like you to turn off, please. How was your weekend? You do anything exciting?

Gavin Taylor: You know, my mom came in town, she's still hanging out with kids, so that's exciting. We went to the zoo, did some fun stuff, had a good Easter. So it was all good.

Chris LaFay: Very nice. Now when your mom comes in town or when family comes into town, it doesn't normally lean towards the, the chill side of life or does it lean toward the chaotic side of life? No judgment. I'm just curious.

Gavin Taylor: It's a lot. It is a lot. Mainly because the kids.

Chris LaFay: Gotcha.

Gavin Taylor: Yeah. New kids get wound up just like they do with any grandparents or whatever. It's. Kids get wound up. They don't act like they do. The, the schedule is out of whack. It's the biggest thing.

Chris LaFay: Yes. I say that as if I have. A lot of experience. I don't, but my, my nieces are. Oh, come on, come on. Keyboard connect. You know, all these things are Bluetooth and you're realizing, you know, I realize if Bluetooth just doesn't work, none of my peripherals work. I'm like, that's scary in a way. I'm like, I can't. Obviously some of them have plugs. I realize that, like that's not, I'm. Not that oblivious to technology, but. We going back to kids and schedules and stuff. My. It's not meant to be as morbid as it sounds, but my, my sister in law on my wife's side. My wife's sister is in the process of getting a divorce, which sucks.

Gavin Taylor: And.

Chris LaFay: So she moved in with her parents and she has two kids. Two kindergarten or first grade and preschool. And so they're basically living at grandma. And grandpa's house right now. These kids. And man, these kids are loving life living over there. But they have to make these like mental swaps because this isn't just fun time at grandma's, this is life at grandma's.

Gavin Taylor: So yeah,.

Chris LaFay: Now we're back.

Gavin Taylor: There you go.

Chris LaFay: Now we're back. I feel more at home now.

Gavin Taylor: No. You know what's funny about the Bluetooth thing? You said there's two things I refuse to do Bluetooth, and that is keyboard and mouse. Like, this is where the gaming part of me comes into play. But I need that instant reaction time with it, not the minuscule lag you get that a normal person would never like, realize. Is there you.

Chris LaFay: Huh?

Gavin Taylor: Huh?

Chris LaFay: Yes, exactly. I mean, dude. But like with RuneScape though, you don't.

Gavin Taylor: Have to be like, oh, absolutely you do.

Chris LaFay: I thought it was. I thought it was. I thought it was. I thought it was. I thought it was. Turnbait. No. Oh.

Gavin Taylor: So it's. It's a tick system. Okay. Yeah. So a lot like, wow, where it hits those certain ticks, you gotta be tick. Perfect.

Chris LaFay: I see. I got you. I got you. That makes sense. All right, now I have all my stuff. Oh, junk. What's my password?

Gavin Taylor: Oh, crap.

Chris LaFay: I need to log into. Back into WordPress. By the way, I am getting up. I am pulling up all the coupon. Stuff that I worked on. This is not.

Gavin Taylor: I'm excited to see it.

Chris LaFay: Yes, I got it to a good point. It's not meant to be.

Gavin Taylor: 100, Don't forget. I need to go over the QA document that I made last week and I want to talk to you about the web design development. Like, overall. Hey, developer. Regardless what developer we use, I want to be able to hand them our sop. Like, follow this. It is up to tell them, hey, this is how you write the code or anything like that. But hey, here's the do's and don'ts. Here's the standard things that we need. I want to talk to you about that by the end of this call too.

Chris LaFay: Okay, cool. All right, here we go. Seven minutes of rehashing and setting up my life again. We are back. Those are not neither of those screens. Right? That's the right screen. There it is. Okay, so I believe you see the back end of WordPress. Fantastic. Okay, so I started building out the basics of what I'm just calling the local jungle core plugin because I have a feeling we're going to add some pieces to this. So I didn't want to just call it QT coupons because that seemed like a bad idea. So what this, what this plugin does now is I went ahead and set some very basic settings kind of at like the. At the business level. Now, are we utilizing all of these things? We're absolutely not. But I just went ahead and just wanted to get the mind turning in this way. So, like what is the primary address? Primary. Like, these are all, like, the, like, the. The things we talked about, like, from, like, months ago, Right? Core things,.

Gavin Taylor: Brands, technically. Right?

Chris LaFay: Yeah, exactly. Correct. Yes. So when you add this plugin, and it will add a default settings panel that can be expanded upon later. Again, not really using any of this right now. Just for. Just to show. It adds in two sections to your panel, it adds in coupons, and it adds in locations. Locations is mostly fluffy at this point. It's not entirely fluffy, but it's there just as a. As a sample. So coupons. You have all of your coupons, you have them categorized. I'm gonna. I'm gonna display this as if it's, like, overly simple, because it kind of is. So when you edit a coupon, you can edit its name, you can edit the price. You have your little WYSIWYG editor for typing in whatever description that you want. You have your disclaimer. You can have the expiration dates, Which. The default's 14, unless you change it. And then you can make the. You can edit the sort order if you wanted to add prioritization. And then over here, there's all your categories. Make sense.

Gavin Taylor: Yes.

Chris LaFay: Fantastic. So over here on the home page, there is a custom block called LJ coupons. When you drop LJ coupons. And please ignore the fact that there's, like, text, color, weirdness in the back. End of the site. Like, I'm not. Yeah, not too worried about CSS at the moment. When you drop in the block, you have your settings panel. Over here, I can display them by most recent, which will just show the three most recent ones you see here. Now, there's three down there. Now, I can show them by category. If I only wanted to show the ones that are general, those are the ones that are general. Or I could do a manual selection. And here's my list of all the different things. And I can bring in the. I'll bring in the dealer savings, European oil change, and full synthetic oil. Now, it doesn't show the column layout on the back end, but on the front end, you can change it to whatever column layout that you want. So if I wanted to go to column, I could now go ahead and save this. I went ahead and added in a fourth. So now if I go over here to the homepage. If I go over here to the homepage.

Gavin Taylor: Nope.

Chris LaFay: If I go over here to the homepage, we have our coupons. Now, the title is over here. The title's in black at the moment, but we had the Two column layout there. So now let's just go back over here and say let's not do manual. Let's do by category and by oil changes. Save refresh. And then now we have our two. Oil change coupons here.

Gavin Taylor: Okay, so question on this, the format of it. Because last week we talked about how we have three different patterns, I guess you would call it. That's exactly what we call it. I don't know why I said that. The different patterns, are we able to change that as well? So what my recommendation, multiple.

Chris LaFay: So what my recommendation would be is that rather than dealing with different patterns and trying to figure out which of those are. You always have a title here. So if it's like I know that you combine different oil changes together. So this is going to be the oil change coupon in the description we would format. This is where you would be like full synthetic. Wow. I don't know what I'm doing. I don't know what the frick I'm doing. 67 Traditional.

Gavin Taylor: Yep.

Chris LaFay: 89, Etc. Etc. Now one thing I did not take into account is if you, here's where you could put in like if you're doing different pricing, you could use to do/89. And let's go over here. Let's delete this. And then update. No, this is, this is bothering me. This is really bothering me. Synthetic. So we can discuss more in detail. Like what's the best way to do that. But I always go for the simplest field set and then work within the confines of the simplest field set rather than. Because if you create different field groupings for different layouts, you're going to be, you're going to get confused on which ones, which ones, which one. So I would rather come up. I'd rather use this as a base and be like now that we see what that is, how could we morph this into something appropriate?

Gavin Taylor: So does that same thing affect the emails as well? The email coupon?

Chris LaFay: So I, I can't send email from my local computer out. So I haven't tested that.

Gavin Taylor: No, I get that.

Chris LaFay: But what this will do and what this is. The last part I wanted to show you is locations. So we had this. There's not really a lot of information here yet. These could eventually be your actual location pages. Like when you edit this right now it's just metadata. This could actually be a full blown page build so that if you go to a locations page, you could drag and drop blocks on it as well. As well as having this custom data went ahead and plugged all this stuff in here as well too. And then we have our email routing. There's the GM email, the admin email and then the system API email. Now the reason I show you all this is what it will. What this does is when you click on email coupon at the bottom it says select Location Loganville, Snowville. Now if I go over here to locations and let's say that I go ahead and delete Loganville. Refresh. There is no local. It just. It defaults to the one that you already have.

Gavin Taylor: So it has the inherent logic in there that will look okay.

Chris LaFay: So the, the nice thing about this, the same thing you could apply. I forgot the, I forgot the exact site that we looked at. But there was like the multi location stuff over here that could end up becoming a custom block that's called like header header cta. That is the combination of schedule and the phone call button. And if you're on a page that's not a specific location, it'll showcase both. It'll. It'll loop through the locations, showcase their hours of operation with a button that then triggers a modal that has multiple locations at your disposal. Or if you end up being on a single location page, it would know that and it would only show the. The schedule online link when it prompted a modal box would only show the iframe for that location. And that actually could just switch to this. Basically like if you're on the Snowville location schedule could just because all of that data is right here. I mean it's not literally right here, but it could be right here.

Gavin Taylor: So conflict questions really quick. I'm looking at this because I know in the long run and Craig is very hesitant on an acf. I don't know why. I don't think he even knows either. The old developer just says pounded his head, hey, this is not what we need to do.

Chris LaFay: ACF doesn't add any bloat. It's all back end.

Gavin Taylor: And that's what I'm thinking too. I understand code enough where I understand what this is doing in the back end. But that's also why I'm thinking could this cause any conflicts? Because I know you mentioned you want to get to a point where we have basically a whole settings page where we have things so colors, fonts, everything like that. If multiple settings pages are calling on certain blocks within the site, do you think there's going to be conflict? So for example, right here, what you just said in the header call to action block, we would have logic whether it's one location or multiple locations. We're going to have calls from the settings page for the formatting.

Chris LaFay: I'm listening, I'm listening.

Gavin Taylor: And also FY, I'm pushing away from SiteGround as fast as possible.

Chris LaFay: So can I. Can I interrupt you really quick because I know the draw, I know the direction you're going this question. So I don't know about SiteGround, but I do know about WP Engine. WP Engine does something called page level caching. Now, do I understand all the intricate details of it? No, I don't.

Gavin Taylor: But what I docket, that does that too. That's one of the big reasons.

Chris LaFay: It basically just saves the HTML when you go to a page for the first time, it saves away the HTML output so you don't have to go. Do all those database calls.

Gavin Taylor: Okay,.

Chris LaFay: I can't answer for it on SiteGround, but yeah, technically speaking, you're not wrong. If this will. If this whole thing over, this whole thing over here was doing database calls of like, is this a location page, yes or no? And then display different HTML based on it. Yes, all it does, it does take time, but once that page's HTML is cached, you're good. It doesn't matter anymore.

Gavin Taylor: Which is another thing that we're thinking about doing is going over to Astro and with that we might do, I think it's called Headless WordPress. Basically we use WordPress still, but use Astro as the page. And for what I understand about it, how it works is we would upload the file so WordPress creates the entire file for the site and then you would put it into Astro. And that's more. It's a static page at that point, so it loads extremely fast.

Chris LaFay: So I don't know how Astro works with headless WordPress. The one thing I will say that research should be done on is. So what the. What I do know about headless WordPress and it's coming from a element standpoint, the thing is, I haven't done research on this in probably about a year or two, and a lot has changed in the last year or two is in order to do headless WordPress, you had to build your theme in a very different way, rather than building it with. And this is, this is slightly old school talking here, but you had to build it like with not. Whereas before you built it with. Actually about five years ago, you built. It with PHP files that served up templates. Now, over the Last few years, WordPress has the full site editing suite. A lot of these PHP files have converted to HTML files for templates and this, that and the other. At the end of the day, you're actually. The theme that you build is not just HTML and CSS. You actually build it with like a JavaScript front end basically, and then you call the APIs. It's a very. It's a very different mindset. Now what I don't know and where I'm speaking a little bit out of my. My wheelhouse with this in particular is I'm sure there are some systems and Astro might be one of them. I don't know where you actually do have a WordPress site over here that's built in the standard WordPressy way, the normal way, but Astro just goes and grabs HTML files basically flat your entire website and just shoves all these HTML files flat on a certainly Astro server somewhere. I don't know how Astro works. So I was a challenge because I.

Gavin Taylor: Haven't gone too far into that. I just. So I had a meeting with Craig yesterday and he's pushing more towards that. One of the reasons is because he mentioned something about Cloudflare, how we're not being prioritized. So our page speed is going up and down all the time. And with Rocket.net we're going to get rid of that. And with Astro, it's going to be damn near 100 speed. It's going to be 100% when you go and look at page speed because it's pulling between Rocket.net and Astra. It's pulling directly from the page each time and doesn't go back until you re upload the files where.

Chris LaFay: So do you actually host the entire WordPress site on Astro?

Gavin Taylor: It's more or less converted into Astro. Yeah.

Chris LaFay: So Astro. Okay.

Gavin Taylor: Yeah. And I think that's where we've been playing with Claude a lot more. You got me in that rabbit hole. So how do you think I built.

Chris LaFay: This plugin so quickly?

Gavin Taylor: Like I took that it's going to work is we're going to take all the site files, tell Claude like, hey, I want you to convert this in the Astro site.

Chris LaFay: So are you converting it to an as, like the Astro cms or you or you can. Or are you converting it to a headless WordPress site?

Gavin Taylor: Hold on. We're not 100% sure just yet. 1.

Chris LaFay: So this is the. Oh, sorry,.

Gavin Taylor: Sorry, mom slowed down. Okay, so I haven't put my own time into looking at this. So I'm just spewing what I'm hearing from Craig and I might be playing that telephone Game, but we don't exactly know yet. I think it's either or either we're going to convert it into Astro fully or you headless WordPress.

Chris LaFay: So the one thing I would be. So I don't know how Astro works first off, two, if you're planning on taking your entire theme and basically having Claude go through it and convert it to Headless, that in and of itself is going to be very dangerous to do. Because you need a developer to do that.

Gavin Taylor: Yep.

Chris LaFay: Because they're like, for example, building out like I built this little, this coupons, this little mini plugin all with AI, but I built it with a knowledge base of how to build advanced custom fields, custom blocks, custom post types, etc. Reviewed everything. It messed up like six times while I did it. But it appeared correct. That's the thing. And so there were things that it did that seemed right on the front end but were really bad on the back end. And so we're definitely gonna have the.

Gavin Taylor: Developer like do it. Okay. But I know they're probably gonna do it with that Claude.

Chris LaFay: Yeah. Which is, I mean you, you, you should so.

Gavin Taylor: But I also been playing with the Claude. What is it called? Claude and Chrome. And I was just seeing the limits of it. I tested one of our sites because one of the things that we've been finding is the sites have been referring to the old template that we used is based off a client of ours called G and G. The code of the site still refers to it even though on the front end of the site it doesn't say anything about G and G. So I had Claude and Chrome like scan the site and it found stuff that I never would have found, which I thought was really, really cool.

Chris LaFay: Yeah, I actually, I put together, I put together a proposal for a client. Yeah. Two days ago. And I was having to do research from. It was a government agency. And like one of the last lines was like, hey, by the way, this government agency has an entire design system that they are required to use by the state, so you should include this in your like design style and structure. And I clicked and looked at. I was like, holy crap, they do. I would never have known this before. And Claude was able to find it. I'm like, this is, this is not incredible. Absolutely nuts.

Gavin Taylor: Can you do this for me? Can you record like a 5 minute loom or 10 minute loom, however much, and almost pitch this in a way of like the features, how it benefits us. Everything that I can send to Craig, basically an executive breakdown. Keeping in mind that hey, speed is top priority. This is why ACF works here and this is why it's not going to slow down the site. And that way I can share with him like a brief thing, not share this whole call with him and have you kind of sell him on it in a way. Because I love this, the, the coupon thing. I think this is going to help us tremendously, especially when we build out the full thing with the emails, with everything and we don't have to make all the different patterns and stuff. I think this is going to be so much easier.

Chris LaFay: What you could do also with this is let's say like this. So you're talking about layouts and I know when we're talking about layouts where you're talking about kind of the insides of it. So what I would recommend is at the block level have another drop down menu for basically like what is the,. Like the style of it. So the style of this one is kind of like the dashed lines right with the header text here. So if you wanted to have a couple of different styles to where maybe one of them the title of its large. Maybe another one where it looks like it's like the little ticket punch out and stuff like that, that's all CSS at the end of the day you could have on the block when you drag it in a drop down menu of the. The style of a single coupon. Yeah. And then all of them kind of. Absorb that style. And all it's doing would just be applying a CSS class at. On each coupon to make it. You know, one of them has the dashboard, one of them doesn't like.

Gavin Taylor: I honestly think we don't need to do that anymore. I think that was overkill. I think more times than this it's going to just be this dash thing and then if we need to change it, our developer can throw CSS in. I'm not worried about that.

Chris LaFay: And that's why I built it very simply is you have the basic components. You can make this title tag whatever the fricking heck you wanted it to look like in code without changing the actual block code. You just edit the theme and do whatever you want to with.

Gavin Taylor: So okay, yeah, let's do that then. Let's do that. Like 10 minute loom. I'll send it over to him and he can pick it apart however he wants. I'll come to you with questions next week and we'll go from there.

Chris LaFay: Now the question is he going to be. There's going to be something like I'm going to go back and like change like this. Basically there's hard coding in this, in this theme where all H3 tags are have a default dark color. They don't absorb. Is he gonna be, is he gonna be annoyed by like the paddings here slightly like this left and right pattern?

Gavin Taylor: No, just, just mentioned like, hey, this is super early stages. I don't want to go build something out. I just wanted to show you an option and he don't understand that it's like very skeletal, very foundational.

Chris LaFay: Okay, cool. I just want to make sure that that's the case. Some people are visual people and they just cannot, they cannot break away from their.

Gavin Taylor: I did not know you could change code with inspect.

Chris LaFay: Oh, this the whole point of inspector, bro. Yeah, yeah, you click this little, little dude out over here, little, little selector thing, you just go in here and just be like, plop.

Gavin Taylor: I thought you could just like find code.

Chris LaFay: No, no, you can just type in like that. Like boom. You can move stuff around too. It's like, oh, what would this look like if the price was above it? Boom. Now it's obviously not saving any of this. Yeah, you re like, I made the text wide and I bumped up the font size. Like if I refresh it, boink, it's back down. But you know, yeah, it is. Literally that is the whole point of the inspector is to type in stuff and test things out and then go back over to code and be like, all right, now I know what I'm doing.

Gavin Taylor: So it's kind of funny. My father, my ex father in law gave me this URL thing. There's okay, past life, I was young, extremely broken, but basically on your phone, like you could throw this URL in on the browser and then you could change certain elements and stores used to, you could just show them like, hey, this website says that the price is this and they would price match it. So when I had my son, I would go in and throw diapers and price match at a lower cost. It was screwed up, but I'm pretty sure that's how that worked. Yeah, it was so bad sites and like, hey, it's 10 bucks for a case of diapers and Walmart's like, oh, yeah. Okay. Keep in mind this is a long time ago.

Chris LaFay: These large disclaimers over this.

Gavin Taylor: Yeah, that, that ended pretty quick. I think they caught on to stuff like that.

Chris LaFay: I mean, I think now in order to do price match, they basically have to be able to pull it up themselves, like go to Amazon, type this thing in and show it basically. Which, which totally is what you should do, but. Oh man, that's, that's hysterical.

Gavin Taylor: I've saved so much money on deposits and it was okay. In my defense, it was only Walmart and I don't think Walmart's missing that $5 or whatever it was. It wasn't like we're putting in free diapers or anything.

Chris LaFay: I find it this, this is true on multiple levels and in multiple different facets of life. It is interesting to me how we can, as humans justify our actions based on something not being perceived. Like it's just Walmart.

Gavin Taylor: It's just Walmart.

Chris LaFay: It's just Walmart. They're a big mega company. It's only $10. It's only X. Like it's the, it's the, it's the phrase. It's only fill in the blank.

Gavin Taylor: No, I get it.

Chris LaFay: Because that isn't perceived. Because it's. Because the, the, the lie, the cheating, the whatever it is feeling, which is the feeling. It's not. Nothing is felt like nothing is really felt by the receiving party. It's okay. And we, we all do this across the board and not, you know, not lying about coupon prices. That's not what I'm saying. But like in general, like everybody does it to some degree. And it's just, it's interesting where people.

Gavin Taylor: It's a problem with corporations because once a company is a corporation, that individual is taken out of it, even though there's a CEO, board of directors, whatever the individual peoples pull out of it. And now you're looking at it as corporation, not individual. And that I think is what does that most.

Chris LaFay: Man, this is. Humans are interesting. At the end of the day, humans are very, very interesting creatures. Okay, sorry, go ahead.

Gavin Taylor: And so that was before I ever got in business and understood anything. I was a young dump kid. But.

Chris LaFay: So with this, I'm going to assume I'm gonna basically lead off the video with one of the pain points Gavin and I have talked about is coupon management and that it takes an absurd amount of time on a side by side basis to manage coupons. And he was walking me through how this was done and my thinking was there's a much better way to do this and all the conversations I've had with him. There's also a better way to do some more of this as well too. So I'm kind of laying the foundation there. That's kind of how I'm envisioning kicking off the, the video. Does that feel good?

Gavin Taylor: Yep, that's fine. And oh no, you don't have to mention it, but just say yeah, we talked about your hesitation on ACF and this is why it works, this is why it doesn't cause issues, blah blah, blah. And you acknowledging his view on the ACF thing because I don't think he even knows because he's like me. He knows enough about the code of the site where it's like, okay, yeah, I kind of get what's going on in the back end. But he's very much a marketer too, not a developer. No, he was fed a lot of info from our old developer.

Chris LaFay: Are you doing page level caching right now?

Gavin Taylor: No, no, that's the problem. Okay.

Chris LaFay: Yeah, that'll be solved by pretty much. Any other hosting company.

Gavin Taylor: So Rocket.net is probably going to be the biggest change. We he has done a lot of work in how things are cash, what's being excluded, what's this, that and the other. And it's definitely gotten better. But Rocket.net is really cool.

Chris LaFay: Wait, so are you guys. Are you guys going to rocket.net or are you doing Astro right now?

Gavin Taylor: We're doing Rocket on that. So Rocket.net is the hosting. I want to say. Yeah, Rocket.net is a hosting so it'll still be on WordPress for now. And Rocket.net I switch over a site that we were having trouble with page speed just by switching it. It went from 60 like mid-60s to mid-90s on performance.

Chris LaFay: That's tells you have a good host. I'm just not a big fan of SiteGround. SiteGround. I haven't hosted a site as iground a very, very, very long time. I just don't like it. I've never heard of this. I cannot speak to anything about this at all. I'm trying to see does. Do you know if rocket Net does page level cap? Do you know if they do?

Gavin Taylor: They do. They do.

Chris LaFay: Fantastic. Then I'll, then I'll.

Gavin Taylor: I'll talk and then you get priority to. I don't remember how the all of it works, but it's much, much better. So you just said it on that last page. 98% Of traffic will be cast.

Chris LaFay: There you go. Backup retention 14 days. They don't show the back end of this as well. Interesting. What also bothers me about a lot of software hosting companies. Whatever. Like this is not like an actual screenshot of your back end. Like show me what your back end actually looks like. You don't need to show it to me. It doesn't matter. Like this, this is not a screenshot of your backend. That's just a graph. Like, I don't even know what these things mean. Like that. Actually, this all looks fake. These things drive me nuts because I'm.

Gavin Taylor: Like, better for people like me where it's like, oh, that looks good, but.

Chris LaFay: Then you buy it, and it looks different on the back end than it does. Like, the thing that you got sold is different than the. The thing that you got marketed about is the. Is different than the thing you got sold. That's. That's my core problem with it, is I don't feel like I know what I'm getting until I buy in. That's my problem.

Gavin Taylor: But I do like this.

Chris LaFay: This chart.

Gavin Taylor: It's close enough. Let me share this. I know.

Chris LaFay: Oh, it doesn't matter. We're going down. We're going down. A rabbit trailer.

Gavin Taylor: It's one of those things that I do want to show you because it's really cool. What the hell? Why did he turn on two Factor? The backend does look simple enough where. I don't know why. It's. Oh, it's something. No, I'm not doing that. It's the Authenticator app. I don't want to do that. Never mind. But my whole point was the backend is simple enough where it does not, like, throw you off at all. Okay, so, yeah, the takeaway from that, we're going to record a loom. I'm gonna send it over to him. That way we don't play the telephone game on that. He sees the benefits. You can pull it apart himself, Send me over questions I can ask you, or he can hop on the call next week. Okay, so next order of business, let's go over the Q A sheet that I built out. Oh, I could actually show you something else, too. Okay, there's one more thing I want to do.

Chris LaFay: Have you tested my. Have you tested the. The image thing yet? The image cloud code thing? The image organizer?

Gavin Taylor: No. You know what's funny is I have those emails right here.

Chris LaFay: They're the last ones in your list. That means they're important and you don't want to forget. I, I, I. I'm the same. I'm the same.

Gavin Taylor: It's like, okay, I'm gonna get back to these. I'm gonna get rid of all my other emails. It's the only ones in here. I do the net zero thing. So at the end of the day, I try to complete get rid of all these emails. And then I did that. I'm like, okay, I'm gonna, I'm gonna look at that. And then someone else comes up and.

Chris LaFay: I need somebody to sit with me before I finish up my day for like the last hour and be like, all right, Chris, it's time to clean up your day.

Gavin Taylor: Now.

Chris LaFay: We're gonna sit here together and we're gonna clean it up and make it all nice and good. So when you come in tomorrow, you're happy.

Gavin Taylor: No, you know what? I do? I say myself, like you didn't do today. If you leave, if you leave work and those emails are tasks, you are a pos. And like, yeah, I shame myself for the works. Okay, this is basically the fulfillment launch packet. You do have access to that other sheet, so you should be able to see this. But I'm on. It's a basic. Okay, here's the business info. Here's the template and hosting that we're going to be using. I'll link it. I'm going to link the page, structure the photos, whatever the case may be, the coupons that we need. Now this will work with. Right now I have our coupon process, but this will work with yours too. Where my assistant. We might just assign this to my assistant and she goes and does it either way. Hey, here's the coupons. It'll be a link document. This is what needs to add into the site. And then are they using octoberocket? That's where that text only email will come from. And then all that stuff, I have all the API stuff. The checklist. Oh, the checklist is the QA checklist. So this is where I want to spend some time. Out of everything we talked about, I did this on a global level. But I think this is so detailed that it will apply at the page level. Right. So pages indexing, all pages are present. Pages excluding PPC pages are set to index. PPC pages are set to index. And obviously during the URL structure, they'll know which ones are which. No 404 issues pages are responsive across all devices. All pages load proper. Now, try not to be as I already know the word for that. I don't either. Okay, so I made sure to clarify what that means. Like no broken layouts, missing sections of.

Chris LaFay: Functional issues, navigation, something so something so something to note here. If this is going to be the checklist. Global things like this that say all pages loaded properly. Those are things that humans are just gonna be like, yep, I built the page. I remember it loaded properly. Check and be done. So like you're. You. You're going to have to tread a line here no matter what. Because I know you don't want to have a 10,000 check, like a 10,000 item checklist. I realize that I but me as a developer who has developed in the past and not everybody is my personality type, don't get me wrong. I also know that. But if I built it and I remember it being good and there's a generic checkbox like that, I'm just gonna. Check that sucker off.

Gavin Taylor: Yep. Which we have a filter for. So how the process is gonna work, and I know you're gonna hate this because it's not a one person thing, but how the process is gonna work. Our dev team has the QA process that they go through and internally for them, they have someone other than the developer actually check it. Should. Should check it. Then once they deliver to us, it tags my assistant. My assistants go run through this checklist really quick. That again, she might do the same thing. She might. If it's a 200 page website, she might miss something. So then it goes to me because by the time I look at it, I know it's already been through multiple eyes and I'm able to go through those pages. And now the academy, the accountability rolls downhill. I'll get with my assistant, like why isn't every page check? Then I'll get to the developer. Why is every page? And I feel like after a couple yes, things will slip through, but that checkbox is going to be a little bit more. They're gonna have a second thought before they just click it. That. That's my thought anyway. We're gonna have multiple layers of filter to make sure that this is done properly and multiple sign offs to be able to go live.

Chris LaFay: So that my question is going to be two weeks.

Gavin Taylor: This will be done in two days.

Chris LaFay: Okay. Okay.

Gavin Taylor: The final.

Chris LaFay: I know I'm not. Yeah.

Gavin Taylor: The final sign off should be two days. One with developer assistant, one being myself and possibly Craig. That two week number, I don't know.

Chris LaFay: You only get to two weeks if you have a lot of this stuff legitimately automated.

Gavin Taylor: Yes. And what's going to be really cool is using Claude in this is going to be really helpful as well because I've already tested this out. I've uploaded this list to Claude. Hey, I want you to check this website. And then I uploaded like a screaming frog report to it as well. I'll run the report, upload that report, upload this list. I want you to scan this report, scan the website, make sure everything is correct. And it went through this list. And did it for me too. And that took like two seconds.

Chris LaFay: Now, are you using claude code, Are you using COD in the browser and you're uploading stuff to it or have you actually downloaded the app and it's actually working within files of your, of your computer?

Gavin Taylor: Both.

Chris LaFay: Okay. Have you started creating a repository of. Knowledge for your site?

Gavin Taylor: Not yet. That's not what it's starting. We actually just as a team, we just set up a team meeting for the next four weeks to start that repository.

Chris LaFay: Would it be helpful for me to show you how I've organized some of my stuff as a starting point? Yeah. Do you want me to do that now or do you want to do that later?

Gavin Taylor: I want you to do that later. If you just. I know I hate doing the. Having you do videos, but if you could. That I can show with the team, that would be really helpful too.

Chris LaFay: So mine's going to be very business owner centric with a little bit of dev in there. But I think even seeing it will spark ideas because for me, when I started doing this I had a bazillion ideas and started creating stuff and I wasted hours and then when I saw working things I was like, oh, I could take a little bit from here and a little bit from here and a little bit from here. And now what I have is a lot more well rounded and actually it's. Helpful to me now. Whereas before it was noise.

Gavin Taylor: The team meeting that I'm talking about, it's just gonna be myself, Natalie, Craig and Dan, which obviously I oversee all of fulfillment. Dan oversees client success. Natalie Su's operations as a whole. So it, it's high level enough where we're all going to be able to utilize it.

Chris LaFay: Good.

Gavin Taylor: I would like you to run through this. I know your opinion on the global but I don't know each and every page until we go through strategies. So I'm not entirely sure how we build out like a page by page checklist. And I think this covers our basis. Like for example, coupons. The coupons are centralized. So if one page works, it should all work. The call to action. The. The call to actions are very similar. The call rail, if it was uploaded right. It will work across the site. So all this I think will work. I'd like it if you take a look at this as well. Just like a five minute overview. Yeah, this, this looks good. And leave notes where you think I should change it.

Chris LaFay: My gut just glancing at this, this is probably okay. I'm not trying to like, I'm not. Well, no, you have like all the technical pieces of like script things like call rail and so like you have all, all the stuff that you've listed out here. Looks like it's all the same stuff. That we talked about before. And then two at the page level. I know it's not page level, but the page kind of QA stuff of like content QA testing, making, like doing different responsive breakpoints, consistency with phone numbers and logos and blah, blah. All of that's here. I, I think you've gotten this to at least 85%. I don't, I don't think. I think you use this, test it and then what if it works and it's good, great. If you notice something's missing when you do it, edit it.

Gavin Taylor: Perfect.

Chris LaFay: But I would just, I would ship this and call this done.

Gavin Taylor: Okay.

Chris LaFay: Now trying, not trying to get out of like doing stuff later this way. That's not my point. It's. I think this is fine.

Gavin Taylor: That works for me.

Chris LaFay: I have a problem with closing the loop on my own things and trying to get stuff from 80 to 100% and that's where I waste most of my time. But I'm really good about calling it out to other people, so I'm definitely the pot calling the kettle black.

Gavin Taylor: Anyway, that works. Let me just. I know I made changes and then. I have this in two places, which is freaking crazy. I don't know why I did that.

Chris LaFay: But by the way, I know you have a hard stop in about five minutes, just.

Gavin Taylor: Yes, I do. Okay. So yeah, that's kind of where I'm at. This is, this is kind of the final thing. I don't know how to write this one. Should I. For the handoff to developers, I have an old sheet that basically has a couple pages of do's and don'ts. Very simple stuff like don't resort to plugins. That cannot be our default. Things like that. We're trying to cut some code what we can, blah, blah, blah. As far as all these other sections, I will, I guess just make like a paragraph. I don't expect every developer to really search through this too much, but do you think it'd be better to like for example, for the QA checklist, obviously this is going to be showing them like, hey, all of this needs to be done. I don't want to give them like a step by step, hey, this is how you build our sites for us. So I just want your opinion on if someone were to white label to you and they wanted you follow the standards, what is the best way to communicate those standards. Is it just a list of, hey, here's how this tool works? Whatever. How, how would you recommend that?

Chris LaFay: What I'm going to do, what I'm going to start off with is I have a whole project now within CLAUDE code for everything that we've talked about and all the processes, all the SOPs, everything in conjunction with a lot of my own documentation as well too, about. Just how I do stuff. So what I'm going to do, I actually literally just prompted it of write me up a markdown file of what a good development standards document should look like. So I'm going to take that and the contents of this, like the QA document, because I don't have that QA document in here yet. Because if you have a standard, the standard should kind of align up with the QA document, not one to one. That's not what I'm saying. But it should be a very easy line to draw that if they follow the standards, the QA document should be a breeze. So I'm gonna run through that and get a general idea to start with because I know what you're trying, I know what you're saying, and I understand, I. I understand like the. How do you write up a document that you know not everybody is going to read, but you want it to be detailed enough so that you want to be vague enough so that people actually do read it and don't get overwhelmed by it, but you want it detailed enough to where you can call crap if somebody messes something up. So I get the, I get the.

Gavin Taylor: Pull there, the thing that I struggle with, with the dev.

Chris LaFay: And so. I have thoughts and ideas of what I would do for my like actually. So the way that I'm looking at this is like I have a developer that I'm about to onboard, so how am I. And I've. I've changed a lot of my own processes over the last two to three months. So how do I actually give that dude documentation who's never worked with me before on here are my standards. So this is well time because I'm actually thinking through the same thing now, obviously your process and my process vastly different, but it's the same core. You're trying to solve the same problem.

Gavin Taylor: So, yeah, myself, because I know that that is something I will want to integrate to this. I'd love to share it with you before beforehand.

Chris LaFay: Wrong one. Sorry, talking to myself. Apologies.

Gavin Taylor: It applied to mine too. God.

Chris LaFay: Okay,. Local jungle.

Gavin Taylor: There we go.

Chris LaFay: All right, Dev standards, how does this actually look? No,. I Got my repository too. I got my repository too. Technical. That sucks. Oh, well, that's fine. My Claude bot got into the weeds of my new. The new like local jungle plugin with all like the automations built in with acf. And it was like, as a developer, you should look to automate everything. You should automate, like you should build this. I'm like that. All right, you're. You're not wrong. That is my. That is my leaning. But that's not. That's not what I'm going for here. So like that. That did not help at all.

Gavin Taylor: Okay, well, I will find the document I'm looking for. Again, there's. I've been trying to go through and organize the absolute garbage of a Google Drive that we have. Okay, I'll get you that or I'll integrate it with what you send me. But again, it's just the very standard, hey, here's, here's the do's and don'ts, mega food plugins, etc. Etc. So excuse me, I will look for that. But yeah, I will look for your video. Get that over to Craig. Well, videos. I'll get that over to Craig. We have our first meeting I think on Friday morning. So if you could get me the video about your depository before then, that would be great.

Chris LaFay: Oh yeah, I'm leaving tomorrow morning at like 6am so you gonna get it today?

Gavin Taylor: Today, Perfect.

Chris LaFay: Yeah, there ain't no question about that. Awesome. Dope. Sounds good. I'll get it sent over. If you have any. I'm gonna. If you have any edits to the video, do let me know. I will try to reshoot it. I will have time Wednesday and Thursday. I will just not be in my normal setup. I'll be at a coffee shop in New York City. So it won't be as. Won't be as buttoned up and professional as I normally am.

Gavin Taylor: So what are you going to New York for?

Chris LaFay: I'm hosting an agency. I'm hosting an agency hangout with a buddy of mine. And so we both. Oh, I realized I get all my business from agency partners. And I was like, you know what I'm gonna do? I'm not gonna try to like grow and scale this thing massively and like define an ideal client and only hang out with CMOs and VPs and marketing. Like, I'm just gonna go hang out with agency people and I'm just gonna let my business just grow slowly but surely because I'm like, I have maybe like five really good agency partners that send work Over I. There's no reason for me not to have like 30 so why not? I built literally my entire business off of it, my entire life. So why not try to be intentional about it?

Gavin Taylor: So hey, if you ever want help with ads, let me know. That's my specialty.

Chris LaFay: Do you do side work?

Gavin Taylor: I have my own agency too.

Chris LaFay: Did not know that. I actually, for the amount that you and I talk, I've actually done the least amount of research on like what you've done in the past. Like look at your LinkedIn and all that kind of fun stuff and blah blah.

Gavin Taylor: I. I have another meeting but I have been a paid media specialist for the last few 15 years. So I do Google, Facebook, TikTok. I do it all the strategy and execution on it. That's kind of my specialty where the, the technical like integrations I always do on developers. But I really go full scale to full attribution on the marketing campaigns that I do. So that way we know down to the click where people come from. Is it first attribution? That's attribution, et cetera, et cetera. I've done some really, really big projects. On average I manage seven plus figures a month on ad spend.

Chris LaFay: Learn something.

Gavin Taylor: That's my claim to fame. The, the, my day to day it's. I like building, I like helping agencies build things. So I've jumped, I've jumped a lot. Just help agencies kind of get off the ground and scale to that seven figure mark and then they decide, oh hey, we don't need Gavin anymore. I'm like, okay, do you too? That's kind of the cycle that happens.

Chris LaFay: It's the joy of working with small agencies, man. You get to do a lot of interesting stuff. You get to play in a lot of different sandboxes. Now you have to also deal with a founder that's probably bouncing around like a pinball. Like don't get me wrong, fully understand it. We get to try a lot of.

Gavin Taylor: Things and I learn a lot by doing this over and over and over again. This is the seventh agency, I will say this is the first agency that I believe is over that seven figure of revenue mark that I came on after the seven figures. But it's so.

Chris LaFay: Small.

Gavin Taylor: Relatively that we are taking it back to like that building stage that I really enjoy. But yeah, the, the paid marketing and campaign management, that's where my specialty lies.

Chris LaFay: Interesting. Also, I'm curious, I'm curious, how much does local jungle charge per month for what they for like these like big packages of all the things that they.

Gavin Taylor: Do this would drive you insane and this is something that I haven't completely wrapped my head around. There's no fixed price and it's not that there's no fixed price is that hey, you are spending $20,000 a month in advertising instead of paying your agency managing all that. Give us the $20,000 a month, we will take that, spend it where we need to and we'll get you better results. So we know, we are so confident that we can get better results that hey, if we spend 10,000 but increase the results by 1015, we made $10,000 on it. If we have to spend the full amount to get better results, well, we kind of watch out on that client. But more times than not we know that we can increase the results enough where that's how we make the money.

Chris LaFay: So interesting. It's past 10:30. I'm sorry, my bad.

Gavin Taylor: We'll talk later. Thank you.

Chris LaFay: Audios.