Welcome back everybody. Good morning, at least where I am. This is day number two, officially being out here. Yesterday was setup day. Saw some sign there at the end of the day of some elk, which is great. So starting out fresh today. I got this platypus system. I filled up with water last night and it's literally just, it's like an IV system. So it's filtered water and this is what I'm using to make my oatmeal and my coffee this morning.  So last night the area I found, I marked some spots on my GPS. I'm gonna track back that way and keep going deeper.  It was, I was just out of breath. It was bad. I'm gonna lighten my load a little bit on my pack and I'm just gonna day hunt today and see if we can find at least more sign. Really just put together these clues. I've also been communicating with Lunkers TV through our in-reach devices, our GPS devices. And so we're comparing notes and everything. He's been out here a lot longer. He's given me some some good tips. So let's go make our coffee. Can't get the day started without a good pot of coffee. Let's get in the woods. Okay so we've made it up here about 500 more feet in base camp. And I'm along one of those trails that I, where I'm trying to find a good elk trail that I was seeing yesterday. I am burning up. It's 41 degrees and I'm burning up. I've got a lot more to climb. I'm gonna try to get as high as I can and then just stay on that plateau and walk a few miles and see what I see. I think that they're gonna be pretty high this early in the season. But the thing about this area is it's so thick. You can't really see too far so I might just end up running into them. We're gonna sweat a little bit. Let's keep going up and see what we see. I found a creek right here. I'm starting to see tracks. Like they'll definitely walk along this creek line. So I'm gonna follow it up and then I'm gonna push farther north, northwest and just ride this plateau. If you look at it on a map you'll see a lot of these just they're not like sharp mountain. They seem really sharp when you're up here. But they kind of flatten out and there's some grassy patches on top. I think that's where they're feeding either that or just smack dab in the middle of woods and it's gonna be hard to see on an aerial map but this is thick. It's absolutely gorgeous though. Alright, catch my breath. Let's go up another 500 feet. This area I'm getting to is more open. It's like I've busted through the thick thick stuff. I think all these trees are laid down. It's a pain to get over them. This is so much steeper than what it looks like on camera. I noticed that on my New Zealand hunt. Like it was so brutal. It didn't look as bad on the camera but trust me the calories are burning. I'm also starting to get into some rocks. These more open areas that grow. I've decided to just go after these elk. After ranging that spot is 350 yards away. Probably take me an hour to get there. I go all the way down but I just walked up here and I found a little chute and that's gonna cut my time about half. So this is good. This area right here is prime. I'm feeling I might need to spike out here. I don't get it done today. It's high hopes if I get it done today. But first thing I see it's not a spike. Anything it's legal. Cow, legal bull. Arrow's going. That's fine. So we've got to cross this little ravine here. This river, creek, stream whatever. I think they're going deep into the woods right now so I'm gonna go where I saw them and then track from there and just make sure the wind is right. Oh yeah see where elk cross here too. See I was gonna have to go through here. That is looking like death. This is perfect. I wonder if they bed right here. All this is laid down. Tons of tracks. Fresh, fresh poop. Oh my gosh we're on the juice. Tons of poop. This hunt just got. I'm pretty much above them now. I'm above where the trees grow. I'm like right on the line. I'm gonna stay above and I'm just gonna keep going where I saw them and I'm gonna try to get above them and just just look and see. It's gonna happen. I'm gonna get the chance. This is the area where I saw the elk. I've worked my way up here. Came back around. Didn't see any and I just just wanted to stop right here and see. I mean it's just they were all up in here and the tracks are just everywhere fresh. So what I'm gonna do is I'm just gonna follow their tracks. I'm gonna follow where I saw all of them exit through here and just keep stalking them. The wind is actually good. It's blowing up the mountain a little bit in my face walking this way so I might be able to stalk them. I don't know how fast they're moving but I know they got much bigger legs than me and they do this every day. This is so exciting. I consider today a win just being able to see elk and get within 350 yards. Now I just got to figure out their little movements. I know their bedding areas. I know this is a key feeding area and what they're doing at certain times of the day. I know about 8.30 this morning it was rocking so go see if we can find some. Maybe they're bedded down. They're being real silent. I haven't heard anything so keep trucking. It's not the top but it's closed. There's a big wallow out there and I just heard a bugle. I don't know if this is the same group of elk. There's more bedding areas over here. I'm definitely at the right elevation. I'm seeing tons of sign. Try to call a little bit. Get a little closer to that bugle call. Just made it off the mountain y'all.  What an amazing morning of hunting. That was my first experience with elk ever and it was a workout. I mean I was all the way up there and more and then some deeper on the other side but I figured out where they are living. I know a vast expansion of area where there's tons of fresh sign and I was seeing them. Unfortunately I spooked those ones when I got around that waller area. That was about 40 yards and they kind of split up and then I went down to another spot. Tried to kind of follow them and there was there was a spike. I was glad to know it was a spike like it was just laying down and I've glassed it. Recognized it was an elk. Got ready and as soon as I got up it got up too and I saw it run off and it was a spike so I can't shoot those. So the strategy now I think I'm just gonna have to go up there and sleep with them like take my tent and just take food and be up there for a number of days. Unfortunately that's not gonna be this afternoon. I need to go get some more supplies for my big camp so that I can eat stuff there and then have stuff for up in the mountains and it's a lot to think about when you're out here getting a game plan together to have a successful hunt and fishing trip and just make your experience more enjoyable. What I love is you know I'm just sitting here parked on the side of the road here in the National Park and I'm trudging up the mountain and I'm seeing elk and I never saw another hunter y'all. So this is a pretty awesome experience that anyone can go do. It just costs you I think it's $680 for a elk hunting tag and of course I mean you gotta have some gear if you want to be a little comfortable. But thank you guys for tuning in. Of course we will be after these guys again and doing some more hunting and fishing trips. I spotted some other fishing areas that I wanted to go to on the map today. But thank you for being here. Make sure you smash that like button for seeing elk for the first time here in Bugles and the Great Outdoors. And I will see you on the next one.


