Meeting Title: EdenOS x Brainforge Data Weekly Date: 2026-03-25 Meeting participants: Fireflies.ai Notetaker Chandra, Diego Makarausky, Girish, Ryon, Brylle Girang, Zoran Selinger, Awaish Kumar
WEBVTT
1 00:03:32.370 ⇒ 00:03:33.690 Diego Makarausky: Hey, Girish!
2 00:03:34.350 ⇒ 00:03:36.810 Diego Makarausky: Long time no see!
3 00:03:43.530 ⇒ 00:03:46.170 Diego Makarausky: Fireflies AI.
4 00:03:50.450 ⇒ 00:03:51.720 Diego Makarausky: How’s it going?
5 00:03:52.390 ⇒ 00:03:53.220 Diego Makarausky: November?
6 00:03:54.410 ⇒ 00:03:55.360 Girish: Yo.
7 00:04:03.070 ⇒ 00:04:07.520 Girish: So, this call regarding, can you give the context?
8 00:04:07.720 ⇒ 00:04:08.510 Girish: Diva?
9 00:04:09.680 ⇒ 00:04:18.359 Diego Makarausky: So we have the Brainforge team, right, who’s working with data analytics, mapping, all these connections.
10 00:04:18.620 ⇒ 00:04:21.269 Diego Makarausky: So, the call is with them.
11 00:04:21.660 ⇒ 00:04:34.370 Diego Makarausky: And I think that the goal is just to find, you know, next steps, what they will need to do, what we’ll need to do, and coordinate that. It’s like a recurring meeting that
12 00:04:35.070 ⇒ 00:04:38.930 Diego Makarausky: Every now and then, we’re not able to join, but…
13 00:04:40.170 ⇒ 00:04:42.729 Diego Makarausky: And that’s a good timing for us to be here.
14 00:04:43.560 ⇒ 00:04:46.909 Diego Makarausky: And they own the link, it should be here.
15 00:04:47.100 ⇒ 00:04:47.970 Girish: Lorian.
16 00:04:49.190 ⇒ 00:04:50.050 Ryon: Morning guys, how you doing?
17 00:04:51.640 ⇒ 00:04:52.010 Girish: Yeah.
18 00:04:52.010 ⇒ 00:04:53.240 Diego Makarausky: Hey, I’m good.
19 00:04:53.550 ⇒ 00:04:55.720 Ryon: Very excited, very excited today.
20 00:04:56.870 ⇒ 00:04:57.450 Diego Makarausky: Yeah.
21 00:04:57.450 ⇒ 00:05:00.620 Girish: Did you get a chance to see the intake app here?
22 00:05:00.620 ⇒ 00:05:18.820 Ryon: Yeah, yeah, so I was telling, Diego, you know, definitely some small things, but it’s a damn good start, you know what I mean? Like, it’s really good. Getting a lot of positive feedback from the team, I’ve shared more broadly with some different internal team members, and yeah, a lot of people are like, hey, this is good. But definitely build that refund feature for me. I’m gonna be charging…
23 00:05:18.820 ⇒ 00:05:32.370 Diego Makarausky: No, 100%. 100%, man. I need, and by the way, Surf can go behind the scenes, straight to the Stripe platform, and, you know, like, do it straight from there, like, so even…
24 00:05:32.390 ⇒ 00:05:44.470 Diego Makarausky: If you want to, like, do one today, let’s sync with him first, but you can get, like, an immediate cancellation over there on that payment, because we don’t want you to spend
25 00:05:44.830 ⇒ 00:05:48.849 Diego Makarausky: Millions of dollars, in test orders.
26 00:05:49.230 ⇒ 00:05:57.839 Ryon: I was thinking of grabbing a company card, but I feel like Josh and Adam would be like, why is there, like, thousands of dollars going out the door?
27 00:06:01.850 ⇒ 00:06:15.429 Ryon: And I actually am very excited now, because probably you guys are gonna figure this out really quickly, but now that everyone asks questions of me about, you know, basket intakes and functionality, I’m like, well, I don’t know! Here’s Diego.
28 00:06:15.430 ⇒ 00:06:17.769 Diego Makarausky: Not my problem anymore.
29 00:06:18.270 ⇒ 00:06:24.020 Ryon: Sort of, yes, but also in a good way, you know what I mean? Like, I’m very excited to be working with you guys on this, it’s a lot of fun.
30 00:06:25.250 ⇒ 00:06:32.540 Diego Makarausky: Yeah, thanks for all the help. Everything that a user can see over there, something that you built, so…
31 00:06:33.330 ⇒ 00:06:34.480 Diego Makarausky: You’re part of it.
32 00:06:34.750 ⇒ 00:06:36.830 Diego Makarausky: For the good and the worst.
33 00:06:39.770 ⇒ 00:06:46.130 Diego Makarausky: Let me ping the guys here, they, they send a message, like.
34 00:06:46.250 ⇒ 00:06:48.800 Diego Makarausky: 10 minutes ago, saying, hey, are you guys gonna be there?
35 00:06:51.870 ⇒ 00:07:03.710 Ryon: What is this AutoRx thing, Diego? Give me a bit of background here. Basic is asking us to create a visit type weight loss check-in to enable AutoRx. We would implement new tech. Yeah, so this is the check-in thing we were talking about the other day, isn’t it?
36 00:07:03.710 ⇒ 00:07:12.769 Diego Makarausky: Exactly, yeah, and that’s, like, the feature that BAS asks you to subscribe for it, and we mean that they’re gonna charge more for it.
37 00:07:12.970 ⇒ 00:07:24.600 Diego Makarausky: That will enable, like, those 6 months prescriptions, so as a doctor, they will prescribe you, like, hey, this is something for 6 months, and not just, like, for that specific treatment.
38 00:07:24.640 ⇒ 00:07:33.100 Diego Makarausky: And will enable us to charge if the… even if the patient pays, like, for one month treatment, like, to get auto-refills and things like that.
39 00:07:33.320 ⇒ 00:07:47.700 Diego Makarausky: So, yeah, they’re saying, hey, do you want it? First, sign a contract saying that you’re agreeing to pay me more, and then, if you really want me to enable that, send, like, like, this check-in visit, like.
40 00:07:47.700 ⇒ 00:07:54.100 Diego Makarausky: Full consent and no consent, so we can test if you have it implemented correctly.
41 00:07:54.820 ⇒ 00:08:00.050 Diego Makarausky: So yeah, I think just it’s, like, a matter of how we’re gonna trigger that, if it’s, like,
42 00:08:00.460 ⇒ 00:08:12.849 Diego Makarausky: Once a patient is almost without, like, treatment, we send an email with the, like, check-in link, so they can click, you know, go through a different intakes, submit their answers.
43 00:08:13.000 ⇒ 00:08:23.490 Diego Makarausky: just how you imagine that, that should be implemented. I can get the team working on that, and I just saw that Mitesh said, yes, let’s do it, like, 2 minutes ago, so…
44 00:08:23.840 ⇒ 00:08:25.499 Diego Makarausky: I think that’s a green light.
45 00:08:25.990 ⇒ 00:08:45.690 Ryon: There’s a couple of, non-starters, Diego, that I would say are things we’re definitely gonna see as blockers to get us MVP, the first of which is this, like, the team will flat out just say, no, we can’t do anything, because the 6-month prescription is what got us to, like, being able to, like, continue building. The second is the coupon code. Refunds, they don’t seem to care about that much. We’re gonna take your money and run kind of thing.
46 00:08:45.690 ⇒ 00:08:46.340 Ryon: Just kidding.
47 00:08:46.600 ⇒ 00:08:47.270 Ryon: Alright.
48 00:08:47.920 ⇒ 00:08:54.000 Ryon: Cool. So, real quick for everybody, has everybody got access to analytics?
49 00:08:54.180 ⇒ 00:08:55.660 Ryon: The analytics channel.
50 00:08:57.070 ⇒ 00:08:57.570 Ryon: Gosh.
51 00:08:57.570 ⇒ 00:09:00.990 Diego Makarausky: Thank you, you gave me access to it, I don’t know if Birish has…
52 00:09:01.750 ⇒ 00:09:03.429 Ryon: Just give Garrosh access to it.
53 00:09:10.810 ⇒ 00:09:11.540 Diego Makarausky: pain.
54 00:09:16.070 ⇒ 00:09:21.970 Ryon: Okay, so in that channel, I added in…
55 00:09:22.340 ⇒ 00:09:32.030 Ryon: I think a high-level game plan, for everybody on this. Spoke to Diego and Zoran about it. Here it is, kind of, like, outlined.
56 00:09:32.130 ⇒ 00:09:38.019 Ryon: At a high level. So, phase one, it sounds like tech team, you guys are gonna be building out the,
57 00:09:38.180 ⇒ 00:09:39.430 Ryon: custom events.
58 00:09:39.770 ⇒ 00:09:55.690 Ryon: from, for the intake to fire into the data layer, which is good. We’re gonna be going over that, you know, today, tomorrow, making sure that gets built out. I’m gonna create a comprehensive list of all the events and tags that need to be carried over, so at least we have a comprehensive list.
59 00:09:55.880 ⇒ 00:09:58.500 Ryon: Everything? Awash, yes, question?
60 00:09:59.750 ⇒ 00:10:06.069 Awaish Kumar: Yeah, I just wanted to confirm, like, are these events just directly going to Mixpanel, or…
61 00:10:06.250 ⇒ 00:10:09.040 Awaish Kumar: We are… we are looking to bring that in warehouse.
62 00:10:09.670 ⇒ 00:10:23.990 Ryon: Yeah, so right now, based on what’s R&I scope, the events are going to fire from the GTM data layer, the existing one we have, and they will fire to GA4 or to Mixpanel, right? Client-side events are all come through and go through a segment to Mixpanel, right?
63 00:10:25.640 ⇒ 00:10:38.110 Ryon: Server-to-server events, I still think we need to talk about that. I’m not sure. I don’t know. I think we definitely need to set that up so, like, delivery status and customer profiles and things like that that are feeding to MixedPanel, we’d have to set that up separate.
64 00:10:40.350 ⇒ 00:10:41.000 Awaish Kumar: Okay.
65 00:10:41.450 ⇒ 00:10:42.120 Ryon: Nope.
66 00:10:43.120 ⇒ 00:10:46.309 Ryon: As long as the taxonomy and the logic is the same.
67 00:10:46.700 ⇒ 00:10:57.699 Ryon: Or is close to the same as what we already have inside of the GTM container. This should be a fairly simple one-to-one transition, but, you know.
68 00:10:57.890 ⇒ 00:11:12.609 Ryon: Famous last words, right? Hopefully, it will be that simple, but we’ll see. If it isn’t, when Zarn and IQA, which is Phase 2, with Tag Assistant to confirm client-side events, we’ll end up with
69 00:11:13.410 ⇒ 00:11:26.840 Ryon: an idea of what needs to be built out or what needs to be changed, right? If there’s stuff that’s missing from the data layer, or anything like that, at all. So, yeah. Should be straightforward. I’m gonna be sharing example data layer
70 00:11:29.200 ⇒ 00:11:39.310 Ryon: JSON for each of the core events that we currently receive inside of Basque, so you guys can see it, and see what needs to be loaded into the data layer in that same thread.
71 00:11:39.780 ⇒ 00:11:42.579 Ryon: Zoran, am I missing anything? I think, I think I’m not.
72 00:11:43.280 ⇒ 00:11:47.160 Awaish Kumar: So… Yeah, I have another question.
73 00:11:47.780 ⇒ 00:11:49.030 Ryon: Good wish, yeah, go ahead.
74 00:11:49.030 ⇒ 00:12:08.849 Awaish Kumar: like, previously, when we were working on this, like, you wanted some events, like, that can capture the exact question, answer, time on the screen, and the sequence of the questions, and things like that. Yeah. And we want to do analysis on top of it. So, are you planning to do that analysis directly in MixFunnel, or…
75 00:12:09.160 ⇒ 00:12:15.750 Awaish Kumar: I’m asking so that, like, if those client-side events need to be in BigQuery as well.
76 00:12:16.140 ⇒ 00:12:19.190 Awaish Kumar: If you need to do the reporting on that in Omni.
77 00:12:19.500 ⇒ 00:12:28.800 Ryon: We should have them in BigQuery as well, just so we have them in data warehouse OASH, so yes, yes, technically. And…
78 00:12:28.970 ⇒ 00:12:32.980 Ryon: No. Most…
79 00:12:33.130 ⇒ 00:12:42.130 Ryon: analysis will be done in Mixpanel, so they need to be in Mixpanel, but yes, for redundancy, we need them in BigQuery as well, for Omni and other things as well.
80 00:12:43.800 ⇒ 00:12:46.110 Awaish Kumar: Okay, so I think, I don’t know how…
81 00:12:46.260 ⇒ 00:12:52.440 Awaish Kumar: Is the tech team going to send, those events directly… to MixPlanel.
82 00:12:52.750 ⇒ 00:12:58.679 Awaish Kumar: And BigCarrio is… is going to be through GFO, sorry, the Google Tag Manager.
83 00:12:58.680 ⇒ 00:13:05.790 Ryon: So… For Google Tag Manager, we can set up the events to fire to segment.
84 00:13:06.010 ⇒ 00:13:14.589 Ryon: for Mixpanel, that should be easy, right? So the client-side events should be easy, and we can set up the parameters that need to be saved and sent through from segment, from…
85 00:13:14.980 ⇒ 00:13:19.259 Ryon: GTM to segment to MixedPanel. For BigQuery, that’s…
86 00:13:19.260 ⇒ 00:13:20.819 Awaish Kumar: We need to…
87 00:13:20.820 ⇒ 00:13:21.850 Ryon: Yeah.
88 00:13:22.150 ⇒ 00:13:26.580 Awaish Kumar: to segment, and from segment, it can be also… can also go to BigQuery as well.
89 00:13:27.550 ⇒ 00:13:29.459 Ryon: Okay, so then…
90 00:13:30.430 ⇒ 00:13:42.880 Ryon: I guess I’m gonna lean on Zaron to answer this one, because I think we have some destinations originally built out in BigQuery for the old intake that… the version that I tried to build back in late Q4.
91 00:13:42.880 ⇒ 00:13:51.809 Ryon: Right? But I don’t think those destinations are being used anymore. We can convert them and just use the same ones if we want to, or we can create new ones, it’s really up to you guys.
92 00:13:56.590 ⇒ 00:13:59.279 Ryon: Any objections? Any thoughts on that?
93 00:14:00.470 ⇒ 00:14:10.490 Awaish Kumar: No, not from my side. If… as long as the data comes to BigQuery, we can… we already have the stations set up in segment, we can use those, and create a new data set, and just…
94 00:14:10.640 ⇒ 00:14:11.949 Awaish Kumar: Apply the data there.
95 00:14:12.250 ⇒ 00:14:12.850 Ryon: Okay.
96 00:14:12.970 ⇒ 00:14:31.239 Ryon: Let me call this file out, because I think it’s going to be very useful with setting up the custom events. So, this file inside of Git here, which is inside of the Tri-Eden intake project, this is what was originally built out as the telemetry for the intake system that we tried to build a while back.
97 00:14:31.240 ⇒ 00:14:39.839 Ryon: Right? So here’s all of the different events that were set up and that occurred. Many of these events are…
98 00:14:41.190 ⇒ 00:14:55.049 Ryon: over and above what exists in BASC. I think Awash was calling out this one here as question and answer is ones that’s over and above what’s available in BASC. Some of them are not, like add shipping info, begin checkout, things like this.
99 00:14:55.220 ⇒ 00:15:01.050 Ryon: So, yeah, this is a good list of events. If there’s others that need to be added,
100 00:15:01.130 ⇒ 00:15:19.919 Ryon: obviously, like, for example, you know, the purchase event, some of these other key events, like the thank you page, etc, we can build those out as well, and Zara and I can call them out. Again, I’m trying to combine a checklist here and get it all loaded and set up so we can get that checklist completed, and we can say, like, yep, these are the events, these are the things that need to be built.
101 00:15:20.000 ⇒ 00:15:22.999 Ryon: But this file’s a good starting point, I would say.
102 00:15:23.560 ⇒ 00:15:24.560 Ryon: Cool.
103 00:15:28.060 ⇒ 00:15:34.299 Ryon: Alrighty, am I missing anything, Zarn?
104 00:15:35.780 ⇒ 00:15:36.430 Zoran Selinger: Nope.
105 00:15:36.640 ⇒ 00:15:37.500 Ryon: No? Okay.
106 00:15:37.500 ⇒ 00:15:40.380 Zoran Selinger: I think we… that’s enough for us to start.
107 00:15:45.530 ⇒ 00:15:47.579 Ryon: Yeah, Diego, are we good?
108 00:15:48.080 ⇒ 00:15:48.730 Ryon: Seemed good.
109 00:15:48.730 ⇒ 00:15:59.319 Diego Makarausky: I just wanted to check on what you guys are gonna need from our development team. We created… we had this conversation earlier today with Surf.
110 00:15:59.410 ⇒ 00:16:10.519 Diego Makarausky: So, because of that, we created, like, an epic for it, and a spike that most of this spike might be answered.
111 00:16:10.990 ⇒ 00:16:18.649 Diego Makarausky: By Ryan’s comment, I’m trying to share my screen here, I don’t know if, I’m gonna be allowed to. Can you guys see it?
112 00:16:21.150 ⇒ 00:16:37.059 Diego Makarausky: create a document list of events, so with that document that Ryan just mentioned, probably we’ll already have some of these answers. And we have here, like, the intake improv that you guys were seeing,
113 00:16:37.470 ⇒ 00:16:55.310 Diego Makarausky: as the patient will go through the intake, these are the questions that we need to be tracked. Once they submit an email down the road, we’ll have them being captured here as a lead, then a customer, so I think those are a couple of questions that
114 00:16:55.310 ⇒ 00:17:09.819 Diego Makarausky: Brian mentioned on the channel, but just wanted to see if there’s anything here that, that you guys need to check, if you have any questions, anything that we can, like, elaborate, or maybe put some light on.
115 00:17:11.970 ⇒ 00:17:18.530 Ryon: Can you add my email to this admin section, Diego? I think I had it, but then I tried logging the other day, but I lost it.
116 00:17:18.530 ⇒ 00:17:19.230 Diego Makarausky: Sure.
117 00:17:20.119 ⇒ 00:17:20.859 Diego Makarausky: Right away.
118 00:17:21.470 ⇒ 00:17:26.310 Ryon: He’s right there. Why couldn’t I lock it? It’s right there on the screen. Anyway…
119 00:17:26.319 ⇒ 00:17:26.699 Girish: do it.
120 00:17:27.069 ⇒ 00:17:31.390 Ryon: Yeah, I feel like it’s just user error on my part. Okay.
121 00:17:32.950 ⇒ 00:17:34.069 Ryon: Send the link…
122 00:17:34.070 ⇒ 00:17:34.520 Diego Makarausky: you need.
123 00:17:34.520 ⇒ 00:17:45.789 Ryon: Send the… send the spike and send the epic to the analytics channel, the thread, Diego. I’m gonna start adding stuff there, like tickets and things. I think that’s what Zoran and I.
124 00:17:45.790 ⇒ 00:17:46.199 Diego Makarausky: I know.
125 00:17:46.790 ⇒ 00:17:52.779 Ryon: That’s… that can be our immediate contribution, and, or mainly my immediate contribution.
126 00:17:52.980 ⇒ 00:17:59.369 Ryon: Outside of that, I think we’re good, we just need to get all the tickets created.
127 00:18:01.970 ⇒ 00:18:02.720 Diego Makarausky: Alright.
128 00:18:03.390 ⇒ 00:18:15.169 Diego Makarausky: So, yeah, let us know if you guys need anything from our side. Girish here is the engineering manager, so anything that you guys need from the development team, he’ll be
129 00:18:15.170 ⇒ 00:18:29.569 Diego Makarausky: sharing with a developer and getting that done as soon as possible, and yeah, this is, like, a main priority for us right now, because you guys know, Adam wants this out as soon as possible, and he doesn’t want it to be out
130 00:18:29.620 ⇒ 00:18:39.069 Diego Makarausky: before, we can track everything that’s happening on the intake patient portal and everything else, right? So, anything that you guys need from us?
131 00:18:39.520 ⇒ 00:18:40.780 Diego Makarausky: Yes, let us know.
132 00:18:41.360 ⇒ 00:18:41.770 Ryon: Okay.
133 00:18:41.770 ⇒ 00:18:57.109 Diego Makarausky: One last thing from my side, Ryan mentioned the analytics channel, so maybe we can keep all of this discussion over there on this one channel, so, we don’t get, like, mixed stuff being sent in different places, so…
134 00:18:57.460 ⇒ 00:19:01.290 Diego Makarausky: we can focus on that analytics channel over there, I’ll tell you.
135 00:19:02.430 ⇒ 00:19:03.010 Ryon: Okay.
136 00:19:03.010 ⇒ 00:19:04.110 Diego Makarausky: not underchanneled.
137 00:19:04.820 ⇒ 00:19:05.720 Ryon: Excellent.
138 00:19:06.010 ⇒ 00:19:10.550 Ryon: I’m gonna be sharing more details here in a bit, and then I’ll start adding tickets today. Everything good, guys?
139 00:19:12.340 ⇒ 00:19:13.200 Diego Makarausky: Alright.
140 00:19:13.200 ⇒ 00:19:13.740 Ryon: Awesome.
141 00:19:13.740 ⇒ 00:19:16.480 Diego Makarausky: I saw a few other studies, go and go.
142 00:19:16.750 ⇒ 00:19:18.479 Ryon: Alright. Thanks, guys.
143 00:19:20.120 ⇒ 00:19:20.710 Diego Makarausky: Bye.