Meeting Title: BF x Kitesight Date: 2025-06-25 Meeting participants: Shekhar, Deep Vaghani, Amber Lin, Awaish Kumar
WEBVTT
1 00:00:09.140 ⇒ 00:00:09.815 Shekhar: Maybe.
2 00:00:11.110 ⇒ 00:00:12.390 Deep Vaghani: Hey, shikar.
3 00:00:14.070 ⇒ 00:00:14.909 Shekhar: How are you?
4 00:00:15.370 ⇒ 00:00:16.430 Deep Vaghani: Good, good.
5 00:00:18.560 ⇒ 00:00:19.160 Shekhar: Yeah.
6 00:00:20.210 ⇒ 00:00:21.439 Deep Vaghani: Are you in the office?
7 00:00:22.190 ⇒ 00:00:22.780 Shekhar: Yep.
8 00:00:24.550 ⇒ 00:00:27.890 Deep Vaghani: Good! Good! You wanna put up the shirt.
9 00:00:28.440 ⇒ 00:00:28.960 Shekhar: Oh!
10 00:00:29.560 ⇒ 00:00:30.160 Deep Vaghani: Yeah.
11 00:00:31.850 ⇒ 00:00:36.816 Deep Vaghani: But yeah, for all the client meetings, let’s make sure we are.
12 00:00:38.250 ⇒ 00:00:38.650 Deep Vaghani: Yeah.
13 00:00:38.650 ⇒ 00:00:40.860 Shekhar: I think this meeting is getting recorded.
14 00:00:46.090 ⇒ 00:00:47.290 Shekhar: Oh, yeah, yeah.
15 00:00:48.250 ⇒ 00:00:50.589 Deep Vaghani: Oh, yeah, it’s recorded because they have.
16 00:00:52.176 ⇒ 00:00:54.259 Deep Vaghani: They have the yeah recording.
17 00:01:04.420 ⇒ 00:01:05.510 Awaish Kumar: I’m a long progress.
18 00:01:05.950 ⇒ 00:01:07.730 Deep Vaghani: Hey!
19 00:01:10.300 ⇒ 00:01:11.390 Amber Lin: Hi! There!
20 00:01:13.390 ⇒ 00:01:13.925 Deep Vaghani: Hey?
21 00:01:14.670 ⇒ 00:01:16.019 Deep Vaghani: How are you guys doing.
22 00:01:17.040 ⇒ 00:01:17.980 Amber Lin: Pretty good.
23 00:01:18.517 ⇒ 00:01:25.409 Amber Lin: I don’t have too much context about this meeting. I’m not sure if Utah’s joining. Do you guys know if he’s joining or not?
24 00:01:27.240 ⇒ 00:01:32.030 Deep Vaghani: Uttam I so last time I was chatting with him, I don’t think.
25 00:01:32.030 ⇒ 00:01:33.570 Awaish Kumar: Thank you for joining a good day.
26 00:01:33.570 ⇒ 00:01:36.459 Deep Vaghani: Yeah, he’s not able to join this. But.
27 00:01:36.460 ⇒ 00:01:37.080 Amber Lin: Okay.
28 00:01:37.640 ⇒ 00:01:44.340 Deep Vaghani: He mentioned to me that he was going to brief you guys, and then
29 00:01:44.610 ⇒ 00:01:57.049 Deep Vaghani: we can talk about availabilities and the type of work that you guys are thinking that we can handle it for you right off the bat and and go from there. Yeah. And then we can connect with them after of this meeting. Yeah.
30 00:01:57.390 ⇒ 00:02:06.930 Amber Lin: I see. Yeah, I’ve looked at the notion docket which I’m shared with us. I believe that should be most of the context that we have
31 00:02:07.747 ⇒ 00:02:18.040 Amber Lin: so based on what you said, I guess the goal for this meeting is to decide on what work we immediately want to start doing together right.
32 00:02:18.870 ⇒ 00:02:20.243 Deep Vaghani: Correct. Yep.
33 00:02:21.240 ⇒ 00:02:24.030 Amber Lin: Let me go find that document.
34 00:02:41.904 ⇒ 00:02:45.359 Amber Lin: Wish! Have you had a chance to locate? Sorry! Go ahead.
35 00:02:46.281 ⇒ 00:02:47.757 Amber Lin: Wish dropped off.
36 00:02:48.250 ⇒ 00:02:59.309 Deep Vaghani: I was just mentioning Shakhar. That Utham, who is CEO of Brainforge, is not able to attend this, but I was supposed to attend this call. And I was going to introduce you with
37 00:02:59.550 ⇒ 00:03:15.769 Deep Vaghani: like the team itself. But yeah, but yeah, Amber, this is Shekhar. He’s a data engineer, senior data engineer in my team. He is working from India. And yeah, we have been working together for a lot of projects. And yeah, I wanted to just give a short introduction.
38 00:03:16.830 ⇒ 00:03:17.510 Shekhar: Thank you.
39 00:03:17.510 ⇒ 00:03:17.950 Amber Lin: Oh!
40 00:03:19.920 ⇒ 00:03:21.600 Shekhar: It was really nice meeting.
41 00:03:23.330 ⇒ 00:03:23.890 Deep Vaghani: Yep.
42 00:03:24.820 ⇒ 00:03:40.850 Amber Lin: Yeah, I’ll also give a quick introduction about myself. So my name is Amber. I’m working as a project manager on Greenforge, and also I help with allocations and looking at my project profitability. So I think.
43 00:03:41.300 ⇒ 00:03:59.280 Amber Lin: well, I manage 3 of the bigger projects on Brain Forge, and I will be able to say clearly what we need for those 3 projects for other ones. We probably need to ask utam on on those. But I do think, he added a few comments.
44 00:03:59.660 ⇒ 00:04:03.159 Amber Lin: And in a document.
45 00:04:04.300 ⇒ 00:04:05.100 Amber Lin: Okay?
46 00:04:09.030 ⇒ 00:04:11.555 Amber Lin: Okay, sure.
47 00:04:30.050 ⇒ 00:04:30.940 Amber Lin: Okay.
48 00:04:31.310 ⇒ 00:04:32.420 Amber Lin: I wish.
49 00:04:34.130 ⇒ 00:04:34.870 Deep Vaghani: You wish.
50 00:04:37.040 ⇒ 00:04:38.569 Amber Lin: Have you guys talked before.
51 00:04:40.830 ⇒ 00:04:47.379 Deep Vaghani: Me and Aveshno, I’ve talked with them a lot like we met 3 different times. Yeah, 3 different locations. So.
52 00:04:47.790 ⇒ 00:04:54.590 Deep Vaghani: oh, wow, okay, yep, we just yeah.
53 00:04:55.017 ⇒ 00:04:56.300 Amber Lin: I see it.
54 00:04:56.660 ⇒ 00:05:02.610 Amber Lin: I mean, we all just did a quick intro I was wondering if I wish you want to introduce yourself.
55 00:05:11.000 ⇒ 00:05:13.371 Deep Vaghani: Yeah, you’re in mute if you’re speaking.
56 00:05:16.180 ⇒ 00:05:19.040 Amber Lin: Hmm, okay, maybe his Internet is not that great.
57 00:05:19.840 ⇒ 00:05:20.560 Deep Vaghani: Okay.
58 00:05:23.340 ⇒ 00:05:26.490 Amber Lin: Yeah. Let me.
59 00:05:27.170 ⇒ 00:05:33.980 Amber Lin: I mean any we can start. We can just start by looking at this document together.
60 00:05:36.040 ⇒ 00:05:39.449 Amber Lin: And talk about anything we want to kick start.
61 00:05:39.900 ⇒ 00:05:47.039 Amber Lin: Do you know, if we don’t mention any projects that he said, he wants you guys to get started on right away.
62 00:05:48.590 ⇒ 00:06:14.400 Deep Vaghani: So I think that’s what we were supposed to talk in this meeting. And if so, so, I can start with the availability that was asking me about. So what I think with them was looking from this call was, what are the immediate availabilities that we have and who I can, you know, like, introduce my engineers to the team. And then who can pick up the tickets that you guys have already like created? Or it’s already, like, you know well flushed out.
63 00:06:15.060 ⇒ 00:06:37.500 Deep Vaghani: And so that is, that was the intent of the call. So from my side. We, you know, I can start giving the availability. So you know, Shaker is one of the senior data engineers. So any form of like data engineering work analytics engineering work that you guys have, which seems, you know, little board, a little bit higher. Technical knowledge. Then, you know, Shaker should be able to, you know. Take on those tickets, help you guys with like updates. And I know.
64 00:06:37.777 ⇒ 00:06:46.379 Deep Vaghani: you guys have certain stand ups with each clients. And so I was just trying to understand more of that during this call. And so that way, we can see if
65 00:06:46.750 ⇒ 00:06:56.460 Deep Vaghani: my developers have to be on stand up every time. Or you know, we can just coordinate via slack updates. And so that way they work on their time zone. Get all the tickets.
66 00:06:56.460 ⇒ 00:06:56.860 Deep Vaghani: This is.
67 00:06:56.860 ⇒ 00:07:26.350 Deep Vaghani: if there are any blockers, you know. We’ll like our morning here in the Us. We get the updates from them. And then, you know, you guys can take it from there and see if it’s easy to unblock, and probably they will be available. So my devs are generally available the mornings for us like early mornings till 11 to 12, like, you know, and then after that they might have to log off. But if they are able to get the blockers away between those 3 4 h in the morning, then they can work on that on their time, and then next day we do.
68 00:07:26.710 ⇒ 00:07:33.931 Deep Vaghani: Like a full dev blogger. So that’s sort of like how we were going to discuss about that availability and how to.
69 00:07:34.480 ⇒ 00:07:47.980 Amber Lin: Yeah, yeah, totally. So for the time zone overlap that you mentioned is that in est. So can you? I just want to write it down of what the time is like, from when to when every day.
70 00:07:49.320 ⇒ 00:07:57.970 Deep Vaghani: Generally speaking, I would say, 12 central time. Shaker, is that fine to say that you guys should be able to take a look at the messages and stuff.
71 00:07:58.480 ⇒ 00:07:59.140 Shekhar: Here.
72 00:08:00.060 ⇒ 00:08:04.940 Deep Vaghani: Yep. So 1212, central, I would say, yeah, that’s when the staff should be available. Yeah.
73 00:08:05.707 ⇒ 00:08:08.569 Amber Lin: Up to 12 central or after 12 central.
74 00:08:08.890 ⇒ 00:08:10.259 Deep Vaghani: Up to 12. Central.
75 00:08:10.260 ⇒ 00:08:10.730 Amber Lin: Oh, okay.
76 00:08:10.730 ⇒ 00:08:15.789 Deep Vaghani: Then, yeah. And after 12 central, it will be hard for them to like, yeah, coordinate meetings and stuff. Yeah.
77 00:08:15.930 ⇒ 00:08:17.650 Amber Lin: I see. Okay, I understand.
78 00:08:18.329 ⇒ 00:08:30.900 Amber Lin: I mean for us, most of our stand ups are mostly in the mornings as well, at least for all of my team. So that shouldn’t be a problem. And usually we also just think, in the morning get any blockers across, and then
79 00:08:31.198 ⇒ 00:08:49.389 Amber Lin: our stand ups are usually 10 to 15 min, and if we have any blockers we just call individually. So that would just be more like a working session together. But there won’t be too much time stuck in meetings, and we also prefer Async updates. So it stand up so only mostly be for blockers, and if there’s any.
80 00:08:51.180 ⇒ 00:08:52.789 Deep Vaghani: Okay, no, that’s great. Yeah. Because
81 00:08:53.260 ⇒ 00:09:00.029 Deep Vaghani: my understanding was, yeah, like, it’s like, updates, probably be fine. If it’s very straightforward blocker or needs to be.
82 00:09:01.660 ⇒ 00:09:05.910 Awaish Kumar: Will it be possible to like? Have some overlap on Esd time zone
83 00:09:06.300 ⇒ 00:09:09.190 Awaish Kumar: like 2, 2, 3 h, or something like that?
84 00:09:09.640 ⇒ 00:09:17.590 Amber Lin: Yeah. They said, they will be available until 12 CST, so that would be until, say, one Pm. Est.
85 00:09:18.960 ⇒ 00:09:20.380 Deep Vaghani: Yeah, it wouldn’t be amazing.
86 00:09:20.380 ⇒ 00:09:20.930 Shekhar: Yep.
87 00:09:24.120 ⇒ 00:09:32.189 Amber Lin: Yeah, and in in terms of how we’re gonna work together So
88 00:09:32.760 ⇒ 00:09:40.649 Amber Lin: engineers would just be taking on fully groomed tickets, right so it wouldn’t wouldn’t participate.
89 00:09:41.104 ⇒ 00:09:50.479 Amber Lin: As a tech lead. We’re helping with the roadmap or grooming. It would just be. We have this ticket we want to assign by this State, and we completed by this date right.
90 00:09:51.540 ⇒ 00:10:06.740 Deep Vaghani: Exactly. Yeah, I mean as as much as flushed out. Better. So that yeah, I’ll be available myself in the, you know, full 8 HA day in the Us. Time zone. If there are things that needs to be discussed and I can relay that to my side of things to then.
91 00:10:06.740 ⇒ 00:10:10.309 Deep Vaghani: Yes, but yeah, that’s the overall idea. If the tickets are flushed out.
92 00:10:11.781 ⇒ 00:10:18.270 Awaish Kumar: Most of the time, like our tickets are grown. But like it’s in data business, you know, like we.
93 00:10:18.440 ⇒ 00:10:25.413 Awaish Kumar: we get data quality issues or some urgent things or things like that. For that we might not have like,
94 00:10:26.230 ⇒ 00:10:35.409 Awaish Kumar: we can just put some slack message. Okay, we got this data complete issue. Let’s debug, or let’s figure out the
95 00:10:35.720 ⇒ 00:10:42.550 Awaish Kumar: so like, that’s our expectation that anybody who comes in is is able to go in and
96 00:10:43.030 ⇒ 00:10:45.290 Awaish Kumar: and take on those tasks.
97 00:10:47.440 ⇒ 00:10:47.920 Amber Lin: Okay?
98 00:10:49.800 ⇒ 00:11:02.779 Amber Lin: yeah. Great. I was looking at the document I was looking at. Under kitesight resource roster and availability. It says to be decided on the start dates. Do we have an estimate of when that would be.
99 00:11:05.280 ⇒ 00:11:07.880 Deep Vaghani: I would say, for start dates.
100 00:11:08.100 ⇒ 00:11:13.319 Deep Vaghani: Let’s so we have a current project going on. So I’m just trying to
101 00:11:13.720 ⇒ 00:11:16.869 Deep Vaghani: make sure that you know, we started at
102 00:11:17.090 ⇒ 00:11:24.260 Deep Vaghani: so Shekhar, is it safe to say 30, th or probably 1st is better, so that it aligns well with everything commercial as well.
103 00:11:25.050 ⇒ 00:11:38.229 Deep Vaghani: Yeah, if you guys have immediate needs. And you guys need think that. Okay, if we can start it, maybe by, you know, next Monday, then it’s it’s fine. But yeah, if you want to keep it Tuesday first, st it’s, I think, then we can make it more clear and.
104 00:11:39.270 ⇒ 00:11:39.850 Amber Lin: Okay.
105 00:11:40.030 ⇒ 00:11:46.730 Awaish Kumar: I also, I would like to understand the collaboration like, how that
106 00:11:46.940 ⇒ 00:11:55.599 Awaish Kumar: goes like we have to like, give you in advance like expectation of hours of engineer required or
107 00:11:55.910 ⇒ 00:12:03.260 Awaish Kumar: or like. It will be good when he is working, and then he can just log in the system that I work
108 00:12:03.700 ⇒ 00:12:08.359 Awaish Kumar: for so hours like, how is it goes like, do you want us to give some.
109 00:12:10.610 ⇒ 00:12:10.970 Deep Vaghani: So.
110 00:12:10.970 ⇒ 00:12:13.329 Awaish Kumar: Maybe month or week, or something like that.
111 00:12:15.740 ⇒ 00:12:41.460 Deep Vaghani: Okay, yeah, that’s a good question. And I believe we haven’t discussed that very thoroughly with the I think so right now, I think there is just estimated hours you have guys assigned. But if you guys have a way to log in hours like probably like harvest or something, then we probably might just go with that approach, and then, you know, assign, however, many hours, that the or who a particular engineer is spending.
112 00:12:41.460 ⇒ 00:12:41.790 Shekhar: Yeah.
113 00:12:41.790 ⇒ 00:12:46.750 Deep Vaghani: Generally generally acceptable with the acceptable like hours that
114 00:12:47.140 ⇒ 00:12:59.829 Deep Vaghani: you know standardized across the industry. So we probably use that as a base and then go with it. Unless you guys have a different idea of like, okay, these are the fixed hours. We don’t want to go over that. And then you know that? Then we can also
115 00:13:00.120 ⇒ 00:13:20.389 Deep Vaghani: see if we are able to do that as well. But yeah, we can log hours in a system of your choice and then from there we can. Yeah, we’ll generate, invoice. And so I can talk commercials with them. But yeah, in terms of like tracking it. We guys are good with any approach you have thought of. Yeah.
116 00:13:21.450 ⇒ 00:13:30.559 Shekhar: The second option is, yeah, what we can do like any of your team can give us some expectation like, Oh, this ticket or this is a smaller ticket. Yeah.
117 00:13:30.780 ⇒ 00:13:33.169 Shekhar: that will surely help us.
118 00:13:33.760 ⇒ 00:13:34.310 Deep Vaghani: Yep.
119 00:13:34.310 ⇒ 00:13:34.650 Amber Lin: Okay.
120 00:13:36.370 ⇒ 00:13:52.679 Deep Vaghani: Yep, generally. I mean, yeah. There is a high level expectations like there’s always good to keep 20% buffer for any you know, like blockers. And then here, like any sort of like admin work, and whatever like communication our span and stuff like that. But yeah, generally speaking, I think what we have done is like, yeah
121 00:13:53.095 ⇒ 00:14:02.169 Deep Vaghani: any task. If it’s very clear in terms of a dev work, then, yeah, we’ll probably able to just log in all the dev work that was spent on that task. Yeah.
122 00:14:02.690 ⇒ 00:14:03.330 Shekhar: Absent.
123 00:14:06.360 ⇒ 00:14:07.000 Amber Lin: Okay.
124 00:14:07.760 ⇒ 00:14:14.879 Amber Lin: Oh, see, I was looking at. Let me just share my screen.
125 00:14:15.300 ⇒ 00:14:15.640 Deep Vaghani: Yeah.
126 00:14:17.060 ⇒ 00:14:23.950 Amber Lin: This document, and so I put down
127 00:14:24.866 ⇒ 00:14:37.200 Amber Lin: here that perhaps we can start July first, st and if urgent next Monday, do we have any estimates for the other engineer that was listed here.
128 00:14:38.572 ⇒ 00:14:43.040 Deep Vaghani: So, Dave, I believe. Should be same right. Shakhar. July first.st Yeah.
129 00:14:43.040 ⇒ 00:14:43.580 Shekhar: Yep.
130 00:14:47.730 ⇒ 00:14:54.340 Amber Lin: Okay, hmm, ice.
131 00:14:56.620 ⇒ 00:15:00.919 Amber Lin: Okay? So if they’re both available around 10 h per week.
132 00:15:01.070 ⇒ 00:15:08.709 Amber Lin: think a person can either handle, I think, one to 2 projects per person, depending on how it is.
133 00:15:11.800 ⇒ 00:15:12.640 Amber Lin: Thank you.
134 00:15:13.890 ⇒ 00:15:19.823 Amber Lin: I mean, if they’re both available to start, I’m gonna sync with to
135 00:15:21.050 ⇒ 00:15:34.829 Amber Lin: make sure confirm with him, cause I don’t think I can make the decision of where we’re gonna allocate them to I’ll sync with him to get these few things. So decide what projects
136 00:15:36.848 ⇒ 00:15:56.300 Amber Lin: for quite site engineers, and then pick tickets, and then any onboarding items, access, etc.
137 00:15:56.590 ⇒ 00:15:58.130 Amber Lin: And then.
138 00:16:07.220 ⇒ 00:16:13.220 Amber Lin: yeah, so I think I will try to get this done thing.
139 00:16:13.870 ⇒ 00:16:15.560 Amber Lin: Amber
140 00:16:19.040 ⇒ 00:16:20.460 Amber Lin: wish.
141 00:16:21.830 ⇒ 00:16:28.000 Amber Lin: Yeah, I’ll try to get this done by Friday.
142 00:16:29.370 ⇒ 00:16:29.704 Deep Vaghani: Okay.
143 00:16:30.470 ⇒ 00:16:32.979 Amber Lin: And then I’ll inform you guys.
144 00:16:33.550 ⇒ 00:16:41.190 Amber Lin: Oh, and then, notified.
145 00:16:43.910 ⇒ 00:16:53.040 Amber Lin: try to get. I’ll try to get it done by Thursday. Honestly. So we have some time before we can start, and then
146 00:16:53.200 ⇒ 00:17:02.440 Amber Lin: we’ll do these 2 in parallel. So hopefully, we can get set up for next week. That’s the most optimistic estimate
147 00:17:02.846 ⇒ 00:17:16.139 Amber Lin: cause. Utam is traveling, and we’re doing our Q 3 brief planning. I don’t know how much time he will have to meet with me. But I’ll try to get that time. I’ll get back to you guys so we can get started as soon as possible.
148 00:17:16.599 ⇒ 00:17:17.179 Shekhar: Yep.
149 00:17:18.009 ⇒ 00:17:18.579 Amber Lin: Yeah.
150 00:17:18.579 ⇒ 00:17:19.389 Deep Vaghani: That’s great. Yeah.
151 00:17:19.790 ⇒ 00:17:20.170 Amber Lin: Yeah.
152 00:17:20.982 ⇒ 00:17:34.359 Deep Vaghani: Yeah, in terms of onboarding stuff. I think, yeah, I can share any other details you need for creating that access on the systems. But yeah, you can probably use the same emails that from this meeting
153 00:17:35.111 ⇒ 00:17:38.899 Deep Vaghani: for for creating any onboarding access request.
154 00:17:39.810 ⇒ 00:17:46.337 Amber Lin: Sounds good it would. It would have been nice if Luton was here, so we could have get got the 1st item done
155 00:17:46.880 ⇒ 00:17:47.720 Deep Vaghani: Yeah, I don’t.
156 00:17:47.720 ⇒ 00:17:48.690 Amber Lin: Unfortunate.
157 00:17:48.690 ⇒ 00:17:59.560 Deep Vaghani: It was. It was on my side, because he was trying to do it on Tuesday. And then I was, Yeah, we are literally like just running through the time, you know.
158 00:18:00.210 ⇒ 00:18:03.499 Deep Vaghani: Timelines of the new, the project that is currently going on. It’s very tight.
159 00:18:03.500 ⇒ 00:18:04.100 Deep Vaghani: Yeah.
160 00:18:04.100 ⇒ 00:18:09.690 Deep Vaghani: So and I’m also like almost 4 h in the in, the, on, those on those calls myself no.
161 00:18:10.380 ⇒ 00:18:12.430 Amber Lin: I see? Yeah, I understand.
162 00:18:12.430 ⇒ 00:18:13.090 Deep Vaghani: Yep.
163 00:18:13.474 ⇒ 00:18:27.730 Deep Vaghani: but I think he was traveling, he told me like, let’s just create this meeting. So you guys, at least, you know, we introduce, get, get, introduce ourselves. And then yeah, once you are able to. So when he’s back, do you guys know about the is back Friday or something.
164 00:18:28.124 ⇒ 00:18:42.725 Amber Lin: He! He’s traveling to New York to meet with our other CEO to talk about Q. 3 stuff in person. He will be available for meetings where, like, I’ll call him, and we’ll get the items decided.
165 00:18:43.270 ⇒ 00:19:01.299 Amber Lin: yeah, I’ll I’ll also ping him in our partnership channel, but feel free to add any questions that come up because I feel like we’re we probably are forgetting something, because we just remember about the time logging right? Anything like that of, okay, how do we track our time? Just send those questions in the partnership channel, and we’ll sort them out.
166 00:19:02.660 ⇒ 00:19:04.568 Deep Vaghani: Yep, no, that sounds good.
167 00:19:04.950 ⇒ 00:19:05.570 Amber Lin: Great.
168 00:19:05.860 ⇒ 00:19:07.000 Deep Vaghani: Craft.
169 00:19:07.000 ⇒ 00:19:11.999 Amber Lin: I don’t have any more questions we’ll probably have to meet again sometime soon.
170 00:19:12.000 ⇒ 00:19:31.090 Deep Vaghani: No, that’s that’s completely okay. I mean, this was definitely the idea for this 1st meeting. I was not also expecting anything. There was no fixed agenda. So all good from our side. And I think, yeah, this was more for my engineer to just introduce with you guys. But yeah, I think you will see more of Shakhar and dev for at least the.
171 00:19:31.090 ⇒ 00:19:31.770 Amber Lin: Go ahead!
172 00:19:31.970 ⇒ 00:19:38.590 Deep Vaghani: Projects like, yeah, is everybody in the slack channel? So all of our engineers are in a slack channel.
173 00:19:39.390 ⇒ 00:20:00.680 Deep Vaghani: No, I will add, Shakhar and Dave both in the slack channel. Now, and then we do have. Yeah, once, if the more requirements comes up and we need more people like, you know, we can definitely talk about that. Yeah, yeah. But we are, we are able to handle like, yeah, any time, intensive or time, sensitive tasks that you guys have with the client. So yeah, we should be able to do that.
174 00:20:01.270 ⇒ 00:20:03.100 Amber Lin: Okay, totally. Thank you all.
175 00:20:04.000 ⇒ 00:20:05.930 Deep Vaghani: Alright, thanks, guys. Nice meeting you.
176 00:20:05.930 ⇒ 00:20:06.410 Amber Lin: Alrighty!
177 00:20:06.560 ⇒ 00:20:07.850 Shekhar: Bye, bye.