WEBVTT

1
00:00:04.200 --> 00:00:08.320
<v Speaker 1>This is the Full Funnel bTB Marketing podcast, brought to

2
00:00:08.359 --> 00:00:10.320
<v Speaker 1>you by full Funnel dot io.

3
00:00:11.240 --> 00:00:15.720
<v Speaker 2>Let's starve well join us of course.

4
00:00:15.800 --> 00:00:18.359
<v Speaker 1>Yeah, thank you so much for having me. I'm psyched

5
00:00:18.359 --> 00:00:20.519
<v Speaker 1>to dive into anything account based.

6
00:00:21.960 --> 00:00:27.039
<v Speaker 3>Absolutely. One thing that I would love to kick off

7
00:00:27.079 --> 00:00:32.079
<v Speaker 3>with is the fact that I have seen you mentioned

8
00:00:32.079 --> 00:00:35.560
<v Speaker 3>on your linked and profile. So when you are leading

9
00:00:35.640 --> 00:00:39.520
<v Speaker 3>the Global Enterprise Demand GAN at Google, you were able

10
00:00:39.560 --> 00:00:42.960
<v Speaker 3>to increase SCL quality score from such a five percent

11
00:00:43.039 --> 00:00:46.520
<v Speaker 3>to age of five percent in under one year by

12
00:00:46.679 --> 00:00:51.399
<v Speaker 3>partner with the SDR team right developing the shared okayrs

13
00:00:51.600 --> 00:00:56.960
<v Speaker 3>and also create this cross functional alignment what I feel

14
00:00:57.560 --> 00:01:00.479
<v Speaker 3>and I feel this is kind of the universe problem

15
00:01:00.560 --> 00:01:06.159
<v Speaker 3>for most bit of B companies, right, but simply don't

16
00:01:06.159 --> 00:01:09.280
<v Speaker 3>have this cross functional alignment. Not just to say that

17
00:01:09.640 --> 00:01:13.120
<v Speaker 3>we often fight for the credit, right, because this is

18
00:01:13.200 --> 00:01:15.760
<v Speaker 3>kind of the typical bit of the setup. Looks like

19
00:01:16.000 --> 00:01:18.879
<v Speaker 3>marketing needs to prove the marketing so are traving, the

20
00:01:18.959 --> 00:01:22.719
<v Speaker 3>sales needs to prove the sales aurce aving to kind

21
00:01:22.719 --> 00:01:25.680
<v Speaker 3>of measure everything by the last click attribution, and that's it.

22
00:01:25.879 --> 00:01:31.480
<v Speaker 3>So well, I would love to dive deeper and understand

23
00:01:32.439 --> 00:01:35.879
<v Speaker 3>The first thing is how do you define SQL quality score?

24
00:01:37.040 --> 00:01:38.040
<v Speaker 2>Yeah, good question.

25
00:01:38.200 --> 00:01:42.959
<v Speaker 1>So SQL quality score, think about your your typical score

26
00:01:43.239 --> 00:01:46.680
<v Speaker 1>is going to be probably driven off of a band

27
00:01:46.879 --> 00:01:50.159
<v Speaker 1>like budget, authority, need timing, and it's going to be

28
00:01:50.239 --> 00:01:54.239
<v Speaker 1>driven by your SDR team. When I was at Google,

29
00:01:54.560 --> 00:01:57.760
<v Speaker 1>you know, granted, this was you know, probably four or

30
00:01:57.760 --> 00:02:00.079
<v Speaker 1>five years ago now, and we were doing this, so

31
00:02:00.159 --> 00:02:02.799
<v Speaker 1>we didn't have all of the fancy AI stuff.

32
00:02:02.560 --> 00:02:03.319
<v Speaker 2>That we have today.

33
00:02:03.760 --> 00:02:09.680
<v Speaker 1>But quality was a combination of marketing data and sales data.

34
00:02:10.080 --> 00:02:14.680
<v Speaker 1>And one of the particular metrics we've looked at obsessively

35
00:02:15.319 --> 00:02:19.280
<v Speaker 1>was the what was called a rejection reason, so other

36
00:02:19.319 --> 00:02:23.039
<v Speaker 1>companies might call it like disqualification reason, but it's a

37
00:02:23.280 --> 00:02:28.000
<v Speaker 1>basically a sub field in salesforce. When an SDR was

38
00:02:28.039 --> 00:02:31.599
<v Speaker 1>on the phone talking to a marketing qualified lead, they

39
00:02:31.680 --> 00:02:36.000
<v Speaker 1>had to market as you know, for six different stages

40
00:02:36.039 --> 00:02:39.960
<v Speaker 1>to either progress it forward or you know, disqualify it.

41
00:02:40.319 --> 00:02:42.680
<v Speaker 1>And so one of those was disqualification, and then we

42
00:02:42.719 --> 00:02:46.479
<v Speaker 1>had a whole sub field of reasons that they had

43
00:02:46.479 --> 00:02:49.879
<v Speaker 1>to select for why they disqualified it. And that data

44
00:02:49.960 --> 00:02:54.439
<v Speaker 1>alone became the most important part of this SQL quality

45
00:02:54.520 --> 00:02:58.960
<v Speaker 1>score because we could see, you know, if marketing registered

46
00:02:59.000 --> 00:03:02.000
<v Speaker 1>a lead as a market and qualified lead, meaning they

47
00:03:02.080 --> 00:03:06.080
<v Speaker 1>met the marketing scoring criteria of you know, ICP fit

48
00:03:06.400 --> 00:03:10.599
<v Speaker 1>or right job title or really right persona, and then

49
00:03:10.639 --> 00:03:14.400
<v Speaker 1>they hit some kind of behavioral engagement score. Marketing thought

50
00:03:14.400 --> 00:03:16.080
<v Speaker 1>it was good, right, And so this is where you

51
00:03:16.120 --> 00:03:19.599
<v Speaker 1>get humbled because marketing said we created the MQL.

52
00:03:19.599 --> 00:03:20.520
<v Speaker 2>Here you go sales.

53
00:03:20.960 --> 00:03:23.000
<v Speaker 1>But then when you get a feedback loop from sales

54
00:03:23.000 --> 00:03:27.319
<v Speaker 1>that says, we just qualified this because it's the wrong persona. Now,

55
00:03:27.360 --> 00:03:30.000
<v Speaker 1>all of a sudden, that data got us thinking, well,

56
00:03:30.199 --> 00:03:33.240
<v Speaker 1>what happened because on our side it was the right persona.

57
00:03:33.800 --> 00:03:36.919
<v Speaker 1>And so, you know, small example, but you know, let's

58
00:03:36.960 --> 00:03:40.479
<v Speaker 1>say in this case, they were selling to a purely

59
00:03:40.599 --> 00:03:45.240
<v Speaker 1>it right, nothing engineering, nothing infrastructure, nothing data, just pure

60
00:03:45.280 --> 00:03:49.800
<v Speaker 1>information technology. When we would send them a VP of infrastructure,

61
00:03:50.360 --> 00:03:54.680
<v Speaker 1>our MQL scoring would pick up and see VP technology

62
00:03:54.759 --> 00:03:58.120
<v Speaker 1>title cool MQL. But then sales would come back and say,

63
00:03:58.120 --> 00:04:00.319
<v Speaker 1>we can't sell that person. We can never sell that person.

64
00:04:00.360 --> 00:04:03.199
<v Speaker 1>They don't buy you know, chromebooks in this particular case.

65
00:04:04.680 --> 00:04:08.919
<v Speaker 1>So that that feedback loop was really key. And you

66
00:04:08.960 --> 00:04:11.000
<v Speaker 1>know t L d R there is you know, my team,

67
00:04:11.039 --> 00:04:13.800
<v Speaker 1>and we ended up going through thousands and thousands of

68
00:04:13.919 --> 00:04:16.839
<v Speaker 1>m q ls manually based on all of these rejection

69
00:04:16.959 --> 00:04:20.959
<v Speaker 1>reasons from the sales team and and basically figured out that,

70
00:04:21.199 --> 00:04:23.879
<v Speaker 1>you know, our m QL scores weren't as good as

71
00:04:23.879 --> 00:04:28.000
<v Speaker 1>we thought they were, and we had to, you know,

72
00:04:28.079 --> 00:04:30.319
<v Speaker 1>kind of take one on the chin and say, okay,

73
00:04:30.319 --> 00:04:31.360
<v Speaker 1>we've got to go back to.

74
00:04:31.279 --> 00:04:33.560
<v Speaker 2>The drawing board and fix some stuff on the marketing

75
00:04:33.600 --> 00:04:35.800
<v Speaker 2>side lot.

76
00:04:36.000 --> 00:04:39.279
<v Speaker 3>And was the hindsight what would you say, is the

77
00:04:39.399 --> 00:04:42.879
<v Speaker 3>road treason? Is the road problem of all of this? Right,

78
00:04:42.920 --> 00:04:46.279
<v Speaker 3>because it doesn't start, let's say, when we have the

79
00:04:46.279 --> 00:04:49.399
<v Speaker 3>fight for the for the even for the quality of

80
00:04:49.439 --> 00:04:53.079
<v Speaker 3>that specifically, right would say that? Is it kind of

81
00:04:53.199 --> 00:04:57.800
<v Speaker 3>the default GM playbook or anson else?

82
00:04:59.120 --> 00:05:00.519
<v Speaker 2>Yeah, it's a question.

83
00:05:00.759 --> 00:05:03.920
<v Speaker 1>I think two things come to mind, and one is

84
00:05:04.399 --> 00:05:09.519
<v Speaker 1>the the traditional enterprise marketing and sales, you know, the

85
00:05:09.600 --> 00:05:14.839
<v Speaker 1>GTM motion I think is fundamentally.

86
00:05:15.720 --> 00:05:21.160
<v Speaker 2>Not broken, but flawed. Right. I think the idea of marketing.

87
00:05:21.279 --> 00:05:24.560
<v Speaker 1>Services this first half of the funnel and they work

88
00:05:24.680 --> 00:05:27.480
<v Speaker 1>towards a metric like an MQL, and then they throw

89
00:05:27.519 --> 00:05:29.639
<v Speaker 1>it over the fence to sales and then you know,

90
00:05:29.720 --> 00:05:32.439
<v Speaker 1>sales takes it from there and they own the back

91
00:05:32.480 --> 00:05:34.759
<v Speaker 1>half of the funnel. And then you can even think

92
00:05:34.800 --> 00:05:37.959
<v Speaker 1>about customer success. If we're talking about a software company,

93
00:05:38.480 --> 00:05:43.439
<v Speaker 1>I think that that linear progression is not it's flawed, right,

94
00:05:43.680 --> 00:05:47.279
<v Speaker 1>because it allows the teams to just get focused on

95
00:05:47.319 --> 00:05:50.279
<v Speaker 1>that one thing that they're responsible for and then they

96
00:05:50.319 --> 00:05:53.959
<v Speaker 1>can forget about it. And so in this case, you know,

97
00:05:54.040 --> 00:05:56.199
<v Speaker 1>I was I was guilty of doing that, right, Like

98
00:05:56.279 --> 00:06:00.600
<v Speaker 1>I had to actually humble myself as a market leader

99
00:06:00.680 --> 00:06:02.639
<v Speaker 1>and say what I'm doing is wrong.

100
00:06:02.920 --> 00:06:03.519
<v Speaker 2>I've got to.

101
00:06:03.399 --> 00:06:06.279
<v Speaker 1>Trust my peers on the sales side. I've got to

102
00:06:06.279 --> 00:06:08.560
<v Speaker 1>take their feedback, and then I have to do something

103
00:06:08.600 --> 00:06:11.480
<v Speaker 1>about it. And so at a macro level, I think

104
00:06:11.519 --> 00:06:16.360
<v Speaker 1>that is present. And then at a micro level, especially

105
00:06:16.639 --> 00:06:21.279
<v Speaker 1>in enterprises or more mature go to market teams where

106
00:06:21.399 --> 00:06:25.720
<v Speaker 1>let's just say you're you're dealing with, you know, thousands

107
00:06:25.759 --> 00:06:29.480
<v Speaker 1>of leads on a monthly basis like five ten, you know,

108
00:06:29.519 --> 00:06:31.600
<v Speaker 1>even more, some of these enterprise teams are dealing with

109
00:06:31.680 --> 00:06:36.120
<v Speaker 1>millions per quarter, and so when you have that much volume,

110
00:06:37.040 --> 00:06:39.920
<v Speaker 1>it's easy to just like sit back and hide behind

111
00:06:40.000 --> 00:06:42.639
<v Speaker 1>all the screens and the dashboards and the trends and

112
00:06:42.720 --> 00:06:46.279
<v Speaker 1>the graphs and not actually get into the data. So

113
00:06:46.600 --> 00:06:50.000
<v Speaker 1>one thing I advise all time is whether you're dealing

114
00:06:50.000 --> 00:06:53.560
<v Speaker 1>with a thousand leads or a million. Just go into

115
00:06:53.600 --> 00:06:55.279
<v Speaker 1>the data, like you've got to go in and look

