Meeting Title: Brainforge Operations Database Sync Date: 2026-01-26 Meeting participants: Sheshu Chandrasekar, Elizah Joy, Rico Rejoso, Clarence Stone
WEBVTT
1 00:02:17.410 ⇒ 00:02:21.309 Sheshu Chandrasekar: Hey, do we know if, UTom or someone’s gonna be joining?
2 00:02:27.080 ⇒ 00:02:29.980 Rico Rejoso: We can confirm on the operations channel.
3 00:02:34.130 ⇒ 00:02:34.760 Rico Rejoso: I believe…
4 00:02:34.760 ⇒ 00:02:38.579 Sheshu Chandrasekar: I don’t see in the Google Calendar that Tom said yes to this meeting.
5 00:02:39.230 ⇒ 00:02:42.909 Rico Rejoso: Yeah, I think he has a conflict with, CTA.
6 00:02:44.350 ⇒ 00:02:47.820 Rico Rejoso: Client for renewal?
7 00:02:50.030 ⇒ 00:02:52.870 Sheshu Chandrasekar: Okay, why don’t we just link him to the…
8 00:02:54.440 ⇒ 00:03:00.129 Sheshu Chandrasekar: the PowerPoint, and then we can just, like… if he doesn’t show up in the next 2 or 3 minutes, we can…
9 00:03:00.280 ⇒ 00:03:01.120 Sheshu Chandrasekar: you know.
10 00:03:01.400 ⇒ 00:03:13.719 Sheshu Chandrasekar: sync async… asynchronously… sorry, asynchronously, yeah. Also, just thinking about this right now, I’m trying to build up the databases for this Notion, now that… while I’m here.
11 00:03:14.370 ⇒ 00:03:18.770 Sheshu Chandrasekar: I’m just using Carser to build it out.
12 00:03:18.880 ⇒ 00:03:27.310 Sheshu Chandrasekar: So I’m so scared that it’s gonna mess it up, so I’m implementing a plan. Here are the to-do items. I’m gonna post this in our.
13 00:03:27.880 ⇒ 00:03:28.970 Rico Rejoso: do a chat.
14 00:03:30.590 ⇒ 00:03:37.759 Sheshu Chandrasekar: Also, I’m only… I’m not doing it to the main homepage, I’m only doing it to the, the one that you have, Eliza, the one that you drafted.
15 00:03:39.450 ⇒ 00:03:41.540 Elizah Joy: The, like, the guinea pig.
16 00:03:41.870 ⇒ 00:03:43.090 Elizah Joy: Full page.
17 00:03:43.810 ⇒ 00:03:47.100 Sheshu Chandrasekar: Yeah, the one that, the one that says draft.
18 00:03:47.600 ⇒ 00:03:48.610 Elizah Joy: Yeah.
19 00:03:48.610 ⇒ 00:03:49.230 Sheshu Chandrasekar: Yeah.
20 00:03:49.940 ⇒ 00:03:56.780 Elizah Joy: So… Like, do you have, like, the prompts that you use for Cursor for Notion?
21 00:03:56.780 ⇒ 00:04:01.549 Sheshu Chandrasekar: No, I just free flow. I just go… I just free flow it, and then see what happens.
22 00:04:02.290 ⇒ 00:04:02.940 Elizah Joy: Okay.
23 00:04:02.940 ⇒ 00:04:06.589 Sheshu Chandrasekar: And then if I don’t like the output, then I’ll kind of, like, structure it a little bit better.
24 00:04:09.610 ⇒ 00:04:11.899 Rico Rejoso: Honestly, I’m so confused on how to use cursor.
25 00:04:13.060 ⇒ 00:04:20.029 Sheshu Chandrasekar: Okay, like… Like, what’s, what’s, like, the biggest bottleneck? Like, what’s the… the problem.
26 00:04:24.320 ⇒ 00:04:25.280 Rico Rejoso: Okay…
27 00:04:35.290 ⇒ 00:04:36.100 Rico Rejoso: fields.
28 00:04:44.900 ⇒ 00:04:45.880 Rico Rejoso: Okay.
29 00:04:46.020 ⇒ 00:04:46.730 Rico Rejoso: Sure.
30 00:04:50.190 ⇒ 00:04:56.040 Sheshu Chandrasekar: Yeah, I think I don’t like… what I’m gonna do is I’m gonna say, hey, only… use,
31 00:04:57.710 ⇒ 00:04:58.930 Sheshu Chandrasekar: this structure.
32 00:05:00.250 ⇒ 00:05:02.749 Sheshu Chandrasekar: So we’re not gonna change too much of the structure right now.
33 00:06:08.230 ⇒ 00:06:12.770 Elizah Joy: I do have a question on, on here, Shoshua, if that’s okay.
34 00:06:13.000 ⇒ 00:06:14.510 Sheshu Chandrasekar: Yeah, please.
35 00:06:14.660 ⇒ 00:06:18.910 Elizah Joy: In the, like, the enhanced existing database.
36 00:06:19.520 ⇒ 00:06:23.820 Elizah Joy: Do we just… add in the Slack user ID.
37 00:06:24.400 ⇒ 00:06:25.450 Sheshu Chandrasekar: work.
38 00:06:25.560 ⇒ 00:06:27.879 Elizah Joy: Like, also refine the…
39 00:06:28.460 ⇒ 00:06:37.479 Elizah Joy: the contents inside, like, not the contents, but the structure, so that they’re all, like, the same, like, they’re uniformly created.
40 00:06:38.610 ⇒ 00:06:44.369 Sheshu Chandrasekar: Yeah, I think we add the Slack ID. I don’t even know if that’s necessary, I don’t know why Carson is saying that.
41 00:06:44.650 ⇒ 00:06:45.280 Sheshu Chandrasekar: But…
42 00:06:45.280 ⇒ 00:06:45.710 Elizah Joy: Mmm.
43 00:06:45.710 ⇒ 00:06:46.240 Rico Rejoso: Yeah.
44 00:06:47.040 ⇒ 00:06:49.289 Sheshu Chandrasekar: I mean, what we can do, what…
45 00:06:49.960 ⇒ 00:06:51.300 Elizah Joy: I’m sorry, go ahead.
46 00:06:51.670 ⇒ 00:06:53.329 Elizah Joy: Oh, sorry, go ahead.
47 00:06:53.450 ⇒ 00:07:03.619 Sheshu Chandrasekar: No, I was just gonna say, my main thing is, like, I just want to have, like, a database where we have all our documents that’s, like, kind of,
48 00:07:04.050 ⇒ 00:07:05.940 Sheshu Chandrasekar: Separated to policies.
49 00:07:06.210 ⇒ 00:07:12.920 Sheshu Chandrasekar: guides and stuff like that. That’s kind of what I’m thinking, because there are a lot of things in the existing homepage where
50 00:07:13.240 ⇒ 00:07:15.510 Sheshu Chandrasekar: There’s just, like, a lot of,
51 00:07:15.680 ⇒ 00:07:25.110 Sheshu Chandrasekar: it’s not as organized, or it’s, like, very incomplete, because there’s… I see a lot of people creating, like, a document, and then midway through, they just don’t follow up on it.
52 00:07:25.390 ⇒ 00:07:27.440 Sheshu Chandrasekar: So that’s my main thing.
53 00:07:27.830 ⇒ 00:07:35.499 Sheshu Chandrasekar: And also, like, make it quickly accessible. Like, if people need to find things, like, they can find it very easily. It’s, like, my other biggest thing.
54 00:07:37.980 ⇒ 00:07:41.590 Elizah Joy: Hey, slack use your hide.
55 00:07:42.030 ⇒ 00:07:46.900 Elizah Joy: Maybe instead of the Slack user ID, we just add their notion?
56 00:07:47.430 ⇒ 00:07:49.680 Elizah Joy: User… Or…
57 00:07:49.680 ⇒ 00:07:51.279 Sheshu Chandrasekar: Their Notion user? Yeah, that works.
58 00:07:52.390 ⇒ 00:07:55.000 Elizah Joy: What do you mean, like, for the documentation?
59 00:07:55.260 ⇒ 00:07:56.579 Rico Rejoso: database, right?
60 00:07:56.740 ⇒ 00:07:59.290 Rico Rejoso: Is this what that is for?
61 00:08:01.210 ⇒ 00:08:04.370 Sheshu Chandrasekar: This is just for, like, overall. This is for…
62 00:08:07.640 ⇒ 00:08:14.160 Sheshu Chandrasekar: Like, for example, if… Pranav, like, I’m seeing Pranav right now, right? And he created a…
63 00:08:14.160 ⇒ 00:08:14.730 Elizah Joy: Hmm.
64 00:08:15.020 ⇒ 00:08:20.100 Sheshu Chandrasekar: he created an evals document in the Brainforge HQ,
65 00:08:20.330 ⇒ 00:08:30.840 Sheshu Chandrasekar: If he created that, then he should be the owner of it. And I think we should not tag the Slack… Slack ID, you’re right, Eliza, we should just use the Notion, ID.
66 00:08:32.169 ⇒ 00:08:34.539 Sheshu Chandrasekar: To say he’s the owner. Yeah.
67 00:08:36.309 ⇒ 00:08:39.749 Elizah Joy: Okay, I think that’s feasible.
68 00:08:39.750 ⇒ 00:08:40.719 Sheshu Chandrasekar: Does that make sense, sir.
69 00:08:41.799 ⇒ 00:08:53.609 Elizah Joy: Yeah, it makes sense. And, just, another question on that, right? So, existing databases, do we also, like, because we have this, we have a lot of…
70 00:08:53.860 ⇒ 00:08:57.220 Elizah Joy: Files in the documentations.
71 00:08:57.380 ⇒ 00:09:04.110 Elizah Joy: page, right, documentations page. Do we… like…
72 00:09:04.350 ⇒ 00:09:10.430 Elizah Joy: separate those, as you mentioned earlier, like, we… Organize it for…
73 00:09:11.050 ⇒ 00:09:16.679 Elizah Joy: If it’s a policy, if it’s a guide, do we have to, like, Separate those?
74 00:09:16.820 ⇒ 00:09:22.970 Elizah Joy: Pages that we have inside our documentations, or we keep it as that, but in the same page?
75 00:09:23.410 ⇒ 00:09:24.830 Rico Rejoso: It is separated, right?
76 00:09:25.020 ⇒ 00:09:26.109 Sheshu Chandrasekar: Yeah, I think we should stop.
77 00:09:26.110 ⇒ 00:09:32.040 Rico Rejoso: We, we have, we have four, like, I mean, 4 types of, documentation.
78 00:09:32.040 ⇒ 00:09:32.520 Elizah Joy: Yeah.
79 00:09:32.520 ⇒ 00:09:34.580 Rico Rejoso: How to guides, explanation, tutorials.
80 00:09:34.580 ⇒ 00:09:35.550 Elizah Joy: Yeah.
81 00:09:35.740 ⇒ 00:09:36.439 Elizah Joy: I think that is sufficient.
82 00:09:36.440 ⇒ 00:09:38.009 Rico Rejoso: I shouldn’t know what you guys think.
83 00:09:39.020 ⇒ 00:09:45.610 Elizah Joy: Yeah, yeah, I think… Yeah, I was just…
84 00:09:45.890 ⇒ 00:09:52.069 Elizah Joy: Curious if we also want to, like, separate that per page, or…
85 00:09:53.050 ⇒ 00:09:57.050 Elizah Joy: Or should we keep it as it is? Because I think it’s… Already.
86 00:09:57.510 ⇒ 00:09:59.169 Elizah Joy: like, organize…
87 00:09:59.790 ⇒ 00:10:14.150 Rico Rejoso: It is sorted out. It is sorted out on the documentation page already. I guess that would work. Creating another page is, like, they have to click on it just to see those documentations, right, or those pages. I think this is sufficient.
88 00:10:15.020 ⇒ 00:10:18.720 Elizah Joy: Okay, like, it’s just, like, those pages are linked.
89 00:10:18.840 ⇒ 00:10:20.720 Elizah Joy: Two separate pages.
90 00:10:20.960 ⇒ 00:10:25.640 Elizah Joy: But they’re all essentially in the documentations page.
91 00:10:28.160 ⇒ 00:10:32.229 Rico Rejoso: I mean, you want to change how we view the documentation? Is…
92 00:10:33.250 ⇒ 00:10:43.569 Elizah Joy: No, I mean, we keep it as it is, and then if, like, for example, for, like, the sales page… I’m sorry, not sales page, or maybe the GDM pub, we link it, like.
93 00:10:43.750 ⇒ 00:10:45.509 Elizah Joy: The way we’ve set it up.
94 00:10:46.880 ⇒ 00:11:02.189 Rico Rejoso: Yeah, so my idea was, like, and correct me, or you can just open for suggestion, we have this on the documentation, right? So whenever we go to different department-like pages, like, say, for example, people operations and recruitments, and it is sorted out.
95 00:11:02.190 ⇒ 00:11:02.590 Elizah Joy: Yeah.
96 00:11:02.590 ⇒ 00:11:18.889 Rico Rejoso: per department. This is for HR department, there should also be one for people operations, so any documentation that the team could see, because this one right now is currently locked, and the only one that can view this page are those that are within the recruitment group.
97 00:11:21.110 ⇒ 00:11:31.099 Rico Rejoso: Right? So that’s… that’s initially what we wanted to… I mean, we wanted to provide, I mean, give access to pages for necessary individuals, right?
98 00:11:31.100 ⇒ 00:11:31.470 Elizah Joy: Yeah.
99 00:11:31.470 ⇒ 00:11:40.549 Rico Rejoso: But this one, the main page for the people operations are generally available for everyone, so I also tried to… I mean, I restructure it a bit.
100 00:11:41.220 ⇒ 00:11:54.330 Rico Rejoso: I’m done with this, you can check it out and let me know. But yes, regarding the documents, yeah, we can just create a sort or filter out per department, and just have a database per department, yeah.
101 00:11:54.880 ⇒ 00:11:58.220 Elizah Joy: Yeah, yeah, I think that sounds… Good.
102 00:11:59.340 ⇒ 00:12:04.309 Sheshu Chandrasekar: Yeah, I think my biggest thing to this team directory… oh, let me just go back real quick.
103 00:12:07.610 ⇒ 00:12:14.210 Sheshu Chandrasekar: It would be to add a… in the role. I like the title, but I think we need to define it by, like.
104 00:12:14.360 ⇒ 00:12:20.269 Sheshu Chandrasekar: we need to have a tag. Like, it needs to be EP, or a CSO, or…
105 00:12:20.460 ⇒ 00:12:24.670 Sheshu Chandrasekar: You know, like, we just need to have, like, the tags that we have in column department, department column.
106 00:12:25.160 ⇒ 00:12:32.109 Sheshu Chandrasekar: DeSo, if we were to tag someone, in the EP roles, like, it would be easier, right?
107 00:12:32.110 ⇒ 00:12:33.749 Elizah Joy: It’d be easy to just, like…
108 00:12:34.480 ⇒ 00:12:44.759 Sheshu Chandrasekar: say, okay, these are our EPs, and if someone were to add an EP to another team, that tag is already there, so they could just add them immediately and filter.
109 00:12:46.570 ⇒ 00:12:49.599 Rico Rejoso: In the role, or is that regarding access?
110 00:12:52.160 ⇒ 00:12:57.369 Sheshu Chandrasekar: Just a role. Like, I don’t think access really matters, I think everyone can see everything.
111 00:12:57.570 ⇒ 00:13:00.409 Sheshu Chandrasekar: I guess, I think Axis only…
112 00:13:00.650 ⇒ 00:13:03.810 Sheshu Chandrasekar: matters to us when we share the page, right? So…
113 00:13:05.290 ⇒ 00:13:08.860 Sheshu Chandrasekar: So maybe, like, for example,
114 00:13:09.140 ⇒ 00:13:16.260 Sheshu Chandrasekar: Pranab wouldn’t see, like, CSO or anything like that, or he wouldn’t see EPs, anything that EP sees, and that’s, like, a…
115 00:13:16.840 ⇒ 00:13:22.229 Sheshu Chandrasekar: A policy, that we had to implement regarding, like, who can see what.
116 00:13:24.700 ⇒ 00:13:27.329 Sheshu Chandrasekar: Does that make sense? I don’t know if that makes sense there.
117 00:13:27.990 ⇒ 00:13:29.470 Rico Rejoso: Yeah, yeah.
118 00:13:30.920 ⇒ 00:13:32.430 Rico Rejoso: Okay, gotcha.
119 00:13:33.220 ⇒ 00:13:39.420 Rico Rejoso: So it… I think we could just… Whoa.
120 00:13:40.590 ⇒ 00:13:52.110 Rico Rejoso: I mean, I created a role for the… I mean, the JD for the EP, SL, and CSO role. We could… I mean, necessarily should be here.
121 00:13:53.830 ⇒ 00:13:59.610 Sheshu Chandrasekar: Or why don’t we just… yeah, I mean, we can say… so you see the third column?
122 00:14:01.900 ⇒ 00:14:02.650 Rico Rejoso: Which one?
123 00:14:02.870 ⇒ 00:14:04.880 Sheshu Chandrasekar: Sorry, if you go back to the database.
124 00:14:05.640 ⇒ 00:14:06.360 Rico Rejoso: Yeah.
125 00:14:06.360 ⇒ 00:14:10.520 Sheshu Chandrasekar: The third column, we can rename… instead of that being role, we can say title.
126 00:14:11.940 ⇒ 00:14:18.649 Sheshu Chandrasekar: We could rename that to title, and then add another column and say role. And then the role, we’d have a multi-select,
127 00:14:18.890 ⇒ 00:14:25.789 Sheshu Chandrasekar: column where you can… So, like, CSO, EP, SL, go-to-market, stuff like that.
128 00:14:25.790 ⇒ 00:14:30.979 Rico Rejoso: Yeah, that was… what was I supposed, supposed to show you guys, because…
129 00:14:31.700 ⇒ 00:14:36.460 Rico Rejoso: this is, like, the position, right? We have this already, and I created the…
130 00:14:36.590 ⇒ 00:14:55.090 Rico Rejoso: This JD. Basically, this is linked to the roles and description that we have on the recruitment page. So if we add it here, it shows that you’re an AI or automation engineer, and also an engagement planner. So this is… the property title is position, we could just change it to title. What do you think?
131 00:14:56.540 ⇒ 00:14:57.790 Sheshu Chandrasekar: Yeah, that works for me.
132 00:14:57.990 ⇒ 00:14:58.839 Sheshu Chandrasekar: What do you think, Liza?
133 00:14:59.940 ⇒ 00:15:02.449 Elizah Joy: Yeah, I think that makes sense.
134 00:15:03.690 ⇒ 00:15:09.580 Rico Rejoso: Let’s say we change it that, and… It’s not yet visible.
135 00:15:18.160 ⇒ 00:15:20.110 Sheshu Chandrasekar: Oh, I see titles in the bottom.
136 00:15:21.260 ⇒ 00:15:22.270 Rico Rejoso: Yeah, I changed it.
137 00:15:23.380 ⇒ 00:15:32.229 Rico Rejoso: Yeah, no, it should be visible here, but I guess since we have… Diet, though. Okay.
138 00:16:20.130 ⇒ 00:16:21.860 Rico Rejoso: Okay, I’ll look into this.
139 00:16:22.930 ⇒ 00:16:23.530 Sheshu Chandrasekar: Okay.
140 00:16:23.670 ⇒ 00:16:30.550 Sheshu Chandrasekar: Sweet. I think we need to figure out a way to… I just realized how much of a… a big, heavy lift this is gonna be, so I’m gonna…
141 00:16:31.330 ⇒ 00:16:35.370 Sheshu Chandrasekar: I need to figure out a better way to, like, structure a database. The only reason why I’m so…
142 00:16:36.480 ⇒ 00:16:40.270 Sheshu Chandrasekar: I guess… I guess pressed, in a way, is because…
143 00:16:40.760 ⇒ 00:16:45.590 Sheshu Chandrasekar: I want to make sure the databases are correctly structured, so when we build Slackbots.
144 00:16:46.110 ⇒ 00:16:50.059 Sheshu Chandrasekar: It refers to the database and the content in it.
145 00:16:50.390 ⇒ 00:16:54.649 Sheshu Chandrasekar: So it’ll be easier for us to just deploy a Slack bot, so it wouldn’t take us forever to…
146 00:16:55.220 ⇒ 00:17:01.400 Sheshu Chandrasekar: find the content, and find where it’s living in, and then build a Slack bot. I think it’d be very easy if we just…
147 00:17:01.500 ⇒ 00:17:04.630 Sheshu Chandrasekar: give the Notion MCP and select,
148 00:17:05.250 ⇒ 00:17:10.640 Sheshu Chandrasekar: like, access, and then it… we can use Carser to build out these Slack bots and stuff like that. That’s, like, why I’m…
149 00:17:10.900 ⇒ 00:17:13.059 Sheshu Chandrasekar: Being very, careful with this.
150 00:17:15.470 ⇒ 00:17:18.630 Sheshu Chandrasekar: Yeah, so if you guys are… yeah, sorry, go ahead.
151 00:17:18.940 ⇒ 00:17:22.949 Rico Rejoso: Yeah, a few points, I think. Maybe Nick Thom just messaged the operations channel.
152 00:17:24.270 ⇒ 00:17:27.400 Rico Rejoso: He needs update on the AOR and software review.
153 00:17:30.450 ⇒ 00:17:33.310 Rico Rejoso: So, I think those are the biggest notes and updates that we should provide.
154 00:17:33.310 ⇒ 00:17:34.310 Elizah Joy: Yeah.
155 00:17:35.390 ⇒ 00:17:36.070 Elizah Joy: Significant.
156 00:17:37.970 ⇒ 00:17:42.319 Elizah Joy: Should I just send this to, like, in the ops channel, or…
157 00:17:44.780 ⇒ 00:17:45.930 Rico Rejoso: What do you have already?
158 00:17:48.790 ⇒ 00:17:54.729 Elizah Joy: For the AOR, it’s just reviewing the, like, the actual AORs.
159 00:17:54.950 ⇒ 00:18:13.000 Elizah Joy: And then, UDAM wanted, like, to have it reviewed for, like, at the end of the month, every month, so having that included in the system. And then for the software review, we already have the, like, the…
160 00:18:14.470 ⇒ 00:18:22.289 Elizah Joy: review for the softwares that we have. It’s just renegotiating… renegotiating the contracts.
161 00:18:22.470 ⇒ 00:18:31.580 Elizah Joy: And then… Appreciate it, because we have the LinkedIn, like, the sales navigator by the end of this?
162 00:18:31.940 ⇒ 00:18:45.910 Elizah Joy: a month, so January 30th, so that one needs for negotiating into team, and then instead, we only need to cancel one, so that’s Zapier, one tool, and then the others would be moved into
163 00:18:45.920 ⇒ 00:18:53.639 Elizah Joy: like, the most essential tools that we have, like, Gmail, as what Una mentioned, and the operations channel.
164 00:18:53.670 ⇒ 00:18:59.450 Elizah Joy: Is that moving those into… from month… on a monthly payment basis to…
165 00:18:59.520 ⇒ 00:19:09.779 Elizah Joy: be through an annual one. The only thing I was thinking about that is, remember when we showed, like, the numbers to the financing?
166 00:19:10.200 ⇒ 00:19:18.900 Elizah Joy: like, this… They’re… like, they… Did not recommend, like, having those in an ag ball.
167 00:19:19.060 ⇒ 00:19:21.930 Elizah Joy: Payment plan, because it makes…
168 00:19:22.290 ⇒ 00:19:34.809 Elizah Joy: how can I say? It’s, like, more expensive in their opinion, but of course, Udom, it’s, still gonna be the one doing those, review for softwares. And then…
169 00:19:34.990 ⇒ 00:19:38.590 Elizah Joy: The only thing is the dashboard for Omni.
170 00:19:39.500 ⇒ 00:19:41.269 Elizah Joy: for the software.
171 00:19:41.970 ⇒ 00:19:56.670 Rico Rejoso: Yeah, let’s just first set out an update, like, a list of tools that we can, we suggest we can cancel or, you know, downgrade, and a list of tools that we can,
172 00:19:56.670 ⇒ 00:20:04.160 Rico Rejoso: upgrade to an annual payment. Some of it will be, like, Google, figma… Oh.
173 00:20:04.160 ⇒ 00:20:05.180 Elizah Joy: Yeah.
174 00:20:05.180 ⇒ 00:20:10.510 Rico Rejoso: 1Password, just those few suggestions, and we can let UTOM decide a po…
175 00:20:10.590 ⇒ 00:20:12.300 Elizah Joy: Afterwards, okay?
176 00:20:12.430 ⇒ 00:20:23.539 Rico Rejoso: We just need to provide an update on where we’re at and what list do we have right now, and also present or let them know about the conflict, that the finance team pres… I mean, mentioned, which is…
177 00:20:24.550 ⇒ 00:20:30.199 Rico Rejoso: Right, if we’re paying for month-to-month per usage for a specific tool.
178 00:20:30.560 ⇒ 00:20:31.989 Elizah Joy: That would be in the car.
179 00:20:31.990 ⇒ 00:20:43.549 Rico Rejoso: And plus the cost, if we can afford to pay a one-time payment for an annual, right? Or if not, we can just stick with monthly, right?
180 00:20:44.060 ⇒ 00:20:54.610 Rico Rejoso: We just let them know about it, and let him make the decision. For the AOR, I think we’re good with it, right? Let’s just… let’s just inform… move them that we’re good with it, and it’s a poor review.
181 00:20:54.610 ⇒ 00:20:57.330 Elizah Joy: in, for the AOL…
182 00:20:57.330 ⇒ 00:21:01.479 Rico Rejoso: pertaining to the operations AOR, or the whole company AOR?
183 00:21:01.890 ⇒ 00:21:04.369 Elizah Joy: The whole thing.
184 00:21:04.990 ⇒ 00:21:06.860 Elizah Joy: Okay, let me share.
185 00:21:12.410 ⇒ 00:21:18.450 Elizah Joy: with the, AOR that we have, he wants to have, like,
186 00:21:18.640 ⇒ 00:21:25.410 Elizah Joy: So this one will be updated, every end of the month. When we have the AOR review, he wants to have that
187 00:21:25.460 ⇒ 00:21:36.940 Elizah Joy: added in, like, the, internal review cycle. So that’s that. So this will be updated. So this is still based on the last quarter of last year.
188 00:21:36.940 ⇒ 00:21:49.300 Elizah Joy: And then, essentially, with the AORs that we have here, he wanted the finance one to be added in here, so I added that one. And basically having these owners for each
189 00:21:49.390 ⇒ 00:21:52.550 Elizah Joy: A water.
190 00:21:54.320 ⇒ 00:22:02.720 Elizah Joy: For those. So yeah, it’s now, up for review. Then this one needs updating for the end of this month.
191 00:22:04.290 ⇒ 00:22:10.420 Rico Rejoso: Okay, so we could just, let him know that the descriptions are done, and we just need to update the status.
192 00:22:11.150 ⇒ 00:22:12.919 Elizah Joy: Mmm, okay. Yep.
193 00:22:13.910 ⇒ 00:22:14.400 Rico Rejoso: Alright.
194 00:22:14.400 ⇒ 00:22:22.200 Elizah Joy: Yep, and I do have this, month, the internal review cycle that we do for this, so it’s gonna be a monthly one.
195 00:22:22.970 ⇒ 00:22:27.650 Elizah Joy: So that we have, like, the team leads and the CRI.
196 00:22:27.800 ⇒ 00:22:28.440 Elizah Joy: having the.
197 00:22:28.440 ⇒ 00:22:34.590 Rico Rejoso: When this should be discussed… should it be discussed after the end of month, or… By enrollment.
198 00:22:35.490 ⇒ 00:22:45.100 Elizah Joy: By end of month, and then we review, like… like, that’s the cycle that we’re gonna be doing. So every end of month, so that we have that updated.
199 00:22:45.860 ⇒ 00:22:46.770 Rico Rejoso: Alright.
200 00:22:47.310 ⇒ 00:22:53.959 Elizah Joy: Yeah, so that they are up to date. Because the ones that we have, like, when he’s given this to me.
201 00:22:54.260 ⇒ 00:22:57.370 Elizah Joy: think the, DRIs are not updated.
202 00:22:57.590 ⇒ 00:23:00.190 Elizah Joy: So, yeah, I’ve got those updated.
203 00:23:00.860 ⇒ 00:23:06.529 Elizah Joy: Yep, so for the AOR, it’s just, reviewing that with the team leads.
204 00:23:06.660 ⇒ 00:23:13.059 Elizah Joy: And then software is canceling and renegotiating, and then decision from monthly to annual.
205 00:23:13.650 ⇒ 00:23:22.500 Elizah Joy: And then… The Omni dashboard, I think they’ll… be really… Helpful to see.
206 00:23:22.620 ⇒ 00:23:28.839 Elizah Joy: where we’re currently at with this software. And just a question on that, Shashu, do we want to have, like.
207 00:23:29.440 ⇒ 00:23:37.340 Elizah Joy: the action… not just the software expenses in the… in Omni, but also the… Other expenses that we have.
208 00:23:37.960 ⇒ 00:23:40.290 Sheshu Chandrasekar: Yeah, I think we should combine both.
209 00:23:40.990 ⇒ 00:23:41.530 Elizah Joy: Okay.
210 00:23:44.360 ⇒ 00:23:47.349 Elizah Joy: Okay, so yeah, I’ll always send this update to Wufong.
211 00:23:48.760 ⇒ 00:23:50.829 Elizah Joy: for software and AOR.
212 00:23:51.450 ⇒ 00:23:52.070 Rico Rejoso: Okay.
213 00:23:53.220 ⇒ 00:23:58.389 Rico Rejoso: And for the expense form, is there… I mean, how are we on that?
214 00:23:59.820 ⇒ 00:24:03.180 Elizah Joy: This expense form is still in Notion.
215 00:24:04.680 ⇒ 00:24:08.230 Elizah Joy: keep that in there, then we send it in Slack.
216 00:24:11.780 ⇒ 00:24:17.559 Rico Rejoso: Okay, is there any steps we need to take to update those, or what else?
217 00:24:18.670 ⇒ 00:24:22.600 Elizah Joy: Just those, the only thing on my end is…
218 00:24:24.040 ⇒ 00:24:31.810 Elizah Joy: like, with the… if we just send the link on, like, Slack, right? So it might get… like.
219 00:24:32.790 ⇒ 00:24:39.800 Elizah Joy: People might find it hard to find the link for the, expense review or approval?
220 00:24:40.140 ⇒ 00:24:46.990 Elizah Joy: So is it… I was thinking if it’s better if it just… if we have that in linear. But the thing is…
221 00:24:47.430 ⇒ 00:24:52.900 Elizah Joy: In linear, we don’t get to, like, actually see the review.
222 00:24:53.870 ⇒ 00:25:01.009 Sheshu Chandrasekar: Right, so you’re saying, like, how do we… so how do we see, if an expense has been entered in? Is that what you’re saying?
223 00:25:01.820 ⇒ 00:25:06.900 Elizah Joy: Yeah, and we keep that in our database, and then accessible for Smell…
224 00:25:07.660 ⇒ 00:25:11.180 Sheshu Chandrasekar: No, that makes a lot of sense. So, I was thinking this, right? I was thinking…
225 00:25:11.400 ⇒ 00:25:17.909 Sheshu Chandrasekar: Right now, it could be a simple form on Notion, and then once… It’s been submitted.
226 00:25:18.090 ⇒ 00:25:21.419 Sheshu Chandrasekar: It gets, captured in a Google spreadsheet.
227 00:25:22.080 ⇒ 00:25:25.429 Sheshu Chandrasekar: And we just check it every day to see, okay, like.
228 00:25:25.560 ⇒ 00:25:29.930 Sheshu Chandrasekar: These are the following expenses that we have. We’re tracking And then…
229 00:25:30.040 ⇒ 00:25:35.510 Sheshu Chandrasekar: Eventually, once we get Omni running, we can see that expense being inbound. And then, we just need to figure out a way.
230 00:25:35.510 ⇒ 00:25:36.030 Elizah Joy: Which is…
231 00:25:36.030 ⇒ 00:25:40.179 Sheshu Chandrasekar: Say, like, this expense has been approved, so the person that submitted that expense can
232 00:25:40.310 ⇒ 00:25:43.529 Sheshu Chandrasekar: will know, right? So, that’s, like, the biggest thing right now.
233 00:25:43.940 ⇒ 00:25:47.940 Elizah Joy: Yeah, because this is the current form that we have, like, in Notion.
234 00:25:48.620 ⇒ 00:25:56.950 Elizah Joy: But yeah, I think, I like your recommendation, and that’s just… because I also want to be… like, sorry, go ahead, Rico.
235 00:25:56.950 ⇒ 00:25:58.960 Rico Rejoso: I mean, yeah, go ahead. Yeah, I was thinking out loud.
236 00:25:59.720 ⇒ 00:26:09.949 Elizah Joy: Yeah, just that on my end, because I wanted to make it accessible for the team as well, because we’ve already mentioned this to them, like, last Friday during our Friday retro.
237 00:26:11.780 ⇒ 00:26:24.219 Rico Rejoso: I mean, for the meantime, what we can do is automate it, and just whenever someone submitted a form, we can have a Slack notification in the ops channel, just to inform that, I mean, that a form has been submitted.
238 00:26:24.530 ⇒ 00:26:28.729 Rico Rejoso: And… Because there are two ways. One would be the
239 00:26:29.320 ⇒ 00:26:35.930 Rico Rejoso: form updates or workflow, anything like that on Notion, and one would be truly in your ass, so we can track.
240 00:26:36.790 ⇒ 00:26:37.350 Rico Rejoso: Fuck.
241 00:26:37.460 ⇒ 00:26:41.329 Rico Rejoso: prior… I mean, our prior conversation was how we can,
242 00:26:41.460 ⇒ 00:26:45.880 Rico Rejoso: How can we, like, link the form to create.
243 00:26:45.880 ⇒ 00:26:46.330 Elizah Joy: or…
244 00:26:46.330 ⇒ 00:27:00.830 Rico Rejoso: pre-order ticket on linear ops, right? So whenever a form is created, a Slack channel, a Slack notification, a Slack would be… a Slack notification would be on the ops channel, and a linear would be… a ticket would be created on linear.
245 00:27:01.020 ⇒ 00:27:08.130 Rico Rejoso: Right? So that’s initially what we discussed and how that should go. So, let me take a look at it. I can…
246 00:27:08.660 ⇒ 00:27:14.270 Rico Rejoso: let me see how I can help you out on that. But yeah, it’s good… I think it’s better if we have
247 00:27:14.760 ⇒ 00:27:18.910 Rico Rejoso: the database and… Notion, since we have everything there.
248 00:27:18.910 ⇒ 00:27:19.850 Elizah Joy: Mmm.
249 00:27:19.850 ⇒ 00:27:23.609 Rico Rejoso: promote the use of information rather than other Google Workspace tools.
250 00:27:24.530 ⇒ 00:27:39.190 Elizah Joy: Okay, yeah, because, I think it’s also, like, what you’ve mentioned, Rico, is that, like, with all these expenses, because expense for us from the team, we have to keep track of it, like, so yeah, I think Notion is…
251 00:27:39.330 ⇒ 00:27:40.550 Elizah Joy: Yeah, good for that.
252 00:27:41.120 ⇒ 00:27:50.189 Sheshu Chandrasekar: Wait, but quick question here. Can we use Notion to export that into Google Sheets? Because, ultimately, we want to move this to Omni, right? So…
253 00:27:51.050 ⇒ 00:27:56.470 Sheshu Chandrasekar: There’s a provision for us to export that database from Notion into Google Sheets.
254 00:27:57.200 ⇒ 00:27:58.309 Sheshu Chandrasekar: Is that correct?
255 00:27:59.650 ⇒ 00:28:01.779 Elizah Joy: Mmm, let me just see…
256 00:28:04.800 ⇒ 00:28:05.690 Sheshu Chandrasekar: Because I…
257 00:28:06.560 ⇒ 00:28:08.469 Rico Rejoso: I haven’t tried it.
258 00:28:08.470 ⇒ 00:28:15.539 Sheshu Chandrasekar: Yeah, no, exactly. That was my biggest concern, because I was definitely on the same page as you, Rico. I wanted to put this.
259 00:28:15.540 ⇒ 00:28:16.220 Elizah Joy: Hmm.
260 00:28:16.600 ⇒ 00:28:17.600 Sheshu Chandrasekar: in Notion.
261 00:28:17.780 ⇒ 00:28:25.520 Sheshu Chandrasekar: But then, when we need to do, like, you know, quarterly expense reviews and stuff like that, and we’re at some point gonna migrate to Omni.
262 00:28:25.910 ⇒ 00:28:30.729 Sheshu Chandrasekar: I don’t know if that would make best sense for us to use Notion,
263 00:28:31.450 ⇒ 00:28:36.549 Sheshu Chandrasekar: But also, at the same time… also at the same time, you’re… you do bring a valid point that…
264 00:28:36.940 ⇒ 00:28:38.499 Sheshu Chandrasekar: How are we gonna…
265 00:28:39.360 ⇒ 00:28:48.749 Sheshu Chandrasekar: like, route the data that, this person uses to form, and then how does it get to Google Sheets? Like, how does that… that workflow work? So that’s something we need to think about.
266 00:28:48.750 ⇒ 00:28:49.780 Elizah Joy: anymore.
267 00:28:50.080 ⇒ 00:28:50.790 Rico Rejoso: Hmm.
268 00:28:50.790 ⇒ 00:28:53.730 Elizah Joy: Yeah, in Notion, we can,
269 00:28:53.930 ⇒ 00:29:12.090 Elizah Joy: Because, yeah, in Notion, we can download the CSV file, and then we can update that. Like, I mean, not update, but add into an Excel sheet, if that’s one… if that’s what we want, so that it’s connected to, Omni, but I think it’s gonna be manual.
270 00:29:12.090 ⇒ 00:29:21.799 Rico Rejoso: What Sheshu wanted is, like, a live page, a live page and spreadsheet, right? So whenever a form is submitted during Notion, it should also appear in Spreadsheet, something like that, right? Sheshu?
271 00:29:22.090 ⇒ 00:29:23.190 Sheshu Chandrasekar: Yeah, that’s correct.
272 00:29:24.170 ⇒ 00:29:29.580 Sheshu Chandrasekar: But, I mean… I mean, if we need to do something right now, I’m okay with
273 00:29:29.690 ⇒ 00:29:36.270 Sheshu Chandrasekar: having this form builder, and all the expenses get tracked on Notion Database.
274 00:29:36.700 ⇒ 00:29:39.770 Sheshu Chandrasekar: For now, and then we just need to figure out a way to, like.
275 00:29:40.020 ⇒ 00:29:45.890 Sheshu Chandrasekar: make sure that data gets captured. Because, I mean, obviously, let’s just build something right now, show that we have it.
276 00:29:46.750 ⇒ 00:29:51.249 Sheshu Chandrasekar: I know Utam mentioned that last… last week on Friday, so let’s just have something out there.
277 00:29:51.420 ⇒ 00:29:54.630 Sheshu Chandrasekar: And then we can figure out how to, like, automate that data flow.
278 00:29:55.250 ⇒ 00:29:55.790 Sheshu Chandrasekar: For us.
279 00:29:56.820 ⇒ 00:30:02.940 Sheshu Chandrasekar: Because eventually, like, we do want to use Omni, right? Like, that’s, like, kind of the end goal. Like, we want to track every single expense.
280 00:30:03.070 ⇒ 00:30:09.280 Sheshu Chandrasekar: on OPNI, so… we want to make sure that everything that’s on Omni’s live data,
281 00:30:09.530 ⇒ 00:30:11.630 Sheshu Chandrasekar: That would make it very easy for us.
282 00:30:11.840 ⇒ 00:30:14.190 Sheshu Chandrasekar: So we just go in and check it out, so…
283 00:30:14.390 ⇒ 00:30:16.080 Sheshu Chandrasekar: It’s kind of where I’m thinking right now.
284 00:30:17.670 ⇒ 00:30:19.819 Rico Rejoso: Okay, so I think it’s a later problem.
285 00:30:20.460 ⇒ 00:30:26.899 Sheshu Chandrasekar: Definitely, definitely a later problem. Let’s just build this out, let’s just roll it, roll this expense, Notion database, and then…
286 00:30:26.900 ⇒ 00:30:27.740 Elizah Joy: Hmm.
287 00:30:27.740 ⇒ 00:30:30.350 Sheshu Chandrasekar: We can figure out how to automate that entire process later.
288 00:30:30.350 ⇒ 00:30:31.120 Elizah Joy: Okay.
289 00:30:31.680 ⇒ 00:30:39.959 Rico Rejoso: I can help out on this one, on the notification, and Elijah, I think we just need to post this on the Brainforge team channel, to let.
290 00:30:39.960 ⇒ 00:30:40.400 Elizah Joy: Everyone knows.
291 00:30:40.670 ⇒ 00:30:48.570 Rico Rejoso: That we have this kind of form that they can fill out whenever there’s an expense, instead of them emailing it or sending an email to them or the finance team.
292 00:30:48.570 ⇒ 00:30:48.920 Elizah Joy: Hmm.
293 00:30:48.920 ⇒ 00:30:51.869 Rico Rejoso: There’s a way for us to also track it is through this, right?
294 00:30:52.570 ⇒ 00:30:56.310 Elizah Joy: Okay. Yep, I’ll send that in Slab.
295 00:30:56.310 ⇒ 00:31:06.909 Sheshu Chandrasekar: And I’ll add this form to the People Ops, because ideally, what I wanted is the People Operations, like, a go-to place for new individuals that contains all the policies, and.
296 00:31:07.330 ⇒ 00:31:16.669 Rico Rejoso: I mean, policies for new hires, right? How to access this, how to work on this, what’s our, working regimen here in Brainforge, and everything, so I just wanted…
297 00:31:17.060 ⇒ 00:31:20.179 Rico Rejoso: that page to be like that. So I add this one.
298 00:31:20.670 ⇒ 00:31:24.599 Rico Rejoso: There, so they can access it, or they can easily access it, if in case.
299 00:31:25.270 ⇒ 00:31:26.540 Elizah Joy: Okay.
300 00:31:27.230 ⇒ 00:31:33.000 Sheshu Chandrasekar: Yeah, that works. And then, let’s just slowly build out the databases in the new homepage.
301 00:31:33.320 ⇒ 00:31:36.070 Sheshu Chandrasekar: So we can just migrate it over, and then…
302 00:31:36.250 ⇒ 00:31:44.460 Sheshu Chandrasekar: Ultimately, the main reason we want to build this homepage is because we just need databases, so let’s start creating that a little bit better.
303 00:31:45.000 ⇒ 00:31:57.670 Sheshu Chandrasekar: I know it’s very open-ended right now, so I’m gonna take some time this afternoon to kind of, like, structure out the databases, like, map out the database that we want to build, and build out all those key fields as well.
304 00:31:58.270 ⇒ 00:32:02.019 Sheshu Chandrasekar: And then tomorrow, we can start building and migrating whatever can.
305 00:32:02.610 ⇒ 00:32:03.120 Rico Rejoso: The database?
306 00:32:03.120 ⇒ 00:32:03.520 Elizah Joy: Okay.
307 00:32:03.520 ⇒ 00:32:07.140 Rico Rejoso: we are on the left navigation, these are all finalized, right? Or…
308 00:32:07.330 ⇒ 00:32:09.040 Rico Rejoso: Are we still gonna change the.
309 00:32:09.040 ⇒ 00:32:16.930 Elizah Joy: these, I did get these from… these are the active databases that we have in Notion.
310 00:32:17.220 ⇒ 00:32:18.580 Elizah Joy: So…
311 00:32:18.790 ⇒ 00:32:26.390 Elizah Joy: I’m not sure if we want to keep or remove some of them, or maybe consolidate some of the database that we have.
312 00:32:28.190 ⇒ 00:32:31.009 Sheshu Chandrasekar: I think consolidating would be a smarter move here.
313 00:32:31.010 ⇒ 00:32:31.350 Elizah Joy: Hmm.
314 00:32:31.350 ⇒ 00:32:34.940 Sheshu Chandrasekar: I feel like we don’t need to be as granular, we just need to be.
315 00:32:34.940 ⇒ 00:32:35.820 Elizah Joy: Hmm.
316 00:32:36.060 ⇒ 00:32:41.120 Sheshu Chandrasekar: We need to have high level, and then whoever needs to access it can use filters to get what they need.
317 00:32:43.280 ⇒ 00:32:43.850 Elizah Joy: It’s kind of.
318 00:32:43.850 ⇒ 00:32:46.510 Sheshu Chandrasekar: like, my thinking, but I’m open to different ideas.
319 00:32:47.040 ⇒ 00:32:51.500 Rico Rejoso: Yeah, I agree, because there’s, like, pages here that are within the other pages.
320 00:32:52.160 ⇒ 00:32:53.760 Elizah Joy: Yeah.
321 00:32:54.400 ⇒ 00:32:56.380 Rico Rejoso: I think we can discuss all that, yeah. Yeah.
322 00:32:58.120 ⇒ 00:32:58.820 Elizah Joy: Okay.
323 00:32:59.810 ⇒ 00:33:12.679 Rico Rejoso: Okay, yeah, a few next steps is to, provide Utem with the updates that he requested, software and AOR, and also forward the slides to the operation channel, so Utem can also take a look at.
324 00:33:12.680 ⇒ 00:33:13.450 Elizah Joy: Hmm.
325 00:33:13.450 ⇒ 00:33:14.759 Rico Rejoso: What we’re doing right now, okay?
326 00:33:15.460 ⇒ 00:33:27.300 Sheshu Chandrasekar: Yeah. Yeah, and then one last, one last thing here. So I know he’s saying we need to review the AOR and software review. Can you… is that the software review expenses, or is that, like, something completely different?
327 00:33:27.960 ⇒ 00:33:34.189 Elizah Joy: It’s what we call the project that we have, like, reviewing the softwares.
328 00:33:34.760 ⇒ 00:33:37.020 Sheshu Chandrasekar: Oh, got it, like, seeing the usage and stuff?
329 00:33:37.540 ⇒ 00:33:38.600 Elizah Joy: Yeah.
330 00:33:38.600 ⇒ 00:33:41.210 Sheshu Chandrasekar: Gotcha. Okay. That’s…
331 00:33:41.210 ⇒ 00:33:43.739 Elizah Joy: Yeah, because 4 on the AO…
332 00:33:44.020 ⇒ 00:33:57.180 Elizah Joy: for the AOR is that we only need the confirmation, the AOR doc confirmation, so aligning the AORs that we have to the right owner, and then making sure that it’s
333 00:33:57.890 ⇒ 00:34:01.540 Elizah Joy: Still, like, relevant to this quarters.
334 00:34:01.670 ⇒ 00:34:02.810 Elizah Joy: Goals.
335 00:34:04.350 ⇒ 00:34:04.690 Sheshu Chandrasekar: Got it.
336 00:34:04.690 ⇒ 00:34:08.809 Elizah Joy: I think one thing, Cheshu, for you, I think this’ll be…
337 00:34:09.380 ⇒ 00:34:16.939 Elizah Joy: helpful. This is where we initially kept all, like, when we were planning for… Let me just…
338 00:34:19.010 ⇒ 00:34:24.050 Elizah Joy: Okay, this one, when we were initially planning for, like, this was December of last year.
339 00:34:25.090 ⇒ 00:34:29.350 Elizah Joy: Yeah, I think Utam also has notes in here.
340 00:34:29.699 ⇒ 00:34:33.640 Elizah Joy: So maybe, just those.
341 00:34:34.100 ⇒ 00:34:35.850 Sheshu Chandrasekar: So I just want to show you that.
342 00:34:36.830 ⇒ 00:34:43.289 Elizah Joy: Yeah, we keep all the projects and the timeline here in the Instagant for Gantt chart.
343 00:34:43.469 ⇒ 00:34:51.030 Elizah Joy: So, high priority, and we also have one low priority, but these are for, like, February and…
344 00:34:51.480 ⇒ 00:34:54.760 Elizah Joy: March projects, or even earlier than that.
345 00:34:55.540 ⇒ 00:34:57.070 Sheshu Chandrasekar: Gotcha. Okay.
346 00:34:57.330 ⇒ 00:34:58.439 Sheshu Chandrasekar: That makes sense.
347 00:35:01.470 ⇒ 00:35:11.959 Sheshu Chandrasekar: So, I guess one last question here. For the expenses, do we have, like, a policy on how to submit expenses, like, not the software expenses, but, like, general expenses?
348 00:35:12.790 ⇒ 00:35:16.729 Elizah Joy: They’re actually all in one pitch now.
349 00:35:17.550 ⇒ 00:35:27.510 Elizah Joy: Okay. This form that we have, that, like, it has this section for if it’s a software, if it’s a tool, software, if it’s a tool, or if it’s an equipment.
350 00:35:34.260 ⇒ 00:35:35.850 Sheshu Chandrasekar: Sorry, can you repeat that last part again?
351 00:35:36.280 ⇒ 00:35:43.020 Elizah Joy: Okay, so yeah, so the form that we currently have is their consolidated by, like.
352 00:35:43.390 ⇒ 00:35:45.100 Elizah Joy: Oh, so it doesn’t matter.
353 00:35:45.100 ⇒ 00:35:46.179 Sheshu Chandrasekar: Gotcha, so it doesn’t even…
354 00:35:46.180 ⇒ 00:35:49.600 Elizah Joy: No matter if it’s equipment, or food, or lodging. Yeah. Okay.
355 00:35:49.780 ⇒ 00:35:54.020 Elizah Joy: At the moment, we have travel, equipment.
356 00:35:54.660 ⇒ 00:35:58.649 Elizah Joy: softwares, and I think we have others as well in there.
357 00:35:59.150 ⇒ 00:36:00.710 Sheshu Chandrasekar: Okay. Okay. Sweet.
358 00:36:00.710 ⇒ 00:36:11.320 Rico Rejoso: We also get, like, a confirmation or a guide. Like, for example, I think what I mentioned before, like, he wanted to have, like, a certain price range. If that’s within budget, we can just…
359 00:36:12.000 ⇒ 00:36:17.319 Rico Rejoso: approve it immediately. If not, they’re gonna be up to discussion per week during this.
360 00:36:17.320 ⇒ 00:36:17.870 Elizah Joy: Hmm…
361 00:36:17.870 ⇒ 00:36:23.180 Rico Rejoso: kind of meeting? Is there, like, a policy or an SOP on how that dot ghosts.
362 00:36:24.130 ⇒ 00:36:30.400 Elizah Joy: At the moment, we have the only one for equipment.
363 00:36:30.430 ⇒ 00:36:47.439 Elizah Joy: So for the equipments, let me… I think this is the old one. So for equipments, because I remember, like, Zoran asking for, like, a keyboard, like, initially, initially… we initially wanted to give him, like, a webcam, and our price range for that is a hundred…
364 00:36:47.540 ⇒ 00:36:56.359 Elizah Joy: And then he also requested for a keyboard, but I think that price range was above what we wanted.
365 00:36:56.630 ⇒ 00:36:57.780 Elizah Joy: So…
366 00:36:57.920 ⇒ 00:37:05.539 Elizah Joy: Yeah, but just at the moment, we only have one for expense… For… not for expenses, but for equipment.
367 00:37:05.810 ⇒ 00:37:07.710 Elizah Joy: There’s a policy on that.
368 00:37:08.610 ⇒ 00:37:12.700 Elizah Joy: Because we do have a budget on that, like, $100?
369 00:37:12.800 ⇒ 00:37:17.729 Elizah Joy: But for monitors, for people asking for monitors, we do higher than that.
370 00:37:19.220 ⇒ 00:37:21.339 Rico Rejoso: Okay, so I think we have to cover.
371 00:37:21.340 ⇒ 00:37:24.000 Sheshu Chandrasekar: So it’s only for equipment and software at the moment.
372 00:37:24.690 ⇒ 00:37:25.150 Elizah Joy: It just…
373 00:37:25.150 ⇒ 00:37:30.829 Rico Rejoso: for equipments. For software, do we have, like, a price range? Is it the same $100 for it?
374 00:37:31.770 ⇒ 00:37:38.350 Elizah Joy: Not at the moment. We don’t have the price range for that. We haven’t discussed the price.
375 00:37:38.610 ⇒ 00:37:44.980 Elizah Joy: on that yet. I think because the only person that asked for a software was Luke.
376 00:37:45.280 ⇒ 00:37:55.670 Elizah Joy: And then we were trying to add… the challenge with the adding loop to the Sales Navigator was, on UTAM’s account, he cannot add in more…
377 00:37:55.840 ⇒ 00:38:06.310 Elizah Joy: team members, or he cannot buy it for other team members. It’s the same with Robert. And then, the thing with that, that’s why we have to renegotiate with,
378 00:38:06.900 ⇒ 00:38:17.529 Elizah Joy: the contract or the plan for the sales navigator was that Robert has his, and then Utam has his. I’m not sure who the other team member
379 00:38:17.740 ⇒ 00:38:29.080 Elizah Joy: as, like, we have, like, 3 or 4 accounts for that at the moment. We should be having 4, but, at the moment, Luke was using Roberts, because Roberts
380 00:38:29.420 ⇒ 00:38:31.700 Elizah Joy: Plan is about to expire.
381 00:38:32.010 ⇒ 00:38:48.950 Elizah Joy: by the end of this month, and by the end of this month, Robert will be canceling his, Sales Navigator subscription, and we will be trying to get into a team subscription, or team plan for Sales Navigator, so that we have, like, lower…
382 00:38:49.240 ⇒ 00:38:53.239 Elizah Joy: Or we have discounted price for Sales Navigator.
383 00:38:55.640 ⇒ 00:38:56.450 Sheshu Chandrasekar: Got it.
384 00:38:56.940 ⇒ 00:38:57.590 Rico Rejoso: Okay.
385 00:38:58.950 ⇒ 00:39:06.810 Elizah Joy: Yeah, so at the moment, we have the one for equipments. For softwares, we don’t have those one yet.
386 00:39:07.490 ⇒ 00:39:11.180 Rico Rejoso: So, maybe one, another few steps is to confirm
387 00:39:11.540 ⇒ 00:39:17.060 Rico Rejoso: Regarding the budget that we have for software, and consolidate the.
388 00:39:17.060 ⇒ 00:39:17.439 Elizah Joy: mess with me.
389 00:39:17.440 ⇒ 00:39:20.460 Rico Rejoso: That we have for tools and equipment and software tools.
390 00:39:20.610 ⇒ 00:39:30.600 Rico Rejoso: So that… I mean, I think the main goal is to not have UTM loop into this, to such process and task.
391 00:39:31.030 ⇒ 00:39:37.050 Rico Rejoso: If we can get confirmation regarding to the budget of the software tools that we can approve.
392 00:39:37.240 ⇒ 00:39:46.760 Rico Rejoso: immediately, and we can go for that. I mean, we can stick with it, and every time there’s new requests, we can just go and process it ourselves.
393 00:39:47.690 ⇒ 00:39:48.400 Elizah Joy: Okay.
394 00:39:49.790 ⇒ 00:39:50.640 Elizah Joy: Okay.
395 00:39:53.550 ⇒ 00:39:55.890 Rico Rejoso: Alright, anything else?
396 00:39:57.960 ⇒ 00:40:03.380 Sheshu Chandrasekar: Nothing on my end. I’m gonna map out this database, get you guys… get it to you guys, and then…
397 00:40:03.380 ⇒ 00:40:03.960 Rico Rejoso: Okay.
398 00:40:04.480 ⇒ 00:40:09.489 Sheshu Chandrasekar: Yeah, and then also I’ll look into the Omni stuff, and…
399 00:40:10.230 ⇒ 00:40:17.979 Sheshu Chandrasekar: figure out exactly how we want to track all that expenses when someone submits it. So, that’s something I’ll work on on my end.
400 00:40:18.880 ⇒ 00:40:25.280 Sheshu Chandrasekar: But if there’s any suggestions, I really would like to make some headway today on that notion, so if there’s anything that…
401 00:40:25.390 ⇒ 00:40:31.050 Sheshu Chandrasekar: Pops up, like, a question, concern, just let me know, and then we can go about it.
402 00:40:32.810 ⇒ 00:40:37.950 Rico Rejoso: I guess we’re just gonna wait for the results of what you’re doing, and provide a feedback after.
403 00:40:37.950 ⇒ 00:40:39.000 Sheshu Chandrasekar: Yeah, absolutely.
404 00:40:39.750 ⇒ 00:40:46.710 Rico Rejoso: Yeah, Eliza, I’m gonna help you out on the expense form. Where’s that located? Is that on the operations or the documentation?
405 00:40:47.240 ⇒ 00:40:49.550 Elizah Joy: It’s under… Sweet.
406 00:40:49.770 ⇒ 00:40:56.930 Elizah Joy: Documentations, and then… Expense request. I’ll send it to you aunts.
407 00:40:58.280 ⇒ 00:40:58.930 Rico Rejoso: Alright.
408 00:40:59.760 ⇒ 00:41:05.660 Elizah Joy: Yeah, also, I think, Robert has, like, an equip… he wanted to request for a new
409 00:41:05.940 ⇒ 00:41:11.350 Elizah Joy: Device, new computer, actually. So, but he hasn’t filled that one out yet.
410 00:41:11.930 ⇒ 00:41:15.310 Rico Rejoso: No worries, I think that’s the reason why Utham wanted us to,
411 00:41:15.710 ⇒ 00:41:18.430 Rico Rejoso: Email or keep in contact with Upgrade Team.
412 00:41:20.040 ⇒ 00:41:24.940 Rico Rejoso: No one he mentioned earlier, because we can distribute equipments and tools with their help.
413 00:41:25.400 ⇒ 00:41:25.880 Rico Rejoso: And I…
414 00:41:25.880 ⇒ 00:41:26.710 Elizah Joy: Okay.
415 00:41:26.710 ⇒ 00:41:31.209 Rico Rejoso: They’re offering that kind of services yet. I haven’t looked into that email.
416 00:41:32.570 ⇒ 00:41:36.750 Elizah Joy: Okay, I think… I don’t think I’m in that thread, right?
417 00:41:37.040 ⇒ 00:41:42.569 Elizah Joy: So yeah, I’ll just… Yeah, I don’t think I’m in that thread yet.
418 00:41:42.570 ⇒ 00:41:47.300 Rico Rejoso: Okay, I’ll get that to you. Anything else, that we have?
419 00:41:48.550 ⇒ 00:41:51.499 Sheshu Chandrasekar: Yeah, I got one last question. Oh wait, Eliza, you can go ahead.
420 00:41:51.500 ⇒ 00:41:53.359 Elizah Joy: Go ahead. Yeah, go ahead, Sasha.
421 00:41:53.360 ⇒ 00:41:55.719 Sheshu Chandrasekar: Do we have a… do we have a Figma account here?
422 00:41:56.050 ⇒ 00:41:56.770 Rico Rejoso: Yep.
423 00:41:57.070 ⇒ 00:42:01.769 Sheshu Chandrasekar: Yeah. So do… so if I just log into my Brainforge account using Figma, can I just,
424 00:42:02.940 ⇒ 00:42:06.739 Sheshu Chandrasekar: Do I need to get approved or anything, or it’s automatically approved?
425 00:42:06.740 ⇒ 00:42:08.440 Rico Rejoso: Let me give you access, I’m sorry.
426 00:42:08.640 ⇒ 00:42:09.580 Sheshu Chandrasekar: No, you’re good.
427 00:42:15.460 ⇒ 00:42:16.320 Rico Rejoso: Okay.
428 00:42:16.740 ⇒ 00:42:19.710 Rico Rejoso: Anything else that you need access with?
429 00:42:20.330 ⇒ 00:42:24.289 Sheshu Chandrasekar: I don’t, at the moment, I think… yeah, I think I have everything I need.
430 00:42:24.650 ⇒ 00:42:25.200 Rico Rejoso: Okay.
431 00:42:25.540 ⇒ 00:42:26.609 Sheshu Chandrasekar: I’ll invite you to.
432 00:42:27.960 ⇒ 00:42:28.950 Sheshu Chandrasekar: Perfect, thanks.
433 00:42:33.730 ⇒ 00:42:40.759 Rico Rejoso: Alright, if nothing else, I think we’re good. Eliza, I think… I guess you’ll be the one who’s gonna reply to Tom’s message.
434 00:42:40.760 ⇒ 00:42:45.520 Elizah Joy: Yep, I’ll send this message right away after this song.
435 00:42:45.950 ⇒ 00:42:51.050 Rico Rejoso: Alrighty. Well, thank you guys. If anything else, again, let me know, and also feel free to.
436 00:42:51.310 ⇒ 00:42:54.580 Rico Rejoso: assign tasks on linear, and I can take a look at it.
437 00:42:55.230 ⇒ 00:42:57.030 Rico Rejoso: And work on it, definitely.
438 00:42:57.730 ⇒ 00:43:01.740 Elizah Joy: Alright, thank you so much, Rico. Thank you, Shashu.
439 00:43:02.450 ⇒ 00:43:03.030 Sheshu Chandrasekar: Thank you both.
440 00:43:03.580 ⇒ 00:43:05.259 Elizah Joy: Thank you, bye!