Meeting Title: CSO <> SL Standups Date: 2026-03-11 Meeting participants: Awaish Kumar, Brylle Girang, Pranav, Uttam Kumaran, Zoran Selinger, Demilade Agboola, Rico Rejoso
WEBVTT
1 00:01:14.020 ⇒ 00:01:15.230 Brylle Girang: Hello, Oish.
2 00:01:21.760 ⇒ 00:01:22.770 Awaish Kumar: Hi.
3 00:01:23.780 ⇒ 00:01:24.720 Brylle Girang: Good morning.
4 00:01:24.970 ⇒ 00:01:25.720 Awaish Kumar: Morning.
5 00:02:12.510 ⇒ 00:02:13.230 Uttam Kumaran: Hey, guys.
6 00:02:14.740 ⇒ 00:02:15.300 Awaish Kumar: Right.
7 00:02:15.650 ⇒ 00:02:16.660 Pranav: Hey, good morning.
8 00:02:17.210 ⇒ 00:02:18.150 Uttam Kumaran: Hey, good morning.
9 00:02:19.500 ⇒ 00:02:23.630 Uttam Kumaran: Okay, I already feel good about this process, because we have a lot to talk about, so…
10 00:02:31.890 ⇒ 00:02:34.200 Uttam Kumaran: So who are we missing? Sam?
11 00:02:35.410 ⇒ 00:02:36.340 Brylle Girang: Some will not be joining.
12 00:02:36.340 ⇒ 00:02:37.060 Uttam Kumaran: lost.
13 00:02:37.550 ⇒ 00:02:38.230 Uttam Kumaran: Okay.
14 00:02:41.990 ⇒ 00:02:42.789 Brylle Girang: Greg?
15 00:02:42.790 ⇒ 00:02:43.510 Uttam Kumaran: engineered.
16 00:02:43.750 ⇒ 00:02:44.380 Uttam Kumaran: red.
17 00:02:44.380 ⇒ 00:02:46.139 Brylle Girang: Greg might not be joining, too.
18 00:02:47.110 ⇒ 00:02:53.930 Uttam Kumaran: Okay, let’s jump into it. So… Let’s see…
19 00:02:56.320 ⇒ 00:02:58.990 Uttam Kumaran: Okay, you guys can see this?
20 00:02:59.620 ⇒ 00:03:00.380 Uttam Kumaran: Right.
21 00:03:03.640 ⇒ 00:03:04.200 Brylle Girang: Yep.
22 00:03:04.970 ⇒ 00:03:05.540 Uttam Kumaran: Cool.
23 00:03:05.830 ⇒ 00:03:07.819 Uttam Kumaran: Okay, so I… I think…
24 00:03:07.940 ⇒ 00:03:13.730 Uttam Kumaran: This is sort of our first day doing this, already… we’re already thinking about some ways to improve this, but
25 00:03:13.880 ⇒ 00:03:26.069 Uttam Kumaran: I think mainly, I want this to be, like, what… what is the delivery enablement-like team, which is right now just me and B. Like, what are we automating for you guys? And, like, what are we fixing process-wise?
26 00:03:26.550 ⇒ 00:03:34.640 Uttam Kumaran: I want it to be like, okay, what else should we be doing? Are there things here that are lower priority? Are there things that are higher? And then, let’s talk about
27 00:03:34.710 ⇒ 00:03:47.630 Uttam Kumaran: clients. So, maybe I’ll just start today. We worked on a couple things. In particular, I think one thing that has been great, is we worked on a, data platform
28 00:03:47.810 ⇒ 00:03:52.660 Uttam Kumaran: document update skill. B, which client did we, like, run that for?
29 00:03:56.370 ⇒ 00:03:57.349 Uttam Kumaran: You’re on mute.
30 00:04:01.150 ⇒ 00:04:02.299 Uttam Kumaran: You’re still on mute.
31 00:04:04.460 ⇒ 00:04:12.839 Brylle Girang: Sorry, I ran the update, the update part of it for Amble, and then I am running the kickoff part of it for Magic Spoon.
32 00:04:13.820 ⇒ 00:04:18.240 Uttam Kumaran: Okay, so basically, I just want to share what this is.
33 00:04:18.839 ⇒ 00:04:21.670 Uttam Kumaran: So…
34 00:04:21.860 ⇒ 00:04:40.159 Uttam Kumaran: this document, which is the data platform documentation, as everybody knows, is just a pain in the ass to keep updated. But is, like, actually, the moment you need it, or a client asks for it, it’s, like, really, really nice to have this. So we built a automation that allows you to, like.
35 00:04:40.340 ⇒ 00:04:47.820 Uttam Kumaran: basically, It runs through every single sheet of our template, and updates all these fields.
36 00:04:48.050 ⇒ 00:04:57.989 Uttam Kumaran: We actually also just ran this for… for Element, and it’s working pretty well. So, that’s something that we’re gonna release today, and ideally, like, once a week.
37 00:04:58.160 ⇒ 00:04:59.929 Uttam Kumaran: Y’all can just run this.
38 00:05:00.310 ⇒ 00:05:08.079 Uttam Kumaran: It’s gonna be super helpful. Like, if you look at the default, if you look at the Element Data Platform documentation.
39 00:05:08.520 ⇒ 00:05:13.990 Uttam Kumaran: You’ll see that Similarly, like, there’s so much context.
40 00:05:14.510 ⇒ 00:05:17.629 Uttam Kumaran: On tools, on sources, on metrics.
41 00:05:18.100 ⇒ 00:05:24.550 Uttam Kumaran: And so we wanted to create an automation that pulls from transcripts, pulls from the platform, and, like, keeps this sheet.
42 00:05:24.920 ⇒ 00:05:25.850 Uttam Kumaran: tidy.
43 00:05:25.980 ⇒ 00:05:30.259 Uttam Kumaran: So, B, like, how do you… there’s a… there’s a skill right now to do that.
44 00:05:31.990 ⇒ 00:05:41.200 Brylle Girang: Yeah, yeah, exactly. So, I have created one general workflow for data platform documentation. It’s divided into three main parts.
45 00:05:41.270 ⇒ 00:05:54.320 Brylle Girang: The first one is Kickoff, which will also embed in the client engagement kickoff workflows in the future, where it will create the data platform documentation from scratch, and fill out
46 00:05:56.280 ⇒ 00:05:59.500 Brylle Girang: I’ll try data platform documentation as the command.
47 00:05:59.500 ⇒ 00:06:03.610 Uttam Kumaran: Yeah, yeah, so that’s the kickoff one, and then this is the… I may not have the latest.
48 00:06:04.000 ⇒ 00:06:07.580 Uttam Kumaran: But there should be one for data platform documentation, right?
49 00:06:11.030 ⇒ 00:06:30.900 Brylle Girang: Yeah, so what it does is, it basically creates the first phase of the data platform doc for you. So it uses our standard template, and it’s linked via MCP, so whenever it updates in the future, we have a new documentation, we have new tabs, then it will automatically… the rule or the workflow will automatically be updated.
50 00:06:31.320 ⇒ 00:06:44.199 Brylle Girang: The second part is backfill, so let’s say a new CSO comes in, the data platform doc has not been updated for 3 weeks, then backfill should be able to do everything else for you.
51 00:06:44.290 ⇒ 00:06:58.729 Brylle Girang: And then the third one is update, which is going to be used for regular updating, and we’re also planning to, like, embed this into the daily workflows that the CSOs and SLs will be using.
52 00:06:58.990 ⇒ 00:06:59.370 Uttam Kumaran: Okay.
53 00:06:59.370 ⇒ 00:07:11.689 Brylle Girang: Our main goal here in the next weeks or so, is to have… is to give you guys workflows that will then leverage these skills on a step-by-step process.
54 00:07:12.560 ⇒ 00:07:18.480 Uttam Kumaran: Yeah, so if you go into Cursor and you go into Skills, you’re gonna see here all the various skills that we’re working on.
55 00:07:18.880 ⇒ 00:07:32.579 Uttam Kumaran: Several of them are related to, basically, updating the data platform. This is a data platform doc update skill. So for anyone on the data side, you can just run this today. And as long as you send it your…
56 00:07:32.790 ⇒ 00:07:38.349 Uttam Kumaran: The… the sheet that you’re… That you’re using, it’ll go run that fix.
57 00:07:38.510 ⇒ 00:07:49.119 Uttam Kumaran: So, that’s an example of something we pushed. Another thing that is coming this month that we’re working on, or coming this week, we’re working on transitioning off of Instagant.
58 00:07:50.490 ⇒ 00:08:04.150 Uttam Kumaran: basically because it’s annoying to update, and it’s no… not programmable. So, I think we’re gonna move towards linear, using, like, linear milestones. Is everyone familiar with that? Like, has everyone used that?
59 00:08:06.070 ⇒ 00:08:07.249 Pranav: Oh, I haven’t.
60 00:08:07.250 ⇒ 00:08:08.360 Zoran Selinger: Not really.
61 00:08:08.740 ⇒ 00:08:09.950 Demilade Agboola: I haven’t.
62 00:08:10.830 ⇒ 00:08:13.779 Uttam Kumaran: Okay, okay, so let me show you guys, like, kind of what it looks like.
63 00:08:13.980 ⇒ 00:08:17.039 Uttam Kumaran: So if you go into an initiative, and…
64 00:08:17.490 ⇒ 00:08:20.709 Uttam Kumaran: I don’t know, is there… like, this is sort of the view.
65 00:08:20.850 ⇒ 00:08:24.140 Uttam Kumaran: I don’t know if we have another one, B, that’s, like, filled out.
66 00:08:24.480 ⇒ 00:08:31.390 Uttam Kumaran: But that’s okay. Basically, there is a version of a Gantt in linear.
67 00:08:31.960 ⇒ 00:08:36.189 Uttam Kumaran: Where it’s basically… an initiative is, like, a higher level goal.
68 00:08:36.309 ⇒ 00:08:42.160 Uttam Kumaran: You can consider this, like, a work stream. And then within a work stream, you have projects.
69 00:08:42.309 ⇒ 00:08:44.609 Uttam Kumaran: Within a project, you have tickets.
70 00:08:44.960 ⇒ 00:08:49.140 Uttam Kumaran: And the nice thing is you can put start and end dates on these.
71 00:08:49.340 ⇒ 00:09:01.539 Uttam Kumaran: And… basically, we have the same, like, Gantt functionality. It’s, of course, like, a little bit more technical, so we can… we can change, like, what gets displayed here, but the nice thing is, like.
72 00:09:01.710 ⇒ 00:09:05.570 Uttam Kumaran: we can basically, like, now, like, basically do everything, I think, in linear.
73 00:09:05.760 ⇒ 00:09:10.340 Uttam Kumaran: And this, this, we’re gonna build skills to keep this updated, so…
74 00:09:10.770 ⇒ 00:09:13.550 Uttam Kumaran: I’m fairly confident that, like, by Monday.
75 00:09:13.850 ⇒ 00:09:17.810 Uttam Kumaran: We should have a path towards, like, Mixing Instagant.
76 00:09:18.460 ⇒ 00:09:27.649 Uttam Kumaran: But you guys tell me, like, I still think it’s, like, really professional-looking, and so I’m still not, like, married to this one, but in terms of speed to keep this up to date.
77 00:09:27.870 ⇒ 00:09:29.370 Uttam Kumaran: It’s, like, way better.
78 00:09:31.420 ⇒ 00:09:47.459 Brylle Girang: Well, you know what’s amazing, Otem? You shared, like, the AI Gantt Maker recently, and so with the projects in linear, we’ll be able to, like, extract the info from these linear milestones, and then feed it to the AI Gantt Maker instead, which would make.
79 00:09:47.460 ⇒ 00:09:48.190 Uttam Kumaran: Yeah, so.
80 00:09:48.190 ⇒ 00:09:48.710 Brylle Girang: bull.
81 00:09:49.220 ⇒ 00:09:55.030 Uttam Kumaran: Yeah, so I think we’ll think about something else that’s, like, maybe more business-facing or slide-facing, but…
82 00:09:56.210 ⇒ 00:09:58.980 Uttam Kumaran: I think this is easier to maintain, because anyone, like.
83 00:09:59.230 ⇒ 00:10:01.739 Uttam Kumaran: Have any strong objection to this?
84 00:10:04.560 ⇒ 00:10:05.310 Uttam Kumaran: Okay.
85 00:10:05.800 ⇒ 00:10:08.050 Uttam Kumaran: So that’s what’s gonna change there.
86 00:10:08.380 ⇒ 00:10:11.420 Uttam Kumaran: We’re also working on a client health automation.
87 00:10:11.720 ⇒ 00:10:23.590 Uttam Kumaran: ideally, this is gonna basically allow several stakeholders to just know the state of a client. So, for example, between me, between B, between the CSO and a client, between the SL and a client.
88 00:10:23.600 ⇒ 00:10:32.730 Uttam Kumaran: Each of those people care about different things in regards to client health, and we’re gonna build an automation that allows that person to get a perspective
89 00:10:32.790 ⇒ 00:10:40.319 Uttam Kumaran: in a short amount of time on what’s happening. For me, it’s important because, like, I have to see across everything and sort of find where to go help.
90 00:10:40.420 ⇒ 00:10:58.349 Uttam Kumaran: on your client, it’s actually helpful for you to see, like, where are the potential risks from both the CSO and SL perspective as well. So we’re gonna work on that, and then ideally, we’ll be running some of those before this meeting, in order to, like, basically drive discussion here. So I think that’s also going to be helpful.
91 00:10:58.640 ⇒ 00:11:03.479 Uttam Kumaran: The other thing that’s coming out this month is I’m working on a bunch of data skills.
92 00:11:03.800 ⇒ 00:11:04.800 Uttam Kumaran: And so…
93 00:11:04.910 ⇒ 00:11:14.130 Uttam Kumaran: for Awash and Demi, and probably everybody else on your teams, I’m starting to work on a bunch of things related to,
94 00:11:14.340 ⇒ 00:11:19.780 Uttam Kumaran: what I’m kind of calling, like, an agent-powered, like, data environment.
95 00:11:19.920 ⇒ 00:11:24.530 Uttam Kumaran: Basically, this is like, okay, how… across…
96 00:11:25.700 ⇒ 00:11:34.609 Uttam Kumaran: It’s basically, like, across data engineering, across analytics engineering, and across analysts, what are the common tasks
97 00:11:34.710 ⇒ 00:11:53.669 Uttam Kumaran: And then how do I actually build a set of skills to help you guys do things? Whether it’s create… set up DBT, whether it’s, create this type of model, whether it’s investigate, a missing column, all of those common things, I want to give you guys skills to be able to do that.
98 00:11:53.740 ⇒ 00:12:02.479 Uttam Kumaran: So that things speed up. The other thing, of course, that we know is, like, CI is really difficult. So we’re gonna build a lot of different, like, PR workflows.
99 00:12:02.650 ⇒ 00:12:09.219 Uttam Kumaran: that just allow us to prevent bugs from entering the system. And this is something we can bring to every client pretty easily.
100 00:12:09.800 ⇒ 00:12:12.500 Uttam Kumaran: does that make sense?
101 00:12:13.940 ⇒ 00:12:14.720 Awaish Kumar: Yep.
102 00:12:16.630 ⇒ 00:12:20.560 Uttam Kumaran: So we roughly… today, I think the AI team has a lot of that.
103 00:12:20.660 ⇒ 00:12:26.780 Uttam Kumaran: I think I want to move my time towards helping the data team, sort of, with a lot of these features.
104 00:12:27.280 ⇒ 00:12:40.799 Uttam Kumaran: And then the rest of it, I think this month, I’ll also start to think about our conversation from, I think it was, yesterday or Monday, about, like, the service, the SL sort of revamp. Like, how do we think about where the SL needs to sit?
105 00:12:41.040 ⇒ 00:12:44.419 Uttam Kumaran: And, like, how do I… how do I focus on my time?
106 00:12:44.730 ⇒ 00:12:53.170 Uttam Kumaran: B is gonna be spending a lot of time focusing on skills and automations and support for the CSO, and then I’m gonna be spending some time on service leads.
107 00:12:53.580 ⇒ 00:13:06.640 Uttam Kumaran: If I talk about this… the new process changes, one is, like, this meeting, so I think, you know, I think, you know, excluding Sam and Greg, I feel like this meeting is going to be good for us just to talk about updates.
108 00:13:06.840 ⇒ 00:13:15.239 Uttam Kumaran: I spoke with the engagement planners, and we’re gonna start to work on a transition. I think, actually, there’s gonna be, maybe, potentially, some of them are actually gonna help
109 00:13:15.240 ⇒ 00:13:27.529 Uttam Kumaran: with some of this automation, which will be helpful. But overall, like, one thing that I want to start to ask every day is, like, are you guys feeling like you can now use the skills to do all these things?
110 00:13:27.540 ⇒ 00:13:31.719 Uttam Kumaran: Whether it’s updating linear tickets, updating data platform documentation.
111 00:13:31.780 ⇒ 00:13:42.289 Uttam Kumaran: Like, I really want you guys to try the skills, and then tell us if it’s not working, or where it’s not working. But in our testing, in the last, like, two weeks, we’re feeling like
112 00:13:42.560 ⇒ 00:13:45.839 Uttam Kumaran: You should be able to do all the tasks that were there.
113 00:13:46.040 ⇒ 00:13:53.670 Uttam Kumaran: And so tell me where the pain point is. We’re also working on playbooks, and so playbooks is sort of what I was talking to…
114 00:13:53.980 ⇒ 00:13:57.049 Uttam Kumaran: use Auron about yesterday, which is just, like.
115 00:13:57.170 ⇒ 00:14:02.440 Uttam Kumaran: Starting to think about all the various, playbooks for,
116 00:14:02.770 ⇒ 00:14:10.170 Uttam Kumaran: Let’s see, let me find it… Playbooks for, by creating different, like,
117 00:14:11.230 ⇒ 00:14:16.340 Uttam Kumaran: atomic tasks. Basically, the thing I was looking at yesterday was,
118 00:14:16.770 ⇒ 00:14:19.330 Uttam Kumaran: I wanted to break down,
119 00:14:19.520 ⇒ 00:14:32.659 Uttam Kumaran: when you go from, like, an SOW to an offer to somebody, to then the projects associated with it, and then ultimately to the tickets that are related to it. And so I pushed a PR…
120 00:14:33.310 ⇒ 00:14:41.359 Uttam Kumaran: Related to this… some point… Let me find it…
121 00:14:45.790 ⇒ 00:14:48.280 Uttam Kumaran: Okay, I can find it, and maybe it’s in my…
122 00:14:48.960 ⇒ 00:14:51.519 Uttam Kumaran: Maybe it’s in Slack… okay, yeah, here.
123 00:14:51.800 ⇒ 00:14:57.169 Uttam Kumaran: So there’s this, like, reusable epic, reusable playbooks plan that I sort of worked on.
124 00:14:57.290 ⇒ 00:15:03.739 Uttam Kumaran: And the net of it, is really in this, in this document here.
125 00:15:03.860 ⇒ 00:15:10.210 Uttam Kumaran: Which basically talks about, like, oh, this is the implementation plan. Okay, here, here it is.
126 00:15:12.090 ⇒ 00:15:15.640 Uttam Kumaran: Basically, you have your domain.
127 00:15:15.760 ⇒ 00:15:33.349 Uttam Kumaran: you have a type of artifact, and you have a frequency at which you do it, right? And so, ultimately, what this is, is, like, you have a domain of, like, an area of work, you have a type of artifact, and you have how often you run it. All of these go all the way down into, like, a single ticket that someone works on.
128 00:15:33.520 ⇒ 00:15:35.810 Uttam Kumaran: And so, here’s a good example of, like.
129 00:15:35.960 ⇒ 00:15:45.180 Uttam Kumaran: these are common plays that are getting run, right? Like, an EP audit, SOW creation, ticket creation. And so we’re working on, basically, playbooks
130 00:15:45.400 ⇒ 00:16:02.849 Uttam Kumaran: for you to be able to have, be able to basically say, I’m doing X amount of work, I’m doing this X work for client, I want to pull down and take the classic Epic we’ve used for doing that work. So it should make, like, starting a client a lot faster and a lot easier.
131 00:16:03.010 ⇒ 00:16:12.889 Uttam Kumaran: I’m gonna… I’m gonna do the first versions of these, and, like, this is really, I think, the chain that I wanted to highlight, which is, like, we have a service line.
132 00:16:13.080 ⇒ 00:16:14.710 Uttam Kumaran: We have a subservice.
133 00:16:14.820 ⇒ 00:16:18.700 Uttam Kumaran: We have an offering, right? We have a phase of that.
134 00:16:18.880 ⇒ 00:16:26.999 Uttam Kumaran: And then we have, like, the SOW folder, and then it goes all the way down into the ticket. So service line, subservice, offering, phase, deliverable ticket.
135 00:16:27.630 ⇒ 00:16:33.689 Uttam Kumaran: Right? And ideally, these should be reusable every time we do something.
136 00:16:33.900 ⇒ 00:16:40.540 Uttam Kumaran: Right? And so that’s what I’m hopefully… I want you guys to start thinking more about this piece?
137 00:16:41.560 ⇒ 00:16:45.980 Uttam Kumaran: and worry less about, like, okay, now that I’ve sold this deal.
138 00:16:46.200 ⇒ 00:16:54.260 Uttam Kumaran: I gotta go think about all the phases and deliverables. For the most part, most of the stuff we’re selling, we’ve already done once, and so we’re gonna continue to codify these into, like.
139 00:16:54.570 ⇒ 00:17:07.230 Uttam Kumaran: think about, like, you come to a menu, you come to a restaurant, you can pull this thing, I’m doing this thing for a client, this thing for a client, and then more of the CSO’s job and the team lead’s job is just to, like, drive the execution of that, and customize it based on your client.
140 00:17:07.270 ⇒ 00:17:23.839 Uttam Kumaran: And so now you can use cursor to drive all of that customization and all of that initialization, right? So I really want… the reason why a lot of us aren’t using linear and aren’t using the GANs, and this is my assumption, but, like, I’m also running clients, is just it takes a lot of time.
141 00:17:23.920 ⇒ 00:17:37.029 Uttam Kumaran: You know, it takes a hell of a lot of time, and so I want… I don’t want to replace the use of those tools, but I want to give you guys automations to impact, like, entire linear projects in, like, minutes.
142 00:17:37.250 ⇒ 00:17:49.300 Uttam Kumaran: Like, hey, create this project with these tickets, assign these, clean up my tickets, all those things that typically would take 30 minutes, 1 hour, you can now do in minutes, but it still requires you to trigger that.
143 00:17:49.510 ⇒ 00:17:53.950 Uttam Kumaran: Right? So that’s, like, kind of, like, what our… Play is here.
144 00:17:54.110 ⇒ 00:17:55.560 Uttam Kumaran: Any questions?
145 00:17:55.870 ⇒ 00:17:56.410 Uttam Kumaran: There.
146 00:17:56.410 ⇒ 00:17:59.409 Pranav: Yeah, so when we think of, like, one of these…
147 00:17:59.420 ⇒ 00:18:16.559 Pranav: like, features or services, I forget maybe, like, how to exactly phrase it, but, like, one common thing that I see with, like, all AI projects is, like, they want something of the sorts of, like, an MCP server or a knowledge base. Yeah. Is that a good example of, like, what you’re talking about here?
148 00:18:17.070 ⇒ 00:18:23.999 Uttam Kumaran: Yes, exactly. So, I don’t know if this has the exact,
149 00:18:24.840 ⇒ 00:18:36.109 Uttam Kumaran: I don’t know if… I don’t know if I actually ended up writing some of these, but yes. Basically, if you look underneath the AI service, there’s workflow automation, knowledge engineering, AI infra.
150 00:18:36.640 ⇒ 00:18:42.000 Uttam Kumaran: And one of these, I forgot what, each of these has a README, one of these is related to MCP creation.
151 00:18:42.160 ⇒ 00:18:45.180 Uttam Kumaran: And so we’re creating these atomic units of work.
152 00:18:45.280 ⇒ 00:18:56.490 Uttam Kumaran: So that, like, when you go to a client, you sell an SOW, one, the sales team, which is gonna be a lot of you for a lot of deals, you can pick from things that we’ve already done, and not have to think about, like.
153 00:18:56.490 ⇒ 00:19:08.550 Uttam Kumaran: what is the atomic unit of work? Similarly, when you sell something, you now can match it to something that exists, and not have to recreate. Instead, what you’re bringing to the table is, like, how is this slightly different?
154 00:19:08.770 ⇒ 00:19:21.999 Uttam Kumaran: like, what is the sauce for this client that we’re doing, though? Like, maybe we’re doing something technically new, or, like, it’s not exactly the way we’ve always done it. Those are the tweaks, actually, that are more important, but I want to get you 80% of the way there faster.
155 00:19:22.500 ⇒ 00:19:35.790 Uttam Kumaran: So on the data side, right, for, like, Awesha and Debbie, you guys know, like, we do these audits, we’re doing data infra, we’re doing analytics and BI, and then now we’re adding edge, and then on the strategy side, we have, like, all these different things, so…
156 00:19:36.060 ⇒ 00:19:49.969 Uttam Kumaran: we’re just gonna build these out, and I’m… I’m really hopeful that, like, for the most part, when we sell a deal, it’s really clear the tickets involved. Like, that’s the goal. Like, what are the tickets involved in this deal, and can you have clarity about that, you know?
157 00:19:52.480 ⇒ 00:19:53.070 Awaish Kumar: Yep.
158 00:19:55.330 ⇒ 00:19:55.980 Uttam Kumaran: Cool.
159 00:19:59.570 ⇒ 00:20:12.130 Uttam Kumaran: Great. And then my next piece, and this is maybe a question for you guys, I think now that we don’t have these morning meetings, I think it’s… my open question is, like, what do you guys want to do? Like, do you still want
160 00:20:12.400 ⇒ 00:20:14.810 Uttam Kumaran: to book… stand-ups.
161 00:20:14.930 ⇒ 00:20:20.189 Uttam Kumaran: Should I just leave that to you guys to figure out? Like, what do you think is… is best?
162 00:20:24.310 ⇒ 00:20:36.130 Zoran Selinger: Yeah, so stand-ups, so, for example, for… I still see strategy service stand-up and even daily stand-up, they’re still in the calendar. I don’t know if those are happening or not.
163 00:20:36.130 ⇒ 00:20:41.270 Uttam Kumaran: It’s cause a… it’s cause a robber is just out. So…
164 00:20:41.270 ⇒ 00:20:44.240 Zoran Selinger: Those are officially canceled right now, right?
165 00:20:45.220 ⇒ 00:20:49.590 Uttam Kumaran: Yeah, like, I guess this is where I want to say, like, it’s up… it’s up to this group.
166 00:20:49.730 ⇒ 00:20:57.730 Uttam Kumaran: like, if… I can ask Robert what he wants to do, but I want… I’m… I’m… meaning, like, I just want to make this change this week.
167 00:20:58.290 ⇒ 00:20:59.200 Uttam Kumaran: But…
168 00:20:59.410 ⇒ 00:21:05.539 Uttam Kumaran: Yeah, I would prefer… like, my recommendation is, like, you guys pick when you want to meet with your teams.
169 00:21:06.070 ⇒ 00:21:08.330 Uttam Kumaran: And you just meet with them during the day.
170 00:21:08.330 ⇒ 00:21:10.329 Zoran Selinger: In the way you want to do it, and…
171 00:21:10.330 ⇒ 00:21:11.949 Uttam Kumaran: Try not to do it, like.
172 00:21:12.190 ⇒ 00:21:18.729 Uttam Kumaran: hey, what ticket are you working? Like, make it a real meeting, but, like, meet for 15 minutes and get everything done, and then move on, you know?
173 00:21:27.670 ⇒ 00:21:33.529 Zoran Selinger: Yeah, I think the only… the only risk, of that is that,
174 00:21:33.670 ⇒ 00:21:41.260 Zoran Selinger: We might be in a position where we do more things in private messages that way.
175 00:21:41.370 ⇒ 00:21:44.250 Zoran Selinger: So, not everything… you might get…
176 00:21:44.250 ⇒ 00:21:46.859 Uttam Kumaran: My ass will be do it in the channel.
177 00:21:47.190 ⇒ 00:21:49.160 Zoran Selinger: Yeah, we… we will have.
178 00:21:49.160 ⇒ 00:21:49.959 Uttam Kumaran: You’ll have to do in the chat.
179 00:21:49.960 ⇒ 00:21:51.650 Zoran Selinger: Cognizant of that, yeah.
180 00:21:51.650 ⇒ 00:22:09.230 Uttam Kumaran: Yeah. Well, I mean, I can help you… if you’re, like, if you’re okay with the first, then I can help you with the second. Because if I’m not, like, what… if I don’t see… if, like, for example, if we don’t see messages in the Slack channel, I’m not gonna be able to understand at all what’s going on on a client, so…
181 00:22:09.980 ⇒ 00:22:13.190 Uttam Kumaran: But that’s, I feel like, more habit. Like, I’m less worried about that.
182 00:22:14.470 ⇒ 00:22:26.609 Uttam Kumaran: because ultimately, I’m worried about… first job is, like, doing whatever we need for the client. So, even if that’s in DMs, the client is happy, like, we can then talk about that. But, like, my first job is, like.
183 00:22:26.820 ⇒ 00:22:28.479 Uttam Kumaran: Are we nailing it, you know?
184 00:22:28.590 ⇒ 00:22:29.980 Uttam Kumaran: DMs or not.
185 00:22:30.140 ⇒ 00:22:30.920 Uttam Kumaran: Heh, yeah.
186 00:22:30.920 ⇒ 00:22:31.470 Zoran Selinger: No.
187 00:22:32.010 ⇒ 00:22:39.069 Zoran Selinger: I think… I don’t know if the rest agree, but I think, yeah, just between the SLs and CSOs.
188 00:22:39.360 ⇒ 00:22:44.360 Zoran Selinger: We can make a decision on each client, and that’s it. If we need to, or we don’t.
189 00:22:45.880 ⇒ 00:22:46.500 Uttam Kumaran: Okay.
190 00:22:47.480 ⇒ 00:23:03.689 Demilade Agboola: I think my question is, how do we keep track of progress? Because, I mean, that’s what the formula standouts were for, in the sense of, it was important to know what is progressing on a day-to-day basis, and how close we’re cutting it towards the deliverables.
191 00:23:03.690 ⇒ 00:23:06.859 Uttam Kumaran: But that should… but that’s gotta be in… that’s gotta be in linear, I feel like.
192 00:23:08.210 ⇒ 00:23:09.070 Demilade Agboola: Right?
193 00:23:14.700 ⇒ 00:23:23.619 Demilade Agboola: I mean, yes, but I feel also, like, Lineo doesn’t actually always, like, give room for a cry for help, for instance, or…
194 00:23:23.860 ⇒ 00:23:32.769 Demilade Agboola: Just, like, hey, this is supposed to be done on Friday, it’s Wednesday now, it doesn’t seem like.
195 00:23:32.770 ⇒ 00:23:36.059 Uttam Kumaran: And then I… I think you gotta call… I think you… I think you have to call the meeting.
196 00:23:36.380 ⇒ 00:23:42.179 Uttam Kumaran: Like, I think that’s the point I want to make, is, like, if there is something that cannot be handled via Slack.
197 00:23:42.330 ⇒ 00:23:45.489 Uttam Kumaran: Or linear, then… then call the meeting.
198 00:23:46.280 ⇒ 00:23:53.350 Uttam Kumaran: Does everyone else agree, or like… I mean, I feel like, for me, I… I… like…
199 00:23:53.770 ⇒ 00:24:00.699 Uttam Kumaran: in order to do my… like, again, I think in order to do my job, which is, like, oversight and, like, finding ways to help.
200 00:24:01.050 ⇒ 00:24:07.100 Uttam Kumaran: all of you guys, I need to see the progress in something visible.
201 00:24:07.200 ⇒ 00:24:17.990 Uttam Kumaran: And so my point being is that if it’s in linear, I can be more helpful, but you as the team leader, if you’re not getting those updates in linear, and you’re not hearing in Slack.
202 00:24:17.990 ⇒ 00:24:29.749 Uttam Kumaran: Call the meeting, and call the meeting every day. Call the meeting twice a day, until that starts changing. Doesn’t… I don’t care. You do whatever you want to do. You be as heavy-handed as you need in order to accomplish your job.
203 00:24:30.150 ⇒ 00:24:37.270 Uttam Kumaran: I will… I’m not… I don’t… what I’m saying is, like, I felt like it is… it is, situational.
204 00:24:37.530 ⇒ 00:24:41.330 Uttam Kumaran: like, I think the way we’ve been doing it, where, like, there’s a stand-up in the morning.
205 00:24:41.450 ⇒ 00:24:57.610 Uttam Kumaran: some clients get more top points versus another. It’s like, it’s just so broad that I want you guys to figure out, hey, for this client, we’re struggling, I’m not getting the updates from my team, I’m gonna just, like, let’s just talk every day until we don’t need to do that, you know?
206 00:25:04.980 ⇒ 00:25:05.940 Uttam Kumaran: What do you think?
207 00:25:11.920 ⇒ 00:25:28.140 Zoran Selinger: Yeah, I don’t think that needs to be micromanaged at all, yeah, I agree. I think we’re all experienced enough to just run that as necessary, as long as we do a lot of it in, like you said, either in the channel or in linear.
208 00:25:28.390 ⇒ 00:25:32.260 Zoran Selinger: As long as it’s enough visibility, We should be good.
209 00:25:37.860 ⇒ 00:25:50.749 Uttam Kumaran: Yeah. I mean, I also think that, like, what Zoran said is, like, you just have to loop in Awash and Sam as you guys need. Like, I think that’s one of the big things on the data side, is that, like.
210 00:25:50.750 ⇒ 00:26:03.100 Uttam Kumaran: for example, with Greg, I think he’s doing a good job in calling out, like, that there is an issue, but away, I think he just has to call you and, like, hash it out with you on what the plan is, versus, like.
211 00:26:03.250 ⇒ 00:26:12.129 Uttam Kumaran: Hey, everybody, there’s an issue, you know? And so I think that’s the relationship I want to try to see between people that are leading a team and the service leads.
212 00:26:12.350 ⇒ 00:26:21.270 Uttam Kumaran: And, like, Sam is also there, like, you guys just, like, be like, hey, can you… because this team should rely on itself to then give instruction to everybody else.
213 00:26:21.780 ⇒ 00:26:23.819 Uttam Kumaran: And, like, that’s the way it should be. I think…
214 00:26:23.970 ⇒ 00:26:30.870 Uttam Kumaran: If you’re… I think, yes, you hope that when you say, I need help, and people… a bunch of people raise their hand, but it may not be that way.
215 00:26:30.940 ⇒ 00:26:46.119 Uttam Kumaran: And so instead, I think, like, what I want to see is that Greg and you, Demi, like, are calling Awash and being like, hey, I have this problem. Similar to, like, how you addressed Ashwini, you say, hey, I’m having this problem. Awash should be, like, one of your first escalations.
216 00:26:46.200 ⇒ 00:26:47.000 Uttam Kumaran: Right?
217 00:26:47.360 ⇒ 00:26:55.989 Uttam Kumaran: I think asking in the delivery… in our delivery team, Slack is fine too, but, like, that’s kind of, like, what I would say, because I’ll always use my first escalation, too.
218 00:26:58.320 ⇒ 00:27:13.169 Zoran Selinger: I have, like, I had a message today in the Eden channel, and I… actually, I had that question for a while and never asked. I think this is a good opportunity. So I have this task,
219 00:27:13.360 ⇒ 00:27:21.910 Zoran Selinger: That is… Ashwini, is working on it. Yeah. About the affluence costs, right?
220 00:27:22.030 ⇒ 00:27:28.479 Zoran Selinger: So… I just raised a question today about where we are with it.
221 00:27:28.770 ⇒ 00:27:37.509 Zoran Selinger: I CC’d Ashwini, obviously, in the Eden channel. I CC’d Greg, since he’s got… he’s a CSO now. Should…
222 00:27:37.640 ⇒ 00:27:42.900 Zoran Selinger: Should we ping awash, CC Ovish, in everything data related?
223 00:27:42.900 ⇒ 00:27:44.400 Uttam Kumaran: I mean, Wage, what do you think?
224 00:27:44.700 ⇒ 00:27:45.290 Zoran Selinger: Yeah.
225 00:27:45.290 ⇒ 00:27:55.320 Awaish Kumar: Yes, I think, if it requires, like, data-related, like, if it’s an implementation work, then yes.
226 00:27:56.180 ⇒ 00:28:03.480 Awaish Kumar: I need to see, like, if it’s taking longer, if it’s, like, justifiable, or it’s just because…
227 00:28:03.480 ⇒ 00:28:07.679 Uttam Kumaran: Yeah, this is where, like, I think away should be your, your, your, like.
228 00:28:07.920 ⇒ 00:28:19.059 Uttam Kumaran: backstop on, like, support. Because ultimately, I want… if… ultimately, I… I… if I… if a problem comes to me, I just am now gonna be like, did we go to the SLs first?
229 00:28:19.330 ⇒ 00:28:25.260 Uttam Kumaran: And I think awaits are similar to me in that, like, I don’t care, tag me on every single thing, because I’ll end up reviewing it.
230 00:28:25.550 ⇒ 00:28:30.310 Uttam Kumaran: But this is where, like, for me, the more I get tagged, or the more it escalates to me.
231 00:28:30.470 ⇒ 00:28:36.289 Uttam Kumaran: I… my job is to literally go into, like, the 5,000 degree burning building every day.
232 00:28:36.550 ⇒ 00:28:41.849 Uttam Kumaran: So, instead, for anything that’s, like, around 200 degrees, like, send it to Hoish.
233 00:28:42.140 ⇒ 00:28:57.439 Uttam Kumaran: Because there’s something else burning that I need to go do, and if there isn’t, then I’m gonna go sell business for us, right? But that’s the piece I want to do, is, like, create this escalation layer and make that super clear, and that this team needs to rely on itself. Like, I think…
234 00:28:57.710 ⇒ 00:29:01.569 Uttam Kumaran: I think when we were small, we relied on everybody in the team, but…
235 00:29:01.910 ⇒ 00:29:11.520 Uttam Kumaran: I would say tag Awash, because at least you’ll have his guidance, and he’s aware, so that in case it doesn’t happen, he’s like, yeah, I can take this on, you know?
236 00:29:14.000 ⇒ 00:29:24.509 Zoran Selinger: Yeah, basically here, I wasn’t sure, so Ashwini is working on that ticket. Maybe it’s already done. Basically, I just need an update. Not sure if I need to…
237 00:29:24.820 ⇒ 00:29:34.640 Zoran Selinger: I see, tagging a wish is, like, I’m already escalating the issue, right? Which is maybe not necessary right away.
238 00:29:34.640 ⇒ 00:29:40.970 Uttam Kumaran: But, like, I guess, I guess this is what I’ll say, is, like, let’s say you tag a Srini and you don’t hear for 8 hours.
239 00:29:42.150 ⇒ 00:29:44.100 Uttam Kumaran: You might as well tag away.
240 00:29:44.370 ⇒ 00:29:48.250 Uttam Kumaran: I don’t know. It’s like, what… I don’t know, this is where I’m like…
241 00:29:48.380 ⇒ 00:29:50.540 Uttam Kumaran: It’s gonna be noisy for a bit.
242 00:29:50.990 ⇒ 00:29:53.170 Uttam Kumaran: And we’re gonna be hiring, but, like…
243 00:29:53.680 ⇒ 00:30:01.700 Uttam Kumaran: I think you need to just cover your bases, like, make… if you think someone on your team is gonna drop something, then don’t… don’t, like…
244 00:30:02.070 ⇒ 00:30:21.750 Uttam Kumaran: say it nicely, just to, like, catch it later. Just do the thing that you know is right. Be like, I have a feeling this person’s not gonna take it, but you have a couple options. You can tag Awash, you should say, hey, can we huddle? You can just, don’t even ask, just call people, or say, we need a meeting, right? But ultimately, like, you guys are on the hook, so…
245 00:30:22.080 ⇒ 00:30:26.620 Uttam Kumaran: Don’t let it… don’t let it slip, like, be really forward, you know?
246 00:30:26.720 ⇒ 00:30:35.519 Uttam Kumaran: Ultimately, early is better, and the earlier you find out that someone is gonna drop something, the better, because then someone else in this group can be helpful, you know?
247 00:30:38.470 ⇒ 00:30:47.860 Demilade Agboola: Also, on that ticket in particular, though, like, I think Sweeney should be done with it, or, like, should… because I know I have been syncing with him on it and helping him, like.
248 00:30:48.200 ⇒ 00:30:53.729 Demilade Agboola: Like, let him know how to handle that ticket, so, like, everything should be in place, and if it’s not done.
249 00:30:54.610 ⇒ 00:31:07.990 Zoran Selinger: I actually do see some data coming in, I just don’t have the latest status. I don’t know if it’s really done. I see that status is PR in reviews, I just wasn’t sure.
250 00:31:09.090 ⇒ 00:31:26.370 Uttam Kumaran: Okay, I’ll let you guys handle that, but I think that’s… that’s clear. I think I… I just need to… someone… they just booked some time, one of the clients, on my calendar, so we can keep this short. I think we have our meeting later, too. But I just wanted to highlight a couple things on the hiring side.
251 00:31:26.480 ⇒ 00:31:27.970 Uttam Kumaran: And then…
252 00:31:28.100 ⇒ 00:31:46.489 Uttam Kumaran: like, some of this, I think, B, if you want to just stay on maybe for 5 minutes and just hear from people on, like, anything else that we need automations on. We sent an offer to Advait for Data Analyst. I’m pretty sure he’s gonna join. Ideally, my goal is, like, he’s just gonna handle anything dashboarding.
253 00:31:46.710 ⇒ 00:31:48.199 Awaish Kumar: Sunday.
254 00:31:48.200 ⇒ 00:31:56.320 Uttam Kumaran: Like, that would be wonderful. We also sent a tentative offer to Jasmine, although her start date would be end of month April.
255 00:31:56.790 ⇒ 00:32:03.089 Uttam Kumaran: But she’s still gonna be part-time, so I think my question for this group, and we can talk in Slack, is like.
256 00:32:03.330 ⇒ 00:32:13.220 Uttam Kumaran: where is she highest leverage for everybody, you know? And then, we’re continuing to hire one more AI engineer, a data engineer, and an analytics engineer.
257 00:32:13.560 ⇒ 00:32:26.080 Uttam Kumaran: So, again, like, I’m hoping that, like, in a… in, like, a month… in half a month’s time, this team is actually more about, like, leading clients, less in the weeds.
258 00:32:26.330 ⇒ 00:32:34.039 Uttam Kumaran: I am… spending money and spending my time trying to solve this, so… Like, just keep hustling until…
259 00:32:34.440 ⇒ 00:32:36.510 Uttam Kumaran: But we have great candidates, like…
260 00:32:36.840 ⇒ 00:32:40.399 Uttam Kumaran: Yeah, some people are gonna make it, for sure, very soon, so…
261 00:32:42.910 ⇒ 00:32:52.179 Uttam Kumaran: Okay, I’m gonna jump. Maybe B, if you want to just stay for 2 minutes and just see if there’s anything else anyone has in terms of more automations we should build, that would be fantastic.
262 00:32:52.710 ⇒ 00:32:53.859 Brylle Girang: Yeah, sure.
263 00:32:54.220 ⇒ 00:32:58.220 Uttam Kumaran: Okay, okay. Okay, thank you guys, let me know how I can help today. Appreciate it.
264 00:32:58.860 ⇒ 00:32:59.330 Zoran Selinger: Okay, bye.
265 00:32:59.330 ⇒ 00:33:09.359 Pranav: I have a quick question, actually, on the client health tracker. I know you guys still haven’t built that, but how are you guys thinking about it? Because I think there is, like, a lot of, like.
266 00:33:10.110 ⇒ 00:33:17.660 Pranav: That could be actually, like, super valuable in terms of, like, all the different variables that we bring in, all the different contexts we bring in.
267 00:33:17.780 ⇒ 00:33:21.230 Pranav: Is there kind of a…
268 00:33:21.500 ⇒ 00:33:28.659 Pranav: Yeah, I guess, where are we at on that process, or are we, like, still kind of, like, really beginning stages?
269 00:33:29.310 ⇒ 00:33:44.820 Brylle Girang: Yeah, let me just share my screen here. So, we have, like, two plans for this. The first one is a real dashboard that OTAM is working on, and that will focus on, like, the quantifiable metrics regarding the client health.
270 00:33:44.890 ⇒ 00:33:58.699 Brylle Girang: maybe the percentage of our progress, the percentage of tasks that are overdue, etc. Autom is working on it, we don’t have a draft yet, but it’s going to focus more on the… on the numbers. How can we…
271 00:33:58.880 ⇒ 00:34:01.520 Brylle Girang: Quantify what the client health is.
272 00:34:01.660 ⇒ 00:34:05.179 Brylle Girang: The second part that I am working on is more of…
273 00:34:05.360 ⇒ 00:34:14.579 Brylle Girang: like, a narrative, or the qualitative part of client health. This is still ongoing, it’s the first draft.
274 00:34:14.840 ⇒ 00:34:26.740 Brylle Girang: We’re… basically, we’re using all of the skills, all of the tools that we’re making into… and combining them into creating, like.
275 00:34:27.620 ⇒ 00:34:29.530 Brylle Girang: a summary of.
276 00:34:30.159 ⇒ 00:34:40.489 Brylle Girang: the client health. So, what’s the top summary? What has changed? What’s our status for these scopes? Etc. What are the risks and blockers?
277 00:34:41.080 ⇒ 00:34:50.089 Brylle Girang: we’re still discussing on how… on what the final version would be, but this is the idea. Like, we want to be in a place where
278 00:34:50.340 ⇒ 00:35:05.639 Brylle Girang: you can just go to a single page, you can see everything there. And if you’re a new CSO, you’re taking over another client, etc, then you have a clearer way, or you have a clear picture that you can just look into, and then you’ll have everything.
279 00:35:05.900 ⇒ 00:35:10.200 Brylle Girang: Right? And this is also going to be embedded into our current workflows.
280 00:35:10.350 ⇒ 00:35:19.929 Brylle Girang: the EPA audits, commands, the weekly updates, all of those will then stream into this client health.
281 00:35:20.140 ⇒ 00:35:23.109 Brylle Girang: So we’re taking a look at all the parameters.
282 00:35:23.710 ⇒ 00:35:30.399 Pranav: I guess what I’m thinking, then, is, like, probably two different skills, for CSOs, which I think would be useful, is, like.
283 00:35:30.630 ⇒ 00:35:39.929 Pranav: are we utilizing resourcing well, in that, like, based on our MRR, are we using too many hours, too little hours?
284 00:35:39.930 ⇒ 00:35:40.270 Brylle Girang: Yeah.
285 00:35:40.270 ⇒ 00:35:43.090 Pranav: If we can get, like, a…
286 00:35:43.340 ⇒ 00:35:51.860 Pranav: maybe, like, a health score on that, that would be… that would be great. Basically, like, I guess pulling from Clockify or,
287 00:35:51.880 ⇒ 00:36:08.420 Pranav: we’re also gonna be… at least I’m going to start putting in, like, hours estimates for linear tickets, and so, like, pulling from that would also be, probably useful, especially since, like, Clockify is maybe a little bit too lagging of an indicator. And then…
288 00:36:08.460 ⇒ 00:36:13.650 Pranav: One other one is, like, yeah, based on how far we’re into, like, completing a workstream.
289 00:36:14.430 ⇒ 00:36:31.609 Pranav: getting to know, like, okay, you’re getting close to end, like, this work stream ending, we probably need to start scoping out new work. That would also be great. So, like, okay, yeah, we’re just, like, kind of just getting a, like, a singular value, kind of saying, like, okay, you’re 80% done, or…
290 00:36:31.720 ⇒ 00:36:38.699 Pranav: 90% done, like, you need to, like, start thinking about what you’re gonna work on next. Yeah, those two things I think, would be helpful.
291 00:36:39.500 ⇒ 00:36:57.630 Brylle Girang: Yeah, that totally makes sense. For the first thing, when it comes to resource allocation, we have already enabled our operating MCP, which allows the operations team and Rico here to, like, create reports based on our operating allocations. And at the same time, we’re actually considering
292 00:36:57.630 ⇒ 00:37:09.840 Brylle Girang: into moving from Clockify to operating. We’re, like, trying to build a proposal for that, so that our hours, our hourly tracking is directly connected to the actual allocations.
293 00:37:09.840 ⇒ 00:37:10.250 Pranav: Nice.
294 00:37:10.250 ⇒ 00:37:23.980 Brylle Girang: So we can have, you know, triggers. Hey, you have already dedicated 10 hours for magic spoons, you already… you only have 15 hours this week, chatter, and that should flag us immediately. For the second thing.
295 00:37:24.570 ⇒ 00:37:42.170 Brylle Girang: the linear… our plan to migrate from Instagram to linear should totally help with that. Like, the main reason why Instagan is not currently working is because it doesn’t give us the opportunity to, like, create reports, to, like, create flags or warnings whenever a work stream is ending.
296 00:37:42.250 ⇒ 00:37:50.949 Brylle Girang: So once our timelines is in linear, then definitely that should streamline… that should also stream into the reports that we’re making.
297 00:37:51.600 ⇒ 00:37:52.450 Brylle Girang: That’s helpful.
298 00:37:52.450 ⇒ 00:37:54.040 Pranav: That sounds great. Yeah.
299 00:37:54.810 ⇒ 00:38:12.070 Brylle Girang: Yeah, and at the same time, when it comes to the skills that we’re planning, you can check out the management operations sheet. I think everyone has access to this, and in the role-based skills tab, we’re just creating a compilation of all the skills that we’re planning to automate for
300 00:38:12.290 ⇒ 00:38:18.559 Brylle Girang: Basically, for everyone, for all the roles here. For the CSOs, you can see here that
301 00:38:20.980 ⇒ 00:38:40.760 Brylle Girang: We have… we were planning to create skills when it comes to updating the internal client health, the summaries, the executive summaries, the escalations, etc, as well as the audits. So take a look at this. I would love to, in the meantime, for the sake of our time here, I would love to hear more about what you think.
302 00:38:41.120 ⇒ 00:38:47.290 Brylle Girang: Are the pain points? Are the friction points within your workflows that we maybe can help with?
303 00:38:49.670 ⇒ 00:38:54.410 Brylle Girang: Considering that Instagan should be out of the way in the next few days.
304 00:38:58.410 ⇒ 00:39:03.349 Zoran Selinger: I have a technical question just about PRs. I don’t know if this is a correct place to…
305 00:39:03.350 ⇒ 00:39:03.710 Brylle Girang: Okay.
306 00:39:03.710 ⇒ 00:39:12.999 Zoran Selinger: So, when I submitted a PR yesterday on our platform, so that automatically triggered this document council review.
307 00:39:13.620 ⇒ 00:39:25.639 Zoran Selinger: And then that suggested a few changes. I’ve done those changes today. I was hoping when I push another commit, this would re-trigger this document council.
308 00:39:26.350 ⇒ 00:39:28.779 Zoran Selinger: Can that be re-triggered somehow?
309 00:39:30.950 ⇒ 00:39:32.290 Brylle Girang: I would need to check this.
310 00:39:32.290 ⇒ 00:39:42.270 Zoran Selinger: PR creation. I, I see that the, that the GitHub action is just set up for the, when PR is created, but on every, every repush.
311 00:39:42.960 ⇒ 00:39:45.490 Zoran Selinger: I don’t know if… if we can do that.
312 00:39:46.190 ⇒ 00:39:49.920 Brylle Girang: Yeah, I’m going to leave that for Otam, but… .
313 00:39:50.260 ⇒ 00:39:50.930 Zoran Selinger: Okay.
314 00:39:51.300 ⇒ 00:40:11.079 Brylle Girang: I’m a bit cautious about it being run every time that we commit, and I’m leaning more into it only being run when you first create the PR, because I fear that we’ll be stuck in the loop with Document Council, where it’s not… we’re not going to be in a green state, right? But that’s a good question, I’m going to forward that to Otam.
315 00:40:11.680 ⇒ 00:40:18.899 Zoran Selinger: Yeah, I don’t know if it’s possible… it’s probably… I mean, it’s possible to, so if that, GitHub action
316 00:40:19.550 ⇒ 00:40:22.490 Zoran Selinger: Does it have, like, manual,
317 00:40:22.900 ⇒ 00:40:29.400 Zoran Selinger: a trigger for manual running. If it does, maybe we can do it sometimes, right, if we think we need to.
318 00:40:29.400 ⇒ 00:40:29.920 Brylle Girang: Yep.
319 00:40:30.220 ⇒ 00:40:33.580 Zoran Selinger: That could be maybe a good thing.
320 00:40:34.150 ⇒ 00:40:41.130 Brylle Girang: Yeah, actually, Document Council is not just a GitHub action, it is a cursor skill that everyone here can use.
321 00:40:41.520 ⇒ 00:40:49.429 Brylle Girang: So, I think that’s also an important skill that we can leverage here. If you create SOWs, if you create, maybe.
322 00:40:50.120 ⇒ 00:41:03.800 Brylle Girang: any documents that you will be sending over to the client, the document council will spawn sub-agents without context, so that it’s unbiased, and then try to review the documents based on the.
323 00:41:03.800 ⇒ 00:41:04.120 Zoran Selinger: different.
324 00:41:04.120 ⇒ 00:41:05.640 Brylle Girang: Personas that we have.
325 00:41:05.890 ⇒ 00:41:13.689 Brylle Girang: So, if you’re creating SOWs, if you’re creating proposals, etc, use the Document Council skill to help you out.
326 00:41:14.820 ⇒ 00:41:22.679 Brylle Girang: Yeah, but aside from that, any other pain points, any ideas of the skills, workflows that we should create for you?
327 00:41:23.760 ⇒ 00:41:27.980 Awaish Kumar: Can we have the skills for, like, individual data?
328 00:41:28.500 ⇒ 00:41:29.610 Awaish Kumar: Tasks.
329 00:41:31.070 ⇒ 00:41:38.310 Brylle Girang: Yeah, so Autumn is going to work on that with Amber, so we have decided yesterday that when it comes to
330 00:41:38.470 ⇒ 00:41:43.360 Brylle Girang: Like, these niche skills, where it involves actual technical stuff.
331 00:41:43.470 ⇒ 00:41:45.499 Brylle Girang: It would be best if we…
332 00:41:45.750 ⇒ 00:42:03.710 Brylle Girang: if we assign a person who’s, like, knowledgeable and has actually experience with the actual technical stuff that we’re doing. So, we will be creating skills dedicated for that, and I think Otam’s plan on creating the DPT-related skills is the first phase.
333 00:42:03.770 ⇒ 00:42:07.069 Brylle Girang: of that plan, but definitely a wish.
334 00:42:07.140 ⇒ 00:42:14.540 Brylle Girang: As long as the platform supports, you know, MCP’s APIs, then skills are in the horizon.
335 00:42:17.200 ⇒ 00:42:20.409 Brylle Girang: But, if… when it comes to priority.
336 00:42:20.760 ⇒ 00:42:30.950 Brylle Girang: I don’t think it’s going to be the priority for this week or next week. We’re focusing on how can we enable the people to actually get on top of things.
337 00:42:31.200 ⇒ 00:42:33.820 Brylle Girang: And that should be the first… the next space.
338 00:42:34.790 ⇒ 00:42:37.550 Awaish Kumar: Yeah, my question is, can it be a PR?
339 00:42:37.910 ⇒ 00:42:38.670 Awaish Kumar: Check.
340 00:42:41.000 ⇒ 00:42:41.990 Awaish Kumar: like, on a guitar.
341 00:42:41.990 ⇒ 00:42:42.560 Brylle Girang: Yeah, we can…
342 00:42:42.560 ⇒ 00:42:45.080 Awaish Kumar: There are multiple checks that need to pass.
343 00:42:45.080 ⇒ 00:42:45.590 Brylle Girang: Yep.
344 00:42:46.340 ⇒ 00:42:49.849 Awaish Kumar: I’m thinking about, like, if we create a PR,
345 00:42:50.420 ⇒ 00:42:53.740 Awaish Kumar: In a PR, we should have a guideline, what connections and what…
346 00:42:54.160 ⇒ 00:43:00.109 Awaish Kumar: Cadentials to use, and using that, it can basically create new tables in a staging environment.
347 00:43:00.450 ⇒ 00:43:07.390 Awaish Kumar: And calculate the diffs, compare it to productions, and write down the… Findings in the description.
348 00:43:08.480 ⇒ 00:43:20.170 Brylle Girang: Okay, gotcha. I’m going to note that workflow that you just mentioned, Awash. I think that OTAM is… this is already within the plans of OTAM in the coming weeks, but yes.
349 00:43:22.080 ⇒ 00:43:22.860 Awaish Kumar: Okay.
350 00:43:26.030 ⇒ 00:43:35.599 Demilade Agboola: Yeah, and also other steps, like setting up dbt. So, for instance, once you can put the environmental details, like, point to the keys.
351 00:43:36.000 ⇒ 00:43:37.759 Demilade Agboola: And then,
352 00:43:39.370 ⇒ 00:43:45.330 Demilade Agboola: give the details, like what warehouse and all of that. It should be able to set up DVT automatically for you, without…
353 00:43:46.510 ⇒ 00:43:48.210 Demilade Agboola: I’m spending time doing that.
354 00:43:50.000 ⇒ 00:43:51.560 Brylle Girang: Let me double check that one.
355 00:43:52.380 ⇒ 00:43:56.910 Demilade Agboola: So basically, initializing dbt, setting that up, primary.
356 00:43:59.600 ⇒ 00:44:01.970 Demilade Agboola: Would be… would be quite helpful.
357 00:44:04.420 ⇒ 00:44:06.609 Brylle Girang: Yeah, I think it’s covered here,
358 00:44:08.310 ⇒ 00:44:20.280 Brylle Girang: So, we have specific skills here dedicated to the engineers, so this is our commitment that we’re not only going to be looking at, like, the soft skills, the communication skills, etc.
359 00:44:20.320 ⇒ 00:44:24.419 Demilade Agboola: I’m talking about, like, the skills for, like, an automation.
360 00:44:26.190 ⇒ 00:44:38.219 Brylle Girang: Yeah, this is exactly what it is. So, we’re laying down the tasks here that will then be creating the skills in cursor. So this includes refactoring.
361 00:44:38.390 ⇒ 00:44:41.730 Brylle Girang: Reviewing…
362 00:44:41.730 ⇒ 00:44:43.589 Demilade Agboola: There’s not initializing, that’s what I’m saying.
363 00:44:45.690 ⇒ 00:44:47.070 Brylle Girang: I’m going to add that one.
364 00:44:47.250 ⇒ 00:44:48.120 Demilade Agboola: Okay.
365 00:44:48.570 ⇒ 00:44:55.030 Brylle Girang: Gotcha, okay. But, I’m pretty sure that you have… you have seen that our cursor usage
366 00:44:55.130 ⇒ 00:45:04.250 Brylle Girang: have been blowing up recently, and the main cause of that is because UTAM has been using cloud agents to deploy stuff without
367 00:45:04.290 ⇒ 00:45:15.290 Brylle Girang: him actually doing, or actually writing the codes, or setting up the infrastructures. So, he is currently in the testing phase of trying to see
368 00:45:15.330 ⇒ 00:45:25.779 Brylle Girang: how… how far can we push cursor, and how far can we push AI into actually building stuff for us? And that should include, the stuff that you… that you have mentioned, Demi.
369 00:45:28.490 ⇒ 00:45:29.090 Demilade Agboola: Sure.
370 00:45:31.140 ⇒ 00:45:44.700 Brylle Girang: Okay, and I’m going to take both of those, the stuff that you have mentioned, Awash, and then Demi. I’m going to input those specifically into here, so that it’s always going to be in our pipelines.
371 00:45:44.700 ⇒ 00:45:52.510 Brylle Girang: And then at the same time, I’m going to ask Otam how the Document Council works in GitHub, Zora, just so that we’re clear on that.
372 00:45:53.570 ⇒ 00:45:57.469 Brylle Girang: And, yeah, anything else that we can help you out with?
373 00:45:57.760 ⇒ 00:45:59.789 Pranav: Yeah, quick question,
374 00:46:00.030 ⇒ 00:46:08.480 Pranav: you just mentioned this, but, did you say the operating MCP is, like, in progress, or it’s already, like… we’ve already kind of set it up to, like…
375 00:46:09.110 ⇒ 00:46:13.489 Pranav: Or is that just something that I should set up to then pull in that resourcing information?
376 00:46:14.210 ⇒ 00:46:32.180 Brylle Girang: It is already in the repo, so you can check the MCP tools in Cursor. If operating’s there, then you can try it out. It’s written right. I personally have used it to, like, balance the allocations of the clients under my pocket.
377 00:46:32.270 ⇒ 00:46:41.370 Brylle Girang: And then you can also use it, like, to create reports. Like, how far are we, or how many hours do we have left for a Cetera client?
378 00:46:41.810 ⇒ 00:46:43.210 Brylle Girang: But you can try it out.
379 00:46:43.870 ⇒ 00:46:44.790 Pranav: Okay, perfect.
380 00:46:45.490 ⇒ 00:46:51.599 Brylle Girang: And Rico, can you confirm that you have already, like, embedded the MCP to the Operating 101 guide?
381 00:46:53.080 ⇒ 00:47:00.090 Rico Rejoso: Added it and also posted on the EP, but not at, not at, again, the CSO or SO, channel.
382 00:47:00.090 ⇒ 00:47:00.650 Brylle Girang: Okay.
383 00:47:02.770 ⇒ 00:47:05.799 Brylle Girang: So yeah, short answer, yes, you can, you can try it out right now.
384 00:47:06.290 ⇒ 00:47:06.950 Pranav: Perfect.
385 00:47:10.370 ⇒ 00:47:19.890 Brylle Girang: All right. Yeah, I think we’re good. So, Awash, if you have any clients that you want to, like, focus on today, feel free to schedule the calls with the engineers or the CSOs.
386 00:47:24.860 ⇒ 00:47:26.089 Brylle Girang: Thank you, everyone.
387 00:47:26.240 ⇒ 00:47:27.090 Awaish Kumar: Thank you.
388 00:47:27.800 ⇒ 00:47:28.120 Brylle Girang: Bye bye.
389 00:47:28.120 ⇒ 00:47:28.619 Pranav: Thank you well.
390 00:47:28.620 ⇒ 00:47:29.500 Rico Rejoso: Thanks, guys.