- Duration: 37 min
- Platform: zoom
- Attendees: Ben Ornstein, Mehul Jariwala, Michael Houck, Rafael Bruno, Rizwan Hameed, sid, ✨ Michael’s AI task manager via Hoop.app, siddharthsathe04@gmail.com, mehul@megaphone.network, sid@megaphone.network, rafaelbrunosiqueira@gmail.com
- Source: Read.ai 01JP0MSQY47N8EFGZT1JY3V3KM (https://app.read.ai/analytics/meetings/01JP0MSQY47N8EFGZT1JY3V3KM)
Transcript
[UNKNOWN_SPEAKER]: Hey, guys. Morning. [Michael Houck]: How are you guys? [Conference Room (sid) - Speaker 2]: Hello, guys. Going good. How are you? How was your weekend? [Michael Houck]: Yeah, pretty good. I went to the Dallas Mavericks game. It was nice. Okay, let’s jump right in. So, let me open up linear here. [UNKNOWN_SPEAKER]: All right, there we go. There we go. [Michael Houck]: Okay, so we are now making great progress for a few weeks now, so we’ll want to see a big week this week. I think I obviously sent over that big thread on that competitor I found, and I guess we can start. I want to get your guys’ thoughts on that, and then that’ll determine sort and how we prioritize things? [Rafael Bruno]: That most of that we could do like in one month if we focus only on that, because not talking about the front end, but talking about the back end and the integration with the scraper. What I read there, I think we could do like in one month. You, if we only focus on that. [Conference Room (sid) - Speaker 2]: So, Rafael, just curious, what does that include, like, just the scraper thing? Or maybe or maybe we can, I mean, I was, I was, I was creating a list of features for my own reference, like what are the list of features that they have based on on the message that you created. So based on that I was creating what all things can we do. So I was thinking maybe we can split it and give give individual timeline to each of it so that it feels more realistic because not all of those features will be integrated into a system at the same time probably the easy the quick ones can be done first and then based on how we break down, we can approach it. But this was just my way of thinking. [Rafael Bruno]: That the only part that might take a while to do, it’s the integration with other platforms, like the ones that you’ve mentioned, like HubSpot, Salesforce. Yeah. [Michael Houck]: Let’s remove the need for that for now. That can be, that’s not something that would block us from launching the rest of this. [UNKNOWN_SPEAKER]: That’s something that we could do as like a second release. [Michael Houck]: So how does that change things? [Rafael Bruno]: Want me to create like what Sid suggested like something, like a list of things that one needs to be done in the backend and in the frontend. [Michael Houck]: Yeah, that sounds good. Sid, I think we were messaging about something last night. Did you put something together? [Conference Room (sid) - Speaker 2]: Yeah, for the CRM, right? So basically I was thinking like there would be two or three major steps before I come, like, start talking about the proposal thing. I just wanted to confirm, like, the first step is that we will be adding leads, like, we’ll be generating the leads, right? The leads are basically the prospective users. [UNKNOWN_SPEAKER]: Is that correct? [Michael Houck]: Yeah, I think so. I think I understand what you’re saying. Basically, all we need to do is, at least for this part of the work, is to identify who’s engaging with the Megaphone user’s content, and then put them in a list, and then let the user download that list for Megaphone, and in the future, integrate with their CRM, whether it’s HubSpot or PipeDriver or whatever else, so that they can send the liens directly from uh, megaphone to, to there without needing to download and re-upload there. [UNKNOWN_SPEAKER]: Okay. [Conference Room (sid) - Speaker 2]: I think that makes a lot of sense now. So, uh, just to reiterate my understanding, the first step is as a, like, if I’m a caster, I got 10 posts, I got an engagement on my post. So here in this case, I will be able to download it on, uh, integrated with my CRM, like the post that the list of 10 users will be passed from megaphone to my CRM based on which one I’m connecting my account with, right? [Michael Houck]: Um, yes, except for the word users. These people are not users. They’re just people who interacted with this user’s LinkedIn content. So potential users for that person’s product, who that person can then reach out to via the copy that they have written in their CRM. [UNKNOWN_SPEAKER]: Right. [Conference Room (sid) - Speaker 1]: Potential users. Correct. [UNKNOWN_SPEAKER]: Okay. [Michael Houck]: So I think, uh, so this, uh, let’s, let’s just call them leads, which is what they are. [Conference Room (sid) - Speaker 2]: Yeah, it’s correct. Okay, so roughly from my for integrating the CRM, the backend thing, I think this is about 15 days, two weeks time, we can have it integrated into this CRM. I’m also taking into account that the fees, the functionality where we allow them to connect to one of these connected account with one of these or all of these three CRM. Systems. So that is one thing and then whatever post whatever link they give us the URL of the post, we will go get the list of the leads and then pass it over to their CRM. So this is the whole integration that I’m like whole whole functionality that I’m thinking about and keeping that in mind I think 1515 to 20 days is the maximum like on the 15th day, we can have it on the dev environment, test it among ourselves. And then there may be some like one or two changes here and there. So for that, another two or three days. [Conference Room (sid) - Speaker 1]: So basically 15 to 20 days is the time that I’m seeing. [Michael Houck]: And does that include like the other bullet points in the Slack message that I sent? So not just the part about getting the leads and sending them to the CRM, but also, um, you know, there’s work there around restructuring, um, how we use the group’s functionality, right? Because we want to put people into one big central group. And, um, um, obviously it’s not like related to the marketing work or the front end work, that stuff that would be separate, but, um, yeah, just, is that taking into account all the backend functionality that I wrote out or [Rafael Bruno]: just the, About that part, where do you want, if I understood correctly, it’s like if someone shares a broadcast, everyone on Megafon would have a chance to engage with that broadcast, right? [Michael Houck]: Not quite. I think that that would slow things down. What we’ll want to do is pick some number of megaphone users at random and send it to them via WhatsApp or Telegram or SMS. If we make it so that people need to log into the platform and they have this huge list of requests from every broadcast that was shared that day, and they have to go through them and pick which ones they want to engage with versus not, we’re very quickly going to get to a place where no one is actually doing that. So I think our UX of sending people the messages via the chat platforms instead of on our platform is right. And I also think that having some number, I don’t know what that number is, but some number of people randomly chosen who are not in the creator network to receive that message is the right call. So having it be limited. So we can figure out what that number is over time. Um, I’m also, I’m having one of our contacts, I mean, one of our ghost writers from the content agency do a demo with the competitor and they’re going to record the call. And so we’re going to learn things like, you know, how do they incentivize their users to engage with their other users posts and things like that. So I don’t have all the answers right now, but they’re going to do that interview later this week, hopefully. Hopefully, maybe the latest early next week. So basically, by the time next sprint comes around, and we’re planning out, you know, not this week, but the next two weeks, we’ll have more clarity there in the details of how this implementation should work. [Conference Room (sid) - Speaker 1]: Yeah, so talking about the timeline, and what I’ve taken into account. So see, so right now the CRM thing was more clear of what we need to do. So that so for that I can for sure say within 15 on the 15 day we can have it on there. And as you get more clarity about other thing about the board thing, right? I can I can utilize some of the time from this this 15 days and and use it to build the board functionality as well. But I think I will be able to give a better answer, like put a better date once we get like some offset requirements here. [Conference Room (sid) - Speaker 2]: Okay, I think that makes sense. [Michael Houck]: Since we don’t have all those exact requirements, we probably won’t until the end of this week. I think what we should do is probably not change course too much this week unless you guys feel otherwise. I’d rather that we get things like the settings page done as much as possible before we move on to this new work. I don’t know how much is left, but I would imagine we can at least make some meaningful progress there while we’re sort of waiting for this to, excuse me, to, um, to get clarity. Um, if there’s bandwidth to do things like, you know, start integrating with some list of CRMs. Okay. We can talk about that, but I sort of, I hesitate to kind of throw that in the mix when we have this other project that’s like halfway done, but speed is also kind of really important here. So it’s a tough choice. Rafael, on your side, where are we at on the various things? Cause that’ll help me kind of prioritize this. [Rafael Bruno]: Okay. So I’m almost done migrating everything from Upstash to AWS. I just need to wait for Rizwan to finish his part so we can test everything and make it’s working. We’re still monitoring what is going on with the describer. Rizwan is fixing some other parts of like retry logic so we can see some improvements about the campaign setup flow. This is the only flow that I need to finish to and also I have some test tasks but on the campaigns project this This is the only part that I need the backend to finish before we integrate everything with the frontend. And I also have some other bugs that I’m looking into. This would be like a summary of my things. [Michael Houck]: Okay, so on campaigns we’re not, we wouldn’t be able to finish this week, but the other stuff maybe we could finish up this week as well. Yeah. Okay. Okay, let’s do that. These other kind of lingering projects this week. And then when we get to sprint planning for next week, we can discuss prioritizing you and Sid both kind of tag teaming different parts of this change versus you finishing up campaigns first. [UNKNOWN_SPEAKER]: Okay. [Michael Houck]: Sid, on your side, can you tell me about the settings page where we’re at there? [UNKNOWN_SPEAKER]: Yeah, sure. [Conference Room (sid) - Speaker 1]: So on the setting side, it’s on the backend, like on the overall project side, we are doing pretty good. As of now, I can say we are mostly 20-25% done, including backend frontend both. And right now we are planning to launch this somewhere in next sprint. So internally, I and Mehul, we are planning to launch in the middle of next sprint, that will be way before end of this month. So somewhere in the last month, we are planning around 25th. That’s when we can say like we’ll hand it over for testing to Ben and other people like everyone can give thoughts on this thing. So yeah, that is the overall progress. That’s a target date we’re planning for internally. And the current progress is about 25th. Okay, got it. [Michael Houck]: All right, let’s, let’s make as much progress there as we can this week. It’s worth calling out that since we will be updating, Jesus, since we’ll be updating the way that people are interacting with groups functionality, we’ll probably update the settings page for that too. So I would say if you’re going to leave a part off for now, leave anything related to groups and inner circle off the settings page for now and prioritize the other parts since we might be changing up how that’s [Conference Room (sid) - Speaker 1]: used. Yeah, makes sense. So right now, we will be excluding groups as well as the teams feature. And everything apart from that, we are going ahead with that. We will be implementing. So just one request. So I was talking to Mehul. So as a developer, it would be really nice if we can get access to Figma, the dev access to Figma. Is that possible? Just checking with you if that can be doable. Because that will save the time of creating the design and the browser. [Michael Houck]: Yeah, Mehul and I have talked about this. It’s hard because we’re on an annual plan for Figma. And so like it’s, it’s, it’s for one project, it just doesn’t really make sense to do it. Um, I can see if we can put them on like a, a monthly plan, but I think since we’re on an annual plan for everyone else, it’s tough to, um, which by everyone else, I just mean me and Celine basically. So yeah, I don’t know. Um, I’ll look into it and see what I can do. [Conference Room (sid) - Speaker 1]: Fine. No issues. We’ll manage otherwise. If it’s doable, great. Otherwise, it’s fine. We’ll find some other way. [UNKNOWN_SPEAKER]: Okay. [Michael Houck]: How much would it speed things up? Just give me some context. [Conference Room (sid) - Speaker 1]: I think both of us can answer. From my perspective, I think it will speed up by half a day or something. Half a day at least. But I think Mehul, you can answer this better since you’re working on the front end. [Mehul Jariwala]: Yeah, I guess it will it will really help because it is automatically converting the rest and so that at least we just need to move the things here and there. So we can give it a try. I mean, we can try to implement any of the plugin and then see how that that will help. But yeah, I used a past project, but it is really hard. But since you mentioned we were having the access issue. So let me know if you can build to figure it out. [Michael Houck]: Okay, well, I just, I just upgraded you. So let me know if that works. [UNKNOWN_SPEAKER]: Okay. Okay. Thanks a lot. [Conference Room (sid) - Speaker 1]: Thanks a lot. Just as a suggestion, maybe like after, after we are done, maybe you can cancel the subscription if that helps on the subscription side. I think in about 10 to 15 days we should be done. Sorry to interrupt. Yeah. [Mehul Jariwala]: Just let me know when you guys are done. Yeah. Yeah, sure. [Conference Room (sid) - Speaker 1]: Thanks. Thanks a lot. [Michael Houck]: Yeah, of course, no problem. Okay. And then, Mehul, give me an update on where things are at on your side. I know you’re sort of in between everything right now, so just give me some context. [Mehul Jariwala]: Yeah, so about the content queue, I have finished everything related to the front-end side. There are a few comments which I received from Rafael, so that all the things got addressed. Now I’m currently working on the setting page, user setting page, which I’m going to I finished like, as Sid mentioned, I finished like 10-15% of the progress, like creating the UI of the mobile and desktop both together. And yeah, so that’s the program. My target would be like finish this first user setting page before going to anything else. [UNKNOWN_SPEAKER]: Okay. Yeah. It sounds good. [Michael Houck]: I think that’s the right priority. I’m looking through the sprint now and I think everything else that you’re assigned for the most part is, uh, even in next sprint is campaign related. So yeah, let’s finish up the settings page first. Um, is content queue ready to go? Cause I feel like we were trying to launch that like almost a month ago. So I want to make sure, are we, are we ready to launch that? [Mehul Jariwala]: Yeah, from my side of everything. Is good. Maybe the file if you can confirm from your side as well. [Rafael Bruno]: See, just need just just needs to finish fixing some some stuff. And then how you will will be able to review and give your inputs and if everything is okay, we can release it. [Conference Room (sid) - Speaker 1]: Yeah, I feel I already informed that the points that you asked me to do they are done that they’re on there. I think there are two other points from the whole third and fourth point. I’m not sure if you understand, but you can give inputs on those. [Mehul Jariwala]: Oh, yeah. Sorry to interrupt. Hong just wanted to confirm on that. So let’s say if user paid for the first screen, user paid for the plan and then when user reach on second screen and he mistakenly refresh the page. So do you want to like implement some confirmation model or or we allow them to refresh it. I mean, that will very rare scenario. We already blocked the close button and the close icon as well. [Michael Houck]: If they refresh, why doesn’t it just reload where they are? [UNKNOWN_SPEAKER]: Yeah, I can reload. [Mehul Jariwala]: But the thing is, we need the data from the back and that this is where the left. [Conference Room (sid) - Speaker 1]: So maybe you can do it like this. Let’s say they refresh, they make a payment and before submit the content request, they refresh, right. So when they come back, in the model itself, we should identify which step they are in before payment. I mean, before content request or after content request, right. So you can see the value in the local storage. And based on that, again, show the screen, you will be able to fetch the data of the person. So that’s, that’s what I say, right, you can see the value in the local storage before after after the payment is made and before they submit the content request okay I’ll check no problem but I don’t think so that will help but yeah I’ll check I think that that will do it right the that’s what we want here once they refresh and if they have made a payment but not submitted the content request the model should start from step two That’s it. If you want any back-end API, let me know. Happy to give it to you, but this can be purely front-end play. [UNKNOWN_SPEAKER]: But sure, let me know. Okay. Yeah. [Mehul Jariwala]: So I’ll check with Sid. Yeah. Let’s get content queue live this week. [Michael Houck]: I don’t, I don’t think we should have any reason to to wait longer, obviously I’ll review it when it’s fully ready, but yeah, I think we were targeting like mid-February, so we’re almost a month behind. So let’s get it live, and let’s get the settings page stuff done as much as possible. At least, Sid, as you’re thinking about that, let’s get it to a place where it is like launchable, right? Even if we don’t get all the functionality in there, let’s just get the settings page to a place where we can feel good launching it, and then if people have other features that they want to add later. And we have things we’ve left off that we know we want to add later. That’s fine. We’ll probably move on to this new work next sprint. So let’s get as much of it ready to go as possible this week. [Conference Room (sid) - Speaker 1]: Yeah, the settings page, right? Yes. I think most of it should be ready. Whatever we have planned, except the teams and the groups, it should be ready as of now. And that’s what we are planning for. I’ll still let you know, I’ll still keep you updated on the daily business. [Michael Houck]: Sounds good. And then last thing, Rizwan, tell me where you’re at on your stuff, because there is basically with this new work, with the message I posted in the channel last night, there’s some new things that you’ll need to do. Not urgently, not this week, but there’s new stuff we need to build. So I want to make sure we wrap everything else up this week, if possible. [Rizwan Hameed]: So give me some context there. So, as you may know, we have shifted from UPS to SPS. So, I’m shifting all the boards to communicate to the SPS accordingly. So, post-engagement changes are done already for the confirmations. Now, I’m like, you know, at least handling the planned scale events for the SPS. That ticket is in progress right now, so hopefully that will be done today. As well. I’ll try my best and then there’s another choose to implement the same as this changes on the other bots as well like the profile photo the update following these kind of bots as well and other than that there’s the one account replacement logic bot that is 50% done already for the later ones. I just need to make the changes for the later ones. So my plan is I can already talk to you in the messages My plan is to cover as possible by this week. So we play things up and that’s so far. [UNKNOWN_SPEAKER]: I think we lost him. Can you hear me now? [Michael Houck]: Now I can hear you. [UNKNOWN_SPEAKER]: Okay. So here I was. [Rizwan Hameed]: Oh, Can you guys hear me? [UNKNOWN_SPEAKER]: Yep. Yes. OK. [Rizwan Hameed]: So I was saying like, you know, the reprocessing the fail limits is in progress. And account replacement logic is 50% done already for the Twitter ones. And now I’ll be working on the LinkedIn one as well. Plus, I’ll be making the similar changes of the SQS for the remaining boards. Once these are done, I’ll be pulling up the remaining things that we haven’t been able to do. So my plan is to cover as much as possible by this week. So we have something, some space on my board for the next work as well, for the next week. [Michael Houck]: Okay, I think once this is done, I’m banning all infrastructure work unrelated to new feature development for at least a month. So let’s call it till the end of April. So if anything comes up that we need to do, fuck it, let’s do it and everything we do starting next sprint should be new feature work, nothing unrelated to that. Across the board, not just with the scraper, I mean in general. [UNKNOWN_SPEAKER]: All right, okay, big week. [Michael Houck]: We need to get this stuff done so that we can do this new work. I’ll keep you guys updated with what the design team gets back to me with. I’m hoping we can get at least some wire work our frames this week so that by next week we can begin work on some of the stuff on the front end, even if we’re waiting on them to do like the hi-fi color design and everything like that. Cause I think we already know what sort of the color palette and you know, elements like that are to a large degree. So I’ll keep you guys updated. Please keep me updated. Please keep linear updated. I wanna have a good week this week. [UNKNOWN_SPEAKER]: So let’s do that. [Conference Room (sid) - Speaker 1]: Okay. Sounds good. Just one thing, one update on the WhatsApp thing. So that one is a bit tricky. I don’t have a lot of access to the webhooks thing. So based on my research right now, I’m doing partial fixes on the WhatsApp thing and pushing it to production. And as soon as I’m done with the current content queue and other ongoing bug fixes, I’ll spend some more time on that and fix that issue. But right now the thing, the situation is that I don’t, I don’t have access. That’s one thing. That’s not the only reason blocking the issue. Second thing is that WhatsApp itself, they don’t have an API that gives us that tells us what is the reason that they’re that they were not able to send the message. So that is the second thing and based on this and some other points that I saw, I think most of the people in the industry they use Twilio to send WhatsApp messages. Twilio they are just using because it’s more reliable. It gives a lot of insight into what, even if a message fails, why it why did it fail? [Michael Houck]: So yeah, I think I think since there’s the access issue, can you just Rafael, can you just take this this bug on and get a fix because I think you set the WhatsApp system up. So let’s just optimize for speed. No, nothing. And familiarity with that part of the system because we can’t spend a lot of of time on bugs, but this one is stopping our users from getting posts, which is basically breaking the network. So yeah, I guess, Rafael, if you want to jump in there and get it fixed ASAP, please do so. I’ll do that. Okay, cool. [UNKNOWN_SPEAKER]: All right, guys. See you. See you. [Rafael Bruno]: Anything technical that you guys would like to Oh, OK. About content queue, how long do you guys estimate that this will be ready for Hulk to test? [Mehul Jariwala]: I guess this is on my side. Probably I’ll fix it tomorrow morning, which means your nighttime things will be ready. [Rafael Bruno]: OK. Got it. [UNKNOWN_SPEAKER]: Yeah. See you guys. [Rafael Bruno]: Take care. [UNKNOWN_SPEAKER]: Bye.