ASP Global - Current

Chris LaFay: It. Parker, this is what's happening. The first video call that I think we've done. This is actually. This is like brand new. Like, I've never actually, like, started a, like, new person that I've met and not been on video for, like, majority of our conversations. Nice. Nice to see you, sir.

Parker: Yeah, yeah, good to see you too. I like the guitars in the background. I also, I play guitar as well.

Chris LaFay: Hey, there you go. How long you been playing for?

Parker: Since I was in sixth grade.

Chris LaFay: So there you go.

Parker: Yeah, a long time. A long time.

Chris LaFay: Do you. Where do you play often? And if so where. Like where and how.

Parker: Yeah, I, I played like, it was my whole life in like, high school and college, like planning B and bands and stuff. These days I, you know, pick it up when I can. I really wish I was playing more. You know, it's one of those things that's like, damn, I. I really need to be playing more guitar. But, you know, it is what it is.

Chris LaFay: Do you pick up. Have you picked up any other instruments over the years or is guitar been the one and only, not, you know,

Parker: other, like, stringed instruments that I could pick up, like ukulele and whatnot. But that's just because the skill translates. But not, not properly. No. I've always. I always wish I had started with piano, you know, as an adult. Now I' why didn't someone make me play piano as a kid?

Chris LaFay: I it. I learned trumpet in middle school and high school. That was my starting instrument. And so I was able to understand how to read sheet music. And then if you can imagine, playing trumpet with braces on is a very unpleasant experience. And so at one point I realized I'm not going to do anything with trumpet long term. So, yeah, I was like, I'm not going to put myself through this pain and agony anymore. And my mom always taught me, like, when you're in like, middle school, high school, like, just play an instrument throughout those years. Doesn't matter which one, just do it. It's. It's a good muscle to. To do, to use. And so I had like two more years of high school left. So I picked up guitar because my friend played guitar.

Parker: Yeah. Yeah.

Chris LaFay: So glad I did that. Because guitar led to piano, which led to bass, which most recently led to drums. Oh, nice. I am trying really hard to become a better drummer. I can keep a decent beat. Yeah, I've gotten a lot better over the last year, year and a half or so. But that, that is a challenge. That is a huge, huge challenge. It breaks your Brain so much.

Parker: Oh yeah, no doubt. I've dabbled a little bit. Do you have like an electric kit or a full kit?

Chris LaFay: So my, my wife, last year or a year and a half ago for Christmas got me an electric kit. We rearranged one of our rooms that we weren't using and we kind of turned it into a sitting room. And there's this little nook in that room that was like the perfect size for an electric drum kit. And so she was like, I got you. And so.

Parker: Yeah, right on.

Chris LaFay: Awesome. Yes, yes, very nice. So website stuff, man, you've asked a couple of really good questions over the course of this week. Obviously you've taken a look at stuff, you process through it. I'm not going to sit here and talk at you. What questions do you got for me?

Parker: Yeah, just a few, I guess. Four topics. Some of them are just asking more so I can learn. Okay, so number one, I think I've decided against multi site and the reason I think that is because. And you can still talk me out of it. But my thought is that we're going to get the Primo site up and it is going to continue to evolve all the time. Like we're going to be working in, like I mentioned, like education modules and other stuff that's going to actually have people properly interacting with our site beyond just like look at these products and the ASP site is never going to see any of that. And I don't even know like honestly how long the ASP site will exist and it's like in this form. So for that reason I thought like maybe we just like you said, duplicate like kind of how the basic framework of it looks from the Primo site, but just keep them separate. That's my thought.

Chris LaFay: That's fine. And I think all of those reasons, check the boxes of why you would have them separate. And so like I have no. If I had a rebuttal, I would absolutely give it to you. But yeah, yeah, you're saying the things and I don't see any. Like, obviously you know your brand way better than I do right now, but the longevity that you're thinking makes it look like both of these are going to be on very separate tracks long term. So it's actually okay for them to start from the same spot and deviate widely. That's okay. And so as long as all those things are true, then I wholeheartedly agree with you. So cool.

Parker: All right, well, let's plan on that then. Second one is I don't know if this like comparison or analogy makes any sense. But obviously we want our site to have, like, good SEO so that when people are searching for this type of product, we are among the top results. But we're not competing with that many companies. There's like maybe eight at maximum, 10 companies who have products like this in the world. So that makes me think, you know, we're not selling lamps. We're not competing with 10,000 other companies to have our lamp be the top listing. So for that reason, like, on a scale of 1 to 10, how much, how far do we need to be going with SEO to get good performance? Like, do we just need the foundation of, like, Yoast and the right words, or do we need to do a little more?

