Meeting Title: Ops Sync Date: 2026-03-05 Meeting participants: Elizah Joy, Rico Rejoso
WEBVTT
1 00:02:58.210 ⇒ 00:03:00.220 Elizah Joy: Hi, Rico, can you hear me?
2 00:03:01.000 ⇒ 00:03:04.390 Rico Rejoso: Hey, Eliza, sorry I was late. I was staying with you, sir.
3 00:03:07.240 ⇒ 00:03:09.589 Rico Rejoso: Okay, we can start off.
4 00:03:11.390 ⇒ 00:03:14.810 Elizah Joy: Yep, so… Share.
5 00:03:15.550 ⇒ 00:03:17.149 Rico Rejoso: I don’t know, let me share my screen.
6 00:03:17.150 ⇒ 00:03:17.840 Elizah Joy: Yep.
7 00:03:18.570 ⇒ 00:03:22.760 Rico Rejoso: Let’s, let us go through the tickets we have for this sprint, or for the cycle.
8 00:03:23.820 ⇒ 00:03:30.969 Rico Rejoso: adding your tickets with the tasks that you’ve been doing so far in the sprint, and I see you also closed out some of the tasks here. Great job.
9 00:03:30.970 ⇒ 00:03:31.820 Elizah Joy: Hmm.
10 00:03:32.100 ⇒ 00:03:45.349 Elizah Joy: Yep. A main thing for me today, like, the top offers on my list is the upgraded team policy that we have. I did see the…
11 00:03:45.560 ⇒ 00:03:56.469 Elizah Joy: Message that the finance team has sent over about the repercussions of Having, like, the buyout.
12 00:03:56.850 ⇒ 00:03:59.870 Elizah Joy: So yeah, thinking on that.
13 00:04:01.420 ⇒ 00:04:03.540 Rico Rejoso: Yeah, let’s discuss that.
14 00:04:03.930 ⇒ 00:04:06.619 Rico Rejoso: I also kind of figured out…
15 00:04:07.220 ⇒ 00:04:12.500 Rico Rejoso: yesterday that this will happen, so I encourage you to send out that message, right?
16 00:04:13.040 ⇒ 00:04:13.429 Elizah Joy: to the server.
17 00:04:13.430 ⇒ 00:04:22.579 Rico Rejoso: reason I want you to send out that message, because probably you’re going to receive feedback coming from them. And at the same time, the reason why we want to keep them involved is that they’re handling our finances.
18 00:04:22.580 ⇒ 00:04:23.260 Elizah Joy: Yeah.
19 00:04:23.890 ⇒ 00:04:37.900 Rico Rejoso: although there are external parties, we want to make sure that they also know the cycle of our cash flow, even though we come see, or Robert sees, that this is manageable, and also a good part in the future.
20 00:04:38.330 ⇒ 00:04:45.090 Rico Rejoso: I mean, I know, I saw Megan’s comment that only involving W2 employees, right?
21 00:04:45.330 ⇒ 00:04:49.840 Rico Rejoso: Or W2 folks. And since we don’t have anyone yet.
22 00:04:49.950 ⇒ 00:04:52.530 Rico Rejoso: But we have those… we have those…
23 00:04:52.710 ⇒ 00:04:56.609 Rico Rejoso: aligned or proposed for those such as Luke and Kayla.
24 00:04:57.420 ⇒ 00:04:59.520 Rico Rejoso: which are folks, within U.S.
25 00:05:00.320 ⇒ 00:05:07.699 Rico Rejoso: So maybe let’s enclose, or, you know, let’s, further close the scope of…
26 00:05:08.010 ⇒ 00:05:11.229 Rico Rejoso: Or of those folks that can evade the service.
27 00:05:11.630 ⇒ 00:05:12.330 Elizah Joy: Okay.
28 00:05:12.670 ⇒ 00:05:26.920 Rico Rejoso: So I think the next problem would be how you will respond to those folks that have requested, which are after you, such as Zoran, who probably is expecting this, since Utam discussed this with him already, about the possibility, or…
29 00:05:27.060 ⇒ 00:05:31.089 Rico Rejoso: You know, the possibility of providing devices, right?
30 00:05:31.510 ⇒ 00:05:32.350 Elizah Joy: Yeah.
31 00:05:33.190 ⇒ 00:05:47.559 Elizah Joy: Yeah, because we’ve… yeah, I think… from my… if I can recall, like, we announced this December, and then, yeah, I think, I’ll keep… because we have four at the moment, right? So we have Utam, we have Kayla.
32 00:05:47.740 ⇒ 00:05:52.290 Elizah Joy: And then we have Zoran requesting for devices.
33 00:05:52.820 ⇒ 00:05:53.450 Rico Rejoso: Hmm.
34 00:05:54.140 ⇒ 00:06:01.400 Rico Rejoso: So maybe we can opt… I don’t know, based on what Megan says here in the comments that I’ve… which are pretty long…
35 00:06:01.890 ⇒ 00:06:02.500 Elizah Joy: Yeah.
36 00:06:02.800 ⇒ 00:06:04.169 Rico Rejoso: Probably this.
37 00:06:04.680 ⇒ 00:06:07.480 Rico Rejoso: Those will have to wait until the second quarter.
38 00:06:07.650 ⇒ 00:06:16.240 Rico Rejoso: Of this year. And, probably we have to rewrite the documentation, stating that it’s only for W-2 folks.
39 00:06:16.820 ⇒ 00:06:18.860 Elizah Joy: Yeah. It’s a good thing that this is…
40 00:06:18.860 ⇒ 00:06:25.070 Rico Rejoso: Not made public yet by our executives, or did they already mention this during our retro?
41 00:06:25.250 ⇒ 00:06:44.530 Elizah Joy: Oh, this was already mentioned. Utam was the first to mention this, on a retro, I think, first week of January, if not first week, last year, December. But it’s, what was just said to the team is that it’s, it’s in progress, or about to start, but not finalized yet.
42 00:06:44.960 ⇒ 00:06:48.170 Rico Rejoso: Okay. I mean, they probably did forget about it.
43 00:06:48.170 ⇒ 00:06:49.160 Elizah Joy: Hmm.
44 00:06:49.160 ⇒ 00:06:50.900 Rico Rejoso: It’s been a couple of months already.
45 00:06:51.040 ⇒ 00:06:56.369 Rico Rejoso: But, yeah, let’s refresh those folks. Let’s get that documentation done, and.
46 00:06:56.370 ⇒ 00:06:56.810 Elizah Joy: Night.
47 00:06:56.810 ⇒ 00:06:58.580 Rico Rejoso: Do, that tread.
48 00:06:58.800 ⇒ 00:07:07.499 Rico Rejoso: informing Megan that, hey, we updated the document, this is only covering folks, or U.S. folks, USW2 folks only.
49 00:07:08.180 ⇒ 00:07:13.710 Rico Rejoso: At the same time. I don’t know, I haven’t checked the document yet, but if there’s, like, processes there.
50 00:07:14.250 ⇒ 00:07:23.590 Rico Rejoso: that would be changed, as long as it meets the requirements of those that are W… or that are USW2 folks. I think that’s good.
51 00:07:24.120 ⇒ 00:07:25.310 Elizah Joy: Okay.
52 00:07:25.630 ⇒ 00:07:26.210 Rico Rejoso: Okay.
53 00:07:26.250 ⇒ 00:07:27.310 Elizah Joy: And…
54 00:07:27.310 ⇒ 00:07:39.470 Rico Rejoso: Yeah, just finalize the document. We can’t keep this going unless we got the W-2 documentation. So probably if we will enforce this, the only one that we’ll be providing our equipments with will be with,
55 00:07:41.220 ⇒ 00:07:42.240 Elizah Joy: Yeah.
56 00:07:43.230 ⇒ 00:07:44.250 Elizah Joy: Okay.
57 00:07:44.410 ⇒ 00:07:52.779 Elizah Joy: Yeah, I think Robert has already… initially, we got Robert, but he’s already bought his, so yeah, just Udam at the moment.
58 00:07:55.090 ⇒ 00:07:57.519 Elizah Joy: Okay, I’ll get that done.
59 00:07:57.620 ⇒ 00:08:01.820 Elizah Joy: And then… next on my list…
60 00:08:02.030 ⇒ 00:08:08.040 Elizah Joy: is… I’m currently in conversation with Luke on the on LinkedIn.
61 00:08:08.220 ⇒ 00:08:12.349 Elizah Joy: Sales Navigator, because I did check Udam’s…
62 00:08:12.650 ⇒ 00:08:17.880 Elizah Joy: Plan, and it’s currently… it’s not allowing his…
63 00:08:18.230 ⇒ 00:08:31.620 Elizah Joy: plan to buy more seats, or to switch plans, because, what’s… what it’s saying is it’s, the option isn’t available. Like, in LinkedIn, UTAM has multiple subscriptions, so…
64 00:08:31.800 ⇒ 00:08:42.209 Elizah Joy: what we can do here is either have Robert’s account as the main account for the team plan for Sales Navigator, and then we just add Udon’s and Luke’s.
65 00:08:43.049 ⇒ 00:08:44.210 Elizah Joy: So…
66 00:08:44.490 ⇒ 00:08:54.489 Elizah Joy: So that’s the next step there, because, yeah, can’t add any more subscription to Udam’s account. It might be we have.
67 00:08:54.490 ⇒ 00:08:56.350 Rico Rejoso: subscription for UTAM.
68 00:08:56.600 ⇒ 00:08:57.850 Elizah Joy: Is there an event?
69 00:08:58.250 ⇒ 00:09:03.570 Elizah Joy: Yeah, actually, he’s already got the Sales Navigator, plan.
70 00:09:03.840 ⇒ 00:09:04.290 Rico Rejoso: Okay.
71 00:09:04.290 ⇒ 00:09:10.070 Elizah Joy: But it’s just, on a… like a personal plan for…
72 00:09:10.590 ⇒ 00:09:18.980 Elizah Joy: the first LinkedIn Sales Navigator. And what we’re aiming for is to have this team plan so that we get more discounts since we’re adding
73 00:09:19.110 ⇒ 00:09:23.909 Elizah Joy: more seats. But yeah, we have an active sales navigator planned for him.
74 00:09:24.640 ⇒ 00:09:28.530 Elizah Joy: And it just… at the moment, we can’t switch plans.
75 00:09:28.530 ⇒ 00:09:35.079 Rico Rejoso: So we cannot expand, Mutam’s current plan. I know… you mentioned it’s personal, or for… for him only.
76 00:09:35.810 ⇒ 00:09:36.370 Rico Rejoso: We can expect…
77 00:09:36.370 ⇒ 00:09:36.980 Elizah Joy: Yeah.
78 00:09:36.980 ⇒ 00:09:37.710 Rico Rejoso: implant.
79 00:09:38.300 ⇒ 00:09:43.860 Elizah Joy: We can expand to the team plan, but it, I believe it’s gonna come from Robert’s account.
80 00:09:43.940 ⇒ 00:09:58.699 Elizah Joy: If that’s, feasible, because, at the moment, it’s saying that, Udom has multiple subscriptions, and I did look at it. Yes, he has other subscriptions for, the LinkedIn itself, and there’s, at the moment, he’s got 3.
81 00:09:58.900 ⇒ 00:10:11.559 Elizah Joy: So, he cannot change any plans. It’s either we have to cancel the current one, the Sales Navigator, plan that he has, which I believe he’s gonna run up until…
82 00:10:14.750 ⇒ 00:10:20.040 Elizah Joy: Yeah, I think April 1st, since it started October 1st.
83 00:10:20.440 ⇒ 00:10:22.859 Elizah Joy: And it’s on a monthly,
84 00:10:23.600 ⇒ 00:10:24.860 Rico Rejoso: April 1st.
85 00:10:25.050 ⇒ 00:10:32.649 Elizah Joy: Yeah, so it’s either we cancel it now, and then wait April 1st for us to move to the team plan.
86 00:10:33.190 ⇒ 00:10:40.310 Elizah Joy: Because, yeah, I believe Udrama is actively using this one, so that’s why I don’t wanna, cancel it right now.
87 00:10:40.370 ⇒ 00:10:45.390 Rico Rejoso: Free, free trial ends when? March 27th?
88 00:10:45.690 ⇒ 00:10:50.149 Elizah Joy: Yeah, March 26th, and then we plan to move her…
89 00:10:50.550 ⇒ 00:10:53.609 Elizah Joy: Add her to the team plan, actually, on the 20th.
90 00:10:53.740 ⇒ 00:10:57.390 Elizah Joy: Before the free trial ends.
91 00:11:00.500 ⇒ 00:11:01.270 Rico Rejoso: Okay.
92 00:11:01.590 ⇒ 00:11:06.750 Elizah Joy: So, March 26th.
93 00:11:07.720 ⇒ 00:11:08.170 Rico Rejoso: March.
94 00:11:08.170 ⇒ 00:11:12.399 Elizah Joy: But we plan to move her on March 20th, so that…
95 00:11:12.620 ⇒ 00:11:25.529 Elizah Joy: we plan ahead, because, the concern there was, since Kayla’s already in the Recruiter Life Plan, she’s got… she’s already sent messages to people, and there might be some responses that
96 00:11:25.670 ⇒ 00:11:37.739 Elizah Joy: she might not get if she switches to the Sales Navigator plan, so we’re just trying to avoid that. So we will switch, start moving her on March 20th.
97 00:11:38.140 ⇒ 00:11:38.830 Elizah Joy: Mr. How about you.
98 00:11:38.830 ⇒ 00:11:40.660 Rico Rejoso: How about for Robert? How about for Robert?
99 00:11:40.990 ⇒ 00:11:47.919 Elizah Joy: It’s the same, actually, because for Robert, Luke is using that, and Luke has mentioned it ends on…
100 00:11:48.110 ⇒ 00:11:51.849 Elizah Joy: March… because it’s also on a monthly plan.
101 00:11:52.000 ⇒ 00:11:54.020 Elizah Joy: March 27th?
102 00:11:54.490 ⇒ 00:11:55.800 Rico Rejoso: 37th. Okay.
103 00:11:55.800 ⇒ 00:11:57.190 Elizah Joy: Yeah, March 27th.
104 00:11:57.190 ⇒ 00:12:03.300 Rico Rejoso: So if we’re gonna implement the team plan, we’re gonna do it by March 27th, or prior to March 27th.
105 00:12:03.300 ⇒ 00:12:03.850 Elizah Joy: Yeah.
106 00:12:03.850 ⇒ 00:12:08.930 Rico Rejoso: schedule it by then. Then, have Kayla
107 00:12:09.040 ⇒ 00:12:19.779 Rico Rejoso: move to under Robert’s account, then with some canceled, within March 20th, then join Robert’s account, or will be added to Robert’s team plan, right?
108 00:12:19.890 ⇒ 00:12:33.759 Elizah Joy: Yeah, so that… yep, I think that’s the best way to go, since Luke has been actively using Robert’s account in there, and he’s mentioned that he’s got, like, a number… numerous number of
109 00:12:33.980 ⇒ 00:12:38.680 Elizah Joy: Conversations in there, so he’s been using it, like.
110 00:12:38.830 ⇒ 00:12:40.900 Rico Rejoso: But nothing… Plus, once.
111 00:12:40.900 ⇒ 00:12:41.490 Elizah Joy: Yeah.
112 00:12:41.490 ⇒ 00:12:42.480 Rico Rejoso: Plan, right?
113 00:12:42.690 ⇒ 00:12:43.530 Elizah Joy: Yeah, nothing.
114 00:12:43.530 ⇒ 00:12:45.780 Rico Rejoso: Their email, their messages, and everything.
115 00:12:45.950 ⇒ 00:12:57.549 Elizah Joy: Yeah, nothing… nothing will be lost, it’s just we don’t want to have, like, a day where there is no active subscription for each of their accounts, so that the messages would still keep on coming.
116 00:12:57.780 ⇒ 00:13:04.770 Rico Rejoso: Okay, so for recruitment, I mean, we can upgrade Robert’s plan to a team plan.
117 00:13:05.070 ⇒ 00:13:05.900 Elizah Joy: Mmm.
118 00:13:05.900 ⇒ 00:13:08.160 Rico Rejoso: by the 20th, right? Then we can move
119 00:13:08.550 ⇒ 00:13:11.089 Rico Rejoso: plan under Robert’s plan by the 28th.
120 00:13:12.110 ⇒ 00:13:22.229 Rico Rejoso: We can cancel UTAM’s account by then. It will end March or April 1st, and we can move, or we can have… We can dedicate an account for Utam under Roberts, right?
121 00:13:22.480 ⇒ 00:13:25.879 Elizah Joy: Yeah, on, October 1st or before that.
122 00:13:26.170 ⇒ 00:13:30.839 Rico Rejoso: Can we not, like, cancel one of the subscriptions that UTAM has by April 1st?
123 00:13:31.520 ⇒ 00:13:32.760 Elizah Joy: Let me… But that will…
124 00:13:32.760 ⇒ 00:13:37.829 Rico Rejoso: caused a delay for, like, 10 days for Kayla and for 3 days for Robert, right?
125 00:13:38.000 ⇒ 00:13:50.420 Elizah Joy: Yep, that’s true. We can cancel it ahead of time. It’s just so, we have to prepare for any, like, conversations and stuff. But yeah, we can cancel it ahead of time.
126 00:13:51.180 ⇒ 00:13:59.680 Rico Rejoso: Okay, let’s propose that option, either with Tom or Robert, then just prepare, like, What are the risk.
127 00:13:59.950 ⇒ 00:14:00.390 Elizah Joy: Yeah.
128 00:14:00.390 ⇒ 00:14:07.920 Rico Rejoso: if we went through UTAMS, or we went the subscription under UTAM’s account, or if we go through under Robert’s account, right?
129 00:14:08.210 ⇒ 00:14:08.720 Elizah Joy: Since…
130 00:14:08.720 ⇒ 00:14:12.599 Rico Rejoso: I think the only risk for when we go through Thumbs account is the delay.
131 00:14:13.080 ⇒ 00:14:13.590 Elizah Joy: Yeah.
132 00:14:13.590 ⇒ 00:14:23.560 Rico Rejoso: They said they will not be having any subscription in LinkedIn for both Kayla and Robert, right? And if it’s Robert, there’s, like, any… the only risk would be
133 00:14:23.680 ⇒ 00:14:27.270 Rico Rejoso: We thumb would be… I don’t know, is there, like…
134 00:14:27.510 ⇒ 00:14:30.600 Rico Rejoso: with Tom’s account will be, like, a sub-account, right? Would there be.
135 00:14:30.600 ⇒ 00:14:31.180 Elizah Joy: Mmm.
136 00:14:31.180 ⇒ 00:14:33.330 Rico Rejoso: Difference from the main account itself.
137 00:14:33.870 ⇒ 00:14:51.489 Elizah Joy: Not really, it’s gonna be the same, it’s just, Robert’s gonna be, like, the admin of the entire team account, but, the plan would still remain the same. Like, they’ll still have the capabilities that they currently have in the Sales Navigator plan. They’re just added into a team account.
138 00:14:52.070 ⇒ 00:14:55.959 Rico Rejoso: Okay, I see. Alright, so there’s not much risk if we go through Roberts, right?
139 00:14:56.140 ⇒ 00:14:57.810 Elizah Joy: Yeah, yep.
140 00:14:58.370 ⇒ 00:15:06.049 Rico Rejoso: Okay, so maybe let’s just come up with a transition plan. Yeah. If we, or let’s say draft a transition.
141 00:15:07.550 ⇒ 00:15:08.510 Rico Rejoso: learn.
142 00:15:09.290 ⇒ 00:15:14.459 Rico Rejoso: to moving… To a team planner.
143 00:15:14.700 ⇒ 00:15:18.090 Rico Rejoso: LinkedIn impact, okay? Alright, great.
144 00:15:18.280 ⇒ 00:15:27.279 Rico Rejoso: And afterwards, once you confirm this one, once you make the payment by the 20 other stuff, make sure you put a bookmark on your calendar, just to make sure we get this done by then, alright?
145 00:15:27.280 ⇒ 00:15:27.970 Elizah Joy: Mmkay.
146 00:15:27.970 ⇒ 00:15:29.370 Rico Rejoso: I made a ticket for you here.
147 00:15:29.720 ⇒ 00:15:37.110 Rico Rejoso: Once we settle down all the action items here, which is drafted a transition plan,
148 00:15:38.640 ⇒ 00:15:49.249 Rico Rejoso: then we’re good, okay? Then we can close this out, then we can create another one for, making that subscription. Let’s just make sure that everyone agrees on this one, and if you can send this to a sales channel.
149 00:15:53.250 ⇒ 00:15:53.930 Rico Rejoso: Yeah.
150 00:15:53.930 ⇒ 00:15:56.590 Elizah Joy: After the transition plan, right?
151 00:15:57.550 ⇒ 00:15:58.100 Rico Rejoso: Yeah.
152 00:15:58.470 ⇒ 00:16:13.689 Rico Rejoso: Like, send us out, like, hey guys, we identified, some couple ways that we can go through with our LinkedIn team plan. I draft… we drafted a transition plan, once we started moving from.
153 00:16:13.690 ⇒ 00:16:14.200 Elizah Joy: Mmm.
154 00:16:14.200 ⇒ 00:16:17.639 Rico Rejoso: individual to a team plan, and here are the suggested steps.
155 00:16:18.020 ⇒ 00:16:18.680 Elizah Joy: Okay.
156 00:16:18.930 ⇒ 00:16:23.669 Rico Rejoso: Like, yeah. We want to make sure that they are aware on what’s gonna happen, and they will, you know.
157 00:16:23.780 ⇒ 00:16:36.720 Rico Rejoso: I mean, expectation is clear that if ever that they’re gonna lose access to some of it for a couple of hours or days, they are aware of it and, you know, will not hinder their operations, so they can settle everything prior to that date.
158 00:16:37.060 ⇒ 00:16:38.260 Elizah Joy: Yep.
159 00:16:38.580 ⇒ 00:16:41.830 Rico Rejoso: Because I don’t know if we have any big events or campaigns.
160 00:16:43.080 ⇒ 00:16:45.750 Rico Rejoso: You know, go through by that time, but we’ll definitely.
161 00:16:45.750 ⇒ 00:16:46.259 Elizah Joy: Oh, you’re kidding.
162 00:16:46.260 ⇒ 00:16:50.770 Rico Rejoso: We have to be prepared to have that, or to have the campaign launched prior to having the transition.
163 00:16:50.770 ⇒ 00:16:52.650 Elizah Joy: Yeah. Yeah.
164 00:16:52.810 ⇒ 00:16:59.200 Elizah Joy: Okay. Take note of. And then, I’ve already sent the…
165 00:17:00.370 ⇒ 00:17:06.609 Elizah Joy: Oh, sorry, no, I’ve already updated the slides that we have for ops for tomorrow.
166 00:17:06.760 ⇒ 00:17:10.239 Elizah Joy: It’s in there, I’m not sure if we wanna…
167 00:17:10.359 ⇒ 00:17:16.670 Elizah Joy: expand this more, then I’ve also sent this to the culture channel.
168 00:17:17.000 ⇒ 00:17:29.050 Elizah Joy: For Bryle and the execs to update. So that’s that. I’ve already, created the message that we’re gonna send on Friday. Let me send that to you in Slack.
169 00:17:29.450 ⇒ 00:17:31.339 Rico Rejoso: Wait, you have two here.
170 00:17:40.160 ⇒ 00:17:50.700 Rico Rejoso: Okay, yeah, I mean, I can check the slide later today. We’ll probably have to make sure that we have all the forms. By the way, did you draft the message that we’ll be sending to the Brainforge team?
171 00:17:50.700 ⇒ 00:17:51.720 Elizah Joy: Yeah.
172 00:17:51.970 ⇒ 00:17:54.789 Elizah Joy: Okay. Yep, I’ll send this now to you.
173 00:17:55.200 ⇒ 00:17:58.130 Rico Rejoso: Yep, and once good, you can just,
174 00:17:58.550 ⇒ 00:18:01.320 Rico Rejoso: schedule it for sending, maybe around 2PM.
175 00:18:01.460 ⇒ 00:18:03.359 Elizah Joy: Or 3, 2 p.m. Okay.
176 00:18:04.570 ⇒ 00:18:10.259 Rico Rejoso: Okay, let me just delete one of this, because I believe you already have the next steps here.
177 00:18:14.020 ⇒ 00:18:22.829 Rico Rejoso: Alright, send team-facing documentation to BFRetro. Okay, we’re gonna check this one, so I’ll probably go in here.
178 00:18:23.340 ⇒ 00:18:29.149 Rico Rejoso: And the delivery process form, I believe this is done, what… there’s the next steps here for me?
179 00:18:29.150 ⇒ 00:18:30.700 Elizah Joy: Mmm, yeah.
180 00:18:30.890 ⇒ 00:18:36.099 Rico Rejoso: Okay, let me do that. Let me assign this to me now, since you’re good with it.
181 00:18:36.210 ⇒ 00:18:39.829 Rico Rejoso: And what are the remaining? Finance, aging automation.
182 00:18:40.280 ⇒ 00:18:41.620 Elizah Joy: Yep.
183 00:18:41.620 ⇒ 00:18:43.830 Rico Rejoso: software dashboard, did you guys.
184 00:18:43.830 ⇒ 00:18:44.360 Elizah Joy: Yeah.
185 00:18:44.360 ⇒ 00:18:45.199 Rico Rejoso: For this one?
186 00:18:45.540 ⇒ 00:19:01.459 Elizah Joy: Mustaf is currently working on it, he’s messaged me yesterday on it, and I’m just waiting on updates from him, if it’s already, fixed in Snowflake, and then after that, we can continue doing this.
187 00:19:02.200 ⇒ 00:19:04.550 Rico Rejoso: Software dashboard.
188 00:19:05.680 ⇒ 00:19:09.300 Rico Rejoso: Waiting updates… follow-up today.
189 00:19:12.140 ⇒ 00:19:14.619 Rico Rejoso: But it’s a day 0305.
190 00:19:14.720 ⇒ 00:19:15.490 Rico Rejoso: Okay.
191 00:19:16.910 ⇒ 00:19:17.570 Elizah Joy: Yeah, literally.
192 00:19:17.570 ⇒ 00:19:23.680 Rico Rejoso: finance, aging automation, are we still working on this one? Or are we cancelling this? What’s the plan?
193 00:19:24.250 ⇒ 00:19:34.840 Elizah Joy: Yep, we’re working on this one since, I’ve already started doing this in Zapier. It’s just connecting QuickBooks and Zapier, because we’ve already…
194 00:19:34.840 ⇒ 00:19:36.969 Rico Rejoso: Access to QuickBooks, right?
195 00:19:37.310 ⇒ 00:19:45.320 Elizah Joy: Yup. Megan said she’s already sent it over in ops. I’m gonna check that one, because I did ping her.
196 00:19:45.490 ⇒ 00:19:48.510 Elizah Joy: Yesterday, for the QuickBooks.
197 00:19:48.850 ⇒ 00:19:52.880 Rico Rejoso: Okay, I don’t think, she’s gonna reply today, if…
198 00:19:52.880 ⇒ 00:19:53.810 Elizah Joy: Yeah.
199 00:19:54.340 ⇒ 00:19:55.710 Rico Rejoso: Can you…
200 00:19:56.030 ⇒ 00:20:01.099 Rico Rejoso: If ever, I think I can access QuickBooks using Thumbs account. I don’t know if I can…
201 00:20:01.100 ⇒ 00:20:02.780 Elizah Joy: hand that over to you.
202 00:20:02.780 ⇒ 00:20:08.169 Rico Rejoso: Or not, or… Well… I mean, I have the… I have access to Utem’s Google account.
203 00:20:09.120 ⇒ 00:20:11.739 Elizah Joy: I think you can add me, maybe?
204 00:20:11.930 ⇒ 00:20:17.850 Elizah Joy: Just add the operations… is that possible? The operations account in QuickBooks?
205 00:20:18.270 ⇒ 00:20:21.399 Rico Rejoso: It’s just like, what do you call this? A subaccount.
206 00:20:21.920 ⇒ 00:20:23.010 Elizah Joy: Mmm.
207 00:20:23.010 ⇒ 00:20:25.050 Rico Rejoso: Something like that, that I can access only…
208 00:20:25.540 ⇒ 00:20:34.850 Rico Rejoso: you know, just sign in and pass keys for Google. That’s what I can access, but I cannot share the account or the Google account itself to you.
209 00:20:34.980 ⇒ 00:20:35.460 Rico Rejoso: So, if.
210 00:20:35.460 ⇒ 00:20:36.520 Elizah Joy: Oh, okay.
211 00:20:36.520 ⇒ 00:20:51.000 Rico Rejoso: I might have to take this over from you. If you can, like, if you have this in place already, like, with all the, flow, and if there are, like, codes and stuff there, or the automation that you want to set up, if you can just.
212 00:20:51.000 ⇒ 00:20:51.590 Elizah Joy: Nope.
213 00:20:51.590 ⇒ 00:20:59.650 Rico Rejoso: Maybe I can implement it on my end, and I can help you out, close this one. I can still assign this to you, since you basically created everything, I just executed it.
214 00:20:59.870 ⇒ 00:21:09.440 Elizah Joy: Yeah, I think, yeah, that’ll be great. You can just… when I say connect it in Zapier, because that’s what’s missing in there.
215 00:21:10.060 ⇒ 00:21:15.210 Rico Rejoso: Provide… provide instructions… let me know what I should do to help you out on this.
216 00:21:15.210 ⇒ 00:21:16.130 Elizah Joy: Hmm.
217 00:21:16.620 ⇒ 00:21:17.120 Elizah Joy: Okay.
218 00:21:17.120 ⇒ 00:21:17.750 Rico Rejoso: Okay.
219 00:21:19.920 ⇒ 00:21:25.980 Rico Rejoso: for connecting… QuickBooks… With Zapier, right?
220 00:21:28.350 ⇒ 00:21:33.940 Rico Rejoso: Okay, if you can forward this to me after this, or maybe later today within the noon… by noon?
221 00:21:34.420 ⇒ 00:21:34.780 Elizah Joy: Yeah.
222 00:21:34.780 ⇒ 00:21:38.370 Rico Rejoso: I can help you out on this. Just let me know what needs to be done. I’m not…
223 00:21:38.370 ⇒ 00:21:38.970 Elizah Joy: Yeah.
224 00:21:39.320 ⇒ 00:21:43.909 Rico Rejoso: adapt to You know, but if you provide me instruction, I could probably help you out on that.
225 00:21:44.350 ⇒ 00:21:48.470 Elizah Joy: Yep, okay. Send that over then, I think.
226 00:21:48.850 ⇒ 00:21:49.810 Elizah Joy: Anything…
227 00:21:49.810 ⇒ 00:21:50.840 Rico Rejoso: else?
228 00:21:52.300 ⇒ 00:21:59.020 Elizah Joy: Anything… nothing else would… If we could, I think…
229 00:22:00.520 ⇒ 00:22:04.479 Elizah Joy: I can take more other tasks for today.
230 00:22:05.020 ⇒ 00:22:08.580 Rico Rejoso: Yeah, no worries, we’re also… we’re kind of free.
231 00:22:08.690 ⇒ 00:22:09.690 Rico Rejoso: So I…
232 00:22:09.690 ⇒ 00:22:10.700 Elizah Joy: Oh, okay.
233 00:22:10.700 ⇒ 00:22:13.340 Rico Rejoso: From ops to sales, to be honest.
234 00:22:13.490 ⇒ 00:22:14.130 Elizah Joy: Nope.
235 00:22:14.130 ⇒ 00:22:19.120 Rico Rejoso: Working on a cursor command, and that can help us draft the end of week.
236 00:22:19.600 ⇒ 00:22:24.159 Rico Rejoso: And also the… What do you call this? End of day.
237 00:22:24.490 ⇒ 00:22:25.370 Rico Rejoso: So we don’t have…
238 00:22:25.370 ⇒ 00:22:26.100 Elizah Joy: Mmm.
239 00:22:26.100 ⇒ 00:22:32.270 Rico Rejoso: draft that, and maybe you can… Yeah. The command is, visible for everyone that is using our cursor.
240 00:22:32.530 ⇒ 00:22:38.979 Rico Rejoso: So you can drive out, you know, my inputs and everything, as long as everything is within Slack.
241 00:22:39.820 ⇒ 00:22:40.480 Elizah Joy: Mmm.
242 00:22:40.480 ⇒ 00:22:54.380 Rico Rejoso: within linear, right? Because the basis for cursor… for that cursor command would be, like, checking out the dates. If you can see here, there are, like, two rows here that has dates, right? This one is the date created, and the other one is the date it was edited.
243 00:22:54.750 ⇒ 00:22:59.380 Rico Rejoso: So let’s… Hold… The Friday Retro Prep here was created
244 00:23:00.020 ⇒ 00:23:06.389 Rico Rejoso: Created yesterday, and it was edited today, and it was marked as done.
245 00:23:06.690 ⇒ 00:23:14.180 Rico Rejoso: So the command will be looking at all tickets that are Marcus Dunn, that was edited within today, for the end of day.
246 00:23:15.200 ⇒ 00:23:21.529 Rico Rejoso: list out all those… all those tickets or tasks that was done, and we’ll provide a end-of-day
247 00:23:21.720 ⇒ 00:23:24.469 Rico Rejoso: Summary for you, right?
248 00:23:24.850 ⇒ 00:23:28.009 Elizah Joy: Yeah, and that’s… sorry, go ahead, go ahead.
249 00:23:28.010 ⇒ 00:23:29.319 Rico Rejoso: Yeah, go ahead, your question?
250 00:23:29.470 ⇒ 00:23:33.090 Elizah Joy: That’s gonna be sent directly in Slack, or…
251 00:23:33.090 ⇒ 00:23:33.710 Rico Rejoso: I don’t…
252 00:23:34.040 ⇒ 00:23:35.400 Elizah Joy: in cursive.
253 00:23:35.800 ⇒ 00:23:36.809 Rico Rejoso: Just in person.
254 00:23:37.110 ⇒ 00:23:38.150 Elizah Joy: Oh, okay.
255 00:23:38.150 ⇒ 00:23:41.279 Rico Rejoso: It’ll be a lot if it can send it via Slack Apple’s laptop.
256 00:23:41.280 ⇒ 00:23:41.650 Elizah Joy: Break.
257 00:23:41.670 ⇒ 00:23:42.859 Rico Rejoso: MCP yet.
258 00:23:43.020 ⇒ 00:23:43.380 Elizah Joy: Yeah.
259 00:23:43.380 ⇒ 00:23:51.429 Rico Rejoso: So, it cannot read anything that is in Slack, so as much as possible, any tasks that we have here, like triage and stuff.
260 00:23:51.620 ⇒ 00:23:57.140 Rico Rejoso: put it here in, put it here in… what do you call this? In linear.
261 00:23:57.370 ⇒ 00:23:57.860 Rico Rejoso: So.
262 00:23:57.860 ⇒ 00:23:58.560 Elizah Joy: What’s the market?
263 00:23:58.560 ⇒ 00:24:16.619 Rico Rejoso: run, and you’re preparing for the end of day, just use that command, the cursor will gather everything, they just need to confirm what linear team are you pertaining to, just say, create an NFW or slash command NFW or review, then put in the linear team, which is operations, and it will do it for you.
264 00:24:17.180 ⇒ 00:24:26.150 Elizah Joy: Mmm, yeah, I think that’s good, because I was asking Cursor this, like, early this week, if there’s a way that we can
265 00:24:26.150 ⇒ 00:24:39.740 Elizah Joy: Well, what I had in mind originally was the transcript from platform, if you could, gather that and then organize that for, like, the daily sync that we send out, but I think, your process is much…
266 00:24:39.840 ⇒ 00:24:44.810 Elizah Joy: Cleaner, because it’s, connected and linear. It’s more real-time.
267 00:24:44.810 ⇒ 00:24:49.110 Rico Rejoso: cursor, it also has the… Vaults, or the folds.
268 00:24:49.110 ⇒ 00:24:49.440 Elizah Joy: Yeah.
269 00:24:49.440 ⇒ 00:25:01.709 Rico Rejoso: contains all the transcript that is in the platform. So the platform is connected in Cursor or in GitHub, so all the transcript is stored in GitHub. Cursor can read that, and it’s also part of the prompt, not just.
270 00:25:01.710 ⇒ 00:25:02.190 Elizah Joy: Mmm.
271 00:25:02.190 ⇒ 00:25:14.409 Rico Rejoso: all that is a linear ticket, but also to read everything in the trans… the transcript. So it’s a transcript plus linear, then it will create that as, that end of day, or end of week report.
272 00:25:14.960 ⇒ 00:25:15.510 Elizah Joy: Yeah.
273 00:25:15.510 ⇒ 00:25:18.150 Rico Rejoso: It will also suggest steps, let’s say.
274 00:25:18.730 ⇒ 00:25:23.380 Rico Rejoso: It read through all the tickets, it listed all the tickets, but upon checking the transcript.
275 00:25:23.920 ⇒ 00:25:28.210 Rico Rejoso: It’s, some of the action items in the transcript are not yet in linear.
276 00:25:28.540 ⇒ 00:25:29.250 Elizah Joy: Perfection.
277 00:25:29.250 ⇒ 00:25:31.320 Rico Rejoso: That’s a next step that you need to take.
278 00:25:31.550 ⇒ 00:25:40.179 Rico Rejoso: Like, next step, put this here, because it’s not in linear yet, but it’s… it is in this transcript, so it’s gonna cross-reference those transcripts and linear, right?
279 00:25:40.540 ⇒ 00:25:42.090 Elizah Joy: That was an issue.
280 00:25:42.090 ⇒ 00:25:47.979 Rico Rejoso: that I had, like, you know, we cannot just solely depend on linear. What if you forgot anything in linear?
281 00:25:47.980 ⇒ 00:25:48.800 Elizah Joy: Yeah.
282 00:25:48.800 ⇒ 00:25:50.389 Rico Rejoso: That’s not connected yet, right?
283 00:25:50.390 ⇒ 00:26:03.349 Elizah Joy: Yeah, that’s right, and yeah, I do… originally, what I did have was, like, the daily priorities for that day, but I think, yeah, this is good. It’s just, everything will be in cursor.
284 00:26:03.510 ⇒ 00:26:04.919 Elizah Joy: Yeah, we’ll be fine.
285 00:26:04.920 ⇒ 00:26:15.949 Rico Rejoso: to, you know, because it’s pretty hard, because before, what I was doing is going to platform, copying the transcript, going to GPT, pasting the transcript, right, and having it prompt
286 00:26:16.100 ⇒ 00:26:18.140 Rico Rejoso: into the output that I wanted to.
287 00:26:18.850 ⇒ 00:26:19.180 Elizah Joy: Mmm.
288 00:26:19.180 ⇒ 00:26:20.620 Rico Rejoso: Which is a lot of manual things.
289 00:26:20.620 ⇒ 00:26:21.070 Elizah Joy: Yeah.
290 00:26:21.070 ⇒ 00:26:27.110 Rico Rejoso: You know, Cursor can do that. Try to optimize how we can use Cursor further.
291 00:26:27.110 ⇒ 00:26:28.210 Elizah Joy: Christian, yeah.
292 00:26:28.210 ⇒ 00:26:33.590 Rico Rejoso: I also use Cursor for our end-of-month, list of items that we have published.
293 00:26:34.590 ⇒ 00:26:46.110 Elizah Joy: Yeah, I did… I had a call with Brile yesterday, and trying to utilize Cursor more. I do have a question on this, though.
294 00:26:46.220 ⇒ 00:26:52.519 Elizah Joy: Do we have, like, the… we used to use ChatGPT, right, for the format of our SOPs?
295 00:26:52.670 ⇒ 00:27:03.109 Elizah Joy: Do we have that in cursor, or can you share any prompts, or add the prompts? Not prompts, but the format that we want for the SOPs that we do in Notion?
296 00:27:04.320 ⇒ 00:27:11.469 Rico Rejoso: Wait… I believe I have that in cursor, because I already submitted a PR for that.
297 00:27:12.270 ⇒ 00:27:13.900 Rico Rejoso: Let me just share this.
298 00:27:14.050 ⇒ 00:27:20.299 Rico Rejoso: Maybe this is a perfect opportunity for us to discuss that. I was also exploring cursor more, so…
299 00:27:21.270 ⇒ 00:27:22.080 Rico Rejoso: or stuff.
300 00:27:22.210 ⇒ 00:27:27.879 Rico Rejoso: But let me see, template, templates, scripts…
301 00:27:33.230 ⇒ 00:27:37.820 Rico Rejoso: But I also, I already have it here, it’s more, it’s like, use the format.
302 00:27:38.660 ⇒ 00:27:39.350 Elizah Joy: -
303 00:27:39.400 ⇒ 00:27:50.320 Rico Rejoso: template or document format. That’s what I do. That’s what I say, and it will pick up the template that we have here. But I can create a skill.
304 00:27:50.690 ⇒ 00:27:51.870 Rico Rejoso: Sorry.
305 00:27:52.820 ⇒ 00:27:55.440 Rico Rejoso: Or a, this is what I’m doing.
306 00:27:56.280 ⇒ 00:28:01.339 Rico Rejoso: Right, this is the end of the… end of week updates for you. We can create an action or skill.
307 00:28:01.340 ⇒ 00:28:01.930 Elizah Joy: Yeah.
308 00:28:01.930 ⇒ 00:28:08.329 Rico Rejoso: Where it can, what do you call this? Look for the templates, or the…
309 00:28:08.870 ⇒ 00:28:15.720 Rico Rejoso: format that we had for documentation in Notion. And also this, we can use this in creating files in Notion, by the way.
310 00:28:15.720 ⇒ 00:28:16.590 Elizah Joy: Yeah.
311 00:28:16.960 ⇒ 00:28:21.570 Elizah Joy: Like, files, like, it’ll directly uploaded in Notion, is…
312 00:28:21.810 ⇒ 00:28:37.070 Elizah Joy: Did I understand that correctly? Oh, not yet. What I usually… what I used to do was that, once it’s set up in here, is that I would copy it in Notion. But how do you do that? Like, push it through Notion?
313 00:28:37.560 ⇒ 00:28:42.779 Rico Rejoso: That’s what I did before. I was kind of… that’s… that’s what I say, I was playing a lot with.
314 00:28:43.550 ⇒ 00:28:48.929 Rico Rejoso: I’m trying to learn more about this. I usually say use… Notion MCP.
315 00:28:50.020 ⇒ 00:28:53.009 Rico Rejoso: you have to make sure that the MCP is all connected.
316 00:28:53.620 ⇒ 00:29:03.629 Rico Rejoso: enabled or connected, right? So I have linear connected, I have Notion connected, I have operating that I would be connecting, but it was connected prior. I can also, like, assign
317 00:29:03.890 ⇒ 00:29:06.359 Rico Rejoso: Or allocate hours and operating.
318 00:29:06.360 ⇒ 00:29:07.270 Elizah Joy: music business.
319 00:29:08.100 ⇒ 00:29:12.180 Rico Rejoso: Since it’s… it’ll be better if we have the Slack MCP, but we don’t have the.
320 00:29:12.180 ⇒ 00:29:12.830 Elizah Joy: Yeah, sweet.
321 00:29:12.830 ⇒ 00:29:15.069 Rico Rejoso: I cannot read any conversations lapped yet.
322 00:29:15.370 ⇒ 00:29:22.720 Rico Rejoso: and Notion is good. This is… this is the tricky part, I guess, when I was discussing this with Gabe.
323 00:29:22.960 ⇒ 00:29:26.129 Rico Rejoso: Because Notion sometimes works, sometimes it doesn’t.
324 00:29:26.590 ⇒ 00:29:27.240 Elizah Joy: said that?
325 00:29:27.240 ⇒ 00:29:31.160 Rico Rejoso: what I do usually, like, it… Crystal says that I cannot
326 00:29:31.370 ⇒ 00:29:34.529 Rico Rejoso: look for the file in Notion, I just turned this off.
327 00:29:34.720 ⇒ 00:29:37.590 Rico Rejoso: Or disable this and turn it on back, or turn it on?
328 00:29:37.590 ⇒ 00:29:38.140 Elizah Joy: Mmm.
329 00:29:38.140 ⇒ 00:29:39.590 Rico Rejoso: Or enable it again.
330 00:29:39.710 ⇒ 00:29:45.010 Rico Rejoso: then I just typed in the prompt again, or just what I said here, I just entered it again.
331 00:29:45.190 ⇒ 00:29:46.590 Rico Rejoso: And it seems to work.
332 00:29:46.740 ⇒ 00:29:53.639 Rico Rejoso: But as mentioned before by Yukon and Brad, they’re having a hard time with Notion MCP, that’s why
333 00:29:53.800 ⇒ 00:29:58.050 Rico Rejoso: They’re suggesting to have, Obsidian, right?
334 00:29:58.050 ⇒ 00:29:59.080 Elizah Joy: Mmm…
335 00:29:59.080 ⇒ 00:30:03.550 Rico Rejoso: I looked into Obsidian, and maybe you can do your research as well.
336 00:30:03.990 ⇒ 00:30:06.749 Rico Rejoso: Obsidian is more like of an empty file compiler.
337 00:30:06.750 ⇒ 00:30:07.170 Elizah Joy: Yeah.
338 00:30:07.170 ⇒ 00:30:08.960 Rico Rejoso: up a GitHub stuff.
339 00:30:09.300 ⇒ 00:30:09.800 Rico Rejoso: And in.
340 00:30:09.800 ⇒ 00:30:10.600 Elizah Joy: It’s not…
341 00:30:10.720 ⇒ 00:30:13.150 Rico Rejoso: Suitable for client presentation.
342 00:30:13.810 ⇒ 00:30:14.670 Elizah Joy: Mmm.
343 00:30:14.670 ⇒ 00:30:19.510 Rico Rejoso: We usually have clients, we just have them go to, or when we have, like, you know, new hires.
344 00:30:19.720 ⇒ 00:30:24.480 Rico Rejoso: We usually either go to Google Docs, or Notion.
345 00:30:24.860 ⇒ 00:30:25.240 Elizah Joy: have them.
346 00:30:25.240 ⇒ 00:30:30.149 Rico Rejoso: And I think the whole team is using Notion, so I think Obsidian is not that…
347 00:30:30.560 ⇒ 00:30:34.119 Rico Rejoso: We just have to make this work as much as possible.
348 00:30:34.220 ⇒ 00:30:34.840 Rico Rejoso: But, yeah.
349 00:30:34.840 ⇒ 00:30:35.340 Elizah Joy: Similar.
350 00:30:35.340 ⇒ 00:30:37.260 Rico Rejoso: work in progress. You can, you can say.
351 00:30:38.530 ⇒ 00:30:56.410 Rico Rejoso: Use Notion MCP, but the problem here is you have to be, since Notion has a lot of, how do you call this, LinkedIn page, you have to be specific, like, when I was, if I was, or if I wanted them to look, within the operations manual in operations, right?
352 00:30:56.410 ⇒ 00:31:03.360 Rico Rejoso: I specifically say, use Notion MCP, go to Internal Operations Operations Manual, and look for
353 00:31:03.440 ⇒ 00:31:10.399 Rico Rejoso: then the document or the policy that I wanted them to check, then… Add this part.
354 00:31:10.520 ⇒ 00:31:12.510 Rico Rejoso: Edit will edit the file in Ocean.
355 00:31:14.070 ⇒ 00:31:15.359 Rico Rejoso: You just have to wait there.
356 00:31:16.370 ⇒ 00:31:25.439 Elizah Joy: Okay, that’s cool. I think this is very helpful, because at the moment, yeah, I do still copy and paste stuff in there.
357 00:31:25.440 ⇒ 00:31:31.280 Rico Rejoso: you can check it out. But, I was kinda, like, still doubtful about this. So whenever I’m…
358 00:31:31.500 ⇒ 00:31:39.819 Rico Rejoso: you know, having them change a document. By the way, you cannot undo this once you ask Cursor to write a document. It’s pretty hard to undo.
359 00:31:40.070 ⇒ 00:31:40.930 Elizah Joy: Mmm.
360 00:31:40.930 ⇒ 00:31:48.050 Rico Rejoso: make sure that, you know, we’re not missing, or we’re not missing any part. I usually still copy it, like, for example here.
361 00:31:48.800 ⇒ 00:31:52.450 Rico Rejoso: what would happen? I just usually…
362 00:31:53.810 ⇒ 00:31:56.470 Rico Rejoso: Still, make sure that I copy it.
363 00:31:57.080 ⇒ 00:31:59.229 Rico Rejoso: Or select everything, control.
364 00:32:00.380 ⇒ 00:32:06.440 Rico Rejoso: Then have cursor edit it and stuff, and you will see the edited part since it’s not highlighted, right?
365 00:32:06.930 ⇒ 00:32:08.560 Elizah Joy: Yeah.
366 00:32:08.560 ⇒ 00:32:09.979 Rico Rejoso: But if in case, you can just…
367 00:32:10.310 ⇒ 00:32:17.319 Rico Rejoso: delete everything and paste it again since you copied the original one, because you cannot undo anything that you’ve asked Cursor to do.
368 00:32:17.700 ⇒ 00:32:20.929 Elizah Joy: Oh, okay. Doesn’t have that feature, so you have to be careful, right?
369 00:32:21.250 ⇒ 00:32:22.500 Elizah Joy: Yeah, okay.
370 00:32:22.900 ⇒ 00:32:26.069 Rico Rejoso: Alright, yeah, so I think that’s it. I just showed you how I…
371 00:32:26.070 ⇒ 00:32:35.209 Elizah Joy: Yeah, thanks so much for that. This is, yeah, this is very helpful. I’m trying to utilize cursor more as well. It was…
372 00:32:35.420 ⇒ 00:32:42.999 Elizah Joy: Yeah. One of my goals for, upcoming days and weeks, utilize Cruiser more.
373 00:32:43.430 ⇒ 00:32:53.110 Rico Rejoso: Yeah, let’s do that. I mean, this is a tool provided by the company, and that’s not… I mean, if we’re gonna implement a tool for everyone to use, we might as well be the first one to test it out and make.
374 00:32:53.110 ⇒ 00:32:53.680 Elizah Joy: Yeah.
375 00:32:53.680 ⇒ 00:32:54.920 Rico Rejoso: That’s it on our end, right?
376 00:32:55.370 ⇒ 00:32:57.180 Elizah Joy: Yeah, I do agree.
377 00:32:57.480 ⇒ 00:33:00.830 Rico Rejoso: Okay, I just made that,
378 00:33:03.250 ⇒ 00:33:05.899 Rico Rejoso: Maybe you can test it out,
379 00:33:05.900 ⇒ 00:33:06.380 Elizah Joy: questions in Japan.
380 00:33:06.380 ⇒ 00:33:22.450 Rico Rejoso: I know we have, like, some downtime once you complete some of the tasks that you’re working on. We didn’t get any priorities yet from our stakeholder, but let’s make sure that anything that we’re executing or working on right now, there’s no loophole, or we can fill in the gaps accordingly, right?
381 00:33:22.450 ⇒ 00:33:22.900 Elizah Joy: Yeah.
382 00:33:22.900 ⇒ 00:33:29.789 Rico Rejoso: questions, we can respond to them confidently, since we have everything documented, or in Notion, or we have worked on it to make sure that, you know.
383 00:33:30.550 ⇒ 00:33:30.990 Elizah Joy: Yeah.
384 00:33:30.990 ⇒ 00:33:33.690 Rico Rejoso: There won’t be any backdoors for questions.
385 00:33:33.990 ⇒ 00:33:35.390 Elizah Joy: Yeah, yeah.
386 00:33:36.030 ⇒ 00:33:37.980 Rico Rejoso: What else?
387 00:33:38.210 ⇒ 00:33:42.269 Rico Rejoso: I guess… next week we have the finance meeting, right?
388 00:33:43.560 ⇒ 00:33:47.660 Rico Rejoso: Basically what Uttum wanted to do us here is…
389 00:33:47.790 ⇒ 00:33:56.010 Rico Rejoso: sync with finance, and I think this is another one that we need to add to the finance process. They wanted us to be involved in the
390 00:33:56.570 ⇒ 00:34:00.849 Rico Rejoso: Accounts Payable Review, or AP review.
391 00:34:01.040 ⇒ 00:34:01.560 Elizah Joy: Excuse me, what?
392 00:34:01.560 ⇒ 00:34:11.440 Rico Rejoso: that is, is to make sure that before we send out payments to contractors or to folks within Brainforge, we have the capacity to fund that.
393 00:34:11.630 ⇒ 00:34:29.549 Rico Rejoso: So one would be an AR review, what are our account receivable, or how much funds do we have in the bank for us to send out payments to contractors. And after we distinguish that, and after we distinguish, like, who are fifth for this one, we just have to, go back to UTAM by
394 00:34:30.370 ⇒ 00:34:31.690 Rico Rejoso: Tuesday, during our.
395 00:34:32.429 ⇒ 00:34:43.869 Rico Rejoso: and propose, like, hey, we have this account, available, we have $20,000 in the back, and here are the list of folks that, we can set out payments to. We just need
396 00:34:43.979 ⇒ 00:34:48.149 Rico Rejoso: You to let us know who to prioritize for sending out payments.
397 00:34:50.040 ⇒ 00:35:03.330 Rico Rejoso: Because previously, Utam was dictating everything on his own. Well, he’s still gonna do that, but, you know, let’s just take some steps off his plate and help out on the APR review, okay?
398 00:35:03.330 ⇒ 00:35:05.720 Elizah Joy: Yeah, okay, yep. And.
399 00:35:05.720 ⇒ 00:35:06.660 Rico Rejoso: Yeah, go ahead.
400 00:35:06.660 ⇒ 00:35:14.430 Elizah Joy: Oh, sorry, go ahead. This is not a question… no, I’m not that much related to this, but yeah, you go first.
401 00:35:15.310 ⇒ 00:35:21.669 Rico Rejoso: I mean, they wanted UTB to take this over, but…
402 00:35:21.670 ⇒ 00:35:22.090 Elizah Joy: Yeah.
403 00:35:22.090 ⇒ 00:35:23.210 Rico Rejoso: I suggest that…
404 00:35:23.540 ⇒ 00:35:36.370 Rico Rejoso: there’s… I mean, there’s… for your second month within the company, there’s a lot that you have to absorb, so I wanted to, you know, stand by with you as well to make sure that you fit, at the same time.
405 00:35:36.370 ⇒ 00:35:42.030 Elizah Joy: If you have any questions, I could also help answer that since I’m part of this. Yeah.
406 00:35:42.040 ⇒ 00:35:51.700 Rico Rejoso: else, I wanted to make sure that I can… or that we can both work together on it, because one goal that we wanted here in operation is that what I can do, you can do, right?
407 00:35:51.700 ⇒ 00:35:52.920 Elizah Joy: Mmm, I agree.
408 00:35:52.920 ⇒ 00:36:00.880 Rico Rejoso: We are a complete duplicate of every task or process that we’re working on, so that, you know, whatever one is out, one can take over.
409 00:36:01.080 ⇒ 00:36:14.649 Elizah Joy: Mmm, yeah, I agree on that, and I don’t mind, that at all. I think, having Union Loop in there as well is great, because, yeah, you know more on the processes that we do have.
410 00:36:15.260 ⇒ 00:36:16.740 Elizah Joy: Especially on that.
411 00:36:19.380 ⇒ 00:36:20.470 Rico Rejoso: Yep, questions?
412 00:36:20.610 ⇒ 00:36:27.060 Elizah Joy: Not… just that, we have to update the… submitting the…
413 00:36:27.500 ⇒ 00:36:34.929 Elizah Joy: clockify hours. It’s a minor change, but we have to, like, strictly enforce that they have to submit that by the end of the
414 00:36:35.030 ⇒ 00:36:41.470 Elizah Joy: Like, say, the end of the month, and then anything before that doesn’t get added to the…
415 00:36:41.800 ⇒ 00:36:43.440 Elizah Joy: on their invoice.
416 00:36:43.640 ⇒ 00:36:45.899 Elizah Joy: It’ll be added to the next…
417 00:36:46.270 ⇒ 00:36:50.720 Elizah Joy: invoicing, do we have to update the documentation that we have for that?
418 00:36:52.360 ⇒ 00:36:57.799 Rico Rejoso: Yeah, we have to. At the same time, what’s gonna happen? Since they put in the date already, and they cannot edit it, I guess?
419 00:36:57.800 ⇒ 00:36:58.300 Elizah Joy: Mmm.
420 00:36:58.300 ⇒ 00:37:01.529 Rico Rejoso: What’s gonna happen to those hours that were added?
421 00:37:02.410 ⇒ 00:37:08.950 Rico Rejoso: After… we’ve done, or we’ve done… or we’ve forwarded to finance. Like, let’s say that.
422 00:37:09.690 ⇒ 00:37:19.950 Rico Rejoso: hours, but right now, he has 120 hours. So what’s gonna happen to the 60 hours right now? Does he have to change the date to March, so it will show on the.
423 00:37:20.470 ⇒ 00:37:21.110 Elizah Joy: payment cycle.
424 00:37:21.110 ⇒ 00:37:25.130 Rico Rejoso: Or should we have finance take note of it on their end?
425 00:37:27.250 ⇒ 00:37:29.040 Elizah Joy: Yeah.
426 00:37:29.600 ⇒ 00:37:34.800 Elizah Joy: I think it can be… It should be added to the next invoice.
427 00:37:35.120 ⇒ 00:37:36.769 Elizah Joy: Do the next month.
428 00:37:37.610 ⇒ 00:37:39.530 Elizah Joy: If they added those in late.
429 00:37:39.850 ⇒ 00:37:47.349 Elizah Joy: But I’m not sure if finance is gonna agree to do that, because what could happen is that
430 00:37:47.640 ⇒ 00:38:07.489 Elizah Joy: It can be a habit, again, of our team members to add hours late, knowing that it’s still… their hours are still gonna be added to the next invoice, right? I think it’s just a mess… It can be a bit complicated when… for the dates, if I’m making sense, like, the hours was…
431 00:38:08.290 ⇒ 00:38:17.930 Elizah Joy: I mean, it was billed to the client during this month, and then they get paid, for the following month if the hours are submitted late, so I think that’s just a bit of the…
432 00:38:18.390 ⇒ 00:38:22.059 Elizah Joy: Things that we have to think of.
433 00:38:22.370 ⇒ 00:38:29.179 Rico Rejoso: So, what we can do here, I mean, let’s think of it right now. What we can do here is that, once we see the changes, like.
434 00:38:29.320 ⇒ 00:38:35.330 Rico Rejoso: Let’s say he downloaded the stuff the second day of the month, Right?
435 00:38:36.160 ⇒ 00:38:49.990 Rico Rejoso: there were, like, changes within the fifth, so we need to add an extra step by the fifth day of the month. Let’s try to compare the data of the one that we submitted to finance and the one that we have currently on Plopify, and let’s see if there are any discrepancy.
436 00:38:50.580 ⇒ 00:38:58.159 Rico Rejoso: 50 hours more today compared to when we sent it to finance, so we need to take note of those hours that were added, right?
437 00:38:58.160 ⇒ 00:38:58.729 Elizah Joy: That’s ridiculous.
438 00:38:58.730 ⇒ 00:39:02.680 Rico Rejoso: Note of that, we send out, or we check the list of the SLAs. If you can see.
439 00:39:03.000 ⇒ 00:39:05.649 Rico Rejoso: operations here, we have the escalation database.
440 00:39:05.650 ⇒ 00:39:06.450 Elizah Joy: Yeah.
441 00:39:06.870 ⇒ 00:39:14.460 Rico Rejoso: This person are not yet in the escalation database, but he submitted late. He submitted his hours late.
442 00:39:14.590 ⇒ 00:39:19.900 Rico Rejoso: For this month, so we’ll add him to the escalation database. This is gonna be his first offense.
443 00:39:20.340 ⇒ 00:39:23.819 Rico Rejoso: for the SLA document, or as per the escalation document.
444 00:39:24.790 ⇒ 00:39:40.320 Rico Rejoso: First offense, meaning we just have to send a direct message with the policy and inform him about this and that, that you have to follow this and that, or if not, you will be… or you will be, what do you call this? You will be enforced with a second, what do you call it? A second offense.
445 00:39:40.690 ⇒ 00:39:41.079 Elizah Joy: You will be back.
446 00:39:41.080 ⇒ 00:39:51.050 Rico Rejoso: escalated to a second offense or second occurrence, meaning that you will be given a written documentation to acknowledge that you have not yet again submitted your hours on a timely manner.
447 00:39:51.300 ⇒ 00:39:52.080 Rico Rejoso: Right?
448 00:39:53.240 ⇒ 00:40:00.499 Rico Rejoso: And after we document that, after we send out the necessary… or we follow the necessary escalation framework.
449 00:40:00.920 ⇒ 00:40:10.359 Rico Rejoso: With the hours that we’ve identified as discrepancy for the previous month that should be recorded by finance, we just need to send an email to finance.
450 00:40:11.540 ⇒ 00:40:21.690 Rico Rejoso: Hey, Finance. Hi. The following folks have added hours for this month, for the previous month, February, but were added late.
451 00:40:22.040 ⇒ 00:40:23.439 Rico Rejoso: Right? So…
452 00:40:23.840 ⇒ 00:40:35.430 Rico Rejoso: A following escalation… I mean, an escalation process was done for the following folks, but please take note of the following payments, which will be added on the next payment cycle, which is for the month of March.
453 00:40:36.980 ⇒ 00:40:37.640 Rico Rejoso: Right.
454 00:40:38.050 ⇒ 00:40:38.780 Elizah Joy: Yeah.
455 00:40:39.580 ⇒ 00:40:42.780 Rico Rejoso: Or, we can send it out, too, by the 15th.
456 00:40:43.140 ⇒ 00:40:45.180 Rico Rejoso: But it still will be for March.
457 00:40:45.850 ⇒ 00:40:46.630 Elizah Joy: Mmm, no.
458 00:40:46.630 ⇒ 00:40:55.019 Rico Rejoso: that option. We can send it fully on the next payment cycle along with that month cycle, or we can send it by the 15th, not by the end of month.
459 00:40:56.600 ⇒ 00:40:58.579 Rico Rejoso: Maybe we can include it in the email.
460 00:40:58.790 ⇒ 00:40:59.460 Rico Rejoso: like…
461 00:40:59.460 ⇒ 00:41:00.210 Elizah Joy: Depending power.
462 00:41:00.210 ⇒ 00:41:09.099 Rico Rejoso: finances and availability should be sent by the 15th, or are we capable to send it by the 15th, or should we wait until the end or the next payment cycle to send this out?
463 00:41:09.570 ⇒ 00:41:11.200 Elizah Joy: Okay.
464 00:41:11.390 ⇒ 00:41:13.400 Rico Rejoso: So one thing is we have to draft the email.
465 00:41:13.640 ⇒ 00:41:17.749 Rico Rejoso: We have to draft the first message for the escalation.
466 00:41:18.640 ⇒ 00:41:24.469 Rico Rejoso: Or the link of the Slack message that we will be sending, so everything would be, in general.
467 00:41:24.470 ⇒ 00:41:24.970 Elizah Joy: Let’s see.
468 00:41:25.430 ⇒ 00:41:34.070 Rico Rejoso: just to make sure that we don’t miss out on anything, okay? We shouldn’t be sending out a personalized message unless we wanted to discuss this in depth during a meeting.
469 00:41:34.070 ⇒ 00:41:34.550 Elizah Joy: Mmm.
470 00:41:34.550 ⇒ 00:41:36.920 Rico Rejoso: a snack card, or snack cuddle.
471 00:41:37.280 ⇒ 00:41:37.890 Rico Rejoso: Right?
472 00:41:40.470 ⇒ 00:41:42.699 Rico Rejoso: Or do you have any suggestions? Let me know.
473 00:41:43.480 ⇒ 00:41:46.020 Elizah Joy: -
474 00:41:47.390 ⇒ 00:41:49.359 Elizah Joy: I think, yeah, we… let’s keep it.
475 00:41:49.500 ⇒ 00:41:58.010 Elizah Joy: Consistent throughout, like, emails and stuff, and other messages that we do send out to the team.
476 00:41:58.330 ⇒ 00:42:02.719 Elizah Joy: I think having that…
477 00:42:03.810 ⇒ 00:42:09.189 Elizah Joy: Checking it on the 5th… on the 5th of the month is good, so that
478 00:42:09.380 ⇒ 00:42:18.440 Elizah Joy: We get to see if there are any changes for the past couple of days. For example, for the end of the month, if they added in, and then also
479 00:42:19.000 ⇒ 00:42:22.620 Elizah Joy: I think the 5th of the month will be a good date.
480 00:42:22.810 ⇒ 00:42:29.179 Elizah Joy: So that we can check it, because I think if… and then it gets added to the next, cycle.
481 00:42:29.900 ⇒ 00:42:33.800 Rico Rejoso: 15th of the month is when we check, or the 5th of the month.
482 00:42:34.370 ⇒ 00:42:38.879 Elizah Joy: 5th of the month, so it’s close to the end of the month.
483 00:42:39.300 ⇒ 00:42:48.289 Rico Rejoso: Okay, and we… on the email to finance, we get… we let Finance choose whether or decide whether we push it by the 15th or the 30th of the month, okay?
484 00:42:48.780 ⇒ 00:42:53.089 Elizah Joy: Yep, that’s… I agree on that, so that… because they,
485 00:42:53.540 ⇒ 00:42:56.600 Elizah Joy: So, for the cash flow purposes.
486 00:42:57.600 ⇒ 00:43:03.290 Rico Rejoso: At the same time, people like options. That’s been my… Moto form.
487 00:43:03.660 ⇒ 00:43:04.720 Rico Rejoso: Quite so long.
488 00:43:05.130 ⇒ 00:43:05.749 Elizah Joy: People like me.
489 00:43:05.750 ⇒ 00:43:08.229 Rico Rejoso: Let’s provide them options and let them decide.
490 00:43:08.660 ⇒ 00:43:09.969 Elizah Joy: Yeah.
491 00:43:10.340 ⇒ 00:43:14.930 Rico Rejoso: Alright, so, yeah, that’s it. So I think another step or another action, I think, for us is to
492 00:43:16.170 ⇒ 00:43:22.709 Rico Rejoso: Add a step to the finance process for this process, which is the invoice.
493 00:43:22.970 ⇒ 00:43:32.409 Rico Rejoso: Sending for team members, and linked out any necessary policies or documents that we have to follow when we encounter that process or that situation.
494 00:43:32.880 ⇒ 00:43:34.269 Elizah Joy: Yeah. Okay.
495 00:43:34.470 ⇒ 00:43:35.620 Rico Rejoso: Any questions?
496 00:43:36.130 ⇒ 00:43:38.540 Elizah Joy: Nothing else on my end.
497 00:43:40.010 ⇒ 00:43:44.349 Rico Rejoso: Okay, nothing else. Also, I’ll work on some cursor commands for now to help.
498 00:43:44.820 ⇒ 00:43:48.670 Rico Rejoso: out for the end of week, and also for running an audit on Veneer.
499 00:43:48.780 ⇒ 00:43:55.600 Rico Rejoso: And stuff, and I’ll let you know if you wanted to sync regarding that. Also, we need to have a meeting
500 00:43:56.120 ⇒ 00:43:57.730 Rico Rejoso: I guess tomorrow would be.
501 00:43:58.290 ⇒ 00:43:59.370 Rico Rejoso: Like, Thursday, right?
502 00:43:59.780 ⇒ 00:44:00.550 Elizah Joy: Yeah.
503 00:44:00.820 ⇒ 00:44:11.960 Rico Rejoso: Yeah, I didn’t… I forgot when I said this, but we need to have a meeting to discuss the recruit… to discuss the process that operations are involved with, right?
504 00:44:13.060 ⇒ 00:44:18.700 Rico Rejoso: Maybe let’s formalize that, let’s create an agenda and topics that we should discuss before we jump into that meeting.
505 00:44:19.190 ⇒ 00:44:22.529 Elizah Joy: Okay. I’ll set that up in our calendar.
506 00:44:22.910 ⇒ 00:44:29.989 Rico Rejoso: Okay, yeah, that’s it for me. If you don’t have any questions, I’m good. Just let me know if you have, via Slack, or…
507 00:44:30.580 ⇒ 00:44:33.530 Rico Rejoso: a message. I’ll be available on the other sheet, okay?
508 00:44:33.950 ⇒ 00:44:36.359 Elizah Joy: Okay, thank you so much, Rico.
509 00:44:36.360 ⇒ 00:44:37.779 Rico Rejoso: Alright, thank you, Eliza. Have a good one.
510 00:44:37.780 ⇒ 00:44:39.610 Elizah Joy: Thank you. Bye.