116
00:06:55.319 --> 00:06:57.120
<v Speaker 1>at the lead profile. You have to look at the

117
00:06:57.160 --> 00:07:00.240
<v Speaker 1>sales notes. You have to look at the behavior of

118
00:07:00.279 --> 00:07:05.199
<v Speaker 1>those contacts that they conducted with marketing and the different

119
00:07:05.319 --> 00:07:08.000
<v Speaker 1>activities and that sort of thing. Like you have to

120
00:07:08.360 --> 00:07:12.000
<v Speaker 1>get close to it because that's where the real insights are.

121
00:07:12.120 --> 00:07:15.040
<v Speaker 1>I think, like the ones we're talking about that really matter,

122
00:07:16.000 --> 00:07:18.399
<v Speaker 1>and you'll notice you'll notice the good, the bad, and

123
00:07:18.439 --> 00:07:18.879
<v Speaker 1>the ugly.

124
00:07:19.000 --> 00:07:21.120
<v Speaker 2>If you do that, love it.

125
00:07:21.199 --> 00:07:24.560
<v Speaker 3>And they're saying AI can help with this, I know

126
00:07:24.680 --> 00:07:28.240
<v Speaker 3>that you go and maybe just a quick announcement for everybody,

127
00:07:28.399 --> 00:07:32.600
<v Speaker 3>So we'll hostile as Savans Annual Virtual Full Funnel signment

128
00:07:32.720 --> 00:07:35.399
<v Speaker 3>next week where Still would be one of the speakers

129
00:07:35.439 --> 00:07:39.360
<v Speaker 3>and he'll be talking exactly about the topic of AI

130
00:07:39.639 --> 00:07:45.040
<v Speaker 3>workflows for each stages of your ABM funnel. So we'll

131
00:07:45.079 --> 00:07:47.720
<v Speaker 3>leave it for that part, right, But anyhow, I would

132
00:07:47.720 --> 00:07:51.439
<v Speaker 3>love to ask you, considering your experience of playing with

133
00:07:51.519 --> 00:07:55.160
<v Speaker 3>A either think AI can help with this initial qualification

134
00:07:55.439 --> 00:07:57.199
<v Speaker 3>and score them?

135
00:07:57.480 --> 00:08:02.040
<v Speaker 1>I do, Yeah, And to give everybody a quick sneak peek,

136
00:08:02.879 --> 00:08:05.800
<v Speaker 1>that's one of the workflows we'll talk about just in general,

137
00:08:05.879 --> 00:08:09.959
<v Speaker 1>the idea of using AI for account scoring, leads scoring,

138
00:08:10.319 --> 00:08:15.439
<v Speaker 1>intense scoring, really scoring in general is incredible And if

139
00:08:15.439 --> 00:08:17.279
<v Speaker 1>you think about it, you know, even when I was

140
00:08:17.319 --> 00:08:19.680
<v Speaker 1>at Google, right, one of the biggest companies on the planet,

141
00:08:20.319 --> 00:08:26.000
<v Speaker 1>I was restricted by resources that were technical to build

142
00:08:26.160 --> 00:08:32.000
<v Speaker 1>things like propensity models, you know, dynamics scoring and things

143
00:08:32.039 --> 00:08:36.759
<v Speaker 1>like that, which are based on statistics and machine learning.

144
00:08:37.399 --> 00:08:42.320
<v Speaker 1>And now we all have access to that skill set

145
00:08:42.399 --> 00:08:47.120
<v Speaker 1>at our fingertips, right, especially if you've used even.

146
00:08:46.919 --> 00:08:47.919
<v Speaker 2>Just general prompting.

147
00:08:48.000 --> 00:08:52.919
<v Speaker 1>Right, Like my first introduction to call it like statistical

148
00:08:52.960 --> 00:08:54.200
<v Speaker 1>analysis was was.

149
00:08:54.200 --> 00:08:57.080
<v Speaker 2>Just with chat GPT. Right. I don't really know that much.

150
00:08:57.320 --> 00:08:59.960
<v Speaker 1>I'm fairly technical as a marketer, but I could go

151
00:09:00.080 --> 00:09:04.799
<v Speaker 1>back and forth with chat GPT and basically build you know,

152
00:09:04.919 --> 00:09:07.960
<v Speaker 1>a machine learning expert, right, and then started to push

153
00:09:08.080 --> 00:09:10.799
<v Speaker 1>further and say, okay, well, what kind of machine learning

154
00:09:10.840 --> 00:09:12.480
<v Speaker 1>methods could you use?

155
00:09:12.519 --> 00:09:13.320
<v Speaker 2>Which ones are.

156
00:09:13.200 --> 00:09:17.279
<v Speaker 1>Best for things like lead scoring or finding trends within data?

157
00:09:17.559 --> 00:09:19.360
<v Speaker 1>And then you can go and you know, build that

158
00:09:19.440 --> 00:09:21.639
<v Speaker 1>base of prompts and put that off to the side,

159
00:09:22.440 --> 00:09:25.360
<v Speaker 1>eventually evolve that into more of like an agentic use

160
00:09:25.519 --> 00:09:28.679
<v Speaker 1>of AI, where you can feed data in more real

161
00:09:28.759 --> 00:09:31.279
<v Speaker 1>time and dynamically and then you can get an output

162
00:09:31.799 --> 00:09:32.919
<v Speaker 1>at that point in time.

163
00:09:33.600 --> 00:09:35.919
<v Speaker 2>And so it's incredible because I don't.

164
00:09:35.679 --> 00:09:39.480
<v Speaker 1>Know too many off the shelf software programs today that

165
00:09:39.600 --> 00:09:44.799
<v Speaker 1>have that level of customization and can deliver lead scoring

166
00:09:45.080 --> 00:09:49.279
<v Speaker 1>at that at that scale and that level of personalization, right,

167
00:09:49.320 --> 00:09:52.799
<v Speaker 1>And so I think that's that's the really the most

168
00:09:52.840 --> 00:09:56.120
<v Speaker 1>amazing thing to me is we can we can We're

169
00:09:56.159 --> 00:10:00.000
<v Speaker 1>pretty close to being able to build our own ABM

170
00:10:00.080 --> 00:10:04.360
<v Speaker 1>tech stacks that are completely unique to our team, our product,

171
00:10:04.480 --> 00:10:08.720
<v Speaker 1>our market, our motion, and we can, like you know,

172
00:10:08.799 --> 00:10:11.480
<v Speaker 1>execute a lot of the steps that we use traditional

173
00:10:11.519 --> 00:10:14.000
<v Speaker 1>software for we can now do with AI.

174
00:10:15.759 --> 00:10:19.200
<v Speaker 3>Yeah, that makes perfect sense. I totally agree. And just

175
00:10:19.240 --> 00:10:23.519
<v Speaker 3>to wrap it up, so one of the solutions what

176
00:10:23.639 --> 00:10:25.559
<v Speaker 3>I have heard from you and just correct me if

177
00:10:25.559 --> 00:10:31.360
<v Speaker 3>I'm wrong, kind of to make the first step towards

178
00:10:31.399 --> 00:10:35.240
<v Speaker 3>alignment with sales, even if we play let's say the

179
00:10:35.360 --> 00:10:40.360
<v Speaker 3>MCL playbook and we can't do anything, is just manually

180
00:10:41.559 --> 00:10:46.639
<v Speaker 3>qualifying all like, really do the market and lead qualification

181
00:10:46.799 --> 00:10:50.879
<v Speaker 3>before transferring innocent to sales. Right, So this is the

182
00:10:50.919 --> 00:10:53.919
<v Speaker 3>first thing and the second one, and you can do it,

183
00:10:54.080 --> 00:10:56.399
<v Speaker 3>say yeah, you can do it manually whatever you prefer,

184
00:10:56.799 --> 00:10:59.639
<v Speaker 3>but also what I feel is really important and I

185
00:10:59.639 --> 00:11:04.000
<v Speaker 3>would like to get your take on this. When we

186
00:11:04.080 --> 00:11:07.279
<v Speaker 3>do this qualification, we just need to think about that

187
00:11:07.320 --> 00:11:10.720
<v Speaker 3>this is just an individual contact, right, and this content

188
00:11:10.840 --> 00:11:15.919
<v Speaker 3>might have completely different journey compared to the account. Right,

189
00:11:16.360 --> 00:11:19.360
<v Speaker 3>So if we want to make sense of that engagement,

190
00:11:19.480 --> 00:11:23.799
<v Speaker 3>we need to pair the signal, right, or the engagement

191
00:11:23.840 --> 00:11:27.600
<v Speaker 3>that we captured it with that content was the historical

192
00:11:27.679 --> 00:11:30.480
<v Speaker 3>interactions with the account, all the signals, so all the

193
00:11:30.519 --> 00:11:34.840
<v Speaker 3>information that is available about this account, account research, et cetera, right,

194
00:11:35.360 --> 00:11:40.200
<v Speaker 3>engagements with other Buying Committee members and then together with sales,

195
00:11:40.799 --> 00:11:44.440
<v Speaker 3>make sense of that engagement. Right, what could it mean

196
00:11:44.600 --> 00:11:49.120
<v Speaker 3>in terms of like account activities and strategic initiatives they

197
00:11:49.159 --> 00:11:53.960
<v Speaker 3>have and what could be our best next action that

198
00:11:54.080 --> 00:11:58.480
<v Speaker 3>would add value for this specific individual? Right? What do

199
00:11:58.519 --> 00:12:02.120
<v Speaker 3>you think about this? I'm just complicated to my chance.

200
00:12:02.200 --> 00:12:04.440
<v Speaker 3>Oh you need just to say, hey, guys, you got

201
00:12:04.440 --> 00:12:07.639
<v Speaker 3>to buy and commit to member engaged, go get them?

202
00:12:08.080 --> 00:12:09.200
<v Speaker 2>Yeah no, no, this.

203
00:12:09.279 --> 00:12:13.440
<v Speaker 1>Is fantastic because you've actually just set the stage really

204
00:12:13.480 --> 00:12:16.320
<v Speaker 1>well for what the talk next week will be about.

205
00:12:16.440 --> 00:12:19.600
<v Speaker 1>And so I know the title is you know AI

206
00:12:19.720 --> 00:12:21.200
<v Speaker 1>workflows for ABM.

207
00:12:21.759 --> 00:12:24.200
<v Speaker 2>But really what we're going to go through in that.

208
00:12:24.120 --> 00:12:29.879
<v Speaker 1>Session is my philosophy on ABM and how it's evolved.

209
00:12:30.240 --> 00:12:32.240
<v Speaker 2>And you now hear contact.

210
00:12:31.759 --> 00:12:36.039
<v Speaker 1>Based marketing right, So there we actually need to sort

211
00:12:36.039 --> 00:12:41.840
<v Speaker 1>of reinvent what the demand creation and capture process looks

212
00:12:41.919 --> 00:12:46.000
<v Speaker 1>like and map that to account based funnels and contact

213
00:12:46.000 --> 00:12:48.840
<v Speaker 1>based funnels. And when we do that, we can then

214
00:12:49.000 --> 00:12:52.519
<v Speaker 1>look at the intersection of signals and data and activity

215
00:12:52.919 --> 00:12:56.480
<v Speaker 1>between accounts and contacts, and I think that's really where

216
00:12:56.519 --> 00:12:59.120
<v Speaker 1>the where the magic is. And so so one, if

217
00:12:59.200 --> 00:13:01.960
<v Speaker 1>you if you have the infrastructure and the architecture to

218
00:13:02.039 --> 00:13:05.679
<v Speaker 1>collect that data, and you do are able to collect signals,

219
00:13:06.080 --> 00:13:09.399
<v Speaker 1>you now have the sort of m VP for AI.

220
00:13:09.840 --> 00:13:11.799
<v Speaker 2>In my mind, you need to have a good.

221
00:13:12.120 --> 00:13:14.559
<v Speaker 1>Base of data that you're that you're building any of

222
00:13:14.600 --> 00:13:17.360
<v Speaker 1>these AI workflows off of. So that's number one, which

223
00:13:17.399 --> 00:13:21.679
<v Speaker 1>is fantastic. Number two is you now have extremely unique

224
00:13:21.759 --> 00:13:26.559
<v Speaker 1>data across third party, first party owned operated sources that

225
00:13:26.600 --> 00:13:29.919
<v Speaker 1>you can use for personalization, which is which is also

226
00:13:30.000 --> 00:13:33.200
<v Speaker 1>exciting because we've all gotten those messages that are like

227
00:13:33.679 --> 00:13:37.279
<v Speaker 1>half personalized, like they they scraped something from our most

228
00:13:37.320 --> 00:13:39.720
<v Speaker 1>recent LinkedIn post. And then slapped it in an email

229
00:13:39.960 --> 00:13:42.159
<v Speaker 1>and blasted it out to us. That's not personalization.

230
00:13:42.879 --> 00:13:44.320
<v Speaker 2>We need. We need we need.

231
00:13:44.200 --> 00:13:46.960
<v Speaker 1>Dozens of signals at a contact level, so we can

