88 Acres - Sales

Sa. I never set up my meetings to have waiting rooms. I just let. Let people join my. So mine is when I create them, it said to have waiting rooms mainly because I want to make sure that I have all my crap together. So I. When I created under your name, more than likely it absorbed that. By the way, the person. So two people. Luke Jarvis is the, like, performance marketing person. I did not talk to him, but she was the one who she references. Like, he's the person that knows a lot of more of the technical stuff than I do. Lynn is the person that I chatted with. Got it. And Lynn is just there, like, marketing person. I will probably bow out after about 30 minutes or so, and I will make that known ahead of time. I'm just going to let them know that I'm going out of town tomorrow. And I put this in. It's important for me to join, but I just won't be able to stay the whole time. Got it. And they're. They're looking at byob, but their main focus is potentially. Should they upgrade their theme? Yes. What will they. What will they get from it? I didn't speak too specifically about it last week, and they're heavy on B2B, not B2C. Right. As far as the web sales, that I don't know. All I know is that the majority of their income comes from brick and mortar. So, yeah, got it. I know nothing about how they do fulfillment. Did they find us through the Magic Zone case study? I think so. I asked how they found us, and they said Magic Spoon, but it wasn't. Magic Spoon themselves did not make a recommendation because I asked here about that on Monday. Could be Stay AI making the recommendation then. And so I dropped in. While we were talking about byob, I was like, I know we built it with Stay AI. And I kind of paused there to see if she would grab on to, like, that, and she did not. So which that still could be the case. Well, looking at their PDP page, I don't see a way to subscribe, which is what Stay I does. Thrives with. Bingo. I mean, honestly, subscriptions is Magic Spoon's biggest piece of revenue driving on their website. Mm. But they do have a managed subscription, but it's not on the PDP page. That's weird. All right, we got people. Got Luke. Foreign. Luke. How are you doing today, sir? How's it going? It has been. It has been a day. My wife and I are traveling early tomorrow, and the Atlanta airport is in absolute shambles at the moment with so Many people. So today has been a. Get stuff done and leave as early as humanly possible. Tomorrow morning is the plan. So are you going anywhere fun? We are actually. We're going to. So we're. We're in Georgia and one of my good friends lives out in Arizona, and so we're gonna go spend the week with him and his family and just kick back and relax and enjoy some good conversation. So. Very relaxing way to. To end a couple of hectic weeks, needless to say. So awesome. How about you? You up to anything out of the ordinary? Not really. We're up near Boston and we're just coming out of. Coming out of winter, so the snow is melted and. Yeah. But otherwise pretty standard. There you go. Very nice. Now, are we. I know I tried it with Lynn last week. Are we gonna wait for her to join here? You did okay. There we go. That might have been her. There we go. Hi. Good morning. I'm sorry. You are all good. No worries. You. Were you up to anything exciting this weekend? What? Sorry? Were you up to anything exciting this weekend? We went skiing. How about you? Very nice. I was just telling Luke about the. We're about to get a prep to go to Arizona this coming week. So it's today and tomorrow. We're a little bit crammed, needless to say. So I'll probably. Actually, on that note, probably only be able to stay on this call for about 30 minutes, but I knew time was of the essence, so I wanted to at least make sure that I was here. I wanted to say, hey, this is important to me, but I know that this conversation is mostly going to revolve y' all and Andrew, so. Sounds good. Okay. Should we kick it off, Chris, or. I don't know if you, like, briefed Andrew on our conversation or how do you want to. I did brief Andrew on our conversation. Luke did. Luke, did you get a debrief on our conversation from last week as well, briefly? L and I have been chatting, so no, no worries. It was a brief conversation at that. And so our. So what we chat. What Lynn and I chatted about last week was a couple of small things. One was talking a little bit about building your own bundle and what that looked like under the magic spoon. Case study is kind of what brought some of that to the forefront. Also looking at what would a Shopify version 1 to version 2 upgrade look like and what would the benefits be from that? Like, is it. Yes, the site's dated, but is that. Is there going to be an roi? Whether that's an administrative time and flexibility or in direct like, you know, because of that flexibility will immediately be able to, you know, start up taking sales and start dumping in, you know, possible ads to pages and things along those lines. And so that's where we're getting out a little bit over my skis as I run the company. I'm not a Shopify e commerce expert and that's why I wanted to bring Andrew into the picture because that is his bread and butter. And so Andrew, I'll let you know. Introduce yourself. Yeah, so I'm Andrew. Worked with Chris for I don't know, 20 years or something like that. Been in E commerce and web for 20 years as well. Anything from small mom and pop shops and nonprofits up to, you know, 100 million dollar companies, government done it all kind of thing. So eight or nine years experience with Shopify, specifically 15 issues with Worth WordPress. So a lot of different CMSs, a lot of different platforms. I'm not really like siloed into any specific platform. I'm one of those engineers that can like touch anything and it'd not be a big deal kind of thing. But in recent years it definitely has been a lot heavier in Shopify just because so many people are using them and migrating to the Shopify platform in the last five, six years. So a lot of experience, a lot of experience with Shopify specifically e commerce, etc. As Chris said, manage the Magic Spoon website, the Build Drum bundle, all that kind of stuff. A lot of experience with the third party platforms as well with Shopify. So like think Rebuy, Stay, AI, all those other integrations. A lot of experience with that. A lot of experience upgrading from Shopify 1.0 to 2.0 and you know, working through does it make sense? So that's obviously what the conversation today will probably revolve around is what makes sense from a standpoint for y'. All. With that said, let's dive into yalls like internal setup, like how you currently manage your Shopify site, who does it? What kind of updates are you doing? Do you all have a dev team? What does that look like? You know, just that workflow. Yeah, so I can speak to that. So I run our E comm business over here at adiadacus, primarily DTC and Amazon. So just so you understand where I'm coming from, I'm like in the weeds on Shopify on the daily. So I'm glad we're approaching this from an ROI lens because that's really the way that we're looking at it. As well. The way we're set up right now, we have a pretty standard tech stack. Shopify Recharge for subscription, Klaviyo for email, and then a few other kind of third party apps. We do have a dev team, not in house that we work with. We honestly don't make changes to the website that often. That would require any sort of coding. We obviously are putting products in and out of stock and changing pricing, but we're not making any updates to the site structure or to any of the major pages that often. I guess that's the short answer. Does that answer what you're asking? Yeah. As far as third party integrations, do you all use any third party page builder like PageFly Builder IO, anything like that? Yeah, the only one we use is on our product pages and it's a mess. It's one of the reasons we wouldn't mind getting a site upgrade. Again, we don't make changes to the product pages that often. But the way that it's built, each product page has a theme built out in pagefly, which is crazy, but we don't really use Page Fly for anything else apart from product pages. Everything else is basically coded, coded into the theme. And I just want to make sure I'm crystal clear. When you say each product has its own Page fly, is it quite literally each individual product has its own template? Yeah. So when they designed the site, the they wanted specific colors and like logos and content for each product. And they meaning not us. Sorry, just be clear. Not under our leadership. Okay, continue. The agency you're working with at the time and. Yeah, so because they wanted such customized content and they didn't build it into the back end like it wasn't pulling from the back end, they decided to make them each on a template. How many years ago was this? Oh, three. We've been on the same. We've been on the same longer. I've been actually. It would have been longer. Yeah, I think it was like four or five. We've been, we've been on the same theme for something like eight or nine years. So it's again the site. This is why I'm interested to look at it from an ROI perspective because the site functions. So like one of my questions is if we took the site exactly as it is, front end wise and user experience and we just put it onto say like a dawn theme or one of the upgraded themes, what impact would we see? Like is it just site speed? Is it usability? Like what's the impact there? I guess that, that would be my first question. Yeah, great question. So. So I don't know what your current theme started as, but if it's eight or nine years old, that's definitely Shopify 1.0. No question. Yeah. In addition to that site speed, that's a tough one. So if you ask Shopify, Shopify will tout some number like 30 or 40% page speed increase by upgrading to 2.0. Okay, that's an inflated number in my personal experience. Yeah. If you go stock theme to stock theme, yeah, you probably could get 30 to 40%. But you know, nobody's using a stock theme. Right. I would say realistically speaking, what I see on average is probably like a 10 to 15% page speed increase. Okay. The bigger piece of that though, I would say is the accessibility side of things. That has changed a lot in the last five or six years. Newer themes are definitely a lot more up to date on WCAG standards for being compliant with accessibility. Okay. Have you all been sued yet? We have had some ambulance chasers nipping at our heels, but right now we just have accessibly layered on top which I don't like and apparently it's not even fully protect full protection. So we're okay for. I wouldn't say we're okay. We haven't. We don't have anyone trying to sue us right now. But I guess that is a potential. Okay. Yeah, that's why I definitely use the word yet. Because it's a matter of time. Unfortunately, any one of any size, especially E commerce, is a target of the ambulance chasing lawyers. There was a period of time where it kind of like fell off and they weren't filing as many lawsuits. But I've definitely seen it pick back up in the last like nine months. Again example, Magic spoons had like three in the last eight, nine months. So can I ask you a question that you probably shouldn't know the answer to? Or maybe you do. Do you know what the financial impact of that typically is? Is it like a $10,000 payout or 100,000? Like what do we. Yeah. So I will, I will give you an average across all the clients I work with. So this is not just a magic spoon number. So I can't get in trouble anywhere from 6 to $7,000 in the low end. And that's like bottom of the barrel up to about 20, maybe 25. And that's settling outside of court. Okay. General average is 10 to 15 though. Okay, that's helpful. So the assess accessibility side. Yes, I totally agree. They as a platform sell themselves as something they're not. It's not an all encompassing, like you can check it off and be done kind of thing is slapping a band aid on something that's broken and hoping the band aid fully takes care of everything, which it does not. Yeah. I'll also say that generally speaking, a good accessible website is actually a good usable UX website for regular users as well. Right, Right. So they go hand in hand. So really it's like if you build a great website, it's going to be accessible as well. So in regards to the theme though, so you'll get better accessibility, you'll get a little bit of a page increase. I definitely would not recommend page speed being the reason you upgrade. It's generally the ROI is just generally not there for that. Yeah. Going from 1.0 to 2.0, one of the big pieces that truthfully makes it like worthwhile is, is how you and your internal team are using the website. And the reason I say that is because with 1.0, as you know, like most of the websites hard coded, even Shopify, you know, the customizer is there, but you can only do so much with it in 1.0. Yeah. So if you're making a lot of content changes, adding pages, etc. You can use the customizer a lot better in 2.0. And, and generally speaking, if the theme is built properly, you don't need a third party page builder. It's not like a definitive rule, but generally speaking, you don't. In addition to that, by not having the page builders, the page weight of your pages is generally smaller because it doesn't add in all that fluff that the page builders add in. If you're not making a lot of changes to the website, you might not really see the benefit then because that's really where two shines. I don't know where the next area of return would be. I. I assume like conversion rate optimization. I mean it's not. Again, our site isn't terrible. People are converting on it, but there might be some like tweaks on the user experience that could help. Yeah. Do y' all do any crow currently? When we have time. Let me ask this, are y' all a small team? Yeah. Okay. Yeah, makes sense. Yeah. We're not doing it. We haven't been. We haven't done any true AB testing in a while. We've actually deliberately deprioritized our DTC business over the past year just because we're focusing on other areas. So yeah, that's the, the short answer. Got it. So there is a third option. We've done this with Magic Spoon. Magic Spoon, same thing. Their theme was built in like 2017 or 18 or 19, something like that. It's very old. It's a clunker for sure. Cost to upgrade, it doesn't make sense for them. So what we've actually done is we've piecemeal upgraded it so their theme as a whole is actually still a 1.0 theme. But we upgraded the main theme, liquid file to 2.0 and then we've selectively done certain pages templates. So like the PDP template, collection templates and that's it. Those are all 2.0. Everything else on the site still 10. So the main areas that customers touch from a conversion standpoint, they get the most traffic, et cetera. We upgraded those specific pages to 2.0 and what that did was it took a lot of the work off of us, the dev team having to make changes to those pages and essentially empowered the Mattress Moon marketing team to be able to use Shopify Customizer to add a new content block, smooth stuff around, that kind of stuff. So there's a way to do that. I don't think it's something that Shopify like recommends per se, but it is definitely doable. And it's in my opinion the more cost effective way because you're selectively targeting pages where you're actually seeing ROI and it's actually impacting your day to day business and how you actually are able to edit the website. Got it. Can I ask a question about that as being a not web person? So this might be a dumb question, but assuming that we wanted to add additional pages, then with that option, do they then like what if you have a. If you're operating on a site that's 1.0 and 2.0 blended, like, then what happens? Like, say we wanted to build out our content marketing because we're trying to drive SEO and we wanted to like enhance our blog content. But like it's not really like easy to mess around with on 1.0, then what happens? Do you just build a new section 2.0 and then update it or how does that work? Yeah, think of it like this. When we're upgrading a PDP page or collection page or blog post as an example, we're actually taking the template behind the scenes and converting it from 1.0 to 2.0. Let's say it's blog posts. As an example, if we upgrade the blog post template to a 2.0 template, then whenever you're creating new blog posts, you just select the right template on that blog post to use the 2.0 template so that you've got the upgraded 2.0 features, et cetera for that. In that specific instance, nothing would really change on our end because either way we're entering the content in like the HTML editor. Unless I'm wrong, you guys can correct me, but it would just be the case of once you've entered the content, you select a different template on the side from the dropdown and then it shows different on the website. But I think it's like a non web person. For example, when we've done that, it's like the text isn't formatted right or the image is in the wrong place, or we've had issues. And then Luke member, you were like, well, I can't fix that because of whatever or I don't because I'm not a web person. But remember we were having issues with like the font and the image and it was like the margins looked weird and it just was like looking really weird. So to me that's like, yeah, that's, that's just because the template is coded badly. So like the way it shows up on the website isn't correct. But if we created a new template, like they basically don't code the template to say if H1 like add this is what it should look like. It should have this much padding underneath. This is what paragraphs look like. So that when we entered into the HTML section, it should show up all correctly on the front end. But we went ahead and like changed our font and did things with code that was for like other font, if that makes sense. Okay. So that's why we were trying to jimmy rig the look and feel on the front end. In that instance. It would just be like, we could keep our current template and just fix that so that it didn't show up incorrectly, or we would develop a new one. Okay, so then be able to change things like the nav or whatever. So I'm thinking like in this world of I know you're giving us options and we'll figure out like, what does it cost for these and what makes sense. But like, like in the, like, Luke and I have talked about how we don't really like love the nav right now as far as. And we don't have a complicated, like we don't have a ton of pages on our site, but it's like product pages are like obviously like very, very important. And then we have kind of like everything else like nested under seed, I think it's called like seed co or something. And we wanna like. I guess I'm just trying to understand if there's opportunity to like rethink the structure. So the nav structure is not a dev change, that's something we can do. What they would do is update the look and feel basically of the nav and how things show up on it. But there's settings in the back end of Shopify where we would like nest things differently or change the title of the nav or whatever so that we could still do. On our end it's more like we would determine which pages we would upgrade that are more like high touch. Okay, okay, that makes sense. Yeah. So two ways to view it would be either high traffic or high value, which is usually overlap a little bit, but not always. I have a couple more questions we've been discussing. I'm sure you guys have get this question pretty often, but the role of AI in, in terms of building websites, it sounds like on the one end you can get a pretty like low end, easy functioning website built by AI, but that's not going to fit our purposes when on the other end it sounds like it is useful for say updating things in a page builder or something like that. Is that how. How is it, how's your experience been? Is that is what I'm. Does what I'm saying make sense or are you seeing it some, some other way? Yeah, that's sort of a tough one to answer at this point. I would say from our standpoint, from an engineering level, we actually can use a lot of AI to do a lot of building. I think the difference on our side though is because we really understand what's happening behind the scenes when something is spit out incorrect, we can look at the code and go, okay, we know exactly what it is. Whereas a non engineer is just going to keep prompting and getting probably something bad. Outside of code though, if from what I'm seeing currently low technical people are able to use it on like a very modular scale where they can do very small tasks and get pretty good results. So it's like if you wanted to build a page real quick, let's say in the Shopify customizer, using the WYSIWYG editor, you could use ChatGPT to spit out some really solid formatting for that that you can just copy and paste in content into the page builder and it be ADA compliant, it looked good, it functioned well, etc. Stuff like that. I think totally doable you could do that today. Got it. If I was to approach this from say the user checkout flow, I would want to look at like each stage of the flow, like homepage collection page, product page, and try to figure out where the sticking points are, trying to fix them. Do you guys have like a shorthand way of doing that or I guess, how would you approach it? Because I'm just trying to think up, you know, where the ROI would mainly come from, if that makes sense. Yeah. So usually that's done through Pro. Doing a lot of AB testing, session recording, reviewing Google Analytics data. There's not really like a surefire methodology to say like this is what you do to figure out what works. It's like a combination of testing, reviewing data, looking at sessions, finding those sticking points. Because depending on what the problem is, sometimes that issue will show in GA4 data, sometimes it won't, which is where the session recordings really comes in. Because there's sometimes you don't see a data, but you can see it on a screen recording. There's not an easy answer to that, unfortunately. It's a lot of data review. Okay. As a starting place, you could use GA4. You could build a go through the GA4 explore feature. And what is it called? It is. Give me just a second, I'll pull it up. There is a way to do a Explore report, but do it inversed. So you start from checkout and then it goes backwards. It is funnel exploration. Path exploration. Path exploration, yeah. So you use the default path exploration and then once that comes up, you can just go up and click Start over and that sets it as a blank template. And then on your starting node you're going to start from your checkout page and then work backwards. What that does is it shows you how people got the checkout. Got it. Okay, say we want to go kind of the whole hog and start completely from scratch. New template. What? What? I guess what are the resource requirements and how long do you think that would take for a site like ours? A great question. I would definitely want to get access to your Shopify admin to look and see what all the different integrations are. High level though, I would say using dawn or Horizon as your starter theme, it's the go to at this point. Horizon, obviously is the latest and greatest flavor of Shopify 2.0. Yeah, it's a little. The reason why I recommend one of those two themes is because Horizon is still a very green, immature theme. Dawn, obviously, even though it's technically not like actively supported by Shopify anymore. It's very mature. So you got to review the use cases of what y' all need versus which one makes sense. But use that as a starter theme. Take the same layout design you have now. No reason to change it. I think it looks great, works for your brand. Just take that, build it into the new template. Whatever integrations you'll have. Obviously I need to be integrated again. Ballpark though. I would say generally speaking, if you're doing redesign like that, where you're like shifting, it's. I'm gonna throw a really wide number out here obviously, but somewhere between 15, 20,000 on the low end and then I mean you, you could technically go. The sky's the limit. But I would say on average 15, 20 to probably 30 is where you're generally probably at. Okay. And once we can see some of the integrations that you guys have, we'll be able to give you a very specific number and a very specific timeline. Okay. A lot of it just has to do with the integration piece. Yeah, definitely. Is it like a month or like 5 months? Probably around the 2 month timeline, give or take. Because we're not doing normally. We kind of start with a three month time frame for pretty much all website builds and we kind of adjust from there. Given that we're not going to be doing any major design, we take that three months and we reduce that down to about two. Then thinking about integrations and different 301 redirects that have to happen or any of those types of things, that might increase it a little bit. But I would say that a safe bet is between two and three months. Okay, question about, like, I know again you have to like go in and check on the back end, but you're like blended option that you were like, we could do this, but maybe not recommended, but you know, the upgrading some pages, like given our where we are and that we don't make like a ton of updates and anything we'd be looking to update is really to like product pages or probably blog or content to drive SEO. Do you think that would be an option we should be considering as well? So you don't have to give me like dollar numbers, but percentage wise, how much of your business would you like roughly say would. Would be through your website dsc. So I think ecom between DTC and Amazon is something like 30% and then DTC is probably about a third of that. So. So based on, yeah, based on that really high level recommendation, I would say I, if I were you, I probably would look at that. Option of just selectively updating pages versus whole nine yards. Just because I think with the size of where your DTC is right now, you'll get a better roi, especially with a small team doing incremental changes versus just trying to come in and blanket redo everything at once. Because if you selectively target, let's just say three pages to start with, that gives your team time to take those three pages, make changes, create new pages, create new content, focus on SEO, maybe push some Google Ads landing pages or meta landing pages or whatever and see what your lift and conversion actually is with that. And if you see a really good lift in conversion, then you can definitely justify doing more. But with DTC not really being a huge piece of your business and a huge focus of your business right now, I think what you'd probably end up doing is doing this massive overhaul and then not having the time to really focus to drive the traffic and get the value out of a full overhaul. That's my high level recommendation though. I don't want to discourage you if you are definitely looking to like grow that and grow your team and whatnot. But I think where you're at right now, that probably makes the most sense. I think right now we're trying to assess all options and I think something I said to Chris early on is like, it's tough because it hasn't been a priority selling channel for us. We've been pretty much forecasting flat growth. We're trying to make a case to further invest and grow. We don't want to like drive back, drive traffic to a site that's like old and not ideal. We're trying to like lay out options. So like, I'm not sure what's going to be like the right option and path, but it needs to be an option that further supports like where the business sees D2C, like fitting in as a selling channel. So like do we want to continue invest it, you know, on. So maybe we want to do the full overhaul or it's like, okay, no, like let's do it in baby steps. So I think it's like helpful understanding that as an option, I guess like going back to cost. And I know like how, I know we're just like ballparking here, but if we, if we decided to go down that path of like say we said three pages we wanted to start with or it's like all the product pages and blog to start, like what, what's like a phased cost structure for something like that? Because I know you said like 15 to 30 ish or up to 30 probably. And then like the timeline, I guess, to get that done. Yeah. So again, that sort of determines what your theme currently looks like. The big driving factor is the theme liquid file. Just being able to take a look at that to see, like, is it a giant mess that needs to be cleaned up at the same time that it's upgraded? Because that can be a factor there. I'll give you a rough estimate based on, like, Magic Spoon, for instance, when we did the first round of changes for Magic Spoon to upgrade them to 2.0. So we did three PDP templates and the theme liquid file. That's it. Off the top of my head, I want to say that was about 30 to 40 hours of work, and we did that over the period of like, three weeks or something like that. So that's just like a rough ballpark. So you're looking at a route somewhere between, like, on the lower end, if that was a little bit of a lower estimate versus a little bit higher, somewhere between like 5 and 8k. Okay. Give or take. Okay, that's helpful. Is that something. Sorry, sorry, I'm not the web person. So, like, is it something where doing it in a phased approach, is there any detriment to, like, the back end of fully transitioning over? Meaning, I guess, like, right now I know we've put a lot of, like, band aids for, like, on top of, like, things instead of fixing them in the short term. So, like, is there any, like, negative to, like, doing it in a phased approach? One just from, like, being able to fully transition later? And then my second question is going back to that accessibility bucket that you had mentioned just from, like, being sued, how does that cover us there? Like, is that still, like, leaving us very exposed because we've only, like, upgraded some of it, or is that, like, something because, like, that probably should be factored into. Does full upgrade, like, completely eliminate that as a. I mean, I know the risk is never eliminated, but does that, like, significantly reduce our risk? Or, like, how does the half upgrade fit into the accessibility piece as well? Yeah. So first question, downsides. There's not really a downside other than if you end up doing the entire site, I think you might end up paying a little bit more just because the phased approach, instead of it being all at once and done efficiently, you're kind of piecemealing it. So it does end up costing overall just a little bit more if you end up doing the whole thing. That's probably the only downside. Second question, as far as like upgrading accessibility and stuff it depends on. So there's a lot of things that play into accessibility to make you quote unquote compliance or, you know, clear of the gray area, I guess I should say, because I hate to use the word compliant because there's no codified set standard for accessibility. Which is why all these lawsuits exists is because it's just gray. But there is a way to get out of that gray area as much as possible. So it depends on which pages you update more so than anything. And the reason why is what I generally see from getting lost, lawsuits getting filed. It's alt tags are always mentioned on images. That's the number one thing I see in every single lawsuit. The that I've dealt with with clients is alt tags, either alt tags not being present or not being meaningful. So like there's something in the alt tag, but it doesn't make quote unquote sense. That's a big one. Anything around pricing, sales promotions and marketing, the checkout flow, the ability to add a cart, the ability to see sizing nutrition information like that kind of stuff is all the biggest factors. So if we were to do. I'll use PDP page as an example. If we were to do the product display page in that upgrade, we'd make sure that products by default have alt tags displaying. Obviously the image has to have an alt tag applied to it. In Shopify, like text, we'd make sure that all the buttons were accessible. Any menu items that were on that page were accessible. Nutrition obviously would need to be visible. I think just quick glance on your website, I didn't see like nutrition in text form. It might be on the alt tag of the image. I don't, I don't know yet. But whatever was on that page we would handle. But things like say the cart that would be separate. Right. So since the cart's on every page, technically if there was an issue with the cart, that would exist on every page. So it's like really tough to definitively say like handling a page would handle everything because of like cart checkout klaviyo pop ups. Like we've seen Klaviyo pop ups have issues as well. If that pops up on every page, then that becomes an issue on every page. Yeah. Okay. Unfortunately, that's helpful. That's helpful. I don't know. Luke, do you have any. Any other questions? I don't think so. I think we probably need to have a discussion on our side. Yeah. What would be a good next step? Like we can, we can talk on our side and get a tighter scope to you guys. So we could, like, better price it or would you like. I don't know if popping around on the back end is, like, possible. I don't. To like how. I don't know what would be, like, the best next step here. Yeah, I think. Yeah, I'm sorry, go ahead. I was gonna say, I think obviously y' all talking about it is a big factor because. Yeah, you have to decide what makes sense. Secondary to that, though, while you're talking, if you wanted to grant us access to be able to take a look at your theme to see kind of what we're dealing with, that would give us an idea to be able to give you a more precise number. Regardless of what option you were to choose, then we'd at least know what we're getting into to say, oh, okay, this is either going to be a bigger or smaller lift than we thought or, you know, whatever, if that's the route you want to go. I can. If you. I'm assuming y' all probably have a collaborator code on your account, so if you provide the collab code, I can just request access through our Shopify partner account. Yeah, got to remember where to find that. Settings. Users. I think it's users. Yeah, I just had to do this for someone the other day. Let me pull it up. It's. Let's see. We did this for Urban Pops. Yeah, yeah, I got it. I got it. 4617. 4, 6, 1, 7. Okay, give me just a second. Okay, so we just need. Where is it? View files, manage apps, and where is theme? Theme, theme, theme, theme. I'm overlooking it. Where is it? Themes. Here we go. Themes, Edit. Theme. Do you. And you mentioned blog posts. Y' all currently use blogs at all? Not too often. Yeah, we're not posting regularly. We kind of do, like, tranches of five. You know, like, we'll launch five and then do nothing for a few months. Got it. Okay. Meta objects. What is your fulfillment fulfillment look like? Do you all have three pl. No, we have in house fulfillment, so it connects to shipping easy, I believe. Shipping easy. Okay. One fulfillment location or multiple? Just one. We're vertically integrated, so we make everything and, like, everything is in the same facility. Oh, nice. Okay, that makes it easy then. Magic Spoon is definitely not. They have a very complex setup. And are y' all on Shopify Plus? No. No. Okay. All right. Invite sent. And y' all said that you do subscriptions through recharge. Is subscriptions a large part of your D2C business? Through the website, I think like 15%, 15 to 20, something like that. Okay, so that's a huge opportunity for you all then. Yeah. Okay, good to know. Okay, so once we have access, I can pop in, take a look at the theme, kind of see what we're working with, get a better idea there, take a look at your apps, see if there's any, like, crazy integrations that we need to be aware of from y' all side. Obviously talk through the different options. I think that there's probably a couple different ways I would look at it. One would be how does your business operate today? What do you want your business to operate as? If you want to make improvements to get to a better place and you're going to invest money and whatnot, do you also have the time, effort, and money to support that once it's done, to drive traffic, do the marketing, do the ads, all that kind of stuff as well? Yeah. And then if you had the ability to make changes on the website, easy. Obviously you don't now, but if you had the ability to, would you update the website more often? Because that's obviously value as well. That's. Yeah, that's really the high level things I think I just accepted. So you should see something on your end. Yep, got it. Okay, so I guess have a look on your end and we'll have a discussion and then I guess we can reconnect. Do you want to put a time on the calendar for next week to. To reconvene? Yeah, I think that sounds good. Awesome. I'm looking at both Andrew and mine's calendar. Andrew, is your calendar up to date for next week? It should be, yes. Okay. Tuesday, the 31st in the afternoon is probably the best. Sometime between 12:30 and 2, it looks like we're open at. Are you. Got you guys at. Yes. Where's. Yeah, Easter. Yeah, I mean, we're all eastern time here. Yeah, we're open that whole time, so. Yeah. Awesome. Andrew. I'm gonna go ahead and put it in for 12:30. Okay, that works. Awesome. Wonderful. Yeah. One quick question. Looking at the code, do y' all use anything like Semrush or Ahrefs or anything for, like, website monitoring from an SEO and marketing standpoint? So we have a. An SEO agency at the moment that provides us Semrush reports, but we're not really doing anything on our end. Got it. Okay. I'll. Chris, I'll run a report on our end. Just as well to see kind of where it sits currently. Wonderful. So what. What we'll do is we'll come to the table with basically just some based on this conversation, some more honed in numbers and honed in timelines based on the scope that we all just outlined here today. We won't have anything completely formal to present because if you guys have some, you know, modifications and changes based on Yalls discussion over the next week, we want to make sure that we hear those and take those into account as well. So we'll be able to give you guys a much better starting point from there. We'll then hear from you guys on what, what edits and modifications you feel like would make the most sense based on those numbers now. And then we can then determine what an actual next step is going to be after that meeting. Does that sound good? Yeah, no, that sounds. Sounds great. Fantastic. Well, awesome. Well, if you guys have any questions as you guys are talking, send us both an email. I am going to be out of office most of the rest of the week, so sure you do copy Andrew on any of those. And if we have any questions or I shouldn't say we. If Andrew has any questions as he's looking into things this week, he'll hit you both up about it. Okay. Sounds perfect. Thank you so much for both your time. Enjoy your trip, Chris. Will do. I appreciate it. Have a good rest of the day guys and I'll catch you all later. Sounds good. Thanks. Thank you. Have a good one. Bye.