Josh Clemente (00:00):
All right. Welcome to Friday Forum June 23rd, 2023. Get right into it. So Friday Forum weekly sync time for us all to celebrate recent achievements across the company. We have now officially launched what we’ll call our cultural counterbalance meeting, which is the Monday Metrics Meeting. And the purpose of this one is to talk about the good stuff, share what’s going on, connect. The purpose of that one, Monday Metrics Meeting is to dive deeper into the mechanisms and metrics that guide our business health. So that’s just a level set on what we’re here to do. All right, so this week, as I just talked about, we launched our first Monday Metrics Meeting. I want to give a special shout out to Maze but also to Galit who was our dry run presenter for the validation effort. So the purpose of validation is that each project that we ship will have a set of metrics that are associated with the core objectives of that function that the project sits within.
(01:02):
And we will not present on a project until we have validated through measurement, understand the positive or negative outcome as it relates to that core metric, and then we’ll present on that with a deep dive with a lot of probing and better understanding exactly what that metric means and how that project achieved it so that we can have this very high confidence scientific method that underlies how we build stuff. So anyway, we did a dry run on that this week. That was shared, that meeting was shared, so please check that out. The format will continue to evolve. We’re going to improve the metrics that we’re looking at and the analytic systems that we’ll pull them in the future. We also did a bunch of cleaning house on the engineering side. So we retired Bite.ai, the system that we were using, the platform that we were using for some image recognition stuff.
(01:50):
We also cleaned up a lot of AWS and other systems that we were paying a little extra for and generally tightened up budget on the engineering side while we had a chance during this app surface reduction that we’ve been doing. And then we shipped a big improvement to the ChatGPT driven logging feature. So we have certainly run into some issues with the open API that drives that feature and in some time or in some cases it can take up to, we had some outliers that were waiting for five minutes for ingredients to populate. So this timeout functionality gives a very elegant fail safe essentially where if that is running for too long, I think it’s now four seconds, we will provide them with our own internally recognized ingredients. So we’ve shipped that and we should see a favorable improvement in the usability of that function or that feature.
(02:40):
We have hit our four-year anniversary or birthday here at Levels. Well, we will on Sunday anyway. So we have a little video in comms that I, very thankful to Tony and Erwin for putting together, but a nice celebration of the journey we’ve been on for the past four years. On the growth front, so we’ve hit a stable signup CVR, so conversion rate is stable. It’s hovering in the five to 6% range, which is very good, but we’re not going to be investing heavily in more updates there until we start focusing on some of the other big projects. So it’s good to see consistency there. Our partner conversion rate is back up after a few weeks of declines. And so yeah, we’re going to be moving into the next major focuses. One of them is going to be driving traffic back up, so we’ve seen a steady decline this monotonic decline in top of funnel. Basically people who are landing on our home page. We touched on this last week, there’s a lot of forensics going on in the background to understand exactly what’s happening here and it is definitely multifactorial and pretty well understood.
(03:42):
And so driving that back up is going to be a major focus. Right now on the growth side, we’ve got the Levels classic signup, which is currently in AB testing or, yeah, in AB testing. We’ve had a couple confounding bugs pop up this week, so we don’t have good results on that just yet. But suffice to say, once we’ve measured the success of that project, we will ship that to 100% of our new hour traffic coming into the home page. And then we’re going to shift focus to the new home page infrastructure and build. So you can see a little image of how the infrastructure is being merged into a single unified home page and that will be very modular and flexible. And so we’ll build out that infrastructure. Then we’ll build out that page, launch that. Then we’re going to focus on growth measurement, a couple more analytics efforts there, and then moving into core referral flow before we start focusing on increasing signup.
(04:32):
So we can think about it as we’ve hit a good point with our conversion rate, we now need to massively increase the traffic to the home pages where that conversion process begins and then repeat. We’ve got a big July coming, so we are relaunching with partners as everyone knows. We were driving in a certain direction over the past six months with a new product Vertical and a lot of that process involved re-educating our partners on how to talk about our product and what that feature set was going to be. We then corrected course leaning in on Levels classic, and so there’s a bit of a stutter step there involved to get our partners back on the same path with us. We’ll be sort of relaunching a lot of those efforts. We’ve got a big performance marketing push. We’re going to be looking to take back organic search ads. So right now if you search Levels CGM or Levels, any combination of anything, you’re going to end up seeing a bunch of ads that are not for Levels that are the top links, the URLs right under the search bar.
(05:26):
And so that’s obviously confounding our traffic. We’re not owning the effect of our hard effort here because people are ending up on the wrong website. We’ll be starting to focus there. Our podcast tour, which Casey is deeply in the throes of as of right now, we’ll start to release episodes. We’ve got our podcast ads effort on a whole new level. Pricing experimentation going on, which of course plays with our large IRB studies. We have to work very intentionally there on getting new pricing models and experiments up and running that well with our IRB structure, so we’ll be working on that. And then we’ve got some modal testing incentives on the home page as well. All going live in the next few weeks and into early July, so lot’s happening here. Big effort to get to this point.
(06:11):
On the content side, a lot of member stories are being reused for marketing. So there’s a really interesting effort that the Haney walked through in his async this week just describing how we are going about going into all of the historic member stories that we’ve got, collecting the insights that were shared from that member, and then we’ll be able to reuse those in a really interesting way for remarketing or rather for marketing. So testimonials and being able to specifically describe how individuals in our cohort of member stories learn from Levels. And that’s a really interesting way to reuse this eternal content that we produced. We’ve got a newsletter weekly experiment. So right now the newsletter is very long form and it goes out biweekly, so we’re going to be testing a template for weekly. It’s going to be a little shorter form. We’re going to hopefully be able to maintain the same outstanding click-through rates that we see.
(06:57):
We’re going to be cleaning up toxic back links, which just help the sort of health of our SEO ranking. We had a new whole new Level episode on ultra processed food with Dr. Timothy Harlan and our own Rob. And then we’ve launched the Levels TikTok here. So TikTok is explosively viral if it hits, it hits and we have a lot of great short form content that we can use here. So it’s exciting to see that live. We’re going to learn a lot. And then we’re experimenting finally with basically mining through our YouTube videos to search for the moments where our audience is particularly interested and you kind of see these bumps in watch time and viewership and in these certain areas of our long videos. And so we can create sub cuts of those sections of the videos and mind for additional engagement through those. So we’ll be, again, this is all about adding leverage to the content we produced and not letting it expire.
(07:46):
On the support side, definitely still adapting to new change as we work on new infrastructure and update policies like state tax. We’ve got a new refund policy which the team is putting together. So proposal and work to improve our refund policy to be extremely fair and extremely forthright with our members while simultaneously preventing Levels from unnecessarily losing money in a large number of unnecessary replacements. So we’re working on just improving and fine tuning to make sure we give the best experience combined with sensible underlying cost economics. And then we’ve got five weeks under our 7% replacement rate, seven weeks under our contact rate target. So a lot of good stuff going on there. And we’re continuing to iterate with the autonomy team who have been brought on over the past few weeks to scale our support team. Definitely some ebbs and flows in terms of effectiveness there. So shout out to the support team for continuing to do great work. And we’ve got a function dive from Taylor coming up shortly on that.
(08:41):
And finally, Amazon Pharmacy effort is in internal testing. So there’s a comms link up, go check it out, give it a shot. It’s very exciting that we’re here. We’ve migrated PostHog from, this is a bit over my head, but we’ve migrated from a local instance of PostHog to PostHog cloud, which allows us to get seamless end-to-end journey visibility for engagement and other analytics, which is really a huge lever for us. And we’ve also merged these into a single instance so engineers can test event firing locally. So just basically gives our engineers much more control over visibility. This will work very closely with our measurement project and it also is a huge benefit to the growth team.
(09:20):
And finally, our single merged app for iOS is going live or is going into internal testing next week. So we’re just polishing that up. Tons of great work from product and ENG over the past several weeks to get that going. Okay, lots there. We touched on all of it. All right, quick culture and kudos. So Matt has jumped head first into the growth team. Big shout out to Matt owning all the analytics over on the growth side and really just getting up to speed super fast. There’s just an unknowable amount of chaos happening as you try to take on these new data streams and learn them end to end. And Matt has been wrangling that admirably and really helping us all better understand the data sets and how those align with RP zero metrics. So there’s tons of this happening, but just really want to shout out Matt for the adaptability and taking this on head first.
(10:14):
All right, another highlight. So new product ideas. We talked about this last week, but the comms channel for new product ideas is live. We are building a product that we love. So please do not suppress your feedback, do not suppress your ideas. Even if we can’t work on them now, which in all likelihood we will not be able to work on them now, it’s really important to create a backlog of features that we can build that we want and will use and that we think other people will want. So a couple ideas that popped up in this channel this week. Notification management, community challenge ideas, manually generating insights, and then food log macros leaning into the AI ChatGPT revolution. So hopefully these get your wheels spinning, get into that comms channel, share your ideas, don’t be shy.
(11:00):
Company objectives, keep this one in mind. This is my background, but does this get us to 10% month-over-month growth? This is the end. Now let’s all think about ways that we can contribute here. It’s not just a growth effort, right? And we charged through that. This might be a short week because we do not have a special guest this week, which is just fine. So we will jump into Victor’s design update over the week.
Victor (11:29):
Okay. So we’ve had accountability top of mind for some time now, but what is it? Why is it important and how do we want to do it? To start, we’ve been hearing from our members that they’re missing ways to set goals and to stay on track of their goals. Just buying a CGM itself is an indication that people do want to stay accountable, and take control of their health. They want to understand how outside factors like diet, sleep, and exercise affect their overall health. Cosmos mentioned this recently and we’re doing an okay job to signal what high blood sugar means generally and what you can do to minimize or even avoid it. But we’ve been pretty ineffective in aiding people whether at currently and how to interpret their own health data.
(12:11):
As an anecdote, I’ve recently had pretty high glucose readings during the nights and mornings for really no apparent or obvious reasons like late night snacking or alcohol. But they increasingly become better throughout the day, throughout the afternoon and into the evening, which is pretty much the opposite to most people. So what’s really going on here? Those are the kind of things that I want Levels to help me understand. So what can we do to help? Well first, in order to shape our design process before going straight into solution mode here, we want to align on some key user stories, explain our uses, wants, needs and motivations along the way. Who are they? What do they need and what’s their motivation behind it? Knowing this, we can help identifying users or help ideating solutions based on their needs.
(13:00):
So these specific four areas is where we primarily want to focus on for our user stories. It’s around empowered goal setting, smart meal logging, positive reinforcement and education. We of course do all this to an extent today, but we think we can really improve intention here if we listening to our users’ needs and wants around these four. So let’s start with a story around empowered goal setting. The story we want to solve for here is as I progress through my health journey, IE, who they are, I need the ability to flexibly set and adjust goals according to my progress IE what they need. With easier and more upfront access to my data, I can make informed adjustments enhancing my commitment to my wellness journey, IE, their motivation around it. So we’ve heard the members that are missing a better way to set goals and also make those goals customizable and adjustable that adapt to where they’re and where they’re going in their health journey.
(13:51):
A couple of options we’re identifying as we’re exploring this is to make our daily goals customizable. Our daily goals, the checklist as you know and maybe love today and adaptable to where you are and your journey and what your health goals are long-term. Think here for example, the activity rings from Apple watch. So moving on to smart logging. We’ve also heard feedback from the recent evolution and launch of our logging that while we receive great data from our new tagging system, the overall process causes just too much friction and confusion today. We still think we can build around the current iterations. So we wanted to make a story around meal logging here and considering how it’s a central feature in a core loop today. So the story is as an optimizer, I need an easy to use meal logging feature that provides immediate feedback on the impact. Immediate think, for example, synthetic maybe graph, but at least a score, immediate feedback on the impact of my blood sugar levels and other potential blood panel analytes.
(14:47):
So for example, how a meal log can reflect back to your latest blood panel and certain analytes within that. This helps me shape my dietary decisions that align with my health objectives. So we want members to see and understand the connection between actions and outcomes, but in order to do that, we have to make the process as frictionless as possible. We can improve on the current flow as is, but we also want to identify tools that can make things 10x faster than us or for us rather. So if we use Bytesnap here as an example where a meal log or a meal picture rather tells us everything we need to know, maybe not everything but everything we need to know in order to surface that knowledge back to you, just snapping a picture of the food and getting an instant result that could be a two second process, five second process at least, which is much, much quicker than it’s today.
(15:34):
Meal logging is and will be for the foreseeable future core loop and a future feature that needs to be a win-win for both parties. You give us enough data about your meal and we should be able to give you much more valuable data back in return. Onto positive reinforcement. So we ask our members a lot, we ask them to log food, we ask them to complete these tasks every day, connect with Apple Health or their blood panels, et cetera. All this makes sense, but if we can’t give people enough value from our ask, they will not only stop doing it, but they will eventually churn. So the story around this is, as someone who thrives in positive reinforcement, I want to be rewarded from completing daily tasks and streets that lead to my health goals. This helps me to keep up my habits and motivation to continue and encourage me to share my achievements with my community.
(16:20):
So I don’t think this one needs to be so hard or serious to do, but we really do need to do a better job in celebrating people’s wins small and large and they will be much likelier to keep going. The health journey I think is often a very lonely one, right? So unless you have close peers doing something very similar, your community will be small if not non-existent here. So I think in this case, let’s be that community that they’re missing and cheer them on along the journey.
(16:45):
Lastly, education. Obviously our members have access today to vast amounts of education both from our content team as well as learning from their own data. But how accessible is it really here? So story goes, ask a lifelong learner, I want to understand the nuances and implications of my health data. This means I need access to digestible relevant information that enhances my understanding of my health and empowers me to make informed decisions. For example, it’s much harder to find glucose data than it used to be. The stability score is gone from the today screen. We have stability ring, but the score is gone. We know that people like that a lot. The Explorer screen, while it might not have been a huge success, it is gone and have been for some time. There are more examples, but the point here is to make information we have available when our members need it. We know a lot and we have a lot to tell our members, but we need to find the right avenue, the right timing and format to do so.
(17:34):
These are the four stories we’re based on this accountability project round. From here, my job is to come up with options, how to target the problems within each story, discuss with product and engineering to collectively decide what we think is most high value and create wide-frame flows. While this specific screen from a wireframe has no real significance other than reflecting back to a meeting I had with Sam the other day when he mentioned the old wireframing tool Balsamiq. This is from Balsamiq and I think while I had its purpose, I’m frankly pretty glad it’s gone. When we feel good about these flows, we’ll like to be able to start edge work from this point for any structural work, but we’ll probably also want to create high-definition designs of key screens within each floor that makes up the majority of the UX. And from here, engineering should be able to mostly refer to these key screens and components from their design system to implement the majority of their overall experience.
(18:21):
If not, which is likely depending on project, we probably need to fill any potholes within the design system so this workflow becomes more and more true. Lastly, and this maybe it depends on the product itself, but depending on any given solution here, there might be interactive moments during a flow that wireframes nor high-definition designs can communicate. This is where interactive prototypes might be needed, like this one, which holds no other relevance rather than showing a specific interaction here. This is likely to come into play during their rewards and celebrations work, which is a lot of times a very gamified experience.
(18:55):
So overall this is a new era for a design product and engineering and how we all work together. This is the first big project. As the company evolves and while we might stumble on some roadblocks along the way, I think as long as we focus on the process here and how we learn from past experiences and how we work together, I’m super excited to work with all you on this and other big initiatives as we go from here. So as usual, feedback is always wanted and appreciated. So let me know what you think as we start this. Thank you.
Josh Clemente (19:19):
Awesome. Yeah, a lot of great stuff there. I think the accountability project brings in a lot of these concepts that we’ve talked about for a long time, packages them into one of the core themes that the evolution beyond all the basics includes. And I’m stoked to see the sort of scrappy approach that Victor’s laying out here. All right, I think we got… Yes. So we have a function update from Taylor. Number experience.
Taylor (19:58):
Hello, I’m Taylor. I’m pretty sure everyone that works at Levels has either met me or knows me at this point, but just in case this is a function update, which I’ve never done before. We’re going to do the best we can here. This is the structure I was given to be fair, so I just rolled with it so I apologize in advance if you are so bored out of your mind, go for a walk. Okay, day in the life, none of my days are the same, even though these core responsibilities really don’t change that much, what tasks fall into them on a regular basis change frequently. So that’s kind of cool because I get bored easy. Support escalations. All of the full-time team members share the load of handling escalations from our contractor group autonomy.
(20:44):
So every day there’s some number of escalations from them for either they don’t know how to do a task, so we’re educating or there’s a task that needs to get done that they’re not necessarily qualified to do quite yet or they’re escalating a potential bug or something like that. And then from full-time team members, I usually will take care of something that is like I’ll take over a ticket if it falls into the support and engineering bucket and it’s a bug that we’re going to try and figure out or if it’s a retool or a stripe issue, that’s usually something that I would take care of as well. On the TruePill management side, I took that over from Chris some time ago. I couldn’t really tell you when, but I run those meetings every week and I try to make sure we don’t run out of inventory, which let me tell you is a process.
(21:30):
Doing that and then navigating delays and putting stopgap measures in place or whatever is necessary to make sure that we don’t run out of inventory, that is out, that isn’t me. And then also under TruePill management is packaging stuff. And then right now I’m reevaluating the mailers that we use and picking out a new vendor, picking out the mailer and then I will work with Ben and do designs and we’ll get a new mailer, which is super exciting. Some people don’t get thrilled about packaging, but it tickles my fancy. So that’s that.
(22:00):
And then support and engineering. This came out of Commerce 2.0, which feels like a completely different lifetime ago, but it was only seven months ago. And I started serving as the bridge between the two teams during that project because things were just changing so quickly that it made it easier when each team was only communicating with one person and that culminated in this doc here, it’s not really a doc, it’s a project page. This used to be the Commerce 2.0 project in Linear and now it’s support ops triage and it’s evolved quite a bit. It was Commerce 2.0 and then eventually it just became the dumping ground for any and all support tickets for whoever was on call for engineering. And now it’s much more specifically related to customer experience, operations and related types of issues.
(22:47):
And it can come from anyone. Previously it was all support that was creating tickets in here and now anyone on the team can put a ticket in here and it makes me happy when somebody else adds a ticket here. I’m like, oh my god, they’re using it. It’s exciting. So support will come in and add new tickets. I will triage those every day and get them where they need to go, whether that’s the backlog or over to the on-call engineer or a specific area owner, which is a new process that we’re working through with backend and just keeping this as an organized, reliable place for both engineering and support to just manage the issues that we encounter in all the different areas. And I do a daily roll-up post at the end of every day of new tickets, what’s going on, things that need attention and that kind of stuff. And that gets posted in the ops support channel, if you ever feel like reading one. Sometimes I will throw in GIFs to make people laugh, so that might be worth a visit.
(23:40):
And then projects and random tasks, this changes frequently. Kind of similar to what I say down here. I will literally help wherever and on whatever. If I see that there is a need and nobody is doing it and I have time, I will just do it. I have always been like that. That’s how I ended up taking accounting classes at my job three jobs ago. I will just do, so I will pick things up sometimes that aren’t necessarily related to my role, like copy editing for Chris. I can’t let him send out an email if there’s no commas in the right spots. I must. Sorry Chris. And then projects, most of it is DRI like related. This memo which will be live by the time everybody watches this, but anything that is in supporter operations where something could operate more effectively, more efficiently, more cost effective, I will try to pick up when I have the chance to just to keep things buttoned up.
(24:37):
And I’m also a firm believer in if you can button things up when you have time, it will make busy seasons so much more manageable. So I really try to do that with the ending of beta. This became the thing I wanted to do most because I was like, I’ve wanted to do this, so working on that. And then major deliverables, these are the DRIs that, I don’t know why I was doing air quotes for that, these are the DRIs that I’m actually responsible for. And then these came out of past ones support and engineering came out of the fact that I was like I would support DRI for Commerce 2.0, TruePill, I would support DRI for the RX to OTC transition. So it’s like some of my past project DRIs ended up laddering up or giving me a path to do my current ones.
(25:23):
And then ways I can help, I’m happy to help in whatever way I can be helpful. I think I’ve had the benefit of working with I think most people at Levels now, at least in some capacity. So I’m always happy to be helpful if I can lend a hand. And whether it’s copy editing Chris’s emails or working through an issue or talking through a policy change or anything related to the customer experience, I’m happy to help. I’m also incredibly organized to an annoying degree, so if you need help with that, I’m your girl. And I’ve project managed in three different fields, so decent at that if I can be of service there too. So that’s it. If you have any questions, let me know. Otherwise, thank you for listening to me talk about myself for nine and a half minutes.
Josh Clemente (26:16):
Right, thank you Taylor. This is the format we’re going with these days is function updates, so we’ll do more deep dives like this. I definitely would love, and first of all, I appreciate everyone participating in this. Thank you Taylor for of all the broad spectrum that you are working on and also taking on a small project like this to share that across the team. Definitely would love to get feedback on the approach we’re taking here with Forum and how to continue to add important and insightful segments on what each function does and each individual does. This is the format for that. So thank you Taylor. I think we have basically just raced through today’s meeting, which that’ll happen sometimes. No hiring updates. If you’re watching this and you’re interested in what we’re up to here, check out Levels.link.careers. As we continue to cross our goals this year, this slide should change proportional to that success. We’ve got a lot of time for individual contributions. Stop the share here and let’s jump into it.
(27:29):
I’m going to go ahead. You can raise your hand with a little reactions thing at the bottom. I’m just going to say four years in, I did a little scrolling through my phone and my photos and touched on each June over the last five years actually. And it was not much after this point five years ago that I was driving cross country with all my belongings in my truck too poor to get a hotel, so literally sleeping in the bed of the truck on the Rio Grande River. And I happened to just stumble into Sam at the convention, at the Albuquerque convention that I stopped by on my drive to Philly and that was the first time we talked about what would ultimately be Levels.
(28:08):
Four years ago we were doing the meetup where Sam and I had filed the incorporation documents and we were just meeting people and we met David and we met Andrew Connor and we met a couple folks who are now consulting with us or have contracted with us and just that was the first real event and I put a little photo of that in the comms thread and it’s really crazy to. I feel like we’re still in that moment. And then I zoom out and I see where we are and how sophisticated our functions are and how much we’ve impacted so many people, tens of thousands of people and we are still obviously just getting started.
(28:45):
And then also second contact yesterday, the team just want to shout out by name everybody who just crushed it yesterday, Sean, Subi, Jesse, Adam, Daniel, Jeremy, just putting in first of all a very long day, but many, many long days to get to the point where we were able to do a pretty sophisticated biological test in vivo, safely in a sterile manner, and then get great results. Adam’s burn the midnight oil to get our first data there and we’ll continue to do so with Daniel and it’s just amazing. So thank you team. Thanks Ben for coming in and filming that. We should have some good content to share with the rest of the group. And yeah, I feel really super stoked four years into this thing for another 40 of it. I want Levels to be a household name for generations and I think we’re going to make that happen. That’s my personal and my professional way. Hui?
Hui Lu (29:44):
Yeah, first of all, Taylor, love your update and thanks for being an amazing partner to engineering as always. I remember when I was interviewing and I was talking to Josh and there is the prep material that Josh sent me beforehand about reading all the R&D side of things and at that time I was like, yes, I want to join this because I love just how we are doing things on R&D side. For me as a software engineer, I know what the impact I’m going to make is on the software side, but the R&D side of things, I feel that’s really what’s going to make Levels so unique and also to make the real impact in the world as I always have been wanting my career and my part on my career contribution would be.
(30:35):
And it felt like a crazy dream when I was talking to Josh and also after joined listening to the R&D side of things and it started to feel more and more real increasingly and more recently. And then this morning when I was talking to Sam, Sam was like, this was the first time or I guess the time window that we started to feel their likelihood on the yes side is higher than on the no side. So that’s really exciting to hear. I guess I just also feel very excited and just want to share my excitement on this. And yeah, just big shout out to the R&D team.
Josh Clemente (31:22):
Thanks Hui. Yeah, I remember those conversations well, so I’m glad you’re still stoked about it. Ryley.
Ryley Walker (31:31):
I wanted to actually give two professional shout outs. One to the growth strategy memo and just the growth team for rallying around growth, documenting where they’re headed in a really clear, understandable way. That is just such an important rallying point for where we’re headed as well as my function specifically is so much easier to plan and look at numbers and understand where we’re headed when those things are all documented and written out in an understandable way. So that was just awesome to work with Tom and the growth team on that. Also have to say awesome update Taylor and I love that format because it’s so important that we’re scrappy like that. It’s such a scrappy like hey, this is what we’re doing, it’s organized, but also whatever it takes LFG. And so just love that update culturally and professionally.
Josh Clemente (32:40):
Thanks Ryley. Mike D?
Mike (32:45):
Yeah, so a couple of quick things. Just want to give a quick shout out to Jackie. As I’ve started to get ramped up on the growth team, Jackie has just been super helpful, extremely organized, and just making it as simple as possible to absorb so much information. So I just want to say thank you to her and obviously to my man TG. And then, yeah, it’s pretty wild. It’s on my calendar the birthday of Levels and I’m not really that good at taking stock of things as I’m definitely more the person of what I did yesterday or the past doesn’t really matter and what we do today and going forward matters, but it’s pretty wild to just, we may have had a tough time recently, but to think about all the things that we’ve done and all the momentum that we have, it’s just really motivating and obviously Josh, thanks for being the guinea pig and let’s fucking go.
Josh Clemente (33:46):
Nothing to add. Mercy.
Mercy Clemente (33:51):
I watched the four year video right before getting on Forum, so I was already excited and then getting on Forum and seeing everything recapped, it’s just really cool. It’s cool to see how much has happened in four years and also in the three years I’ve been here is really wild. And then being in the office yesterday for second contact, it was a long day but it was really crazy. All that happened and it was accomplished in one day is just definitely we’ll go down in history. It’s going to be a big day when everything is just fully up and running and Levels has its own device. I’m just excited.
Josh Clemente (34:29):
Yeah, it was one time we got a bit of an audience there. All right folks, we got more time so we’re going to have to fill this one way or another. Any other shares? Chris?
Chris Jones (34:43):
All right. As you guys probably know, I’m out walking the dogs because that’s what I do on Friday Forums. Welcome to Montana on a beautiful day, hashtag Farm embl 2.0 coming sometime soon to you. Ryley already approved the budget. A couple things. One, the four year video was incredible, so thank you for everyone on that. That was just great to see the memories and how far we’ve come and what we have left to do. Personally, later today I’m driving up to the great white North to Furney Canada for a gravel bike race and I’m going to drive Ryley under the bus because he is not coming down to cheer me on and I’m just trying to figure out, where are the props? So wish me luck. If I am not back, I’m eaten by a bear somewhere in Canada.
Josh Clemente (35:36):
Enjoy. Chris, that sounds like a blast. Looks like beautiful weather there. Casey.
Casey Means (35:41):
Hey everyone. Yeah, just want to plus one to everyone about the R&D. It’s hard. We’re all moving so fast, I feel like it’s important that we just don’t take this in too much stride. It’s like science fiction coming true. It’s incredible. This is not just big for Levels but feels like it’s big for the scientific and medical community. This next step towards bringing a new technology to the world, it’s so incredible. And Josh, I’m just really in awe of you having this idea and now it’s coming to reality. That is amazing and so amazing that the whole R&D team is just crushing. I wish I could be a fly on the wall and I cannot wait to see the video that it sounds like Ben took. Can’t wait to watch the four year video. I can’t believe it’s been four years. It’s been the best four years of my life, or almost four years for me. And it’s just so exciting. I can’t wait, like you said, for the next 40.
(36:48):
On my end, loving L.A, really enjoying living here. I’m going into week four now and I’m just spending a lot of time in my backyard. I’m really happy. I hope people will come visit. I got a cold plunge, which I’m really excited about and so come, this is the carrot to have people come visit me. And my brother and sister-in-Law and nephew and dad are all going to be here this weekend and I am so excited to see my family and my sweet 15 month old nephew. So that’s what’s going on with me. Hope everyone has a great weekend.
Josh Clemente (37:27):
Sounds awesome. Well, I’ll definitely have to come try out that cold plunge, looks quite legit. A lot of fun. Love this team. Happy four years and have a great weekend.