232
00:13:46.960 --> 00:13:49.559
<v Speaker 1>build a profile of who that person is, what their

233
00:13:49.600 --> 00:13:51.879
<v Speaker 1>pain points are, and what they care about, and then

234
00:13:51.919 --> 00:13:55.080
<v Speaker 1>come up with a completely unique message that you know,

235
00:13:55.159 --> 00:13:58.200
<v Speaker 1>almost gives them that aha moment at that point in

236
00:13:58.240 --> 00:14:01.279
<v Speaker 1>time when we deliver something to them. And with those

237
00:14:01.320 --> 00:14:05.120
<v Speaker 1>two things in place, then the third is that next

238
00:14:05.200 --> 00:14:08.840
<v Speaker 1>best action piece, which is something I remember I heard

239
00:14:08.879 --> 00:14:12.279
<v Speaker 1>that term like six or seven years ago. I was

240
00:14:12.320 --> 00:14:17.759
<v Speaker 1>talking to a machine learning engineer. It's fairly common in software.

241
00:14:17.840 --> 00:14:17.960
<v Speaker 2>Right.

242
00:14:18.000 --> 00:14:22.440
<v Speaker 1>You think about you buy a hat on Amazon, it's

243
00:14:22.480 --> 00:14:25.879
<v Speaker 1>then going to show you a product for hat cleaners

244
00:14:26.039 --> 00:14:29.639
<v Speaker 1>or hat storage or hat hangars. Right, that's just next

245
00:14:29.639 --> 00:14:32.799
<v Speaker 1>best action, Right, it's taking your existing behavior and trying

246
00:14:32.840 --> 00:14:35.720
<v Speaker 1>to predict what you'll do or buy or need next

247
00:14:36.120 --> 00:14:38.159
<v Speaker 1>based on that historical behavior.

248
00:14:38.440 --> 00:14:39.600
<v Speaker 2>So we can now do that.

249
00:14:39.679 --> 00:14:43.960
<v Speaker 1>We can now do that dynamically based on the scoring

250
00:14:44.039 --> 00:14:44.440
<v Speaker 1>that we.

251
00:14:44.360 --> 00:14:46.480
<v Speaker 2>Can evolve when it comes to an account and.

252
00:14:46.519 --> 00:14:50.399
<v Speaker 1>Contact level, and then again bringing those two data sources

253
00:14:50.440 --> 00:14:53.799
<v Speaker 1>together so we can get a view into what is

254
00:14:53.879 --> 00:14:57.440
<v Speaker 1>generally happening in this account, and then who within the

255
00:14:57.519 --> 00:15:01.159
<v Speaker 1>account is most likely driving that decision, and then we

256
00:15:01.200 --> 00:15:04.159
<v Speaker 1>can act accordingly and leverage all of the data that

257
00:15:04.200 --> 00:15:07.720
<v Speaker 1>we have from prior customers and prospects to say, Okay,

258
00:15:07.759 --> 00:15:10.039
<v Speaker 1>this is the next best thing we should do, right.

259
00:15:10.039 --> 00:15:10.799
<v Speaker 2>And that's when you.

260
00:15:10.759 --> 00:15:15.519
<v Speaker 1>Get tactically into the effectiveness of AI. Right and thinking

261
00:15:15.559 --> 00:15:19.000
<v Speaker 1>about a recommendation engine that your marketing team is now

262
00:15:19.080 --> 00:15:23.720
<v Speaker 1>powered by. I just get pretty fired up thinking about that.

263
00:15:23.720 --> 00:15:25.720
<v Speaker 1>That's pretty cool, right, and we can you can build

264
00:15:25.759 --> 00:15:28.440
<v Speaker 1>that now exclusively for teams.

265
00:15:29.279 --> 00:15:32.039
<v Speaker 3>Love it? Thank you? By the way, guys, Yeah, welcome

266
00:15:32.080 --> 00:15:35.000
<v Speaker 3>to ask us any questions. As always, we'll do this

267
00:15:35.039 --> 00:15:38.240
<v Speaker 3>whole final life. We're going to cover all of them,

268
00:15:38.399 --> 00:15:40.720
<v Speaker 3>so feel free to drop them in the chat and

269
00:15:40.799 --> 00:15:44.440
<v Speaker 3>I will pick them up. And what I would love

270
00:15:44.519 --> 00:15:52.000
<v Speaker 3>to move next is to ask you about the process

271
00:15:52.039 --> 00:15:56.559
<v Speaker 3>you used to create this share OKAYRS with SDRs, right

272
00:15:57.399 --> 00:15:59.559
<v Speaker 3>of course, I mean this is the first step to

273
00:15:59.600 --> 00:16:05.240
<v Speaker 3>the cross functional alignment. But I assume that you need

274
00:16:05.279 --> 00:16:08.360
<v Speaker 3>to do a lot of change change management internally, right

275
00:16:09.639 --> 00:16:13.799
<v Speaker 3>of course. Typically you have different incentives, different processes, and again,

276
00:16:13.879 --> 00:16:17.399
<v Speaker 3>as we poke, you can even have this credit conflict,

277
00:16:17.840 --> 00:16:22.720
<v Speaker 3>so can you walk us through the entire process and

278
00:16:23.080 --> 00:16:24.639
<v Speaker 3>just explain how did you do this?

279
00:16:25.799 --> 00:16:26.080
<v Speaker 2>Sure?

280
00:16:26.159 --> 00:16:31.039
<v Speaker 1>Sure, Yeah, it's a disclaimer. Is easier said than done.

281
00:16:31.399 --> 00:16:34.600
<v Speaker 1>Uh I would. I think of it in two components, right,

282
00:16:34.679 --> 00:16:37.720
<v Speaker 1>there is the change management piece that you mentioned. That's

283
00:16:37.799 --> 00:16:41.799
<v Speaker 1>like the people side, and then the other side is process.

284
00:16:42.360 --> 00:16:46.279
<v Speaker 1>And I think a lot of go to market organizations

285
00:16:46.360 --> 00:16:49.679
<v Speaker 1>they jump right into process. So i'll share that first, Right,

286
00:16:49.720 --> 00:16:52.720
<v Speaker 1>that's your typical Okay, we're going to use HubSpot for

287
00:16:52.799 --> 00:16:55.240
<v Speaker 1>lead scoring. We're going to have a demographic score, we're

288
00:16:55.240 --> 00:16:58.519
<v Speaker 1>going to have a behavioral score, and oh, you know

289
00:16:58.679 --> 00:17:01.519
<v Speaker 1>sales has these s LA's and they're going to run

290
00:17:01.519 --> 00:17:04.640
<v Speaker 1>a band script or use spin methodology, and you know,

291
00:17:05.119 --> 00:17:08.279
<v Speaker 1>all these teams they have all of these wonderful processes

292
00:17:08.319 --> 00:17:11.200
<v Speaker 1>in place, but then they don't have the people aligned

293
00:17:11.480 --> 00:17:12.400
<v Speaker 1>and that will break.

294
00:17:12.720 --> 00:17:13.599
<v Speaker 2>And then in.

295
00:17:13.559 --> 00:17:15.759
<v Speaker 1>Other cases, which I think is better, is you get

296
00:17:15.759 --> 00:17:18.200
<v Speaker 1>the people aligned and they don't have the process yet,

297
00:17:18.279 --> 00:17:20.240
<v Speaker 1>and that's okay. We got to get the people aligned

298
00:17:20.240 --> 00:17:23.519
<v Speaker 1>first and then we can build process around that. And

299
00:17:23.559 --> 00:17:26.000
<v Speaker 1>so for me, like one of the let's see, this

300
00:17:26.119 --> 00:17:26.920
<v Speaker 1>probably took me.

301
00:17:28.000 --> 00:17:28.680
<v Speaker 2>This took me like.

302
00:17:28.640 --> 00:17:33.240
<v Speaker 1>Eight months to be honest, of getting an enterprise sales

303
00:17:33.240 --> 00:17:36.480
<v Speaker 1>and marketing team aligned, but a couple of the key

304
00:17:36.519 --> 00:17:42.160
<v Speaker 1>components that were really critical, where I had autonomy and

305
00:17:43.039 --> 00:17:49.039
<v Speaker 1>ownership of the entire demand generation process, the budget, the activities,

306
00:17:49.279 --> 00:17:55.160
<v Speaker 1>the resources, the channels, you know, the website like those things, right,

307
00:17:55.200 --> 00:17:57.759
<v Speaker 1>So I do think that is important. You don't, as

308
00:17:57.799 --> 00:18:00.880
<v Speaker 1>a marketing leader need to own it, but you at

309
00:18:00.960 --> 00:18:03.759
<v Speaker 1>least need to get alignment with your peers so that

310
00:18:03.960 --> 00:18:07.920
<v Speaker 1>everything that demand generation touches or is adjacent to.

311
00:18:08.440 --> 00:18:10.880
<v Speaker 2>Is complete, completely aligned. Right.

312
00:18:11.079 --> 00:18:14.000
<v Speaker 1>Without that, you're going to run into problems where you

313
00:18:14.079 --> 00:18:17.480
<v Speaker 1>might have the best LinkedIn campaign on the planet, but

314
00:18:17.519 --> 00:18:21.039
<v Speaker 1>your landing pages are terrible because your because your web

315
00:18:21.039 --> 00:18:23.839
<v Speaker 1>team isn't bought in and they're just giving you like random,

316
00:18:23.960 --> 00:18:25.400
<v Speaker 1>random stuff that doesn't quite fit.

317
00:18:25.680 --> 00:18:27.839
<v Speaker 2>So you've got to get that alignment first.

318
00:18:28.920 --> 00:18:32.400
<v Speaker 1>The other piece was the person I worked with on

319
00:18:32.440 --> 00:18:37.200
<v Speaker 1>the sales side was basically a mirrored version.

320
00:18:36.920 --> 00:18:39.759
<v Speaker 2>Of me, but on the on sales. So so she led.

321
00:18:39.599 --> 00:18:45.200
<v Speaker 1>The SDR team and her ownership was really on you know,

322
00:18:45.319 --> 00:18:50.599
<v Speaker 1>think of like SQL too, like stage two opportunity. And

323
00:18:50.640 --> 00:18:52.960
<v Speaker 1>then depending on the deal side, there was an account

324
00:18:53.000 --> 00:18:56.079
<v Speaker 1>executive or you know, maybe a senior sponsor or executive

325
00:18:56.079 --> 00:18:59.559
<v Speaker 1>sponsor or something like that involved. But her role was

326
00:18:59.640 --> 00:19:03.519
<v Speaker 1>on that core piece of SQL to opportunity creation and

327
00:19:03.559 --> 00:19:07.400
<v Speaker 1>then progression into an actual qualified deal. And so we

328
00:19:07.400 --> 00:19:13.680
<v Speaker 1>were both completely incentivized to work together because I essentially

329
00:19:13.720 --> 00:19:17.559
<v Speaker 1>owned the steps prior to SQL and she owned all

330
00:19:17.559 --> 00:19:18.920
<v Speaker 1>the steps after SQL.

331
00:19:19.400 --> 00:19:23.759
<v Speaker 2>So when we got together, you know, one we aligned

332
00:19:23.880 --> 00:19:24.559
<v Speaker 2>on like.

333
00:19:24.519 --> 00:19:27.960
<v Speaker 1>Overall principles like okay, marketing is going to be a

334
00:19:28.880 --> 00:19:32.559
<v Speaker 1>you know, a generator of revenue. We're going to generate meetings,

335
00:19:32.599 --> 00:19:34.880
<v Speaker 1>We're going to generate opportunities. We're going to connect that

336
00:19:35.000 --> 00:19:37.559
<v Speaker 1>to revenue. We're going to be data driven in how

337
00:19:37.599 --> 00:19:41.960
<v Speaker 1>we analyze the effectiveness of marketing campaigns and channels and tactics,

338
00:19:42.440 --> 00:19:43.119
<v Speaker 1>that sort of thing.

339
00:19:43.160 --> 00:19:45.000
<v Speaker 2>And so we came together at that level.

340
00:19:46.119 --> 00:19:49.559
<v Speaker 1>But then the other piece was we started by saying,

341
00:19:49.599 --> 00:19:53.319
<v Speaker 1>what is the single most important metric that we should

342
00:19:53.440 --> 00:19:57.880
<v Speaker 1>both be accountable for? And when I say accountable, I

343
00:19:57.920 --> 00:20:00.759
<v Speaker 1>mean going on to a bi weekly pyce line review

344
00:20:01.119 --> 00:20:04.720
<v Speaker 1>with the GM of Product, the VP of Sales, the

345
00:20:04.799 --> 00:20:08.319
<v Speaker 1>head of marketing, and like going into the fire and

346
00:20:08.799 --> 00:20:13.079
<v Speaker 1>together owning why sqls.

347
00:20:12.680 --> 00:20:13.359
<v Speaker 2>Were what they were.

348
00:20:13.400 --> 00:20:16.519
<v Speaker 1>So that was the metric we picked that was the determinator,