it's good to see everyone's names in the chat. I'm very excited to kind of discuss and bring one of my fabulous experts and colleagues along the ride with me today. So we'll be actually talking quite a bit about what a CRM is and sort of what we can see and expect from a platform like HubSpot. But before we dive in, more formal introductions. Some of you may recognize my face from other TechSoup webinars. Some of you may have joined me last month where we discussed persona development. But for those of you who I have never met before, my name is Whit Godden. I am the director of strategic marketing here at TAP. I've been very fortunate enough to spend the last two and a half years working incredibly close with the TechSoup team through the design and management of TechSoup's digital marketing and website services. And we also, along with Janelle, we're also really big contributors to building key educational materials like this webinar today. Along as well as courses and blog articles. So I'm Whit. I'm going to go ahead and allow Janelle to introduce herself. Thanks, Whit. I'm Janelle Beck. I'm the director of digital growth here at TAP. I spend a lot of my time strategizing, developing and implementing various nonprofit solution across really all the different digital spheres. That includes web development, marketing and operations. I also act as our technical strategist for CRM projects, especially through HubSpot. And I do a lot of the automation and management moving forward for our clients. You'll also start to see my name sprinkled across the web on the TechSoup site. I write a lot of their blogs focusing on website and marketing solutions. Awesome. Yeah, she's the brands. I'm more of like the puppet at the front of the show for like a better terms. But thanks, Janelle. I'm really excited to do this with somebody else for once. And I'm glad that you're able to join me and pass on all of your expertise and knowledge. But before we dive into that, what is TAP? Who is TAP? So a little bit about who we are. We are actually TechSoup's marketing technology partner. And we strive to empower organizations for good. So what does that mean? It really basically means that your vision is our mission. As I mentioned over the last two years, I've been sort of spearheading alongside Janelle and some of my other colleagues, our partnership with TechSoup delivering the digital marketing and website services through the TechSoup marketplace. But I think it's also important to note that for this particular webinar that here at TAP, we are actually a certified platinum partner with HubSpot. So we have had a lot of experience building and implementing a CRM tool. And we're very, very excited at the opportunity that is coming up. And that has been presented today through the partnership between TechSoup and HubSpot. So we'll kind of dive into what that looks like closer to the end. But for today, I really just want to give a special thank you to HubSpot and TechSoup for kind of coming together and recognizing that in order for our nonprofit organizations to really thrive within the digital landscape accessibility to these different platforms is really, really paramount. So we'll get into sort of what that looks like at the end of the webinar today. But before we kind of get into that, as you noticed, it is a HubSpot webinar. But before we dive into HubSpot specifically, I really want to make sure we're allowing for enough contextualization of what a CRM is and what it does and how it should exist within your marketing strategy. So we'll start off today with kind of a brief highlight of what inbound marketing is.  It's the methodology that Janelle will kind of talk us through. And then that will help us better understand and build a framework to really look at what a CRM is and what it can and what it really should do. And then really focusing on it, how it can increase your organization's communications effort. We will end today's presentation with highlighting four key strategic tactics. Now, these are just four. We don't want to bombard you. I mean, Janelle and I, as we were preparing for today, I think we both agree, like, we're very passionate about this topic on both a solutions end as well as sort of like a strategic and strategist. I'm a digital strategist. She's a technical strategist. So you can only imagine our coffee conversations at the middle of the day. So we're going to just leave you with some breadcrumbs of what four key strategic approaches. So we'll kind of look into collecting your information, segmentation, AB testing, what is AB testing, and how it can differentiate, and then marketing automation. So without further ado, I'm going to kick it over to Janelle to talk us through a little bit about what inbound marketing is. Awesome. So like what was saying, it's really important to have a better understanding of what this CRM technology is really built on and the methodology that drives all of all of these tactics. As we look at marketing, there are really two major buckets. One type is known as traditional marketing. You might also hear it referred to as outbound marketing or push marketing. That might be something like a billboard or radio ad, a flyer, a TV commercial, the goal there being to get your message out to as many people as possible in the hopes that the right audience is in there somewhere, we'll see it and then we'll act on it. The obvious challenge here with outbound is that especially for nonprofits, you're competing for the same space both physically and mentally for your audience with companies who traditionally have much higher budgets to be bidding against you. Luckily, we have another form of marketing which is known as inbound and it looks to essentially take this and flip it on its head. This methodology has been gaining a lot of traction within the B2B and nonprofit sectors because of the way that it really pulls your audience in instead of competing dollar to dollar for the attention of your audience. You might also hear this called content marketing, pull marketing, inbound marketing and really all this means is what we're looking to do is take your right, the ideal audience and deliver the right message to that right person at that right time. What does this actually look like? Inbound marketing is really split into four key stages and that seeks to drive a five-stage conversion pattern. What inbound marketing looks to accomplish is to first attract strangers to your organization through such tactics like blogging, keyword targeting and social media. Those methods really help you to turn strangers into visitors on your website. Once you have visitors on your site, what you're looking to do is engage those people into becoming leads and you can do that through forms, call the actions and landing pages. The idea here is really to just initiate enough interest to capture that potential supporter even if they haven't reached their end goal or their intended activity so that we can continue to nurture them through our systems and through our pipelines. Once you have them in your system, that's when your CRM really comes into play. You want to work to convert that lead into a supporter with email marketing and automated communication which is just known as workflows. The main difference in inbound marketing compared to outbound marketing is this next step where the actual relationship building doesn't end with a conversion but we're looking to delight those supporters into promoters and we do that with surveys, social marketing and smart content which is essentially just content that adapts to the person who's interacting with that piece of content. Once a person is a promoter, what they'll do is they'll be so interested in your organization and their mission that they're going to be bringing in more strangers and visitors to then repeat this process. So essentially this becomes a big cycle or a pinwheel that turns into a well oiled machine of organic and natural and sustainable support for your organization. And everything you see here can be accomplished within a CRM like HubSpot from all of these stages and all of the tactics that we're going to be putting into play. Now I'll hand it back to Whit so that we can really define what it's like to leverage a CRM. Awesome. Thank you Janelle. So the question that some of you might be having right now is what is a CRM? So I'm going to start off with a little understanding. Now that we have the understanding from that inbound marketing, we're going to kind of dive into the definition and then kind of explore what those functions are and then we're going to see those functions in action. So here it is. A CRM stands for Customer Relationship Management or Manager. It's a tool or a database. It's a tool for organizations to better manage your contacts, automate your data entry, design effective communication strategies, and provide an accurate reporting for teams and stakeholders. So what does this mean? So let's unpack this a little bit, right? So when someone fills out their information on your site, the CRM is where you kind of store all of that information. And then depending on that CRM, whether or not it's a MailChimp or a Salesforce and then this case, and yes, Nicole, we will get the deck to you at the end of the webinar, so don't fret. What you're able to do with that information and organize and then make necessary actions against that information is really going to depend on the platform that you have. So you may know and traditionally some of you might be using an Excel spreadsheet as your CRM database and you're kind of leveraging it that way. But really what we're looking at is being able to organize them into either lists or tags and in HubSpot we call those properties with the necessary data information that allows us to make follow-up decisions on how we want to engage with that person, whether or not that is posting on social media, writing content on your blog, building out landing pages. So think of those like buckets or those different tags as maybe donors or maybe donors that are $100 donor a year. Maybe you have another tag that says that these are the $500 donors. So being able to kind of segment and we'll get to that kind of that piece there is really the main functionality of what a CRM is and then being able to integrate that information and integration is basically connecting two systems together to be able to make actions based off of that information. So for example on this diagram here I have a little layout, right? So we have our four supporters or four donors, their donor information whether or not you're collecting donors on classy or give lively, whatever the platform is, a platform like HubSpot can integrate into that donation platform and actually bring in those details. How much money, how much, how many donations, what are the value of those donations? Other things could be volunteers, other things could be partners, supporters, sponsors. You can kind of develop a lot of these overwork those, bring all of that information into your CRM and then being able to either follow up and market through automation, automatic email systems, through conversations on the back end amongst team members. So if we're both working on a particular stewardship opportunity with a with an individual contact, it's helpful to have that collaboration tool be able to have that information on the back end and see when did Janelle email that person and is there something for me to follow up on all that living within this database. And then I think the most important part and where a lot of nonprofits I think have an opportunity is to be able to report against that data effectively, efficiently and accurately, right? So when we talk about a CRM you might hear the term, a central source of truth, right? So being able to ensure that you have accurate data that you can also measure and build reports against can help you grow your organization through building out infographics to showcase your impact and drive donations. It could be a way to show your supporters or your sponsors the efficacy of your efforts. So it's a really, really strong tool for everyone to be considering implementing into their organization. So I'm going to pass it back to Janelle and let her kind of talk through some of the key sort of functions that a CRM should be able to do for you. Thank you. So first I just want to address kind of in the chat. Salsa is another kind of CRM definitely targeted at nonprofits. I think from everyone's comments it's less user friendly. One of the reasons why we love HubSpot is because it doesn't take a developer, it doesn't take an expert marketer to be able to start to utilize it. So we'll look more into what HubSpot can do and its usability but just kind of keep that in mind that Salsa is definitely not the only solution for a good CRM. So in terms of a CRM the actual functions and capabilities are going to vary a lot from platform to platform and even within that platform depending on the level or the subscription that you have those functions can really vary. However there are really these five key functions that we want to make sure a good CRM solution has so that when you're looking to implement one into your organization you kind of know what functions to look for and that you should be looking to implement. So the core function of a CRM like what we've been talking about is just contact management and simply this is the way that you store, track and manage everyone that comes into contact with your organization. That could be a volunteer, a donor, a company, sponsors, potential supporters or even the community that you're serving. What this allows you to do is to start to think of your contacts more like a business does as if their leads to be nurtured through your pipeline. Even though we aren't traditional businesses it's important to start to think that way so that we can leverage our communication and our outreach to form longer lasting relationships which is going to create that sustainable support for your organization. The third function that we're looking for your CRM to offer is email management and this should really include all of the phases of email marketing from designing to writing to sending those emails. This is really important because we're going to be spending all this time collecting information on your audience and the way that they're interacting with your organization online and we want to be able to take that data and then send out emails based on those triggers of their activity or their demographic information. Another cool feature of a CRM would be to actually use it as an internal resource. Keeping all of your information files and content in a centralized and cloud-based system allows your organization to stay consistent online. This will really help to streamline your outreach efforts as we increasingly move to a digital and remote environment. You'll also be able to bring in additional stakeholders so that they're able to leverage the same materials that's available to your internal systems. So for example if you have a board of directors who are going and doing outreach giving them a certain level of access to your CRM will allow for a comprehensive place where you can have your marketing materials your collateral meeting notes and the most up-to-date resources that they can use. And finally you have the fun part and this is the stuff that I'd like to focus on which is the reporting and analytics. This is where all of your different efforts are coming together so that you can collect, manage, and really disperse data that is clean and consistent through both custom and templated reporting so that you're able to see how your organization is really performing. What this will allow you to do is get kind of a baseline understanding of how your organization is functioning online and that will allow you to grow over time. You'll be able to start to get a better understanding of where your contacts are coming from, the time it takes to move through your pipeline, how many touches or pieces of communication it takes to make a conversion, what your conversion rates are, how your traffic is growing, and really all the ways that all of these tactics are growing and improving over time. What these reports will allow you to do is really to start to learn how to improve, test out new ideas, and most importantly figure out which channels and digital tactics your resources are really best spent on. Another cool feature of having a nice clean and robust reporting system is the ability to create easy to access dashboards so that you can report back to key stakeholders whether that's how you use your funding, the amount of people that you're interacting with or supporting, and have that in one comprehensive place. So now I'll hand it back over to Whit so we can look at how this has actually started to make an impact across nonprofits. Thanks, Janelle. Yes, I promise we're going to get into the inaction piece, but before we dive into that, just now that you kind of have an understanding of like what a CRM does, I wanted to just highlight a few key metrics out there that I was able to find regarding sort of like the impact that or that CRMs have on organizations that are actually leveraging these types of tools, and I'm seeing a lot of suggestions in the chat. That's awesome. There is no one-size-fits-all for a CRM, so definitely do your homework, and I think there's a lot of great solutions out there, but this is a metrics on overarching sort of CRM utilization. So what we saw, what we were able to find through different surveys online and reports online, is that 74% of organizations have stated that the CRM technology gives better access to customer data. I think this goes very well into what Janelle just explained, is being able to develop and build out those reporting tools, whether or not it's what you need to do from an outreach perspective, or a way to report from internal conversations, that's to stakeholders or to your board of directors, whatnot, so you can really show the actual clean data and impact, and being able to have everything centralized, rather than I've had some clients where they're managing things from their inbox to an Excel sheet to CSV file with all their donors, and they're trying to kind of put them all together, and the opportunity for human error is much higher, right? But rather than being able to just kind of go in and click one button, and then all of a sudden you have a beautiful report, and you know that it's clean, and it's easier to access, and anyone can access it. It's not in my inbox, it's not on my computer, it's built, and it's saved in the actual CRM, so anyone with access can actually get there. 92% of organizations believe that a CRM is crucial to delivering more meaningful relationships. This goes back to really understanding who your donors are, and how, or sorry, who your contacts are, and how they're engaging, right? And then making the appropriate decisions when it comes to communications through email marketing, social media marketing, landing page development, all of that stuff, and we'll get to, when you get to this in action piece, there's a really great tool that is available on HubSpot that can really deepen your knowledge of your contacts, so that you can build much richer and more meaningful relationships as you continue to engage with them across the platform and across your efforts. And then there was a 27% increase in customer retention for organizations using a CRM, so a lot of nonprofits we talk to and work with are like, how do I get my one-time donors to become a repeat donor or an ongoing donor, right? That's a strategic content, strategic marketing, strategic decision, and plan that needs to be built out, but you have to have one, the information, and then two, the tools to actually execute that strategy. So by having a tool like a CRM with an integrated marketing hub or marketing platform or marketing tools, you're more likely to capture and retain that individual donor to continue to come back to your site, find rewarding elements of what your organization does, and then hopefully the goal would be to either make another donation or become a repeat donor or supporter of your organization. So now we've come to the point, oh, I'm sorry, I jumped ahead of myself, one last piece here is I want to kind of go through, I'm going to pull my experience working for one of my favorite old jobs in the back, back in the day, is really understanding the features versus the benefits. So as we talk through these actions, these showing you some like use examples of how to like leverage these different tools, knowing what the feature is, and then how does that actually benefit an organization? So you heard Janelle May reference it a little bit, we'll kind of show it again, a workflow automation. So a workflow automation is essentially the ability to set a set of steps or triggers to happen on the back end. So when a donor signs up for this or makes a donation, is there an automatic workflow that says they donated this, have they already donated X, okay, let's bump them up to, you know, our platinum donor, and then you have a section in your CRM where you can see everyone who's donated in lifetime or for that year $500 or more. This really allows for you guys to build on nonprofit organizations to build capacity, because you're not having to do that manually. It's all getting done through a workflow, and it also allows to maintain consistency. There's no, there's less likelihood of human error or a miss trigger or a miss send because you have a computer, the AI kind of doing that for you. I'll also show an example of a workflow automation as it relates to email marketing, which I think is a great opportunity for nonprofits to start leveraging. Customization. If your CRM is what it is, it's a little bit challenging. So you want to be able to allow, you want to have a CRM, like HubSpot, that you can customize and really make it work for your organization. What are those, what are those tags, tagging systems? How do we manage our lists? Being able to, how do we build the reports that are actually important for us? You're not kind of pigeonholed into a turnkey solution. You have the ability to really customize those features to make it work for your organization. Integrations. I touched on in the beginning, how does one system connect to another? Those systems are so crucial to ensuring that you have real time and accurate data. So being able to connect into your donor platforms or other platforms that you might be using for reporting tools or I'm working with a nonprofit right now that does wholesale for farms. So connecting to their ERP and being able to bring in all those order information and then track all that information within the CRM database. Integrations are such a crucial and important piece so that you're making sure that all of your data sources are connected and they're staying accurate and they're updated in real time. Customer service. Definitely an important feature of any CRM. I'm sure we've all experienced it with multitude of different software solutions out there. Something's not working right or you don't know how to get something to work right. You know, it's important that whatever solution you choose has a strong customer service so that you can better understand and use the systems to its most, the best of its capabilities. Social media management and monitoring. This is another really important component as you're looking to manage your CRM data and CRM contacts. Being able to measure and understand how did this one social media post actually make an effect on this final number whether or not it was your donation or your volunteer acquisition or maybe a program participation if you're trying to kind of run that. So you can having that leverage point of being able to tie it into your social media management and of course monitoring the ability to respond and engage with the people who are actually interacting with your content is really, really important. Meeting scheduling. This is, there are so many different solutions out there but it's very helpful if it's built into the context that you might be working with right. Especially if you want to keep a track of how many times have we met with this person. Where are the notes from those conversations. And then in some cases a live chat feature is a really, really great resource to have. So if I'm going to your website and I need to find a resource I can type it into either a live chat or an AI bot and that can support your visitors finding what they need or who they need when they're visiting your site. So now that we've kind of really unwrapped all of this stuff about inbound marketing, CRMs, what it does, what are the important features. We're going to dive into really showcasing these, some of these features in action. So I'm going to kick it back to Janelle and she's going to talk us through the first two. Awesome. All right. So first I just want to touch on the examples that we're using here are HubSpot specific. I see a lot of people in the chat talking about CRM options and there's definitely a lot out there in the ecosystem. The reason why we love HubSpot and really work with them is because if we look at the different CRM options, HubSpot falls in that place where power meets ease of use. So as we walk through these, we'll get to see exactly how it looks on the HubSpot, but the tactics and the methodology behind it can be applied to the different CRM systems that we're all discussing here. So we keep talking a lot about all these contacts in our systems, but what's really important to understand is how they're getting in there and one of the most important ways is forms. So forms, if we think back to that inbound methodology slide, it's a way that we're converting visitors on our site to leads.  So for example, if you're asking someone to sign up for a newsletter, that's a pretty low value ask. Newsletters are pretty easy to come by. There's no one-on-one communication needed and it's easy for your organization to deliver on that promise, right? Asking anything more than their name and email might turn them off and not have them subscribe because you don't have that relationship built yet to ask them for more information. As you build out these forms in the form fields, it's important to always remember, is it more important for me to have this information or for this visitor to see what this value is? Your newsletter is a great way to build relationship over time because you're using it to show the good work that you're doing in the community, the events that you have, the impacts you're making and that's more important than having a full-fledged contact record of everything that we need to know about this person eventually. A more comprehensive form would be something like a contact best form, right? That person is asking for a bigger value. They're requesting a one-on-one communication and that allows you to ask for more form fields. Maybe you're asking for more in-depth information about how to contact them, the role that they play within your organization, and the reason for reaching out to you. We can skip to the progressive form fields. One of the reasons we also love HubSpot is because for every feature that you have on HubSpot, you're able to grow as your organization grows and increase the complexity and the way we target information in the system. If we start off with basic forms over time, what we want to do is make those more complex so that the data that we're collecting is more clean and efficient. Progressive fields allows you to make your form smarter and more efficient across your website. With standard form fields, the way those work is the same fields will show in that form regardless of who is looking at that form or who's interacting with that piece of content. But if you have progressive form fields and that person comes and fills out a form for the second or third time, we don't have to keep asking them the same contact information, and that allows us to build out more information about that person over time to get a better sense of who that person is all around. Another way we can do that is to actually have those progressive form fields change on the form itself. For example, if you are an educational-based community organization and you're looking for volunteers to sign up, but your volunteers need a master's degree. Maybe it makes sense to ask them yes or no if they have a master's degree and then trigger more form fields to show up live because you know that they're a valid lead for a volunteer and then you can build out that application. All right, so the next piece we're going to look at is segmentation. So the information that you're collecting on these forms are brought into your CRM as properties. Properties are essentially just pieces of information or data that you can collect about a contact or company, and this allows you to learn more about your audiences over time and the demographic information that's similar or patterned throughout. This data also allows for more personalization over time.  This allows you to create mass marketing and mass communication without losing that personalization piece or the feeling like you're having a one-on-one communication. So for example, if you look to send a follow-up email to sponsors, to everyone who gave a sponsorship for a fundraiser that you just had, you can write one email one time and then use that forever, and what that would look like would be inserting these personalization tokens into that email. So, hi, First Name. Thank you and the team at Organization Name for sponsoring Event Name, and that all happens in a massive way so that you're able to cut down on that administrative burden that it takes to follow up with everyone without losing the relationship building piece. Another key piece of what segmentation allows you to do is actually build out lists of contacts based on either behavior or information like demographic information. These lists is what helps you power targeted emails and personalize your website content depending on the audience that's viewing it, and this is what ultimately powers your marketing automation. Lists can also help you keep track of who's in your system and keep your data really clean. So you're able to see who's a volunteer, who's a donor, who's a board member, and have a quick list to reference moving forward. You can also cross-reference the data that you have to determine the contacts in your system who are not current stakeholders, but you believe can be more easily nurtured into a conversion. So what does that actually look like? Let's take a donor for example. Say you have a list of donors who've contributed $500 and more in the last year. What we can do is analyze all of the properties that we have for those people and look at patterns and then start to make assumptions for who else we can target based on that information. If your donor base starts to share or have patterns on demographic information, maybe their job title, their industry, or how they've interacted with your organization such as Attendant Agala, what we can do is we can cross-reference with other stakeholders in your system who have not donated and then send targeted information to help that conversion happen. And for anyone who's a little advanced out there, the next step in that process would be to take that information and apply it to advertising. Google ads, Facebook ads, LinkedIn ads. Once you have a clear idea of what those properties are and what the demographic information is of the people you should be targeting, that will make you able to build out these ads without spending a lot of dollars to reach large people or large audiences by knowing exactly the types of people who are more likely to convert. Awesome. Thank you, Janelle. So the other two kind of inaction moments that we're going to discuss on, the first one is A-B testing. Now, if any of you guys have been on any of my other marketing webinars, you may already have heard this term or if you have marketing background, you may know what that is. But for those of you who may not have ever heard of the term A-B testing, it's also known as split testing, but it essentially allows you to compare two versions of something to learn which is more effective. And I think one of the number one opportunities in organizations that I see is something very simple. It's A-B testing your email subject lines. So I'm looking at this from a better best type of scenario. So the better version, which you can pretty much do on any email marketing platform out there, is essentially split your list in two and try sending an email with a subject line one and then splitting your list on the other half and sending an email with a subject line two. These are having, you have to kind of manually create these situations, send those emails off separately, and then essentially go look at the report at the end of it and see which one performed better. So when we're talking about subject lines, we really, that's going to help us influence the open rate. If something's in my inbox, how is that subject line incentivizing your recipients to actually open that email? So in order to track and understand which subject line worked better, we would be looking at, as I have outlined in these red boxes, the open rate. So the open rate is the percentage of people that actually opened the email versus the total entire send pool that you have. So in this scenario, if we have subject line A had an open rate of 38.8% and subject line B had an open rate of 45.6%, we can, from a statistic and a data perspective, say subject line B worked better. Now, what if there was a solution that allowed and helped and supported doing this automatically? Well, that's amazing. And there is a solution out there, and it is on HubSpot, and I will show you an example of that. So inside of HubSpot, when you go to make a new email, just as if you would on any other email mass email marketing option is in the upper left hand corner, you have this little create AB test. So what that does is it allows you to actually in the one single email that you're sending is to assign one subject line A, one subject line B, and then as it sends out that information, it's actually automatically reporting back to itself, which is performing better, and then we'll switch to the higher performing subject line so that you didn't waste one of those halves of customers or quarter maybe in this example, getting a subject line that may not have been as viable. So as you can see here, we've got 25%, 25% going to A and B. And as that information comes through, the remaining 50% of those emails are going to be sent to the winning version. And this happens automatically. And then you can see here, if we go into the AB test results, we can actually see version A, version B, in this particular email campaign, which one actually performed better and where it fell back on there. Let me go to the next slide. The last piece that we're going to talk about is marketing automation. And this is where I was talking about workflows. So briefly, like a marketing automation is you telling the AI, the computer system, the software, when something happens, do this, or when a person does this, respond with this. And that happens on an automatic setting. And it's predefined by the user on the backend. And I'll be honest, it's pretty amazing what you can do. And some of you might already have been doing this when in this example, which is a single email automation, which is when someone signs up for my newsletter, send them a thank you email, welcoming them to our organization. So this would be considered a single email automation that just goes out once. And this is, you can do this on pretty much any and all email platforms. But when we move into more of a workflow dynamic, and workflows in this example, are we're looking at email marketing, is how do we want to follow up with a second, potentially a third, or even a fourth email, depending on the recipient's behavior. So I can also share with Aretha to send out, I have a diagram of sort of like what a workflow would look like in relationship to a donation workflow. So the initial step, someone made a donation, we say thank you, maybe with a request to increase their donation, or not. And then if they, we might send an automatic email to each later, thanking them again, sharing with them what their donation was able to do for your organization. Thank you for your $25. With that $25, we were able to deliver food to the unhoused communities in San Diego. If you'd like to continue your support, we ask that you make another donation or become an ongoing person, an ongoing donor. If they make that donation, they would split off and they could say thank you for becoming an online donor, and then a subsequent preset determined list of emails that would go out over a period of time. On the other side, if they don't make that donation, you might decide, can we make another ask? If anyone on this call is from the Stewarding, on your organization's stewardship committee, or on board, or working within that space, it all comes down to just making the ask. And a lot of times we leave that up to scheduling a meeting, sending an automatic email, I mean a manual email, but by utilizing platforms and tools and technology like workflow automations, a lot of that lift is taken off of your shoulders from an organizational and overhead perspective, and you're able to do the other things a lot more efficiently. And as well as the rest of the features here, the reporting capabilities around these are also incredibly robust. So you can continue to look at how are these pieces working and how can we continue to optimize those workflow automations rather than just trying to remember to send the follow-up email in the first place. So in conclusion, I think the big, big, big picture here is any CRM that you have, and I've seen a lot of great conversations happening in the chat here, is ensuring that whatever database you have, it's clean data, and it's connected through an integration point to allow for automation growth and that you can optimize those operations internally. So as we continue to have conversations with one another, with our colleagues, with our board, and you look at maybe investing in a CRM system, leveraging that integration point is going to be incredibly critical because it allows and supports for all three of these core components of really making an actionable and effective use of your CRM through your communication strategy. I'm going to leave with a little bit of a another pat on the back to HubSpot specifically and TechSoup through their partnership. But this, if you want to talk about, like I saw a lot of conversations of it, does it connect to this? Does it connect to that? Or does this platform connect to this? This is, I would say, a the HubSpot's app ecosystem where it is now. These are always updating and always changing. So it's an incredible resource of opportunities to leverage all of that data you guys have internally in your CRM system and be able to do lots of different things like lead generation, automation, social media, sales, any and all of the above. So I know that Aretha sent out the link before, but definitely take a look and start to explore what the solutions look like. You know, I don't want this to be too heavy of a sales conversation. It really is about tactics and helping you guys find the solutions and using those solutions to, at the end of the day, increase your impact and grow capacity within your organization and doing that with data-driven decisions and the ability to return back to those stakeholders and say, what we're doing is working and here are the numbers and here's the information to kind of show that that's the case. And then lastly, of course, as always, you know, if you have any questions about what we went over today, you can get in touch with us through this email here. We are excited to be partnering with TechSoup as well to help support nonprofits who are looking to take advantage of this new partnership with HubSpot through the HubSpot for nonprofits. So feel free to click the link in this and then we will definitely love to speak with anybody who has further questions on what HubSpot can do for you guys and any and all other marketing or website questions you might have. With that, I think Aretha just let us know that there are a few questions in the Q&A. So I'll invite Janelle back. Thank you, Jen. I hope that this was helpful. We'll kind of get through all of the Q&A and any final answers and then we'll let you all get back to your day of changing the world and making it a better place. Aretha, do you want me to answer? Yeah, I do want to answer this question from Amory and a couple of other people about the chat room. I'm sorry you're not able to copy and paste. I don't know why that's not happening, but I would definitely keep trying or screenshot something that you want to share. But as far as TechSoup sitting out all the chat, we have to get permission from everybody to share their information or share, because we use a platform called SlideShare and SlideShare is open source. So that means anybody in the world can go and SlideShare and type in something and pull up this whole chat. And so Whit could sue me and say I didn't give you permission to say I was there that day. I did something wrong that day. So yeah. Aretha, I'll give you any but I totally respect other people's privacy. That totally makes sense, but I trust you with my information. All right. So go ahead. Janelle, why don't you read the Q&A? Do you see Q&A? I do. Let me see. So the first question that came through is what advantage does the cost version of HubSpot have over the free version? So this is a great question. The way HubSpot in particular is set up is like we said at its core, it's a CRM. And then from there, it's developed out hubs that you can add on to that CRM functionality. So there's a marketing hub, a sales hub, a service hub, and operations hub. So there's a lot of room to grow within the platform. So when we look at that, it's really a wide range when we look at the cost version versus the free version. The free version is a really good place to start just formatting and starting to collect that data. But really what you want to do is look into what hub best suits the need for your organization and how can you grow into having that hub as a part of your operations. Most often, we look at the marketing hub as being a really great solution for nonprofits. And a lot of the features and functionalities that we talked about today are included in that marketing hub piece. Yeah, I think that's a great answer. To your point, Janelle, it's really about making sure when you're going into that any paid version of it, that it's the right one for your organization. I've been working with a nonprofit recently that I think I mentioned them earlier. They are a kind of a solution for selling wholesale and connecting farmers to marketplaces. So they're looking at, okay, do we leverage the sales hub for that so that they can help kind of manage their internal sales database? And as they're working through these different relationships with different wholesalers, they're able to track those from an operational perspective internally versus to Janelle's point, a marketing hub where it's really leveraging a lot of the tactics and tools that we just highlighted like AB testing. And I did see someone ask if AB testing is available on the free version. It's not. It's going to be something that comes within the marketing hub, the marketing professional hub in there. But again, there's lots of solutions and lots of ways to kind of tiptoe and get your toes wet and kind of jump into to the different options there. I would love, you know, I think that I hope that Ann Marie that kind of answers a little bit to your question about HubSpot has a free marketing sales hub service and operations. How can you guys as a start as a nonprofit that is starting up utilization utilize that opportunity? Do you know, do you want to touch on a little bit about like what's available maybe in the marketing starter package and how that might compare? Or is that worth the conversation today? Yeah, so there are a lot of core marketing functionalities available in that free section. So as you're starting off, if you're a brand new organization and you're really just looking to start to build out these processes, it does make sense to start on that free account. What you'll be able to see once you're in HubSpot is all of the different features. They're still in your platform. There's no question as to what it's capable of doing, but you will see a little lock mark, which will signal which piece you need to upgrade to for that core functionality to be added on. So a major difference between the free to the starter version for the marketing hub would be the ability to take some of the HubSpot branding off of the forms that you're able to add to your website. There's a little bit more customization that comes with the properties that you're building, more robust emailing functionality. So all those different features, there's kind of like what was saying a good, better best. And that really just depends on what level you have across the hubs. Nice. I'll answer spaffords, which is, are there features of HubSpot that are tailored specifically to the needs of nonprofits? I think that's a great question. It goes back a little bit to what we were, what I kind of discussed about the customization and the ability and the capabilities of customizing the different features and functions within HubSpot. So the benefit is of that is like you, no nonprofit, many nonprofits may not function the exact exactly the same way. So the ability to go in and define these different properties, the way that you segment your lists and then what you do by your workflow automations. You can really customize it for your nonprofits needs. The second piece that I think is really important to touch on is its capability to sort of integrate into the systems that you might be using like your donor platforms and things like that. Integrating across those different, you know, as I mentioned before that, that wholesaler connecting it to their ERP is really vital so we can continue to maintain and manage their centralized CRM data and database to match all of these different data input places. I want to just quickly touch on an anonymous attendee, Janelle, is that all right if I answer the Salesforce question? Yeah. I actually just found a great link as well. So I'm going to drop it in the chat while you're talking. Yeah. So Salesforce is a beautiful platform. It's a great sort of CRM and they have a wonderful nonprofit discount free version for that. And that's amazing and I think it's a great solution for a CRM. I think where the opportunities lie sometimes is the Salesforce itself does not have a belt out of the box necessarily out of the box hubs like these hubs that we're talking about within HubSpot to connect and do things with that information. A lot of times getting the information out can be a little bit challenging and cumbersome and requires a level of technical expertise to be able to ensure that you're getting data in and getting data out effectively. Janelle, do you want to take the file and content management capabilities? Yeah, let's see. So can we talk more about the file and content management sharing capability of HubSpot, thinking specifically about storing impact stories, marking collateral, etc. So if you're familiar with something like Google Drive or Dropbox, it functions very similarly. It's cloud based system. We're able to create folders and different level of access across your teams so that you can have up to date information of files that you can store in the system. In terms of impact stories, I'm assuming that that might be a video. There's multiple ways to integrate video in HubSpot both in your emails and your landing pages. They do have direct integrations with video platforms so you're able to see even the viewership in those videos over time where people are dropping off, what that engagement actually looks like and also have them live on an external source like YouTube and embed links that you're able to see, click through rates and that sort of thing. Are you familiar with KEEP? I'm not. Infusionsoft? I'm not familiar with that platform either. So Christy, unfortunately, I don't know if we're going to be able to expand on the comparison with that. So I apologize. What features are unique to Sales Hub that are not available in Marketing Hub? Let's see. So Sales Hub is more targeted at that one-on-one relationship building. That would be better suited for organizations who have large funders or large donors where it's a one-to-one relationship that you're nurturing over time. The Marketing Hub is more focused on the automated mass communication, the kind of the top-to-middle-of-funnel approach. I feel like the Marketing Hub works really well with nonprofits because a lot of the features that you have in there, including the email templates and the snippets and that sort of thing, that can be used in the sales process as well. So I really think and what you can let me know your opinion on this, but unless you're really focusing on donors or larger funders, Marketing Hub, if you're going to pick between the two, is probably the better solution. Yeah, that's a great, great suggestion. And I have worked with nonprofits. I've been on the board of nonprofits where we do. We have these very high-dollar opportunities within, and that's where it may even be a conversation to have with your development director or your stewardship committee on your board and getting an understanding of how is it with managing these six, seven, eight-figure prospects, right? We call them prospects. And how are you tracking and managing and collaborating on those particular individuals over time? I'll give an example of an organization I'm on the board of. We had an individual who had engaged with our organization many, many, many years ago, and our Stewardship Committee just fortunately was very good at staying in touch with them. And they actually, upon, like when they passed away, they donated over $10 million grant or donation to the organization. And it was really just because of that continued conversation piece, right? So I think that's a great example, a great way to kind of differentiate the two. There's actually another question in the chat that I'd like to call out, that we already have a CRM in converting to another one is such a daunting project, having to contact all existing donors to change or renew their donation on the new platform. Any solutions to make this easier? So actually with HubSpot, we can integrate with whatever that current donation platform is so that that process is not being interrupted. We also offer implementation and migration services so that you won't have to go on that journey alone. I guess that's time. But yes, I think just quickly to touch on that. I think it's always important when you're starting with something new or you're migrating over, this is a great opportunity to make sure you have the system set up correctly. So definitely take the time to make sure that as you move over or as you start something new, you're really doing it the best way you can from the out gate. It's much easier to build something correctly than to fix something that's a mess after it's already been built. So that's just my little two cents there. And on that note, I guess, Aretha, are we finishing up here? Yes. Thank you all for coming. Make sure you fill out the survey. Thank you.


