Meeting Title: Ops Sync Date: 2026-03-09 Meeting participants: Elizah Joy, Rico Rejoso
WEBVTT
1 00:00:49.320 ⇒ 00:00:50.660 Elizah Joy: Hi, Erica.
2 00:00:52.770 ⇒ 00:00:54.539 Rico Rejoso: Eliza. How are you?
3 00:00:54.950 ⇒ 00:00:57.330 Elizah Joy: Hi, I’m Claude. How about you?
4 00:00:57.800 ⇒ 00:01:00.579 Rico Rejoso: Great, great, I’m good. Happy Monday.
5 00:01:01.030 ⇒ 00:01:02.470 Elizah Joy: Yeah.
6 00:01:02.470 ⇒ 00:01:06.579 Rico Rejoso: So, it’s… what do you call this? It’s Daylight Savings,
7 00:01:06.580 ⇒ 00:01:07.470 Elizah Joy: Yeah.
8 00:01:09.830 ⇒ 00:01:15.449 Rico Rejoso: Alright, okay, well, the good thing is that we worked early, we finished early, right?
9 00:01:15.450 ⇒ 00:01:30.739 Elizah Joy: Hmm, yeah, I did… it was… I, like, I forgot… it slipped my mind that it’s daylight savings already. The good thing is I did, like, check my calendar early before, but yeah, that’s right.
10 00:01:32.000 ⇒ 00:01:35.860 Rico Rejoso: I actually figured out, like, 5 hours.
11 00:01:36.700 ⇒ 00:01:39.070 Rico Rejoso: Six hours from now.
12 00:01:39.800 ⇒ 00:01:40.760 Rico Rejoso: Alright.
13 00:01:42.170 ⇒ 00:01:48.490 Rico Rejoso: Okay, before we step into our current cycle of checking all the lists that we have.
14 00:01:50.700 ⇒ 00:01:53.609 Rico Rejoso: I mean, yeah, let’s just jump in, jump right in.
15 00:01:54.440 ⇒ 00:01:55.979 Rico Rejoso: Let me just share my screen.
16 00:01:57.500 ⇒ 00:01:58.310 Rico Rejoso: Okay.
17 00:01:58.460 ⇒ 00:02:01.680 Rico Rejoso: This one’s for 8, Tom, so it’s not turn this one.
18 00:02:02.070 ⇒ 00:02:02.730 Rico Rejoso: Sweet.
19 00:02:03.410 ⇒ 00:02:08.679 Rico Rejoso: Some of the tickets were from last week. Let us check out what happened to those tickets.
20 00:02:08.680 ⇒ 00:02:09.650 Elizah Joy: Alright.
21 00:02:09.990 ⇒ 00:02:13.799 Rico Rejoso: Okay, this one’s still blocked by Mustafa, right?
22 00:02:14.130 ⇒ 00:02:15.279 Elizah Joy: Yeah.
23 00:02:15.950 ⇒ 00:02:18.219 Rico Rejoso: What’s our next steps for this?
24 00:02:19.020 ⇒ 00:02:23.710 Rico Rejoso: Did you follow up, when did… when was the last conversation or follow-up you had with Mustafa?
25 00:02:23.710 ⇒ 00:02:27.800 Elizah Joy: It was last Friday, so I, pinged him again.
26 00:02:27.930 ⇒ 00:02:29.739 Elizah Joy: To get help on this.
27 00:02:30.110 ⇒ 00:02:34.050 Elizah Joy: So, yeah, the last follow-up was today.
28 00:02:36.030 ⇒ 00:02:38.480 Rico Rejoso: peeing again. Let’s try it pee again Tuesday.
29 00:02:38.640 ⇒ 00:02:39.140 Elizah Joy: -
30 00:02:39.140 ⇒ 00:02:39.980 Rico Rejoso: Tomorrow.
31 00:02:44.220 ⇒ 00:02:47.860 Rico Rejoso: Alright, let’s do that. Let’s leave this for now.
32 00:02:48.490 ⇒ 00:02:54.849 Rico Rejoso: Right, we know that they’re busy, so let’s just hang on for a second. How about for this? What are… what happened to this?
33 00:02:54.850 ⇒ 00:03:05.049 Elizah Joy: This has already, been set up in Zapier, so just the connection in Google, not Google, but QuickBooks to test it out if it’s working as…
34 00:03:05.790 ⇒ 00:03:07.440 Elizah Joy: And…
35 00:03:09.190 ⇒ 00:03:14.390 Rico Rejoso: Okay, QuickBooks. Okay, so this one is good in Zapier, so we just have to set it up in QuickBooks, right?
36 00:03:14.390 ⇒ 00:03:14.770 Elizah Joy: app.
37 00:03:14.770 ⇒ 00:03:19.750 Rico Rejoso: It’s just one… this one is for me. Okay, alright.
38 00:03:20.090 ⇒ 00:03:21.200 Rico Rejoso: That’s my fault.
39 00:03:23.040 ⇒ 00:03:24.739 Rico Rejoso: Okay, let me work on that.
40 00:03:25.400 ⇒ 00:03:32.170 Rico Rejoso: Let’s put it in the mute here… This one’s good.
41 00:03:33.230 ⇒ 00:03:37.400 Rico Rejoso: interview scorecard… I think this has been reviewed, so…
42 00:03:38.760 ⇒ 00:03:41.619 Rico Rejoso: Market is done here for participants…
43 00:03:43.080 ⇒ 00:03:46.020 Rico Rejoso: Okay, in progress. How are we on this?
44 00:03:46.230 ⇒ 00:03:50.620 Elizah Joy: This is the Google script, right? So I’ve been having… I think it’s…
45 00:03:51.030 ⇒ 00:03:56.499 Elizah Joy: complicated… not too complicated, but it’s a bit complicated for me, like the Google script.
46 00:03:56.940 ⇒ 00:04:00.230 Elizah Joy: like, set up for this?
47 00:04:01.150 ⇒ 00:04:02.250 Rico Rejoso: Hmm, okay.
48 00:04:04.390 ⇒ 00:04:09.559 Rico Rejoso: What are the blockers? What do you need? What else do you need to help you out, so we can help you out on this?
49 00:04:09.560 ⇒ 00:04:25.489 Elizah Joy: This one, I did, had the help of Cursor for this. I think it’s just, I did not… because I had this on the end of my list for last Friday, so I… for this one, I just ran out of time, but I can continue doing this one today.
50 00:04:25.490 ⇒ 00:04:30.290 Elizah Joy: Because I’ve already started with it, and I’ve got the help of cursor to help me.
51 00:04:30.290 ⇒ 00:04:31.170 Rico Rejoso: Dude.
52 00:04:32.160 ⇒ 00:04:33.650 Rico Rejoso: Alright, great, yeah.
53 00:04:33.750 ⇒ 00:04:40.619 Rico Rejoso: Okay, so, one thing, whenever you’re moving, tickets from one status to another.
54 00:04:41.160 ⇒ 00:04:51.350 Rico Rejoso: definitely there are changes that happened, right? That’s why you identified it from, like, moving it from to-do to in progress. There have been any progress on this one. Can you put all… can you also add a comment to it?
55 00:04:51.350 ⇒ 00:04:53.259 Elizah Joy: Okay. Right? Because…
56 00:04:53.260 ⇒ 00:04:59.380 Rico Rejoso: If you, also saw the operations end of week that I was testing out.
57 00:04:59.830 ⇒ 00:05:19.629 Rico Rejoso: I use a command and cursor to generate that. Now, that command includes reading the comment that was left behind to include in the update, so there will… there won’t be any update, or the update will be stuck on the last one that left the comment, so if you leave a comment and you’re the most recent individual.
58 00:05:19.750 ⇒ 00:05:20.260 Elizah Joy: the…
59 00:05:20.270 ⇒ 00:05:24.750 Rico Rejoso: walkthrough on this ticket, that will also be included in the update, and we will…
60 00:05:24.750 ⇒ 00:05:26.900 Elizah Joy: Alright? Okay.
61 00:05:28.590 ⇒ 00:05:33.569 Rico Rejoso: Okay, so I need you to leave your, later today, if you worked on this.
62 00:05:33.890 ⇒ 00:05:35.280 Rico Rejoso: This one’s…
63 00:05:35.610 ⇒ 00:05:47.229 Rico Rejoso: Okay, same goes. I think we had… we just haven’t… yeah. We have the end of week… end of week ready, so next step for this is, from slides, is to, update.
64 00:05:51.550 ⇒ 00:05:53.190 Rico Rejoso: Update, okay?
65 00:06:03.620 ⇒ 00:06:07.189 Rico Rejoso: Let’s update a slide for tomorrow, and let’s get it prepared.
66 00:06:11.820 ⇒ 00:06:18.760 Rico Rejoso: This one’s good. Last update that I have here is I just need to draft the proposal for the follow-up. Should be on Friday, but…
67 00:06:19.560 ⇒ 00:06:24.190 Rico Rejoso: We had a lot of meetings, last Friday, so I’ll continue this today.
68 00:06:26.460 ⇒ 00:06:40.059 Rico Rejoso: finance escalation for them, maybe this is a tie with the NPE that Kyla, is reviewing. We had a back-and-forth conversation and also a comments through the, Notion page that we’re working on.
69 00:06:40.090 ⇒ 00:06:49.779 Rico Rejoso: And due to other tasks that we’re working on, I guess this was, sidelined, but we will work on it again, so you can make action of this before the 10th, or before tomorrow, so we can
70 00:06:50.260 ⇒ 00:06:55.110 Rico Rejoso: Upload those hours by the…
71 00:06:55.740 ⇒ 00:06:58.150 Rico Rejoso: By the 15th, okay? Let me work on that.
72 00:06:58.610 ⇒ 00:07:00.820 Rico Rejoso: For Jasmine. Yep, go ahead.
73 00:07:00.820 ⇒ 00:07:07.239 Elizah Joy: Just a quick update on the… I think I haven’t got… Remember I messaged Demi on the pro… like, the…
74 00:07:07.400 ⇒ 00:07:22.580 Elizah Joy: I think it was Monday or Tuesday, the… about this, the finance escalation process, and then, we sent him the Slack message about, his hours not being, like, added to the current, month or cycle, and that we’re gonna be sending him.
75 00:07:22.730 ⇒ 00:07:29.900 Elizah Joy: like, a form, or, not a form, but a letter. He hasn’t responded on that.
76 00:07:30.200 ⇒ 00:07:32.149 Elizah Joy: So, yeah, just an update on that.
77 00:07:32.960 ⇒ 00:07:36.510 Rico Rejoso: No worries, yeah. The good thing is you did inform him about it, right?
78 00:07:36.510 ⇒ 00:07:37.180 Elizah Joy: Mmm.
79 00:07:37.260 ⇒ 00:07:44.920 Rico Rejoso: what we’re gonna do from, Kena and I, either of us should be pinging him to discuss this one, so we can have a written acknowledgement of…
80 00:07:44.920 ⇒ 00:07:45.600 Elizah Joy: Yeah.
81 00:07:45.600 ⇒ 00:07:53.489 Rico Rejoso: the incident that happened for the monthly hours, right? So thank you so much for that step. We’ll be moving… we’ll be stepping in to help you out on this, alright?
82 00:07:53.800 ⇒ 00:08:12.490 Elizah Joy: Yep, thank you. And then, oh, one last thing, Holly, she’s also added in her hours very, very late, so that was, I think, Thursday when she, or Thursday or Friday, but she, that she messaged that, her hours has been updated, so I’m…
83 00:08:12.990 ⇒ 00:08:22.889 Elizah Joy: Yeah, that was the… she hasn’t responded to me, like, the few days or few weeks prior to that, but it was really a really, really good response from Holly.
84 00:08:23.250 ⇒ 00:08:31.039 Rico Rejoso: Okay, let’s do this. I think we have this process. We’re in… I also have to walk you in through our escalation process, right?
85 00:08:31.040 ⇒ 00:08:31.820 Elizah Joy: Mmm.
86 00:08:31.820 ⇒ 00:08:40.450 Rico Rejoso: So, for that instance, if, like, if Holly doesn’t have any record yet, let’s see, operations. This is our dashboard.
87 00:08:43.140 ⇒ 00:08:43.890 Rico Rejoso: Later, too.
88 00:08:44.250 ⇒ 00:08:48.390 Rico Rejoso: Okay, so this is our escalation database right now… Wait, what happened?
89 00:08:48.830 ⇒ 00:08:49.210 Elizah Joy: Okay.
90 00:08:49.210 ⇒ 00:09:03.730 Rico Rejoso: We have… we just have, Cassie, and supposedly, which is for first occurrence, a DM reminder was sent for the out-of-office, and I’ll be creating one for Demi. I just haven’t created one yet, because the action was not yet taken, but let’s record it for Demi.
91 00:09:04.810 ⇒ 00:09:06.470 Rico Rejoso: Same goes.
92 00:09:06.800 ⇒ 00:09:07.800 Elizah Joy: Click on this.
93 00:09:07.910 ⇒ 00:09:17.339 Rico Rejoso: if… for Holly, for example, if you look at the database and there’s no, Holly’s not yet here, you can just go ahead and proceed with the first appearance, right?
94 00:09:17.340 ⇒ 00:09:19.880 Elizah Joy: And if we look at our.
95 00:09:20.850 ⇒ 00:09:23.830 Rico Rejoso: escalation framework.
96 00:09:23.990 ⇒ 00:09:30.680 Rico Rejoso: For the first esc, first appearance, or first time that they, they did not.
97 00:09:30.790 ⇒ 00:09:44.169 Rico Rejoso: I’ll follow the policy, here’s what we’re gonna do. We’re gonna send them a direct message, or conversation, restate the requirement, and also the policy. So I also added here a message that you can also use.
98 00:09:44.170 ⇒ 00:09:46.120 Elizah Joy: Messaging.
99 00:09:46.870 ⇒ 00:10:01.980 Rico Rejoso: For the reminder, like, hey, just a quick heads up about a policy, and about her or him not following that policy, included the link for the policy, so he or she can also review the policy and make sure that on the next time that… on the next time, this won’t be happening, right?
100 00:10:02.670 ⇒ 00:10:06.139 Rico Rejoso: So you can use this one whenever, like, someone,
101 00:10:06.540 ⇒ 00:10:19.580 Rico Rejoso: regardless of what policy has been violated, send them a message about it in the policy, right? Because first thing, you want to make sure that, you know, you guys are aware that there is a policy in place for that process, and you’re not following that process at all.
102 00:10:20.100 ⇒ 00:10:26.989 Rico Rejoso: So here’s the chat to you. Just read on this document, follow this one, and make sure that the policy that you’ve shared is the team-facing policy.
103 00:10:28.330 ⇒ 00:10:35.219 Rico Rejoso: So you can send this one to Holly, as well, and if he or she, like, further…
104 00:10:35.930 ⇒ 00:10:43.300 Rico Rejoso: Like, state that… He or she was not aware of this one, that’s why you’re sending this.
105 00:10:44.070 ⇒ 00:10:53.759 Rico Rejoso: Alright? And at the same time, we’ll be… later on our meeting, if you can take note, we will be adding a process with the finance team about the…
106 00:10:54.550 ⇒ 00:10:59.000 Rico Rejoso: what do you call this? About the, late hour submission.
107 00:10:59.190 ⇒ 00:11:00.330 Elizah Joy: Right.
108 00:11:00.330 ⇒ 00:11:17.579 Rico Rejoso: Okay, because, we’re the one who’s going to, it should be coming from us. We’re going to initiate that. Like, send them an email by the 10th or the 15th that, hey, here are the folks that have submitted their, hours late for, let’s, let’s say, for example.
109 00:11:17.690 ⇒ 00:11:21.300 Rico Rejoso: And we want you guys to add them to,
110 00:11:21.620 ⇒ 00:11:24.000 Rico Rejoso: For this mon- for the previous month.
111 00:11:24.170 ⇒ 00:11:29.789 Rico Rejoso: Right, so we need to consult with Holly later if what’s the best process, but again, that is the latter part of the agenda.
112 00:11:29.800 ⇒ 00:11:30.650 Elizah Joy: Right.
113 00:11:30.650 ⇒ 00:11:34.309 Rico Rejoso: I’m just telling you so you’ll be reminded of it. I might forget it, but yeah.
114 00:11:34.640 ⇒ 00:11:40.130 Rico Rejoso: You can take note of that and bring it in, bring it in later, later, meeting and conversation.
115 00:11:40.310 ⇒ 00:11:41.040 Elizah Joy: Okay.
116 00:11:41.040 ⇒ 00:11:43.510 Rico Rejoso: Okay, so yeah, just send the first occurrence.
117 00:11:43.630 ⇒ 00:11:49.870 Rico Rejoso: through, or do the first appearance action or, action step, then I’d send out the message to Holly.
118 00:11:51.020 ⇒ 00:11:52.000 Rico Rejoso: she’s aware.
119 00:11:53.360 ⇒ 00:11:57.089 Rico Rejoso: By the way, this is not the first one that… first time that Holly did it.
120 00:11:57.590 ⇒ 00:12:07.479 Rico Rejoso: for last month. We just didn’t have an escalation framework in place yet for last month, so we don’t have… we didn’t record it for, you know.
121 00:12:07.670 ⇒ 00:12:13.740 Rico Rejoso: Just to be fair with everyone, we’ll start recording it from the time the escalation process Listen, please.
122 00:12:15.440 ⇒ 00:12:17.960 Rico Rejoso: Okay, what else?
123 00:12:17.960 ⇒ 00:12:22.089 Elizah Joy: On my end, I wanted to add…
124 00:12:22.310 ⇒ 00:12:26.660 Elizah Joy: like, the… From last Friday, I’ve already sent
125 00:12:26.900 ⇒ 00:12:34.160 Elizah Joy: the, transition plan to UTOM, and then he’s good with the plan, but he mentioned that he wanted to make it
126 00:12:34.290 ⇒ 00:12:50.590 Elizah Joy: like, the timeline a bit shorter. So, I did, I was looking into it, and then what I did was I reached out to the Sales Navigator, sales support or customer support using UTAM’s account.
127 00:12:50.590 ⇒ 00:13:00.460 Elizah Joy: Then, I’ve just, received the email from there to schedule a call with them. So I did schedule a call, but, it is for…
128 00:13:00.990 ⇒ 00:13:02.790 Elizah Joy: Tomorrow…
129 00:13:04.020 ⇒ 00:13:17.340 Elizah Joy: Tomorrow at 3pm Philippine time, because those are the only available hours, like 12 noon Philippine time up until 6pm. So yeah, I did schedule a call with them, and then we’ll look into how we can…
130 00:13:17.410 ⇒ 00:13:18.730 Rico Rejoso: Wait, really?
131 00:13:18.930 ⇒ 00:13:22.510 Elizah Joy: Philippine time? Yeah, it’s Philippine time.
132 00:13:22.510 ⇒ 00:13:23.850 Rico Rejoso: House that they have…
133 00:13:24.690 ⇒ 00:13:30.920 Elizah Joy: Not sure what… yeah, I did… I thought that initially that was Eastern, or.
134 00:13:30.920 ⇒ 00:13:33.909 Rico Rejoso: I think that’s based off your calendar, or your.
135 00:13:34.250 ⇒ 00:13:36.340 Elizah Joy: Aww, yeah, I did.
136 00:13:36.850 ⇒ 00:13:39.459 Elizah Joy: Yeah, it did sync in my calendar.
137 00:13:39.720 ⇒ 00:13:40.550 Elizah Joy: Lake.
138 00:13:40.930 ⇒ 00:13:49.640 Elizah Joy: Yeah, 3 p.m. 3 a.m. Eastern. Not sure, but, I’ll CC you to the email, because I’ve just received this.
139 00:13:49.940 ⇒ 00:13:52.079 Elizah Joy: Earlier.
140 00:13:57.410 ⇒ 00:14:04.669 Rico Rejoso: Okay, yeah, I guess that’s too late for you to do, so let’s make sure that once you’re scheduling.
141 00:14:04.800 ⇒ 00:14:08.849 Rico Rejoso: Something like that. Make sure to do it, within working hours.
142 00:14:08.850 ⇒ 00:14:10.650 Elizah Joy: Eastern. Yeah.
143 00:14:10.650 ⇒ 00:14:11.940 Rico Rejoso: How long is the meeting?
144 00:14:11.940 ⇒ 00:14:13.749 Elizah Joy: Oh, it’s just for 15 minutes.
145 00:14:13.850 ⇒ 00:14:18.759 Elizah Joy: It’s a very quick meeting. It’s like,
146 00:14:19.120 ⇒ 00:14:23.030 Elizah Joy: Because I was requesting for the LinkedIn Sales Navigator for UTOM.
147 00:14:23.190 ⇒ 00:14:25.710 Elizah Joy: And then they mentioned that they have
148 00:14:25.840 ⇒ 00:14:42.339 Elizah Joy: After, like, basically after the call, it’s like, they’re gonna be enabling UTAM’s account for a Sales Navigator team plan, if that makes sense. So yeah, but, that… the process includes having that initial call with them to see if…
149 00:14:42.350 ⇒ 00:14:48.979 Elizah Joy: Having that Sales Navigator team plan is fit for us, but we already know that that’s the route that we want to do.
150 00:14:50.720 ⇒ 00:14:52.180 Rico Rejoso: Okay, I see.
151 00:14:52.790 ⇒ 00:14:53.810 Elizah Joy: Yep, so I think…
152 00:14:53.810 ⇒ 00:14:55.290 Rico Rejoso: Turn about the hours, yeah.
153 00:14:55.800 ⇒ 00:15:13.480 Elizah Joy: Yeah, I don’t mind the hours that much, because, yeah, I’m awake during those hours, but it’s just a quick 15-minute call, and then from there, I think we could just, instead of having Robert’s account as the primary, we can just do Udam, because we want to…
154 00:15:13.830 ⇒ 00:15:22.320 Elizah Joy: shorten the timeline that we transition everyone from the individual plan to the team plan for Sales Navigator.
155 00:15:26.160 ⇒ 00:15:32.299 Rico Rejoso: Okay, so you’re gonna meet with the LinkedIn Sales Team Navigate- sales, Sales Navigator team.
156 00:15:32.490 ⇒ 00:15:33.130 Elizah Joy: Which is…
157 00:15:33.130 ⇒ 00:15:35.240 Rico Rejoso: Tomorrow, maybe. Yeah.
158 00:15:35.430 ⇒ 00:15:41.049 Elizah Joy: Yeah, so… Yeah, so I think that’s 3 a.m. Eastern.
159 00:15:41.260 ⇒ 00:15:43.980 Rico Rejoso: Okay, and what are the next steps after we meet with them?
160 00:15:44.290 ⇒ 00:15:52.460 Elizah Joy: After this, they’re gonna enable us, because I did, look into it further, like, the… the scenario that we have with Utam’s account.
161 00:15:52.480 ⇒ 00:16:08.200 Elizah Joy: After the call, once they see that it’s a fit, but I’m sure that they’ll allow us to have a sales team, sales navigator team plan, they would add in that feature or option for Utam’s account to switch to the team plan, so…
162 00:16:08.210 ⇒ 00:16:20.749 Elizah Joy: After that, we can start, switching or changing plans for Utam’s account, then we can add in Robert’s, and then Luke’s, and even, Kayla’s, because we can already start.
163 00:16:20.980 ⇒ 00:16:26.180 Elizah Joy: Like, enabling her Sales Navigator account?
164 00:16:27.850 ⇒ 00:16:31.569 Elizah Joy: Even if he’s, still using the Recruiter Lite account.
165 00:16:34.490 ⇒ 00:16:35.200 Rico Rejoso: Okay.
166 00:16:39.980 ⇒ 00:16:41.040 Rico Rejoso: those,
167 00:16:41.410 ⇒ 00:16:44.929 Rico Rejoso: I’ll further refine this, let’s make it a,
168 00:16:45.760 ⇒ 00:16:49.770 Rico Rejoso: Medium price. For now, I’m gonna assign it to you, Eliza.
169 00:16:52.620 ⇒ 00:16:53.210 Rico Rejoso: I agree.
170 00:16:53.470 ⇒ 00:16:57.410 Rico Rejoso: The greatness. One… Alright.
171 00:16:57.750 ⇒ 00:16:58.630 Rico Rejoso: Gave me.
172 00:16:59.230 ⇒ 00:17:03.450 Rico Rejoso: Also notice here that the upgraded theme was done, right?
173 00:17:03.620 ⇒ 00:17:04.319 Elizah Joy: Hmm.
174 00:17:04.329 ⇒ 00:17:07.869 Rico Rejoso: Last week, what are the last updates that we had from that ticket?
175 00:17:08.250 ⇒ 00:17:13.119 Elizah Joy: The last updates that we have from that ticket were,
176 00:17:13.750 ⇒ 00:17:31.899 Elizah Joy: we wanted to move from the W-2 account, right? Or just having our W-2 employees, which at the moment, we don’t have those yet in place, but yeah, just, making sure that for the device leasing, it’s for the
177 00:17:32.030 ⇒ 00:17:47.250 Elizah Joy: W2 employees that we have, but at the moment, it’s only Utong. I did, we did send the Slack message to the finance team. We haven’t heard, we haven’t had any response from them yet to see, because, yeah, we did update the
178 00:17:47.320 ⇒ 00:18:04.500 Elizah Joy: plan or the documentation that we have for the upgraded device leasing. So the next step for that is, once finance team has confirmed, we can then, discuss that tomorrow for our ops meeting, for UTAM’s, review.
179 00:18:15.120 ⇒ 00:18:21.940 Rico Rejoso: Okay, so one of our goals here is to get is to get the… Feedback.
180 00:18:21.940 ⇒ 00:18:22.890 Elizah Joy: Mmm…
181 00:18:24.640 ⇒ 00:18:26.510 Rico Rejoso: get feedback from finance.
182 00:18:27.430 ⇒ 00:18:32.400 Rico Rejoso: Then, also… What do you call this?
183 00:18:36.360 ⇒ 00:18:40.319 Rico Rejoso: Request for a suggestion from them?
184 00:18:41.260 ⇒ 00:18:56.510 Rico Rejoso: for the EK, or the exact time that we can implement this, because I guess, if we have everything, the documentation and everything planned out already, and the list of people that we’re gonna purchase, the big question is when should we make that purchase, right?
185 00:18:59.280 ⇒ 00:19:00.090 Elizah Joy: Yeah.
186 00:19:06.500 ⇒ 00:19:08.170 Rico Rejoso: Okay, let’s have that for now.
187 00:19:08.870 ⇒ 00:19:20.519 Rico Rejoso: Okay, let’s try to pause this out. I think this has been pending for too long, but let’s not… yeah, let’s make sure that we follow up with them, in case they haven’t gone back yet for, like.
188 00:19:21.000 ⇒ 00:19:23.170 Rico Rejoso: After 2 days or so, right?
189 00:19:24.250 ⇒ 00:19:29.100 Rico Rejoso: So let me just set up this one-off issue for you. Alright.
190 00:19:32.980 ⇒ 00:19:33.810 Rico Rejoso: Alright.
191 00:19:34.010 ⇒ 00:19:35.170 Rico Rejoso: What else?
192 00:19:35.700 ⇒ 00:19:39.560 Rico Rejoso: Yeah, okay, being for both Joseph and for Jasmine.
193 00:19:41.450 ⇒ 00:19:45.470 Rico Rejoso: Notion for anyone, for team members… yeah, okay.
194 00:19:47.590 ⇒ 00:19:53.969 Rico Rejoso: I think let’s cancel this… It’s the same with this.
195 00:19:54.860 ⇒ 00:20:01.150 Rico Rejoso: Alright, and… This one, I’m gonna post also the recurring tickets that I have set up.
196 00:20:01.520 ⇒ 00:20:04.330 Rico Rejoso: Such as this… Alright.
197 00:20:04.700 ⇒ 00:20:12.419 Rico Rejoso: Now, by the way, sharing you this, sharing this to you, by the way, the OKRs that we have.
198 00:20:13.610 ⇒ 00:20:14.609 Rico Rejoso: Where was it?
199 00:20:16.800 ⇒ 00:20:17.580 Rico Rejoso: Mmm.
200 00:20:21.030 ⇒ 00:20:32.249 Rico Rejoso: Or… For operations team, which is the centralized ops request free, for 3 hours, have everything in linear.
201 00:20:32.320 ⇒ 00:20:50.109 Rico Rejoso: So I just want to show you how we’re, measuring this, right? So how are we… how do we know that we’re… we’re, reaching, or let’s say we’re achieving this OKR? Simply by using the… by using cursor, right? So, if you remember last Friday, we had a couple of folks
202 00:20:50.110 ⇒ 00:21:14.760 Rico Rejoso: that, I mean, we have a couple of folks now. We have a couple of forms that were created, and we also, provided an update on… during our retro, and at the same time, we also sent… you sent out a message on the Brainforge team about the forms that we have, making sure that everyone’s also aware about the processor forms, so that’s one thing. First thing is we have to inform the team that… or make them aware that we have this kind of process, and if they’re not looking at it, again.
203 00:21:14.760 ⇒ 00:21:23.319 Rico Rejoso: again, I think that falls under court already, as long as we have everything prepared for them, and we make the rightful actions for the announcement.
204 00:21:23.320 ⇒ 00:21:35.320 Rico Rejoso: Right? So, how are we measuring this one? I’m using cursor right now, and also reviewing the tickets that we had, or that were sent as triage, right? Making a quick,
205 00:21:35.820 ⇒ 00:21:40.990 Rico Rejoso: Because, making a quick list of,
206 00:21:41.200 ⇒ 00:21:49.269 Rico Rejoso: all the requests that is made throughout, or through the use of linear and linear ask, right?
207 00:21:49.400 ⇒ 00:22:05.609 Rico Rejoso: So, if there are anything that you think would be the best way for us, or, you know, a process that we can use linear and Slack automation, just let me know. We can discuss it with Inkam afterwards, and I’ll have you lead that project as well.
208 00:22:06.030 ⇒ 00:22:06.420 Elizah Joy: Hmm.
209 00:22:06.420 ⇒ 00:22:13.379 Rico Rejoso: Because we want to make sure that we, the goal for this is to eliminate everyone sending, sending us a direct message.
210 00:22:13.380 ⇒ 00:22:14.030 Elizah Joy: Yeah.
211 00:22:14.030 ⇒ 00:22:22.530 Rico Rejoso: Right? And requesting for sub. One thing, because you cannot see my messages and, requests from folks that are sending me a message.
212 00:22:22.530 ⇒ 00:22:41.720 Rico Rejoso: And I want to make sure that everyone in the operations have clear visibility of what everyone or what other team members are requesting, right? So if whenever I cannot, you know, step in and work on that, you can definitely take it over, and you have full context of what’s happening with my updates, and also the description of what was requested.
213 00:22:43.420 ⇒ 00:22:47.330 Rico Rejoso: So that’s one thing. We’re measuring that true cursor.
214 00:22:47.430 ⇒ 00:22:58.900 Rico Rejoso: Another… our next OKR would be automation process pulls in a context so ops team can execute with no additional context. Now, last week I created a,
215 00:22:59.370 ⇒ 00:23:00.969 Rico Rejoso: Command and cursor.
216 00:23:00.970 ⇒ 00:23:03.850 Elizah Joy: So if you go in cursor, and if you type in…
217 00:23:04.050 ⇒ 00:23:09.359 Rico Rejoso: the forward slash… and reach obstinate.
218 00:23:09.830 ⇒ 00:23:23.480 Rico Rejoso: or maybe once you click on the forward slash, you will see the commands that is there. We have the enReachOps ticket. Basically, what it does is, reviewing all the tickets that we have in linear.
219 00:23:23.720 ⇒ 00:23:30.100 Rico Rejoso: And it will, list out all the tickets that doesn’t have enough contacts.
220 00:23:30.280 ⇒ 00:23:30.800 Elizah Joy: Right.
221 00:23:31.060 ⇒ 00:23:46.400 Rico Rejoso: and provide a list of that, alright? So every week, we’re going to run this, I’m planning on putting an automation for this, so it will do it every Monday, and make sure that all of our tickets, when… whatever we created in Linear has full context, and with all the resources, and the
222 00:23:46.650 ⇒ 00:23:56.630 Rico Rejoso: files, reference to it, right? So, example, this one that we just created, it doesn’t have anything, just the goal for the ticket and the title, right?
223 00:23:56.630 ⇒ 00:24:00.669 Elizah Joy: So later on, we’ll run a inventory shops ticket in the afternoon.
224 00:24:00.750 ⇒ 00:24:13.940 Rico Rejoso: and have cursor come up with all the description and stuff here. So whenever you’re looking at this, this one is assigned to you, so whenever you pull it out, you have full context on what’s happening, or what should be done for this ticket, okay?
225 00:24:14.820 ⇒ 00:24:18.029 Rico Rejoso: So, I was thinking of running this twice every week.
226 00:24:18.210 ⇒ 00:24:30.320 Rico Rejoso: First on Monday, second would be on Wednesday, because again, we have, we’ll be creating a agenda, or a list of action items after our meeting with UTAM tomorrow, right?
227 00:24:30.740 ⇒ 00:24:33.300 Rico Rejoso: So definitely, you have to enrich those tickets as well.
228 00:24:33.810 ⇒ 00:24:36.000 Rico Rejoso: Okay, where were we?
229 00:24:36.300 ⇒ 00:24:44.350 Rico Rejoso: So that’s how we measure this one as well. Now, for the last one, I may need your help, alright? So I already walked you through our legal process.
230 00:24:44.350 ⇒ 00:24:44.840 Elizah Joy: Yeah.
231 00:24:44.840 ⇒ 00:24:46.830 Rico Rejoso: And our, I believe.
232 00:24:46.830 ⇒ 00:24:47.230 Elizah Joy: equipment.
233 00:24:47.230 ⇒ 00:24:50.329 Rico Rejoso: Did I walk you through our onboarding, client onboarding? Not yet.
234 00:24:50.330 ⇒ 00:24:56.469 Elizah Joy: Not yet, not yet for client onboarding, just the recruitment and then the legal.
235 00:24:56.720 ⇒ 00:25:05.109 Rico Rejoso: Okay, so if you can put that on our list to walk through our client onboarding, because I may have as well. I mean, we have a couple of,
236 00:25:05.600 ⇒ 00:25:15.519 Rico Rejoso: proposal in place already, so if ever we are going to onboard them, I’m going to assign this to you, right? So you also have the feel of how we onboard clients, right?
237 00:25:15.520 ⇒ 00:25:16.040 Elizah Joy: nope.
238 00:25:16.220 ⇒ 00:25:22.699 Rico Rejoso: So, one thing is that we want to make sure, or we have to remove Robert and Infam
239 00:25:22.960 ⇒ 00:25:40.759 Rico Rejoso: out of the way when we’re executing SOPs, NDAs, onboarding, and other, signing docs, right? Unless, again, they’re necessary for us to… for them to be involved in, such as they need to be the signer for this before we reach out to clients and stuff, but other than that.
240 00:25:40.760 ⇒ 00:25:44.520 Rico Rejoso: Any process that they’re currently
241 00:25:44.840 ⇒ 00:25:47.889 Rico Rejoso: Included, we have to move them out.
242 00:25:47.890 ⇒ 00:25:50.430 Elizah Joy: Right, and take over as much, right?
243 00:25:50.430 ⇒ 00:25:54.500 Rico Rejoso: Because we want to make sure that, all of this are not,
244 00:25:54.770 ⇒ 00:25:56.899 Rico Rejoso: All of this are not being blocked.
245 00:25:57.040 ⇒ 00:26:02.529 Rico Rejoso: By them, and we can send them out freely, from the operations side.
246 00:26:02.560 ⇒ 00:26:03.549 Elizah Joy: Yeah. Right.
247 00:26:03.550 ⇒ 00:26:15.010 Rico Rejoso: So, first, right now, we can… there’s no way for us to measure this, automatically. Right now, I’m just going through all our requests coming from email, from Slack.
248 00:26:15.100 ⇒ 00:26:26.080 Rico Rejoso: And reading through if we can… or listing out all the requests coming from them for NDAs and client onboarding, then listing it out on a table, which is…
249 00:26:27.150 ⇒ 00:26:28.179 Rico Rejoso: not efficient.
250 00:26:28.200 ⇒ 00:26:39.599 Rico Rejoso: Right, so as… along with me ramping up… ramping you up with this process, I also wanted to see if you have any suggestions on how we can further take them
251 00:26:39.600 ⇒ 00:26:48.220 Rico Rejoso: Of the process, and we can just, you know, have a smooth flow with them blocking certain parts of the process, right?
252 00:26:48.220 ⇒ 00:26:49.150 Elizah Joy: Sorry.
253 00:26:49.150 ⇒ 00:26:59.389 Rico Rejoso: Right now, I have a suggestion, which is included in the ticket that I was working on, which is the sales process one, because in the sales process, that involves discovery call.
254 00:26:59.530 ⇒ 00:27:07.480 Rico Rejoso: to demo, to creating contract and creating SOW, up to signing contract and onboarding. So that’s the sales process, right?
255 00:27:07.480 ⇒ 00:27:07.880 Elizah Joy: Hmm.
256 00:27:07.880 ⇒ 00:27:17.649 Rico Rejoso: So, I’m also inserting part of it where we can set up an automation in HubSpot, so whenever a folk or a lead or a deal is, moved.
257 00:27:17.790 ⇒ 00:27:37.290 Rico Rejoso: from this process to… from this status to a different status, and that status requires us to send them an NDA, we will be receiving a Slack notification in our channel, and we can just send it out without, the founders requesting the operations team to send out an NDA, right?
258 00:27:37.290 ⇒ 00:27:37.810 Elizah Joy: I think that…
259 00:27:37.810 ⇒ 00:27:38.580 Rico Rejoso: what’s the…
260 00:27:39.090 ⇒ 00:27:45.280 Rico Rejoso: For me, was the best way to get notified about this, and we can send this out without them requesting it, right?
261 00:27:45.280 ⇒ 00:27:45.960 Elizah Joy: Yeah.
262 00:27:45.960 ⇒ 00:28:04.869 Rico Rejoso: And for… same goes with client onboarding. Once they change the status to done in HubSpot, will be… or close to 1, or completed, we can… we will be receiving a Slack notification about it, and we can just proceed to onboarding, and just, you know, review all the documents on the email as we see fit.
263 00:28:05.800 ⇒ 00:28:20.640 Rico Rejoso: I was also thinking if we could have a Google MCP in cursor, or Slack MCP, which could help us further check out or make sure that we have all the reference, conversation, documentation in linear as well, so we don’t… we don’t have to, like, you know…
264 00:28:20.750 ⇒ 00:28:34.839 Rico Rejoso: request anything from our founders, right? So those are the few processes that I’m working on. I’m going to add you to the, sales process that I’m working on, and make sure that you also get a view of it. So if you have any suggestions, just let me know, okay?
265 00:28:34.840 ⇒ 00:28:36.579 Elizah Joy: Yep. Yep, I will.
266 00:28:39.660 ⇒ 00:28:40.580 Rico Rejoso: Alright.
267 00:28:41.000 ⇒ 00:28:50.520 Rico Rejoso: So, I guess that’s, all our OKRs for the… for quarter one. I mentioned it, and I discussed to you, Tom and Robert, that both of these are…
268 00:28:50.690 ⇒ 00:28:51.630 Rico Rejoso: on track.
269 00:28:52.290 ⇒ 00:28:55.310 Rico Rejoso: Since we have a way to,
270 00:28:55.990 ⇒ 00:29:14.100 Rico Rejoso: to track, or let’s say, what do you call this? Measure this OKR. For this one, it’s still off track. Since, I mean, we can measure it, but it’s pretty manual, and we’re trying to eliminate that manual process as much as we can, so this is still off track, but we have a process in place to, you know,
271 00:29:14.600 ⇒ 00:29:18.350 Rico Rejoso: To get them out of the way when it comes to this kind of process, right?
272 00:29:18.790 ⇒ 00:29:22.389 Rico Rejoso: So we just don’t have a way to track this automatically, so we’re just…
273 00:29:22.650 ⇒ 00:29:24.609 Rico Rejoso: I’m looking into that for now.
274 00:29:24.710 ⇒ 00:29:28.799 Elizah Joy: Let me know if you have any suggestions on how we can track this, or a better way.
275 00:29:28.800 ⇒ 00:29:34.740 Rico Rejoso: a better process or way for us to execute this and make sure that we’re, reaching out these OKRs, okay?
276 00:29:34.920 ⇒ 00:29:36.060 Elizah Joy: Okay.
277 00:29:36.060 ⇒ 00:29:41.079 Rico Rejoso: Okay, so right now, all the tickets that you have are listed, and later?
278 00:29:41.290 ⇒ 00:29:41.730 Elizah Joy: speaker.
279 00:29:41.730 ⇒ 00:29:42.300 Rico Rejoso: that.
280 00:29:43.180 ⇒ 00:29:48.389 Rico Rejoso: If ever there are new ad hoc stuff come in.
281 00:29:48.420 ⇒ 00:29:49.859 Elizah Joy: Just let me know.
282 00:29:49.860 ⇒ 00:29:57.709 Rico Rejoso: If you… or you could just create a ticket for it, and let me know if you have any… if you need help on… while working on that stuff. At the same time.
283 00:29:58.030 ⇒ 00:30:00.979 Rico Rejoso: I’ll have you work on some of the 3-H tickets, alright?
284 00:30:00.980 ⇒ 00:30:01.540 Elizah Joy: Yep.
285 00:30:01.890 ⇒ 00:30:03.540 Rico Rejoso: So, once you see it, friage.
286 00:30:04.390 ⇒ 00:30:09.589 Rico Rejoso: Just assign it to you, accept it, or move it to in progress if you’re working on it already.
287 00:30:09.850 ⇒ 00:30:10.280 Elizah Joy: And you can…
288 00:30:10.280 ⇒ 00:30:16.390 Rico Rejoso: start working on it, and mark it as done as you see fit, okay? Yeah. But if you need any assistance, just let me know, I’m available on Slack, right?
289 00:30:16.390 ⇒ 00:30:17.540 Elizah Joy: Alright.
290 00:30:17.930 ⇒ 00:30:18.840 Rico Rejoso: Anything else?
291 00:30:19.080 ⇒ 00:30:25.370 Elizah Joy: Nothing else, but if, yeah, I do, I found there’s some questions, I’ll message you on Slack.
292 00:30:25.660 ⇒ 00:30:29.939 Rico Rejoso: Okay, yep, no worries. Also, make sure that, you provide, again, comments and.
293 00:30:29.940 ⇒ 00:30:30.719 Elizah Joy: Oops. Yeah.
294 00:30:30.720 ⇒ 00:30:35.479 Rico Rejoso: And just, you know, update of what happened to the thing as you were on them, okay?
295 00:30:35.480 ⇒ 00:30:38.059 Elizah Joy: Yep, yep, I will do that after.
296 00:30:38.660 ⇒ 00:30:43.589 Rico Rejoso: Alrighty. By the way, I’m also working on the end of the, command.
297 00:30:44.720 ⇒ 00:30:49.979 Rico Rejoso: That I’ve created. I’m just gonna do an end of day, so you don’t have to, you know, wait for me.
298 00:30:49.980 ⇒ 00:30:50.530 Elizah Joy: Yeah.
299 00:30:50.530 ⇒ 00:30:54.219 Rico Rejoso: Send an update, as long as I update it or put in a comment.
300 00:30:54.450 ⇒ 00:30:57.209 Rico Rejoso: on the tickets that I’m working on.
301 00:30:57.320 ⇒ 00:31:02.939 Rico Rejoso: You can just… use Cursor to, generate that update every day.
302 00:31:03.120 ⇒ 00:31:06.830 Rico Rejoso: Okay. That will make your life easier. Oh, yeah.
303 00:31:06.830 ⇒ 00:31:16.670 Elizah Joy: But we’re still gonna send that, like, 6 or 7 p.m. Eastern, right? Thus, like, the same time that we used to send it out before.
304 00:31:16.940 ⇒ 00:31:28.360 Rico Rejoso: Same time with break. We just have to make sure that, you know, you know, I’m not blocking you, since I think you’re waiting for me to send my updates, and you’re not gonna send anything unless I send out that… I send that out, right?
305 00:31:28.550 ⇒ 00:31:33.719 Elizah Joy: Mmm, yeah, so I want to make, like, let’s… I want to consolidate our reports.
306 00:31:33.720 ⇒ 00:31:37.740 Rico Rejoso: Okay, yeah, the crucial step for that is for us, for both of us.
307 00:31:38.310 ⇒ 00:31:41.209 Rico Rejoso: Put in comments on the tickets that we’re working on, because…
308 00:31:41.680 ⇒ 00:31:55.399 Rico Rejoso: Cursor is not gonna put anything, or it’s gonna rely on the most recent update or comment that we put in. And if that comment is outdated, like, 3 days or 4… it came from last week, that would… that would be pretty much outdated.
309 00:31:55.610 ⇒ 00:31:56.270 Elizah Joy: Yeah.
310 00:31:56.630 ⇒ 00:32:01.550 Elizah Joy: Quick question on that, and also, it’s also gonna read, like, the…
311 00:32:01.960 ⇒ 00:32:09.890 Elizah Joy: tasks that we have under the status, like, once they’re done in the status, right? Comment and status.
312 00:32:10.790 ⇒ 00:32:15.790 Rico Rejoso: Yeah, so let me, yeah, we can provide any suggestions on how, at the end of the week.
313 00:32:15.930 ⇒ 00:32:26.329 Rico Rejoso: would work. If you… end of day, sorry. If you saw the end of the, update that I had, and you prefer a different setup, just let me know so we can edit the command.
314 00:32:26.520 ⇒ 00:32:34.149 Rico Rejoso: And we can have it the way you prefer it, or prefer the way that we both would prefer it to be, okay?
315 00:32:34.150 ⇒ 00:32:34.740 Elizah Joy: Okay.
316 00:32:35.060 ⇒ 00:32:40.699 Rico Rejoso: Just let me know, okay? I’m working on it right now, so if you can let me know after this meeting, that would be great.
317 00:32:40.970 ⇒ 00:32:42.180 Elizah Joy: Okay, everyone.
318 00:32:43.200 ⇒ 00:32:43.790 Rico Rejoso: Alright.
319 00:32:45.180 ⇒ 00:33:00.739 Rico Rejoso: Okay, other than that, I think we’re good. If you don’t have any questions, I think that’s it for now. We have a meeting later today with finance to discuss about the steps that they want us to get involved in. Just wanted to let you know about it and remind you about it, alright?
320 00:33:00.740 ⇒ 00:33:04.339 Elizah Joy: Yep, okay, yep.
321 00:33:05.500 ⇒ 00:33:15.659 Rico Rejoso: Alright, thank you so much, Eliza. If nothing else, have a great Monday. I’ll be assigning tickets to you later on, once I work on some stuff, and feel free to take a look at it by midday, okay?
322 00:33:15.660 ⇒ 00:33:18.070 Elizah Joy: Alright, thank you so much, Rico.
323 00:33:18.070 ⇒ 00:33:20.139 Rico Rejoso: Alright, thank you, Eliza. Have a great one.
324 00:33:20.140 ⇒ 00:33:21.670 Elizah Joy: Thank you, bye.