Elisabeth Hedge - Sales
Chris LaFay: Hello, number two this time. The joy period. How has your week gotten started for you?
Elisabeth Hedge: Yeah, it's been good. It's been a little busy, but not too much. So just some blog writing and.
Chris LaFay: Yeah, very nice. What do you enjoy, what do you enjoy blogging about? Or is it for clients and not personal?
Elisabeth Hedge: Actually, yeah, it's actually for clients.
Chris LaFay: Gotcha.
Elisabeth Hedge: Yeah, but it's good. How about you?
Chris LaFay: I was up in New York City last week. I hosted a get together with agency folks. Hopefully meet some new people and have good conversation. Honestly, that's the whole point is just have conversations with people. And so we basically tried the like anti conference where it's like everybody says the best part of a conference is like the after hours things that happen,.
Elisabeth Hedge: The hangouts, because then you can actually connect with people.
Chris LaFay: So we basically just. The thesis was, would people come out to something if it was just the conversations? So we had bowling the first evening, so the people had like some kind of like lightweight activity to get to know new people. And then the following day, all day we hopped to about three different coffee shops slash lunch locations. And you could just kind of like join it, like join in one if you wanted to, hop out for the other one and whatnot. And then we ended the day at a really cool like bar kind of place. And so kind of wrapped up the day there. And so I put on my host hat and I don't like to wear that one for super long periods of time.
Elisabeth Hedge: So it can be a lot because you're also thinking about the coordination and backup plans and making sure that you have everything ready.
Chris LaFay: Yes. And I like when I plan something, I like planning it to a T. I'm also a fly by the seat of your pants kind of person as well too. So I kind of mix them, mix them together a little bit, which is fun personality quirk, but, you know, here we are.
Elisabeth Hedge: All right. Yes, that's great.
Chris LaFay: So we're talking here today because you have done some content import stuff for two people that I very much enjoy. David Feldman, who wrote that book right there, and the Wiser Sisters. And so, yes, when I was like, I need help, both of them were like, you should talk to Elizabeth. I was like, that sounds great.
Elisabeth Hedge: Awesome. I'm glad that they're happy with me.
Chris LaFay: Yes. Everybody that I've ever hired for the most part has come recommended from either one or two different sources. And so I'm gonna keep that trend alive. Shall we? So talk to me a little bit about content importing and WordPress. You can take that very vague question. Whatever direction you would like to.
Elisabeth Hedge: Yeah. So I've done some stuff in WordPress. I've mostly worked with Becca and Leah and Squarespace and then David on a project on this other program that I'd never touched before in my life.
Chris LaFay: What was.
Elisabeth Hedge: Was. Let me think, I have it somewhere.
Chris LaFay: Was it Ve. Sorry, was it something called Veya?
Elisabeth Hedge: No, it was. What was it called? I'm trying to remember. It was with, you know, it's somewhere in like the back of my mind there was some product he was using for the import. I can pull it up really quick.
Chris LaFay: I'm very, very curious about that because I know that David has his own software that he's built that's called Vea. But everything else that I'm aware of is WordPress. So I'm kind of.
Elisabeth Hedge: He was using something else for a content population system. So it was the content population system and it was storyblock. That's what it was. Oh,.
Chris LaFay: Interesting.
Elisabeth Hedge: Was interesting to use because I'm used to Squarespace where if I need to change something, I'm just able to do that. This was very much like working with a product coordinator of his and having to like say like, hey, I don't think this is the right spot. And then they were like, oh, let me go talk to the coders. So like it was very like I was just doing content population.
Chris LaFay: Yeah.
Elisabeth Hedge: Not like the extra stuff that I usually would do just to quickly fix something. So it was very different from WordPress or from Squarespace or any of the other ones that I've used before. So it was interesting. But it was also cool because it was visual. It was very, very easy for content population purposes.
Chris LaFay: So you didn't have to work creatively for the most part. It was just like put the content in and it just works.
Elisabeth Hedge: Yeah, like it just, it pops in because they coded it to work for it. So it was very interesting. That was my first time using it and David had explained it. He was like, it's like Squarespace on steroids. I would agree because it has a lot more of the coding ability. From what I understand. I was able to see the coding side of it, but from what I understood, like, it has a lot more of that hands on ability which Squarespace kind of takes away from people.
Chris LaFay: So yes, yes. Everybody's like, which CMS is better? I'm like, there's all pros and cons.
Elisabeth Hedge: It literally depends on what you're doing and what you want to do and how old you are. To be honest,.
Chris LaFay: That Is true. If you haven't learned anything new in a decade, chances are you're too old.
Elisabeth Hedge: So my, my mother in law, she was on WordPress. I switched over to Squish Squarespace and built her website for her on Squarespace. Because I was like, this is way too complicated. Because she was like, can you fix it for me? And I was like, I mean, I could, but then I would be like a manager for your website. I don't want to do that all the time. So I moved her to Squarespace and I was like, this is going to be the most easy thing ever for you. Because she calls us with like every techie question she ever has and she still calls me with Squarespace, but it's a lot easier to guide her over the phone.
Chris LaFay: Yeah.
Elisabeth Hedge: Because she's in California, I'm in Texas. So there you go.
Chris LaFay: Yeah, yeah, Yep.
Elisabeth Hedge: But yeah, so I've done website management on WordPress. That's pretty much as far as it's gone. Adding information to kind of already built pages, got people.
Chris LaFay: Okay, that makes sense. So all that sounds good. What you're going to find with this is we're going to actually be right down the middle. So there's going to be some elements of Squarespace where you kind of have control and then there's going to be some that are very much like storyblock, where you just, you fill out the form and it just pops out the thing with very little control. So what I feel like would be the best use of time is to actually walk you through kind of what, how we set a lot of things up and that'll get you, I'll call it 65% of the way there. Because in reality a lot of this is just repetition. Right. Like it's using it, playing around with it, messing it up, deleting it, starting over, blah, blah, blah. So let me share my screen with you. Would it be helpful if I recorded this session? So if we do end up doing some stuff together, you can come back and look at this as a, as a prime.
Elisabeth Hedge: Yeah.
Chris LaFay: Awesome.
Elisabeth Hedge: Yeah, for sure.
Chris LaFay: Let me go ahead and push the magic buttons. Don't. Not that one, this one, this one and that one.
Elisabeth Hedge: Do you exclusively use WordPress or do you use other.
Chris LaFay: I would say that the quantity of work we do that you would touch is 95, 98% WordPress. We also have started to do more builds in Shopify that typically doesn't require as much content, mostly just like in mass importing. For the most part we haven't really touched Webflow. At all. We definitely don't do Squarespace. And so WordPress is going to be the, the bulk of things. So. And let me go ahead and share. I'm going to share the whole window of this one with you. Awesome. One of the things that we always create with every client is something called a block library. And for the most part everything is named very logically. Now, ignore the lack of spacing here on this page. The default spacing got changed. I haven't edited yet. So that's why you see some stuff that's squishy together. And so within WordPress we build all of our websites using their built in page builder called Gutenberg. I think it's now called WordPress full site editing. Gutenberg rolls off the tongue so much better. So I use that. So anything that is core Gutenberg has that squarespace feel. More of a squarespace feel. You can drop in multiple blocks. You can, you can change font sizes, colors, the whole nine yards. There are blocks that have such a unique layout to them to where we custom coded the block so that layout's locked in and all you have to do is just fill out the form. I'm going to walk you through a couple of those examples just so you have an idea of how some of these things work. One of the things we very commonly do is we create case studies for clients. We do a lot of agency work and stuff like that. And so one of the things that we're. I'm a strong proponent of is that I can type. It's fine. If there's ever content on a site that's going to be replicated and used in multiple places, we like to store that away separately. So like if they wanted a certain case study on three different pages, you don't want to import that three times. That's dumb.
Elisabeth Hedge: Right.
Chris LaFay: So what you'll see a lot of in our websites is we'll have these second, these sections on the back end of WordPress that are honestly just like lines of content. Like they're basically just like a form fill.
Elisabeth Hedge: So like, yeah, I've used these before.
Chris LaFay: Perfect. Exactly.
Elisabeth Hedge: Yeah.
Chris LaFay: So when you go over here to this is the back end of Gutenberg testimony, there's a testimonials block and if you notice when you click on the edit button, it shows up, it shows up a form. And so here you can just drop in whichever testimonials that you want. So if you want to add in Allie Hogan and Angela Anderson or whoever, you can do that. And then now they all show up. Magically so not going to dive too far into these blocks because they're kind of self explanatory if you know what you're getting into. So like for example, there's a columns field. What do you think this field does if you change the number of the.
Elisabeth Hedge: Columns as the number of columns or detracts the number of columns?
Chris LaFay: The way that I teach is I try to make things to where they sound really dumb and stupid. I know for me that helps me remember them because it's, it's like, oh yeah, duh, that was obvious. I've learned that about my style and I've also learned that some people don't take that the same way that I take it is just trying to simplify it and dumb it down. So just a heads up, that's my style. There's different toggle fields. Like if they wanted the image attached to them, boom, you toggle it on and off. Those are all relatively simple. So things like this as well too. Like your icon pods, they are the same way. So we have columns, they have two different orientations, so vertical and horizontal. So you can swap those around. And if you notice kind of the background color is kind of dark here. So if you wanted to switch it into the opposite mode, it switches with a white background with black text. There's obviously a dark background image behind this. That's why it doesn't work well. But you have those options and then you have for these, these are all custom. So you have the ability to upload an icon, a header, a description. These just don't have buttons. So you see the button text and link, they don't appear because there's nothing in them. And then you can add as many of these as you want. In general, that's about as far as I'm going to take this section, this type of thing. Does that make sense?
Elisabeth Hedge: Yeah, sounds great.
Chris LaFay: Awesome. So those are custom blocks. They all fit about the same way. So let's look at something that is not custom. So this is what I call the thin call to action. Because the thing is, for simple blocks, we want to give clients flexibility at the end of the day. This is our thin CTA here. Got a heading tag, a paragraph and a button if you were to actually drop the thin cta. And there's a patterns library for all this stuff which have the same names as they have in the block library. If you were to expand all this, you'll see there's a row that's two columns. We have a stack which has a header and A paragraph. And then we have a buttons container as well too. So looking at a couple of these things, this outline view is I live and die by the outline view. Because it's hard to click into things inside of a cms. So with this button, if I wanted to go change its styles, WordPress's settings live on this right hand sidebar. So the left hand tab is like the page level settings and then the right hand tab is whatever block you have selected and its settings. And so they have. Each block typically has two settings panels. One is like general administrative settings and then one is the actual style of it. So here, if you didn't want the color to be the background color or the primary color, you could make it yellow, dark green or black. And if you notice, most of the time we have code written to where the text color automatically kind of switches around for you. That's the way the thing should be. You could also manually change the text color here. Sometimes you would have to do that, but a lot of times, hopefully not perfect. One of the things that you will see very often is this little interlinking squares. These are groups of blocks. This is going to be one of the most common things you see kind of at the the highest level of the outline because groups let you do a lot of different things. So if you notice, kind of the width of the page is kind of the width of the navigation bar. I call that the content width. But obviously we have some elements that go full width. And here's the reason why you use something like a group is because at the group level you have the ability to keep it at its content width, go a little bit wider or go all the way full. The group is where you have a lot of these not custom settings, but this is where you get a little bit into squarespace type of things. Let's look at this header here or the CTA medium. Ignore this big custom block down here at the bottom. For the time being, inside this group, all we have is a columns block. That's it. It's just a basic. Every run of the mill columns walk inside the left hand column. You have a header, paragraph and buttons. And then the right hand column you have an image. There's literally nothing unique about this at all. Every CMS has something like this. The reason why you group that rather than just putting the columns here is because when you have a group, if you go over to styles, you have the ability to add inside padding on the insides of things. And we have default sizings. And as you Work on a single site, you'll kind of know eventually. For this site, kind of the default spacing on this one's going to be 30, but maybe another one's 50. Just depends on art style and whatnot. And so you go here and Change that to 50, change that to 50, and now everything is nice and nice and even. Excuse me, you can also, in this section here in the group, you can also change the background color. So if you wanted to go light, you could go light. That's where the group shines, is you do all your core styling at the group level and let everything trickle down, if you will.
Elisabeth Hedge: Perfect.
Chris LaFay: Notice how the text all change colors and stuff like that too. You could also add background images. You could plop in a background image there and then also modify the image's opacity. Now, some things in WordPress, the editor has a lot of extra code, and so sometimes the special code like background opacity and stuff like that don't pass through into the editor. It's about 20% of the things. So you could do stuff like this as well. So everything basically starts out kind of at the group level and then kind of works inward. Okay, so what. What is the most like. So actually, before I go to the next section, any off the cuff questions about that?
Elisabeth Hedge: No, I don't think so. I think I understand. I've done a couple of things in an editor that looked like it. I'm not sure if it was that editor or not. So it was for an author though. So it wasn't that in depth of a.
Chris LaFay: That makes sense. So you'll have a lot of different layouts to choose from at the end of the day. We have a lot of stuff already coded and if you can't find a block in the library, you can always go back to the block library page, copy that and then paste it in as a starting point as well. What is the most common thing? And this is actually the impetus of why we're talking here today. So I'm going to show you two things. So this is a new client of ours and their website, from an aesthetic perspective, isn't too bad, but it's very sporadic, it's very random. So they have five different fonts, they have five different colors and they don't really know how to utilize them. Headers look like this and like this. And then you're using the header text down here. The header text for a text link like that should be a button. Then you throw this little guy in here too, right? Yeah, exactly. It's actually a really bad. This script font's really nice looking but it's not really great for web unless you have really large. It's hard to read. We're going to mix that by the way. What we're doing is Figma pulled up. No, because my computer crashed last time. Number rock. So the way that we think about things, as you probably can tell, is kind of in a building block format. We don't really think page by page. It's like what are the 12 to 15 different components and then what are the different subdivisions of them? Do we have like. So that. That thin CTA on the consume site? Actually this, this obviously can be flipped around. You go image on the left, content on the right. You can change the background color if you want. You can even go wide width if you'd like to. There's a lot of different ways to utilize this one thing. So that's how we like to think. We did a block audit of their website and they have a lot on lumber rock and they're all different. So the details of these don't matter too much. But what we're going to do is we're basically going to take all these from a design angle and we're going to consolidate them down into about 12 to 15 building blocks that have. That are a little bit better design. Because the design of these is very scattered. For example, here's an icon pod and then up here we also have an icon pod.
Elisabeth Hedge: So there's two.
Chris LaFay: So there's two. And there's more actually as well.
Elisabeth Hedge: Okay.
Chris LaFay: And so there it's all scattered to the. Oh, here's the other one. There's the other one right there. Boom.
Elisabeth Hedge: Okay.
Chris LaFay: All different fonts and all different things. So what we're going to do is we're going to design out 12 to 15 building blocks that take the core of their aesthetic and then make the blocks a lot more flexible and not have all this duplication.
Elisabeth Hedge: Yeah.
Chris LaFay: And so the reason why we're talking is that in the footer, these pages and the homepage they're going to spend some time on, these are the ones that we're going to worry with. The others just need to be brought over. What you're going to see at the end of the day is a block library that honestly doesn't have nearly as many things for on the consume site, probably about 12 to 15 building blocks on this page. And the goal will be to go into these pages and use whatever is logical to bring over that content. Now that means it's probably going to be laid out differently like these. I'm personally not a big fan of important text being hidden behind hovers, so we would probably use like an image columns block where there's an image with the text below it automatically. Me.
Elisabeth Hedge: Yeah. Okay.
Chris LaFay: And so before you get started on this and also these hero sections, there's no text on them.
Elisabeth Hedge: Oh yeah. It's just a picture.
Chris LaFay: It's a. It's a beautiful picture. You need text on these things. Not. It doesn't have to be humongous, but you need something there.
Elisabeth Hedge: It just needs to be a H1 that exactly what it is. Yeah.
Chris LaFay: So you know where you're at. Like, you actually went to the right place. And so we'll.
Elisabeth Hedge: Doesn't that also affect the accessibility, not having the header right there.
Chris LaFay: Look at that.
Elisabeth Hedge: Okay.
Chris LaFay: Also, this is not accessible either. Like this orange with this thin outline. So we're. We're ditching this style completely.
Elisabeth Hedge: Perfect.
Chris LaFay: And so all the stuff that we have, I won't say by default will be accessible because at the end of the day, somebody can put orange text on top of an orange background, but it should be easier to stay being accessible. I don't have my updated style guide on this computer. I have it on that computer. I won't be able to pull it up now, but before the content import process gets started, we'll sit down for an hour or so and just be like, here's our block library. This is what we're thinking. And we'll go through a handful of these pages and be like, these are bad ideas. Just pull the images with the text and just put them in like a column layout.
Elisabeth Hedge: Perfect.
Chris LaFay: This would be like the. See, whatever the actual, like, whatever we call like the cta that's just going to be. The CTA might not have a background image. It might. It might not. I don't know. But we'll kind of talk through some of those core pieces. Because at the end of the day, the point of these is to get a lot of the content on the page. The person that we're working with over there is a content strategist and can go and edit all these things later. So really the goal is to move it all over.
Elisabeth Hedge: That way they can edit.
Chris LaFay: Yes, in there.
Elisabeth Hedge: Okay, perfect.
Chris LaFay: And if we can find some, like, templates, meaning, like, I haven't looked at all these yet, but, like, let's say that all six of these are. All five of these use the same core layout. Let's go ahead and create it. Have you created Generically first and then be able to duplicate that generic one across multiple. So that is the plan, and that's. That's going to be the core of what we do together. Typically not 40. No, it's about 40 pages. Typically not 40 pages worth. Typically it's going to be somewhere around the like 5 to 15. But this one's a little bit larger.
Elisabeth Hedge: So is this your first project?
Chris LaFay: The lumber rock with the. Yeah. So they have. What I'm really excited about with them is this company is a part of a larger conglomerate that owns a handful of different, like decking and construction companies. If we knock this out of the park, they have. Multiple people there have told me all of their family websites are due for overhauls. This is just number one.
Elisabeth Hedge: That's awesome. That's great.
Chris LaFay: I would love. I hate this part. The part that we're talking about. I despise it greatly.
Elisabeth Hedge: Okay. I like it.
Chris LaFay: Which is wonderful. Exactly. So what. In terms of pricing, how do you think about pricing for this stuff? Because I realize the first one's gonna be a little sketchy because we're learning different things. Future ones will be a lot easier because once we build sites basically the same way all the time.
Elisabeth Hedge: Yeah.
Chris LaFay: So you'll be able to get a better idea for project number two if I just say, hey, here's the old site. We need 20 pages. Look at the old site. You kind of have an idea of our blocks. Tell me.
Elisabeth Hedge: Yeah.
Chris LaFay: How do you want to talk about it for this first go round?
Elisabeth Hedge: So I learned with David that I don't want to do like, a upfront giant payment if possible, because I want to make sure that it's more accurate because he tried doing like a. Here's all of the hours that we think it will use. And I used way less. So I think if you're okay with it, I'd like to do. I. I charge $30 per hour, so I'd like to do. For this first project so we can get an idea of how long it takes and stuff. Just by hour. If that works for you. Yeah, I usually just use a timer with Harvest, and we have Harvest, so.
Chris LaFay: We'll just get you added to our Harvest account so that you can just log out.
Elisabeth Hedge: Okay, perfect. So, yeah, I usually just do that. And then I can just invoice you.
Chris LaFay: You actually just do payroll, actually, so you don't have to worry about invoicing.
Elisabeth Hedge: Perfect. Okay. Perfect.
Chris LaFay: I. I know that when I was a freelancer, that's what I always preferred. And so that's typically how we do it, however, if you would like, if it makes life easier for you, you do not have to do that. You can send us invoices every other Friday and get paid that way.
Elisabeth Hedge: Yeah, so no, it's okay. I can definitely do the. Okay, payroll. The payroll is great. That makes it really easy.
Chris LaFay: What we'll do then, in terms of like a small micro project, what we'll do. For this site, My goal, the design phase is not going to take as long as it normally does because we already have their aesthetic locked and loaded. It's just more about rearranging development. I have found ways to expedite some of that because that's what I do. And so let's block off somewhere between eight and 10 hours as a starting point and that'll cover the hour so that we work together on. Hey, here's your block library. This is all the stuff that you have access to. Here's the old site where you'll download all your images from and all that kind of fun stuff and blah, blah, blah. Let's see what you can get done in that block of time and ask questions and things like that. Hopefully that amount of time should give you probably somewhere between like five and ten pages worth of content under your belt. Probably on the lower end of that. But if you find somewhere you have some efficiencies with them, then great. That should then be able to give you an idea of with much more confidence. Here's the rest of the 40 that we have.
Elisabeth Hedge: That sounds good.
Chris LaFay: Sound good?
Elisabeth Hedge: Yep, that sounds great.
Chris LaFay: This is currently indesign. We kicked off with them Monday. This will probably not hit for another 30 days or so. What I'm going to do is I'm going to get you in touch with my project manager who does a lot of my books and stuff like that. I have a very nimble team. We all wear multiple hats over here.
Elisabeth Hedge: Yeah, you're good.
Chris LaFay: And so I'll get you in touch with her to get your contract set up, get you into payroll, into harvest the whole nine yards over the next couple of weeks. And then a couple of weeks after that, we should have this set for the block library being ready to go. We can schedule an hour together, go over everything, record it all, give you access, and then you can have fun for the project.
Elisabeth Hedge: You're thinking, so May. So it would be May 15th to the 15th or how long are you thinking it would take for us to do so, like how. When do you want it complete?
Chris LaFay: So, like, if we could knock all of it out within About a two week span, that'd be great. So I like to think about starting things on Mondays. It just makes life simpler. So if we met on a Monday and said, here's your credentials, here's the block library, here's the old site, this is what I'm thinking in terms of how some of this weird disjointed content will kind of map to these new blocks to kind of give you an idea. And then how to use a couple of specialty blocks as well too, if those could be knocked out that first round by like Wednesday. So kind of that 8 hours ish spread between Monday, Tuesday, Wednesday questions, all that kind of stuff. We have a follow up on Wednesday where we talk about what the rest of it looks like and then finish the rest of it up over the next week and a half. And we'll have some touch points in there. It's like you finish your grouping of five pages, let's go take a look at it really quick.
Elisabeth Hedge: Okay, sounds great.
Chris LaFay: And I'm all about asynchronous feedback. Like I have zero issues with being sent a loom video and being like, hi, I did this. Do you have problems? And if I don't, perfect, great. We just save time.
Elisabeth Hedge: Perfect.
Chris LaFay: And I do the same thing as well too. It's not me being anti personal, it's just efficient. Efficient. And I like efficiencies.
Elisabeth Hedge: Yeah.
Chris LaFay: So that's good. Awesome. All right, any other questions at the moment?
Elisabeth Hedge: No questions at the moment. Probably more when we meet.
Chris LaFay: So yeah, and we'll have some. Like, if this goes well, they're going to have other sites. We also have another potential site where we're only doing Deb, but they need us for a little bit of content. So like there will also be like little. Another. Actually a good example of what would be extraordinarily helpful is. Let me show you because I just did these myself and I wanted to call my eyeballs out and I would prefer not to call my eyeballs out. Going back to the Consume Media site, what we ended up doing for them is they're going to actually write all their own content. And we had a wireframe for about five different page types and the wireframes didn't match up one to one with the actual block designs. But that's kind of not the point. The point is just a general storytelling practice. And so what we did was we went through. So like these are all their individual products that they have. So if you click on Learn more and testimonials. I created this layout using the building blocks. And some of these look familiar now that you've seen them.
Elisabeth Hedge: Yeah.
Chris LaFay: And then if you were to go to the other one, animated explainers. Oh look, it looks exactly the same. Like I copy and pasted this. Oh wait, I did this. Took me a God awful amount of time because they probably had about six page templates and about 30 pages and those six page was going to be the copy and pasted and then categorized under the right like page section. This is very common. Typically we don't do 30 of them. Typically we do about five to 10. And a part of our process that is extraordinarily slow because it lays on my shoulders is taking an existing website of content that the content's okay but it doesn't tell a good story. A general layout with blocks and being like we have these five core pages that we just need a layout put on the screen with just like the headline text written so that like the headlines are kind of like the chapters if you will of like this is kind of where the content's going to go. So like why should you consider this product? Sub product A, sub product B, projects that have this in there, Testimonials about this, etc. So like that right there is probably the most common thing that I will need help with because that is a blocker that probably only takes a day of time. That takes me two weeks to do because I hate it. So that is the end of my soapbox. But that's another common thing as well too. And that will happen. We have a couple of projects closing that we'll need that help for as well. So.
Elisabeth Hedge: Okay.
Chris LaFay: There will be.
Elisabeth Hedge: Yeah.
Chris LaFay: When I find my people, I keep them busy now it's not, it's up and down. Don't get me wrong. It's project work for the most part. But once I find somebody you into collective and you don't go anywhere at that point.
Elisabeth Hedge: So that's great. I like stick sticking around. That's why I have been with Becca and Leah since 21 and then we had a break and then I started with them again this January. So.
Chris LaFay: And tactic I am. Words cannot describe how excited I'm about this because I have a lot of the mental load of all this sitting in my head. I'm about to remove that mental load and that excites me. I will send an email to you and dawn and she will have questions for you to answer to fill out paperwork, all that jazz. I don't know what those are.
Elisabeth Hedge: That's great.
Chris LaFay: I'll let her handle those, so that's perfect.
Elisabeth Hedge: All right. Thank you so much, Chris.
Chris LaFay: Awesome.
Elisabeth Hedge: Thank you.
Chris LaFay: I'm sorry we're a few minutes behind. I do apologize about that.
Elisabeth Hedge: No, it's totally fine. Thank you so much, though, and I hope you have a great week.
Chris LaFay: You, too. Take care.
Elisabeth Hedge: All right.
Chris LaFay: Bye.
Elisabeth Hedge: Bye.