Okay. So aqueous solutions of sodium hypochlorite, best known as household bleach, are prepared by reaction of sodium hydroxide with chlorine gas. How many grams of sodium hydroxide are needed to react with 25.0 grams of chlorine? So the only thing, oh, and then it gives us the reaction equation. So the only thing, other thing that it gave us was the mass of chlorine gas, right? So chlorine gas was 25.0. And it wanted to know, well, how much sodium hydroxide would we need to completely react with that 25 grams? So does everybody understand what it's asking? So remember the, so I guess I'm going to give it away since this is the first one we're doing today and I don't want to push you guys to hardball recording. But remember that the reaction equation gives us a mole to mole ratio of these various substances that are reacting and forming in the actual reaction. Is everybody okay with that? So it's a mole to mole ratio based on the coefficient in front of each one of those individual species or substances. Is everybody okay with that? Okay. So let's just go ahead and underline the coefficients. Remember, if the coefficient is one, it's just implied it's not there, you know, so we don't actually formally put it. I'm going to eventually stop doing this for you guys, but for right now I think it's a good thing. So in other words, since it's a mole to mole conversion and it wants us to eventually convert chlorine to sodium hydroxide, that gives us the actual ratio of the mole to mole conversion. So in other words, I'm just going to write that ratio really quick. So two moles of sodium hydroxide equals one mole of chlorine dex. Is everybody okay with me doing something like that? So that's eventually what we're going to need. The first thing we need to do though, if we're going to get to moles of chlorine, right, and we have grams of chlorine, we've got to get, yeah, we're going to have to get the moles of chlorine. How do we do that? Mole or mass, right? So if we look up at the periodic table, it's 3545, so 35.45 times 270.90 grams of chlorine. One mole of chlorine. Okay, I'm going to not do this, I'm not going to solve every step. I'm going to just keep going along on the conversion train here, okay? So I'm going to be able from that to cancel out my grams of chlorine. Is everybody fine with doing that? So now we're at moles of chlorine. Remember, we wanted eventually to get, I think, grams of sodium hydroxide, right? Yeah, right, that's right. Grams of sodium hydroxide. So firstly, we need to get to moles of sodium hydroxide. Okay, so using that conversion factor that was derived from the chemical equation. So now, we've got to figure out, well, what's the molar mass of sodium hydroxide? If you, I'm just going to do it on my calculator, I'm not going to formally write it out. If you're having trouble with that, please go back to the molar mass figures, okay, and check it out. So, sodium 22.99 plus oxygen is 16 plus hydrogen is 1.08. So, I got 40.00 grams of sodium hydroxide. One mole. I'm doing it the wrong way though. 40 grams of sodium hydroxide. And of course, the reason I was able to figure that out, even though I know Justin almost caught me, right, before I figured it out, was because I looked at my units and I would realize that, you know, I had them inverted. I couldn't cancel them. And then, she gave me the answer. 36 bigs. Okay, any questions on that one?


