Meeting Title: Phoenix Product Launch Planning Sync Date: 2026-02-05 Meeting participants: Greg Stoutenburg, Nandika Jhunjhunwala
WEBVTT
1 00:02:34.970 ⇒ 00:02:36.210 Greg Stoutenburg: Hey, Nantika.
2 00:02:36.210 ⇒ 00:02:37.889 Nandika Jhunjhunwala: Hi, how’s it going?
3 00:02:37.890 ⇒ 00:02:38.989 Greg Stoutenburg: Doing well, how are you?
4 00:02:39.660 ⇒ 00:02:48.880 Nandika Jhunjhunwala: Good, good. Yeah, just wanted to thank, after a conversation, I spoke to, multiple people internally, and
5 00:02:49.030 ⇒ 00:03:03.509 Nandika Jhunjhunwala: I apologize for all the confusion with, like, what’s going into product and not. I think there’s a lot of confusion internally as well, as we, like, go towards launching the new version of, like, default, and…
6 00:03:03.510 ⇒ 00:03:06.560 Greg Stoutenburg: Yeah. I just wanted to preface this by saying that.
7 00:03:06.630 ⇒ 00:03:18.670 Nandika Jhunjhunwala: a lot of what’s gonna go into, like, version 1 of Phoenix is very different than how Phoenix would look, like, even, like, a week later. So I think what they’re doing is iteratively shipping new features, and
8 00:03:18.670 ⇒ 00:03:27.249 Nandika Jhunjhunwala: starting off with, like, a list of, like, 5 or 6 features that they’re gonna have on day one, and then they’re gonna add on to that. Which is why I think, like.
9 00:03:27.460 ⇒ 00:03:29.310 Nandika Jhunjhunwala: I was speaking to
10 00:03:29.420 ⇒ 00:03:33.610 Nandika Jhunjhunwala: the product lead, and he said that a lot of screens we’re looking at in Figma are…
11 00:03:33.840 ⇒ 00:03:52.769 Nandika Jhunjhunwala: not how Phoenix is gonna look on day one. So going off of that assumption, like, that’s why, like, I’m not being able to answer a lot of your questions and our questions as we go through, like, the user journeys and the onboarding flow, is, like, a lot of those screens are not yet implemented, or are going to be implemented anytime soon, so…
12 00:03:52.770 ⇒ 00:03:53.520 Greg Stoutenburg: Okay.
13 00:03:53.520 ⇒ 00:03:59.689 Nandika Jhunjhunwala: One of those questions that… You asked about was, like, the tool enrichment screen.
14 00:03:59.890 ⇒ 00:04:18.700 Nandika Jhunjhunwala: So, things like that are not yet implemented, like, what tool, widgets we’re gonna offer them, and so on and so forth. The other thing that’s not, I think, going to be part of Phoenix is the Ask Anything sort of query bar. I did not know that until yesterday.
15 00:04:18.700 ⇒ 00:04:20.740 Greg Stoutenburg: Good, that’s a good one. Yeah.
16 00:04:20.740 ⇒ 00:04:25.160 Nandika Jhunjhunwala: Yeah. Yeah. So things like that are,
17 00:04:25.480 ⇒ 00:04:36.629 Nandika Jhunjhunwala: coming up, like, because I’ve just recently joined as well, and nobody besides the product and the engineering team knows what’s going to be in Phoenix so far.
18 00:04:36.630 ⇒ 00:04:37.409 Greg Stoutenburg: Yeah, true.
19 00:04:37.410 ⇒ 00:04:51.320 Nandika Jhunjhunwala: And I’m trying to align with them on that. But what I do have is a list of things that are going to be in Phoenix. I think pretty much, like, 85% there.
20 00:04:51.620 ⇒ 00:04:54.150 Nandika Jhunjhunwala: I can share that with you.
21 00:04:54.150 ⇒ 00:04:55.310 Greg Stoutenburg: Great.
22 00:04:56.010 ⇒ 00:05:05.080 Nandika Jhunjhunwala: And maybe we can chat through it. I… I just very recently got access to it as well, so I’m gonna send you the Notion document.
23 00:05:09.770 ⇒ 00:05:13.740 Nandika Jhunjhunwala: Sort of the biggest push is towards the common data model.
24 00:05:13.810 ⇒ 00:05:31.899 Nandika Jhunjhunwala: So for Phoenix, they’re… they’re gonna sync data from forms, from their CRM, from, like, any website visit, and anything else they may enrich for in a workflow. So all that data is going to be captured in a common data model.
25 00:05:31.970 ⇒ 00:05:36.680 Nandika Jhunjhunwala: And they have the ability to, like, prioritize data based on, like, where it’s coming from.
26 00:05:36.760 ⇒ 00:05:52.270 Nandika Jhunjhunwala: and pick, like, its sources, and pick, like, if they prefer an enrichment provider, and that’s, like, sort of, like, the main core offering of Phoenix, and that’s what they’re focusing on. And then going off of that, there’s workflows, and then tables. Tables is sort of, like, if you’re familiar with Clay.
27 00:05:52.600 ⇒ 00:05:53.200 Greg Stoutenburg: Yup.
28 00:05:53.200 ⇒ 00:06:07.060 Nandika Jhunjhunwala: our version of Clay within the product, and that’s, like, I think the starting point for Phoenix, I’m realizing. So maybe we can… we can discuss more on, like, the workflow and enrichment, and, like.
29 00:06:07.230 ⇒ 00:06:21.059 Nandika Jhunjhunwala: Maybe, instrumenting the default OS screen still, and, like, the widgets we’re gonna have access to. Yeah. And any granularity that we’re missing currently, we can maybe just skip over it and come back to it later in terms of the tracking plan.
30 00:06:21.920 ⇒ 00:06:29.190 Greg Stoutenburg: Yes, absolutely. Yeah, solid update, that’s very helpful. Okay, so just, like, picking…
31 00:06:29.640 ⇒ 00:06:33.629 Greg Stoutenburg: A couple of things that we know will ship.
32 00:06:33.770 ⇒ 00:06:37.420 Greg Stoutenburg: core data… you said core data model…
33 00:06:37.570 ⇒ 00:06:38.070 Nandika Jhunjhunwala: Yes.
34 00:06:38.070 ⇒ 00:06:39.680 Greg Stoutenburg: and tables.
35 00:06:39.930 ⇒ 00:06:41.469 Greg Stoutenburg: Start there? Yeah.
36 00:06:41.470 ⇒ 00:06:44.290 Nandika Jhunjhunwala: Yes. And the other thing is Pixel.
37 00:06:44.720 ⇒ 00:06:58.659 Nandika Jhunjhunwala: So, I’m not too familiar with Pixel, and I’m gonna, like, educate myself on that. Okay. But Pixel is basically, like, a de-anonymization tool that we have within Phoenix, and you can do more stuff with it, like, if someone, like.
38 00:06:58.770 ⇒ 00:07:07.189 Nandika Jhunjhunwala: sort of types in a form, and they don’t hit submit, Pixel has the capability to, like, recognize who did that, and it can trigger a workflow.
39 00:07:07.190 ⇒ 00:07:07.810 Greg Stoutenburg: Right.
40 00:07:07.810 ⇒ 00:07:20.640 Nandika Jhunjhunwala: based on, like, oh, like, someone typed in the form, but they didn’t book a meeting, so go reach out to them, sort of thing. So Pixel is, like, basically like a UTM, with additional capabilities built on top of it.
41 00:07:20.640 ⇒ 00:07:21.110 Greg Stoutenburg: Okay.
42 00:07:21.110 ⇒ 00:07:29.159 Nandika Jhunjhunwala: So I will, like, educate myself exactly on what Pixel does, and I’m not sure if, like, that’s something we can track, because it’s not, like…
43 00:07:29.330 ⇒ 00:07:29.840 Greg Stoutenburg: Yep.
44 00:07:29.840 ⇒ 00:07:34.839 Nandika Jhunjhunwala: Basically, in the product, but more, like, on the back end.
45 00:07:34.970 ⇒ 00:07:35.350 Greg Stoutenburg: Okay.
46 00:07:35.350 ⇒ 00:07:39.549 Nandika Jhunjhunwala: And then I think, like, workflows and the core data model.
47 00:07:39.760 ⇒ 00:07:49.400 Nandika Jhunjhunwala: might be good screens to start off with, and, like, the default OS. And I think the rest of, like, the granularity of those events that
48 00:07:49.810 ⇒ 00:07:54.739 Nandika Jhunjhunwala: we’re missing, we can just sort of, like, make it, like, TBD or something.
49 00:07:54.740 ⇒ 00:07:57.110 Greg Stoutenburg: Yeah, we can do that. We can absolutely do that.
50 00:07:57.360 ⇒ 00:08:03.509 Greg Stoutenburg: Yeah. Okay, do you expect the onboarding flow is gonna follow what the designs show?
51 00:08:03.920 ⇒ 00:08:04.460 Nandika Jhunjhunwala: So…
52 00:08:04.460 ⇒ 00:08:05.070 Greg Stoutenburg: solid.
53 00:08:05.280 ⇒ 00:08:06.530 Nandika Jhunjhunwala: No, so…
54 00:08:06.530 ⇒ 00:08:07.350 Greg Stoutenburg: Unfortunately.
55 00:08:09.170 ⇒ 00:08:09.950 Greg Stoutenburg: I just wanted to clarify.
56 00:08:09.950 ⇒ 00:08:11.370 Nandika Jhunjhunwala: Yes, so I…
57 00:08:11.370 ⇒ 00:08:11.750 Greg Stoutenburg: Beautiful.
58 00:08:11.750 ⇒ 00:08:20.260 Nandika Jhunjhunwala: I synced with the product lead, and I was, like, asking him all these questions about onboarding, and he’s like… he’s like, wait a second, this is not what onboarding might even look like.
59 00:08:20.270 ⇒ 00:08:34.830 Nandika Jhunjhunwala: So I think he also mentioned, but again, these are not videos I know of, and Caitlin is out, and when she’s back, like, I’ll bother her a ton about this, but I think every single step in the onboarding is meant to be, like, skippable.
60 00:08:34.880 ⇒ 00:08:43.589 Nandika Jhunjhunwala: Okay. So, like, you can be prompted to connect your CRM, but you can skip it. You can be prompted to connect your calendar, but you can skip it. You can be prompted to, like.
61 00:08:43.890 ⇒ 00:08:59.769 Nandika Jhunjhunwala: tell more about yourself, or, like, your branding choices, and all of that, but you can skip it. Again, those details are still in the air. The only two people working on onboarding are, like, Kate and then the founder, Nico. So maybe Yami, like, comes into office, today.
62 00:08:59.790 ⇒ 00:09:08.799 Nandika Jhunjhunwala: before our meeting, I’ll try to, like, catch him and ask him final onboarding thoughts, and, like, what… if he has, like, a version of the onboarding flow we can refer to.
63 00:09:08.880 ⇒ 00:09:14.350 Nandika Jhunjhunwala: So, I, I apologize, I think, like.
64 00:09:14.760 ⇒ 00:09:19.300 Nandika Jhunjhunwala: A lot of it is still up in the air, and we’re basically working with,
65 00:09:19.450 ⇒ 00:09:23.629 Nandika Jhunjhunwala: a black hole, and, like, what I can also, like, I would try to advocate for is, like.
66 00:09:23.820 ⇒ 00:09:33.669 Nandika Jhunjhunwala: getting access to, like, a version of Phoenix maybe you and I can log into, and I think that’s gonna be most helpful, whenever the team is to that point that they can do that,
67 00:09:33.800 ⇒ 00:09:37.379 Nandika Jhunjhunwala: I will try to get you login access as soon as I can.
68 00:09:37.580 ⇒ 00:09:44.839 Greg Stoutenburg: Cool, yeah, great, that’s very helpful. Yeah, thanks for that. So, what I’ll do then is,
69 00:09:45.240 ⇒ 00:09:46.920 Greg Stoutenburg: The milestones that we have.
70 00:09:47.160 ⇒ 00:10:04.309 Greg Stoutenburg: those are… we can keep those, we can instrument all those. I’ll just… I put a pause on everything that I mapped out for the onboarding flow. I’ll continue to think through what some of the event properties should be, and then, you know, we’ll just revise, or trim or add as we need to.
71 00:10:04.670 ⇒ 00:10:08.630 Greg Stoutenburg: For default OS management,
72 00:10:08.850 ⇒ 00:10:21.279 Greg Stoutenburg: probably can go ahead and put those in the tracking plan, because I only, like I said yesterday, I only put 4 events in for that anyway, like, you know, widget modified, like, those will apply. Of course. You can have them in the tracking plan.
73 00:10:21.280 ⇒ 00:10:21.970 Nandika Jhunjhunwala: Yeah.
74 00:10:22.230 ⇒ 00:10:25.489 Greg Stoutenburg: When we see what those designs look like, we’ll.
75 00:10:25.490 ⇒ 00:10:25.970 Nandika Jhunjhunwala: Yep.
76 00:10:25.970 ⇒ 00:10:27.990 Greg Stoutenburg: We’ll update as necessary.
77 00:10:28.360 ⇒ 00:10:39.380 Nandika Jhunjhunwala: And definitely, even if those, like, events are not instrumented today, or as, like, soon, these are gonna be events that we implement later on, for sure. So, we can absolutely keep them.
78 00:10:39.380 ⇒ 00:10:53.640 Greg Stoutenburg: Yeah, and the tracking plan is going to be, in part, a project management tool for the implementations, right? So there will be a column that’s like, has this been instrumented? And, you know, yes or no. And so, as long as we know
79 00:10:53.640 ⇒ 00:11:09.010 Greg Stoutenburg: what the workflows are, regardless of what they look like. We can do… we can continue moving forward on the tracking. It’s where there’s uncertainty about what the workflow will be that we then go, okay, let’s… let’s not work on this part yet.
80 00:11:09.140 ⇒ 00:11:19.229 Greg Stoutenburg: So, okay, that sounds, that sounds good. I have a little time between now and when we’ll meet to look through the Notion doc you provided.
81 00:11:19.390 ⇒ 00:11:22.989 Greg Stoutenburg: And I might even be able to start doing some mapping just based off of that, even without design, so…
82 00:11:22.990 ⇒ 00:11:23.350 Nandika Jhunjhunwala: For sure.
83 00:11:23.350 ⇒ 00:11:27.820 Greg Stoutenburg: Yeah, that sounds good. We’ll just keep moving forward where there’s, you know, we’ll just have to keep…
84 00:11:28.050 ⇒ 00:11:29.950 Greg Stoutenburg: iterating. Sounds good.
85 00:11:29.950 ⇒ 00:11:30.650 Nandika Jhunjhunwala: Yeah.
86 00:11:30.650 ⇒ 00:11:33.240 Greg Stoutenburg: I’m flexible. Cool, yeah, alright.
87 00:11:33.240 ⇒ 00:11:36.869 Nandika Jhunjhunwala: No, thank you so much for being flexible, and I apologize for being too late.
88 00:11:37.150 ⇒ 00:11:38.540 Greg Stoutenburg: Just wanted, you know, empower the.
89 00:11:38.540 ⇒ 00:11:41.250 Nandika Jhunjhunwala: Alright, save you hours. Bye.