Chris LaFay: So I'm going to get a little over my skis in this because SEO is not my. My personal strength, but I'm going to kind of give you my general. My general gist here is I am always a fan. Let me actually back up. Let me ask. Let me actually ask a different question. And I realized that part of this answer, you're going to be skewed because the Primo site literally has a single page on it right now.

Parker: Yeah.

Chris LaFay: Let's just pretend for a second that the Primo site's traffic did not increase at an exponential pace or even like a strong linear pace when the new website launched. It just stayed. Your marketing efforts stayed very consistent with what you're doing, the whole nine yards. And it, you know, obviously it'll grow a little bit by a little, because if the company grows, chances are your website's traffic is going to grow. If I, by saying these sentences and words, you from your seat, how does that make you feel about your company's overall growth trajectory? Do you feel bad because you don't think that that's going to be enough? Like, basically the marketing stuff that you're doing right now and the types of stuff that you're getting clients in is not going to be enough, or do you feel good about that? And having an. What I'm going to call an influx of organic traffic and leads doesn't really matter that much. Which side of that continuum do you fall on? It's an.

Parker: It's an interesting question. On one hand, no one is going to convert to our products because they saw our website.

Chris LaFay: Okay.

Parker: Like, it's. We have a very much. Yeah, like, someone needs to be in the hospital convincing a clinician to do XYZ for us to ever convert business. However, we do get, like, inquiries that come because someone saw Something, somewhere. So I guess it doesn't. I don't live super far in one direction or another. I would like to have more organic traffic just so that people are getting more familiar with our brand in general. But ultimately it's not really impacting our bottom line directly that much.

Chris LaFay: Great. That's the perfect answer. So this is my thought. When the new website launches, it'll obviously have Yoast on there. You can then go to town putting in meta descriptions, the whole nine yards, doing whatever you want to, build out pages, build out blog post, all of that stuff. Do that. If you decide that you want to have a legitimate SEO strategy, tack that on top later. Because right now, like with the primo site, there's. You have one page. There is no, like, SEO juice to port over. All this stuff is going to be new. Yeah, right. Right. So don't. This is an overly general statement, and I find that it's true more than 50% of the time that people say they want organic traffic and they want all this stuff, but in reality, they don't realize that they need to be consistent with SEO. But on the flip side, a majority, the same majority, doesn't need that. So they, if they say it as a buzzword almost and be like, I want organic. I'm building a new website, so my organic thing should just increase. It doesn't really work that way. And so if you want to have a dedicated, if you want to grow organically, work with an SEO provider. And that's going to be the way to do it. I do need to send my wife a quick text message. Really?

Parker: You're good, you're good. No worries. That. That'll give me a chance to write a note or two.

Chris LaFay: We're doing. We're swapping off laundry loads. And so whenever there are times you like when as soon as it's done, it needs to come out. And so I'm seeing. I don't know if she's home right now, so I'll have to send her another text in a minute probably. But so sorry about that. You're good. So, yeah, that's my. Does that all make sense?

Parker: Yep, that makes perfect sense. Okay, next question. And if I overlook this in your proposal, I apologize, but I didn't see it.

Chris LaFay: There's a lot of stuff in there. It's very intentional.

Parker: I, as the only person at my company who knows even a little bit about WordPress and managing a website, I know that once you build the site, and especially combined with the instructional stuff, educational stuff, that you're gonna give us. I could manage the site completely from there, but the powers that be are like, we have to have someone to that we can call day and night to like fix our website when stuff inevitably goes wrong. And I'm like, you know what? If you guys want to pay for that, go for it. So I guess my question to you is do you do some sort of like ongoing maintenance and like hosting of site type stuff?

Chris LaFay: So in terms of maintenance, like what you typically think of, like the $500 a month and lower sort of thing where you have like a couple of hours at your disposal. I'm not set up for that. I'm set up for larger retainers probably north of 2, 20002500 where we're helping grow the website strategically.

Parker: Yeah.

Chris LaFay: My assumption is that's not what you need, but what I'll say, you know, Mickey Melon. And so if any of my clients ever need maintenance, I tell them to go talk to Mickey because Mickey is built for that one purpose.

Parker: That's what we pay for today. Exactly.