Hi everybody. I'm going to talk about how we, for the past year, created several libraries of short components for Client I've been working on. I'm working with. First, let me introduce myself. So, hi. I'm Xavier Lefebvre. I'm French. I live in Paris. I'm a team leader on React and React Native Projects for a company called BAM, indeed. Overall, it's a consulting and development agency. We work for any type of companies to accompany them to build some successful products. And so, as any of you in this room, I do love tech as much as I love traveling. So, being there with you today is quite nice. It's like quite an amazing opportunity to go to India. And like that. Good. You're less going to hear the breathing. Now it's good. Like that. Do you hear me well? Yeah? No, no. Okay. Thank you. And I do also love, among other things, motorcycles. But why do I put motorcycles here? Because I have this little image of a motorcycle and all its components. And it made me think of that. What we're doing is a little bit of that, because it's like many different components with different sizes, with different responsibilities and scope that we need to assemble together to make a website. Or to make several websites. And depending on the motorcycle, some components can be reused on other websites. So, what I'm going to talk about, I'm going to talk about why we started this project of shared components and how we tried to tackle this topic. Then I'm going to deep dive in some of our design decisions that helped us make this a success.  I'm going to tell you how we consider that we're making it a success. And how we organize ourselves to tackle the issues that other teams or our teams meet while developing on this project. So, it started from a wish last year. Our client, which is a big bank, said, it would be awesome if we could finally and successfully, because we already tried. Create shareable components in order to read them on different apps, give them to other departments or even one day, potentially, sell them outside. We didn't reach this place yet. We're approaching, give them to other departments. So, why did they say that? It's been a long time we worked with this client, and we developed a lot of different websites over the past seven years. And it happened quite some time that we redeveloped the same kind of features. Slightly different, but in the business of the bank is always the same behind. And so some features can be accessed, could be reused and are reused effectively on websites which have a different user target. So, let's see a little bit what I mean by that. So, that's an example. That's an example of one of those features. It's a full page feature. It's called a fan sheet, a fan being like a source of money that's used to be invested. And it's part of life insurance, for instance. And this specific feature, it's a full detail of the fan. So, it can be interesting, and it is interesting for B2B, for internal purposes or B2C. And this fan sheet has been, for instance, made several times for different websites. So, our first attempt, which was named Commando. So, the setup is a team is working on one website, another team is working on another, but they have to share a component. There is something there that they could reuse. So, what we did is we created out of the blue like that a command code base which was called Commando, and both teams were contributing. From that, we output a simple, huge JS bundle that was served directly as a script, which was directly downloaded by the website. The problem was that the code base was growing without specific architecture. So, a lot of components really didn't follow the same syntax or the same architecture. The JS bundle was huge, same, just one for every purpose. And in the end, at this time, there was no versioning strategy. So, if you had, if you pushed a new version with breaking changes, you could be pretty sure it would break your website. So, after that, of course, it didn't work out, we ditched it. After that, a second project was called Tapas, which is, I don't know if you know about Tapas, which is like a little Chinese dish, food that's meant to be shared. So, same setup at the beginning, but this time, one team started to own the project. So, they were the one taking care of its architecture and its improvement. Or the other team, for instance, team two or more, were contributing to the project directly. Then, this time, we versioned, of course, our JS bundle on GitHub directly, and we packaged them. So, they could bring it directly into their code base before bundling the final website. It still had some issues. First issue is, once again, the first team, the team one, but first and main objective was to take care of its own website. So, they didn't really think enough in terms of reusability, and they didn't really have this focus. Second one being that, once again, it was a big JS bundle. So, any type of components, even if you didn't use, need them.  And last one is that the versioning system was on GitHub. So, you needed a GitHub account to be accessed to our private GitHub team to be able to access them. So, it was clearly not perfect. And there were solutions for all of that, but we didn't, at this time, try to use them properly. So, last attempt, last year, at the moment where our client said the quote I told you, we launched this project which is called Component Studio. Same setup at the beginning. So, this time, with a specific core team, like you would have for any open source project. And other team contributing. After that, we created and split architecture in several libraries. And same at the end. We packaged it in order to be reused on the host projects, on the websites. But this time, for each of the solutions, we, for you, for managing several libraries into one repository, we use Lerna, which you might know, which is a mono repository manager. And for giving our packages to our users, we used Verdacho, which is a private NPM open source. And this made a big, big difference. Thanks to this, we can say, and I'm going to give you a proof at the end, that it works. So, that's a demonstration of what we have right now in our project of reusable components. It's, we use Storybook. It's our basis of development, of validation, and it's our showcase as well. Everything is accessible from there. So, a developer, when he's going to develop, he's going to develop, thinking, even though it is from another team and he needs to contribute, he's going to develop thinking about reusability because he's going to develop directly inside of Storybook. Apart from his own project.  You have the knobs, so it's a props of your component. You can play around with them and see the impact it has in live. And, and it's also used for our own product owners to validate and to, to show what the capability and what the components are available in, in our project. So, let's, let's dive in for some tips of what we think made the difference. So, if we can, if we come back to this, this part of the, of the, of the diagram. First, I want to, I want to dive in a little bit into how we organize our packages and components. Then let's dive in a little bit more into our code structure of each of those components. And finally, how we limit the impact of breaking changes because it's a project for instance, there is six other teams working with us on the daily basis and pulling, pulling requests of changes on the, on the code base. So we are not capable as a core team to, to check all of them. The thing is that we want to be agile and go fast. And so we, we had to set up an automated process, a strong process and with, with formation to, to, to make it work well. So first, how we, we cut down our packages and components. We follow our atomic design. So I don't know if you, if you know about the atomic design principles. It's a, it's Brad Ford who, who created those principles. And it's, it's, it explains you how to cut your UI components in, in a hierarchy. So the, the biggest one, I'm starting to start by the biggest one. It's called in our, in our case, we used the organism as the biggest one, which is almost a full feature. They're a full page feature. Then inside you have the molecules. A molecule can be composed in order to make an organism, of course. And then you have the atom, which is a simple UI component. So let, let me come back to that. The impact it has on our code organization. So UI, as I just told you, as you've seen before, it's an atom. It's pure UI. There is no business in it. So this is the party you would expect in a design system like material UI, for instance. It's completely customizable and composable. Then what comes next? We called it widgets. It's business connected directly this time. It's, it still has a pretty, a pretty small shape and it's composable when it shares a common business purpose. So for instance, I was talking about funds. Funds, it's a specific business data. So all the widgets about funds can be composed together to make a bigger product. And at the end, you have the organisms, for instance, the friendship I told you, or, or chatbot. So that's the advantage. And they're full page features and they do satisfy by themselves a user need. So a friendship is a composition of widgets. But we also, for instance, have a chatbot and this chatbot needs to answer some, some questions about funds. So directly, the chatbot is going to retrieve those widgets and display them as, as it would have done it with a friendship. Let's take a deeper look at the code now of each of those parts. So that's, that's impossible to read. So let's, let's go a little bit in it. At the bottom, so you have the UI UI is pretty simple. There is not, not a lot to say about that. You have a component, you have its style. So it's not connected, so you don't have much more. And we do have a theme, a theme setup and feature. I didn't, I'm not going to talk about it now because I'm not going to have the time, but I would love to talk about that later if you're, if you're interested. After that, so you have our widget, our widget on the, on the right of it, you see it's called components. So this is the UI place. This is where you have your JSX. It's a composition of UI components, mainly that's being fed with data from a container, which is, which is classical. The container is going to fetch this data from a service that we created in order to, to optimize composition of widgets at the, at the, at the organism level. And it's, it's using what we call a modellizer, which is an adapter of the data that comes from the back in order to, to, to just to clean it and to, and to have calculated the, calculated the variables if necessary. So this, this widget, we export it in three ways. As a standalone. So you just take it, you put it inside of your website, even if you don't have reactive work, it can work and it displays, it displays directly the data. It fetches it, it closes it, of course, and it displays it without you thinking. And we export it in two, two separate pieces as well as a dump component without any data and the, the data fetching service by itself for you to be able to recompose it from the top. So for instance, the friendship, an organism is composed on the, on the right side, as you can see with the purple of widgets and of UI components on the left part, because our stack, our stack of our website is made of Redux. We decided directly inside of those, of those organisms to, to put Redux. So in order for the, for the, for the host projects to be able to embed the store of this product in case, for example, inside of their own, to do optimization, not have to call twice the same, the same, the same data or reuse it somewhere else in the, in the application, if the data is already available. And this Redux store is using our fetch widget data service to be able to, to, to get the data that is necessary for the widgets you're using. So now I wanted to, to, to dive a little bit into breaking changes because it's an interesting topic and even more for us that any team member, any outside team member can, can do a request, merge its code in its own, with its own team directly. So there is a risk of, high risk of breaking changes because if they change something that another team is working on and without communication, it can be, it can be problematic. So breaking change just for reminder is a change in one part of a software system that causes other parts to fail, which happens when you change the existing API of, of libraries without one user even, of course, even more. And what should I pay attention to? So for instance, your, we expose components, we expose some functions, but mainly we expose components. So the signature of your components, if you change it, if you delete some, some parts, some props, for sure you're going to have issues. So the exposed components and function names are their props or the function parameters. That's part of, of the potential breaking changes you could make. The component style as well. So it's, it's the style by itself. So I don't know if you change a color or a font. It's, it's, it is somehow a soft breaking change because it's still going to have an impact for the end user. It's not going to break your site, but at least if you change a font, it might be real. But beyond that, the space it takes in terms of height, weight or margin is, is might funds in this case might break a website. So this is part as well on the, on the little things we need to, to pay attention to when we talk about breaking changes. And last part, when we break the peer dependency, which has a breaking change, for sure the whole project we will have, normally we'll have to, to update this peer dependency, but we'll have to pay attention to the same breaking changes. So you need to warn them. The example here being for instance, style components. We do use style components to develop, to, to take out the style of our components. And you can, it's a peer dependency because you can only have one version running on your code. So if they, if they push a new version with breaking changes, we will have to make sure that our host projects use the same version and fix the same problem with the same type of breaking changes. What we set up to help developers anticipate. We use flow. It could work with TypeScript in our whole code. And we expose in the same way as Flowtyped, our API with Flowtypes connected directly. That's, that's a nice advantage because Flowtyped is really, is, is connected completely to the, to the base project it's supposed to type. It's very, we, we provide directly the types with our libraries. So they're connected directly. So if a developer changes the signature of a component, changes its props, it's going to break in his ID because he's not going to have changed the exposed Flow API. So then it's going to break, he's going to need to change it. He doesn't have a choice. The CI will be read. He's going to, he's going to adapt his, his Flowtype API. And if he didn't pay attention, his pull request will directly, thanks to dangers that runs in the CI, tell him that he changed a Flow API file and that it might mean breaking change. So he needs to pay attention. And it did help us in some cases to, to anticipate breaking changes. There is also an automatic semantic versioning system based on the commits, like was mentioned a little bit earlier in another, in another talk. And so when the developer knows he's making a breaking change, he's capable of seeing it directly at the commit level. And he's going to be, it's going to create a major directly. So people know that if, if there is a major to bump, there is potentially a breaking change. And thanks to that, at the same time, there is an automatic change log generation with all the details directly coming from the commits, using commitism. So how do we know that such a project is successful? The little business part I think is interesting for, for all of us, because even as, as tech people, we need to be able to potentially find a way on the, on the speech to convince business managers to do such, such kind of projects. So our return on this investment formula is, is quite simple. It's for sure, improvable. It's the same for all components we expose. Of the cost it would have, if it was redone on a normal project, times the number of times this component has been reused. And to this, we subtract our project by itself, full cost, our team, but even the time that the contributors spend to contribute. So as a tech team, our main focus is on the right part. It's not on the left part. The left part is the sales part. It's the fact that you find, you find people to reuse your components. It's mainly on the right part is to reduce the project cost, meaning that it needs to be faster and easier and more robust to develop on this website with less, with as many as, as, as a few bugs as possible. But we did not arrive to this point after a year without struggling. So what we did, we started tracking the issues, like the issues we would have on a GitHub repository. That's pretty complex graph, yeah, of our issues. So at the bottom of the bar, you can see that all the issues, it's orange plus red, all the issues that were made, for instance, for by the other teams that they wanted to share with us. And on the blue, it's a contribution. So it's activity on the repository. It's to see if there is correlation between the number of issues and the activity we have. So there is a correlation, for sure. We can see that at the middle on the number four, we did, before that, set up enough actions and positive, positive tools and, and, yeah, improvements on our code base to, to, to have a flat number of issues, even though the activity was, was a little bit increasing at that, at that time. Why did it increase three times? We discovered lately that it was mainly because there is a lot of turnover, because we're an agency. So the developers, there is a lot of turnover in the developers. And each time that there is an increase in issue, it's mainly because our new developers coming on our project and they didn't know all our flow and how it worked because it's quite, it's quite dense. So with these issues, with this graph, we started tackling them. How did we organize ourselves? So first, every day, like, like, without missing a day, we would take at least an hour to take a look at the ongoing actions of some, some fixes we wanted to set up to make sure that it was on track. We then prioritized based on the type of issue. So if it's a bug, it's more important than if a developer just was blocked for five minutes. And the developers lost time. So thanks to this prioritization, we are capable of then tackling the most important ones every day. And going to the, into the depths of each issue and to the root causes to understand exactly what's in the flow, which can be the training of the developer. It can be that potentially it's meeting, it's, it's missing a little tool to, to, to allow, to prevent him from doing a mistake to, to do. And then every week, we took weekly actions to make sure that in our, in our development flow normal, we, to make sure that those biggest root causes, as we call them, wouldn't come back. So this is an example of, of our diagram of our graph of, of main root causes. And the top one, for instance, lately is we have a lot of issues with YarnLink. It's like, I don't know if you know YarnLink, you connect your, your own library to a host project to see directly the impact it has live on your host projects. So it's, it's useful if you want, for instance, so you're, you're developing a website and you're using a library, but something doesn't work well or you want to improve it and see the impact it has on your website, you use YarnLink. So is it worth it to do such, such a project? We consider, thanks to the little formula you saw before, that really we saved 18% of development costs for those projects since almost a year ago. So for us, this alone is enough to tell us that it's worth it and we're going to continue. And a second side effect that, that rise naturally was the fact that it's, it created a consistent UI, UI, UI, UI design across all the platforms. That was not always the case because each team was separate. You don't really enough talk to each other and organize themselves well to have a consistent UI. Now that they shared a common base of, of components of any size of components, the UX team at the same time had to, to start synchronizing themselves by even more. So first it is a success and we're going to continue in the, in the coming year. That's it. That's it for me. And I wanted to thank the people that worked on this project because it's not, I wouldn't be here if, if we didn't do that all together. Yeah. Yeah, we have, we have one here. Micronus. Okay. So I wanted to know how you guys are managing the versions of the component for the library. So suppose a team A, uh, suppose you have a component in library, tap component, which is an internal component. And team A is using version 0.5. And there are some bugs and something like that in that component. You fixed it and you expose the new version or whatever. So are you asking all other teams to upgrade their components in their project best or what, how you guys are managing that? Yeah. For the, for the moment, it's like, it's really an internal company project. So all the teams, we're not that far from each other. So we do have a WhatsApp chat and we do, we, we, we do give news when, when something is changing, but we're not, we're not obliging anyone, no one to, to upgrade. They do as they wish, like they would for a normal library. So, so we, we trust them in making the right decision based on, on what we, we change and what we improve if they see the value in it, because they have to prioritize their own development roadmap as well. Okay. So on a second question, when you ask your other teams or other products, let's say application team A or two, what you say. So you guys are exposing it through some gate directory or you are creating an NPM bundle for that. Or okay. So you guys are creating NPM bundle. I didn't want to put this. Yeah. This one is huge. But yeah, we do. Is it, is it, is it, uh, yeah, on the right side, you can see the, the little vids, it's Verdatio. So Verdatio, it's, uh, it's a private NPM. So it means that we, uh, we, we each, each package is, is pushed on this Verdatio. It's really like NPM. And then the other teams, when I need to, to take the latest updates, they do a yarn, yarn add, uh, the name of the thing with the right, the right, uh, number, the right version. Hi. So when I'm writing my code as components, I always get, uh, confused about, for example, if I have a component that takes some text and renders it with the box shadow and with some font color and all those things, I'm always confused about how much customizability should I expose on props for that component? Should the box shadow be also customizable? How much of the styling should be customizable? So how do you guys look at this problem of when you build components? How much is, uh, inherent to the component and how much can be custom customized using props? Okay. Um, what do I have there? No, no, no, no. I didn't put it there. Um, I was expecting a diagram. I don't, I don't have, um, how we do that. So there is those three layers. There is UI. There is a, so we call it UI, which are the atoms. There is a molecule and then there is organisms for the, for the atoms. We consider that. So first, first, of course, they're already compliant with the UI, UI design of the company at first. So most of the time, this is going to be enough for the, for the, for the other projects. But then as the really simple components, we allow, um, full, full, uh, customizability of the component by itself for the other teams. They can do whatever they want with it. We expose, we expose most of the, of the style. We use a specific themes, uh, system we did by ourselves with style components. Um, then at a, at a higher level, when you go through the molecules and the organisms here, it's different for, for instance, because we don't want it's, it would be too customizable and too complex and too crazy after to, to, to anticipate some breaking changes. So here we do a lot of some stuff, but based on what was really necessary, based on the, on the, on the questions that those team asked us in terms of improvements they wanted to make in the style. So it's mainly, it's mainly like color, color of text or font, um, and sizes, sizes of them, of the components, for instance. And it doesn't go further than that. We want to set the style at the same time that, as I told you, it does set the, the UI, the UX for all of those projects. And it's a good thing. Uh, one, one second, please, uh, please do not leave the auditorium till the QA is done because we have few announcements to be done. All right. Yeah. Next question, please. Hello. Yeah. Thanks. Thanks for the presentation. It was a nice one. So, uh, how do you tackle the inter, uh, these components, communication that you guys are doing? What's the strategy that you guys followed for that? The communication between these components when they communicate or if, if there, if there is a communication happening between these components. Yeah. So here, here, for instance, so the friendship. So that's, that's the little thing I didn't explain here because it would have taken more time. So friendship is made of, of widgets of different widgets that are supposed to be connected indeed. Uh, and the, the fight, how our backend is done is that it's one route, when huge route that, that gives all the necessary data data to create a friendship. So of course here you wouldn't want to have to, if you call 10 widgets, you wouldn't want to, to make 10 calls to the same route. So that's what was that way we created. And it's pretty, it's pretty raw and straightforward. We created a full service with all the, all the, the widgets that compose a friendship in it. And, um, for, and this service, when you reuse it, you call it and you give it the name of the widgets you're composing with. Okay. And it's, it's going to, for you make the call with the right parameters. And the difference is there is several routes. There is four routes in total. There is some other stuff I didn't mention. And it's going to, you're not going to have to think about that. It's going to put this, all the data properly with the modellizers I told you, so the adapters for each widget inside of a, of an output object with the name of the widget and the data it needs to, to, to get to properly get displayed.  So you don't, you don't care at all yourself at least about how it works inside. But then if you want to create a new widget, it's, it's another problem is way more complicated because it's, it's like a big function with a lot of if else. Yeah. Next question. Hey, Anand here. So, uh, of course, uh, nice presentation and we asked about the versioning and all right. So someone asked from there about versioning. So, so it's like you are, uh, managing monodepo and how you are actually building these components because you are having atomic molecules and organism, right? So you might have different build process for these components and how extensibility is working for these components. You think that they might have different build process. I'm talking about like what build process approach you have taken, uh, for these components. And suppose I need to tweak a bit of, you know, the, so for example, I take one atomic component and I want to write something on top of that, right? Which might not be the part of that repo like atomic component, but I want something to be changed. So how to extension is going to work for those components where I'm trying to use it. So I don't know if it's, I'm going to answer your question. You tell me, right? I think you put it there. Did I, did I not? I did. So we have, we have a, it's, it's a tree. You cannot, I'm sorry, you cannot see it well. I'm going to tell you. It's a, it's a tree. It's a decision tree that we, we gave to all the peers, the product owners and the developers, uh, for them to be able to make the right decision before making any change inside of the, of the project. And the first, the first step is to make sure that the change they want to make can be a change on something that already exists or it can be a new feature. It has, they have to prove that it's going to be reused by another team. If they make a change directly to a component that's not going to be reused, we tell them to, to customize it directly or extend it directly on their own project. First, if they do prove that, then they need to make sure that the UX UI is compliant and validate it with the UX UI once again. So for this whole UX UI, uh, um, working together well. And then last step, it's a technical step and we do, uh, workshop with them of like, it depends on the complexity of one hour to ours to, uh, to understand where we're going to fit this feature on architecture to, to put it at the right place. All right. So, and what about the server side rendering? Like, uh, how you guys are way we didn't, we didn't, we didn't for the moment. It's pure SPA. It's a good question, but we didn't tackle that yet. Yeah. Next question. Mentioned a tool that you use in production for monitoring. I was unable to catch the name of that tool. Can you talk more about that? A tool for what? What was it? It's a for monitoring your production issues. Yeah. Issues. You use a tool. We use the handmade tool with Google spreadsheets and Google scripts. And it's working pretty well. So all the issues they're shared on it. We use Trello a lot, Trello boards a lot. Our development process is on Trello board, but our, and it's some specific from my company are solving process, issue solving process is also on Trello on another board. So when a team has an issue, they create a card with a specific template inside of the Trello board at the beginning of the flow of, of resolution. And we connected directly Google script to the API of Trello to be able to get the right data and to, to, to show it this way.


