1 00:00:14,866 --> 00:00:16,155 Justin Norris: Welcome to RevOps FM. 2 00:00:16,155 --> 00:00:20,566 Today, we are continuing our series, looking at truly unified RevOps 3 00:00:20,576 --> 00:00:23,876 teams, teams that are actually supporting the entire go to market 4 00:00:23,886 --> 00:00:28,236 organization for marketing to sales to CS and exploring what does this 5 00:00:28,296 --> 00:00:29,976 actually look like in practice? 6 00:00:29,986 --> 00:00:31,316 What are the things that make it work? 7 00:00:31,316 --> 00:00:32,386 What are some of the pitfalls? 8 00:00:33,116 --> 00:00:38,226 And we are chatting with Cody Geimann, COO of GTM operations at Mercado. 9 00:00:38,566 --> 00:00:40,306 Which happens to be one of my favorite platforms. 10 00:00:40,346 --> 00:00:41,366 I'm a big fan of Workato. 11 00:00:41,986 --> 00:00:45,886 Cody's been in RevOps for over 13 years and he's helped navigate revenue teams 12 00:00:45,886 --> 00:00:49,226 through some really incredible periods of growth, like when he was COO at Qualtrics, 13 00:00:50,306 --> 00:00:56,656 took them through an 8 billion acquisition by SAP followed by a 27 billion IPO. 14 00:00:57,126 --> 00:00:58,396 So he's been in the trenches. 15 00:00:58,396 --> 00:01:00,136 He's got the scars to prove it. 16 00:01:00,136 --> 00:01:01,796 And he's got a lot of wisdom to share. 17 00:01:01,866 --> 00:01:03,376 I am excited to dig in. 18 00:01:03,806 --> 00:01:04,965 Cody, welcome to the show. 19 00:01:05,321 --> 00:01:06,551 Cody Guymon: Hey, thanks so much for having me. 20 00:01:06,621 --> 00:01:07,331 Appreciate it. 21 00:01:07,671 --> 00:01:08,771 Justin Norris: I would love to just start. 22 00:01:08,873 --> 00:01:12,903 think a lot in my own work about like, what is this thing that we do? 23 00:01:12,913 --> 00:01:13,703 What is it for? 24 00:01:13,703 --> 00:01:15,053 What is the actual job? 25 00:01:15,063 --> 00:01:18,323 Because it's sort of like, glue that sits between a lot of 26 00:01:18,353 --> 00:01:19,743 other pieces of the business. 27 00:01:20,173 --> 00:01:24,333 How do you think about the scope and mandate of GTM operations 28 00:01:24,333 --> 00:01:25,183 through your own experience? 29 00:01:26,086 --> 00:01:26,646 Cody Guymon: I love that. 30 00:01:26,646 --> 00:01:27,616 I love the glue. 31 00:01:27,686 --> 00:01:28,496 You said the glue. 32 00:01:28,496 --> 00:01:31,976 I often think of the quarterback I played baseball as a catcher, kind of 33 00:01:31,976 --> 00:01:36,336 a field general type of position, but I think Rev Ops really is that right? 34 00:01:36,386 --> 00:01:39,668 And we're enabling go to market to exceed, high growth goals. 35 00:01:39,728 --> 00:01:41,178 That's ultimately the end goal. 36 00:01:41,628 --> 00:01:46,198 And there's a wide variety of ways in which RevOps can help accomplish that. 37 00:01:46,218 --> 00:01:51,271 So, I like Glue, Quarterback, Enabler, we're here to make sure that, the 38 00:01:51,271 --> 00:01:53,762 revenue teams hit and exceed targets. 39 00:01:54,348 --> 00:01:57,319 Justin Norris: One of the, themes that I often explore and just things 40 00:01:57,319 --> 00:02:02,179 that I reflect on in my own day to day is the extent to which we're 41 00:02:02,739 --> 00:02:05,849 both supporting those teams and helping those teams and giving them 42 00:02:05,859 --> 00:02:10,012 things that they asked for, and at the same time, there's a reciprocal. 43 00:02:10,434 --> 00:02:13,484 you mentioned the word coach, you know, the coach is also kind of evaluating 44 00:02:13,484 --> 00:02:17,224 the performance of those teams and and driving them in different directions and 45 00:02:18,044 --> 00:02:21,424 How do you thread that needle personally between like I'm here to help you. 46 00:02:21,424 --> 00:02:23,454 I'm here to support you But I'm also here to like keep you 47 00:02:23,454 --> 00:02:25,524 honest and keep you on your toes 48 00:02:26,026 --> 00:02:27,566 Cody Guymon: it's all about the approach. 49 00:02:27,926 --> 00:02:32,569 I think personally, Cause you know, we're here to help, here to support, here to 50 00:02:32,569 --> 00:02:37,789 enable, but at the same time, we have access to a lot of data and insights that. 51 00:02:38,684 --> 00:02:41,514 Sales reps don't have, I mean, they're doing what I think is 52 00:02:41,524 --> 00:02:42,684 the hardest job on the planet. 53 00:02:43,569 --> 00:02:48,939 carrying a quota and 50 percent of their pay is tied to it and all that good 54 00:02:48,939 --> 00:02:50,439 stuff, but we, get advantage points. 55 00:02:50,449 --> 00:02:54,559 So I think the approach is just the key is like, even with the coaching, it's 56 00:02:54,559 --> 00:02:58,469 still, I'm here to help say, Hey, I'm seeing this on the insights I'm seeing 57 00:02:58,469 --> 00:03:04,099 that your average sales price is declining quarter of a quarter and our win rates 58 00:03:04,119 --> 00:03:05,929 decreasing in the inbound channel. 59 00:03:06,259 --> 00:03:07,191 Like what are we doing there? 60 00:03:07,191 --> 00:03:09,391 And it's like collaborative, what do you think's happening? 61 00:03:09,721 --> 00:03:10,621 are we getting desperate? 62 00:03:10,621 --> 00:03:12,161 So that's why the ASP is falling. 63 00:03:12,161 --> 00:03:12,411 Mike. 64 00:03:13,249 --> 00:03:15,489 why aren't we holding value stronger? 65 00:03:15,489 --> 00:03:18,753 and I think that you can thread the line as long as the approach 66 00:03:18,753 --> 00:03:19,978 is super collaborative, right? 67 00:03:19,978 --> 00:03:24,478 As soon as it becomes ivory tower, Rev Ops folks saying, Hey, this, that, 68 00:03:24,489 --> 00:03:26,879 and the other just doesn't feel right. 69 00:03:26,989 --> 00:03:30,633 we've had coaches that are ones that'll get in there with you and help you 70 00:03:30,633 --> 00:03:34,583 figure it out and really work with you for me, baseball on my swing or. 71 00:03:34,973 --> 00:03:35,783 Whatever it might be. 72 00:03:35,783 --> 00:03:36,823 So I think it's all about the 73 00:03:36,833 --> 00:03:37,293 approach. 74 00:03:38,133 --> 00:03:41,083 Justin Norris: It's interesting in your example, you're kind of modeling working 75 00:03:41,083 --> 00:03:46,845 with, reps down in the field to what extent do you find it useful to go and 76 00:03:46,845 --> 00:03:51,105 actually go one on one with members of revenue teams, go to market teams 77 00:03:51,125 --> 00:03:55,755 versus working through their manager, their coach, the leaders of those teams. 78 00:03:56,405 --> 00:03:59,215 Cody Guymon: it's always good to get a pulse of the field at the rep level. 79 00:03:59,605 --> 00:04:00,505 I meet with reps. 80 00:04:00,505 --> 00:04:03,545 I wouldn't say that I do it weekly, but every quarter for sure, I'm 81 00:04:03,545 --> 00:04:04,715 meeting with reps every month. 82 00:04:04,715 --> 00:04:05,635 I'm meeting with reps. 83 00:04:06,482 --> 00:04:11,137 and so I think it's important to feel the pulse reps and I'll mix that up. 84 00:04:11,137 --> 00:04:14,607 High performers, medium performers, that sort of thing, just to get a feel. 85 00:04:15,872 --> 00:04:18,812 But then for the most part, working through sales leadership, I mean, 86 00:04:18,822 --> 00:04:22,512 even in my role, I'm working with, the business leader segment leader 87 00:04:22,632 --> 00:04:24,274 kind of level for most of it. 88 00:04:24,404 --> 00:04:28,734 And then, folks on my team, whether they're in sales ops or enablement, 89 00:04:30,031 --> 00:04:33,341 they're going to also have counterparts that are business units that they support. 90 00:04:33,341 --> 00:04:38,651 And so we'll work through kind of a combo of sales leadership and ops team 91 00:04:38,661 --> 00:04:41,721 members that support those business units to kind of work collectively. 92 00:04:42,266 --> 00:04:45,756 For the most part, but I still like to get a pulse by meeting with reps for sure. 93 00:04:46,219 --> 00:04:48,489 Justin Norris: The examples that we've chatted about very 94 00:04:48,489 --> 00:04:50,711 briefly so far, sales examples. 95 00:04:50,711 --> 00:04:50,731 very much. 96 00:04:51,198 --> 00:04:52,718 and you have a sales ops background. 97 00:04:52,778 --> 00:04:54,978 So that's the place where you started from, just as I was 98 00:04:54,978 --> 00:04:56,268 looking at your LinkedIn profile. 99 00:04:57,338 --> 00:05:01,534 It's interesting to me when I chat with folks about, what makes you nervous? 100 00:05:01,534 --> 00:05:04,570 What do you worry about when you think about a unified function, at least the 101 00:05:04,570 --> 00:05:07,240 people that are outside of sales ops, like on the marketing side of the CS side, 102 00:05:07,620 --> 00:05:10,810 common refrain is, Oh, we're just going to get like swallowed up by sales ops 103 00:05:10,810 --> 00:05:13,137 and just be, sort of on the periphery. 104 00:05:13,147 --> 00:05:15,507 And it's still really going to be very sales centric. 105 00:05:16,019 --> 00:05:18,559 and our concerns are going to be pushed to the side. 106 00:05:19,199 --> 00:05:19,979 How do you think about that? 107 00:05:19,979 --> 00:05:24,390 Particularly as you've come more from a sales centric place about keeping all 108 00:05:24,390 --> 00:05:26,213 those functions in, view and in scope. 109 00:05:26,510 --> 00:05:28,290 Cody Guymon: so just to back up a little bit. 110 00:05:28,290 --> 00:05:31,500 The scope that I have here at work auto is, beyond sales ops. 111 00:05:31,500 --> 00:05:33,300 Like you said, it's marketing ops. 112 00:05:33,370 --> 00:05:33,870 It's C. 113 00:05:33,870 --> 00:05:34,140 S. 114 00:05:34,140 --> 00:05:34,450 Ops. 115 00:05:34,450 --> 00:05:35,880 It's partner operations. 116 00:05:36,600 --> 00:05:37,690 It is sales ops. 117 00:05:37,720 --> 00:05:38,670 It's enablement. 118 00:05:39,613 --> 00:05:44,713 go to market data, deal desk, compensation, those sort of functions. 119 00:05:45,653 --> 00:05:47,641 It's a great question and very observant. 120 00:05:47,912 --> 00:05:49,132 do have a sales ops background. 121 00:05:49,132 --> 00:05:52,672 So the things that I'm bringing up are talking about, mainly sales reps and 122 00:05:52,672 --> 00:05:58,622 things of that nature, but I think all the other functions need to have the 123 00:05:58,622 --> 00:06:03,816 same sales rep focus, I would say that to my teams, like if you're marketing ops. 124 00:06:04,071 --> 00:06:07,291 And you're generating pipe and you have SDRs and you have inbound and paid. 125 00:06:07,291 --> 00:06:09,721 Like, how is it converting at the rep level? 126 00:06:09,811 --> 00:06:10,921 Are you sitting down with reps? 127 00:06:10,921 --> 00:06:12,283 Do they feel like the quality is going up down? 128 00:06:12,813 --> 00:06:13,593 what does it look like? 129 00:06:13,593 --> 00:06:18,323 And even for partner ops, like we have a partner ops function and, it's great. 130 00:06:18,565 --> 00:06:22,645 we want to look at our PMMs and what we're generating and that's awesome. 131 00:06:22,645 --> 00:06:24,465 But what's happening at the rep level? 132 00:06:24,525 --> 00:06:26,995 Are they feeling like they're working well with partners? 133 00:06:26,995 --> 00:06:28,555 Are they closing deals at a clip? 134 00:06:28,555 --> 00:06:29,385 That's appropriate. 135 00:06:29,465 --> 00:06:33,325 I know that I say it as you might say as a sales operator, but I think every 136 00:06:33,355 --> 00:06:37,079 other organization needs to have the same mentality like is what we're doing 137 00:06:37,079 --> 00:06:41,049 in our function, whether it's marketing ops or not, marketing ops, partner ops. 138 00:06:41,169 --> 00:06:42,899 Are we helping sales reps? 139 00:06:42,899 --> 00:06:45,799 When if we are, we're doing our job. 140 00:06:46,058 --> 00:06:47,429 If we're not, we're not doing our job. 141 00:06:47,469 --> 00:06:50,389 I don't care what metrics and dashboards we have to make us feel good. 142 00:06:50,924 --> 00:06:52,034 We're not hitting revenue targets. 143 00:06:52,034 --> 00:06:52,644 We're not winning. 144 00:06:52,654 --> 00:06:55,070 And I think Mercado has that mentality. 145 00:06:55,207 --> 00:07:00,107 our head of marketing ops, Michael fan, he's written automations that are 146 00:07:00,107 --> 00:07:04,671 happening in the background, and they're generating pipeline at amazing clips. 147 00:07:04,671 --> 00:07:07,681 one of his recipes that he's built, which is a workflow automation. 148 00:07:08,421 --> 00:07:11,261 is reaching out to people that jump on our landing page, but 149 00:07:11,261 --> 00:07:12,871 don't fill out our demo request. 150 00:07:13,416 --> 00:07:16,806 If they leave the page and they're a Mark Cato contact where Cato just in the 151 00:07:16,806 --> 00:07:20,216 background will meet you will email them within five minutes and say, Hey, saw you 152 00:07:20,216 --> 00:07:22,116 jumped on a website to get a demo request. 153 00:07:22,116 --> 00:07:23,016 You didn't fill it out. 154 00:07:23,496 --> 00:07:24,606 Do you want to re engage? 155 00:07:24,656 --> 00:07:30,416 And that little recipe automation that he built generated over 2 million, a pipeline 156 00:07:30,416 --> 00:07:33,006 and a quarter for our sellers to go win. 157 00:07:33,016 --> 00:07:37,876 And he's very focused on am I as an ops leader generating pipe for our 158 00:07:37,876 --> 00:07:41,586 sellers to win, which I want all of my leadership team to be thinking. 159 00:07:42,211 --> 00:07:42,811 The whole time. 160 00:07:42,811 --> 00:07:44,411 So really cool observation. 161 00:07:44,411 --> 00:07:46,171 Good question, but I don't know if that helps. 162 00:07:46,171 --> 00:07:48,331 I would think everybody should be thinking that way. 163 00:07:48,421 --> 00:07:48,831 no matter 164 00:07:48,831 --> 00:07:49,501 what org you're 165 00:07:49,778 --> 00:07:50,207 Justin Norris: I love it. 166 00:07:50,207 --> 00:07:54,928 And I actually was in, some meetup of some kind where Michael was 167 00:07:54,938 --> 00:07:58,298 presenting and he presented that automation that you just described 168 00:07:58,848 --> 00:08:00,358 and it was like jaws were dropping. 169 00:08:00,998 --> 00:08:04,398 it's really cool on some level, but even beyond the technical part, what I 170 00:08:04,398 --> 00:08:08,883 find interesting is, the fact that he is thinking about generating pipeline, 171 00:08:08,913 --> 00:08:13,143 not delivering something else that somebody else asked for so that they 172 00:08:13,143 --> 00:08:16,433 can deliver pipeline, but in his own right, and that is not a mindset. 173 00:08:16,433 --> 00:08:17,983 A lot of ops teams. 174 00:08:18,633 --> 00:08:22,430 Always have, a lot of them are more in a service orientation type 175 00:08:22,430 --> 00:08:24,775 of posture do you cultivate that? 176 00:08:24,775 --> 00:08:26,105 Is that workado culture? 177 00:08:26,105 --> 00:08:27,425 Where does that come from for you? 178 00:08:27,742 --> 00:08:28,642 Cody Guymon: I think it's both. 179 00:08:28,692 --> 00:08:31,012 I think Mercado had it before I arrived. 180 00:08:31,539 --> 00:08:33,999 to Michael's credit, he's been here a while to others. 181 00:08:33,999 --> 00:08:36,999 Credit this we're here before I was, I've been here 18 months. 182 00:08:37,078 --> 00:08:42,838 So, it's definitely a workado culture mindset, automate first, what can we do 183 00:08:42,866 --> 00:08:46,497 with our tool, drink our own Kool Aid, all that type of stuff to go help win. 184 00:08:46,497 --> 00:08:50,387 And then, when I got on board, I think I emphasized that as well. 185 00:08:50,397 --> 00:08:51,857 Like, how are we going to go generate pipe? 186 00:08:51,857 --> 00:08:55,047 What are we going to go do to help when, it's all of us collectively. 187 00:08:55,047 --> 00:08:55,507 So. 188 00:08:56,157 --> 00:08:56,997 yeah, I think it's a bit of both. 189 00:08:57,057 --> 00:09:03,388 I've always been pro very pro sales, in my career of like helping sales when, and 190 00:09:03,388 --> 00:09:08,150 so that, might be, part of who I am as well, but yeah, definitely it's a good 191 00:09:08,150 --> 00:09:10,000 combo when it was already here for sure. 192 00:09:10,000 --> 00:09:11,750 And then I'm trying to try and amp it up 193 00:09:11,750 --> 00:09:12,090 too. 194 00:09:12,465 --> 00:09:14,135 Justin Norris: So maybe we can just dive a little bit deeper 195 00:09:14,135 --> 00:09:16,055 into the structure of your team. 196 00:09:16,055 --> 00:09:18,794 You mentioned some of the functions that you support. 197 00:09:18,794 --> 00:09:22,147 Can you walk us through who's on it and how you kind of staff those 198 00:09:22,147 --> 00:09:23,107 different areas of the business? 199 00:09:23,515 --> 00:09:24,605 Cody Guymon: Yeah, for sure. 200 00:09:24,745 --> 00:09:27,045 So we talked marketing ops, Michael fan. 201 00:09:27,115 --> 00:09:29,035 Uh, he has a team of about five. 202 00:09:29,925 --> 00:09:32,715 And so it is that team. 203 00:09:32,775 --> 00:09:36,185 We have partner ops led by a guy named Ryan McCabe. 204 00:09:36,385 --> 00:09:40,485 He's got a team of one FTE and two interns, a team of three. 205 00:09:41,445 --> 00:09:46,925 We have CS operations, customer success operations, Tom McClavish runs that org. 206 00:09:46,955 --> 00:09:50,465 It's a team of two with a couple of dotted lines. 207 00:09:51,580 --> 00:09:58,060 we have our sales ops organization, which is five led by Maria Joseph. 208 00:09:59,310 --> 00:10:04,405 we have a field readiness org, which we call it field readiness here, but it's, 209 00:10:04,460 --> 00:10:06,420 often called enablement at other orgs. 210 00:10:06,835 --> 00:10:07,965 Led by Chris Harper. 211 00:10:08,045 --> 00:10:08,935 It's a team of six. 212 00:10:10,145 --> 00:10:11,665 We have go to market compensation. 213 00:10:11,665 --> 00:10:14,435 So all variable comp for all go to market functions. 214 00:10:15,005 --> 00:10:16,555 It's led by Sean Simpson. 215 00:10:17,245 --> 00:10:24,364 We have our deal desk team led by Rebecca Rubico and she's, got a team of three 216 00:10:25,174 --> 00:10:27,344 supports from global, but wargs there. 217 00:10:27,344 --> 00:10:31,624 And then we have go to market analytics and insights led by Tyler Lawson. 218 00:10:32,174 --> 00:10:33,324 It's a team of three right now. 219 00:10:33,324 --> 00:10:35,884 We're going to grow that to four, hopefully five years soon, but. 220 00:10:36,664 --> 00:10:38,524 That's kind of the structure of my org. 221 00:10:38,524 --> 00:10:42,544 I think what's nice is the purview is you kind of see end to end all of the funnel. 222 00:10:42,634 --> 00:10:46,984 You get to see, the whole view, whereas at Qualtrics, it, I didn't 223 00:10:46,994 --> 00:10:50,734 have that full purview is it was very siloed in different organizations. 224 00:10:50,734 --> 00:10:52,894 It's really just refreshing to see it all. 225 00:10:53,494 --> 00:10:55,704 come together and you can just move faster. 226 00:10:55,754 --> 00:10:59,954 Planning's easier when you're all coordinated and it's just, it's fantastic. 227 00:10:59,964 --> 00:11:00,964 People know each other. 228 00:11:00,964 --> 00:11:05,244 And so even my new things, like someone will say, Hey, can I, you know, turn off 229 00:11:05,244 --> 00:11:07,344 this sales, this field in Salesforce? 230 00:11:08,219 --> 00:11:11,499 if you as a sales ops team, just kind of like, Hey, yeah, everyone in 231 00:11:11,499 --> 00:11:14,728 sales ops, we're good, but you know, let's turn it off, a lot of times 232 00:11:14,728 --> 00:11:18,388 damage happens now when you see, Oh, CS ops is like, no, no, no, no, no. 233 00:11:18,388 --> 00:11:22,334 We use that field for this reason or that reason, or, everybody says, 234 00:11:22,334 --> 00:11:23,804 no, we all don't need that field. 235 00:11:23,804 --> 00:11:25,634 We can turn it off and we can clean up stuff quick. 236 00:11:25,634 --> 00:11:29,314 Like that's one little example of how you can move fast, but it's 237 00:11:29,314 --> 00:11:30,991 really nice just to be coordinated, 238 00:11:31,306 --> 00:11:34,326 Justin Norris: And did you inherit this unified structure or was 239 00:11:34,326 --> 00:11:37,556 that unification project something that you led when you join? 240 00:11:38,024 --> 00:11:41,414 Cody Guymon: No, it was part of when I joined it, but even ultimately 241 00:11:41,454 --> 00:11:44,724 more upstream a little bit, it was part of the recruitment process. 242 00:11:44,856 --> 00:11:50,303 when I was interviewing for this role and leaving, Qualtrics, I really worked 243 00:11:50,303 --> 00:11:55,243 with BJ, our CEO to kind of design what the org chart would look like. 244 00:11:55,272 --> 00:11:59,877 what makes sense to have in this organization and can we work seamlessly 245 00:11:59,877 --> 00:12:01,667 and why and why not for each function. 246 00:12:02,527 --> 00:12:06,147 So when I joined, I think, I think for the first quarter, it was like just sales ops. 247 00:12:06,147 --> 00:12:08,327 And I was learning just workado. 248 00:12:08,377 --> 00:12:10,007 I was learning how we're set up and. 249 00:12:10,562 --> 00:12:13,982 I joined in Q4, which every ops leader knows is always fun because you're 250 00:12:13,982 --> 00:12:17,822 doing the annual plan and getting ready for territories and quotas and pipe 251 00:12:17,822 --> 00:12:19,212 gen goals and all that type of stuff. 252 00:12:19,772 --> 00:12:22,522 So it was just drinking from a water hose, but then after the first quarter, 253 00:12:23,012 --> 00:12:26,312 I'd started Q2, all the groups came together and it's just been awesome. 254 00:12:26,694 --> 00:12:30,294 Justin Norris: Were there specific pain points or challenges with the way that 255 00:12:30,294 --> 00:12:34,940 work had functioned before that, the VJ was trying to solve by like recruiting 256 00:12:34,940 --> 00:12:38,340 you and having that plan in place or was it just sort of, we think this 257 00:12:38,350 --> 00:12:39,850 is the next step and it'll be good. 258 00:12:39,865 --> 00:12:42,265 I 259 00:12:42,320 --> 00:12:42,650 Cody Guymon: of both. 260 00:12:42,650 --> 00:12:46,957 I think we're kind of gotten to the size and scale crossing, you know, a 261 00:12:46,957 --> 00:12:50,357 hundred million in revenue and growing and, at that size and scale, you gotta 262 00:12:50,357 --> 00:12:53,737 get coordinated and you gotta set up processing systems that work together. 263 00:12:53,737 --> 00:12:57,667 So I think there's a bit of like right size and scale to start 264 00:12:57,667 --> 00:12:58,727 laying the groundwork there. 265 00:12:59,387 --> 00:13:01,657 Uh, you know, when I joined, I think there were some issues. 266 00:13:01,657 --> 00:13:02,527 I think we were. 267 00:13:03,777 --> 00:13:09,057 I, I remember trying to set up a pipeline goals for the following year, and for 268 00:13:09,057 --> 00:13:12,897 me, pipeline goals in dollars, like how many dollars do we need by source and 269 00:13:12,907 --> 00:13:19,086 by quarter and by sales team, so really matrix down to the, granular level. 270 00:13:19,286 --> 00:13:22,936 And, you know, when we started doing that right off the bat, it was 271 00:13:22,936 --> 00:13:26,426 like, okay, well, this org measures in dollars, but this one's doing 272 00:13:26,466 --> 00:13:28,336 count of ops and this one's doing. 273 00:13:28,981 --> 00:13:32,501 Ops that are qualified in this stage, but they don't really care about earlier 274 00:13:32,501 --> 00:13:37,281 stages and it's like, well, how do we get coordinated as a whole to know if 275 00:13:37,281 --> 00:13:38,921 we're ahead or behind paces of business? 276 00:13:38,931 --> 00:13:42,341 So we can't just like reach out and ping everybody individually 277 00:13:42,351 --> 00:13:43,311 and see if we're doing okay. 278 00:13:44,081 --> 00:13:46,641 So it was just stuff like that, but I knew that was going to be there. 279 00:13:46,651 --> 00:13:49,741 When you have silos everywhere, it's hard to be coordinated. 280 00:13:49,741 --> 00:13:51,571 You're going to do what's best for your business unit. 281 00:13:51,571 --> 00:13:52,451 And that that's great. 282 00:13:52,501 --> 00:13:55,481 And that works to a certain scale of company. 283 00:13:56,021 --> 00:14:00,561 Then you get to a spot where, if you're a later stage, pre IPO company, need 284 00:14:00,561 --> 00:14:02,411 to know future quarter predictability. 285 00:14:02,411 --> 00:14:06,101 And is the pipeline we're generating today enough for tomorrow? 286 00:14:06,101 --> 00:14:07,741 And could we confidently. 287 00:14:08,611 --> 00:14:12,462 Set a beat and raise if we needed to, if we were going public and you start 288 00:14:12,462 --> 00:14:15,132 working backwards from there, you need to standardize on a lot of things. 289 00:14:15,272 --> 00:14:17,322 So I knew that coming in though. 290 00:14:17,432 --> 00:14:20,092 I mean, that's, that's kind of stuff that gets me excited is going and 291 00:14:20,092 --> 00:14:22,072 building and doing all that stuff. 292 00:14:22,072 --> 00:14:25,282 I think once it's all set and in motion and turnkey. 293 00:14:26,028 --> 00:14:27,958 you know, it's not as, not as fun, 294 00:14:31,378 --> 00:14:34,198 Justin Norris: to dig a little into the example that you provided, because I think 295 00:14:34,198 --> 00:14:38,128 it's really interesting and probably many operators have that experience of like, 296 00:14:38,658 --> 00:14:42,868 everyone's got their own spreadsheet, their own metrics, not in alignment. 297 00:14:43,768 --> 00:14:48,398 So the vision of the promised land, so to speak, of where you want to get 298 00:14:48,398 --> 00:14:55,483 to might seem clear, but getting to Everyone on board, especially when, 299 00:14:55,570 --> 00:14:57,720 there's a lot of different people already doing things their own way. 300 00:14:57,980 --> 00:14:59,110 That could be challenging. 301 00:14:59,450 --> 00:15:03,000 What's the like change management process that you follow to kind of 302 00:15:03,310 --> 00:15:05,490 bring everybody into that aligned state. 303 00:15:06,165 --> 00:15:07,375 Cody Guymon: not, not easy. 304 00:15:07,455 --> 00:15:13,485 So I think one area that's like the key starting point is that when 305 00:15:13,485 --> 00:15:17,207 I joined, a fellow colleague who worked for me at Qualtrics joined 306 00:15:17,207 --> 00:15:21,187 at the same time, Tyler Lawson to run go to market data and analytics. 307 00:15:21,317 --> 00:15:26,057 So we had a central team that was going to own standardized 308 00:15:26,107 --> 00:15:28,707 reporting, pipeline pacing. 309 00:15:30,117 --> 00:15:33,167 Average sales price definition, win rates. 310 00:15:33,177 --> 00:15:35,257 Like you have one spot to go, right? 311 00:15:36,197 --> 00:15:37,017 So that's key. 312 00:15:37,047 --> 00:15:42,427 I think first is just to get like an owner that sits in the org and that's great. 313 00:15:42,447 --> 00:15:45,287 Now that person can really collaborate with all the groups 314 00:15:45,287 --> 00:15:46,647 and, bring that data together. 315 00:15:46,647 --> 00:15:49,254 So that was kind of step one, but to your point, it's still a 316 00:15:49,254 --> 00:15:51,154 lot of change management to go. 317 00:15:52,014 --> 00:15:55,404 Either take that reporting on or in some cases tweak it. 318 00:15:55,454 --> 00:15:59,124 We're going to go from count of ops to dollars and that's going to be different. 319 00:15:59,224 --> 00:16:02,250 And, we're gonna have targets now that are different. 320 00:16:02,250 --> 00:16:04,660 They're in dollars and not count and things of that nature. 321 00:16:04,660 --> 00:16:06,980 So there's just a lot that happens. 322 00:16:06,980 --> 00:16:10,552 But I think one of the key components for Ramos leader is to be collaborative. 323 00:16:10,552 --> 00:16:14,462 If you work well with others and you could talk to the why you start with 324 00:16:14,462 --> 00:16:15,982 the why it's important to do that. 325 00:16:16,002 --> 00:16:18,642 Not just I'm doing this because it's the way I did it before. 326 00:16:18,642 --> 00:16:19,752 And we're going to do it here. 327 00:16:19,752 --> 00:16:23,612 And I know everything that's not gonna work, but if it's like, Hey, 328 00:16:23,612 --> 00:16:26,772 this is the reason why I think we all want to standardize on dollars or 329 00:16:27,092 --> 00:16:28,512 I'm using that as the example, but. 330 00:16:28,970 --> 00:16:31,520 this is why it matters and why it will really matter when we're public 331 00:16:31,520 --> 00:16:32,660 or in the future at some point. 332 00:16:33,395 --> 00:16:34,795 then I think it's all fine. 333 00:16:34,825 --> 00:16:41,045 It's not super smooth, but like, generally being friendly, collaborative, 334 00:16:41,145 --> 00:16:42,755 looking out for their best interest. 335 00:16:42,755 --> 00:16:43,885 Why would they not like it? 336 00:16:43,895 --> 00:16:47,415 And how can you mitigate that feeling generally goes a 337 00:16:47,415 --> 00:16:47,885 long way. 338 00:16:48,850 --> 00:16:49,800 Justin Norris: Don't be a jerk. 339 00:16:50,540 --> 00:16:51,280 In essence, 340 00:16:51,595 --> 00:16:52,465 Cody Guymon: Don't be a jerk. 341 00:16:52,625 --> 00:16:53,445 Yeah, that's great. 342 00:16:53,445 --> 00:16:54,835 I think that sums it up pretty 343 00:16:54,835 --> 00:16:55,245 well. 344 00:16:55,667 --> 00:16:58,177 Justin Norris: am intrigued by how you described the go 345 00:16:58,177 --> 00:16:59,643 to market, analytics function. 346 00:16:59,643 --> 00:17:00,823 Hopefully I got that right. 347 00:17:00,823 --> 00:17:02,573 I'd love to just like better understand. 348 00:17:03,003 --> 00:17:07,221 What they do, are they like the data team or do they work with 349 00:17:07,221 --> 00:17:09,101 another sort of business data team? 350 00:17:09,131 --> 00:17:10,531 I'd love to just go deeper into that. 351 00:17:11,039 --> 00:17:12,348 Cody Guymon: The data team 352 00:17:12,358 --> 00:17:13,169 for everything revenue. 353 00:17:13,694 --> 00:17:13,993 Justin Norris: Let me know. 354 00:17:14,064 --> 00:17:14,314 Okay. 355 00:17:14,864 --> 00:17:19,204 Cody Guymon: So, you know, you're going to have finance professionals in FP& A 356 00:17:19,204 --> 00:17:23,651 that are going to own all the financial data, but, as far as revenue metrics 357 00:17:23,651 --> 00:17:29,321 are considered, this team owns it and they, build out data dictionaries 358 00:17:29,321 --> 00:17:31,571 and get buy in on definitions, right? 359 00:17:31,611 --> 00:17:35,501 There's oftentimes 15 different definitions for what a 360 00:17:35,501 --> 00:17:38,261 customer is, Depending on which department you're talking to. 361 00:17:38,951 --> 00:17:42,391 And so if there's a place to document that, like if finance is asking for 362 00:17:42,391 --> 00:17:46,191 a data poll or whatnot, or they're pulling data and that, that cut count 363 00:17:46,191 --> 00:17:51,071 of customers looks different than maybe the go to market analytics team polls. 364 00:17:51,498 --> 00:17:52,278 why is that? 365 00:17:52,278 --> 00:17:52,598 Right. 366 00:17:52,678 --> 00:17:54,888 and if you have definitions clearly laid out. 367 00:17:55,463 --> 00:17:59,302 A data dictionary catalog, you know, central source of truth for that 368 00:17:59,712 --> 00:18:00,822 just becomes pretty easy, right? 369 00:18:00,822 --> 00:18:04,742 I mean, the average sales price could be really interesting, right? 370 00:18:04,742 --> 00:18:12,320 If you have a, quarter with a 9 figure deal, that's the only 1 you've ever had. 371 00:18:12,320 --> 00:18:13,450 And you're looking at a chart. 372 00:18:13,460 --> 00:18:16,730 Do you exclude that 1 for the sake of analytics purposes? 373 00:18:16,730 --> 00:18:16,800 Just. 374 00:18:17,070 --> 00:18:17,760 Exclude it. 375 00:18:17,760 --> 00:18:19,730 So we could see without that one, were we okay? 376 00:18:19,730 --> 00:18:22,250 Or were you just going to celebrate that we were just awesome because of 377 00:18:22,250 --> 00:18:23,620 one deal pulled up the average, right? 378 00:18:23,950 --> 00:18:28,690 So there's just different ways you can slice data as a go to market professional. 379 00:18:28,690 --> 00:18:31,648 And so you've got to have a central kind of source of truth for 380 00:18:31,648 --> 00:18:33,578 those, and that's what that team 381 00:18:33,578 --> 00:18:33,998 does. 382 00:18:34,983 --> 00:18:37,643 Justin Norris: This data dictionary that you describe, this seems 383 00:18:37,643 --> 00:18:39,873 like a very tactical question, but I'm interested in these things. 384 00:18:40,093 --> 00:18:40,833 Like, where does it live? 385 00:18:40,833 --> 00:18:43,253 Is it a shared Google sheet that people can access? 386 00:18:43,253 --> 00:18:44,583 Do you have some kind of knowledge base, a 387 00:18:44,583 --> 00:18:45,053 wiki? 388 00:18:45,248 --> 00:18:45,538 Cody Guymon: the high spot, 389 00:18:46,127 --> 00:18:47,467 it's a high spot page. 390 00:18:47,467 --> 00:18:51,427 Yeah, that's what we use for our kind of centralized repository for 391 00:18:51,447 --> 00:18:53,177 everything kind of go to market related. 392 00:18:53,197 --> 00:18:56,097 And we can kind of drop that And send it to everybody. 393 00:18:56,662 --> 00:18:59,352 Justin Norris: And does that team have, if we just think about the tech stack 394 00:18:59,392 --> 00:19:02,702 that they're using, do they have sort of their own data warehouse, whether 395 00:19:02,702 --> 00:19:05,822 that's like Snowflake or big query or whatever they're using, or do they 396 00:19:06,092 --> 00:19:10,712 still share space with the rest of the org in terms of data and warehousing? 397 00:19:11,794 --> 00:19:15,120 Cody Guymon: they'll have their own pulled out for go to market and stuff like, and 398 00:19:15,120 --> 00:19:15,720 utilize that. 399 00:19:16,515 --> 00:19:19,365 Justin Norris: Thinking about, you sketched out this org design 400 00:19:19,375 --> 00:19:22,155 during recruitment, you've come in, you've, you've built it out. 401 00:19:22,155 --> 00:19:23,945 It sounds like 40 people. 402 00:19:23,945 --> 00:19:26,775 I didn't, I wasn't keeping count, but it felt like about there by the 403 00:19:26,800 --> 00:19:27,170 Cody Guymon: Yeah. 404 00:19:27,220 --> 00:19:29,010 35, 35 ish, Yeah. 405 00:19:29,220 --> 00:19:29,630 Yeah. 406 00:19:29,640 --> 00:19:30,480 It's a good, good man. 407 00:19:30,510 --> 00:19:32,040 Interns probably 40. 408 00:19:32,130 --> 00:19:32,440 Yeah, 409 00:19:32,575 --> 00:19:33,265 Justin Norris: big team. 410 00:19:33,345 --> 00:19:37,135 any like pain points or challenges because I know there's the benefits and 411 00:19:37,135 --> 00:19:40,751 I'm a believer in this function that's why we're talking about this, but Being 412 00:19:40,751 --> 00:19:43,651 realistic if someone else was to take this journey, what are some of the 413 00:19:43,851 --> 00:19:45,381 challenges that they should watch out for? 414 00:19:46,256 --> 00:19:46,446 Cody Guymon: man. 415 00:19:46,446 --> 00:19:47,416 That's a good question. 416 00:19:47,876 --> 00:19:52,996 a lot of direct reports, so that's, that's, tough with like, 417 00:19:53,056 --> 00:19:56,930 you know, wanting to have enough time with everybody, individually. 418 00:19:56,930 --> 00:20:03,110 I think for me, the key there is when hiring, make sure that you look for 419 00:20:03,110 --> 00:20:09,020 people that can thrive in ambiguity, if they need a lot of handholding, It's 420 00:20:09,020 --> 00:20:12,330 going to be really difficult for me to give them the time needed for sure. 421 00:20:13,119 --> 00:20:15,249 so that, time spread, I think is key. 422 00:20:15,249 --> 00:20:16,569 Now there's some things we could do. 423 00:20:16,579 --> 00:20:19,539 We can find another person and consolidate some stuff, but I don't want to do that. 424 00:20:19,539 --> 00:20:22,309 I think we're trying to be lean as a business, be more efficient. 425 00:20:22,376 --> 00:20:23,046 I can do it. 426 00:20:23,046 --> 00:20:25,380 I can be spread, but you know, span of control. 427 00:20:25,510 --> 00:20:26,040 It's a big team. 428 00:20:26,170 --> 00:20:27,250 There's a lot of, folks there. 429 00:20:27,250 --> 00:20:29,127 So that's just, I think, time management. 430 00:20:29,387 --> 00:20:30,067 is important. 431 00:20:31,377 --> 00:20:33,737 don't know that I would say there's a lot of like challenges. 432 00:20:33,747 --> 00:20:37,717 There's a lot more pros than any cons bringing them all together. 433 00:20:37,797 --> 00:20:41,937 I mean, we move faster, we move more efficiently, we're more coordinated. 434 00:20:42,007 --> 00:20:44,967 We, I mean, we did our annual term within, a week, everything was done. 435 00:20:44,977 --> 00:20:48,977 I mean, quotas were loaded for the new year in the systems the 436 00:20:48,977 --> 00:20:51,437 day the annual term flipped over. 437 00:20:51,997 --> 00:20:56,867 So everybody had quotas, comp plans were done and sent out for 438 00:20:56,867 --> 00:21:00,577 signature within 10 days, territories were done within three days. 439 00:21:00,647 --> 00:21:02,027 I mean, like you can get stuff done. 440 00:21:02,027 --> 00:21:04,677 Pipeline targets were done before we even started the quarter. 441 00:21:04,732 --> 00:21:07,739 It's it's a lot easier to be coordinated when you have all the groups, when you're 442 00:21:07,739 --> 00:21:12,229 kind of waiting on another group and their, boss to like prioritize it for you. 443 00:21:12,229 --> 00:21:16,919 And then that's a key component of everything you're trying to build. 444 00:21:16,919 --> 00:21:20,899 Like, if it's siloed, that just, now your annual turn can take six weeks. 445 00:21:21,019 --> 00:21:21,889 It can take two months. 446 00:21:21,979 --> 00:21:24,649 I've heard of some areas of taking three months, like, and the first 447 00:21:24,649 --> 00:21:26,219 quarter before everything's dialed. 448 00:21:26,219 --> 00:21:28,859 That's just so slow to get started off on a new year. 449 00:21:28,859 --> 00:21:30,409 So, I don't know many 450 00:21:30,409 --> 00:21:30,999 cons 451 00:21:31,749 --> 00:21:35,005 Justin Norris: Mean that's amazing Exploring the example you gave a 452 00:21:35,005 --> 00:21:38,540 little bit further let's say the structures were separate, like 453 00:21:38,870 --> 00:21:40,810 compensation, territory, stuff like that. 454 00:21:41,150 --> 00:21:45,210 Is it the primarily like the marketing sales alignment that makes that hard 455 00:21:45,210 --> 00:21:48,760 when the groups are separate and that, marketing's got to sign onto 456 00:21:48,770 --> 00:21:50,280 its pipeline quota or. 457 00:21:50,680 --> 00:21:52,320 Cody Guymon: Yeah, I think it's all of them. 458 00:21:52,320 --> 00:21:56,501 It's hard when they're all like, you know, if it's just sales ops and marketing 459 00:21:56,501 --> 00:22:00,971 opposites and marketing and partner opposites and partners, it's just so hard 460 00:22:00,971 --> 00:22:05,131 to get yet targets that you're pulling up, like really difficult to get targets. 461 00:22:05,131 --> 00:22:08,419 If you don't know what each group is doing, And to check it, 462 00:22:08,429 --> 00:22:11,699 like, are we good enough at the macro to be able to hit a number? 463 00:22:11,709 --> 00:22:14,049 And, you know, targets is part of it. 464 00:22:14,049 --> 00:22:15,229 Territories is part of it. 465 00:22:15,859 --> 00:22:17,149 SKO is part of it. 466 00:22:17,269 --> 00:22:19,889 if you're fragmented all over the place, it's really difficult to put on 467 00:22:19,889 --> 00:22:22,806 a coherent SKO or, a revenue kickoff. 468 00:22:22,816 --> 00:22:23,716 But, it's really difficult. 469 00:22:23,726 --> 00:22:26,936 You're just waiting on hopefully other people to prioritize what 470 00:22:26,946 --> 00:22:29,956 you're prioritizing, but if you think about in marketing, there's so many 471 00:22:29,956 --> 00:22:33,086 different things going on at the annual turn within just marketing, right? 472 00:22:33,106 --> 00:22:38,540 Like, pipeline targets as part of it, but the gardener magic quadrant comes 473 00:22:38,540 --> 00:22:43,190 out in Q1 and is our website ready what's our messaging to the market 474 00:22:43,190 --> 00:22:46,320 going to be like, there's so much stuff that has nothing to do with ops 475 00:22:46,360 --> 00:22:49,255 that becomes Always mission critical. 476 00:22:49,275 --> 00:22:53,285 So having the marketing ops pulled out to be able to support that, but 477 00:22:53,285 --> 00:22:59,925 also really prioritize and know since August that these things were due, you 478 00:22:59,925 --> 00:23:01,745 just work on it a lot earlier, right? 479 00:23:01,775 --> 00:23:04,885 Like we have an offsite for my whole organization in September every year. 480 00:23:05,635 --> 00:23:09,875 And in September, we start end goal in mind, February 1st, 481 00:23:09,885 --> 00:23:12,015 which is our fiscal February 1st. 482 00:23:12,065 --> 00:23:14,165 These are all the deliverables we need to have done. 483 00:23:14,825 --> 00:23:16,145 How do we back into that now? 484 00:23:16,185 --> 00:23:16,975 Are we on pace? 485 00:23:17,315 --> 00:23:19,095 Are we behind where we're behind? 486 00:23:19,095 --> 00:23:22,275 Are we waiting on any key decisions and we have that build 487 00:23:22,275 --> 00:23:23,355 up all the way to February 1st. 488 00:23:23,355 --> 00:23:28,573 So we know, it's getting prioritized in Q3, for every group, 489 00:23:29,045 --> 00:23:31,504 Justin Norris: The planning you just described is, the operational 490 00:23:31,514 --> 00:23:33,704 backbone planning of the company. 491 00:23:34,004 --> 00:23:38,394 And then there's the, net new projects, new features or deliverables or 492 00:23:38,394 --> 00:23:40,374 requests and what you prioritize. 493 00:23:40,414 --> 00:23:44,389 And in some ways, even though it's siloed, having the functions, the ops 494 00:23:44,389 --> 00:23:45,929 teams embedded within their functions. 495 00:23:45,929 --> 00:23:46,299 That is. 496 00:23:46,739 --> 00:23:50,249 makes it kind of simple because the marketing ops person or leader goes to 497 00:23:50,249 --> 00:23:51,509 the CMO and is like, what do you want? 498 00:23:51,509 --> 00:23:53,399 And the sales ops person goes to the sales ops leader. 499 00:23:53,769 --> 00:23:54,329 What do you want? 500 00:23:54,599 --> 00:23:55,779 Now you've got everyone together. 501 00:23:56,469 --> 00:23:57,629 What does planning look like? 502 00:23:57,629 --> 00:23:59,496 Like, how do you manage that? 503 00:23:59,506 --> 00:24:03,326 And how do you figure out like, where are we going to allocate and budget our time? 504 00:24:03,738 --> 00:24:04,398 Cody Guymon: good question. 505 00:24:04,398 --> 00:24:08,018 I think what I do is I do the urgent and important matrix. 506 00:24:08,538 --> 00:24:09,308 It's always mine. 507 00:24:09,308 --> 00:24:11,638 Like, is this going to move the needle for importance? 508 00:24:11,638 --> 00:24:14,218 Like, is it going to bring value to the business and then 509 00:24:14,228 --> 00:24:15,638 is it urgent or is it not? 510 00:24:15,718 --> 00:24:19,898 And I like to do that actually siloed. 511 00:24:20,418 --> 00:24:24,032 So I like to go with Michael and marketing ops and be like, what's the most important 512 00:24:24,032 --> 00:24:25,462 things you're working on right now? 513 00:24:25,492 --> 00:24:29,442 Because what I don't want to do is collectively, if we do that as a big 514 00:24:29,452 --> 00:24:35,532 go to market, Operations organization, I might be pulling if, if I did 515 00:24:35,532 --> 00:24:38,862 that, I would be pulling resources that should be dedicated to their 516 00:24:38,862 --> 00:24:44,492 department into like a collective, you know, group and, and I think then you 517 00:24:44,492 --> 00:24:46,572 start service abilities really bad. 518 00:24:46,572 --> 00:24:51,252 I think, you know, like, You start to get away from what the rev ops leader 519 00:24:51,252 --> 00:24:54,152 should be doing, which is supporting each group individually, but like 520 00:24:54,152 --> 00:24:55,752 collectively working together faster. 521 00:24:55,752 --> 00:24:58,139 And so wouldn't do that. 522 00:24:58,369 --> 00:25:02,543 like to do those actually siloed on the like strategic projects you're talking 523 00:25:02,543 --> 00:25:05,973 about, like for the CMO, I want to make sure he knows like the marketing 524 00:25:05,973 --> 00:25:09,853 ops team as they're back and they're going to do things for annual planning 525 00:25:09,853 --> 00:25:13,453 and for the broader org that matters, but they're going to have dedicated at 526 00:25:13,453 --> 00:25:15,273 least 50 percent of their time to go do. 527 00:25:15,703 --> 00:25:17,713 Whatever strategic project you're working on. 528 00:25:18,523 --> 00:25:21,557 And so, I don't like to like get it all together because you might have, 529 00:25:21,577 --> 00:25:25,577 okay, this quarter, 90 percent of my whole organization, we're going 530 00:25:25,577 --> 00:25:28,237 to all put heads down and focus on sales ops stuff that matter. 531 00:25:29,011 --> 00:25:30,241 you're just a big sales ops team. 532 00:25:30,674 --> 00:25:33,114 Justin Norris: And that's what like the head of CS and the head of marketing 533 00:25:33,124 --> 00:25:36,974 worry about with a central function is that all like that the center of gravity 534 00:25:36,974 --> 00:25:41,163 will get, sucked away from them and they won't get, but at the same time, it is 535 00:25:41,163 --> 00:25:46,313 interesting to me, sometimes I've seen in businesses that I've been working in 536 00:25:46,313 --> 00:25:50,853 like marketing's, doing pretty well and CS is doing pretty well, like we don't 537 00:25:50,853 --> 00:25:53,213 have a term problem, we don't have a pipe generation problem, but the sales 538 00:25:53,213 --> 00:25:57,615 team can't close and that's actually the most critical, um, Area of the business. 539 00:25:58,015 --> 00:26:00,215 Do you see it as your job to triage that at all? 540 00:26:00,215 --> 00:26:04,075 Like have that purview across the business and direct those resources accordingly. 541 00:26:04,588 --> 00:26:07,489 Cody Guymon: Yeah, do think that's important to triage and 542 00:26:07,499 --> 00:26:09,009 like have a focus for sure. 543 00:26:09,729 --> 00:26:13,999 I don't necessarily love muddling resources allocation at like 544 00:26:13,999 --> 00:26:15,789 the analyst level, do that. 545 00:26:15,859 --> 00:26:19,890 However, if there are times where it's like, in this hyper growth late stage. 546 00:26:19,890 --> 00:26:20,190 So. 547 00:26:20,680 --> 00:26:24,100 It's not like I have a lot of folks that are, sitting around with nothing to do. 548 00:26:24,110 --> 00:26:26,170 If I did, that'd be sweet. 549 00:26:26,184 --> 00:26:27,914 we could flex a little bit, right? 550 00:26:27,934 --> 00:26:33,420 Like, I think one example where, you could have some flex, especially at Workato is. 551 00:26:33,715 --> 00:26:36,155 you know, a lot of people can build recipes that work on it. 552 00:26:36,225 --> 00:26:39,765 That's part of our, it's part of our culture to be able to use the tool. 553 00:26:40,695 --> 00:26:45,615 So if we had like a massive backlog of really high impact, urgent 554 00:26:46,135 --> 00:26:48,035 recipes, we wanted to go build the. 555 00:26:48,450 --> 00:26:50,200 You know, drive the business forward. 556 00:26:50,220 --> 00:26:54,081 And, they were mainly with, let's say CS ops right now. 557 00:26:54,201 --> 00:26:57,681 And, we just didn't have enough builders in our CS ops team to 558 00:26:57,681 --> 00:26:59,631 go through that backlog quickly. 559 00:26:59,971 --> 00:27:03,181 Theoretically, if I had a lot of bandwidth across my, my business, I 560 00:27:03,181 --> 00:27:06,639 could say, Hey, team for the next three days, let's get, a couple analysts 561 00:27:06,639 --> 00:27:09,369 from marketing ops, a couple analysts from partner ops, cause you all are 562 00:27:09,469 --> 00:27:10,999 humming right now and have some time. 563 00:27:11,504 --> 00:27:16,073 Let's get you to come build recipes with CS and go, triage that you 564 00:27:16,073 --> 00:27:18,643 could definitely do that for sure. 565 00:27:18,693 --> 00:27:25,603 And I think there were times 4 plus years ago where you had some 566 00:27:25,713 --> 00:27:28,873 excess capacity to be able to mix. 567 00:27:29,603 --> 00:27:30,953 I think right now. 568 00:27:31,638 --> 00:27:36,218 In the efficiency gain, get profitable environment that we're in. 569 00:27:36,228 --> 00:27:37,108 It's not a luxury. 570 00:27:37,108 --> 00:27:38,028 I have at work auto. 571 00:27:38,028 --> 00:27:38,728 It's not a luxury. 572 00:27:38,728 --> 00:27:43,688 Most ops leaders have is to have this like flex workload type of shift 573 00:27:43,718 --> 00:27:45,308 because we're just trying to be lean. 574 00:27:45,508 --> 00:27:48,878 So ideally, yes, you could do that. 575 00:27:48,978 --> 00:27:52,028 I haven't seen that in the last few years of my career. 576 00:27:52,028 --> 00:27:55,202 maybe there are others that have that, surplus workload, 577 00:27:55,540 --> 00:28:01,073 Justin Norris: And from that point of view of like, profitability, economizing, are 578 00:28:01,073 --> 00:28:05,373 there ever times where you find yourself like, hypothetical CMO wants to do X, Y, 579 00:28:05,383 --> 00:28:07,913 Z, or head of CS wants to do, et cetera. 580 00:28:08,333 --> 00:28:12,373 But actually this is where I feel the business, needs most like, 581 00:28:12,423 --> 00:28:15,113 , there's, giving them what they want versus giving them what they need. 582 00:28:15,473 --> 00:28:18,743 Do you ever find you have to, negotiate that at all? 583 00:28:18,963 --> 00:28:22,803 Cody Guymon: I think generally the negotiation is more so, for instance, 584 00:28:22,803 --> 00:28:27,743 like, my CS ops leader, it's like he has a running prioritization, 585 00:28:28,660 --> 00:28:29,840 to do list really, right? 586 00:28:29,870 --> 00:28:33,850 Like big projects and things, and it's kind of sorted high to low. 587 00:28:34,480 --> 00:28:40,930 And I think more of the pushback is when a new thing comes on to say, okay, CS 588 00:28:40,930 --> 00:28:45,830 leader, we have 15 things here that we have on the priority list one through 15. 589 00:28:46,710 --> 00:28:50,100 If you want this by Friday, does that mean you want number one and 590 00:28:50,100 --> 00:28:54,760 number two to be delayed now, or are we now slotting this in as number 591 00:28:54,760 --> 00:28:56,510 one, or does that one come in? 592 00:28:56,510 --> 00:28:58,260 And generally that's like a dance, right? 593 00:28:58,260 --> 00:28:58,840 It'll be like. 594 00:28:58,910 --> 00:29:02,440 I still need number one and number two, but let's bring this into 595 00:29:02,440 --> 00:29:05,600 number three and it's something quick we can get done and that's okay. 596 00:29:05,600 --> 00:29:07,690 If the other two get bumped away, you know what I mean? 597 00:29:07,690 --> 00:29:13,000 Like that's generally, I think the negotiation, I think from my perspective, 598 00:29:13,820 --> 00:29:20,730 I try not to Push back too hard on what those domain leaders feel is important. 599 00:29:20,730 --> 00:29:23,510 And that's, I guess I felt like super strong about it, but 600 00:29:24,030 --> 00:29:26,257 to me, like I'm not the CMO. 601 00:29:26,287 --> 00:29:29,310 Like I've been versed in marketing throughout my whole career. 602 00:29:29,310 --> 00:29:32,604 And I feel a little bit of like, who am I to, Say what's important and whatnot. 603 00:29:32,624 --> 00:29:35,754 I can come back with like, here's the list. 604 00:29:36,314 --> 00:29:39,664 Here's how long we need to get these things done. 605 00:29:40,194 --> 00:29:43,904 And like, where do you feel like this slots, I think is a better combo. 606 00:29:43,964 --> 00:29:48,074 I mean, I could ultimately, like, if I felt completely like no 607 00:29:48,084 --> 00:29:49,364 way, that's not that important. 608 00:29:49,636 --> 00:29:53,347 maybe say something, but generally like, I'm pretty, reluctant to 609 00:29:53,347 --> 00:29:54,897 really push back too far there. 610 00:29:54,897 --> 00:29:57,587 unless I think it's like egregious, which is very rarely, if any. 611 00:29:57,976 --> 00:29:59,406 Justin Norris: Thinking about impact. 612 00:29:59,465 --> 00:30:02,441 you mentioned that, project that Michael worked on, which is, super cool. 613 00:30:02,441 --> 00:30:05,011 What are the, some of the other things that you're just, you know, really 614 00:30:05,011 --> 00:30:08,141 proud of that you feel your team's been able to deliver over the last while? 615 00:30:08,641 --> 00:30:11,261 Cody Guymon: I think some of those automations pieces that you either 616 00:30:11,261 --> 00:30:13,071 drive pipeline or efficiency are great. 617 00:30:13,151 --> 00:30:15,781 those will always be what I say with Ricardo because 618 00:30:16,111 --> 00:30:17,611 it's our tool and I love it. 619 00:30:17,611 --> 00:30:22,349 But I think another one, that's important Is, I'll just pull up a 620 00:30:22,349 --> 00:30:25,979 report that I think it's used every day by hundreds of people and it's, uh, 621 00:30:26,019 --> 00:30:28,162 it's a pipeline pacing report, right? 622 00:30:28,162 --> 00:30:33,012 for Q2 that we're in right now, are we ahead or behind pace for 623 00:30:33,012 --> 00:30:38,400 pipeline generation by source, 23 days into the quarter and then 624 00:30:38,420 --> 00:30:39,950 tomorrow we refresh that thing. 625 00:30:39,950 --> 00:30:41,480 And it's 24 days into a quarter. 626 00:30:41,480 --> 00:30:45,161 We're ahead or behind pace and It's by segment and then as you expand the 627 00:30:45,161 --> 00:30:47,031 segment, it has every team underneath. 628 00:30:47,071 --> 00:30:47,571 So I know. 629 00:30:47,571 --> 00:30:47,931 Okay. 630 00:30:47,931 --> 00:30:52,961 Overall, we're good with partners, but by double click, we're like doing great in 631 00:30:52,961 --> 00:30:54,681 a mea, but like, North America is behind. 632 00:30:54,681 --> 00:30:54,951 Right? 633 00:30:54,986 --> 00:30:55,746 what are we doing? 634 00:30:55,756 --> 00:30:58,492 And so knowing that, leading indicator piece. 635 00:30:59,317 --> 00:31:03,417 Is a really important part because it's beyond just a report. 636 00:31:03,427 --> 00:31:07,624 It's, transforming an organization to think not just about today. 637 00:31:08,904 --> 00:31:11,994 It's like thinking about long term success, future quarters. 638 00:31:12,796 --> 00:31:16,746 and so I think like, if you were to ask like what thing, when I 639 00:31:16,766 --> 00:31:20,636 came here in the last 18 months is like, hopefully trying to reorient 640 00:31:20,676 --> 00:31:25,955 and think beyond current quarter, for sustainable long term success. 641 00:31:26,525 --> 00:31:29,045 rather than coming into a quarter and be like, whew, thanks. 642 00:31:29,045 --> 00:31:30,045 We got enough pipeline. 643 00:31:30,665 --> 00:31:30,965 Great. 644 00:31:30,995 --> 00:31:31,435 All right. 645 00:31:31,435 --> 00:31:32,635 We, we feel okay. 646 00:31:33,905 --> 00:31:37,015 And then it's like, Ooh, pipeline got cleaned those first two weeks. 647 00:31:37,055 --> 00:31:37,815 Now we're behind. 648 00:31:37,845 --> 00:31:39,145 Oh no, now I don't feel good. 649 00:31:39,145 --> 00:31:39,395 Right. 650 00:31:39,395 --> 00:31:41,925 It's like, should be cleaned real time. 651 00:31:42,495 --> 00:31:46,035 So it's not like a cleanup every start of the quarter. 652 00:31:46,445 --> 00:31:49,575 We should know actually, before we even get to that quarter, we feel pretty 653 00:31:49,575 --> 00:31:52,885 good because we know we've been on track for the last three quarters or not. 654 00:31:53,669 --> 00:31:56,884 but that goes with, long term planning, annual planning goes into 655 00:31:56,894 --> 00:31:58,904 forecasting and having an idea about. 656 00:31:59,414 --> 00:32:00,984 running a forecast call. 657 00:32:01,424 --> 00:32:05,164 Part of my job is I run the sales forecast call for all of our business units. 658 00:32:05,374 --> 00:32:10,344 And when I go into that call, every week, eight or nine of the quarter, we have 659 00:32:10,344 --> 00:32:14,574 a current quarter forecast call, but we also have a future quarter forecast call 660 00:32:15,094 --> 00:32:18,494 and every rep and leader in the company will go and look at their next quarter, 661 00:32:18,494 --> 00:32:21,594 scrub the pipe and give an initial call for that against their number. 662 00:32:22,244 --> 00:32:25,428 And so it's not just pipeline, but we're talking forecast now, and then, 663 00:32:25,748 --> 00:32:29,142 you get beyond that and you're looking at an events calendar and marketing. 664 00:32:29,142 --> 00:32:33,117 And there's a lot of ways that you can be thinking more into the future, and I 665 00:32:33,117 --> 00:32:33,887 think that's key. 666 00:32:34,597 --> 00:32:37,797 Justin Norris: Let's drill on forecasting because a, it's just super interesting. 667 00:32:37,797 --> 00:32:38,677 It's super important. 668 00:32:38,677 --> 00:32:42,197 And it's an area where I think, a lot of businesses now that we're 669 00:32:42,197 --> 00:32:46,937 not in the hyper growth, free money, everyone's just buying everything mode. 670 00:32:47,377 --> 00:32:51,907 a lot of businesses perhaps have seen the fragility, the weaknesses in their 671 00:32:51,907 --> 00:32:55,894 own forecasting methodology to use a particular, like you, described it 672 00:32:55,894 --> 00:32:58,304 at a high level, some of the things that you do, is there a particular 673 00:32:58,304 --> 00:33:01,754 methodology you follow, or is it really just about, Clean data, regular 674 00:33:01,754 --> 00:33:02,984 inspection, that sort of thing. 675 00:33:03,456 --> 00:33:05,886 Cody Guymon: I think it's a lot of things, it is clean data. 676 00:33:05,916 --> 00:33:06,726 That's important. 677 00:33:07,019 --> 00:33:10,239 it is regular forecast calls weekly with inspection. 678 00:33:10,412 --> 00:33:14,082 it's knowing people well, reading people. 679 00:33:14,512 --> 00:33:18,092 you probably see right here, I've got a poker table in my office. 680 00:33:18,112 --> 00:33:22,262 Like part of my favorite thing is to read people like, are they bluffing me or not? 681 00:33:22,372 --> 00:33:22,702 Right. 682 00:33:22,752 --> 00:33:26,331 That's important to know, So there's the art and the science to all of it. 683 00:33:26,991 --> 00:33:32,890 And I think, can use all the data and analytics in the world for sure. 684 00:33:33,310 --> 00:33:38,705 But if you have a massive needle mover deal, have you done enough inspection on 685 00:33:38,705 --> 00:33:42,878 that, the analytics will give you a yay or nay based on like Salesforce hygiene. 686 00:33:43,928 --> 00:33:46,648 But, do we feel like we're going to go get that deal? 687 00:33:46,698 --> 00:33:47,408 Yes or no? 688 00:33:47,428 --> 00:33:49,308 Is the sales leader going to do whatever it takes? 689 00:33:49,308 --> 00:33:51,868 Is the sales rep going to go on site and camp out there for 690 00:33:51,868 --> 00:33:53,088 a week to get the deal done? 691 00:33:54,014 --> 00:33:57,604 there's a lot of intangible kind of things that I think are important to a forecast. 692 00:33:57,604 --> 00:33:59,224 So it's just about getting in the details. 693 00:33:59,404 --> 00:34:00,944 It's about knowing the needle mover deals. 694 00:34:01,184 --> 00:34:01,804 It's about. 695 00:34:02,244 --> 00:34:05,824 Knowing people and if they, if they sandbag or they don't, it's 696 00:34:05,824 --> 00:34:09,009 about, knowing if they have a claim, do they have multiple paths 697 00:34:09,159 --> 00:34:10,429 to that number or do they not? 698 00:34:11,349 --> 00:34:13,168 Is it a single path to that number? 699 00:34:13,168 --> 00:34:16,799 And so very risky, or is there multiple paths and what are those paths look like? 700 00:34:16,958 --> 00:34:19,149 and so you can rely on it a bit heavier. 701 00:34:20,040 --> 00:34:21,380 it's asking those questions. 702 00:34:21,860 --> 00:34:22,120 Okay. 703 00:34:22,120 --> 00:34:24,750 If that deal falls out, how do you get to that call still? 704 00:34:25,139 --> 00:34:28,344 And I also think, some people are too rigid on their forecast. 705 00:34:28,880 --> 00:34:34,070 manual submissions, there'll be like a commit and a high, like two things. 706 00:34:34,940 --> 00:34:37,585 You're like, well, it's just going to get you a massive range. 707 00:34:37,635 --> 00:34:38,594 Doesn't really help you. 708 00:34:38,594 --> 00:34:38,935 Right. 709 00:34:38,975 --> 00:34:40,309 So I like to do. 710 00:34:40,909 --> 00:34:45,239 A lot of people call it, uh, closest to Penn, nearest to Penn, but I, what I want 711 00:34:45,239 --> 00:34:49,831 to do is I want to hear that, but I I want somebody's response to that question. 712 00:34:50,960 --> 00:34:54,261 I don't want them to have fear if they actually think it went down 713 00:34:54,371 --> 00:34:58,701 week over week, with a low and a high, you want them to converge. 714 00:34:59,421 --> 00:35:02,541 Low, you never want to have drop on that range when you're getting 715 00:35:02,541 --> 00:35:04,091 the sides of your range, right? 716 00:35:05,166 --> 00:35:08,946 The high generally, I guess it would be okay if it goes up, but generally 717 00:35:08,946 --> 00:35:11,906 you want it to hold, or it probably is going to converge and come down 718 00:35:11,906 --> 00:35:12,926 a little bit as the quarter goes. 719 00:35:13,546 --> 00:35:16,646 But that like middle one, whatever you want to call it, your call, your 720 00:35:16,646 --> 00:35:19,966 forecast, your commit, your closest to the pin, whatever we use there. 721 00:35:21,126 --> 00:35:26,021 I think it's really important for people to be like, Plus or minus 3 percent on 722 00:35:26,021 --> 00:35:30,251 that number, like a lot of people just want to see that thing go up and so 723 00:35:30,251 --> 00:35:35,501 they'll say just plus 3%, but like, I don't want that to be a sandbag low number 724 00:35:35,501 --> 00:35:38,491 that just comes up every quarter because I actually then don't know what we're at. 725 00:35:38,591 --> 00:35:42,461 But if there's lack of like fear of retaliation on that one coming a little 726 00:35:42,461 --> 00:35:46,481 bit now, if that thing catapults to the low, that, I mean, that's a whole 727 00:35:46,481 --> 00:35:49,991 nother story, but if you're plus or minus 5 percent on that thing, and you're 728 00:35:49,991 --> 00:35:53,965 generally hitting right or right at it, maybe four weeks into a quarter, I think 729 00:35:53,975 --> 00:35:57,385 that's important too, is to create an environment where you can get honesty. 730 00:35:57,965 --> 00:36:01,275 I've been at some organizations where it's like, you better come out the 731 00:36:01,275 --> 00:36:05,375 gates forecasting at least 80 percent of the number or you could get fired. 732 00:36:05,385 --> 00:36:07,435 Well, what if really the forecast is 60? 733 00:36:08,012 --> 00:36:11,089 you want them just to lie, to make you feel better about 734 00:36:11,089 --> 00:36:12,999 it so they don't get fired? 735 00:36:12,999 --> 00:36:14,439 Like, it's just a weird environment. 736 00:36:14,449 --> 00:36:17,289 But if you're like, no, no, no, I want to know the real all the time. 737 00:36:17,569 --> 00:36:22,065 And that also means on the high, I want to know the real, I don't want you to parking 738 00:36:22,065 --> 00:36:27,765 lot deals in the next quarter that you can bring in in the last second and be a hero. 739 00:36:27,765 --> 00:36:29,135 That's not going to be a hero to me. 740 00:36:29,670 --> 00:36:33,810 And I'd rather have it be an upside deal within the current quarter. 741 00:36:33,810 --> 00:36:34,990 Like, so we know about it. 742 00:36:34,990 --> 00:36:37,030 Let's just be honest and communicate about it. 743 00:36:37,070 --> 00:36:37,750 So we're, good. 744 00:36:37,770 --> 00:36:42,190 And I also know if you've exceeded your number on the last day of the quarter and 745 00:36:42,190 --> 00:36:45,860 you want to push them stuff, you can also tell me, if you need it, we can bring 746 00:36:45,860 --> 00:36:49,350 it in at the global level, but I might not push for that signature today because 747 00:36:49,530 --> 00:36:51,460 I have a light next quarter pipeline. 748 00:36:51,460 --> 00:36:53,720 It feels good to start off a little bit better, but I'll do it. 749 00:36:54,050 --> 00:36:56,780 Like I want to hear that concern come out I don't want to be 750 00:36:56,780 --> 00:36:58,060 searching for it, you know? 751 00:36:58,404 --> 00:37:02,820 Justin Norris: It's so logical and common sense what you're saying and it's cultural 752 00:37:02,820 --> 00:37:04,650 and it's back to not being a jerk. 753 00:37:04,734 --> 00:37:05,654 all that good stuff. 754 00:37:06,114 --> 00:37:07,944 And yet it's, not that common. 755 00:37:07,954 --> 00:37:11,960 Like the negative stereotype of sales culture is the other thing you said, 756 00:37:11,960 --> 00:37:16,790 encouraging this deceptive dishonest behavior and that's really toxic and 757 00:37:16,790 --> 00:37:19,620 it's actually harmful to business performance, not just harmful to people. 758 00:37:19,890 --> 00:37:21,620 why does that dysfunction exist? 759 00:37:21,620 --> 00:37:24,410 Do you think, why are more people not kind of commonsensical the 760 00:37:24,410 --> 00:37:25,380 way that you just described? 761 00:37:25,745 --> 00:37:33,393 Cody Guymon: I think a lack of, probably fear, it's a fear based culture, you know, 762 00:37:33,393 --> 00:37:38,203 and you don't have somebody that's willing to say like, no, I want transparency. 763 00:37:38,203 --> 00:37:39,093 I want honesty. 764 00:37:39,093 --> 00:37:42,623 I want, that then it's really hard, you're in an environment where that's like, 765 00:37:42,633 --> 00:37:46,143 tops down and you have to come out the gates a certain number, you could get 766 00:37:46,153 --> 00:37:48,483 fired and like, That's just the culture. 767 00:37:48,973 --> 00:37:51,990 you need somebody brave to push back against that. 768 00:37:52,250 --> 00:37:57,800 and that's rare because I think, people want to be comfortable and maybe don't 769 00:37:57,800 --> 00:38:00,220 want to stand up to that type of stuff. 770 00:38:00,240 --> 00:38:03,464 But, it is rare ish. 771 00:38:03,464 --> 00:38:08,365 hopefully it's like becoming less and less rare, but it can set you apart. 772 00:38:08,595 --> 00:38:12,560 I think for those that are opportunistic listening to this, Like if you want to 773 00:38:12,560 --> 00:38:16,959 set yourself apart as a RevOps leader, be willing to get uncomfortable. 774 00:38:18,389 --> 00:38:21,189 Be willing to ask like uncomfortable questions and just sit in 775 00:38:21,189 --> 00:38:22,349 the silence for a little bit. 776 00:38:22,349 --> 00:38:24,929 Like, Hey, are you really just committing that deal? 777 00:38:24,929 --> 00:38:28,449 Cause you like are worried if your commits lower, like you're going to 778 00:38:28,549 --> 00:38:31,709 hit a list on a PIP list somewhere. 779 00:38:32,159 --> 00:38:34,923 Cause like, I feel like there's no way you're getting to that number. 780 00:38:35,203 --> 00:38:36,623 Convince me that I'm wrong, please. 781 00:38:36,633 --> 00:38:39,283 Because like, I want to know why you're saying that number. 782 00:38:39,313 --> 00:38:42,673 Maybe I'm missing something, but that feels forced. 783 00:38:43,043 --> 00:38:43,783 It feels. 784 00:38:44,903 --> 00:38:46,463 Like, it's not going to happen. 785 00:38:48,273 --> 00:38:50,503 I would love for it to like, tell me why. 786 00:38:50,513 --> 00:38:52,033 And maybe you're opportunistic. 787 00:38:52,033 --> 00:38:53,333 There's some stuff that I don't know about. 788 00:38:53,343 --> 00:38:53,703 Great. 789 00:38:53,733 --> 00:38:57,353 But like, I think those are the type of combos that's really where 790 00:38:57,923 --> 00:39:01,123 you can set yourself apart versus just like reporting the news. 791 00:39:01,123 --> 00:39:01,423 Right. 792 00:39:02,233 --> 00:39:03,623 Oh, the forecast was 90%. 793 00:39:04,123 --> 00:39:07,996 It's going to be 90 percent and I think it takes a leader to be like, no, what 794 00:39:07,996 --> 00:39:09,186 do you actually think it's going to be? 795 00:39:10,247 --> 00:39:11,797 well, I think it's going to be like 70%. 796 00:39:12,077 --> 00:39:12,427 Why? 797 00:39:12,932 --> 00:39:16,262 Because the data says this and I think this person's kind of scared 798 00:39:16,262 --> 00:39:18,532 because they had a bad quarter last quarter and they don't want to come 799 00:39:18,532 --> 00:39:20,092 out the gates with another bad call. 800 00:39:20,102 --> 00:39:21,242 So they're probably inflating it. 801 00:39:21,571 --> 00:39:23,031 you know, you just got to dig a little bit. 802 00:39:23,143 --> 00:39:24,174 but you can set yourself apart, 803 00:39:24,302 --> 00:39:24,832 Justin Norris: I love it. 804 00:39:25,037 --> 00:39:29,364 one of the things maybe that's in your, corner, at least now at 805 00:39:29,364 --> 00:39:30,874 Workato having that conversation. 806 00:39:30,874 --> 00:39:36,706 You know, you had a great run at Qualtrics and you hit some highs that not, everyone 807 00:39:36,706 --> 00:39:38,416 gets to hit probably relatively small. 808 00:39:38,961 --> 00:39:42,728 Number of people get to have those sorts of exits So maybe first question 809 00:39:42,828 --> 00:39:45,638 is do you feel that that's like an asset that previous experience 810 00:39:45,638 --> 00:39:46,848 now that you go into new roles? 811 00:39:46,848 --> 00:39:51,048 And number two, maybe just walk us through Some of that journey and some 812 00:39:51,048 --> 00:39:54,553 of the battle scars and things that you learn through that kind of growth 813 00:39:54,939 --> 00:39:55,489 Cody Guymon: for sure. 814 00:39:55,619 --> 00:40:00,339 No, I feel very fortunate, very blessed to have joined Qualtrics when I did. 815 00:40:00,339 --> 00:40:03,019 I mean, I joined a rocket ship that was taken off. 816 00:40:03,019 --> 00:40:07,309 And so a lot of that was just, yeah, I'm grateful. 817 00:40:07,529 --> 00:40:10,799 Grateful that I joined when I did, because I think I learned 818 00:40:12,169 --> 00:40:13,939 30 years of experience in six. 819 00:40:13,939 --> 00:40:17,254 I we went from 100 million in revenue to 1. 820 00:40:17,254 --> 00:40:18,084 5 billion when I left. 821 00:40:18,154 --> 00:40:20,534 I mean, it's like, It's insane. 822 00:40:20,534 --> 00:40:24,914 Not many companies grow that fast and go through such transformational 823 00:40:24,924 --> 00:40:29,974 organizational changes in such a short time that it's wild. 824 00:40:30,074 --> 00:40:34,204 We put some op stability in place and prep to go public. 825 00:40:34,439 --> 00:40:36,249 And, you know, Sequoia gave a checklist. 826 00:40:36,269 --> 00:40:37,929 Here's the things you got to do to go public. 827 00:40:37,929 --> 00:40:39,049 We create the roadshow deck. 828 00:40:39,049 --> 00:40:40,369 We got to do the things. 829 00:40:42,139 --> 00:40:44,919 And then we got acquired by SAP a couple of days before going public 830 00:40:44,929 --> 00:40:49,393 for 8 billion, which was super exciting, fun, sad for some people. 831 00:40:49,393 --> 00:40:50,663 Some people wanted to go public. 832 00:40:50,663 --> 00:40:53,193 So, finance team was like, Oh, I wanted that on the resume 833 00:40:53,193 --> 00:40:54,253 and now it's gone, whatever. 834 00:40:54,253 --> 00:40:58,723 But, it was a crazy experience to go then for the next two years. 835 00:40:59,313 --> 00:41:02,423 Learn what a big company does at scale. 836 00:41:02,433 --> 00:41:03,923 How do they operate at scale? 837 00:41:04,013 --> 00:41:06,513 How do they operate with 15 lines of businesses? 838 00:41:07,193 --> 00:41:10,433 How do they forecast with 15 lines of businesses? 839 00:41:10,783 --> 00:41:14,473 How do they communicate about opportunities where you might have 840 00:41:14,483 --> 00:41:18,193 four businesses all working with the same economic buyer at the same time? 841 00:41:18,283 --> 00:41:18,753 Like that's. 842 00:41:20,123 --> 00:41:24,193 learning experience being a part of a company that was when I joined 600 843 00:41:24,193 --> 00:41:28,843 people at the acquisition, maybe it was 2000 people, and then I showed 844 00:41:28,853 --> 00:41:32,853 up to the first sales kickoff event for SAP it's called field kickoff. 845 00:41:33,733 --> 00:41:35,033 And I show up to that event. 846 00:41:35,033 --> 00:41:37,493 There's 15, 000 sellers in North America. 847 00:41:38,726 --> 00:41:40,506 and you're learning how do they do that at scale? 848 00:41:40,656 --> 00:41:43,056 so I learned so much there that was helpful. 849 00:41:44,361 --> 00:41:49,018 my career and got tutored by some amazing ops leaders there. 850 00:41:49,018 --> 00:41:54,308 And, but then I also learned what, kept Qualtrics as a small, nimble machine. 851 00:41:54,308 --> 00:41:56,668 What's the advantages of being small and nimble too. 852 00:41:56,688 --> 00:42:00,428 Like there's a reason we were outpacing growth of the big company 853 00:42:00,468 --> 00:42:04,268 because we, we can move quick, like steering a cruise ship's hard, 854 00:42:05,009 --> 00:42:06,449 steering speed boats pretty easy. 855 00:42:07,449 --> 00:42:08,644 So, learn that. 856 00:42:08,684 --> 00:42:11,466 And then two years after the acquisition, it was, we're going 857 00:42:11,466 --> 00:42:12,596 to break off and go public. 858 00:42:13,146 --> 00:42:15,026 And so we were ready for that. 859 00:42:15,026 --> 00:42:17,976 So that was prepping for you go public again for the second time. 860 00:42:18,581 --> 00:42:20,301 And then actually going public. 861 00:42:20,331 --> 00:42:24,308 And we went public in a COVID environment, which was wild. 862 00:42:24,308 --> 00:42:27,438 I mean, it was like a virtual ringing of the bell, you know, it was like 863 00:42:27,438 --> 00:42:29,988 a button and it wasn't a New York. 864 00:42:29,988 --> 00:42:30,198 It was 865 00:42:30,198 --> 00:42:31,698 like in the Utah office, 866 00:42:31,887 --> 00:42:32,507 Justin Norris: it on zoom? 867 00:42:32,705 --> 00:42:36,115 Cody Guymon: was on zoom, I was in my house just watching it on my TV, right. 868 00:42:36,115 --> 00:42:36,955 It was just wild. 869 00:42:37,145 --> 00:42:37,825 It was just different. 870 00:42:38,825 --> 00:42:42,245 And so, yeah, I learned a lot about that, but then being public 871 00:42:42,245 --> 00:42:43,235 is a whole different beast. 872 00:42:44,195 --> 00:42:47,585 Being public is a different beast than being acquired by somebody that's public. 873 00:42:47,661 --> 00:42:51,311 we were a blip in SAP's radar as far as revenue goes. 874 00:42:52,121 --> 00:42:56,612 But then like actually, setting a beat and raise model, you know, quarterly 875 00:42:56,612 --> 00:43:01,492 earnings calls, prepping for those, having actual stress of like that ticker 876 00:43:01,562 --> 00:43:04,272 right there that I'm looking at, it's going to go up or down based on the 877 00:43:04,272 --> 00:43:06,492 quarter, whole different environment. 878 00:43:06,492 --> 00:43:08,802 So I did that for like six quarters, seven quarters. 879 00:43:09,532 --> 00:43:14,232 And then, um, wanted to go back private, smaller, do it again. 880 00:43:14,482 --> 00:43:19,118 So joined Ricardo's later stage series, E last valuation, 5. 881 00:43:19,148 --> 00:43:19,788 7 billion. 882 00:43:19,788 --> 00:43:23,038 And, just felt like that the team here and the product is great. 883 00:43:23,128 --> 00:43:27,768 And so made the jump here to try and go rinse and repeat and hopefully 884 00:43:27,768 --> 00:43:31,308 get Ricardo to that big, billion plus in revenue one day and all that 885 00:43:31,308 --> 00:43:31,908 fun stuff too. 886 00:43:32,277 --> 00:43:33,637 Justin Norris: Well, I think you made a good decision there. 887 00:43:33,637 --> 00:43:37,694 And I'm curious as you were describing that, really amazing journey. 888 00:43:37,694 --> 00:43:40,674 you asked some hypotheticals, like how do you communicate about opportunities? 889 00:43:40,674 --> 00:43:41,514 How do you forecast it? 890 00:43:41,754 --> 00:43:43,684 Like, I'm actually curious for the answers to those things. 891 00:43:43,684 --> 00:43:45,917 Obviously you can't give it in depth, but give us an example. 892 00:43:45,917 --> 00:43:48,557 cause it does kind of boggle the mind a little bit about how you 893 00:43:48,557 --> 00:43:50,077 would do that at that sort of scale. 894 00:43:50,077 --> 00:43:52,037 If at least for me, who has not experienced that. 895 00:43:52,372 --> 00:43:56,332 Cody Guymon: So at each level in an organization, you 896 00:43:56,332 --> 00:43:57,772 sync with your counterparts. 897 00:43:58,082 --> 00:44:03,442 And there's generally like at the head company, like a sales leader, that's 898 00:44:03,442 --> 00:44:05,112 over all of the lines of business. 899 00:44:05,112 --> 00:44:05,362 Right. 900 00:44:05,402 --> 00:44:10,544 So like Qualtrics, would represent the global forecast for Qualtrics. 901 00:44:11,089 --> 00:44:17,609 And so I would join a call with the global SAP software leader. 902 00:44:17,619 --> 00:44:21,649 And I would be one of 10 lines of businesses, right? 903 00:44:21,759 --> 00:44:25,839 You've got Concur and you have SuccessFactors and you 904 00:44:25,839 --> 00:44:27,229 have lots of other products. 905 00:44:28,259 --> 00:44:32,669 And so I'm giving the Qualtrics number and then someone else is giving 906 00:44:32,669 --> 00:44:37,359 this number and it's all aggregating together in this like massive tool. 907 00:44:38,529 --> 00:44:40,129 and then you get that forecast, right? 908 00:44:40,129 --> 00:44:42,579 So that person's making the same judgments against me that 909 00:44:42,579 --> 00:44:44,959 I'm making like, am I truthful? 910 00:44:44,959 --> 00:44:46,599 Am I a beat and raise person? 911 00:44:46,609 --> 00:44:47,869 Do I miss a lot? 912 00:44:47,899 --> 00:44:51,234 Like they're doing that for their Global unit for the overall 913 00:44:51,234 --> 00:44:51,624 call. 914 00:44:51,791 --> 00:44:53,141 Justin Norris: So it just becomes a roll up of 915 00:44:53,141 --> 00:44:54,791 a roll up of a roll up type of thing. 916 00:44:54,846 --> 00:44:56,726 Cody Guymon: it's a roll up of a roll up and they're all the same. 917 00:44:56,746 --> 00:44:58,326 Every call is the same call. 918 00:44:58,326 --> 00:44:59,506 It's just a roll up of a roll up. 919 00:44:59,506 --> 00:45:04,066 So think about SAP, like with just a lot of product lines, 920 00:45:04,066 --> 00:45:08,516 like if you at your company have multiple product lines, right? 921 00:45:08,516 --> 00:45:10,506 So like at Qualtrics, we had multiple product lines. 922 00:45:10,516 --> 00:45:13,186 So I would get a product line forecast for each of them. 923 00:45:14,176 --> 00:45:17,086 And so imagine that's just like a line of business instead of like 924 00:45:17,086 --> 00:45:18,296 a product within your own company. 925 00:45:18,296 --> 00:45:18,496 Right. 926 00:45:18,496 --> 00:45:21,166 It kind of is, it's a sub product of a bigger company. 927 00:45:21,166 --> 00:45:21,856 And so it's just. 928 00:45:22,226 --> 00:45:23,896 It's kind of the same thing. 929 00:45:23,936 --> 00:45:26,906 And it goes back to the principles we talked about of like, how 930 00:45:26,906 --> 00:45:28,096 do you get accurate at that? 931 00:45:28,126 --> 00:45:32,776 You create transparency, you create safe environments, you dig in and questions. 932 00:45:32,776 --> 00:45:36,026 You have data that will support, you ask really good questions that the data 933 00:45:36,066 --> 00:45:38,096 says that validates or invalidates it. 934 00:45:39,016 --> 00:45:41,226 But it's ultimately the same thing, which is kind of an 935 00:45:41,226 --> 00:45:42,966 interesting thing that I learned. 936 00:45:43,077 --> 00:45:45,077 it's just a lot of layers. 937 00:45:45,127 --> 00:45:48,257 So instead of like in your company, you might have four sales layers. 938 00:45:48,287 --> 00:45:49,017 You might have. 939 00:45:49,372 --> 00:45:52,682 15 to 30 sales later layers at a bigger company. 940 00:45:52,682 --> 00:45:54,082 And each group has their own thing. 941 00:45:54,082 --> 00:45:57,472 So the head of North America will have a forecast with all the North 942 00:45:57,472 --> 00:45:59,482 America line of business leaders. 943 00:46:00,102 --> 00:46:01,152 And then you go beyond that. 944 00:46:01,152 --> 00:46:06,382 And it's like the AVP of enterprise West for SAP, we'll be meeting with all the 945 00:46:06,382 --> 00:46:09,122 AVPs of enterprise West for all of the. 946 00:46:09,702 --> 00:46:13,568 Lines of businesses because they all got to coordinate on the, opportunities. 947 00:46:13,568 --> 00:46:13,798 Right? 948 00:46:13,798 --> 00:46:19,018 So it's like, if one of the lines of businesses has a 2 million deal going 949 00:46:19,018 --> 00:46:22,208 with Apple, it's like, Oh, I've also got something going with Apple and the work. 950 00:46:22,228 --> 00:46:23,958 Can I work on that with you? 951 00:46:23,958 --> 00:46:24,948 And we can coordinate, right? 952 00:46:24,968 --> 00:46:26,588 It's all about coordination at that point. 953 00:46:27,178 --> 00:46:28,708 Pipeline transparency. 954 00:46:28,708 --> 00:46:32,781 And, you're working a bill of materials now with Apple at the executive level. 955 00:46:32,781 --> 00:46:36,141 You're not just doing a departmental deal with like, a manager you're 956 00:46:36,151 --> 00:46:37,851 now going at like, Oh, wow. 957 00:46:37,851 --> 00:46:40,457 We're going to deal with the CEO of that big company. 958 00:46:41,118 --> 00:46:43,478 it's going to be part of a larger deal. 959 00:46:44,068 --> 00:46:47,298 We call them bombs or bill of materials as part of a larger 960 00:46:47,298 --> 00:46:48,968 bill of material transaction. 961 00:46:49,558 --> 00:46:53,508 But it's ultimately the same thing as if you are a company with multiple products, 962 00:46:54,598 --> 00:46:55,488 Justin Norris: That's wild, man. 963 00:46:56,108 --> 00:46:56,928 that's pretty far out. 964 00:46:57,371 --> 00:47:00,901 appreciate that glimpse in, uh, inside, you know, steering 965 00:47:00,901 --> 00:47:02,141 the cruise ship, as you put it. 966 00:47:02,841 --> 00:47:05,511 maybe the last, question we have time for, and we'll just shift gears a little. 967 00:47:05,521 --> 00:47:09,510 I, I'm super curious, for people, especially that have, Managed to go 968 00:47:09,510 --> 00:47:14,580 through these growth stages and have achieved a lot just ways of working and 969 00:47:14,610 --> 00:47:19,640 personal systems routines You have 10 million things that require your attention 970 00:47:19,650 --> 00:47:24,190 at any point in time you start your day How do you kind of figure out where to? 971 00:47:24,950 --> 00:47:28,640 Direct your focus and make sure that you're prioritizing the right things 972 00:47:29,060 --> 00:47:29,250 Cody Guymon: Yeah. 973 00:47:29,250 --> 00:47:31,353 I think, especially in a remote environment. 974 00:47:31,608 --> 00:47:36,418 people have got to have routines and systems, I'm up every day, seven o'clock 975 00:47:36,418 --> 00:47:39,068 in the morning or earlier, right? 976 00:47:39,068 --> 00:47:43,872 It's never after I'm getting going mountain time, usually seven 30. 977 00:47:44,612 --> 00:47:47,878 and then I'll go late, you know, if I'm working with, APJ region, 978 00:47:47,888 --> 00:47:50,008 but like, I have my time dedicated. 979 00:47:50,008 --> 00:47:53,108 My calendar is like insane. 980 00:47:53,388 --> 00:47:56,478 I think we scheduled this thing like six weeks ago. 981 00:47:57,128 --> 00:48:00,758 Like, you just have to have like, be dialed on like, do 982 00:48:00,758 --> 00:48:02,318 you have hard work ethic? 983 00:48:02,478 --> 00:48:06,328 Are you somebody that's just going to crank, you know, and ops, 984 00:48:06,328 --> 00:48:08,068 you should have a motor, right? 985 00:48:08,068 --> 00:48:09,428 You should have an ability to work hard. 986 00:48:10,728 --> 00:48:13,105 and so those systems, matter. 987 00:48:13,105 --> 00:48:14,805 I think there's a second part of your. 988 00:48:15,935 --> 00:48:19,205 Question about more prioritization rather than like actually 989 00:48:19,205 --> 00:48:21,375 like work ethic and tools. 990 00:48:21,375 --> 00:48:25,586 And I think prioritization is always the battle, but I talked about a little 991 00:48:25,586 --> 00:48:29,346 bit earlier, but urgent and important, where does it fall on that quad? 992 00:48:29,396 --> 00:48:30,376 Is it, top, right? 993 00:48:30,446 --> 00:48:34,156 Is it super urgent and super important than we've got to prioritize that one. 994 00:48:34,886 --> 00:48:38,192 And then where do they fall off and which trade offs do you make are the other ones. 995 00:48:38,212 --> 00:48:40,502 So that's generally what I'm trying to do. 996 00:48:40,532 --> 00:48:42,722 I mean, every day I come in and I've got. 997 00:48:43,160 --> 00:48:46,500 like a note card with like the five things I need to like get done 998 00:48:46,500 --> 00:48:49,700 that day or three things sometimes, sometimes it's one thing like today. 999 00:48:49,700 --> 00:48:51,820 It's like board deck board deck needs to get done. 1000 00:48:51,820 --> 00:48:52,720 And I got this podcast. 1001 00:48:52,770 --> 00:48:53,440 That's like. 1002 00:48:54,265 --> 00:48:55,385 All hands on deck. 1003 00:48:55,465 --> 00:48:57,355 So we have a board meeting next week. 1004 00:48:57,995 --> 00:49:01,655 So coming in and I like to start with like a fresh piece of paper every day. 1005 00:49:01,885 --> 00:49:04,105 And I just sit, you know, early in the morning. 1006 00:49:04,805 --> 00:49:05,905 This is what I need to get done. 1007 00:49:06,055 --> 00:49:10,335 This is what we needed to get done as a team one thing that I do is like, 1008 00:49:11,345 --> 00:49:13,235 what can I cancel from my calendar? 1009 00:49:14,665 --> 00:49:18,035 I think that's important every day to do any of these meetings, do they 1010 00:49:18,035 --> 00:49:19,515 slip out of urgent and important? 1011 00:49:19,915 --> 00:49:21,605 And are they part of this list that I wrote down? 1012 00:49:21,605 --> 00:49:23,445 If they're not, can I bump them a week? 1013 00:49:24,405 --> 00:49:25,525 Sometimes that's annoying. 1014 00:49:25,525 --> 00:49:28,285 Like, so sometimes if I've like bumped it enough, I got to be like, okay, I got to 1015 00:49:28,285 --> 00:49:31,595 take that meeting because it's urgent now because I've bumped it multiple times, 1016 00:49:31,595 --> 00:49:35,525 but I think it's important to really get strict on prioritization and I'll say it. 1017 00:49:35,555 --> 00:49:37,735 Hey, sorry, board decks, everything right now. 1018 00:49:37,925 --> 00:49:38,845 I got to bump this meeting. 1019 00:49:39,565 --> 00:49:44,288 but generally it's like being able to say no, being able to push stuff off, being 1020 00:49:44,288 --> 00:49:47,598 able to prioritize your day and then making sure things fall in line with it. 1021 00:49:47,598 --> 00:49:49,908 I think in day by day, if you're doing that every day, then 1022 00:49:49,908 --> 00:49:51,448 your year became prioritized. 1023 00:49:51,618 --> 00:49:54,238 So I don't try and make it like too complex. 1024 00:49:54,528 --> 00:49:59,318 I'm not one to like file it all in JIRA and project management tools 1025 00:49:59,388 --> 00:50:02,688 I'm sure somebody can help me with that, but I'm just like pen and paper. 1026 00:50:03,398 --> 00:50:04,218 Excel spreadsheets. 1027 00:50:04,228 --> 00:50:04,508 Great. 1028 00:50:05,024 --> 00:50:05,494 Justin Norris: I love it. 1029 00:50:05,544 --> 00:50:08,934 And I am grateful that I was the second thing on your list today. 1030 00:50:08,944 --> 00:50:11,834 In addition to the board deck, I really appreciate that. 1031 00:50:12,334 --> 00:50:14,324 This was a super fun chat, Cody. 1032 00:50:14,324 --> 00:50:15,984 So thank you very much for doing it. 1033 00:50:16,345 --> 00:50:16,875 Cody Guymon: Thank you. 1034 00:50:16,895 --> 00:50:17,485 I had a blast. 1035 00:50:17,485 --> 00:50:18,192 this was awesome.