Chris LaFay: So I'll basic you'll still host your own website, so I'll recommend you host on WP Engine. I don't know where you're hosting it right now, but I recommend you host on WP Engine. Or honestly, what I'll do is I'll talk to Mickey and see where he would prefer it be hosted. Y' all would pay for that? Because both me and Mickey are very of the same mindset of we like our clients to own where their site lives. So it's less for like, if you ever need to part ways, there's less friction that has to happen. It's kind of the opposite of businesses be as sticky as possible. No, we try to be as less sticky as possible. Yeah. And so we'll toss it up on a server that you guys own, that Mickey likes to use, that work with his systems. And then you'll talk with him about what those monthly fees are. And they're. He has a couple of different plans. They're all less than 500 bucks a month. I think he has like a. A 150 and a 3, 300amonth plan at the moment.

Parker: Yeah, yeah. I think we're already on his 300amonth plan.

Chris LaFay: There you go. Yeah. So you would just so talk with him about it. I can talk with them for you. I'm going to talk with them tomorrow actually.

Parker: But it's okay. I mean, I think the assumption is that that was going to continue anyway, like, like he was going to continue managing our sites anyway. So that's perfect. Okay. Last.

Chris LaFay: So just to give you an idea of kind of where because his business has changed a little bit and he's going 100 into just maintenance mode. So if there's anything that kind of exceeds the scope of we'll call simple maintenance and like page building and stuff like that towards like, hey, you want to build a new feature on top of the site? That's when we'll come back in, we'll build the feature, toss it on the site and then let Mickey manage it from there on. So sure. We've known each other for years. This is what we do. It's fun.

Parker: Yeah. Got it. Okay, last one is. Okay, the custom post type versus the import from WooCommerce thing.

Chris LaFay: Yeah.

Parker: Okay. The pro. The cons list I've heard of Woocommerce so far is it's heavier, maybe not quite so user friendly and I guess that's it.

Chris LaFay: You're not doing E commerce. Like at the end of the day, you're like the one of the other cons with it specifically for you and how your business is running is WooCommerce has a very like product categorization experience. And my thinking is over time, if you have, you know, your product, this data for these products inside of custom post types, you're not going to be as locked in long term to kind of the. The layouts of WooCommerce that you could have. You could do some more marketing stuff with those single product pages that you have over time. So it's a con. It's not a, it's not a, it's not a huge con by any stretch of the imagination. But one, I think I do like

Parker: the idea more of the custom post type direction. And if I remember correctly, basically you guys would come up with like what that product page looks like for us, show us how to upload all of our product data to it and then over time we would have populated with everything that we need.

Chris LaFay: Right? Bingo.

Parker: Yep.

Chris LaFay: 100. And then you would also have a redirections plugin on the site as well too. So mainly for the ASP site because it has all the products we would in that redirections plugin, you would. Before you delete a WooCommerce product, you grab the URL paste in the new URL. So then @301 redirects to the new one. So.

Parker: Okay, got it.

Chris LaFay: Not that anybody has like a nobody. No, I doubt anybody on your, you know that your customers like have URL saved Away for a rainy day. But yeah, Google's purposes, it's good for it to know where one goes to the other.

Parker: Sure is there. This is a sort of a side question. Let's say we did decide to go away from WooCommerce to a custom post type. Is there a way to export all of that data in a way that's clean enough to where then we could then use it to populate the custom post type, even if it is like somewhat manual?

Chris LaFay: Yeah. Like you can export like product data. Long story short, like in an Excel file. Effectively it might not have. If you have a lot of custom things coming in from custom plugins and things like that, it might not grab every little bit, but it's going to grab your product titles, your variations, your descriptions, your photo URLs. The. The main stuff give you that in an Excel file. And then depending on how we decide to build your custom post types out, there's kind of two ways we can go. One is we can actually kind of keep it very similar. Similar to WooCommerce in the sense of when you build out a new product, you just fill out a form and so the pa. The actual. Like when you view that particular page on the site, you're not having to drag and drop blocks all around. You fill out the form, it all shows up. So that if you ever want to make a change to those from a layout perspective, obviously you need a developer to help you, but it changes it across the board.

Parker: Yeah.