Asked me to come and help them give these toys up. This is their first year. They asked me and I said it sounded like a good deal to me. I'm out and I offer the kids and offer anybody that needs Santa. All they gotta do is call Santa and show it. We've had some come through. This was the first time I've ever seen Santa. They, they amazed. And they, the ones that came through, they really needed what they got. Sure do. It's kind of like a donation. They're round up toys, dollar store it, my plumb will help us a lot. Do what we can to help the people with the local income. But I need you for kids. It's probably, maybe not have a Christmas. Maybe help them out. A lot of people call them out and help. We, we can help them when we try to do the best. Oh, Merry Christmas!


Hey, I'm Frank Bellow. I'm David Olson. We are here at Reggie's live in Chicago out on the road with altitudes and attitude Our new record our new project that Frank and I did. I did some fun here, man. Yeah, it's cool with Blackstar With Blackstar. We're at Sweetwater for a few days rocking the house over there live performance Didn't some recording as well and no we got what do you have at home? What are you playing? HT1R. It's so easy.  Yeah, but it's just at home and I can get watching TV What's your setup on this thing? I know you plug in dude your tone is pretty gripping right now Right now. I just keep it as seen right here. So it's all good. Perfect I don't really make a big deal out of what I do here. It's just get that sound, but you know it It's so easy. Yeah, that's what's great about Blackstar We also had our buddy Gus G rips and so was on one of our tracks called here again on the record Another Blackstar alumni with us. So, yeah, we kind of got Blackstar on the record. We got it alive You know, it's just it's kind of a cool thing for both Frank and I play guitar on the record Blackstar is awesome man keeps us loud and proud all good here without