349
00:20:16.880 --> 00:20:19.279
<v Speaker 1>so I was held accountable to SQLS, so was she.

350
00:20:19.759 --> 00:20:21.920
<v Speaker 1>And then the next level was what I talked about

351
00:20:21.960 --> 00:20:25.359
<v Speaker 1>with the quality metric, was we first looked at SQLS

352
00:20:25.400 --> 00:20:27.359
<v Speaker 1>going up or down, what was the delta, what was

353
00:20:27.400 --> 00:20:29.759
<v Speaker 1>the change, and then why and then we used all

354
00:20:29.799 --> 00:20:33.480
<v Speaker 1>the data to figure that out. So so that's one

355
00:20:33.759 --> 00:20:36.920
<v Speaker 1>is like align on the like the ownership and the

356
00:20:36.920 --> 00:20:40.599
<v Speaker 1>accountability of like your team and your area. Then choose

357
00:20:40.599 --> 00:20:45.319
<v Speaker 1>a metric, become jointly accountable for that metric, and then

358
00:20:45.480 --> 00:20:48.279
<v Speaker 1>you know the third thing is I actually like Google

359
00:20:48.400 --> 00:20:52.599
<v Speaker 1>used the like the Smart Goal system.

360
00:20:52.079 --> 00:20:53.400
<v Speaker 2>Which I probably forget it now.

361
00:20:53.400 --> 00:21:00.319
<v Speaker 1>It's like specific, measurable, attributable, I think, et cetera.

362
00:21:00.319 --> 00:21:01.079
<v Speaker 2>So you can look it up.

363
00:21:01.119 --> 00:21:04.200
<v Speaker 1>But smart system was the like criteria we use to

364
00:21:04.240 --> 00:21:08.960
<v Speaker 1>create the okayrs and then OKRs themselves. It's objectives and

365
00:21:09.039 --> 00:21:11.559
<v Speaker 1>key results, so you had to write those in a

366
00:21:11.599 --> 00:21:15.759
<v Speaker 1>way that were pretty descriptive. Like basically it was like

367
00:21:16.160 --> 00:21:20.039
<v Speaker 1>I'm going to or my team is going to do X,

368
00:21:20.640 --> 00:21:24.480
<v Speaker 1>and it's going to produce Y by this timeframe. So

369
00:21:24.480 --> 00:21:26.680
<v Speaker 1>that's where you use that smart system to write these

370
00:21:26.720 --> 00:21:31.079
<v Speaker 1>goals that will will live you know, throughout the year

371
00:21:31.119 --> 00:21:34.559
<v Speaker 1>if you're doing like quarterly planning, so then all of

372
00:21:34.599 --> 00:21:37.559
<v Speaker 1>those things come together, right and when you have bi weekly, monthly,

373
00:21:37.640 --> 00:21:41.240
<v Speaker 1>quarterly pipeline reviews, this is very clear what you're reporting

374
00:21:41.279 --> 00:21:43.759
<v Speaker 1>on and what you're accountable to.

375
00:21:45.000 --> 00:21:49.799
<v Speaker 3>A lot of I guess how much? So uh, what

376
00:21:50.000 --> 00:21:52.799
<v Speaker 3>I would love to where I would love to pre seeds,

377
00:21:52.960 --> 00:21:55.319
<v Speaker 3>and what I would love to touch Next is the

378
00:21:55.400 --> 00:22:00.240
<v Speaker 3>account precression right kind the parts I have described from

379
00:22:00.279 --> 00:22:03.440
<v Speaker 3>the beginning. I know you've been working a lot on

380
00:22:03.519 --> 00:22:07.480
<v Speaker 3>this and on the framework that you have established out.

381
00:22:07.559 --> 00:22:11.759
<v Speaker 3>Try to pull it in hopefully it will be visible

382
00:22:12.440 --> 00:22:15.759
<v Speaker 3>for everybody, but guys, just in case you have a

383
00:22:15.839 --> 00:22:18.960
<v Speaker 3>button two zoom in. Obviously, if you're watching this from

384
00:22:18.960 --> 00:22:21.319
<v Speaker 3>the smart one, it won't be very convenient, but if

385
00:22:21.359 --> 00:22:24.839
<v Speaker 3>you sit with your laptop you can try to zoom

386
00:22:24.839 --> 00:22:31.000
<v Speaker 3>in and see the framework itself. I also Steve published

387
00:22:31.000 --> 00:22:33.960
<v Speaker 3>it on LinkedIn, so you can download it from his

388
00:22:34.079 --> 00:22:37.160
<v Speaker 3>LinkedIn profile. So I would love to ask you a

389
00:22:37.200 --> 00:22:42.119
<v Speaker 3>couple of questions around this, right so, as we spoke

390
00:22:42.240 --> 00:22:46.519
<v Speaker 3>with you one day. Account progressional account velocity is one

391
00:22:46.519 --> 00:22:50.079
<v Speaker 3>of the most important metrics to track ABM efficiency for

392
00:22:50.119 --> 00:22:53.440
<v Speaker 3>the long sales cycles. For a simple reason, you have

393
00:22:53.680 --> 00:22:57.960
<v Speaker 3>a delayed revenue outcome. You can't just expect if your

394
00:22:58.000 --> 00:23:01.880
<v Speaker 3>Selle cycle ankss eighteen months, you can't expect revenue from

395
00:23:01.880 --> 00:23:03.920
<v Speaker 3>a single program that you are run in for the

396
00:23:03.960 --> 00:23:08.400
<v Speaker 3>first month of months number two. Right, But you need

397
00:23:08.400 --> 00:23:12.000
<v Speaker 3>some leading indicators in place that kind of tell you

398
00:23:12.119 --> 00:23:13.759
<v Speaker 3>that we are doing the right things.

399
00:23:13.960 --> 00:23:14.160
<v Speaker 1>Right.

400
00:23:15.559 --> 00:23:20.599
<v Speaker 3>This is why the account velocity helps because it kind

401
00:23:20.599 --> 00:23:24.279
<v Speaker 3>of shows how the accounts are procressing from one stage

402
00:23:24.400 --> 00:23:28.200
<v Speaker 3>of the bar journey to another. Right, And I will

403
00:23:28.480 --> 00:23:32.759
<v Speaker 3>impact on this as a team or no. So what

404
00:23:32.880 --> 00:23:37.480
<v Speaker 3>I would love to ask you is, maybe, first of all,

405
00:23:37.519 --> 00:23:41.960
<v Speaker 3>can you walk us through the entire framework and explain

406
00:23:42.160 --> 00:23:48.000
<v Speaker 3>if I wanted to build or implement this framework from myself, right,

407
00:23:48.160 --> 00:23:49.799
<v Speaker 3>how to do it step by step?

408
00:23:51.000 --> 00:23:53.960
<v Speaker 2>Yeah? Yeah, yeah, Let's.

409
00:23:53.160 --> 00:23:57.400
<v Speaker 1>Let's get into it and I'll share first this framework

410
00:23:57.440 --> 00:24:01.720
<v Speaker 1>actually came from some of the pain points I experienced

411
00:24:01.799 --> 00:24:05.799
<v Speaker 1>with attribution conversations. And you mentioned it, Andrea at the

412
00:24:05.839 --> 00:24:09.359
<v Speaker 1>beginning to call was you know, we become really obsessed

413
00:24:09.400 --> 00:24:14.960
<v Speaker 1>with you know, multi touch, last touch, incrementality, and those

414
00:24:14.960 --> 00:24:18.319
<v Speaker 1>things are all great, They're wonderful, especially at a more

415
00:24:18.359 --> 00:24:22.640
<v Speaker 1>mature company that's perhaps spending a lot on demand generation.

416
00:24:23.240 --> 00:24:26.839
<v Speaker 1>But I sat back and I thought, from an ABM perspective,

417
00:24:26.880 --> 00:24:29.039
<v Speaker 1>what are we actually trying to do here?

418
00:24:29.240 --> 00:24:29.359
<v Speaker 3>Right?

419
00:24:29.480 --> 00:24:32.839
<v Speaker 1>Like we're trying to take accounts from one stage in

420
00:24:32.880 --> 00:24:36.920
<v Speaker 1>the journey and move them along. Like it's that simple, right,

421
00:24:37.200 --> 00:24:42.079
<v Speaker 1>And that's what account progression is. And so in this framework,

422
00:24:42.119 --> 00:24:46.000
<v Speaker 1>there are three components. There's one which is your account

423
00:24:46.039 --> 00:24:50.519
<v Speaker 1>progression table. This is basically like the inputs you're going

424
00:24:50.599 --> 00:24:53.359
<v Speaker 1>to need from an account perspective to be able to

425
00:24:54.519 --> 00:24:57.240
<v Speaker 1>produce this. And then the second is what I call

426
00:24:57.279 --> 00:25:00.599
<v Speaker 1>the event layer, which this is really the kind of

427
00:25:00.599 --> 00:25:05.039
<v Speaker 1>the dynamic real time data that you'll be collecting for

428
00:25:05.319 --> 00:25:07.400
<v Speaker 1>each account and that's what you're going to use.

429
00:25:07.359 --> 00:25:09.240
<v Speaker 2>Ultimately to build your reporting.

430
00:25:09.759 --> 00:25:14.240
<v Speaker 1>And then the last component is the impact and the

431
00:25:14.319 --> 00:25:17.720
<v Speaker 1>velocity through reporting. And so when you have the like

432
00:25:17.839 --> 00:25:21.319
<v Speaker 1>core table dynamics in place and then you're tracking those

433
00:25:21.319 --> 00:25:25.920
<v Speaker 1>events real time, you can now report on what's happening

434
00:25:26.000 --> 00:25:31.039
<v Speaker 1>within a select group of accounts. And importantly, you can

435
00:25:31.160 --> 00:25:35.039
<v Speaker 1>go back and look at what the you know, like

436
00:25:35.119 --> 00:25:39.519
<v Speaker 1>the origination or the originating place was, or the originating

437
00:25:39.559 --> 00:25:42.200
<v Speaker 1>stage of that account was, and then you can compare

438
00:25:42.240 --> 00:25:45.599
<v Speaker 1>it to baseline, So we now have the ability to

439
00:25:45.759 --> 00:25:49.720
<v Speaker 1>report on, you know, just purely what is happening within

440
00:25:49.759 --> 00:25:53.799
<v Speaker 1>an account, but second, what has been the impact of

441
00:25:53.880 --> 00:25:56.559
<v Speaker 1>the events and the activities we ran and how does

442
00:25:56.599 --> 00:25:59.640
<v Speaker 1>that compare against baseline? And then we can look at

443
00:26:00.440 --> 00:26:03.519
<v Speaker 1>and are we are these accounts progressing as quickly as

444
00:26:03.559 --> 00:26:03.920
<v Speaker 1>we'd like?

445
00:26:04.079 --> 00:26:04.160
<v Speaker 3>Is?

446
00:26:04.200 --> 00:26:06.400
<v Speaker 2>Are they stuck somewhere? How do we? How do we

447
00:26:06.440 --> 00:26:10.279
<v Speaker 2>fix that? Right? So those are the three components. And

448
00:26:10.319 --> 00:26:12.480
<v Speaker 2>then next you have the stages.

449
00:26:12.680 --> 00:26:16.119
<v Speaker 1>So these are the common ones that that I see

450
00:26:16.200 --> 00:26:18.599
<v Speaker 1>and we use all the time with clients, but these

451
00:26:18.599 --> 00:26:21.160
<v Speaker 1>can really be whatever you want them to be. So

452
00:26:21.240 --> 00:26:23.799
<v Speaker 1>you have in a stage like on the left side,

453
00:26:23.799 --> 00:26:27.160
<v Speaker 1>this is completely cold, right unaware, and then you move

454
00:26:27.200 --> 00:26:29.559
<v Speaker 1>and you make an account aware and they become engaged

455
00:26:29.559 --> 00:26:33.759
<v Speaker 1>and qualified and sales ready, customer growth, expansion, et cetera.

456
00:26:33.880 --> 00:26:34.599
<v Speaker 2>Can keep going.

457
00:26:35.039 --> 00:26:38.240
<v Speaker 1>But for you, for anybody really, you could you could

458
00:26:38.400 --> 00:26:41.400
<v Speaker 1>simplify this down into three stages, four stages. You can

459
00:26:41.480 --> 00:26:44.680
<v Speaker 1>change the names of the stages. What's most important is

460
00:26:44.720 --> 00:26:47.400
<v Speaker 1>how you define the stages. And this is where a

461
00:26:47.400 --> 00:26:52.039
<v Speaker 1>little bit of data analysis comes into play and where

462
00:26:52.039 --> 00:26:54.279
<v Speaker 1>you can actually use AI as your friend to do this.

463
00:26:54.359 --> 00:26:55.039
<v Speaker 2>Analysis.

464
00:26:55.440 --> 00:26:59.480
<v Speaker 1>But as an example, like an unaware account, if you

465
00:26:59.519 --> 00:27:01.440
<v Speaker 1>were to go and let's say you have a target

466
00:27:01.440 --> 00:27:04.039
<v Speaker 1>account list of seven hundred and fifty accounts or five

