- Duration: 62 min
- Platform: meet
- Attendees: Jamie Barnes, Michael Houck, ✨ Michael’s AI task manager via Hoop.app
- Source: Read.ai 01JP60D1MHZVMDP10H799MBW4C (https://app.read.ai/analytics/meetings/01JP60D1MHZVMDP10H799MBW4C)
Transcript
[Michael Houck]: Hey, Jamie. Good. [Jamie Barnes]: Well, we got a lot of note takers in here. [Michael Houck]: Let me know. I was like, I’m not sure which one you’re using. [Jamie Barnes]: So I was going to put everybody in. Yeah, I don’t know. [Michael Houck]: I usually use the read AI one. The other one is one I’m just trying out. But I wish I didn’t need any of them. Honestly. [Jamie Barnes]: Anyway, what’s going on? And then good. Lots of changes. I don’t know if you’re updated on the GLP-1 space, but yeah, lots of changes there with what we can sell and what we can’t sell moving forward. From a regulatory perspective? Yeah. It’s like they’ve removed terzapatide and semaglutide from the FDA shortage list, so we can sell compounds soon. That sounds disruptive. It is. It is. [Michael Houck]: It’s a good thing we’re pretty prepared, so we’re good. [Jamie Barnes]: Good. [Michael Houck]: Yeah, I can imagine the sort of landscape there is probably still going to be evolving over the next couple of years. So always got to be prepared for sort of black swan changes. Yeah, for sure. Okay, well, so I caught up with Matt, I guess it was two, I guess it was on Monday. So we talked about this. I think that, and he agreed when we chatted, that there is one option we can do if we want to stick with the current process, still be sending the newsletter out through Beehive, sort of not require any additional operational lift on your guys’ team. Basically, the reason that we import folks slowly initially into new newsletters is for two reasons. One, it’s because it’s less of a risk for deliverability and things like that. And two is just because these companies don’t have, in a lot of cases, big email lists like you guys do to pull from And so if there was a situation where the platform was like, where did you get all these emails from, you guys can easily, we have a big email list that we can pull from, right? So it’s more in line with reality, I would say, than it would be for some company that was just starting out and just trying to build a list through the newsletter from day one. So I talked about this, and what we can do if we want to stick with Beehive is basically just make a couple big imports over the next two weeks into Beehive. So it’d be like, where are we at right now in terms of the subscriber count? I’m logged into a different Beehive account right now, so I don’t need it. [Jamie Barnes]: Let me try the other one, too. Yeah, we’re at 3,485. UNKNOWN_SPEAKER: Right. [Michael Houck]: Yeah, right. Okay. So yeah, so basically, we could realistically get that up to the full amount that we are supposed to be delivering by the end of the second month, basically just doing a big batch in this coming week and then a big batch the following week. So that’s way number one. And again, that’s sort of minimally disruptive for you guys on the operational side and also just process-wise for how we’re working together. The other path we can go is I think what you and Matt talked about, which is where basically we are moving the send into customer IO alongside your guys’ other emails. We ourselves, due to obviously the HIPAA restrictions, aren’t in there, so there is operational work on your guys’ side to schedule the emails, send them out, et cetera. But Matt would be delivering the subscribers via API, and we would be delivering the content to you just in Notion, and then you could sort of do as you pleased with it from there. So either one of those solutions gets us to where we want to be. Just comes down to just a choice of which direction we want to go. [Jamie Barnes]: Yeah. I was kind of worried about deliverability. So like Matt’s leads aren’t the only kind of like non-opt-in leads that we’re getting now. So if, you know, that compounds, I’m not sure, like, it’ll be safe at some point. Like if we’re doing that project and we’re doing this project all out of custom Rio and all out of our domain. Not really sure how safe that would be, which is okay since the other one we could always pull back the lead volume. The only reason I wanted to run on a separate domain was that, right? But I think if we’re going to do a few big imports over the next weeks. So we can hit our what’s the first month goal for the leads was that 10,000 leads is what? [Michael Houck]: Yeah, it was 10,000. And then we we reduced the second month to to 5k. Yeah, so our goal is 15 by the end of the second month and feel comfortable, we can hit that if we’re doing this bigger. But for context, Matt is sort of very, he’s focused on like cold email, best practices, and those don’t really apply in full with newsletters because we’re working off of this really large, robust infrastructure set up that Beehive has to send a lot of these emails. And so, like, for example, when I started my newsletter, you know, I was importing one to 2000 people per week, totally cold to the domain. And, you know, I think our deliverability dipped a little bit down to like 97% for a few weeks. But then we turned some of those people out. And also the domain just, you know, was resilient. And so we were back up to, you know, consistently like 99 plus every week now. So it was very short lived. [Jamie Barnes]: There’s only a couple weeks that that happened for. Got it. Yeah. And I think Matt also mentioned that they could kind of like call the other leads that aren’t engaged, and then kind of top up the lead. So we’re always at like the level that that we’re kind of looking for. I think the thing also, the reason why we wanted to migrate over to customer IO is we have our custom ad audiences and we can do retargeting through there. I don’t know if we could do that through Beehive actually. [Michael Houck]: We could create segments, but we’d need sort of custom fields added to the list. Maybe Matt has a lot of that data already, so we could probably add some of it. But we’d need to go in there and set up segments, and then you could just download CSVs from there and pull audiences from them. [Jamie Barnes]: Got it. Yeah. I mean, because the thing with customer IO, it’s automatic. Every time they do an upload, it’s just going to send it over to Meta real time. And the team isn’t going to have to do any manual uploads. Sure. That’s kind of what we want to avoid. But yeah, Matt mentioned that we’re just not going to get enough value out of the audience if we’re kind of just running the newsletter out of Beehive. And that’s all we’re going to do. Next week, I’m going to be working on a binge eating course that we have. It exists, but it’s not in a great format for now. So I need to put it in a PDF. Make it downloadable. And yeah, I think we’re going to offer that to the people in the newsletter. So then they actually opt in to our marketing, then it would be much safer for those people. Yeah. So actually, yeah, it’s just more, I think more, you know, less work in the long run for us if we migrate to customer I know I mentioned to you before, like we take your content off of Notion and we post it, we send it anyway to our list. So I think in terms of like duplicating work, I don’t think it will be a lot because Edward, the email marketing lead, he does that every week anyway. So yeah. UNKNOWN_SPEAKER: Okay. [Michael Houck]: I mean, that’s fine. We’re happy to work with whatever structure makes it easiest for you guys and makes you guys able to get the most value out of it in like the easiest way. So if that’s us delivering the notion content, and then you guys sort of taking that into customer IO. And again, you know, we’d obviously be happy to help out with customer IO portion, but I know that there are because it’s health, there are data considerations there with HIPAA. So let us know where that line is. And then, you know, we’ll do everything that need us to do sort of up to up to that line. And can obviously advise on on how to how to leverage it if that’s helpful to Cool. [Jamie Barnes]: Yeah, I think what we could do is I could give is it just under that would need access I could give him access to customer IO and He He could go in there he just won’t have access to our customer data so he could build emails But he won’t be able to actually like select the segment and send it and stuff, but he could build it Like in the video builder. [Michael Houck]: That could take some stuff off your plate, especially if we have a template set up in there that he can just drop the content into. That would work great. I don’t think we would need any access other than that, unless there’s other things that you want or need us to do. So that should be sufficient. And then also, it’s already in there if you guys want to move the content around and do other things with it, too. UNKNOWN_SPEAKER: So that works. [Jamie Barnes]: Yeah, works for me. And then, yeah. We sent Matt a BAA because they’re going to need access to Customario. I think they’re going to do daily imports. It’s kind of late in the week. I think we would be able to migrate by Monday. If ever, we’ll see what happens with Matt if we’re able to, because I could just export people out of Behive and import them into Customario. But yeah, I’ll let you guys know if, if we’re still going to send the one through beehive on Monday, the next one, I think I still will. Um, yeah, I need to like, I need to like sit and think through it and like figure out like, what’s the best thing to do for, for next week. Yeah, totally. That makes sense. [Michael Houck]: Um, just keep us in the loop. Um, I’ll monitor the Slack channel and I’ll have Andrew do the same too. So if we’re not going to send, even if you let us know on We’ll probably see it before so whenever you have a chance And then yeah, you would also mentioned like that course You know, I think happy to happy to be a little flexible here and help out Sort of as needed with some of that stuff since we have had so much kind of turbulence back and forth early on What I want to make sure you guys are feeling good about everything. So if there’s anything else we can do to help out. [Jamie Barnes]: Let me know Yeah, I think Some, I think some of the, the only kind of like help that I might need is like copy for pitching that course. Right. So we have the newsletter, we send them the newsletter, but we also want to drip like an email series. You know how you send like the welcome email, you’re going to have that. We’re also going to offer them, you know, the The course, and then they have to like confirm their subscription. Then once they’ve confirmed their subscription, um, Yeah, we can we can actually start them on our email list. Yeah. Cool. Okay. Sounds good. [Michael Houck]: Well, just let me know where you land on all of that. And what you need and want us to help out with and sort of where that line is. And then we’ll make sure that Andrew is available to do all that. So yeah, I think let’s see how that goes over the next week or so. And then we’ll touch at that point, and can determine the right next steps. I think right now, if I’m up to date on the WhatsApp chat, the plan is to cease on the 26th, because we want it to be paused by default. So the sooner we can get clarity on what that future state looks like, the better. But as of right now, our plan is to work with that basically two weeks from today constraint. So we should touch base next week about what the right next step looks like, [Jamie Barnes]: Yeah, sure. So I’ll give you an update tomorrow on whether we’ll be able to migrate to customer IO by Monday. And then I’ll let you know about the binge eating course next week. And then I think because once we start running retargeting for these leads, we should have better from them if they start seeing your ads as well. So yeah, we’ll have like a definitive, like, what are the results? Kind of like an answer to that question probably next week or two weeks from now. So. UNKNOWN_SPEAKER: Okay, cool. [Michael Houck]: Well, let’s just stay in close contact and we can just go from there. UNKNOWN_SPEAKER: Awesome. [Michael Houck]: Thank you so much. All right, Jamie. Talk soon. See you. Great day. Bye.