- Duration: 32 min
- Platform: zoom
- Source: Read.ai 01JBW6VQF1ZD1AFN62RMWQYGV8 (https://app.read.ai/analytics/meetings/01JBW6VQF1ZD1AFN62RMWQYGV8)
Transcript
[Michael Houck]: Can I eat my lunch here? You can eat your lunch here with the bears. [UNKNOWN_SPEAKER]: Dove bears. [UNKNOWN_SPEAKER]: We need to have more bears in here. [Sid]: Hi, guys. Hey, hey, guys. How you doing? I’m OK. How about you? Good. [Michael Houck]: Good, good. Everyone have a good weekend? [UNKNOWN_SPEAKER]: Yeah. [Rafael Bruno]: Yeah, it was my weekend was without internet because for some reason, people decided that they want internet in their house, in their houses. And for that they need to destroy the internet cables of other houses. So I, I got like three or two days without the internet here. [Michael Houck]: Wow, that sounds disruptive. [UNKNOWN_SPEAKER]: Yeah. [Michael Houck]: I guess the good news is that we’re no longer in scramble mode like we were in October. Things have settled down. [UNKNOWN_SPEAKER]: Cool. [Michael Houck]: Everyone else, anyone else do anything interesting this weekend? No, just chill, normal weekends? Yeah, me too. Okay. So let us dive into The sprint, let me share my screen. So if we look at where we’re at so far, we’re actually doing pretty well. So we have a large amount of things in this sprint, probably more than we should, honestly. Should probably try to cut that down a little bit this week. But we’ve already completed 41 points worth of stuff, which is really good, really solid. That’s almost as much as we completed all the sprint. But a lot of the stuff that’s left is pretty high priority stuff. So we’ve got to focus on it. Where did my screen go? There we go. So if I look at what’s in progress right now, what’s left, we can see that we’re making good progress on the bugs. Groups project is getting off the ground, which is nice now that it’s on it and not on bugs anymore. And if we group by project, we can see that too. The SEO stuff, is pretty much done that we wanted to hold to do this sprint. I think there’s one more test that I need to do. And then the switch to Feather, if we’re going to do that. I’m talking with their support team because they have like a concern about the way our DNS is set up and we might need to move to another DNS provider and that might be too much of a hassle to do. So I have to talk to them and see if that’s easy. But yeah, other than that, pretty good. All the urgent stuff is done. We’re making good progress on the high priority stuff too, so overall feeling pretty good about where we’re at. As far as what hasn’t been done, the new account shelf, I think that’s pretty small. It’s probably less points than all these elements individually. We’ll try to get that done this week, but it’s not super high priority, so no big deal if we don’t get to that. The group stuff is much more priority. Priority. And then, yeah, I mean, the group stuff and the referrals page stuff is the biggest, biggest it’s left. So, Rafael, I’ll toss it to you to get us started. Where are we? Well, actually, before I do that, I want to let’s start something new. This meeting, I did not give Ben a heads up about this. So I’m going to put him on the spot here. Ben, can you give us a rundown of how the bugs bug reports from customer queries have been through intercom this week? [Ben Ornstein]: This week as in today or? [Michael Houck]: As in since last Monday. [Ben Ornstein]: OK. Yeah, so I mean there have been. Most of the stuff was. Onboarding related mostly it was like either had just recently, or they had questions about their accounts if they’ve just gone live. And I don’t know like the exact problems with a lot of them, just because I’ve just said like, hey, like Rafael, for example, there’s a problem with this guy’s account. Can you, you know, assist? And he very swiftly helps and all he do. Thank you. But, um, a common bug that I saw, well, it’s not in a bug. It’s just, it’s an interest. I don’t know how we solved for this is, um, when a user switches their URL for LinkedIn or Twitter that requires us to manually kind of update that. Um, that’s one that we’ve gotten. I think, I think we got four or five times last week. [Michael Houck]: Um, four or five times, no way. 4.5 sounds really high. Maybe, I think, at least two or three, maybe. [Ben Ornstein]: I remember solving, like, two, three issues related with URLs. [Rafael Bruno]: That’s so crazy. I feel like that’s, like, such a rare thing. [Michael Houck]: But it definitely did happen more last week. I remember that. Yeah. [Ben Ornstein]: And maybe it just happened to be one of those weeks where it did, and it’s not always like that. Yeah, other than that, it was, yeah, I’m trying to remember. A couple of bugs just related to, man. Yeah, sorry, I’m really blanking here. No, it’s OK. I totally understand. [Rafael Bruno]: I’m very glad that we are not seeing payment bugs anymore, which means that all the issues related with Stripe seems to be solved. Yeah. [Ben Ornstein]: All of the bugs seem to be small ones. We aren’t going like back and forth like a million times on things, which is pretty awesome. They all seem to be small bugs, which is a great sign. [Michael Houck]: Yeah. I think having the payments ID stabilized is really important because those bugs tend to be pretty tricky to solve. They’re also really frustrating for users. Onboarding is also a key area that we, I think, are getting a handle on the bugs. But we just got to solve those quickly, because that’s our first impression with users. And so if they have bad first impression, they’re probably like multiple X more likely to churn. [Rafael Bruno]: So. I have a bunch of those onboarding bugs. I didn’t have the time to stop and make a full analysis. But I imagine that some of those bugs are related with people that they left their emails on the landing page, and we store them as users on the on air table. But when we migrated to this new onboarding flow, the data from those users were not ready to be used in their onboarding flow. So that’s why it was causing a those bugs. This is my hunch. I will try to spend a few hours fixing those data so we can hopefully decrease the number of bugs related with onboarding. I think that’s a pretty good hunch. [Michael Houck]: Because that would make sense why the bugs are sort of popping up at random times. And yeah, I think the couple users that we’ve seen that from most recently were people who probably left on there before. Let’s spend some time on that, but not super urgent. I think that the higher priority stuff is some of the bugs we already have in here, as well as the group stuff, obviously. So Rafael, if Sid needs help with anything on groups, that’s going to take priority right now. But I’ll add something in here for, and we can maybe even push it next sprint, if we have to, but that’s something in here for research data from Airtable. Research if data from Airtable is influencing onboarding bugs. OK. [UNKNOWN_SPEAKER]: You said a couple hours? [Michael Houck]: Yes. Low priority. Yeah. Cool. OK. In that case, Rafael, do you want to kick us off where you’re at on your stuff? [Rafael Bruno]: Sure. Last week I was solving some problems related with all the flows on Stripe. I started that task, but I didn’t have time to finish it. I will finish that today. Today I was also helping on some bugs that were were popping out. And besides that, today I also intend to work on the task to see if we can downgrade the machine that we have on the database so we can reduce our AWS cost. [UNKNOWN_SPEAKER]: Cool. [Michael Houck]: And then as far as, let me actually just pull As far as what’s left for this week, can you give me a sense of whether we’re going to be able to get through all these or if we’re going to [Rafael Bruno]: push some to next sprint? Let me see. All of those bugs seems to be either XML or XML. So I guess we can, hopefully we can get like 90% of them. [Michael Houck]: This is a medium one that we can push to next sprint. This isn’t urgent at all. So I’ll just move that one now. But yeah, the rest are all pretty small. So hopefully we can get through most of them. I’m sure you’ll also be pulled onto some other things too. So just make the progress that you can. The one thing that I would say is important is the referral tracking that we talked about this morning and making sure that’s set up. So the URLs and making sure that it’s tracked then also when when people make it through and get onboarded. And then also we wanna set up template messages for posts that are sent, broadcasts that are sent via InnerCircle, because it’ll be a slightly different template than we use for the Creator Network. And then I have SMS in here because next sprint we’re finally gonna do we’re finally gonna do SMS. We’re finally gonna enable that. [UNKNOWN_SPEAKER]: Okay, cool. [Michael Houck]: So we’re talking about groups. Sid, do you wanna go next? Yeah, sure. [Sid]: So I completed a few other tickets so that, and now I’m working on the group sync. So a few things about groups are completed. For example, creating and allowing people to join the groups, a group like in a circle that is completed. And currently I’m working on the share, in the inner circle. So that one I’ve set up some, like I’ve set up on my local system, local database, and it’s going good. I don’t have any blockers. Basically I’m able to share a broadcast with people in my network, in my inner circle. So I think I’m going, like I’m doing good with this. I don’t have any issues or anything on this one. I think I’ll be able to finish this one in some time. And then I’ll move on. To other tasks for the groups. Yeah, I think that will be my priority for this week. Cool. [Michael Houck]: And for 893 in particular, you’re also testing the case where someone is going to share a broadcast with their inner circle and also with the creator network. They also put budget behind it for creators too. They don’t just share it with their inner circle, right? Yeah, yeah, yeah. [Sid]: Yeah, yeah, right. I mean, the idea is that if they choose to share with both the people create a network and in a circle, then only the unique people in the in both the groups and like in both the create a network and groups will be getting the broadcast. [UNKNOWN_SPEAKER]: Right. [Michael Houck]: And we don’t want to like let’s say that let’s say that you are sending a broadcast and Rafael and I are both in your inner circle. I’m a creator, but Rafael is only in your inner circle. Then even though I’m a creator, you shouldn’t, your broadcast shouldn’t get matched with me in the creator network since it’s already being sent to me via your inner circle. So you get that for free. [Sid]: Yeah, correct. You will not be charged in that case. If you are in the inner circle, you will not be charged. You will be charged like only the people who were in the creator network and not in the inner circle, they will be charged. [Michael Houck]: Cool. And then they’ll have the full budget leftover to spend on creators. Okay, cool. [Sid]: So like what I’m doing is first we will share with the inner circle and then with the, uh, like with the creator network and and all the budget will be utilized for that itself. [UNKNOWN_SPEAKER]: Okay. [Michael Houck]: Then you want to talk a little bit about 8.5.6 too, right? 8.5.6, yeah. [Sid]: I just wanted to understand the scope on this one. Scope as in, is it related with groups? If yes, then I can do it, but I just want to understand what I have to do. Yeah. [Michael Houck]: This goes back to a conversation we’d had. I don’t know if it was with you or with Rafael, but we’ve been talking about it a while ago. How we want to enable pricing at the account level, right? So like, let’s say that somebody is signing up with three accounts and one account qualifies as a creator or as an amplifier, one account they wanna keep on the free tier and one account they wanna keep on the pro tier and they’re willing to pay for it on the pro tier. We wanna let them do that. So that would require probably some changes, both in terms of how we handle payments and also in terms of how it’s represented then on the onboarding flow on the pricing page. I don’t know if it’s worth doing this right now because we might change the way we handle subscriptions in a few months anyway. But I just wanna get a sense of like, if we did do this, am I right that this would just be medium and pretty small or is this gonna turn into like a week or two week thing. [Rafael Bruno]: That could be like a large task because it would involve changing some stuff. It would involve, how can I explain, updating all the subscriptions, not all the subscriptions, but updating every subscriptions that we have active to reflect that on our database. Because right now, if I understood correctly, we are charging, I don’t know, $89 for a pro account. And if the user wants to add an additional account, right now we are charging $39, right? But the idea- I think we updated it to just be 89 and 89. [Michael Houck]: I think we simplified it recently. [Rafael Bruno]: Oh, OK. So we will not have the additional accounts anymore, right? [Michael Houck]: Well, we’ll have the additional accounts, but it’ll be at the same price. Yeah, but the $39 product, we will not have that anymore. [Rafael Bruno]: I’m pretty sure we removed that. Yeah. OK. So we would need to update all the users that have more than one account so they can be charged with the remaining cost that they need to pay, right? [Michael Houck]: No, no, no, no. Bought it before is, you know, they’re grandfathered into that tier. We’re not going to increase prices on people who paid for something cheaper. But the point here would be that if you wanted to add a new account, you could choose to add that account on the pro tier or the starter tier. So I feel like that might be a large task, but I’m not sure. [Rafael Bruno]: I think it would be good if that task would be assigned to me. Okay. Because yeah, I’m more familiar with that. How large do you think it is though? [Michael Houck]: Because again, if this is like a big thing, it doesn’t make sense to do it right now because in, you know, December or January or maybe at the latest February, we’re probably going to remove the two different tiers and just make it a kind of pay as you go model where we take a higher commission. [Rafael Bruno]: I think it could take like two three days to complete that. [Michael Houck]: Okay, so medium is probably correct. Okay, let me reassign this to you. I’m gonna make it low priority and I’m gonna move it to next sprint. So we don’t need to worry about this right now. If we get to it before we launch groups and we have bandwidth to do it, great. But if we don’t, it’s not a big deal and we can just keep doing the pricing as it is. The one thing I’ll say that we do need, though, is we need to have people on the pricing page be able to choose the free tier over the paid tier. Okay, cool. But that’s probably a different thing. Okay. Rafael, in case if we do this next print or whenever, like after you’re done with groups, just loop me in so that I know what we are doing, like what I get family with the scope. [UNKNOWN_SPEAKER]: Sorry, Sid, could you please repeat? [Sid]: I mean, whenever we do this, this sprint, next sprint, or maybe any time, just loop me in when you do so that I can be familiar. Oh, OK. I’ll let you know. That will help me. [Michael Houck]: Sid, since we removed that, do you think that you have bandwidth to take on one or two more small to medium-sized tasks this sprint, or will these three take up the week? [Sid]: I think this will take up the week because I share like 893 ticket. I’ll have to test it back and forth with multiple other scenarios, so that might take up a bit. But if I’m done early, then I can take up other tickets. Like in that case, I’ll let you know, for example, by Thursday or Friday. If I’m done, then I can take up other tickets. [Michael Houck]: Maybe maybe the right move then is just if you do finish these early and try to take some these bugs off Rafael’s plate, because he’s got a lot of these small ones that you could probably also take on. [Sid]: Yeah, sure. [Michael Houck]: I’ll catch up with him once I’m done. OK. Mehul, you obviously completed a ton of these SEO little small ones last week, which is great. Where are we at for this week? [Mehul Jariwala]: I guess we are all set. I was almost done with the group details UI. Probably I’ll try to send you the full review. Uh, one more advantage is which you have was like, uh, luckily we moved to the Figma as a paid version so that I can just try to. Check detail of that sizing of the each and every spacing that that is really helpful for me. And yeah, that’s about me, like finishing the groups, uh, stuff, uh, probably this trend. And as we are moving with the group stuff, right. We, we need to focus on building the screen, right. Because, uh, I mean, because I had a chat with Seaton. He was mentioning probably we need to take a look at all of the inner circle as well, right? [Michael Houck]: This is this is for inner circle. The group details UI. [UNKNOWN_SPEAKER]: Oh, OK. The entire UI, right? [Michael Houck]: What’s that? [Mehul Jariwala]: The entire screen of the group details screen will be for inner circle only, right? [UNKNOWN_SPEAKER]: Yeah. [Michael Houck]: Basically, we’re going to have the groups tab show up on the left hand side bar. When you click into that, then the first screen you’ll see for now will be the group details UI, because you only have one group, right? There’s no group market yet. And so yeah, you’ll see this group details UI, but it will be for your inner circle specifically. Okay, cool. [Mehul Jariwala]: Yeah, then then in that case, I’ll just make the changes. According to the inner circle, and it will be condition wise, that’s fine. We can data and we can improve it. [UNKNOWN_SPEAKER]: Cool. [Michael Houck]: Then the other group stuff is also important, just add you onboarding and then the dashboard. Yeah. [Mehul Jariwala]: I’ll get all the group stuff finished in this sprint only. Cool. [Michael Houck]: And then, yeah, if you get to the new account shelf stuff, I think that the whole thing is pretty small because it’s just adding the sidebar, but I might be wrong. So as you get in there, just, just let me know if you’ll get to it this sprint or not. [Mehul Jariwala]: No. [UNKNOWN_SPEAKER]: Okay. Sure. [Michael Houck]: Yeah. Makes sense. Cool. Okay. And then Rizwan, how are we doing on, you’re working on like a variety of things right now. [UNKNOWN_SPEAKER]: How are we doing? Yeah. [Rizwan Hameed]: So right now the current priority is engagement URL. So that’s what I’m doing right now. And because there’s a larger one, I need to make the changes for the LinkedIn and then for the Twitter as well. So hopefully it will be done in this week. And then I’ll be doing the work on the 1-0-3-8. By the way, who moved this into the progress? I made it as a to-do. [Michael Houck]: Which one? [Rizwan Hameed]: Might have been me. Like 1-0-3-8. [Michael Houck]: Okay, we’ll put it back to do. For these other ones, these have been like lingering for a while. I really just want to knock these out so that we can move move on with our lives. How are we doing? Yeah. [Rizwan Hameed]: So basically the quality validations. So it’s a new dynamic, uh, and a new thing, uh, which we need to cater. And similarly, we have the characters count as well. So these are put in the backlog just because of the other high priority tickets. So that’s why they are in the longer queue. So after that, uh, If you still want these to be done, then yes, that will be my next priority. Otherwise, what do you think? Like, are these? Yeah, I mean, yeah, when we do, we do need it. It’s, you know, this is a 300 ticket. We’re in the 1000. [Michael Houck]: We do, we do still need it though. So do you think you’ll get to these this week? [Rizwan Hameed]: No, because engagement URL is a bigger one. So that will take a whole week. Definitely these will be for the next week. [Michael Houck]: Okay. For some reason it’s not letting me, oh, I can move them here. Okay. I’ll move these into the next sprint. Let’s just wrap these up this sprint, including the scrape one day late bug, since that was from, that was from the V2 launch. So that’s, you know, some users might still be experiencing that. So let’s make sure that’s solved. But if we get these solved this week, then we’ll, then we’ll be good. And then next week we can finally wrap up the and LinkedIn bot and move on to a new platform. Yeah, sure. [UNKNOWN_SPEAKER]: Okay, cool. [Michael Houck]: So in total, we managed to reduce a little bit. There’s probably some more things that I’ll chop out of this. The new account shelf is in here too. So probably realistically, we have like basically to do the same thing we did last week, this week, and then we’ll get to a good spot. So anyone have any questions for me? If not, then I’ll let you guys chat No? [UNKNOWN_SPEAKER]: Okay. Cool. [Michael Houck]: I’ll see you guys on Slack. See you, Hauke. [UNKNOWN_SPEAKER]: Have a good one. [Rafael Bruno]: So guys, anything that you would like to discuss? [UNKNOWN_SPEAKER]: Anything from my side? [Rizwan Hameed]: Yeah, so Phil, I just saw a ticker that is there, like the post one day data. [Rafael Bruno]: So is there… Of the ticket yeah let me check it up so it’s it’s nine double five nine sites I suppose yes one day late let me check Yeah, I, I have to check that message again. But I’ll message you. [UNKNOWN_SPEAKER]: Okay. [Rafael Bruno]: Okay. Yeah, I think so. That was it from my side on the One question, are the bots for the late time engagement working or do you need to do something? I believe the superfast and late bots, they are functional. [Rizwan Hameed]: Okay. And after the call, I will again check the logs and the bot on the machines and then we’ll get back to you accordingly. [Rafael Bruno]: Sure, I will make some here so we can use them. [UNKNOWN_SPEAKER]: OK. Fine. [Rafael Bruno]: How about you, Mehul? Anything that you would like to discuss? [Mehul Jariwala]: No, Rafael. Thanks for asking. [Rafael Bruno]: OK. [Sid]: How about you, Sid? Yeah, all good. OK. [Rafael Bruno]: So have a great day or a great night, guys. [Mehul Jariwala]: See you.