467
00:27:04.119 --> 00:27:09.039
<v Speaker 1>hundred accounts, and you're able to export and get let's

468
00:27:09.079 --> 00:27:12.720
<v Speaker 1>say LinkedIn ad data or you know, Google or.

469
00:27:12.599 --> 00:27:14.640
<v Speaker 2>Meta ad data, and then you have.

470
00:27:15.200 --> 00:27:18.000
<v Speaker 1>Maybe some web data, and then you have like email

471
00:27:18.920 --> 00:27:22.759
<v Speaker 1>service data from like a HubSpot or you know, you're

472
00:27:22.920 --> 00:27:25.839
<v Speaker 1>like a marketo. You could export all of that data

473
00:27:25.960 --> 00:27:29.920
<v Speaker 1>and then essentially map it to each account and then

474
00:27:29.960 --> 00:27:33.960
<v Speaker 1>you can start to index those accounts by stage. And

475
00:27:34.000 --> 00:27:37.440
<v Speaker 1>so unaware, for example, for your definition, might mean that

476
00:27:37.480 --> 00:27:39.640
<v Speaker 1>they have zero engagement.

477
00:27:39.279 --> 00:27:40.480
<v Speaker 2>In the last ninety days.

478
00:27:40.680 --> 00:27:44.839
<v Speaker 1>So any accounts last ninety days no engagement, they get

479
00:27:44.839 --> 00:27:47.759
<v Speaker 1>applied to label as unaware versus aware.

480
00:27:48.359 --> 00:27:50.200
<v Speaker 2>They might have you might like we.

481
00:27:50.240 --> 00:27:54.039
<v Speaker 1>Typically use like ad impressions and clicks and website visits

482
00:27:54.119 --> 00:27:57.160
<v Speaker 1>kind of like top of funnel, some kind of vanity

483
00:27:57.160 --> 00:27:59.720
<v Speaker 1>type metrics that are important to show that they might

484
00:27:59.720 --> 00:28:02.839
<v Speaker 1>be aware. And the same process, you go and you

485
00:28:02.880 --> 00:28:05.079
<v Speaker 1>index all of that and then you map it to

486
00:28:05.200 --> 00:28:07.720
<v Speaker 1>that stage. And then when you do that across all

487
00:28:07.720 --> 00:28:10.240
<v Speaker 1>of these stages, what you have at this step in

488
00:28:10.279 --> 00:28:14.440
<v Speaker 1>The process is a complete indexing of where your accounts

489
00:28:14.759 --> 00:28:19.480
<v Speaker 1>currently sit today, and this becomes your baseline. Everything builds

490
00:28:19.599 --> 00:28:23.599
<v Speaker 1>on top of this. And what we typically see is

491
00:28:23.920 --> 00:28:29.279
<v Speaker 1>we run this report and it's humbling for clients because

492
00:28:30.279 --> 00:28:35.359
<v Speaker 1>it's like eighty ninety percent are unaware, whereas they thought,

493
00:28:35.720 --> 00:28:40.000
<v Speaker 1>you know, they had made more more effort with these accounts.

494
00:28:40.039 --> 00:28:43.599
<v Speaker 1>But when you when you time constrain it, because awareness

495
00:28:43.640 --> 00:28:46.839
<v Speaker 1>is fleeting right when you look at it within ninety days.

496
00:28:46.640 --> 00:28:48.920
<v Speaker 2>We often find, hey, a lot of these accounts are unaware.

497
00:28:49.319 --> 00:28:51.640
<v Speaker 1>And with that insight we can then we can change

498
00:28:51.960 --> 00:28:56.839
<v Speaker 1>our tactics and our strategy quite effectively. And yeah, and

499
00:28:56.839 --> 00:28:59.240
<v Speaker 1>then I can we can dive into this little bit more.

500
00:28:59.279 --> 00:29:01.480
<v Speaker 1>But I've had I did some kind of high level

501
00:29:01.480 --> 00:29:03.880
<v Speaker 1>steps for how you could go about implementing it, what

502
00:29:04.039 --> 00:29:06.640
<v Speaker 1>some of the core data needs are, and then how you.

503
00:29:06.559 --> 00:29:09.799
<v Speaker 2>Can actually look at success through metrics from this reporting.

504
00:29:10.920 --> 00:29:13.440
<v Speaker 3>I have seen a question from LUSA Ojen and she

505
00:29:13.640 --> 00:29:20.160
<v Speaker 3>asked about the tools that's being utilized to implement this

506
00:29:21.160 --> 00:29:24.559
<v Speaker 3>general let's speak and if you can maybe highlight how

507
00:29:25.839 --> 00:29:30.160
<v Speaker 3>a good stack that kind of enables implementation of that

508
00:29:30.839 --> 00:29:33.279
<v Speaker 3>framework looks like that would be helpful.

509
00:29:33.799 --> 00:29:37.039
<v Speaker 1>Yeah, yeah, of course it's it's it's always fun to

510
00:29:37.079 --> 00:29:38.039
<v Speaker 1>talk about the tools.

511
00:29:38.839 --> 00:29:45.960
<v Speaker 2>So for something like this, like there's different levels of complexity.

512
00:29:46.039 --> 00:29:49.839
<v Speaker 2>Let's say one of my favorites, which is can be

513
00:29:49.920 --> 00:29:52.799
<v Speaker 2>really simple, but you can also build some complexity on it.

514
00:29:52.839 --> 00:29:56.880
<v Speaker 1>Is you've got Clay or a similar tool like a

515
00:29:56.920 --> 00:29:58.200
<v Speaker 1>common room or.

516
00:29:59.720 --> 00:30:02.720
<v Speaker 2>U you know, zoom info, like something.

517
00:30:02.440 --> 00:30:06.799
<v Speaker 1>That is is robust with building lists and then mapping

518
00:30:06.960 --> 00:30:10.079
<v Speaker 1>data to those lists. I think Clay is the most

519
00:30:10.119 --> 00:30:15.599
<v Speaker 1>flexible currently. So clay on call it like a component one, right,

520
00:30:15.680 --> 00:30:18.039
<v Speaker 1>like your progression table, so you'd have all of your

521
00:30:18.079 --> 00:30:22.640
<v Speaker 1>target accounts in there, you'd have all of your basic demographic,

522
00:30:22.920 --> 00:30:27.319
<v Speaker 1>firmographic type data in place in a tool like that,

523
00:30:27.920 --> 00:30:32.359
<v Speaker 1>and then next would be think of it as like orchestration,

524
00:30:32.519 --> 00:30:37.519
<v Speaker 1>like where do you execute marketing and sales activities? So

525
00:30:37.599 --> 00:30:40.279
<v Speaker 1>on the marketing side, if you're using you know, just

526
00:30:40.319 --> 00:30:42.839
<v Speaker 1>straight in the channel, it could be in a you know,

527
00:30:42.920 --> 00:30:46.640
<v Speaker 1>Google Meta LinkedIn, et cetera, where you're targeting at an

528
00:30:46.640 --> 00:30:50.319
<v Speaker 1>account level, or you might have a tool in place.

529
00:30:50.400 --> 00:30:53.440
<v Speaker 2>There's a tool I've looked at called Primer.

530
00:30:54.000 --> 00:30:55.960
<v Speaker 1>There's a few others that have popped up that will

531
00:30:56.000 --> 00:30:59.920
<v Speaker 1>allow for basically like LinkedIn grade targeting, but in Google

532
00:31:00.119 --> 00:31:03.079
<v Speaker 1>Meta and Reddit, so you might have some data living

533
00:31:03.480 --> 00:31:05.960
<v Speaker 1>in a tool like that which is going to get

534
00:31:06.000 --> 00:31:11.000
<v Speaker 1>you that awareness level data at the account level. Then

535
00:31:11.039 --> 00:31:15.680
<v Speaker 1>I would say your CRM and whatever your email service

536
00:31:15.720 --> 00:31:18.799
<v Speaker 1>provider is. So if you are sending emails from HubSpot

537
00:31:19.119 --> 00:31:22.519
<v Speaker 1>or marketo or active campaign, you're going to want to

538
00:31:22.519 --> 00:31:24.839
<v Speaker 1>get access to all of that data. And then your

539
00:31:24.880 --> 00:31:26.880
<v Speaker 1>CRM is going to be where all of your sales

540
00:31:26.920 --> 00:31:33.000
<v Speaker 1>activity is. So whether it's Salesforce, a t O pipe drive, like,

541
00:31:33.279 --> 00:31:36.319
<v Speaker 1>there's so many of these that you know now can

542
00:31:36.359 --> 00:31:38.880
<v Speaker 1>can even you can API connect or you can just

543
00:31:38.960 --> 00:31:45.000
<v Speaker 1>export data. But for building the actual report, I've yet

544
00:31:45.039 --> 00:31:47.000
<v Speaker 1>to come across a tool that can do this out

545
00:31:47.000 --> 00:31:50.119
<v Speaker 1>of the box. So when we build these for clients,

546
00:31:50.160 --> 00:31:55.720
<v Speaker 1>it's actually completely through AI and you can do it honestly.

547
00:31:55.720 --> 00:31:57.599
<v Speaker 1>You can do this with a twenty five dollars a

548
00:31:57.599 --> 00:32:02.839
<v Speaker 1>month cloud or cloud subscription where you can have a

549
00:32:03.279 --> 00:32:08.359
<v Speaker 1>dynamic dashboard produced in HTML bi weekly every month, whatever

550
00:32:08.359 --> 00:32:10.160
<v Speaker 1>you want, and then you can just you know, create

551
00:32:10.480 --> 00:32:15.880
<v Speaker 1>create all the underlying context and skills and information so

552
00:32:15.920 --> 00:32:19.640
<v Speaker 1>that it's it's repeatable. But yeah, those those right there

553
00:32:19.720 --> 00:32:23.200
<v Speaker 1>is is kind of all you need because the the

554
00:32:23.640 --> 00:32:27.880
<v Speaker 1>customization of the definitions of the stages and like even

555
00:32:27.920 --> 00:32:31.279
<v Speaker 1>the with the sources of the data. It's it's usually unique,

556
00:32:31.759 --> 00:32:34.480
<v Speaker 1>Like every company is different. Their mix of channels is different,

557
00:32:34.480 --> 00:32:37.839
<v Speaker 1>their mix of tools is different, and so you know,

558
00:32:37.839 --> 00:32:39.960
<v Speaker 1>maybe it's an opportunity for somebody if you've got an

559
00:32:40.000 --> 00:32:43.359
<v Speaker 1>engineering background, go build this tool, uh, and then hit

560
00:32:43.400 --> 00:32:46.160
<v Speaker 1>me up when you do, I can help you sell it.

561
00:32:46.200 --> 00:32:51.880
<v Speaker 2>But yeah, right now, it's it's custom.

562
00:32:50.119 --> 00:32:54.880
<v Speaker 3>A lot of and just maybe your mansion cloned. Do

563
00:32:54.920 --> 00:33:01.240
<v Speaker 3>I think, uh, one day it's just the ultimate solution

564
00:33:01.440 --> 00:33:06.839
<v Speaker 3>to manage it all. And we probably just maybe talking

565
00:33:06.880 --> 00:33:10.839
<v Speaker 3>a little bit of about trends because well I'm absorbing.

566
00:33:11.440 --> 00:33:15.759
<v Speaker 3>Probably we all have heard about clase evaluation, right and

567
00:33:15.960 --> 00:33:20.200
<v Speaker 3>all the tools that kind of appeared and martech and

568
00:33:20.319 --> 00:33:25.400
<v Speaker 3>sales take landscape because of AI. But if I just

569
00:33:25.440 --> 00:33:28.799
<v Speaker 3>think about the development of cloud and cloud cowork and

570
00:33:28.839 --> 00:33:34.160
<v Speaker 3>the integrations with your CRM, with your proprietary data, et cetera,

571
00:33:34.400 --> 00:33:36.720
<v Speaker 3>I think I feel at least it's just a matter

572
00:33:36.799 --> 00:33:42.440
<v Speaker 3>of time when they will either acquire or partner with

573
00:33:43.039 --> 00:33:47.640
<v Speaker 3>the huge database platforms like think about domain for European

574
00:33:47.759 --> 00:33:50.640
<v Speaker 3>providers right, and then they will have access to ever

575
00:33:50.920 --> 00:33:57.039
<v Speaker 3>and then basically they just kill everyone. So when I'm

576
00:33:57.079 --> 00:34:01.839
<v Speaker 3>heading with this, maybe I see it in completely wrong quay.

577
00:34:02.279 --> 00:34:06.279
<v Speaker 3>But even despite of this, well I'm thinking, isn't it

578
00:34:06.359 --> 00:34:10.360
<v Speaker 3>better to kind of simplify Everson for yourself and indeed

579
00:34:10.440 --> 00:34:13.599
<v Speaker 3>start playing, for example Claude or any software that you'll

580
00:34:13.639 --> 00:34:17.480
<v Speaker 3>select for example Google Build right, and especially if your