Chris LaFay: And so it's simpler that. It's simpler from a creative standpoint and it's simpler from a. I want to change all of these in one fell swoop. On the flip side, we can make them to where that custom post type is a drag and droppable, you know, drag and drop blocks. So obviously things will not be identical. 100. I mean, you could duplicate a post or a page and then just edit it, but over time they will deviate. Just because that's the natural thing of what happens when you can customize stuff is they deviate. Yeah. The cons to that is you have to spend more time building pages, a little bit more creative juice. The pluses are you have the ability to drag and drop blocks on stuff. So we don't have to make a decision on that right now. But if we went the importing route and that was a big piece for you, my recommendation would be to give you a set of form fields so that you could import an Excel sheet and automatically populate all of them all at once. But if you wanted that level of flexibility to create product pages kind of as landing pages and tell custom stories on each product, that ability to import would be a lot less. It'll probably be a good thing for you to go through to kind of understand like I have one sheet where all of my data is. I don't have to think about, you know, different stuff. And then on a page by page basis you could tell the story however you want. So there's everything is trade offs at the end of the day.

Parker: Yeah, yeah.

Chris LaFay: So there isn't a right answer. It just depends on what the business goals are.

Parker: So yeah, yeah, for sure. Yeah. That's an interesting one to think about because for the ASP site I would just be like every everything, same format, no doubt. There's no reason to change anything. But on the primo, the product lines are few enough to where there I can imagine a sort of a custom story for each. But I just don't know if that's. Like you said, we don't have to make that decision right now.

Chris LaFay: But and one of the things, if we, if we went the like where we actually had the block editor on the custom post type, we would still have a couple of custom fields kind of in a sidebar of like the key data points. So that if we ever wanted to later down the road build a filter for these things or create a custom block that dynamically pulled three products from this category or that have this thing attached to them, we would have a couple of custom fields that all of those posts would share so that the database would know, hey, these are very specific things about each of these products so that you'd be able to do those things later. Later down the road. Yeah. Okay, so there is a middle ground, but at the end of the day, the middle ground, the building of the page is still manual and fully customizable based on the building blocks. We'll just have some data points over here to the side.

Parker: Yeah, that makes sense. At what point in the process will we need to make a decision on

Chris LaFay: that, so to speak, during the design phase? Because we would want to think if we're going to think about the design in a templated format or are we going to think of it in a, like we're just going to design you 12 building blocks and call it a day. If we're thinking about in a templated format, we want to confirm that in design so that when we get to dev we can sprint.

Parker: Is there a cost difference between those two approaches?

Chris LaFay: No, it's really Just a business decision at the end of the day.

Parker: Okay, got it. Speaking of cost, if I remember correctly, you said going the custom post type route would cost an additional five to seven grand, right?

Chris LaFay: It would cost about. I did talk to my developer, it cost about five. So on the low end of that. Okay, 25 to 30.

Parker: Okay, well why is it that that just seems again just like gut reaction, like a little high for a custom post type. What can you tell me a little bit more about exactly what we'd be getting like visually?

Chris LaFay: Yeah, so we, so when we go the custom post type route, what that typically. So there's, there's multiple levers that we pull. Obviously one lever is what custom functionality do we have. So for you guys, we're duplicate, we're taking one website, we're duplicating it out. There's effort there. So that's not custom functionality, but that's more effort than what a normal site has. Part two, how many total pages are we actually putting thought into building them? This more applies to sites that have 40, 50, 60 pages at their disposal. Of like not talking about woocommerce products or blog posts, but sure, yeah, yeah, yeah. Because WooCommerce and Blog, you can literally just one click import and be done pages. You can't do that. So for you guys, we're doing about five pages per site. That's another level lever for pricing when it comes to custom post types is not the initialization of the custom post type, it's the. Because that's all simple. What typically comes with these custom areas are more building blocks and more templates. So yes, we have our standard 12 to 15 blocks that we design out for projects like this. But when we add in a special type of content that typically adds more building blocks to both design, do the layout of and then develop out. So that building block library might go from 12 to 15 to 15 to 18. And adding in that both the design and development time, that's where that five grand comes in is it just extends the amount of stuff that we're doing. Got it. So if we kept the, if we kept our building block number at what was it? If we got the block number to 15, then we would be fine and we could stay at that $25,000 price point. So there's, this is just the 20 years of experience knowing that the more custom areas of a site mean more design, more QA and more development at the end of the day.

Parker: Okay, I got you. At some point could we, this is back to what we were Talking about a second ago, deciding between sort of more templated product page versus the building block to have some more kind of custom options. I'm just wondering if there's a way you could show us a visual of, like, maybe how that would look. Like, like, what are. I don't know what I'm trying to say here. I would like to, like, see maybe on the, like on the back end or maybe even on the front of someone's website, like, here's. Here are some ones that were done custom versus just like a templated one. And like, here's how you do it. Just to know, like, how difficult would it be for us to do what.

