Okay, so as they said, I am Nick. I lead digital product for Life.Church. This is Cody. He leads one of the engineering teams on our team. And we are both pastors at Life.Church. Okay, so we are excited to share with you guys today about some of the innovative ways that we're using Magnolia to serve our attenders. But what I hope you walk away with, if anything, is that, you know, you're going to be a little bit more. It is always about the person that's on the receiving side of the screen. Everything we do is how do we serve that person in whichever way, whether it's us in the church context, are we leading them further in their faith? Or you guys, in a business sense, that might be how are we serving them with a good or a service or something that they, right? Okay, so to start, I'm going to try and contextualize a little bit our church, who we are as an organization, what we're about. And then what are some of the circumstances that we've found ourselves in that led us to the solutions that Cody is going to take over and share with you guys a little more about. All right. Okay, so who are we? We are a church of 45 different locations across 12 states. Okay, but a better way to say this, we're one church, multiple locations. Every church serves a unique community, a unique local context. But from a central standpoint, we have one senior pastor and one message that goes out to all those churches. However, all those churches are various places that have different needs. So we have to figure out how do we connect with those people in those locales, right? Okay. So, our senior pastor, Pastor Craig Groeschel, he founded this church in 1996 out of a two-car garage in the center of the country in Oklahoma. Okay? And when he founded it, and still today, our mission is core. And it is to lead people to become fully devoted followers of Christ. That's what we do. We wake up every day. Service of technology, meeting a person where they're at, serving them in a need, helping their family. It is all to help lead them to become more fully devoted followers of Jesus. So that was true then, and it's true now. Now, this is the centralized model that we operate out of today. When we started, I mean, we had a couple of campuses, and the staff at each of those campuses had to be really scrappy. They just had to figure out how do they do technology, how do they do HR, how do they do Fridays, all that. But today, with the scale that we've encountered, the growth that we've encountered, we've had to figure out how to scale. And so, we have centralized a lot of the distributable functions, such as HR, such as FIDER, such as technology, so that the pastors at the campus can focus on the person. Right? Okay. So, every week, we get a chance to serve millions of people, both physically and digitally. And at Life.Church Online, which you see here, we serve tens of thousands of people every single weekend. We also have a ministry called New Version, which is the Bible app. It is a ministry of Life.Church, and we founded it in 2008. Originally, the Bible app was one of the first free 200 acts of the Apple Acts. And that first weekend, we saw nearly 100,000 downloads. Right? So, we knew we were onto something. We had eventually created a second app called the Bible app for kids, and that was geared on a different audience and on regeneration. Eventually, we realized, because of the global nature of it, we had to figure out how do we service areas of the world that are less connected or have less data, you know, data-sized devices. So, we created the Bible app Light, which is already with the millions of downloads. It's only about two or three years old. Right? So, to underscore our organizational DNA, we build technology as service of ambition. Okay, so the through life, very different applications. Right? Life.Church, online, our physical campuses, the Bible app. Right? But one organizational conviction, technology should remove barriers, not create that. This isn't rooted in something deeper than strategy. Sorry, this is rooted in something deeper than strategy. And it is that we will do anything short of sin to reach people who don't know Jesus. Okay? And that conviction, ultimately, is what led us to Magnolia, that technology is a ministry in our church, and we have to find tools that will help us serve that ministry. Okay, so why Magnolia? So, let me define our operational reality that we encounter every single weekend at our church. And I hope when you look at this slide, you get a little anxious, get a little nervous, because there's a lot of people that walk through our doors, okay, that are trying to do very different things. And this is just one of 45 locations, about to be 46 locations, about to be 47 locations. Pretty soon, we'll be at 50, 70, 100. And we have to figure out how do we meet each of those people right where their ads serve them really well. Okay. So, that's the context on the weekend. Now, the problem we're trying to solve is our previous infrastructure created dependency. Any content update required technical intervention. There's a lag when every digital interface has to serve as many as a dozen different audiences. And they have to find the time to navigate the tools and not serve the person. So, again, just trying to highlight complexity of what we found ourselves. And that's what led us to Magnolia. It allowed us the authoring experience. I think you guys probably heard that term. I thought it was originally created by us, but apparently not. Apparently, other people could look at it. Right? But that was the deciding factor. It had to be something that a non-developer could use. It gave us the ability to set guardrails. That would become a gatekeeper. That's right. Content ownership could be distributed to the people who actually know the local context. They're the ones closest to the problem. And therefore, how do we empower them to solve it? Right? Okay. But before I hand this over to Cody and let him share about the solutions that we developed, in that spirit of honor, I want to make sure that I honor the people that we chose to partner with, which ultimately was one of the deciding factors. So, where's Flo? There's Flo. He's hiding out in the back. But Flo, you know, when we chose Magnolia, we didn't know much about the product, but the ability to connect with Flo, the investment he made back in us. For it. Sorry. Oh, well. Right. Right. It was just, it was, it was, it was, man, we're choosing to park here just to bend it. And then our implementation partner, I don't know if, if Dalfusion's still really on the scene, but at the time, Chris Briley did an incredible job helping us actually implement the tool. Chris, Bryce, Bryce, I'm sorry. Bryce. Chris Briley's my broker. I get him in these stuff. Okay. So, finally, we found ourselves asking this question. And this is the question I want us to sit on. Can the right person publish the right content at the right moment without weighing on us? Yeah. Yeah. So, so that question right there on the screen, locations had already answered it. We just found that they answered it with Alice. You see, at the locations, while we were trying to solve this centrally, at every one of the locations where they were, where the people were, they were solving it in their own way. Right? Some of them were solving it via QR codes on the screen. This is how to connect with us at this location. Or some of them used a tool called LakeTree. You may have heard of LakeTree. Right? Others were a little bit more savvy. They had you put NFC chips on the back of chairs. And this is how you'd connect with us. So, we found ourselves building tools and building things where our locations weren't using the things that we were building now. But we were still trying to solve. We found 45 locations solving 45 different problems. 45 different ways. They're following me. And because of us, we had no visibility into what they were building. We had no way to track what they were building. We had no way to support what they were building when they would come back to us and say, hey, we need help. So, there was no data. There was nothing for us to come back with. And the important thing to know is that there's actually no single frictionless path for the end user to take a meaningful next step in what we want for them to have. Right? So, that's the problem. So, let me talk to you about what we built. So, you're looking at something that we call the Life.Church Now. And it's three entry points, but it's a single experience. And it's available on the seat back in front of you in person, in audience. So, imagine in your chairs right there, there's a seat backs tag available for you. So, you have a seat-back tag. You can tap it or you can scan it. It's your choice. It works iOS, Android. If you have our app, you can use it right on the home screen. You open up the app. The location part comes up. And it brings you right into the experience. It's your local experience to where you are. Or you can do it directly via direct link. So, you can have a text to you. It can be shared to you. It can be emailed in any other way. Whatever you want, it's available. So, three experiences, but one entry point. We call this a seamless multi-platform experience. It doesn't matter the method that it's brought to you. So, for the two outside of the app entries, right? So, the seat-back tag or the direct links, it's the same experience whether or not you have the app. Right? The browser just simply opens up. The operating system will take you to the page. And then it will actually invite you to download the app as well if you don't have it. But if you do have the app, Universal Linking will just take you directly to the pages that you want. Again, it's the same experience. So, we want whether or not you're deeply ingrained in our church or whether or not you're there for the first time, we want you to have that exact same experience. It doesn't matter where you come in. And what ended up happening is the strategic impact of this is this tool became both a content delivery tool, which it was supposed to be. We found on the other side that it was an app acquisition tool. It was working quietly every weekend in the background. We saw people kind of moving through, I'm new, I don't know anything, to I'm really now engaged because I came in through the web, I came in through this other experience, but now I downloaded the app and now I want more. I want more. Like, you know, they were more engaged. So, we talk about 45 locations, 12 states, cross, and any multi-location organization knows is that to keep global standards while keeping the kind of local autonomy, the genuine feeling of being small and connected, that's the struggle, right? That's the pain that we're always fighting. So, the question we have ourselves is, how do we hold both of these states? And for us, it kind of came between these two intersecting workspaces. And so, Nick talked about it, right? We have this kind of centralized workspace that are across the top and it's our marketing teams, it's our communication teams, it's our central teams that's developing our content that needs to exist across all 45 locations. So, we can build it once, we can push it out, and there's standards, and there's all the things that you want at that level. But then you have this vertical workspace, which is the local campus. And so, they get the horizontal, right? But it's the, hey, I'm your campus pastor. I'm the one that you're seeing on stage every weekend, and I want to connect with you. It's the events that's happening on the weekend, or it's the centralized next steps that's pulling in from the global team. And so, what we found was that it was this horizontal and vertical intersection that meets that genuine feeling that people were missing in a large multi-location organization. And so, what happened is the complexity, it was centralized and solved there, but the humanity was local. It was built locally at the church level. And so, the cool thing about this is that this architecture, as we built it, it scales in two directions. So, Nick talked about it. We could scale really infinitely for our ministries or for our locations. We have 45 today. We're going to go to 50. We'll go to 75. We have goals to hit 100. But nothing has to change from our architecture. It can scale infinitely. But it can also scale in depth, right? So, there are ministries, what we call like men's ministry. You want to meet with a group of men or a sports ministry. Every location is unique to what they want to provide for their community or what's popular in the community. So, it can scale infinitely. And because of Magnolia, this two-workspace architecture was just really built out of the box. We didn't have to write any code. We didn't have to change anything. We can scale deep through our ministries. We can scale wide through our locations. And it's just built on top of what Magnolia built for us. The cross-workspace references, these kind of page-to-art-phys that we're talking about, we'll try to go past and develop. But we knew this architecture was only as good as the people that could use it, which is why the authoring experience was that term again. It mattered more to us than really anything else. And so, let me talk to you about why. Why did this matter so much? Just because for us, our authors were the people at the campuses. They didn't get into their roles to deal with technology. Most of them actually were kind of afraid of technology. They didn't know how to use it. And so, we built this. And they took the roles because they wanted to be present with people. We built this in a way to empower them. And we had to build something that actually just disappeared in the background. They didn't have to think about the technology. So, as you see in Magnolia, right? It's an in-editor experience. What they saw in the editing experience is what the campus attendees saw every weekend. It's the same experience. It's a welcome here. It's the heading. It's the here's your event that's happening this weekend. So, they were building out the weekend experience right there. But on the top, we built in, hey, here's your lifeline. Here's support. Here's copy-paste templates that you just bring in. That's, again, it's just choreographed content that you can bring in. Here's support documents. Here's runbooks for you. Okay, Fanny, let me, as creatures often can, we go over on time. We get, so we're rid of it a little bit short. Are you, so we're getting the time? We got three minutes. Three minutes. All right. Should I talk to you? I speed it up a little bit. All right. So, how easy is it to add content to pages? Three clicks, okay? I can do that in three minutes. I'll do this. You go to page. You add a component. You select a card. You hit save. That's three clicks. Three clicks to put a meaningful next step in front of hundreds of thousands of people every weekend. And that's how we needed to make it so simple. So, before we get to this, well, let's do this. Have you guys paid attention when QR codes have gone up on screen? And trust me, I know the irony in this, because we're going to put QR codes on the screen here in a second. Have you guys watched the room when people try and get you to engage with a QR code? Very, very few people do it. Or if you try, it's gone before you can get your camera out, right? Or you can't quite get it. And we just saw that in our church. We could not engage the audience. This is the process, right? So, yeah. We're all going to have you do. I was going to have you experience what we felt every weekend, right? It was that. It was people trying to scan a QR code, and then it goes away. And what happens, right? You can't find it because they go fast, and then you're looking for what it is. Or it's something up there that may be personal to you, and you don't want anybody to know that that's what it looks, right? So, that's the cost of a QR code. So, the NFC chip that you just tap on the front of your chair is much more intimate. It's small. It's between you. But you can still connect with your location. I need prayer. Or I need help. Or I want to meet you. I'm new here. Yeah. So, let me talk to you a little bit about the numbers, because sometimes it's about the numbers. So, you have over here 6%. We said nothing or did nothing as we made it because of this. And out of the box, we got a 6% conversion rate from the tools we were using before. Simply by putting a sticker on the back of a chair. We'll walk through this a little bit quicker. The no phones out moment, 20%. That is just acknowledging the sticker on the back of the chair. It's there. Do it. We've talked about it a little bit more. We get to 21%. Hey, there's a sticker on the back of the chair. You can connect with me. Every step we talked about it to the phones out moment. Hey, I'm here. Connect with me. Take your phone. Let me show you how it works. Yeah. We got to 32%. 32% over 100,000 person weekend is about 30,000 people. That's right. If you're just physically, right? Yes. Physically. We love to say this. Every number has a knee. Every date has a story. And every story matters to God. That's right. So that's why every number up there matters. Sure. More than just a percentage. But it's an actual purse. It's lit with a store. You take it. So the numbers are at the points, right? So behind every date up, right? Is that purse? Because for us, when we launched this in December, it's the most strategic, impactful month of our calendar year, Christmas. Christmas, we know that is the one time a year that if someone is going to go to church, it will be Christmas services. Or the only time ever that they may go to Christmas services. So behind every data point is a person. Someone who took a step that they may not have taken otherwise is what this tool empowered. So Nick started us with this, right? I'm down. Can the right person publish the right content at the right moment without waiting on us? And for 45 locations, they can. This is what Magnolia empowered us to do. And this is what Life.Church now is. And for record, we know that that's the old brand. We're going to wear it too late. But we'll get around that stuff. Thank you so much.