581
00:34:17.559 --> 00:34:21.760
<v Speaker 3>organization is on Google right, and try to time that

582
00:34:22.159 --> 00:34:27.280
<v Speaker 3>creates that solution internally, compare to develop let's say text tech,

583
00:34:27.480 --> 00:34:31.000
<v Speaker 3>which you still need to integrate right. There is still

584
00:34:31.039 --> 00:34:34.320
<v Speaker 3>a learning curve and you need to train your people

585
00:34:34.400 --> 00:34:36.360
<v Speaker 3>to leverage all of this assorts.

586
00:34:38.280 --> 00:34:41.920
<v Speaker 1>Yeah, yeah, yeah, I mean here's the I think the

587
00:34:42.320 --> 00:34:45.960
<v Speaker 1>reality is when you go on LinkedIn or you know,

588
00:34:46.000 --> 00:34:48.119
<v Speaker 1>you look at Reddit, or you follow the news in

589
00:34:48.159 --> 00:34:51.760
<v Speaker 1>the trends, it seems like the whole world is building

590
00:34:51.800 --> 00:34:56.920
<v Speaker 1>completely unique applications with cloud code, and they just aren't right.

591
00:34:56.960 --> 00:35:00.440
<v Speaker 1>There are if you're in SaaS and like software and

592
00:35:00.519 --> 00:35:04.679
<v Speaker 1>kind of emerging tech, sure, I think it's something to

593
00:35:04.679 --> 00:35:07.960
<v Speaker 1>pay attention to, but there is a whole universe of

594
00:35:08.079 --> 00:35:12.800
<v Speaker 1>companies that honestly they don't even have subscriptions to AI.

595
00:35:13.000 --> 00:35:16.079
<v Speaker 2>Right, you have sort of like shadow.

596
00:35:15.760 --> 00:35:18.639
<v Speaker 1>Use of AI within the company and people just using

597
00:35:19.119 --> 00:35:21.519
<v Speaker 1>free accounts to play around and do stuff, and they're

598
00:35:21.559 --> 00:35:24.960
<v Speaker 1>still you know, trying to create content or write emails

599
00:35:25.079 --> 00:35:27.760
<v Speaker 1>or landing page copy for websites and things like that.

600
00:35:28.159 --> 00:35:30.320
<v Speaker 1>So I think, you know, one thing is like don't

601
00:35:30.440 --> 00:35:32.920
<v Speaker 1>I think for folks, I say, don't don't feel behind,

602
00:35:33.679 --> 00:35:36.360
<v Speaker 1>but don't wait too long, like start playing around, start

603
00:35:36.440 --> 00:35:40.920
<v Speaker 1>start trying some things, and the other pieces that what

604
00:35:41.039 --> 00:35:46.519
<v Speaker 1>I've found is the differentiator for how good your output

605
00:35:46.599 --> 00:35:49.320
<v Speaker 1>is is what you put into it and the thought

606
00:35:49.440 --> 00:35:53.159
<v Speaker 1>that you put into your inputs. So the phrase garbage in,

607
00:35:53.280 --> 00:35:55.840
<v Speaker 1>garbage out is like so true. Everybody knows that, right,

608
00:35:55.920 --> 00:36:00.320
<v Speaker 1>It's really really prominent engineering circles, and it's it's true

609
00:36:00.360 --> 00:36:04.199
<v Speaker 1>for us too as marketers. And so it's you know,

610
00:36:04.280 --> 00:36:06.760
<v Speaker 1>don't get caught by opening up.

611
00:36:07.000 --> 00:36:09.800
<v Speaker 2>A chat window in Claude or Gemini or.

612
00:36:09.719 --> 00:36:14.039
<v Speaker 1>Whatever and you know, writing your single prompt and then

613
00:36:14.039 --> 00:36:16.360
<v Speaker 1>you get an output and you're like, cool, it's great,

614
00:36:16.559 --> 00:36:20.840
<v Speaker 1>Like that that single shot kind of prompting isn't going

615
00:36:20.920 --> 00:36:25.440
<v Speaker 1>to get you to like the complex strategic outputs with

616
00:36:25.480 --> 00:36:28.760
<v Speaker 1>some of the stuff we're talking here. You know, you're

617
00:36:28.800 --> 00:36:32.880
<v Speaker 1>going to have probably anywhere from like ten to twelve

618
00:36:33.400 --> 00:36:37.239
<v Speaker 1>artifacts or like input documents that are going to go

619
00:36:37.280 --> 00:36:40.480
<v Speaker 1>into your final workflow. These are things that you need

620
00:36:40.519 --> 00:36:44.320
<v Speaker 1>to build to train you know, that agent, that project,

621
00:36:44.440 --> 00:36:47.880
<v Speaker 1>that specific chat to do exactly what you want. And

622
00:36:47.920 --> 00:36:50.159
<v Speaker 1>this is where the real marketing work happens, right, Like,

623
00:36:50.199 --> 00:36:52.880
<v Speaker 1>this is your core stuff, this is your ICP, these

624
00:36:52.920 --> 00:36:55.320
<v Speaker 1>are their pain points, These are the value props of

625
00:36:55.360 --> 00:36:56.320
<v Speaker 1>your product and service.

626
00:36:56.360 --> 00:36:57.719
<v Speaker 2>This is your your buying motion.

627
00:36:58.679 --> 00:37:00.519
<v Speaker 1>Jobs to be done, Like, this is all of that

628
00:37:00.639 --> 00:37:03.360
<v Speaker 1>information that has to be really good to get these

629
00:37:03.400 --> 00:37:06.039
<v Speaker 1>things right. And then the third piece here, I think

630
00:37:06.119 --> 00:37:11.119
<v Speaker 1>is that most marketers today are not opening terminal and

631
00:37:11.440 --> 00:37:16.119
<v Speaker 1>running you know, cloud code or like a you know

632
00:37:16.159 --> 00:37:21.599
<v Speaker 1>a companion AI that's helping them write and edit in

633
00:37:22.000 --> 00:37:22.800
<v Speaker 1>QA code.

634
00:37:22.920 --> 00:37:25.360
<v Speaker 2>It's it's incredibly.

635
00:37:24.840 --> 00:37:27.800
<v Speaker 1>Complex, and and even for me, like I'm lucky I

636
00:37:27.840 --> 00:37:30.960
<v Speaker 1>have resources in my company that are really good at

637
00:37:30.960 --> 00:37:31.760
<v Speaker 1>this stuff.

638
00:37:31.440 --> 00:37:34.239
<v Speaker 2>And are like pushing me along to learn more.

639
00:37:35.000 --> 00:37:37.880
<v Speaker 1>But I think it's it's worth trying, right, Like it's

640
00:37:37.920 --> 00:37:41.880
<v Speaker 1>worth going in and experiencing it and and fail and

641
00:37:41.920 --> 00:37:46.559
<v Speaker 1>like break things and see what happens. And that happens

642
00:37:46.599 --> 00:37:48.159
<v Speaker 1>to me all the time. I was just doing something

643
00:37:48.239 --> 00:37:51.079
<v Speaker 1>yesterday and you know, I had all this code on

644
00:37:51.119 --> 00:37:53.079
<v Speaker 1>my screen and I don't even know what the heck

645
00:37:53.159 --> 00:37:54.039
<v Speaker 1>any of it says.

646
00:37:54.719 --> 00:37:57.760
<v Speaker 2>But Claud's helping me figure it out. And you know,

647
00:37:57.920 --> 00:38:00.920
<v Speaker 2>prompted this error is like line once and two has

648
00:38:00.920 --> 00:38:03.679
<v Speaker 2>an error with this and that. I'm like, what the

649
00:38:03.760 --> 00:38:06.159
<v Speaker 2>heck does that mean? Right? And then you go and.

650
00:38:06.119 --> 00:38:08.719
<v Speaker 1>You work through the process of fixing that, and then

651
00:38:08.719 --> 00:38:10.960
<v Speaker 1>it breaks something else, and you know, sometimes you.

652
00:38:11.000 --> 00:38:12.000
<v Speaker 2>Get into these loops.

653
00:38:12.159 --> 00:38:15.960
<v Speaker 1>But you know, that experience I think is pretty valuable,

654
00:38:16.199 --> 00:38:18.880
<v Speaker 1>especially today, to just become familiar with the tools and

655
00:38:18.920 --> 00:38:19.440
<v Speaker 1>how they work.

656
00:38:20.400 --> 00:38:24.239
<v Speaker 3>I love it. Thank you. I just want to ask

657
00:38:24.239 --> 00:38:27.000
<v Speaker 3>you one practical question, if you'll If I look at

658
00:38:27.000 --> 00:38:35.280
<v Speaker 3>this framework, and more specifically on the dashboards section. In

659
00:38:35.320 --> 00:38:38.760
<v Speaker 3>one of the sections, I mean, why you explain the

660
00:38:39.920 --> 00:38:44.880
<v Speaker 3>four types of dashboards. One dashboard is about the forecast support,

661
00:38:45.199 --> 00:38:49.760
<v Speaker 3>So I think this is one of the most problematic eras,

662
00:38:49.840 --> 00:38:53.519
<v Speaker 3>right if you have the long sale cycles. So I'm wondering,

663
00:38:54.639 --> 00:38:59.320
<v Speaker 3>how do you use this framework for forecasting on pipeline

664
00:38:59.559 --> 00:39:06.280
<v Speaker 3>or revenue. And also you mentioned in that deskboard sounds

665
00:39:06.280 --> 00:39:10.239
<v Speaker 3>like stage health wardance. So I think just highlights how

666
00:39:10.559 --> 00:39:14.039
<v Speaker 3>the use for it for fort a custom and how

667
00:39:14.159 --> 00:39:18.960
<v Speaker 3>do you define this kind of stage health wardance I

668
00:39:19.000 --> 00:39:20.000
<v Speaker 3>think would be cool.

669
00:39:20.719 --> 00:39:24.280
<v Speaker 2>Yeah, yeah, that's a good one. So it's it's uh,

670
00:39:25.679 --> 00:39:27.239
<v Speaker 2>it's it's it's based.

671
00:39:26.960 --> 00:39:32.039
<v Speaker 1>On two parts of the initial data gathering process.

672
00:39:32.159 --> 00:39:32.320
<v Speaker 2>Right.

673
00:39:32.679 --> 00:39:35.440
<v Speaker 1>So one thing that's cool about this framework is you

674
00:39:35.480 --> 00:39:40.679
<v Speaker 1>can you can retroactively put this into place, meaning if

675
00:39:40.679 --> 00:39:44.400
<v Speaker 1>you have a bunch of unstructured data across marketing and sales,

676
00:39:44.960 --> 00:39:49.800
<v Speaker 1>you can build the the the progression stages and that table,

677
00:39:50.119 --> 00:39:52.920
<v Speaker 1>and then you can take all your existing data and

678
00:39:53.039 --> 00:39:58.079
<v Speaker 1>map it into that that progression framework, and then you can.

679
00:39:59.280 --> 00:40:02.360
<v Speaker 2>Understand some key metrics that'll.

680
00:40:02.039 --> 00:40:07.199
<v Speaker 1>Be useful for forecasting, right like how many accounts you

681
00:40:07.239 --> 00:40:12.920
<v Speaker 1>know typically fall per stage, what is the delta or

682
00:40:12.920 --> 00:40:16.960
<v Speaker 1>the velocity of how frequently they change? So you know,

683
00:40:17.039 --> 00:40:20.760
<v Speaker 1>in simple terms, the questions of how long does it

684
00:40:20.800 --> 00:40:23.920
<v Speaker 1>take to get an account from unaware to aware? You

685
00:40:23.960 --> 00:40:27.360
<v Speaker 1>can answer that question by doing that retroactive analysis, and

686
00:40:27.400 --> 00:40:29.519
<v Speaker 1>then you can you can peel back the onion further

687
00:40:29.559 --> 00:40:32.639
<v Speaker 1>and say, okay, how many touch points did those accounts have?

688
00:40:33.159 --> 00:40:36.079
<v Speaker 1>What was the average number of touch points? Per week,

689
00:40:37.159 --> 00:40:40.320
<v Speaker 1>What channels were those touch points in, what content did

690
00:40:40.400 --> 00:40:45.119
<v Speaker 1>they engage with, Who were the contacts that engaged at

691
00:40:45.119 --> 00:40:46.920
<v Speaker 1>what point in the journey, And so you can start

692
00:40:46.920 --> 00:40:50.679
<v Speaker 1>to map all of these things across that progression journey,

693
00:40:50.760 --> 00:40:53.320
<v Speaker 1>and so that that's one thing. So you can retroactively

694
00:40:53.400 --> 00:40:57.159
<v Speaker 1>go back and do this analysis, and then you'll get

695
00:40:57.199 --> 00:40:59.519
<v Speaker 1>an output of that, which.

696
00:40:59.280 --> 00:41:00.920
<v Speaker 2>I usually called the baseline.

697
00:41:01.119 --> 00:41:04.079
<v Speaker 1>Like, this is your baseline right where you now as