Chris LaFay: Talk to me a little bit about this. What is what the goal of the product page is, given that nobody is going to actually make a product purchase on the website? Normally product pages, the goal is buy now, add to cart, check out the whole nine yards. So obviously the goal is to request a quote, get in touch. All that jazz. In terms of the story that you want to tell people, talk to me a little bit like, this is kind of. This is. We're dipping in a little bit like, kind of into, like, the discovery side of things right now.

Parker: Sure.

Chris LaFay: But this will. This will help. But. So talk to me a little bit about. I think you want to tell stories on these product pages to drive. Interest isn't the right word, Drive people to an action that is not a standard product structure. Because I've heard interest in that through the meetings that we've had, which is why I was pushing you that direction. So I think.

Parker: Yeah, well, I would just say it's. It's a little extra complicated for me because we're in the middle of, like, acquiring some additional technologies that really do are kind of, like, disruptive in the field, and it requires a lot of education. And it's like, not immediately apparent even from a clinician standpoint, what is this product and how does it work? So there needs to be like, a level of very punchy, like, education. Like, here's five reasons this thing is better than what you're doing now. And so it's. It's more than just like, a list of the features and then the different sizes that the product comes in. It's more of, like, telling the story of, like, if you convert to this product in this, like, system, you're going to be able to get rid of all these products. Your results for X, Y and Z are going to be better. So it's a little bit of that, like, storytelling education element. With like a pretty heavy clinical slant. But I don't know if that needs to live on like the product page or if that could be done more effectively in like a blog post style page related to the product, if that makes sense.

Chris LaFay: Going to ask you a different question.

Parker: Okay.

Chris LaFay: How many. For. I'm thinking about Primo in particular. How many products are going to be on the Primo site AT launch and 12 months down the road? How many will there be? Ish.

Parker: I would say we'll have you look at something real quick. I might even be able to go ahead and show you exactly what it would be. Okay, I'm going to share my screen real quick.

Chris LaFay: By the way, do you have a hard stop at 1:30?

Parker: Not a super hard one. What about you?

Chris LaFay: Okay, I have a meeting at 2 that I have to do a little bit of prep for, so I need to be off by probably 1:45.

Parker: Okay. No, no problem. I. I don't have too much left for you. Okay. This is, you could consider this like the whole Primo company today.

Chris LaFay: Gotcha.

Parker: It all lives in, in here. And so, you know, for a lot of these, you know, just imagine a lot nicer version of this is what we would want. So this is again, more or less every product line that we would have on the website. If we were to have it built tomorrow, 12 months from now, even six months from now, I would expect this to increase by maybe 20%. But with like three new categories. Some. Yes, three to four new categories like these ones. But those three new categories would be much more technical than this one. So they would need like maybe a little bit of extra storytelling. I don't know if that's helpful or not.

Chris LaFay: But yeah, so like go, go back into, go back into the one you were just. I think we're in cushions or something. It doesn't really matter. Okay, so yeah, so in general, each of your products kind of has this core structure where we have like title description, product data points and then related products underneath it. So what, When somebody gets to this page, do they know exactly what they are looking at?

Parker: Anyone who looks at this page will know exactly what this is.

