Meeting Title: Ops Meeting Date: 2026-03-03 Meeting participants: Brylle Girang, Rico Rejoso, Elizah Joy, Uttam Kumaran
WEBVTT
1 00:03:41.530 ⇒ 00:03:42.580 Brylle Girang: Hey guys!
2 00:03:43.510 ⇒ 00:03:44.630 Elizah Joy: Hi, guys.
3 00:03:45.160 ⇒ 00:03:45.810 Rico Rejoso: Hey, ew.
4 00:03:46.480 ⇒ 00:03:49.650 Rico Rejoso: With that message, just give him 1 minute.
5 00:03:50.110 ⇒ 00:03:50.740 Brylle Girang: Okay.
6 00:03:55.340 ⇒ 00:03:56.690 Brylle Girang: Bustario.
7 00:03:59.870 ⇒ 00:04:01.299 Rico Rejoso: Too early, right?
8 00:04:03.120 ⇒ 00:04:03.710 Brylle Girang: True.
9 00:04:07.660 ⇒ 00:04:12.250 Rico Rejoso: Brian, by the way, would you be presenting some part of the delivery? Just a quick update.
10 00:04:12.610 ⇒ 00:04:18.489 Brylle Girang: No, Yes, Eliza, I will be pushing my
11 00:04:19.190 ⇒ 00:04:25.830 Brylle Girang: updates to maybe the Friday retros instead, because it’s not really operation-specific.
12 00:04:26.300 ⇒ 00:04:28.529 Brylle Girang: But more of a company-wide.
13 00:04:28.690 ⇒ 00:04:29.480 Brylle Girang: Update.
14 00:04:30.700 ⇒ 00:04:36.360 Rico Rejoso: Well, I guess, based on last… Operation Sing Conversation.
15 00:04:36.590 ⇒ 00:04:39.579 Rico Rejoso: 2.180% a part of the delivery as well.
16 00:04:40.380 ⇒ 00:04:41.200 Brylle Girang: Mmm.
17 00:04:41.200 ⇒ 00:04:43.199 Rico Rejoso: Not operations related, but, you know…
18 00:04:43.750 ⇒ 00:04:46.679 Rico Rejoso: Some updates on the delivery and what’s happening and stuff.
19 00:04:50.160 ⇒ 00:04:53.180 Brylle Girang: Okay, well, scrap that. I’m working on the slides now.
20 00:04:53.640 ⇒ 00:04:54.969 Rico Rejoso: Yeah, take your time.
21 00:04:55.260 ⇒ 00:04:55.799 Brylle Girang: Thank you.
22 00:04:55.800 ⇒ 00:04:59.510 Rico Rejoso: Don’t take your time, we have, like, a couple of minutes before it starts and stuff.
23 00:05:00.300 ⇒ 00:05:01.370 Rico Rejoso: You can do it, though.
24 00:06:21.270 ⇒ 00:06:22.069 Uttam Kumaran: Hey, guys.
25 00:06:26.310 ⇒ 00:06:27.020 Brylle Girang: Hello.
26 00:06:27.020 ⇒ 00:06:27.809 Rico Rejoso: Good morning.
27 00:06:28.380 ⇒ 00:06:29.520 Uttam Kumaran: Morning.
28 00:06:30.220 ⇒ 00:06:31.390 Uttam Kumaran: How’s everything?
29 00:06:39.520 ⇒ 00:06:41.000 Brylle Girang: Awkward silence.
30 00:06:41.170 ⇒ 00:06:43.640 Uttam Kumaran: Everything’s okay, not okay?
31 00:06:44.400 ⇒ 00:06:47.660 Rico Rejoso: Good, very good. How is everything for you?
32 00:06:48.270 ⇒ 00:06:52.409 Uttam Kumaran: Everything’s… everything’s good, dude. Thank you.
33 00:06:52.870 ⇒ 00:06:53.630 Rico Rejoso: Great, great.
34 00:06:53.810 ⇒ 00:06:56.670 Rico Rejoso: Yeah, I can jump in. I’m Eliza.
35 00:06:56.670 ⇒ 00:06:57.410 Uttam Kumaran: Sure.
36 00:06:58.170 ⇒ 00:07:01.219 Elizah Joy: Okay, let me share my screen.
37 00:07:14.870 ⇒ 00:07:19.659 Rico Rejoso: Okay, yes, happy Tuesday, everyone, good morning, and
38 00:07:20.080 ⇒ 00:07:31.719 Rico Rejoso: quick presentation, for last week’s update, including the month of February, so this is, like, a overall update that we had, from what happened during the month of February.
39 00:07:31.780 ⇒ 00:07:42.090 Rico Rejoso: So, today’s topic will focus on the notion revamp, a bit of team culture, expense requests, and some of the forms and governance that we,
40 00:07:42.370 ⇒ 00:07:45.650 Rico Rejoso: Our processes that we have mapped out, from the month.
41 00:07:45.930 ⇒ 00:07:48.419 Rico Rejoso: Moving on, let’s start off with the renewals.
42 00:07:49.060 ⇒ 00:07:58.110 Rico Rejoso: So, yes, in the next two weeks, we have the following, and also on the past week that was discussed, a term contract for Lilo was graded.
43 00:07:58.320 ⇒ 00:08:16.450 Rico Rejoso: The NDA that, we also reviewed, for… from Caliber will be also reviewed by, Holly to… we’ll be providing updates. None yet, but as of yesterday, Holly started reviewing the NDA already. Global Vet Link.
44 00:08:16.560 ⇒ 00:08:19.360 Rico Rejoso: Robert has been in this, has been…
45 00:08:19.600 ⇒ 00:08:28.779 Rico Rejoso: in conversation with them, the MSA has been sent already, currently in review, and also the client mentioned that they will draft the NDA from their side.
46 00:08:28.890 ⇒ 00:08:38.299 Rico Rejoso: So we haven’t got any response yet, nor a copy of the NDA, but we’ll do… we’ll forward to legal once we get it from that client.
47 00:08:39.370 ⇒ 00:08:39.940 Rico Rejoso: No.
48 00:08:39.940 ⇒ 00:08:44.300 Uttam Kumaran: On that one, Rico, if people… like, are you on that email thread?
49 00:08:44.300 ⇒ 00:08:45.070 Rico Rejoso: Yes.
50 00:08:45.850 ⇒ 00:08:48.439 Uttam Kumaran: Maybe you can request it.
51 00:08:48.440 ⇒ 00:08:48.860 Rico Rejoso: Sure.
52 00:08:48.860 ⇒ 00:08:50.840 Uttam Kumaran: Just to keep it… just to keep it moving.
53 00:08:51.500 ⇒ 00:08:57.050 Rico Rejoso: I was thinking, like, since it was just mentioned yesterday, and they also requested.
54 00:08:57.050 ⇒ 00:09:00.820 Uttam Kumaran: Oh, okay, okay, okay, okay. If it was just yesterday, then that’s fine, that makes sense.
55 00:09:01.250 ⇒ 00:09:06.570 Rico Rejoso: I might follow up by tomorrow, if then, just to make sure we keep the conversation going.
56 00:09:07.880 ⇒ 00:09:25.540 Uttam Kumaran: Okay, great. Yeah, one thing I just want to share is, like, operations is part of the entire process, right? So, I don’t want to see… your guys’ role is not just, like, oh, logistics, right? It’s like, you can actually continue to help play a part in moving things forward.
57 00:09:25.940 ⇒ 00:09:39.120 Uttam Kumaran: You know, oftentimes when it comes to sales deals or other deals, you know, it’s like, oh, okay, we’re waiting on legal, we’re waiting on operations. I mean, I don’t… I’m not saying you guys don’t do a great job, I think, as soon as things come across your plate, but…
58 00:09:39.440 ⇒ 00:09:45.570 Uttam Kumaran: Finding ways to, Help every team continue to move the ball forward.
59 00:09:45.900 ⇒ 00:09:52.729 Uttam Kumaran: you know, it would be helpful, right? Not, thinking about, you know, if you think about the way I do things, right, like.
60 00:09:52.850 ⇒ 00:10:10.069 Uttam Kumaran: I… I keep nudging, however many times I can do so, so taking some of that energy and bringing it to the table, I think, is going to help everybody. So you guys can be more proactive in saying, like, hey, I have to do this, you guys aren’t helping me do this, like, that, you know, so… so keeping mind of that, I think, would be great.
61 00:10:10.580 ⇒ 00:10:17.540 Rico Rejoso: Gotcha, definitely. And at the same time, that’s, one thing. As we map out the sales process, we wanted to get involved.
62 00:10:17.550 ⇒ 00:10:33.520 Rico Rejoso: from deal creation, from not just an NDAs, SOW creations, as well, and editing it to the HubSpot. Part of it is also we want to, as we discussed yesterday, aligning, HubSpot to operating to Clockify, so we need to get more involved in the sales stuff.
63 00:10:34.200 ⇒ 00:10:35.430 Uttam Kumaran: Yes, yes, okay.
64 00:10:35.940 ⇒ 00:10:40.269 Rico Rejoso: Alright, 14 contracts that are expiring this week, we have both.
65 00:10:40.370 ⇒ 00:10:49.329 Rico Rejoso: For Jasmine and Joseph, we have received feedback coming from, Hannah and, Luke. For Joseph, for Jasmine, I don’t have any updates yet in regards to if we’re gonna…
66 00:10:49.330 ⇒ 00:10:55.030 Uttam Kumaran: So, Robert has the feedback on Jasmine. Can you ping… can you ping him in,
67 00:10:55.580 ⇒ 00:11:01.209 Uttam Kumaran: like, the ops channel, in the founding ops channel, or wherever, he has that feedback.
68 00:11:01.680 ⇒ 00:11:10.189 Uttam Kumaran: Okay. He said he would send it out yesterday, I don’t think he got to it, so he has that, though. And then on Joe, yeah, I mean, you guys read the message, like, what’s,
69 00:11:10.440 ⇒ 00:11:11.779 Uttam Kumaran: What’s your takeaway?
70 00:11:13.600 ⇒ 00:11:28.510 Rico Rejoso: Hannah wanted to, have Joe stay, but I don’t think that we have a lot, of tasks that was given to, to Joe as well. In regards to hours also, it’s not meeting the minimum requirement for the hours.
71 00:11:29.200 ⇒ 00:11:34.910 Uttam Kumaran: So do you think it’s more of, like, they just didn’t utilize him? Because he was pretty good at what he was doing.
72 00:11:34.910 ⇒ 00:11:36.309 Rico Rejoso: Like, what do you think…
73 00:11:36.310 ⇒ 00:11:37.650 Uttam Kumaran: What do you think it was?
74 00:11:38.340 ⇒ 00:11:39.959 Uttam Kumaran: I mean, I guess we…
75 00:11:39.980 ⇒ 00:11:49.420 Rico Rejoso: we didn’t need to get more tech, because I guess he was focused on creating more deck. Unless we expand what he’s doing, we can utilize it more.
76 00:11:51.390 ⇒ 00:12:01.419 Rico Rejoso: Because I think Hannah… I think that’s one problem, Hannah’s not utilizing Joe as much, because again, that’s the same issue we had with Hannah, right? Delegating some of the tasks. Hannah used to.
77 00:12:01.420 ⇒ 00:12:03.490 Uttam Kumaran: Yeah, I don’t think she’s delegating enough.
78 00:12:04.380 ⇒ 00:12:06.689 Uttam Kumaran: I mean, what do you think is best here? Because…
79 00:12:07.270 ⇒ 00:12:10.710 Uttam Kumaran: I mean, part of this is, like, okay, if I go…
80 00:12:11.240 ⇒ 00:12:14.030 Uttam Kumaran: if I go run that team, I think I can…
81 00:12:14.390 ⇒ 00:12:18.110 Uttam Kumaran: handle that, but I don’t know, like, I’m wondering, like, what’s the best thing we can do?
82 00:12:18.420 ⇒ 00:12:33.890 Rico Rejoso: Previously, when I was… when, like, we were, like, overseeing marketing, what we’re doing is, right, list down all the tasks of Hannah into linear. Then, once he got past that, hour, or let’s say the points that
83 00:12:34.080 ⇒ 00:12:45.790 Rico Rejoso: she should have for a cycle. I usually handed some things off to Anne and encouraged her to do so. Like, hey, this is beyond what you can do for this week, let’s hand it off to Anne already.
84 00:12:47.390 ⇒ 00:12:57.269 Rico Rejoso: I mean, she kind of, like, still got to head off some of this stuff, but in the end, we still managed to hand it off. I think that kind of supervision, again, for…
85 00:12:57.380 ⇒ 00:13:03.770 Rico Rejoso: Until she gets used to handing off stuff to other team members who are capable of doing so.
86 00:13:06.250 ⇒ 00:13:07.820 Uttam Kumaran: Okay.
87 00:13:08.750 ⇒ 00:13:12.130 Rico Rejoso: Like, let Luke know, since Luke is handling marketing.
88 00:13:12.130 ⇒ 00:13:16.380 Uttam Kumaran: Well, can I ask you for something? Can you, can you run me a report on…
89 00:13:16.770 ⇒ 00:13:23.090 Uttam Kumaran: like, all the tasks that Ann, Hannah, and Joe have done, like, in the last…
90 00:13:23.630 ⇒ 00:13:26.499 Uttam Kumaran: Let’s say month, the tasks and the hours.
91 00:13:26.830 ⇒ 00:13:31.369 Uttam Kumaran: And I basically just want to see, like, if delegation is happening, you know?
92 00:13:31.720 ⇒ 00:13:32.870 Rico Rejoso: Okay, got it.
93 00:13:33.960 ⇒ 00:13:35.989 Rico Rejoso: I’ll do this for the month of February, right.
94 00:13:37.090 ⇒ 00:13:37.780 Uttam Kumaran: Yes.
95 00:13:38.990 ⇒ 00:13:42.160 Rico Rejoso: Let me compile that and provide it. Put in this week.
96 00:13:43.090 ⇒ 00:13:43.710 Uttam Kumaran: Okay.
97 00:13:44.480 ⇒ 00:13:45.070 Rico Rejoso: Alright.
98 00:13:45.280 ⇒ 00:13:48.529 Rico Rejoso: So, moving on from renewals, next is…
99 00:13:49.190 ⇒ 00:13:53.270 Rico Rejoso: Yeah. Any questions so far, for the renewals, or are we good?
100 00:13:55.130 ⇒ 00:13:57.639 Uttam Kumaran: I think we’re good there, so…
101 00:13:58.080 ⇒ 00:14:04.230 Uttam Kumaran: Yeah, I mean, I’m… we’re negotiating with Urban Sems and Elements still, not sure what’s gonna happen.
102 00:14:04.530 ⇒ 00:14:06.250 Uttam Kumaran: I think we dropped Hydra.
103 00:14:06.490 ⇒ 00:14:13.780 Uttam Kumaran: And Lilo. So we’re focusing just on a fewer clients right now, but we’re still selling, you know, more deals, so they’re coming in.
104 00:14:16.340 ⇒ 00:14:17.020 Rico Rejoso: Yep.
105 00:14:18.330 ⇒ 00:14:26.030 Rico Rejoso: And… For recruitment, Kyle is not available since… She is in Pacific.
106 00:14:26.240 ⇒ 00:14:34.270 Uttam Kumaran: We discussed this. I also advise, if and ever, we can have a separate meeting for recruitment, so we can go into the details, having… Okay.
107 00:14:34.270 ⇒ 00:14:47.989 Rico Rejoso: But a quick preview on recruitment. We have, like, 12 interviews this week. That includes 1 final, 2 second rounds, and 9 first rounds, and also a couple of VF chats. One event is also being, I mean, will be hosted by Kayla herself.
108 00:14:48.000 ⇒ 00:15:01.629 Rico Rejoso: We have over 30 applications in the past 7 days, we had a surge of applications, and I believe we had a review yesterday, and some of the folks moving forward, and 2 active job postings for AI Engineer and Senior Data Associate.
109 00:15:02.060 ⇒ 00:15:15.669 Rico Rejoso: Again, we still have the data engineer, interview assessment task that we’re finalizing once we do so. We have two folks that are ready, or we’ll be, we will be emailing, we’ll be sending an email for the final, final interview.
110 00:15:17.930 ⇒ 00:15:19.100 Uttam Kumaran: Okay, great.
111 00:15:20.040 ⇒ 00:15:23.579 Rico Rejoso: So, moving on from recruitment to operations…
112 00:15:23.730 ⇒ 00:15:32.379 Rico Rejoso: Yep, as you know, in the last month, we had this Notion revamp, and a lot has changed from Notion. We had a new homepage for this year.
113 00:15:32.620 ⇒ 00:15:46.969 Rico Rejoso: And that consists of a variety of places and also categories. Main thing is that we want to ensure that it is more accessible, it is quicker for everyone to click in from one page to another. At the same time, it takes less time to do so.
114 00:15:47.270 ⇒ 00:15:50.789 Rico Rejoso: Now, for the notion and documentation… next slide, please.
115 00:15:52.520 ⇒ 00:16:05.579 Rico Rejoso: We did a quick Notion revamp that includes auditing of all the documents, from database tagging, audit follow-through, and homepage optimization. From homepage, we also had this how to use the Notion documentation.
116 00:16:05.610 ⇒ 00:16:14.569 Rico Rejoso: as a guide for everyone who will be using Notion. I know we have the Notion MCP in place, but if in case someone also wanted to go through Notion himself and also
117 00:16:14.750 ⇒ 00:16:20.180 Rico Rejoso: Review or see how Notion is… how Notion can be used.
118 00:16:20.240 ⇒ 00:16:38.799 Rico Rejoso: for themselves, especially for new hire, we had this documentation in place in the homepage so they can also read through it prior to going through any pages. Also, we have the quiz that contains the forms, and a expense request form that is accessible for everyone whenever they need to send out an expense request. We also advise them to use Slack instead.
119 00:16:38.800 ⇒ 00:16:48.019 Rico Rejoso: If they prefer to… which… you set up a, quick control, what’s it called, an automation to get the expense request form and submit it via Slack.
120 00:16:49.070 ⇒ 00:16:49.870 Uttam Kumaran: Okay.
121 00:16:49.870 ⇒ 00:17:01.689 Rico Rejoso: For the Notion structure, it’s this simple. We have this master documentation database with linked and filtered to other pages, such as for the client delivery team, for the operations team, and for everyone in the company.
122 00:17:01.840 ⇒ 00:17:07.840 Rico Rejoso: So, this is, also, we are, creating some SOPs or playbooks.
123 00:17:07.880 ⇒ 00:17:25.770 Rico Rejoso: that are team-facing, which everyone can review. And, Kayla and I were also gathering these team-facing documents, SOPs and policies for everyone, or for us to introduce to, new hires. At the same time, we want to make sure that they review them, prior to, stepping in to
124 00:17:26.260 ⇒ 00:17:28.130 Rico Rejoso: Brainforge. Again.
125 00:17:28.130 ⇒ 00:17:28.450 Uttam Kumaran: Okay.
126 00:17:28.450 ⇒ 00:17:33.079 Rico Rejoso: Go, at most 3 clicks, less friction, and avoid the necessary unfinished pages.
127 00:17:33.080 ⇒ 00:17:35.459 Uttam Kumaran: That’s the goal of documentation and recap.
128 00:17:36.200 ⇒ 00:17:37.559 Rico Rejoso: For the next one.
129 00:17:37.770 ⇒ 00:17:43.629 Rico Rejoso: tools and forms. As mentioned, we have created some tools and, I mean, some forms that can,
130 00:17:43.660 ⇒ 00:18:01.559 Rico Rejoso: help us better record what’s happening, with our team members, such as expense request form. We also created team-facing documents for the team, updated this one, and also gave more details on how we… on what to expect when using the expense request form, such as when can they receive,
131 00:18:01.770 ⇒ 00:18:05.579 Rico Rejoso: their, I mean, response when they made a request.
132 00:18:05.910 ⇒ 00:18:12.260 Rico Rejoso: and also updated the out-of-office form, from Linear. This was,
133 00:18:12.760 ⇒ 00:18:26.880 Rico Rejoso: This was made, prior to us being part of Brainforge. We made a quick update for us to be, for easier, I mean, for convenience access at the same time, updated a few times, so we,
134 00:18:27.130 ⇒ 00:18:35.869 Rico Rejoso: team member doesn’t need to fill out a lot of details when submitting an out-of-office form. We also thought of creating a SICK form in linear,
135 00:18:36.190 ⇒ 00:18:46.550 Rico Rejoso: with the team-facing documentation, this ensures that when someone is, or absent, we also get a record of it, and we can also announce to the team that… or for that team member that
136 00:18:46.720 ⇒ 00:18:56.200 Rico Rejoso: he or she is absent on that day. We still haven’t launched or introduced this one yet, as we finalize the documentation, and we intend to do so on our BF Retro.
137 00:18:57.140 ⇒ 00:18:57.600 Uttam Kumaran: Okay.
138 00:18:57.600 ⇒ 00:19:15.589 Rico Rejoso: same time, the ops request linear automation that we did, wherein everyone can make a request on Slack, and we will receive it on linear, on the triage request. At the same time, we can review it, accept it, and also, as per our SLA documentation, give feedback within the next… or within 48 hours.
139 00:19:17.730 ⇒ 00:19:18.540 Rico Rejoso: As mentioned.
140 00:19:18.540 ⇒ 00:19:24.869 Uttam Kumaran: So my question, my question here, are there other request forms that I can help develop for you guys?
141 00:19:26.090 ⇒ 00:19:41.129 Rico Rejoso: As of now, none, since we have the linear asks and the ops requests, created. We’re still thinking of other ways or other forms or requests that, you know, we can, help the team with. As we identify, we may, inform in the operations channel.
142 00:19:44.000 ⇒ 00:19:48.830 Uttam Kumaran: And then, how many… do you guys know how many you’re getting per… per week.
143 00:19:50.030 ⇒ 00:19:58.460 Rico Rejoso: For, yes, for the ops request, an average, not average, but maximum that we have received for a week is 8 for now, and minimum was 2.
144 00:19:59.850 ⇒ 00:20:00.430 Uttam Kumaran: Okay.
145 00:20:01.020 ⇒ 00:20:05.520 Uttam Kumaran: One question, like, Do you, like, I guess…
146 00:20:06.290 ⇒ 00:20:12.090 Uttam Kumaran: So, you know, one question we had last week was, like, do we still want to do the ops request channel?
147 00:20:12.380 ⇒ 00:20:14.830 Uttam Kumaran: I guess, like, is your feedback that, like.
148 00:20:15.290 ⇒ 00:20:20.079 Uttam Kumaran: we shouldn’t do that public channel. Instead, everybody should just use a linear ask.
149 00:20:20.700 ⇒ 00:20:23.770 Uttam Kumaran: And, like, I guess my question would be…
150 00:20:24.030 ⇒ 00:20:27.280 Uttam Kumaran: Do you want to remove that channel? Or, like, what do you think?
151 00:20:29.230 ⇒ 00:20:31.850 Uttam Kumaran: Or, like, yeah, I guess up to you guys.
152 00:20:32.360 ⇒ 00:20:39.189 Rico Rejoso: Yeah, we haven’t really thought of it at the same time, since the ops requests are coming in linear, and we’re using…
153 00:20:39.190 ⇒ 00:20:39.529 Elizah Joy: are you doing?
154 00:20:39.530 ⇒ 00:20:51.259 Rico Rejoso: linear and accepting those requests. At the same time, the ops request channel that was created is also a great channel for us to look at the requests that we’re receiving from that client, as it serves as a notification for us.
155 00:20:51.420 ⇒ 00:21:00.309 Rico Rejoso: Prior to, and give, you know, just, once we see that there, we also go to linear right away to check, the full details of the request.
156 00:21:00.770 ⇒ 00:21:04.360 Rico Rejoso: So I think it is still beneficial for us to have that ops request chat.
157 00:21:05.420 ⇒ 00:21:06.030 Uttam Kumaran: Okay.
158 00:21:07.320 ⇒ 00:21:14.459 Brylle Girang: Question here, do we have documentation on Linear Ask? Like, what does it do? How can people use that?
159 00:21:15.460 ⇒ 00:21:34.820 Rico Rejoso: That’s what we, finalized, which is… which are the team-facing documentation. Though, that was created, like, last… last week, all the team-facing documentation was revamped last week, we will also be sending it out later this week during our BF retro. So, expect that you can receive it,
160 00:21:34.980 ⇒ 00:21:49.889 Rico Rejoso: A great question also. We can also forward it to our Brainforge team Slack channel, so everyone can take a look at it. We did it before, prior, but right now, since we made a few changes, we might as well launch it again for everyone to see and review.
161 00:21:50.980 ⇒ 00:21:53.159 Brylle Girang: Okay. Well, Tom, it might be…
162 00:21:53.390 ⇒ 00:22:00.349 Brylle Girang: nice if we could see all of this in the platform? Like, do we have a specific page there dedicated to, like.
163 00:22:01.320 ⇒ 00:22:01.900 Uttam Kumaran: fiscal.
164 00:22:01.900 ⇒ 00:22:03.390 Brylle Girang: any specific stuff.
165 00:22:04.470 ⇒ 00:22:06.159 Uttam Kumaran: Yeah, good point. So, like.
166 00:22:06.410 ⇒ 00:22:11.610 Uttam Kumaran: If you have a question, you don’t have to necessarily, like, go through Slack, you can, like, see some of it there.
167 00:22:11.930 ⇒ 00:22:12.460 Brylle Girang: Yeah.
168 00:22:13.300 ⇒ 00:22:22.249 Uttam Kumaran: Can you create a ticket, just in the… yeah, in the platform, or… yeah, I think there’s a platform team, and you can just assign to me, I’ll pick it up.
169 00:22:22.670 ⇒ 00:22:23.290 Brylle Girang: Okay.
170 00:22:28.320 ⇒ 00:22:31.269 Rico Rejoso: Any more questions in regards to the tools and forms?
171 00:22:36.760 ⇒ 00:22:40.510 Rico Rejoso: Okay, I think we can proceed to process.
172 00:22:40.910 ⇒ 00:23:00.450 Rico Rejoso: Yes, as we map out a lot of process that includes operations, delivery, finance, and legal, we are also mapping them out to make sure that we don’t miss any steps as we work on those processes. For now, we have the GTM process map coming from sales. We’re still mapping out the sales itself process.
173 00:23:00.450 ⇒ 00:23:05.140 Rico Rejoso: As, from deals up to, client or contract signing.
174 00:23:05.140 ⇒ 00:23:08.200 Rico Rejoso: So, we want to get more involved in the process, as mentioned.
175 00:23:08.200 ⇒ 00:23:21.990 Rico Rejoso: For legal process map, this one has been finalized. It’s simply from NDA up to contract signing that we have mapped out, and for operations, includes daily, weekly, and monthly, quarterly tasks.
176 00:23:22.110 ⇒ 00:23:25.190 Rico Rejoso: That we have, or project-specific, task.
177 00:23:25.660 ⇒ 00:23:35.060 Rico Rejoso: Same goes with the finance process map, which we wanted to get more involved in. Eliza has been more focused on the finance process map. That includes sending out, our monthly
178 00:23:35.300 ⇒ 00:23:50.500 Rico Rejoso: our end-of-month clockify records, making sure that we don’t miss anything as we help out the finance process, a lot of, projects, with weekly and monthly. And also the recruitment process map that Kayla has taken over with.
179 00:23:50.510 ⇒ 00:24:07.099 Rico Rejoso: I guess right now, or what I’ve created for the recruitment are BF chats and the interview and hiring decision system, but we will further work on, work on some processes up to onboarding, as per Kayla, and we still, we will be providing updates as we go through it.
180 00:24:07.460 ⇒ 00:24:24.739 Rico Rejoso: All right. One thing that we created is the escalation and the SLA, which is a process from when a policy has not been, being… or has not been followed by a certainty member. We can go to this documentation and see. Right now, I’ve consulted with Kayla since
181 00:24:24.740 ⇒ 00:24:35.219 Rico Rejoso: part of, he’s… I mean, she’s part of the people operations. I want to ensure that the escalation process is also suitable, as per… and also the SLA, which
182 00:24:35.230 ⇒ 00:24:40.939 Rico Rejoso: Ensures that the operations will get back to any requests coming from the team members within 48 hours.
183 00:24:42.080 ⇒ 00:24:42.650 Uttam Kumaran: Okay.
184 00:24:43.080 ⇒ 00:24:53.150 Rico Rejoso: Right, and also, lastly, the Operating Enforcement Handbook. We had this… we had a discussion yesterday, which is to update the team facing the EP101 guide.
185 00:24:53.980 ⇒ 00:25:12.219 Rico Rejoso: That includes, the use of cursor, or, cursor, specifically the operating MCP, in helping them out, allocate hours for team members. I’ve also added that in the EP101 guide. I haven’t released that one yet. I’m still doing a quick check before releasing it to the EPs as well.
186 00:25:12.300 ⇒ 00:25:19.939 Rico Rejoso: But so far, we have improved in updating operating and allocating hours. So, we’ll, continue to implement so every week.
187 00:25:20.050 ⇒ 00:25:26.610 Rico Rejoso: Until, until we’ve further polish, this process for our engagement planners.
188 00:25:27.900 ⇒ 00:25:29.030 Rico Rejoso: Any questions?
189 00:25:34.000 ⇒ 00:25:34.730 Rico Rejoso: Okay?
190 00:25:34.940 ⇒ 00:25:46.670 Rico Rejoso: So yeah, this one has been set out in the operations channel. If you have any questions further in the process, as we… as you guys explore through it, just let us know, and we’ll further help, further help out,
191 00:25:46.840 ⇒ 00:25:50.599 Rico Rejoso: Discuss the processes that we’ve mapped out for each department.
192 00:25:51.510 ⇒ 00:25:52.140 Uttam Kumaran: Okay.
193 00:25:52.140 ⇒ 00:25:54.820 Rico Rejoso: So, next one is the expense request. Eliza?
194 00:25:54.820 ⇒ 00:26:08.910 Elizah Joy: Thanks, Rika. So, yeah, as Rica has mentioned earlier, we did, set up the forms for this, so for the expense requests, just a quick update on that is that for this month, we did,
195 00:26:08.940 ⇒ 00:26:18.100 Elizah Joy: set up the form for the expense and equipment requests, so it brought in weekly ops discussion for, like, during our weekly, daily ops sync.
196 00:26:18.110 ⇒ 00:26:37.859 Elizah Joy: Rika and I do get, reviews for the expense requests that we get, and then we do regular coordination with finance team for reimbursement process. So our goal here is to, get each request resolved within 24 to 48 hours, and as soon as possible, if
197 00:26:37.980 ⇒ 00:26:47.099 Elizah Joy: For the team members, and our goal is to have no stale requests, so, we get the requests from team members herself right away.
198 00:26:47.180 ⇒ 00:27:00.919 Elizah Joy: And then, just a quick update, so there’s a current tool request from Kayla. So this is for the weekly ops that we do. So, she wants to do a LinkedIn Recruiter Lite, and I want to get this.
199 00:27:01.080 ⇒ 00:27:04.510 Elizah Joy: discuss this with you, Tom, but
200 00:27:04.620 ⇒ 00:27:15.400 Elizah Joy: My suggestion here is, since she’s gonna be the only team member using Recruiter Lite, I did do my research on this, and I think,
201 00:27:15.590 ⇒ 00:27:28.809 Elizah Joy: if she goes for the recruiter light, it’s kind of the same with the sales navigator, correct me if I’m wrong, but, with the Sales Navigator, since you already have a couple of team members, I think, yeah, we have 4 seats at the moment.
202 00:27:28.810 ⇒ 00:27:40.530 Elizah Joy: For Sales Navigator, so we can increase that to 5 seats, because it’s basically the same, and then we get more feature out of Sales Navigator compared to Recruiter Lite.
203 00:27:42.260 ⇒ 00:27:52.859 Uttam Kumaran: Oh, okay. I mean, I think… is there anything at a… like, I think for particular, she wanted, like, something around job posts and DMs, but you think she should just use SalesNav instead?
204 00:27:53.400 ⇒ 00:28:07.959 Elizah Joy: Yep, because, the thing with that is that she’ll have limitation with the in-mails, if she wants to use those. Since Sales Navigator, they do have more in-mails, like, like 50 in-mails for the
205 00:28:07.960 ⇒ 00:28:18.059 Elizah Joy: plan that we have currently, which is the core plan, compared to the Recruiter Live, which only gets, like, 15 in-mails, and I don’t think that’s, sufficient enough.
206 00:28:18.260 ⇒ 00:28:19.330 Elizah Joy: Or… Okay.
207 00:28:19.600 ⇒ 00:28:21.560 Elizah Joy: The…
208 00:28:21.770 ⇒ 00:28:31.370 Elizah Joy: kind of thing that she wants to do, like, for example, for the job posts. And then we do get advanced filters if we wanna, search for
209 00:28:31.750 ⇒ 00:28:33.930 Elizah Joy: Potential team members.
210 00:28:37.230 ⇒ 00:28:38.710 Uttam Kumaran: Okay. I mean…
211 00:28:39.440 ⇒ 00:28:46.459 Uttam Kumaran: I feel like, you know, I just did a quick search, I think I agree with your take. Do you want to start a discussion and…
212 00:28:47.040 ⇒ 00:28:57.479 Uttam Kumaran: Do you want to start a discussion in operations and mention to her? Because I think you’re right. I believe, like, yeah, it’s kind of the same thing anyway, so… and that’s fine with me.
213 00:28:58.340 ⇒ 00:29:06.370 Elizah Joy: Yep, yep, I can do that. And also, Rika and I was dis- were discussing that, for example, there are team members who want, like.
214 00:29:08.740 ⇒ 00:29:25.199 Elizah Joy: new softwares, however, that would, the reimbursement process would be, like, a monthly thing, so I figured, we could do the recruit, the sales navigator, since we already have that software. But yeah, I could start that discussion, in the ops channel to loop Kayla in.
215 00:29:26.010 ⇒ 00:29:31.750 Uttam Kumaran: Okay, okay. And then, yeah, so I… we… we still haven’t purchased… the,
216 00:29:32.370 ⇒ 00:29:36.170 Uttam Kumaran: We still haven’t purchased, sales now for everybody, right?
217 00:29:36.710 ⇒ 00:29:38.250 Elizah Joy: Hmm, yeah.
218 00:29:41.690 ⇒ 00:29:44.590 Uttam Kumaran: So, is that something that you recommend we do?
219 00:29:44.750 ⇒ 00:29:54.859 Uttam Kumaran: Yep, we can do that, right away after this, because, yeah, we have four… we can do, I think it’s in linear, a ticket in linear, we can do 4 seats for car plan.
220 00:29:54.970 ⇒ 00:30:02.769 Elizah Joy: And then, if Kayla agrees on using Sales Navigator, we can increase that to 5 seats on a team, team plan.
221 00:30:04.280 ⇒ 00:30:04.850 Uttam Kumaran: Okay.
222 00:30:07.170 ⇒ 00:30:13.280 Elizah Joy: Okay, and then for, just a quick update for the Donut app, we did,
223 00:30:13.580 ⇒ 00:30:38.520 Elizah Joy: we’ve been doing the bi-weekly cadence pair team members for one-on-one via Coffee Buddies channel. We did filter out the people that we want to do, like, the donut app pairings, and then, we also included the stats that we do in our weekly ops agenda, and also in the Friday Retro. And I do suggest, since we’re getting… I’ll show the stats after this slide, but we’re getting
224 00:30:39.080 ⇒ 00:30:43.910 Elizah Joy: good, stats for the past few weeks that we’ve been doing the donut
225 00:30:44.200 ⇒ 00:31:00.030 Elizah Joy: app pairings, and in the donut app, there’s a new feature now that you can do, like, a donut selfie. So what that is, is that after, like, team members have paired, in the Coffee Buddies, they could upload
226 00:31:00.030 ⇒ 00:31:04.890 Elizah Joy: I mean, yeah, if they could upload a selfie, if they want, during their Donut app.
227 00:31:05.310 ⇒ 00:31:06.320 Elizah Joy: pairings.
228 00:31:06.320 ⇒ 00:31:07.680 Uttam Kumaran: Oh, okay, nice.
229 00:31:07.680 ⇒ 00:31:23.299 Elizah Joy: And I think that’ll be fun for us, like, for example, if Rico and I have meet, we could also share that, in the Coffee Buddies channel, and I think it’ll be a good, addition for us to, to increase our team culture. So…
230 00:31:24.610 ⇒ 00:31:42.309 Elizah Joy: I think, we can start doing that, it’ll be more fun for everyone, and… yep, for Buddy Program, we did… started soft launching this, like, for example, when we did onboard Bryle, he was paired with Rika, and then, once we get more, like, new team members, it’ll be…
231 00:31:42.310 ⇒ 00:31:50.559 Elizah Joy: fully implemented, so, but we still have a decision pending if we want to do recognition or rewards for buddies.
232 00:31:51.720 ⇒ 00:31:52.989 Uttam Kumaran: Yeah, what do you think?
233 00:31:54.070 ⇒ 00:31:59.369 Elizah Joy: I think we can do, like, a token of appreciation for
234 00:31:59.630 ⇒ 00:32:05.059 Elizah Joy: after the pairing for each, buddies that we do. Maybe, like.
235 00:32:05.540 ⇒ 00:32:09.179 Elizah Joy: A meal or something by the end of those.
236 00:32:09.370 ⇒ 00:32:10.440 Elizah Joy: 6 weeks.
237 00:32:10.440 ⇒ 00:32:10.980 Uttam Kumaran: it.
238 00:32:11.140 ⇒ 00:32:14.560 Uttam Kumaran: Yeah, do you want to also ask Kayla? Because she’s doing some…
239 00:32:14.560 ⇒ 00:32:15.040 Elizah Joy: Yeah.
240 00:32:15.040 ⇒ 00:32:18.459 Uttam Kumaran: Gifts for one year, anniversaries.
241 00:32:18.460 ⇒ 00:32:20.219 Elizah Joy: okay.
242 00:32:20.220 ⇒ 00:32:23.480 Uttam Kumaran: Do you want to ask her? Maybe she can also consider doing, like.
243 00:32:24.070 ⇒ 00:32:26.679 Uttam Kumaran: The person who did the most buddies, like, end of quarter, maybe?
244 00:32:27.060 ⇒ 00:32:27.920 Uttam Kumaran: something.
245 00:32:28.330 ⇒ 00:32:33.729 Elizah Joy: Okay, yep, yep. I can discuss that with you, look, because we do have a call later today.
246 00:32:35.550 ⇒ 00:32:36.440 Uttam Kumaran: Okay, okay.
247 00:32:36.590 ⇒ 00:32:37.100 Elizah Joy: Bye.
248 00:32:37.100 ⇒ 00:32:39.570 Brylle Girang: How does the body selection work, though?
249 00:32:39.970 ⇒ 00:32:42.160 Brylle Girang: Like, who assigns the bodies?
250 00:32:42.850 ⇒ 00:32:57.380 Elizah Joy: At the moment, ops team do assign that, so what happens is, with the buddy program, we do pair them up with a tenured team member, one that’s somehow closer to the role that they… or the department that they’re in.
251 00:32:57.640 ⇒ 00:33:02.889 Elizah Joy: So that they are fully supported during, the four weeks that they’re in the PUTTY program.
252 00:33:03.930 ⇒ 00:33:04.590 Brylle Girang: Okay.
253 00:33:07.450 ⇒ 00:33:08.820 Brylle Girang: Okay, thank you.
254 00:33:10.000 ⇒ 00:33:27.600 Elizah Joy: Okay, and then, for last, pairings, we did get, like, 50%… 56% participation rate as of February 16th. So, this was the recent round, so it did conclude last Friday. We still have yet a few team members to…
255 00:33:28.520 ⇒ 00:33:43.599 Elizah Joy: like, fill up or answer if they’ve met meat or not, but compared to January, February, and, both the donut pairing for February, they… we did good on the stats of that, because we did get a more than 50% of participation rate.
256 00:33:44.470 ⇒ 00:33:45.050 Uttam Kumaran: Okay.
257 00:33:47.090 ⇒ 00:33:55.980 Elizah Joy: Okay, and then for, March, so what’s next is, we’re almost close to closing off all the,
258 00:33:56.850 ⇒ 00:34:07.500 Elizah Joy: projects that we have in Instagant, so that includes the monthly ops control dashboard, so that’s the margin costs and revenue, which you’ve sent over yesterday, Utam. So yeah.
259 00:34:07.800 ⇒ 00:34:11.170 Elizah Joy: I’ll start finalizing this so we can close this off.
260 00:34:11.179 ⇒ 00:34:23.299 Elizah Joy: Early this week or next week, and then we’ll also be aligning the process with HubSpot, operating, Clockify, and then the sales process, and then for the upgraded team.
261 00:34:23.300 ⇒ 00:34:37.970 Elizah Joy: The next steps for this is to just choose the payment plan that we want to do. It’s either we do the 2 years or 3 years leasing plan, and then the shipping info for all the… for the four team members that we have. That includes you, Tom.
262 00:34:37.969 ⇒ 00:34:40.100 Uttam Kumaran: So, we can get that going.
263 00:34:41.500 ⇒ 00:34:45.790 Uttam Kumaran: So yeah, you’re gonna move… you’re gonna take that to the finish line. I think 3 years is fine, right?
264 00:34:45.790 ⇒ 00:34:54.049 Elizah Joy: Mmm, yep, yep. I think for years, because Apple has a good… even if the device has already been for 3 years, it’s still running well.
265 00:34:54.340 ⇒ 00:34:57.619 Elizah Joy: And we’re gonna… we have a good,
266 00:35:00.220 ⇒ 00:35:11.989 Elizah Joy: features, or the devices that we get from Apple, they’re of good, so they’re M4 and M5, so that’s gonna work wonders even during the 3 years.
267 00:35:14.110 ⇒ 00:35:16.480 Brylle Girang: Okay. I have… I have a question.
268 00:35:16.630 ⇒ 00:35:25.290 Brylle Girang: So just curious, when it comes to, let’s say, offboarding, what’s going to be the process for the company-provided devices?
269 00:35:27.040 ⇒ 00:35:38.569 Elizah Joy: No, that’s a good question, because, at the moment, we don’t have that set up yet, or finalized on what we’re gonna do with, for example, the
270 00:35:38.790 ⇒ 00:35:45.660 Elizah Joy: to… like, for example, if the team member doesn’t complete their… the 3-year plan, I…
271 00:35:46.960 ⇒ 00:35:50.499 Elizah Joy: I think I’ll discuss this with Rika and what we can do on that.
272 00:35:55.010 ⇒ 00:35:58.330 Brylle Girang: Okay. In my previous company, we offered.
273 00:35:59.740 ⇒ 00:36:03.429 Elizah Joy: two options. You can… they can buy it out, or, you know.
274 00:36:03.430 ⇒ 00:36:08.160 Brylle Girang: They can just return it to the company, and by buying out, there’s a depreciated cost.
275 00:36:10.820 ⇒ 00:36:12.140 Uttam Kumaran: Oh, interesting, okay.
276 00:36:12.870 ⇒ 00:36:25.679 Rico Rejoso: Yeah, but I guess we, we’ll formalize this one and create a documentation around it, just to make sure we have, you know, we have TensorFlow, because this will still be depending on the upgraded team.
277 00:36:27.060 ⇒ 00:36:31.239 Rico Rejoso: conversation that we’ll be having. Yeah, so yeah, we’ll discuss this later.
278 00:36:31.410 ⇒ 00:36:33.929 Rico Rejoso: Or after this meeting, and get back to the question.
279 00:36:34.330 ⇒ 00:36:34.790 Brylle Girang: Okay.
280 00:36:34.790 ⇒ 00:36:35.400 Rico Rejoso: Bring it up.
281 00:36:35.960 ⇒ 00:36:45.149 Brylle Girang: Also wanted to, maybe we also need to think about the security, like, do we need to install MDMs for these devices, etc.
282 00:36:46.670 ⇒ 00:36:55.460 Uttam Kumaran: Yes, that’s something that, again, I don’t really know a lot about. I did hear that,
283 00:36:55.800 ⇒ 00:37:00.960 Uttam Kumaran: I did hear that Upgraded may be offering that, so maybe worth asking them, but…
284 00:37:01.160 ⇒ 00:37:05.499 Uttam Kumaran: Yeah, if any of you guys have experience with that, like, I’m totally open to thoughts.
285 00:37:06.450 ⇒ 00:37:09.160 Brylle Girang: I have a bit of experience when it comes to
286 00:37:09.310 ⇒ 00:37:13.280 Brylle Girang: this device management, so let’s work together here, Rick on a license.
287 00:37:13.930 ⇒ 00:37:15.370 Rico Rejoso: Yeah, definitely.
288 00:37:16.320 ⇒ 00:37:21.230 Rico Rejoso: Then we’ll loop and upgrade it once we come up with, you know.
289 00:37:21.390 ⇒ 00:37:23.270 Rico Rejoso: Plan on how it should be.
290 00:37:23.520 ⇒ 00:37:25.109 Brylle Girang: So, you can confirm with them.
291 00:37:27.970 ⇒ 00:37:29.010 Rico Rejoso: Thanks, Brian.
292 00:37:29.280 ⇒ 00:37:29.920 Brylle Girang: Okay.
293 00:37:31.090 ⇒ 00:37:31.910 Rico Rejoso: Eliza?
294 00:37:32.310 ⇒ 00:37:50.940 Elizah Joy: Yeah, thanks, Brel. And then, lastly, we’ll be finalizing the delivery process map. At the moment, we already have submissions from CSO. The ones that we don’t have yet are from the SL, so after that, we can finalize that. And then,
295 00:37:51.230 ⇒ 00:38:01.180 Elizah Joy: Of course, ops team is open for any, ad hoc tasks that we want to do for this March, and then we can take that on.
296 00:38:01.950 ⇒ 00:38:02.500 Uttam Kumaran: Okay.
297 00:38:04.380 ⇒ 00:38:08.200 Elizah Joy: Alright, I’ll pass, I’ll…
298 00:38:08.200 ⇒ 00:38:10.090 Brylle Girang: this, over to you, Bryl.
299 00:38:10.400 ⇒ 00:38:28.089 Brylle Girang: Yeah, this is mine. So, over the past two weeks, we have launched two commands, as part of our AI nativity push for the delivery team, and this initially revolves around our EPs. So, the first command, EP audit cursor command, is just,
300 00:38:28.530 ⇒ 00:38:32.570 Brylle Girang: more efficient way to ensure that our EPs and our CSOs
301 00:38:32.610 ⇒ 00:38:50.330 Brylle Girang: are in track when it comes to their linear tickets, making sure that meetings are properly recorded, and we don’t lose any action items from any meetings that we have with our clients. The second one of the weekly kickoff updates is more of,
302 00:38:50.510 ⇒ 00:38:56.770 Brylle Girang: Us improving the way how we communicate with our clients, ensuring that we start the week with…
303 00:38:57.320 ⇒ 00:39:04.880 Brylle Girang: detailed communication plans that we can just send over to their Slack channels in just one command.
304 00:39:05.160 ⇒ 00:39:12.070 Brylle Girang: I’m also working with Kayla in standardizing a cursor walkthrough for onboarding, which means that
305 00:39:12.190 ⇒ 00:39:25.880 Brylle Girang: all newly onboarded people should be… I should be meeting with them, just to make sure that they push using cursor. We have seen through our cursor usage review that
306 00:39:26.090 ⇒ 00:39:40.559 Brylle Girang: going on a call with them, just taking the time to explain how cursor works, how to use cursor, etc, similar to what Otam did with me, was really efficient and effective into making sure that they actually use the tool.
307 00:39:41.040 ⇒ 00:39:48.979 Brylle Girang: At the same time, we have one report completed, and then one report upcoming. The first one is the cursory switch review.
308 00:39:49.050 ⇒ 00:40:01.580 Brylle Girang: It was really not surprising. I sent over the results in the Brainforge team channel, but the first review would be a baseline for us to monitor how
309 00:40:01.920 ⇒ 00:40:13.330 Brylle Girang: that the company adopts Cursor over the next few weeks. For the people that are not utilizing Cursor, I will be meeting with them, I will do the same.
310 00:40:13.500 ⇒ 00:40:21.939 Brylle Girang: things that I did with Hannah and Kayla, and try to understand what their friction points are, so that we can improve how we help them adopt.
311 00:40:22.330 ⇒ 00:40:32.370 Brylle Girang: The second one is an EP pain points and recommendations report that I’m working on this week, and I’ll share the details and the results with you with them.
312 00:40:33.650 ⇒ 00:40:52.670 Brylle Girang: At the same time, we’re working on memos into standardizing and streamlining our tools, and this consists of our Asana versus Linear memo, as well as an Obsygian vs. Notion memo. So for Asana versus Linear, the main goal here is to
313 00:40:53.460 ⇒ 00:40:56.140 Brylle Girang: Move the business into…
314 00:40:56.720 ⇒ 00:41:10.359 Brylle Girang: a one tool for all when it comes to project management. As you may know, when it comes to project management, we have basically three tools. We have linear, we have instant, and we have operating, and in a way.
315 00:41:10.430 ⇒ 00:41:20.780 Brylle Girang: So we’re trying to research and understand if we can just merge all of this together into one tool, which would make adoption easier, which would make compliance
316 00:41:21.050 ⇒ 00:41:28.200 Brylle Girang: how do you call this? Non-negotiable, since there will be less friction points and less reasons for people to
317 00:41:28.340 ⇒ 00:41:31.289 Brylle Girang: To… to not do whatever we’re supposed to do.
318 00:41:31.760 ⇒ 00:41:51.169 Brylle Girang: And then the second one is an oxygen versus Notion memo, so I feel bad presenting this after you presented the Notion revamp that you did, Rico, but this is not meant to undermine whatever efforts you guys have put. I think the framework and the wireframe that you have developed
319 00:41:51.170 ⇒ 00:41:53.869 Brylle Girang: Will greatly help us if we consider
320 00:41:53.870 ⇒ 00:41:58.039 Brylle Girang: pushing Obscision. But the main goal here, or the main point.
321 00:41:58.060 ⇒ 00:42:09.709 Brylle Girang: is to ensure that our knowledge base can also be connected with our vault. So currently, Notion is connected to Cursor via MCP, and it doesn’t really work that well.
322 00:42:09.750 ⇒ 00:42:23.789 Brylle Girang: Obscision works primarily with markdowns, and markdowns can easily be stored in our GitHub repository, which would make, you know, the cursor ecosystem that we have here a lot better.
323 00:42:23.940 ⇒ 00:42:34.460 Brylle Girang: So this is something that I am also researching. I’m creating a plan, and then I’m going to make sure that we focus on our non-negotiables, and treat this as
324 00:42:34.950 ⇒ 00:42:43.310 Brylle Girang: a question on which tool we should use, not should we move to Obscision, or should we leave Notion.
325 00:42:43.880 ⇒ 00:42:45.439 Brylle Girang: Yeah, that’s for delivery.
326 00:42:46.430 ⇒ 00:42:56.009 Uttam Kumaran: Yeah, one thing I want to say there is, like, we’re always in the market to be better, right, in whatever way possible. Like, we’ve all invested in all the tools we’re using, but…
327 00:42:56.220 ⇒ 00:43:06.890 Uttam Kumaran: you know, tools change, and we want to always be on the forefront. So I’m always interested in people coming with new opinions, and then we debate. Like, that’s… that’s it. Like, I think it’s totally, totally fine.
328 00:43:09.390 ⇒ 00:43:10.140 Rico Rejoso: I agree.
329 00:43:16.410 ⇒ 00:43:19.729 Brylle Girang: I think that’s the end of the presentation, right? Okay.
330 00:43:21.290 ⇒ 00:43:27.669 Rico Rejoso: Thank you, if any questions, I mean, yeah, we’re opening the floor for any questions so far, Litong.
331 00:43:28.090 ⇒ 00:43:29.780 Rico Rejoso: Anything that you wanted to add?
332 00:43:30.760 ⇒ 00:43:39.130 Uttam Kumaran: Yeah, I mean, I’m interested to see those memos. You know, I’m also particularly interested, maybe, Rico, in…
333 00:43:39.270 ⇒ 00:43:52.790 Uttam Kumaran: in… for this presentation also, I don’t know if it’s easy for you to put together a slide with just, like, the number of tickets and, like, the categories of tickets that came up. It allows me to sort of see how much this team is taking on.
334 00:43:53.130 ⇒ 00:43:55.450 Uttam Kumaran: Just a simple, like.
335 00:43:56.080 ⇒ 00:44:02.409 Uttam Kumaran: Yeah, you could even just take a screenshot of the linear… the chart in linear, and I don’t want you guys to spend too much time there.
336 00:44:02.590 ⇒ 00:44:08.419 Uttam Kumaran: Just so I can see, like, how many tickets are coming in, and, like, where they’re… what categories they are.
337 00:44:08.890 ⇒ 00:44:24.189 Uttam Kumaran: And then, yeah, again, my last ask is going to be to also try and spend more time in Cursor, and use Cursor to do your tasks, like to ask questions, to invest back into process there. You’re gonna find it very, very, very helpful, so…
338 00:44:24.630 ⇒ 00:44:32.229 Uttam Kumaran: Also, it’s very easy to use Kurser to create tickets in linear, interact with linear. It’s very fast, so give that a shot.
339 00:44:33.130 ⇒ 00:44:39.699 Rico Rejoso: Definitely, yeah. We’re exploring and continuously ramping up with Cursor, as of now. It’s been my…
340 00:44:39.860 ⇒ 00:44:44.669 Rico Rejoso: I mean, it’s been 3 weeks since I’ve used cursor more and more, and we’re learning a lot from it.
341 00:44:44.790 ⇒ 00:44:46.819 Rico Rejoso: So we’ll continue… we’ll continue to do so.
342 00:44:50.490 ⇒ 00:44:51.000 Uttam Kumaran: Race.
343 00:44:52.460 ⇒ 00:44:53.729 Rico Rejoso: Yeah, Eliza?
344 00:44:56.130 ⇒ 00:45:07.150 Elizah Joy: Yep, on my end as well, because I’ve been… Gabe has did, he did set me up in cursor, I’m still, just like Rika, I’m still trying to,
345 00:45:07.440 ⇒ 00:45:12.629 Elizah Joy: navigate cursor, but so far, I think it’s been very, very helpful.
346 00:45:13.070 ⇒ 00:45:14.530 Elizah Joy: on my tasks.
347 00:45:16.460 ⇒ 00:45:24.109 Uttam Kumaran: Yeah, one thing that’s… one thing that’s really interesting is just to call… call Bea and ask him to… to walk you through, you know, so…
348 00:45:24.110 ⇒ 00:45:24.710 Brylle Girang: Yeah.
349 00:45:26.230 ⇒ 00:45:30.490 Brylle Girang: I have scheduled one-on-ones with Eliza and Rico, so let’s walk through Courser.
350 00:45:30.960 ⇒ 00:45:32.230 Elizah Joy: Yeah.
351 00:45:34.610 ⇒ 00:45:40.569 Brylle Girang: Okay, sorry, before I forget, Otam, one thing crossed my mind. I also think that we need to…
352 00:45:41.430 ⇒ 00:45:55.970 Brylle Girang: like, think of a way on how we can translate the GitHub PRs that we’re approving into, like, learning sessions, or maybe learning resources. I can see that we have amazing updates.
353 00:45:56.230 ⇒ 00:46:01.969 Brylle Girang: That we’re approving, but we’re… we’re… we don’t have a way, like, to share.
354 00:46:02.210 ⇒ 00:46:05.500 Brylle Girang: Those ideas, or those, you know, changes within the company?
355 00:46:05.900 ⇒ 00:46:07.150 Uttam Kumaran: Oh, for the platform?
356 00:46:07.720 ⇒ 00:46:15.789 Uttam Kumaran: Yeah, for the platform, for Cursor, the things that… Yeah, I mean, you tell… so… so you tell me what the format is, and I will help you…
357 00:46:16.120 ⇒ 00:46:18.329 Uttam Kumaran: You know, create an automation for it, so…
358 00:46:18.330 ⇒ 00:46:19.460 Brylle Girang: Yeah. Okay.
359 00:46:20.210 ⇒ 00:46:20.900 Uttam Kumaran: Yeah.
360 00:46:23.690 ⇒ 00:46:24.680 Brylle Girang: Thanks, guys!
361 00:46:24.680 ⇒ 00:46:26.450 Rico Rejoso: Okay, that’s it, thank you. Okay.
362 00:46:26.920 ⇒ 00:46:28.199 Brylle Girang: Thanks, everyone. Appreciate it.
363 00:46:28.200 ⇒ 00:46:28.880 Elizah Joy: Alright.
364 00:46:28.880 ⇒ 00:46:29.430 Uttam Kumaran: Okay.
365 00:46:29.430 ⇒ 00:46:29.870 Rico Rejoso: Have a good meal.
366 00:46:29.870 ⇒ 00:46:30.380 Elizah Joy: Thank you.
367 00:46:30.380 ⇒ 00:46:31.150 Uttam Kumaran: Bye.
368 00:46:31.780 ⇒ 00:46:32.620 Elizah Joy: Bye.