698
00:41:04.119 --> 00:41:07.760
<v Speaker 1>a GTM team, you know it takes fifty five days

699
00:41:07.760 --> 00:41:10.519
<v Speaker 1>on average to get an account from unaware to aware.

700
00:41:10.760 --> 00:41:12.719
<v Speaker 1>You know it takes thirty eight days to get them

701
00:41:12.719 --> 00:41:13.840
<v Speaker 1>from aware and engage.

702
00:41:14.199 --> 00:41:15.119
<v Speaker 2>You know that.

703
00:41:17.159 --> 00:41:19.760
<v Speaker 1>Targeted Google ads are the best way to get them

704
00:41:19.760 --> 00:41:22.760
<v Speaker 1>into an aware stage and the most cost effective, and

705
00:41:22.800 --> 00:41:25.719
<v Speaker 1>you know that running webinar replays on LinkedIn is the

706
00:41:25.719 --> 00:41:28.119
<v Speaker 1>best way of getting them from aware to gauge. So

707
00:41:28.159 --> 00:41:30.079
<v Speaker 1>you now have all of these insights that you can

708
00:41:30.119 --> 00:41:34.000
<v Speaker 1>build from, and you have a baseline of how things

709
00:41:34.039 --> 00:41:37.679
<v Speaker 1>progressed in the past. So with that we can now

710
00:41:37.960 --> 00:41:42.039
<v Speaker 1>forecast and know forecasting in a simple way is just

711
00:41:42.440 --> 00:41:45.960
<v Speaker 1>looking at the past and predicting that the same thing

712
00:41:46.000 --> 00:41:48.920
<v Speaker 1>will happen in the future. So let's say, like I said,

713
00:41:49.280 --> 00:41:52.840
<v Speaker 1>this many days, it costs this much budget, is this channels,

714
00:41:52.880 --> 00:41:55.480
<v Speaker 1>these campaigns, this creative, this content, etc.

715
00:41:56.039 --> 00:41:58.199
<v Speaker 2>That's what we had to do historically to.

716
00:41:58.280 --> 00:42:01.119
<v Speaker 1>Move you know, X number of a counts from aware

717
00:42:01.199 --> 00:42:03.400
<v Speaker 1>to engage and you know, all the way through to

718
00:42:03.480 --> 00:42:06.519
<v Speaker 1>a customer. You can use all of that data now

719
00:42:06.519 --> 00:42:09.480
<v Speaker 1>to then forecast what the next quarter will look like,

720
00:42:09.639 --> 00:42:12.840
<v Speaker 1>the next half, the next year, the next three years,

721
00:42:12.840 --> 00:42:14.119
<v Speaker 1>five years, et cetera.

722
00:42:15.039 --> 00:42:16.440
<v Speaker 2>So that would be like the simple way.

723
00:42:17.320 --> 00:42:18.920
<v Speaker 1>I think if you wanted to make it a little

724
00:42:18.920 --> 00:42:22.880
<v Speaker 1>bit more advanced, you could you could apply some like

725
00:42:23.159 --> 00:42:27.480
<v Speaker 1>some compound and growth indicators, like if you know, you

726
00:42:27.559 --> 00:42:31.000
<v Speaker 1>can assume that you know, quarter after quarter, you'll get

727
00:42:31.039 --> 00:42:34.360
<v Speaker 1>better at qualifying leads, the lead quality will get better,

728
00:42:34.679 --> 00:42:38.639
<v Speaker 1>or sales will get better at running their discovery process,

729
00:42:38.719 --> 00:42:41.920
<v Speaker 1>Like you can build that into your forecast model and

730
00:42:41.960 --> 00:42:49.719
<v Speaker 1>that'll help, you know, increase the growth output substantially. Another thing,

731
00:42:50.000 --> 00:42:51.920
<v Speaker 1>probably the more advanced way to look at it would

732
00:42:51.960 --> 00:42:53.960
<v Speaker 1>be if you if you're good on the.

733
00:42:54.000 --> 00:42:56.000
<v Speaker 2>Data side, and you do have all of that data

734
00:42:56.039 --> 00:42:56.519
<v Speaker 2>and you have.

735
00:42:56.480 --> 00:43:00.400
<v Speaker 1>A robust account progression framework in place, you can actually

736
00:43:00.400 --> 00:43:04.719
<v Speaker 1>then apply a more predictive layer to that, and you

737
00:43:04.719 --> 00:43:08.039
<v Speaker 1>could use like more statistical modeling to try to show

738
00:43:08.840 --> 00:43:11.199
<v Speaker 1>what that forecast could look like based on all of.

739
00:43:11.159 --> 00:43:12.719
<v Speaker 2>That historical behavior.

740
00:43:13.320 --> 00:43:16.760
<v Speaker 1>And that's not too just difficult with either if you

741
00:43:16.840 --> 00:43:22.440
<v Speaker 1>have data science resources or you're capable of building a

742
00:43:22.519 --> 00:43:24.840
<v Speaker 1>data science and machine learning agent with AI.

743
00:43:26.039 --> 00:43:30.480
<v Speaker 3>I love it. I guess so much for super detailed answer.

744
00:43:30.519 --> 00:43:33.480
<v Speaker 3>I think it's super helpful. I would actually try to

745
00:43:34.039 --> 00:43:37.199
<v Speaker 3>replicate with my team what you have said and kind

746
00:43:37.239 --> 00:43:44.039
<v Speaker 3>of crete an actionable step by step guide. So again

747
00:43:44.159 --> 00:43:46.599
<v Speaker 3>then lay a shape as everybody because I think it's

748
00:43:46.639 --> 00:43:51.119
<v Speaker 3>really really helpful. Thank you. Uh, maybe just to wrap

749
00:43:51.159 --> 00:43:54.800
<v Speaker 3>it up, I would love to ask two questions that

750
00:43:54.960 --> 00:43:59.719
<v Speaker 3>I received from from our community. One is from me no,

751
00:44:01.840 --> 00:44:06.679
<v Speaker 3>the question about best final metrics to track a BM

752
00:44:06.719 --> 00:44:08.559
<v Speaker 3>at account level.

753
00:44:10.039 --> 00:44:14.639
<v Speaker 1>Best funnel metrics for yes, yes, yeah, good question. It

754
00:44:14.719 --> 00:44:17.400
<v Speaker 1>may be too small on the on the chart here,

755
00:44:17.440 --> 00:44:23.599
<v Speaker 1>but I think for aware think mostly about like what

756
00:44:23.760 --> 00:44:25.719
<v Speaker 1>are the first touch.

757
00:44:25.519 --> 00:44:31.320
<v Speaker 2>Points that a your your I c P has to

758
00:44:31.639 --> 00:44:33.199
<v Speaker 2>engage with you and your brand?

759
00:44:33.280 --> 00:44:38.559
<v Speaker 1>Right, So if you're running ads, you can look at impressions, clicks, reach,

760
00:44:40.000 --> 00:44:42.719
<v Speaker 1>if you're sending emails.

761
00:44:42.199 --> 00:44:42.880
<v Speaker 2>It might be.

762
00:44:45.039 --> 00:44:47.920
<v Speaker 1>You know, maybe opens or clicks like kind of depends

763
00:44:47.960 --> 00:44:49.679
<v Speaker 1>on how you want to define these things.

764
00:44:50.159 --> 00:44:50.400
<v Speaker 2>Uh.

765
00:44:50.440 --> 00:44:54.280
<v Speaker 1>And then the other more prominent source would be your website.

766
00:44:54.840 --> 00:45:00.400
<v Speaker 1>I like when you break down web into multiple kpi right,

767
00:45:00.440 --> 00:45:04.119
<v Speaker 1>because like a visit to the homepage is very different

768
00:45:04.440 --> 00:45:09.679
<v Speaker 1>than a visit to a pricing page or a visit

769
00:45:09.760 --> 00:45:13.280
<v Speaker 1>to a conversion page or like a demo page, et cetera.

770
00:45:13.440 --> 00:45:17.039
<v Speaker 1>So having some kind of hierarchy there on the website

771
00:45:17.239 --> 00:45:21.320
<v Speaker 1>is important. So think of those those typical like top

772
00:45:21.360 --> 00:45:22.719
<v Speaker 1>of funnel metrics.

773
00:45:22.320 --> 00:45:25.360
<v Speaker 2>For that like aware and engaged stages.

774
00:45:25.920 --> 00:45:30.280
<v Speaker 1>And then for like engaged towards qualified, I would think

775
00:45:30.280 --> 00:45:34.159
<v Speaker 1>about what are the actions that your ICP can take

776
00:45:34.559 --> 00:45:37.000
<v Speaker 1>to become known known to you?

777
00:45:37.199 --> 00:45:37.360
<v Speaker 2>Right?

778
00:45:37.440 --> 00:45:42.960
<v Speaker 1>So they go from you know, basically like anonymous to identified.

779
00:45:43.320 --> 00:45:47.559
<v Speaker 1>That's things like registering for a webinar, downloading a piece

780
00:45:47.599 --> 00:45:52.679
<v Speaker 1>of content, you know, a booth scan at an event,

781
00:45:53.679 --> 00:45:56.079
<v Speaker 1>you know, any of those mechanisms where you're able to

782
00:45:56.239 --> 00:46:00.760
<v Speaker 1>capture contact information for a lead is topically what I'll

783
00:46:01.199 --> 00:46:05.760
<v Speaker 1>associate with with engaged and then and then qualified is

784
00:46:05.880 --> 00:46:11.719
<v Speaker 1>actually usually more just like the volume of those activities, right,

785
00:46:11.800 --> 00:46:13.960
<v Speaker 1>So qualified is like kind of think of it like

786
00:46:13.960 --> 00:46:19.280
<v Speaker 1>your typical MQL score. It's like, Okay, the ICP fits

787
00:46:19.400 --> 00:46:23.480
<v Speaker 1>this demographic criteria, great, Now what.

788
00:46:23.400 --> 00:46:24.199
<v Speaker 2>Was their behavior?

789
00:46:24.599 --> 00:46:26.679
<v Speaker 1>And this is the one you can fine tune a

790
00:46:26.719 --> 00:46:29.320
<v Speaker 1>little bit because it depends on your company.

791
00:46:29.360 --> 00:46:32.360
<v Speaker 2>But for example, you know.

792
00:46:32.360 --> 00:46:36.440
<v Speaker 1>Ad impressions don't mean you're qualified, but if there is

793
00:46:36.800 --> 00:46:41.519
<v Speaker 1>enough of them and it's combined with ad clicks, website visits,

794
00:46:41.599 --> 00:46:45.679
<v Speaker 1>content downloads, webinar registrations, all that stuff, right, then okay,

795
00:46:45.719 --> 00:46:49.480
<v Speaker 1>now they are starting to show some qualification there. And

796
00:46:49.840 --> 00:46:51.880
<v Speaker 1>you know the cool thing about this is like what

797
00:46:51.920 --> 00:46:54.239
<v Speaker 1>we're talking about is at the account level, right, so

798
00:46:54.320 --> 00:46:57.519
<v Speaker 1>you have a you can't just apply take your lead

799
00:46:57.559 --> 00:46:59.400
<v Speaker 1>scoring and apply it to an account, right, You're going

800
00:46:59.440 --> 00:47:02.079
<v Speaker 1>to see a lot of activity at an account level

801
00:47:02.239 --> 00:47:02.960
<v Speaker 1>if you are.

802
00:47:03.039 --> 00:47:04.960
<v Speaker 2>Executing a b M properly.

803
00:47:05.039 --> 00:47:08.000
<v Speaker 1>So you know, keep that in mind, and then you

804
00:47:08.039 --> 00:47:11.280
<v Speaker 1>know sales ready is going to be you know that

805
00:47:11.320 --> 00:47:14.280
<v Speaker 1>point in time when that i c P has like

806
00:47:14.400 --> 00:47:16.760
<v Speaker 1>basically raised their hand and said, you know, hey.

807
00:47:16.559 --> 00:47:19.400
<v Speaker 2>I'm interested in talking to your team. So you know, a.

808
00:47:19.360 --> 00:47:23.960
<v Speaker 1>Demo, a trial, contact, sales form, that sort of stuff

809
00:47:24.039 --> 00:47:25.079
<v Speaker 1>is most important.

810
00:47:25.119 --> 00:47:29.039
<v Speaker 3>There, perfect, thank you, and maybe just the last question

811
00:47:29.199 --> 00:47:34.039
<v Speaker 3>from John McCree. He asked what about the main differences

812
00:47:34.079 --> 00:47:37.559
<v Speaker 3>between working at Google Cloud and your agents in terms

813
00:47:37.599 --> 00:47:40.440
<v Speaker 3>of being able to roll out such a successful demand

814
00:47:40.519 --> 00:47:41.400
<v Speaker 3>gen process.

815
00:47:41.800 --> 00:47:44.599
<v Speaker 1>Oh man, that's a cool question. Thanks for asking it,

816
00:47:44.599 --> 00:47:46.039
<v Speaker 1>because I think about this all the time.

817
00:47:47.800 --> 00:47:51.320
<v Speaker 2>Google. To be honest, Google was a was an amazing place.

