Meeting Title: Brainforge Weekly Operations Sync Date: 2026-03-10 Meeting participants: Kaela Gallagher, Elizah Joy, Rico Rejoso, Brylle Girang, Uttam Kumaran
WEBVTT
1 00:00:28.640 ⇒ 00:00:29.939 Kaela Gallagher: Hey, Eliza.
2 00:00:30.410 ⇒ 00:00:32.230 Elizah Joy: Hey, Kayla, how are you?
3 00:00:32.490 ⇒ 00:00:33.990 Kaela Gallagher: Good, how are you?
4 00:00:34.440 ⇒ 00:00:36.190 Elizah Joy: I’m also doing good.
5 00:00:36.580 ⇒ 00:00:37.190 Kaela Gallagher: Good.
6 00:00:39.790 ⇒ 00:00:41.129 Kaela Gallagher: Here we go.
7 00:00:44.240 ⇒ 00:00:45.060 Rico Rejoso: Hey guys!
8 00:00:45.480 ⇒ 00:00:46.130 Rico Rejoso: Morning.
9 00:00:46.850 ⇒ 00:00:47.970 Kaela Gallagher: Morning.
10 00:00:57.520 ⇒ 00:00:59.420 Kaela Gallagher: How was your guys’ weekends?
11 00:01:00.510 ⇒ 00:01:01.170 Rico Rejoso: Good.
12 00:01:01.500 ⇒ 00:01:04.639 Rico Rejoso: It was pretty busy, but yeah. How was yours?
13 00:01:05.170 ⇒ 00:01:07.439 Kaela Gallagher: Good! What were you up to?
14 00:01:08.690 ⇒ 00:01:14.470 Rico Rejoso: I mean, it’s… it’s my sibling’s graduation, so we have to…
15 00:01:14.580 ⇒ 00:01:19.149 Rico Rejoso: come up with presents, with gifts and stuff, so I have to go look for one.
16 00:01:19.870 ⇒ 00:01:25.360 Kaela Gallagher: Oh my gosh, okay, yeah, that’s super busy. Were they graduating from, like, university?
17 00:01:25.930 ⇒ 00:01:27.579 Rico Rejoso: No, just high school, but, you know.
18 00:01:27.580 ⇒ 00:01:28.670 Kaela Gallagher: That’s true.
19 00:01:30.370 ⇒ 00:01:31.660 Kaela Gallagher: That’s exciting.
20 00:01:32.760 ⇒ 00:01:34.090 Kaela Gallagher: In March.
21 00:01:34.380 ⇒ 00:01:36.419 Kaela Gallagher: The end of the school year’s in March.
22 00:01:36.780 ⇒ 00:01:37.450 Rico Rejoso: Yep.
23 00:01:37.850 ⇒ 00:01:40.779 Kaela Gallagher: Oh. When does the school year begin?
24 00:01:41.470 ⇒ 00:01:43.390 Rico Rejoso: June, after summer.
25 00:01:43.610 ⇒ 00:01:47.540 Rico Rejoso: Summer here is, like, typically around April, what, to May.
26 00:01:47.650 ⇒ 00:01:48.330 Rico Rejoso: Yeah.
27 00:01:48.810 ⇒ 00:01:50.340 Kaela Gallagher: Okay, okay.
28 00:01:50.530 ⇒ 00:01:51.350 Kaela Gallagher: Cool.
29 00:01:55.270 ⇒ 00:01:55.970 Kaela Gallagher: Hey, B.
30 00:01:57.810 ⇒ 00:02:00.589 Brylle Girang: What’s up? Oh, why are… why are you…
31 00:02:00.710 ⇒ 00:02:04.039 Brylle Girang: How do you call this? Why are you so prepped, Kayla?
32 00:02:05.020 ⇒ 00:02:06.200 Kaela Gallagher: So what?
33 00:02:06.520 ⇒ 00:02:10.100 Brylle Girang: So, prep, like… how do you call this? I…
34 00:02:10.460 ⇒ 00:02:10.780 Rico Rejoso: I didn’t.
35 00:02:10.780 ⇒ 00:02:13.410 Brylle Girang: Is there an event, or something?
36 00:02:13.410 ⇒ 00:02:21.109 Kaela Gallagher: No, I just did a workout, and then I had to shower, and so my hair is wet, and I just have it tied up.
37 00:02:21.110 ⇒ 00:02:22.820 Brylle Girang: Oh, okay, gotcha.
38 00:02:23.370 ⇒ 00:02:27.529 Kaela Gallagher: Oh, that’s funny. I’m glad I look put together.
39 00:02:28.900 ⇒ 00:02:30.529 Brylle Girang: Put together, that’s the word.
40 00:02:36.100 ⇒ 00:02:37.770 Kaela Gallagher: Hi, Liza. Hi, Rico.
41 00:02:38.410 ⇒ 00:02:38.760 Rico Rejoso: Hey, guys.
42 00:02:39.560 ⇒ 00:02:40.400 Rico Rejoso: Sorry, yeah.
43 00:02:41.100 ⇒ 00:02:47.710 Brylle Girang: Yeah, the weekend is… Significantly relaxed, more relaxed than the Monday.
44 00:02:47.880 ⇒ 00:02:51.660 Brylle Girang: So… That’s something.
45 00:02:52.200 ⇒ 00:02:53.459 Kaela Gallagher: That’s good.
46 00:03:22.480 ⇒ 00:03:24.419 Uttam Kumaran: Hi guys, sorry for the delay.
47 00:03:24.630 ⇒ 00:03:25.220 Kaela Gallagher: Morning!
48 00:03:25.220 ⇒ 00:03:31.070 Uttam Kumaran: Wi-Fi in my house is just, like, not working, so I have to leave.
49 00:03:31.230 ⇒ 00:03:33.920 Uttam Kumaran: I can’t do my job.
50 00:03:36.120 ⇒ 00:03:38.819 Uttam Kumaran: I can’t do a single thing except…
51 00:03:39.020 ⇒ 00:03:44.890 Uttam Kumaran: Walk around, call people on the phone, so… How’s the day going?
52 00:03:46.240 ⇒ 00:03:47.010 Kaela Gallagher: Good.
53 00:03:49.080 ⇒ 00:03:49.730 Rico Rejoso: explore.
54 00:03:51.670 ⇒ 00:03:53.020 Uttam Kumaran: Everybody else okay?
55 00:03:54.120 ⇒ 00:03:54.770 Brylle Girang: Yeah.
56 00:03:55.390 ⇒ 00:03:55.779 Rico Rejoso: Yeah, cool.
57 00:03:55.780 ⇒ 00:03:56.390 Uttam Kumaran: Cool.
58 00:03:57.830 ⇒ 00:04:11.190 Uttam Kumaran: Cool. I’m pumped for this meeting. One note I sent Kayla before this is, like, I think there’s some… some client stuff is starting to grow, so I feel… and I… I made some phone calls and really just asked a few people, like.
59 00:04:11.370 ⇒ 00:04:19.319 Uttam Kumaran: hey, who have you interviewed that you’re, like, a hell yes on, and I have some answers, so I think, you know, we should be able to make some decisions today.
60 00:04:19.540 ⇒ 00:04:20.850 Uttam Kumaran: I think…
61 00:04:21.149 ⇒ 00:04:28.600 Uttam Kumaran: you know, I think it’ll… it’ll allow us to kind of see at least… Kayla, you’ll at least see one person, you know, basically end-to-end, and I think that’ll…
62 00:04:29.350 ⇒ 00:04:31.330 Uttam Kumaran: Help us get a sense of the process.
63 00:04:33.610 ⇒ 00:04:45.109 Uttam Kumaran: And ideally, like, I think one big thing as part of our flow, and this is something, probably, B, we need to work on, is how do we give Kayla a line of sight into the delivery team’s needs?
64 00:04:45.460 ⇒ 00:04:47.510 Uttam Kumaran: From the… from the recruiting side.
65 00:04:47.660 ⇒ 00:05:03.419 Uttam Kumaran: So we can say, like, hey, we’re expecting to close X amount of business, we’re gonna need another engineer here, or someone else, so I’m kind of looking forward to that process, but yeah, let’s, sorry, I kind of derailed a little bit, so let’s go on with the deck, and
66 00:05:03.770 ⇒ 00:05:06.050 Uttam Kumaran: Yeah, go through normal stuff.
67 00:05:06.730 ⇒ 00:05:07.320 Kaela Gallagher: Cool.
68 00:05:08.440 ⇒ 00:05:23.780 Rico Rejoso: Yep, we can jump right in. Again, thank you so much for attending today’s operation meeting. Quick agenda would be renewals, recruitment updates, operation updates, that includes… or that includes our last week, activities and this week’s priorities, and lastly would be delivery updates.
69 00:05:23.940 ⇒ 00:05:30.669 Rico Rejoso: So, to jump in, renewals… Alright, Eliza, next slide, please.
70 00:05:32.850 ⇒ 00:05:48.729 Rico Rejoso: For, renewals, we have the following client contracts that had expired, which is the LMNT and Urban Stems. For LMNT, I know we had a workstream or SOW in place already, I guess we’re just finalizing that before we proceed to, contract signing. Yeah.
71 00:05:49.110 ⇒ 00:05:58.379 Rico Rejoso: for, team contracts, we have, we were just waiting a decision for, Jasmine’s, and, I mean, I also, kind of reviewed the…
72 00:05:58.650 ⇒ 00:06:01.509 Rico Rejoso: discussion you had with Jasmine, so probably we’re just waiting for.
73 00:06:01.510 ⇒ 00:06:02.370 Uttam Kumaran: On Friday?
74 00:06:02.630 ⇒ 00:06:03.510 Rico Rejoso: Yeah.
75 00:06:03.840 ⇒ 00:06:05.839 Rico Rejoso: I’m just waiting for her input, right?
76 00:06:05.840 ⇒ 00:06:12.730 Uttam Kumaran: Yeah, I’m just waiting for her. I mean, she kind of didn’t get back to me on… over the weekend, as she said, so I’m kind of, like, not in a…
77 00:06:13.290 ⇒ 00:06:15.040 Uttam Kumaran: Great mood about that, so…
78 00:06:16.410 ⇒ 00:06:23.469 Uttam Kumaran: We’ll see. I mean, at this point, I’m assuming she’s not going… she’s probably not gonna join short-term, so we’re gonna kind of move forward with…
79 00:06:24.140 ⇒ 00:06:27.219 Uttam Kumaran: Making sure that our analyst team, like, has enough support.
80 00:06:27.390 ⇒ 00:06:37.410 Uttam Kumaran: But yeah, I mean, we’re basically waiting. I think if her contract is expired, then I’m gonna… let’s wait to hear what she has to say before, like, signing an additional one.
81 00:06:37.520 ⇒ 00:06:43.710 Uttam Kumaran: Because she also expressed that she just may not even have time to support us short part-time, so let’s see.
82 00:06:44.590 ⇒ 00:06:55.000 Rico Rejoso: Okay, we could set up a follow-up within this week, to, you know, to… I mean, follow up with Jasmine in regards to her response or input, about the contract signing, right?
83 00:06:55.160 ⇒ 00:07:07.340 Rico Rejoso: And also, we have a… I mean, we’re working on the contract amendment for Joseph, again, in preparation with Hannah’s maternity leave. So, we’ll be having an open contract, maybe on call for now.
84 00:07:07.340 ⇒ 00:07:15.560 Rico Rejoso: And we’ll just be basing ours, for monthly, but I guess, I guess this will, I mean, the need for him will rise,
85 00:07:15.900 ⇒ 00:07:21.389 Rico Rejoso: as the time comes that, you know, Hannah has to be on leave, but we’ll further.
86 00:07:21.390 ⇒ 00:07:31.060 Uttam Kumaran: Yeah, so I think that’s, that’s something that, like, I think, Kayla, for your radar, is, like, Hannah’s gonna go on, on maternity leave, so I wanna make sure that
87 00:07:31.490 ⇒ 00:07:45.890 Uttam Kumaran: like, we need to probably think about who we need to backfill for the marketing team. I think it’s something that probably, like, me… me, you, and Luke should have a conversation on.
88 00:07:46.020 ⇒ 00:07:48.450 Uttam Kumaran: So that we can, like, list out the skill set.
89 00:07:48.680 ⇒ 00:07:52.710 Uttam Kumaran: That we’re looking for, and kind of see what we need to do.
90 00:07:52.930 ⇒ 00:07:54.740 Uttam Kumaran: So… When is the…
91 00:07:54.740 ⇒ 00:07:55.939 Kaela Gallagher: Trinity Week happening?
92 00:07:57.980 ⇒ 00:08:04.789 Uttam Kumaran: It’s a good question. Somewhere in… it’s somewhere in Notion or my notes, but I can start a thread with Hannah as well.
93 00:08:05.650 ⇒ 00:08:08.619 Kaela Gallagher: Okay, and how long is she planning on taking?
94 00:08:09.160 ⇒ 00:08:12.269 Uttam Kumaran: That’s also in the notes somewhere, I just don’t have it top of mind.
95 00:08:12.500 ⇒ 00:08:19.159 Kaela Gallagher: Okay, okay. And do we think Joseph is able to cover the
96 00:08:19.890 ⇒ 00:08:24.329 Kaela Gallagher: her fully for that leave? No. Because I know he’s working another job. Yeah, okay.
97 00:08:24.330 ⇒ 00:08:34.130 Uttam Kumaran: Yeah, no, no, no, yeah, so it’s… so I think Ann and, like, I think Joseph was initially brought on just as, like, part-time help with Dex, so I feel like we’re gonna need…
98 00:08:34.299 ⇒ 00:08:41.190 Uttam Kumaran: probably one more person. But like, yeah, let’s… I think we’re gonna… it’s probably gonna be someone who can hand… who…
99 00:08:41.870 ⇒ 00:08:56.440 Uttam Kumaran: I mean, I don’t know, I think this is where, like, me and Luke… me, you, and Luke have to decide, like, hey, do we want to just hire another, like, part-time designer, and then instead get someone to focus on, like, partnerships, or someone to focus on a different part of marketing? I kind of want to give Luke
100 00:08:56.580 ⇒ 00:08:59.320 Uttam Kumaran: Some of that ownership over deciding who he needs.
101 00:08:59.570 ⇒ 00:09:00.790 Kaela Gallagher: Okay. Because…
102 00:09:00.790 ⇒ 00:09:09.889 Uttam Kumaran: Because Hannah is sort of, like, a jack-of-all-trades, she does a lot of different things, so I want to make sure he has a clear idea of, like, of, like, what skill set he needs.
103 00:09:11.940 ⇒ 00:09:18.149 Uttam Kumaran: So, I think he’s… I mean, we could do that… we could do that sort of hash out this, like, later this week,
104 00:09:18.370 ⇒ 00:09:22.140 Uttam Kumaran: And I can go look back at any materials I have on, like, Hannah’s situation.
105 00:09:22.820 ⇒ 00:09:29.369 Kaela Gallagher: Okay, I might be getting coffee with Luke tomorrow, so if I do, I can definitely chat with him then. Yeah, okay.
106 00:09:29.900 ⇒ 00:09:34.569 Kaela Gallagher: If not, we can get time on calendar. That’s… that’s good to know. Cool.
107 00:09:34.570 ⇒ 00:09:35.120 Uttam Kumaran: Okay.
108 00:09:36.490 ⇒ 00:09:39.690 Rico Rejoso: Yep, and I’ll also add you, Kayla, to the group message that we have with Luke and Hannah.
109 00:09:39.930 ⇒ 00:09:41.630 Kaela Gallagher: Perfect. Thank you.
110 00:09:42.190 ⇒ 00:09:46.889 Rico Rejoso: Okay, so those are, for the renewals. Next one, we have the recruitment.
111 00:09:47.660 ⇒ 00:09:51.790 Kaela Gallagher: Okay, yeah, so just to go over some, recruitment updates.
112 00:09:52.200 ⇒ 00:10:01.850 Kaela Gallagher: We have a very solid pipeline right now, with 12 interviews going off this week, including 2 finals for data engineers.
113 00:10:02.170 ⇒ 00:10:17.239 Kaela Gallagher: I feel confident in filling our four current needs with this pipeline, but the one that I do want to call out as a concern would be our analytics engineer. We only have two analytics engineering candidates that have made it past the Loom video stage right now.
114 00:10:17.310 ⇒ 00:10:22.549 Kaela Gallagher: So that would… that’s the one that I would call out as a concern.
115 00:10:22.550 ⇒ 00:10:23.400 Uttam Kumaran: Okay.
116 00:10:25.110 ⇒ 00:10:28.649 Kaela Gallagher: Oh no. Utom, I’m losing you. You’re cutting out.
117 00:10:34.010 ⇒ 00:10:35.230 Kaela Gallagher: Oh, no.
118 00:10:35.970 ⇒ 00:10:38.649 Uttam Kumaran: Am I still cutting out?
119 00:10:40.970 ⇒ 00:10:44.689 Kaela Gallagher: Yeah. Is he cutting out for you guys, too?
120 00:10:44.690 ⇒ 00:10:45.530 Elizah Joy: Same here, yeah.
121 00:10:45.530 ⇒ 00:10:46.270 Kaela Gallagher: Okay.
122 00:10:47.840 ⇒ 00:10:51.749 Uttam Kumaran: Let’s see… Is any better?
123 00:10:51.750 ⇒ 00:10:53.219 Kaela Gallagher: Now you’re back. Kind of.
124 00:10:53.220 ⇒ 00:10:54.660 Uttam Kumaran: Alright, hold on, let’s see.
125 00:10:56.210 ⇒ 00:11:02.110 Uttam Kumaran: Okay, I can… I couldn’t hear you.
126 00:11:07.530 ⇒ 00:11:08.410 Kaela Gallagher: Okay.
127 00:11:08.890 ⇒ 00:11:11.020 Kaela Gallagher: I guess I’ll just…
128 00:11:11.640 ⇒ 00:11:23.390 Kaela Gallagher: I’ll just keep going through the updates, and yeah, feel free to try to stop me or, put something in the chat. But yeah, the analytics engineer, I’d call that out as a concern, and
129 00:11:24.300 ⇒ 00:11:33.640 Kaela Gallagher: I think right now, I would even consider, like, opening back up our job posting, just considering we only have two that have made it through… through Loom videos.
130 00:11:35.450 ⇒ 00:11:51.939 Kaela Gallagher: A couple updates here, we have the Brainforge Buddy, like, program built out, so that’s ready to go as soon as we onboard somebody, and we also have the onboarding plan developed, including our, like, 7-day, 30-day, and 90-day touchpoints.
131 00:11:52.300 ⇒ 00:12:08.229 Kaela Gallagher: And then I’m meeting with Work Leap today to go over, some tooling for that. And then we also developed our referral bonus. I actually already got, like, a referral sent through from Pranav, and so, exciting to see that the team is,
132 00:12:08.480 ⇒ 00:12:09.760 Kaela Gallagher: using that.
133 00:12:10.000 ⇒ 00:12:22.100 Kaela Gallagher: And then, right after this, we’re doing a recruitment team retro, so, we’ll be going through some feedback, and maybe, Utam, that’s where we can talk about, like, the candidates that people are really excited about,
134 00:12:22.630 ⇒ 00:12:25.470 Kaela Gallagher: And… we might want to fast track forward.
135 00:12:32.420 ⇒ 00:12:34.250 Kaela Gallagher: I think that’s it for me, guys.
136 00:12:41.260 ⇒ 00:12:45.379 Uttam Kumaran: I don’t know if you can hear me anymore, but I’m down to open up the AE position again.
137 00:12:46.430 ⇒ 00:12:47.240 Kaela Gallagher: Okay.
138 00:12:48.180 ⇒ 00:12:49.100 Kaela Gallagher: Okay, so…
139 00:12:49.100 ⇒ 00:12:59.949 Uttam Kumaran: I also have some… I have some referrals, and I also want to explore some of our staffing partners. This is a good moment to…
140 00:13:00.550 ⇒ 00:13:05.930 Uttam Kumaran: Connecting… Make…
141 00:13:07.150 ⇒ 00:13:07.820 Uttam Kumaran: Firm.
142 00:13:14.450 ⇒ 00:13:20.119 Kaela Gallagher: Tom, you’re cutting out again, but I did hear something about staffing partners.
143 00:13:22.700 ⇒ 00:13:28.540 Uttam Kumaran: Yeah, I just… if you… some staffing partners I do with, potentially as helpful for that role.
144 00:13:28.890 ⇒ 00:13:29.610 Kaela Gallagher: Okay.
145 00:13:33.270 ⇒ 00:13:48.669 Kaela Gallagher: I can also plan on doing some, like, targeted, LinkedIn messaging today for the analytics engineer role and see what kind of candidates I can produce. I’ve had success with that in the past. We have somebody going to, finals that I had, like.
146 00:13:48.960 ⇒ 00:13:54.809 Kaela Gallagher: targeted on LinkedIn, so, I can do that with the analytics engineer, too.
147 00:13:58.180 ⇒ 00:13:58.730 Uttam Kumaran: Okay.
148 00:14:01.070 ⇒ 00:14:03.439 Kaela Gallagher: Okay, cool, guys, I think that’s it for me.
149 00:14:04.610 ⇒ 00:14:07.119 Rico Rejoso: Alright, thank you, Kayla.
150 00:14:07.400 ⇒ 00:14:24.369 Rico Rejoso: Moving forward for our last week activities, we have the team-facing docs, which we reintroduced during our retro and sent out to Slack as well. Again, our goal is to reinforce the use of the forms and have all tasks in linear for proper allocation with the operations and for reporting as well.
151 00:14:24.550 ⇒ 00:14:32.219 Rico Rejoso: Blockify to operating, there’s a doc that, was created, and we’re still in discussion. The doc lay out the
152 00:14:32.320 ⇒ 00:14:44.149 Rico Rejoso: pros and cons of using either one. For now, we’ll stick with the current process, as there will be changes in the delivery team, as mentioned yesterday, by UTAM, and this one is kind of… is a low priority for us.
153 00:14:44.200 ⇒ 00:15:02.379 Rico Rejoso: And we also have a cursor command for ops team that we, that’s, currently, or that’s been tested, that we’ve been testing out and will be using moving forward. First one is the end of week and end of date command. This will be utilized by Eliza and, will be used moving forward for our end of week and end of day reports.
154 00:15:02.420 ⇒ 00:15:17.910 Rico Rejoso: We have the enReachOps tickets that we just… we also revised. This is to ensure that all operation tickets have clear context and goal for each task to avoid back-and-forth communication, with the stakeholder or the requester.
155 00:15:18.390 ⇒ 00:15:23.190 Rico Rejoso: Right. Another would be the escalation process. Next slide, please.
156 00:15:23.880 ⇒ 00:15:35.420 Rico Rejoso: We have the first occurrence, second occurrence, and third occurrence. So, simply, first occurrence is just an informal reminder. We’ll just be sending a Slack direct message.
157 00:15:35.480 ⇒ 00:15:53.539 Rico Rejoso: And we just need to restate the requirement, share the policy link, and offer clarification, if needed, for the policy that we have. The second occurrence, or, which is a written acknowledgement, it’s a written summary of the policy and what was not met, and what we’re expecting from our team members.
158 00:15:53.580 ⇒ 00:16:07.329 Rico Rejoso: There’s a part there where the contractor has to acknowledge, and also a commitment compliance. This is signed and will be documented as well. And the third occurrence is a compliance review, which is a live conversation
159 00:16:07.330 ⇒ 00:16:18.730 Rico Rejoso: for us to identify the challenges or barriers from our team members, and to agree on mitigation. This one will also be documented and signed off by the manager, after the
160 00:16:18.760 ⇒ 00:16:21.069 Rico Rejoso: After the meeting or discussion with the team member.
161 00:16:21.120 ⇒ 00:16:31.979 Rico Rejoso: Now, there are some policies that may be defined as critical for which may begin with a written acknowledgement, or the second occurrence, or the compliance review, the third one.
162 00:16:32.340 ⇒ 00:16:41.059 Rico Rejoso: Currently, there’s no policy that is deemed to be critical. If ever we should identify one, we may need to revise the team-facing document to indicate that as well.
163 00:16:41.240 ⇒ 00:16:52.699 Rico Rejoso: Also, we have a compliance tracker database in operations. It’s in the Notion page, Operation Notion page, that logs all the escalation from each team member. There’s a separate infraction per policy.
164 00:16:53.020 ⇒ 00:17:08.010 Rico Rejoso: Per policy. So, like, for example, a team member, has violated a out-of-office, which could result to the first occurrence and another first occurrence for the Clockify policy. So, it’s, the infraction is per policy, right?
165 00:17:08.050 ⇒ 00:17:20.299 Rico Rejoso: So, we’ve started rolling this out. I’ve also inquired with Kayla in regards to the policy that we have to make sure that everything is to… I mean, before we implement this with our team members, and…
166 00:17:20.300 ⇒ 00:17:32.049 Rico Rejoso: We’re also… we have also sent out reminder for the first occurrence to team members that had violated certain policy. Again, our goal for this one is to ensure that all policies are being followed for everyone’s convenience.
167 00:17:32.570 ⇒ 00:17:36.929 Brylle Girang: Rika, just a question. The Ops Notion page, is that private?
168 00:17:37.750 ⇒ 00:17:39.499 Rico Rejoso: Yep, for operations.
169 00:17:39.980 ⇒ 00:17:40.870 Brylle Girang: Alright, perfect.
170 00:17:43.010 ⇒ 00:17:45.379 Rico Rejoso: Yep, any questions so far?
171 00:17:45.720 ⇒ 00:17:46.600 Rico Rejoso: Bernardino.
172 00:17:48.770 ⇒ 00:17:52.070 Rico Rejoso: Alright, if then we can move on to the next slide.
173 00:17:53.940 ⇒ 00:18:09.330 Elizah Joy: Alright, so, we’ve also created, updated the finance process for… this is for the AP, accounts payable, so, it’s going to be a weekly process, so we have a safe-to-pay number and a clear list of those who, who we want to pay via RAM.
174 00:18:09.370 ⇒ 00:18:17.910 Elizah Joy: And then, the cadence for this is every Monday, OPS would run the review and fill… we would fill out the AP worksheet.
175 00:18:17.970 ⇒ 00:18:21.400 Elizah Joy: We have this today, do we wanna…
176 00:18:21.500 ⇒ 00:18:26.149 Elizah Joy: take this offline, Utom, and then we can share the list to you on Slack.
177 00:18:26.310 ⇒ 00:18:27.679 Uttam Kumaran: Yeah, perfect.
178 00:18:30.510 ⇒ 00:18:38.619 Elizah Joy: Okay, and then for the Sales Navigator transition plan, just a quick update on this. We’ve, shortened the timeline originally that we have.
179 00:18:38.650 ⇒ 00:18:57.280 Elizah Joy: So earlier, this morning, I’ve met with the LinkedIn Sales Navigator team. So our goal here is, instead of having Robert’s account, we’ll primarily use, your account with Tom, so that we can move, to the team plan in place. The only thing was when I had the conversation with
180 00:18:57.580 ⇒ 00:19:12.370 Elizah Joy: a Sales Navigator team is, what we can do is that we… at the moment, we don’t have the option for you to change or switch plans, and it is because we have currently the Sales Navigator, core plan in place, the personal plan.
181 00:19:12.370 ⇒ 00:19:29.480 Elizah Joy: So, they recommend canceling their current plan, and then we would… we can… what we can do is we can buy the advanced team plan, and then we can add in the seats there. One of the risks here is that when we cancel, the account that we have, or the current subscription that we have.
182 00:19:29.480 ⇒ 00:19:34.779 Elizah Joy: all the leads that you currently have on your Sales Navigator, so they would be deleted.
183 00:19:34.790 ⇒ 00:19:44.880 Elizah Joy: They mentioned that it can be restored via migration within 24 to 48 hours, but this is with the help of the Sales Navigator customer service help.
184 00:19:45.020 ⇒ 00:19:50.609 Elizah Joy: Another option that we do have is we can wait for your account to expire, but
185 00:19:50.780 ⇒ 00:20:08.729 Elizah Joy: the team plan, we’re going with the advanced plan for this, so for the team plan advance, we won’t be readily available until the end of the subscription, which is on March 28th, so we need to purchase, separate seats for the individual team members for the meantime on this.
186 00:20:08.800 ⇒ 00:20:20.100 Elizah Joy: So I think, yeah, our next steps for us is to decide which option to take, if we want to cancel the current plan, but the others would be… will be removing all the leads that we have.
187 00:20:22.940 ⇒ 00:20:23.490 Uttam Kumaran: Okay.
188 00:20:25.340 ⇒ 00:20:29.139 Elizah Joy: Do we want to move forward with canceling the team plan? Is that okay?
189 00:20:33.520 ⇒ 00:20:36.790 Uttam Kumaran: Yeah, any thoughts from anyone else? I feel…
190 00:20:40.120 ⇒ 00:20:41.609 Uttam Kumaran: I’m okay with it.
191 00:20:42.040 ⇒ 00:20:47.089 Uttam Kumaran: I guess, like, I’m not really using Sales Nav that much, to be honest, personally.
192 00:20:48.360 ⇒ 00:20:50.450 Uttam Kumaran: So, I feel like…
193 00:20:54.110 ⇒ 00:20:55.590 Uttam Kumaran: Yeah, what do you think, Richto?
194 00:20:56.740 ⇒ 00:21:11.369 Rico Rejoso: I mean, we… we can wait, because I think Kayla still has the, recruiter light, still in place until 27, right? So, if we don’t want to risk anything, we can just wait by the 28th to implement that, since we also have a transition plan.
195 00:21:11.370 ⇒ 00:21:23.379 Rico Rejoso: in place, to move forward with UTM’s account as the main account, and just provide individual plan to other team members, right? Instead of us just, going with option A, I think the option B would be…
196 00:21:23.640 ⇒ 00:21:30.910 Rico Rejoso: would be much prepared. We just have, like, a one-day content session, from the recruiter line to the team plan for SalesNet.
197 00:21:33.200 ⇒ 00:21:33.750 Uttam Kumaran: Okay.
198 00:21:37.210 ⇒ 00:21:56.770 Elizah Joy: All right, and then next is the device leasing. So we updated this for, for the documentation. We’ve upgraded that, so it’s been refined according to the, advice from finance. So it’s gonna be, from moving forward, we’re gonna finalize, all the W-2 employees, and as mentioned, by the finance teams at the moment.
199 00:21:56.950 ⇒ 00:22:09.630 Elizah Joy: We only have you, Tom, as the, full-time employee under W-2, but the impact on this is that currently we have, a couple of team members waiting for the device leasing.
200 00:22:09.650 ⇒ 00:22:22.219 Elizah Joy: Including Kayla, who is here today, right? So I think, the next steps for here is we can move forward with the device leasing, but only on your, for you for now, Tom.
201 00:22:25.180 ⇒ 00:22:33.069 Uttam Kumaran: Okay, I’m fine with that. So, like, is… are they still open to doing the device leasing for one person, and then we can expand over time?
202 00:22:33.740 ⇒ 00:22:37.260 Elizah Joy: Yep, yep. Okay. That’s still possible.
203 00:22:37.680 ⇒ 00:22:39.360 Uttam Kumaran: Okay, yeah, let’s go for it.
204 00:22:43.240 ⇒ 00:22:47.750 Rico Rejoso: Yep, quick one for this week’s priorities. We have the sales process and naming convention.
205 00:22:47.800 ⇒ 00:23:07.290 Rico Rejoso: We’re just finalizing the documentation. Robert is out, but we met with the team, Ryan and Luke, to inquire any challenges once we implement this one. Goal, again, is to ensure that there’s no… that there’s no current process that will be affected by this. This is just an additional step to get the operations involved, and to avoid our executives from sending a request via Slack.
206 00:23:07.340 ⇒ 00:23:24.900 Rico Rejoso: Right? The offboarding meeting automation, this is a low priority one, but we’ve started, or Eliza started working on this one. The goal here is to send out notifications to folks when team members offboarded, a quick nudge to save time and to ensure that the team focuses on, important tasks or client tasks, right? And also, OKR measurement.
207 00:23:24.900 ⇒ 00:23:34.719 Rico Rejoso: So we have this in place, and we’re trying to track and report it. For the ops ticket, we’re documenting tickets with no context by start of the week, and also quick checkpoint by midweek.
208 00:23:34.720 ⇒ 00:23:47.999 Rico Rejoso: And also, the linear triage, we’re gathering all total requests made on Slack versus linear. Goal is to identify the requests that can be done through Slack. So, Slack to linear, and propose those changes to the platform team.
209 00:23:48.290 ⇒ 00:23:57.130 Rico Rejoso: Right? So those are some of the priorities for this week, and again, we’re also open to getting more priorities from our stakeholders, if ever there are anything, right?
210 00:23:58.740 ⇒ 00:24:03.819 Rico Rejoso: Yep, and we can move on, if there’s no question, for the ops team to do the delivery.
211 00:24:06.410 ⇒ 00:24:20.529 Brylle Girang: Yeah, okay. For delivery ops, Otame and I are working closely on our truck priorities for this week, which is basically just automating the AP tasks that we have via our Courser workflows, and then pushing our CSOs
212 00:24:20.530 ⇒ 00:24:27.520 Brylle Girang: to use these skills. So we have major updates when it comes to our delivery structure.
213 00:24:28.000 ⇒ 00:24:40.369 Brylle Girang: And that includes, taking off the EP role, so our main goal right now, for this week and the coming weeks, is to make sure that we don’t leave the CSOs and our SLs in the future.
214 00:24:40.470 ⇒ 00:24:44.389 Brylle Girang: With basically no support when it comes to the project management tasks.
215 00:24:44.730 ⇒ 00:24:53.700 Brylle Girang: We’re automating everything that we can to ensure that the CSOs can focus on their client relationship.
216 00:24:54.050 ⇒ 00:25:05.189 Brylle Girang: The second priority is our movement from Instagram to Linear, and I’m currently just mapping out the workflows and then the links between the two projects.
217 00:25:05.280 ⇒ 00:25:15.500 Brylle Girang: And these are my top considerations, just making sure that once we transition, there’s little to no friction point for our CSOs and for our SLs.
218 00:25:16.040 ⇒ 00:25:21.959 Brylle Girang: And the third one, just an update that we have talked with the CSOs and SLOs into
219 00:25:22.190 ⇒ 00:25:25.790 Brylle Girang: Discussing the revamped delivery operating models.
220 00:25:26.030 ⇒ 00:25:41.930 Brylle Girang: Yesterday’s meeting was quite nice, because we had the chance to hear everyone’s feedback, and later, we’re going to be meeting with our EPs, just to make sure that they understand the why, and they understand the upcoming changes.
221 00:25:43.220 ⇒ 00:25:46.889 Brylle Girang: So, the priority for this week, basically, is just delivery.
222 00:25:47.510 ⇒ 00:25:55.709 Brylle Girang: tasks, and making sure that we support the delivery team. And I would need to push back on all other tasks outside of that, for now.
223 00:25:56.460 ⇒ 00:26:00.059 Uttam Kumaran: B is, how fast can we… can we get this linear stuff out, like, this week?
224 00:26:00.790 ⇒ 00:26:01.460 Brylle Girang: Yeah, stop.
225 00:26:01.460 ⇒ 00:26:07.830 Uttam Kumaran: don’t wanna… yeah, I just really don’t want to spend, like, 2-3 weeks. Like, I… the enterprise is expensive.
226 00:26:08.170 ⇒ 00:26:16.989 Uttam Kumaran: But, like, if you think it’s gonna be worth it, and it’s, like, net-net the same expense, then that’s fine. But I also just, like.
227 00:26:17.390 ⇒ 00:26:21.109 Uttam Kumaran: I don’t know, I still, I just want to make a decision on this as soon as we can.
228 00:26:21.980 ⇒ 00:26:28.390 Brylle Girang: permitting Otam that will have the decision out this week, and as much as possible, also do the migration before next week.
229 00:26:32.420 ⇒ 00:26:36.730 Rico Rejoso: A concern for the… you mentioned about eliminating the EP role, right?
230 00:26:37.080 ⇒ 00:26:51.199 Rico Rejoso: So, we have the, I mean, contract for those, for the delivery team, which also indicates the, the 5%, bonus and stuff. Are we going to cancel that as well? And are we going to introduce that to the EP leads,
231 00:26:51.560 ⇒ 00:26:55.690 Rico Rejoso: Or discuss it with our EP leads as well, since they may be looking forward to it.
232 00:26:56.610 ⇒ 00:26:57.690 Brylle Girang: Potam, dok.
233 00:26:57.900 ⇒ 00:27:00.419 Brylle Girang: Do you mind jumping on this question?
234 00:27:02.170 ⇒ 00:27:07.660 Uttam Kumaran: So we’re… yeah, we’re gonna be meeting with them, today.
235 00:27:08.060 ⇒ 00:27:16.350 Uttam Kumaran: And sort of translating what our decision is, and then basically coming to an agreement on, like, what’s the ghost path.
236 00:27:16.990 ⇒ 00:27:18.430 Uttam Kumaran: For those folks.
237 00:27:19.470 ⇒ 00:27:20.030 Rico Rejoso: Okay.
238 00:27:20.240 ⇒ 00:27:27.949 Rico Rejoso: In other words, actually, we have, like, a couple of team members that haven’t signed that one yet. I can cancel the document for signing, if ever.
239 00:27:29.490 ⇒ 00:27:35.170 Kaela Gallagher: Who are the team members that are going to be affected by the EP transition outside of AMBER?
240 00:27:40.530 ⇒ 00:27:41.050 Rico Rejoso: Sorry.
241 00:27:42.040 ⇒ 00:27:45.260 Brylle Girang: On top of my mind, that would be Mustafa, right?
242 00:27:50.600 ⇒ 00:27:58.779 Uttam Kumaran: Yeah, and it’s really just, like, we’re actually reducing responsibilities from them, but yeah, they’re sort of gonna lose this, like…
243 00:28:03.010 ⇒ 00:28:03.930 Uttam Kumaran: Weed.
244 00:28:06.360 ⇒ 00:28:16.410 Uttam Kumaran: I’ll be working with them to see, like, do they want to consider taking on the existing service lead or CSOs, or continuously see the engineer?
245 00:28:18.390 ⇒ 00:28:30.239 Uttam Kumaran: Okay, we missed most of that, but my understanding was that, like, Amber and Mustafa are the main ones affected, and they will transition to CSO or SL.
246 00:28:30.450 ⇒ 00:28:31.429 Rico Rejoso: The exit, yeah.
247 00:28:32.230 ⇒ 00:28:32.880 Uttam Kumaran: Yes.
248 00:28:32.880 ⇒ 00:28:34.000 Brylle Girang: Yeah.
249 00:28:34.500 ⇒ 00:28:35.120 Kaela Gallagher: Okay.
250 00:28:37.130 ⇒ 00:28:49.130 Uttam Kumaran: Anyway, we’re gonna have a conversation with them about where they wanna… where they wanna go. I have a feeling Amber is just gonna wanna stick around as the normal, like, analyst.
251 00:28:49.250 ⇒ 00:28:55.419 Uttam Kumaran: And… I think it’s gonna be up to Mustafa’s decision on what… Neither of them showed, like.
252 00:28:55.780 ⇒ 00:28:58.590 Uttam Kumaran: A ton of… of interest in, like.
253 00:28:59.130 ⇒ 00:29:03.899 Uttam Kumaran: service lead or CSO, so I’m gonna have a conversation with them and see what they want to do.
254 00:29:04.560 ⇒ 00:29:05.559 Kaela Gallagher: Okay, got it.
255 00:29:05.560 ⇒ 00:29:06.720 Rico Rejoso: Okay, got it.
256 00:29:11.940 ⇒ 00:29:17.840 Rico Rejoso: Yep, I guess that concludes our operation meeting for today. Anything else you want to discuss?
257 00:29:18.380 ⇒ 00:29:19.509 Brylle Girang: Thank you, Amanda.
258 00:29:23.820 ⇒ 00:29:25.779 Uttam Kumaran: I think that’s it. Yeah, I think,
259 00:29:26.000 ⇒ 00:29:30.770 Uttam Kumaran: I think, Eliza, if you’re able to send me anything for RAMP that you need me to do, I’m happy to take care of that with you.
260 00:29:31.740 ⇒ 00:29:34.319 Elizah Joy: Yep, I’ll send it through, Slack.
261 00:29:36.340 ⇒ 00:29:36.940 Rico Rejoso: Alright.
262 00:29:38.980 ⇒ 00:29:39.940 Kaela Gallagher: you guys.
263 00:29:39.940 ⇒ 00:29:41.069 Rico Rejoso: Thank you so much, guys.
264 00:29:41.290 ⇒ 00:29:42.710 Uttam Kumaran: Thank you. Appreciate it. Bye-bye.
265 00:29:42.710 ⇒ 00:29:43.739 Elizah Joy: Oh my god.