Chris LaFay: Got it. Okay. So the, the. So the reason I asked that is the given that they know what it is, the details are important. I'm not suggesting the details are not important, but connecting with a potential customer's problem is actually a higher priority than saying here's all the details in a table format because you're trying to connect with them at that point. So. The way that I would think about doing these pages. Hold on, let me. Give me a second to. Yep, my brain computer. This is why, this is why I would recommend. So going back to your custom post type question, the additional costs and things like this. So I'm gonna, I'm gonna use this as a very specific example and it might not be exactly what we designed later, but it's easy to comprehend here. So we have this product information table, right. Obviously this is literally a table inside of a pod. I'm not suggesting that the design of this is complex located, but this type of building block for descriptive product information is not something that you would have on the rest of the marketing site. It's only. This is a block that would specifically be used for the single product. So when we're thinking about adding another custom post type, we know that there's going to be probably three or four different building blocks that we're going to need to build that are either dynamic, that pull data from a product or, or they're going to be very flexible for storytelling that are not necessarily going to be used on the rest of the site. So my thinking is here is that I don't know exactly what stories we want to tell and what that structure is going to be like. We'll. We'll talk more about that like during the wireframing process through this. But the questions that we're going to want to ask when it comes to a product page are what is the core problem that this solves? Or what is that pain point that a customer, when they get to this page knowing what the product is, what is that main headline going to say and make them feel like oh yeah, that is the problem that I'm having. Or that is the pain point that I'm feeling have descriptive text around that. Obviously having CTA is like request a quote and stuff along those lines and then the farther down the page they get, the more and more detailed the information that they get. And within that there's going to be a handful of blocks are going to be designed and built that are specific to this particular type of story to tell. Now can you use those blocks in other places? 100 you absolutely could, but chances are they're going to be highly specific to. To this. So yeah, I, there's going to be a mix between dynamic like content that's pulled from the actual post itself. Kind of like how you save away woocommerce data into fields and also some drag and droppable blocks as well too. So that you have the ability to flex and to customize where commerce. If you tried to do that in WooCommerce. Here's something to add to kind of the pros and cons list. The single product page is completely coded now. They've made some changes to where you can do some drag and droppable blocks and whatnot, but it's a lot more cumbersome to do so. So yeah, you're going to add some flexibility by doing this and you'll also just add some extra blocks to your library that you can use too.

Parker: Yeah, that makes sense.

Chris LaFay: That was a very long winded and winding answer to your question. So I hope I got somewhere close to where you, what you were looking for out of that.

Parker: No, no, you. You did. You did. And I kind of had a, a vision or two just as we were talking about it, which is, you know, the, the Primo portfolio I think is small enough to warrant telling a story about maybe not every single product. Some of them are going to. Are more commoditized than others, but at least for some of them like that product specifically, you know, it's a. It inflates like a hockey table and you can move a patient really easily. So you can tell. You know what I mean? Like it's. There's more to tell than, than what meets the eye. So I think that the custom post type for those reasons you said are probably worth exploring. So. Good. All right, I'm good there. I don't have any more questions.

Chris LaFay: Awesome. That sounds good. Now I know that we have a, a hard deadline of April to get Primo launched. We'll need to go ahead and get rolling here soon because a lot of these typically take about two months and we're gonna hit kind of the month and a half two timeline here shortly. So in terms of when you think you'll have your decision, when do you think that's going to be?

Parker: I. I hope to have the decision made Monday. The people that have to make the decision with me are out of office today or else I would make it today. But yeah, Monday, Tuesday at the latest if I happen to just not be able to get them. But I'm trying to. I want to get started as soon as humanly possible.

Chris LaFay: Awesome. That sounds good. We can basically. So what. What will happen from next steps on my side, just so you have a general idea, is that if all of this sounds good, you get approval, we end up working together. I'll send over a contract that has really the more like the legal. These bulleted point list of like here's all the deliverables. Here's where the QA round sit, the whole nine yards. And here's the rough timeline. Payment, invoice, schedule, all that jazz. I'll send that over to you. That'll be a panda doc link to sign. And then we'll immediately go ahead and get the kickoff call scheduled. And the way that invoicing works is every 30 days. So if it's a three month project in total, it's four payments with a kickoff payment. And then invoices are just done every 30 days for simplicity. So, yeah, try to keep it as straightforward as possible. That is the plan. And we can probably get kickoff scheduled within a week. So, like, if you get confirmation Monday, Tuesday, by the following Monday or Tuesday, we should be able to have a kickoff scheduled. So.

Parker: Yeah, that sounds good. Yeah.

Chris LaFay: Yeah.

Parker: I also, I. I completely forgot. My designer did send me the wireframe or the. The fig.

Chris LaFay: Oh, yes. Yeah.

Parker: And I completely forgot to send it. So let me. I'll just email you the link to that later. Again, that's like a look and feel of what Primo will be. We don't have to necessarily stick to any of that, obviously, but just so you know.

Chris LaFay: That's fantastic.

Parker: Okay, cool.

Chris LaFay: Any other questions for you?

Parker: No, I think I'm good. I hope you enjoy the rest of your weekend. And thank you for putting up with my thousand questions and all that good stuff.

Chris LaFay: You've asked smart questions. I've had some people ask me really stupid questions. These are all really good questions. So much appreciated, sir. I hope you have a good weekend. And we'll touch base either Monday, Tuesday.

Parker: All right, sounds good. Talk to you soon.

Chris LaFay: Take care. Bye.

Parker: All right, bye.