818
00:47:51.880 --> 00:47:57.360
<v Speaker 1>The culture there was was so rich and innovative, and

819
00:47:57.360 --> 00:47:59.519
<v Speaker 1>and the people that I worked with really are are

820
00:47:59.559 --> 00:48:00.079
<v Speaker 1>what made it.

821
00:48:00.199 --> 00:48:02.280
<v Speaker 2>So. I was luckily lucky to be a part.

822
00:48:02.159 --> 00:48:04.599
<v Speaker 1>Of a big team, and I had a team myself,

823
00:48:04.599 --> 00:48:07.039
<v Speaker 1>and I still stay in touch with a lot of them.

824
00:48:07.840 --> 00:48:10.199
<v Speaker 1>And I imagine there are so many companies that are

825
00:48:10.920 --> 00:48:14.760
<v Speaker 1>have tried to like replicate their culture off of you know,

826
00:48:14.840 --> 00:48:17.360
<v Speaker 1>big tech like like Google and Meta and those sorts

827
00:48:17.400 --> 00:48:17.960
<v Speaker 1>of companies.

828
00:48:18.000 --> 00:48:19.440
<v Speaker 2>So so that was one part.

829
00:48:20.239 --> 00:48:23.920
<v Speaker 1>But I will say as a an agency operator and

830
00:48:24.360 --> 00:48:28.280
<v Speaker 1>having a team of you know, strategists and technical folks

831
00:48:28.320 --> 00:48:31.480
<v Speaker 1>that are really experts in in what they do, whether

832
00:48:31.519 --> 00:48:35.639
<v Speaker 1>it's like running ads or you know, building revops, workflows

833
00:48:35.639 --> 00:48:39.280
<v Speaker 1>and that sort of stuff, I am learning at a

834
00:48:39.440 --> 00:48:42.679
<v Speaker 1>speed unlike anything I've experienced in the past. I mean,

835
00:48:42.719 --> 00:48:46.599
<v Speaker 1>I feel like every day I'm learning something, I'm getting pushed.

836
00:48:47.360 --> 00:48:49.119
<v Speaker 1>And when you work with you know, all kinds of

837
00:48:49.119 --> 00:48:52.480
<v Speaker 1>different clients. They're always asking different questions, and everybody's unique

838
00:48:52.519 --> 00:48:55.559
<v Speaker 1>and different, and so you know, there's a lot of

839
00:48:55.559 --> 00:48:56.960
<v Speaker 1>cool things that.

840
00:48:58.000 --> 00:48:59.960
<v Speaker 2>I'm able to see and we're able to do now

841
00:49:00.599 --> 00:49:01.960
<v Speaker 2>that that wouldn't.

842
00:49:01.679 --> 00:49:05.280
<v Speaker 1>Fly at a company, a big company like Google or

843
00:49:05.360 --> 00:49:09.039
<v Speaker 1>big tech. So that speed is really important. And then

844
00:49:09.280 --> 00:49:12.119
<v Speaker 1>you know the ability to test and try things out right,

845
00:49:12.239 --> 00:49:16.119
<v Speaker 1>especially when you have happy clients that are wanting to

846
00:49:16.199 --> 00:49:19.360
<v Speaker 1>test as well, and we can bring ideas like like

847
00:49:19.400 --> 00:49:24.960
<v Speaker 1>this account progression dram works or dynamic intent scoring systems

848
00:49:25.000 --> 00:49:27.000
<v Speaker 1>and say, hey, we've got an idea, can we try

849
00:49:27.039 --> 00:49:27.320
<v Speaker 1>this out.

850
00:49:27.400 --> 00:49:28.239
<v Speaker 2>Let's do it together.

851
00:49:28.880 --> 00:49:31.039
<v Speaker 1>So I think that's kind of the pros and cons

852
00:49:31.079 --> 00:49:33.679
<v Speaker 1>when you work in a big company get to work

853
00:49:33.719 --> 00:49:34.159
<v Speaker 1>with a lot.

854
00:49:34.079 --> 00:49:35.199
<v Speaker 2>Of great, smart people.

855
00:49:35.400 --> 00:49:37.480
<v Speaker 1>Things move a little bit slower, though, and you can't

856
00:49:37.480 --> 00:49:40.000
<v Speaker 1>be as agile and scrappy as you want.

857
00:49:40.079 --> 00:49:42.320
<v Speaker 2>And you know, working with smaller company.

858
00:49:43.599 --> 00:49:47.679
<v Speaker 1>Really the opportunities to kind of seem endless these days.

859
00:49:49.079 --> 00:49:53.119
<v Speaker 3>I can't just say it's kind of so much as

860
00:49:53.119 --> 00:49:58.400
<v Speaker 3>a night's with my own experience, as I've been in

861
00:49:58.519 --> 00:50:04.400
<v Speaker 3>consultant nine years already, after being eleven years in the

862
00:50:04.440 --> 00:50:07.199
<v Speaker 3>corporate world as well, like you were at enterprises, but

863
00:50:07.320 --> 00:50:10.280
<v Speaker 3>I was not in the tech space but at Kimberly Clark.

864
00:50:12.039 --> 00:50:17.119
<v Speaker 3>And the truth is, right now you can connect the

865
00:50:17.159 --> 00:50:20.800
<v Speaker 3>core frameworks that you kind of established in the enterprise,

866
00:50:20.920 --> 00:50:26.000
<v Speaker 3>and then you have clients from multiple industries with different challenges, right,

867
00:50:26.159 --> 00:50:30.679
<v Speaker 3>with different companies, they are target in different market conditions.

868
00:50:30.960 --> 00:50:34.880
<v Speaker 3>And then basically what happens is just strengths and your

869
00:50:34.920 --> 00:50:39.559
<v Speaker 3>core framework. As I'm reflecting a lot about, I'll love

870
00:50:39.639 --> 00:50:43.320
<v Speaker 3>to read Charlie Monger and what he says what is

871
00:50:43.360 --> 00:50:46.760
<v Speaker 3>really important is to learn from multiple disciplines, right, and

872
00:50:46.800 --> 00:50:48.840
<v Speaker 3>then connect the dots, because then you can see the

873
00:50:48.840 --> 00:50:50.440
<v Speaker 3>big picture. The same is here.

874
00:50:50.519 --> 00:50:50.719
<v Speaker 2>Right.

875
00:50:51.119 --> 00:50:53.960
<v Speaker 3>Then when you have this experience from this verticle, you

876
00:50:54.000 --> 00:50:56.760
<v Speaker 3>know this is how it kind of applies in healthcare.

877
00:50:57.000 --> 00:50:59.719
<v Speaker 3>But then you see the challenges, you can immediately see

878
00:50:59.760 --> 00:51:03.679
<v Speaker 3>them from different angle in another space. Right. This is

879
00:51:03.679 --> 00:51:07.159
<v Speaker 3>what kind of helps to kind of strengthen your frameworks.

880
00:51:07.159 --> 00:51:10.159
<v Speaker 3>See the gaps, follows them and prove and I think

881
00:51:10.320 --> 00:51:13.079
<v Speaker 3>this is kind of the beauty of it. Maybe the

882
00:51:13.159 --> 00:51:18.440
<v Speaker 3>last fun question from my side. I have never been

883
00:51:18.480 --> 00:51:22.440
<v Speaker 3>at Google, but I watched the movement the in township

884
00:51:22.599 --> 00:51:26.920
<v Speaker 3>was Oh, Wilson if the experience exactly like I was

885
00:51:26.960 --> 00:51:28.360
<v Speaker 3>described in the moment, Oh.

886
00:51:28.239 --> 00:51:36.639
<v Speaker 2>No, I love that. Yes, and no. What's funny is the.

887
00:51:35.199 --> 00:51:38.719
<v Speaker 1>The in the movie, you know the remember the scene

888
00:51:38.760 --> 00:51:42.039
<v Speaker 1>at Vince Vaughan's like ordering a coffee in a pastry.

889
00:51:42.440 --> 00:51:43.119
<v Speaker 2>So I mean.

890
00:51:42.960 --> 00:51:46.119
<v Speaker 1>That's true, right, Like you go up to a barista

891
00:51:46.440 --> 00:51:48.320
<v Speaker 1>in your office and it's like, what do you want?

892
00:51:49.320 --> 00:51:53.280
<v Speaker 1>You can have anything like coffee, you can have you

893
00:51:53.320 --> 00:51:56.519
<v Speaker 1>can make a flat white with cinnamon and this and that,

894
00:51:56.599 --> 00:52:00.079
<v Speaker 1>and you can get whatever you want. And then on

895
00:52:00.079 --> 00:52:04.119
<v Speaker 1>the shelf is uh, you know, chocolate pastries, strawberry pastries,

896
00:52:04.199 --> 00:52:05.840
<v Speaker 1>peach pastries.

897
00:52:06.039 --> 00:52:10.000
<v Speaker 2>So you can it's going to test your your discipline.

898
00:52:10.960 --> 00:52:13.719
<v Speaker 2>So that's true. But I think too, like the.

899
00:52:13.639 --> 00:52:17.719
<v Speaker 1>Movie if I remember, you know, not every day is

900
00:52:17.800 --> 00:52:20.559
<v Speaker 1>like hackathons and like innovation, like it's it's still a

901
00:52:20.599 --> 00:52:23.400
<v Speaker 1>regular company at the end of the day, and you.

902
00:52:23.440 --> 00:52:25.400
<v Speaker 2>Deal with a lot of bureaucracy and stuff like that.

903
00:52:25.480 --> 00:52:29.320
<v Speaker 1>But I do think, especially my early years there when

904
00:52:29.400 --> 00:52:33.159
<v Speaker 1>google Cloud was not as big and prominent as it

905
00:52:33.239 --> 00:52:38.599
<v Speaker 1>is today, there was a real innovative, scrappy mindset to things,

906
00:52:39.079 --> 00:52:42.199
<v Speaker 1>and I think, you know, Google has a lot of

907
00:52:42.719 --> 00:52:47.679
<v Speaker 1>internal principles that help people and teams like be innovative,

908
00:52:48.480 --> 00:52:50.679
<v Speaker 1>you know, use like design thinking. It was a big

909
00:52:50.679 --> 00:52:56.079
<v Speaker 1>one to just produce like really amazing outputs. And h

910
00:52:56.280 --> 00:52:58.599
<v Speaker 1>you know their marketing I think is you know some

911
00:52:58.679 --> 00:53:00.599
<v Speaker 1>of the best, right you look at the certain marketing

912
00:53:00.639 --> 00:53:02.679
<v Speaker 1>and like the year in search video that they put

913
00:53:02.679 --> 00:53:06.480
<v Speaker 1>out every year. You know, so there there's a there's

914
00:53:06.519 --> 00:53:09.360
<v Speaker 1>a process, there's an equation behind the scenes to get

915
00:53:09.360 --> 00:53:10.440
<v Speaker 1>to that level.

916
00:53:10.519 --> 00:53:13.559
<v Speaker 2>So like that that stuff was cool, love.

917
00:53:13.400 --> 00:53:19.039
<v Speaker 3>It, Thank you so much, really enjoyed our conversation and

918
00:53:19.440 --> 00:53:23.079
<v Speaker 3>looking forward to your keynote at our signed next week.

919
00:53:23.360 --> 00:53:25.880
<v Speaker 3>And as you guess, guys, next week we won't have

920
00:53:26.159 --> 00:53:29.039
<v Speaker 3>a full final life. Well, we have the entire sign

921
00:53:29.079 --> 00:53:34.440
<v Speaker 3>at three days, fifteen keynotes, fifteen great speakers, so make

922
00:53:34.480 --> 00:53:37.440
<v Speaker 3>sure that you have signed up. It's free. We keep

923
00:53:37.480 --> 00:53:40.760
<v Speaker 3>it deliberately free because we're once in the era of

924
00:53:40.960 --> 00:53:45.360
<v Speaker 3>AI slap of the kind of really really really bad content.

925
00:53:45.440 --> 00:53:49.039
<v Speaker 3>We want to bring the practitioners who can share their

926
00:53:49.199 --> 00:53:54.360
<v Speaker 3>actionable workflows have similar conversations like we had today with Steve.

927
00:53:54.480 --> 00:53:57.679
<v Speaker 3>You guys welcome to join and ask any questions because

928
00:53:57.760 --> 00:54:01.400
<v Speaker 3>probably this is the only way to help our community

929
00:54:02.079 --> 00:54:05.719
<v Speaker 3>to stay sane in the world of the nonsense that

930
00:54:05.880 --> 00:54:09.960
<v Speaker 3>we are all experience and today, so thank you so much, Steve.

931
00:54:10.559 --> 00:54:13.679
<v Speaker 3>Excited to have you on board on our signment next

932
00:54:13.719 --> 00:54:16.039
<v Speaker 3>week and see you all guys. Have a good fest

933
00:54:16.079 --> 00:54:17.079
<v Speaker 3>of the week, take care.

934
00:54:17.880 --> 00:54:18.639
<v Speaker 2>Thanks everyone,