As we go about our daily lives, we aren't generally aware of the forces generated by solar activity or the Earth's magnetic field. While these planetary changes are well documented, precisely how they affect human beings is less clear. To answer this question, researchers have turned to the autonomic nervous system, the subconscious control system that regulates bodily functions such as breathing and digestion. Their findings suggest that our nervous systems are well attuned to the energetic fluctuations that ripple through our solar system. The work builds on observations made by the famed astronomer Alexander Chuchevsky during World War I. He noted that battles intensify during peak solar flare periods and that major human events and behaviors closely follow the cycle of the sun, which led to the hypothesis that some unknown solar forces affect human health and behavior, providing a provocative link between events occurring in our solar system and life on Earth. To test this hypothesis scientifically, the team looked at how the human nervous system responds to changes in solar and cosmic radiation, as well as in the Earth's magnetic field. They accomplished this by focusing on heart rate variability, an indicator of autonomic nervous system function. This variability was tracked in 16 women, who wore heart rate monitors for 72 hours per week for five months. The data were then compared to changes in cosmic rays as well as geomagnetic and solar activity occurring over the same period. The team found that heart rate variability significantly correlated to variations in three key variables, cosmic rays, solar activity, and human resonances. Strikingly, the participants' heart rate variability rose in response to increases in these variables, and the response was quite rapid. These positive correlations suggest that human physiology reacts favorably to these forces, supporting Chuchevsky's hypothesis that environmental factors can act as energy sources that affect health, mood, and behavior. Although the full importance of these relationships isn't currently known, the findings suggest that cosmic and solar energy don't just change Earth's magnetic field, they also affect human physiology. The work also poses the intriguing suggestion that some aspects of these energies might subconsciously connect human beings across the world.