1 00:00:14,267 --> 00:00:15,677 Justin Norris: welcome to rev ops FM. 2 00:00:15,677 --> 00:00:19,467 Everyone today, we're going to take a deep look at how to run go to market 3 00:00:19,467 --> 00:00:23,507 systems at enterprise scale and even more exciting, we'll get a peek 4 00:00:23,507 --> 00:00:28,207 behind the scenes at one of the most iconic tech companies around HubSpot. 5 00:00:28,777 --> 00:00:32,827 Today's guest is rich Archibald VP engineering for GTM systems 6 00:00:32,847 --> 00:00:34,357 and automation at HubSpot. 7 00:00:34,367 --> 00:00:35,297 We're among other things. 8 00:00:35,637 --> 00:00:38,697 His team manages HubSpot's own HubSpot implementation, 9 00:00:39,117 --> 00:00:40,987 FinTech and data engineering. 10 00:00:41,527 --> 00:00:45,057 Prior to HubSpot, Rich held engineering and business systems leadership roles 11 00:00:45,057 --> 00:00:47,587 at companies like Intercom and Facebook. 12 00:00:48,197 --> 00:00:50,287 And Rich, I just have a ton of questions for you today. 13 00:00:50,287 --> 00:00:53,977 So we're going to dive in and I'm really appreciative of you coming on the show. 14 00:00:54,585 --> 00:00:55,455 Rich Archbold: Thanks Justin. 15 00:00:55,965 --> 00:00:59,895 I'm delighted to be here and as I said offline, thank you so much 16 00:00:59,895 --> 00:01:01,635 for all of the content you put out. 17 00:01:01,845 --> 00:01:06,073 I am an avid listener of your podcast and just find it so helpful. 18 00:01:06,095 --> 00:01:06,885 Justin Norris: Thank you so much. 19 00:01:07,538 --> 00:01:09,888 To start with maybe just a little bit about your background. 20 00:01:09,888 --> 00:01:13,414 You've written about how you started out, in more of an infrastructure 21 00:01:13,425 --> 00:01:15,125 backend engineering type of role. 22 00:01:15,470 --> 00:01:16,990 Transition to business systems. 23 00:01:17,400 --> 00:01:19,990 I'd love to understand from an engineer's perspective, what kind of 24 00:01:20,060 --> 00:01:22,030 shock to the system did that provide? 25 00:01:22,030 --> 00:01:24,070 And what were some of the learnings that you went through 26 00:01:24,100 --> 00:01:25,090 as you entered that field? 27 00:01:25,826 --> 00:01:29,396 Rich Archbold: so as you said, I started off in backend infrastructure 28 00:01:29,901 --> 00:01:31,736 engineering and I think. 29 00:01:32,103 --> 00:01:39,652 I always loved solving hard, gnarly scalability and operations challenges 30 00:01:39,743 --> 00:01:44,183 and didn't really mind if other people didn't find them glamorous or if 31 00:01:44,183 --> 00:01:48,539 there wasn't a shiny front end set of systems you needed to deal with. 32 00:01:48,620 --> 00:01:53,140 So perhaps it was kind of no surprise that I Eventually made the move into 33 00:01:53,140 --> 00:01:55,511 business systems and go to market systems. 34 00:01:56,331 --> 00:02:02,261 It started out at Intercom, where at the time we had a homegrown billing 35 00:02:02,261 --> 00:02:09,531 system that operated as an Integration layer between Salesforce and Zora, 36 00:02:10,021 --> 00:02:12,181 and this was maybe 4 or 5 years ago. 37 00:02:12,181 --> 00:02:16,493 Now, when, I think we were making so many changes to pricing and packaging at the 38 00:02:16,503 --> 00:02:21,333 time, and maybe how we had implemented some of our usage based billing systems, 39 00:02:21,373 --> 00:02:23,439 uh, intercom just really didn't. 40 00:02:23,439 --> 00:02:25,059 integrate well with Zora at. 41 00:02:25,436 --> 00:02:31,366 we were having a lot of operational challenges, scaling Zora and our CEO 42 00:02:31,366 --> 00:02:34,716 at the time said, Rich, you seem to be good at fixing backend systems, 43 00:02:34,716 --> 00:02:37,946 any chance you could jump in and take a look at our billing system. 44 00:02:37,946 --> 00:02:43,436 And that, really was the beginning jump off point for me, diving into 45 00:02:43,436 --> 00:02:49,876 billing systems and realizing that these are like fascinating, very 46 00:02:49,896 --> 00:02:52,711 difficult, Computational problems. 47 00:02:52,930 --> 00:02:58,341 there's real magic and innovation in integrating between your pricing and 48 00:02:58,341 --> 00:03:04,851 packaging and somebody else's product catalog and billing systems and learning 49 00:03:04,861 --> 00:03:07,821 how you need to match up data models and. 50 00:03:08,189 --> 00:03:09,699 found it absolutely fascinating. 51 00:03:09,949 --> 00:03:14,050 I incredibly difficult and just had a real appreciation for the engineers and leaders 52 00:03:14,050 --> 00:03:18,540 who work in this space that there's, there's just really valuable craft. 53 00:03:19,240 --> 00:03:24,500 I think, while the engineering work was difficult, the more difficult thing was 54 00:03:24,510 --> 00:03:28,829 stakeholder management and understanding who your internal customers are really 55 00:03:28,860 --> 00:03:33,860 being on that point of intersection between oil and water, almost where 56 00:03:33,870 --> 00:03:39,760 you have, salespeople and sales that really work to the quarter and have 57 00:03:39,790 --> 00:03:45,376 quarterly targets and have, like really hard deadlines they need to hit and 58 00:03:45,805 --> 00:03:51,163 really, meaningful performance based compensation that if they can't hit 59 00:03:51,163 --> 00:03:55,683 it, it's really materially impacts them and engineers and product managers 60 00:03:55,803 --> 00:04:01,513 on the other side who operate to like a much more gentle or longer term 61 00:04:01,543 --> 00:04:06,813 cadence and understanding the friction that can happen when people don't. 62 00:04:06,823 --> 00:04:09,975 really understand each other, and, don't really have the 63 00:04:09,975 --> 00:04:11,395 right empathy for each other. 64 00:04:11,445 --> 00:04:16,849 And that kind of human relationship building and empathy and understanding of. 65 00:04:17,428 --> 00:04:21,129 Each side of the coin, I found every bit as interesting and humbling 66 00:04:21,639 --> 00:04:23,189 as, the actual engineering work. 67 00:04:23,189 --> 00:04:26,313 And, over time, I grew to love the space. 68 00:04:26,313 --> 00:04:27,323 I like the. 69 00:04:27,953 --> 00:04:31,437 Breath of different people you get to interact with and learn all 70 00:04:31,447 --> 00:04:32,567 different parts of the business. 71 00:04:33,337 --> 00:04:38,884 and progressively, then I moved from leading our, teams in, owning, billing 72 00:04:39,264 --> 00:04:42,124 to when intercom hired its first CFO. 73 00:04:42,494 --> 00:04:46,573 I switched to report to the CFO to build out are first ever centralized 74 00:04:46,613 --> 00:04:50,263 business systems function and run go to market applications, which had 75 00:04:50,403 --> 00:04:56,406 salesforce marketo and intercom on intercom, our billing team and also 76 00:04:56,406 --> 00:04:58,996 took over our data engineering teams. 77 00:04:59,046 --> 00:05:04,478 And again, that was just, So many new things to learn that I'm really 78 00:05:04,478 --> 00:05:08,638 kind of motivated by learning, and I love to learn new things. 79 00:05:09,088 --> 00:05:11,018 Some people would say they have 20 years of experience. 80 00:05:11,168 --> 00:05:12,418 And I go, is that really 20 years? 81 00:05:12,448 --> 00:05:14,828 Or is it the same 1 year, 20 times over? 82 00:05:15,338 --> 00:05:20,627 And I try and kind of push myself to have a new year of experience every time and 83 00:05:20,987 --> 00:05:25,697 getting to report to a CFO and having all of, like, really Senior finance 84 00:05:25,697 --> 00:05:28,857 execs in your peer group was just a gift. 85 00:05:28,917 --> 00:05:30,447 Fascinating learning experience. 86 00:05:30,707 --> 00:05:34,297 Justin Norris: And you alluded a little bit to the contrast between what you were 87 00:05:34,297 --> 00:05:38,397 doing in business systems and folks on the product side, where you've got engineering 88 00:05:38,397 --> 00:05:40,347 teams and product management teams. 89 00:05:40,557 --> 00:05:44,137 And in that structure, every team's a little bit different, but usually 90 00:05:44,137 --> 00:05:45,567 product management is kind of. 91 00:05:46,127 --> 00:05:51,167 The interface between, the customer and business needs and then the 92 00:05:51,167 --> 00:05:55,227 engineering team who's responsible for how do we bring this to life 93 00:05:55,247 --> 00:05:57,087 in a technically scalable way. 94 00:05:57,567 --> 00:06:00,607 And then in business systems, you kind of have that stripped away. 95 00:06:00,607 --> 00:06:03,997 You're sort of judge, jury, and execution are all wrapped up into 96 00:06:03,997 --> 00:06:06,767 one, so to speak, and that you've got to interface with the business. 97 00:06:06,767 --> 00:06:07,927 You've got to define your requirement. 98 00:06:07,927 --> 00:06:10,933 You, don't have often that separate product management layer. 99 00:06:11,223 --> 00:06:11,883 Was that. 100 00:06:12,748 --> 00:06:13,988 Disruptive for you at all? 101 00:06:13,988 --> 00:06:18,778 Or did you feel a gap not having those functions surrounding him? 102 00:06:19,295 --> 00:06:20,145 Rich Archbold: Yes and no. 103 00:06:20,155 --> 00:06:22,165 You're right that it's totally different. 104 00:06:22,245 --> 00:06:27,995 And even if you do have PMs, while those PMs share some common skill 105 00:06:27,995 --> 00:06:31,575 sets, how they approach their job has to be very different. 106 00:06:31,605 --> 00:06:38,820 That if you're a PM, um, In core products in HubSpot, you are building a product 107 00:06:38,850 --> 00:06:45,700 that is a good product market fit for millions of SMBs, and if your product 108 00:06:45,730 --> 00:06:51,190 doesn't match 100 percent of the needs of the customer, they still have the freedom 109 00:06:51,230 --> 00:06:56,170 to leverage their own engineering team to buy or integrate a different solution. 110 00:06:56,640 --> 00:07:01,388 You don't have to do the last mile Customer installation or professional 111 00:07:01,388 --> 00:07:03,068 services or customer support. 112 00:07:03,068 --> 00:07:04,918 You've dedicated teams for those. 113 00:07:05,508 --> 00:07:11,508 So it's really a, very specialized, very long term, strategic thinking position, 114 00:07:12,108 --> 00:07:18,068 but when you operate as a PM of a business systems team, you have one customer, 115 00:07:18,078 --> 00:07:21,957 usually an enterprise customer rather than an SMB customer who you have to 116 00:07:21,957 --> 00:07:25,648 build 100 percent product market fit for. 117 00:07:26,106 --> 00:07:29,326 You need to do all of the professional services, all of the customer support. 118 00:07:29,736 --> 00:07:32,096 You need to do absolutely everything yourself. 119 00:07:33,146 --> 00:07:36,396 You find it very hard to say no, because that customer you have a 120 00:07:36,396 --> 00:07:40,486 real personal relationship with and that customer generally. 121 00:07:40,931 --> 00:07:44,381 Doesn't have the luxury or you actually really don't want them to have the 122 00:07:44,381 --> 00:07:47,231 luxury of going out and hiring some other consultant or hiring some 123 00:07:47,231 --> 00:07:52,221 other people because that leads to fragmentation, collaboration tax, 124 00:07:52,507 --> 00:07:53,917 that's kind of how, you know, you're failing. 125 00:07:54,257 --> 00:07:57,077 It's not whether your customer is like telling you, you're doing a great job. 126 00:07:57,077 --> 00:08:00,397 It's whether they've gone off and spun up a shadow it, function or. 127 00:08:00,917 --> 00:08:01,007 or. 128 00:08:01,007 --> 00:08:05,137 not, so I think the 2 roles are, I mean, obviously, there's a lot of 129 00:08:05,727 --> 00:08:11,587 commonalities, where, you aren't doing a Coupa implementation project. 130 00:08:11,677 --> 00:08:16,037 What you're actually doing is a procure to pay efficiency project. 131 00:08:16,387 --> 00:08:18,957 And so you need to make sure that you understand who is the customer? 132 00:08:18,957 --> 00:08:20,017 what is the business problem? 133 00:08:20,017 --> 00:08:21,267 What is the ROI? 134 00:08:21,771 --> 00:08:23,451 and don't get over focused on. 135 00:08:24,166 --> 00:08:26,796 Implementing any 1 particular technology or other. 136 00:08:26,806 --> 00:08:29,935 So I think that's where those are some of the, I mean, you need to be really 137 00:08:29,935 --> 00:08:33,875 great at communication and have great empathy and great, problem solving skills. 138 00:08:34,284 --> 00:08:38,365 But, yeah, I think the 2 roles are quite different in the go to market space. 139 00:08:38,395 --> 00:08:42,693 I think, that's really what we look to have our best BSAs, step in and 140 00:08:42,693 --> 00:08:48,744 kind of perform that role where the best BSAs are, part project manager, 141 00:08:49,114 --> 00:08:53,764 part systems administrator, part systems integrator, part customer 142 00:08:53,764 --> 00:08:55,914 support, part solutions engineer. 143 00:08:56,364 --> 00:09:02,820 And, BSAs I've worked with, they really, Look and feel like, a very 144 00:09:02,860 --> 00:09:04,838 operationally focused, product 145 00:09:05,188 --> 00:09:07,358 Justin Norris: And just in case that acronym isn't transparent for anyone, 146 00:09:07,358 --> 00:09:09,778 BSA equals business systems analyst. 147 00:09:10,083 --> 00:09:11,813 Rich Archbold: Yeah, business systems analysts. 148 00:09:12,053 --> 00:09:18,161 Like, I've seen multiple archetypes where some business systems analysts will lean 149 00:09:18,161 --> 00:09:23,007 more on the, product owner or Product manager, almost like a program manager 150 00:09:23,007 --> 00:09:30,317 archetype, and some will lean more towards the systems engineer, solution engineer, 151 00:09:30,347 --> 00:09:35,817 integrations engineer, where they're really adept at being able to configure or 152 00:09:35,817 --> 00:09:41,607 maximize a particular service or leverage, integration technology, like Workado. 153 00:09:42,027 --> 00:09:43,679 So they're almost more like solutions. 154 00:09:43,679 --> 00:09:47,989 engineers, and I think it can be very difficult when you're in a very 155 00:09:47,989 --> 00:09:50,799 small environment, you want your to be able to do all of those things. 156 00:09:50,889 --> 00:09:55,359 But the bigger you get, it can be sometimes difficult to have, like, you 157 00:09:55,359 --> 00:09:59,549 want to have some amount of Swiss army knife, business systems analysts that 158 00:09:59,575 --> 00:10:01,395 can really jump in and do anything. 159 00:10:01,725 --> 00:10:04,045 But I think once you reach a certain point, that's where you need to 160 00:10:04,055 --> 00:10:07,605 think about, do I actually need, A Swiss army knife, business systems 161 00:10:07,605 --> 00:10:12,412 analyst, or do I need a dedicated internal go to market product manager. 162 00:10:12,412 --> 00:10:18,392 And I think at HubSpot today, we're, I'd say we're almost like 90, 10 or 80, 20 163 00:10:18,392 --> 00:10:24,482 in favor of each of our individual teams are generally led by a product manager. 164 00:10:25,062 --> 00:10:29,122 And we do have some amounts of amazingly fungible, business systems 165 00:10:29,122 --> 00:10:31,312 analysts who are really are the. 166 00:10:31,600 --> 00:10:37,530 glue in a lot of different projects where they're able to participate in many 167 00:10:37,530 --> 00:10:41,620 different ways at many different levels, depending on the project that is at hand. 168 00:10:42,386 --> 00:10:44,946 Justin Norris: so maybe digging a little bit deeper than into 169 00:10:44,956 --> 00:10:49,636 your team and its structure, where does it sit within HubSpot? 170 00:10:49,636 --> 00:10:51,665 Is it rolling up into like an it function? 171 00:10:51,665 --> 00:10:54,636 Is it connected to different functional areas that you support? 172 00:10:54,646 --> 00:10:55,976 How does that structure work? 173 00:10:56,683 --> 00:11:01,434 Rich Archbold: So, today we roll up through the, Product organization, 174 00:11:01,434 --> 00:11:03,634 so the R and D arm as such. 175 00:11:04,124 --> 00:11:09,994 So I have a product partner who rolls up through our head of product and 176 00:11:10,194 --> 00:11:13,284 I myself roll up through our CTO. 177 00:11:13,784 --> 00:11:19,329 But for me, I always think I have many bosses that I, like, I feel equally 178 00:11:19,329 --> 00:11:25,599 accountable to our head of sales, head of marketing, head of support, our CFO. 179 00:11:26,919 --> 00:11:36,069 And, while the CTO is my manager, it's great that, like, I certainly report to 180 00:11:36,069 --> 00:11:39,419 him from an engineering quality and from an engineering execution perspective, 181 00:11:39,749 --> 00:11:45,649 but I need to make sure this is such a highly cross functional space with, so 182 00:11:45,649 --> 00:11:49,429 many different, uh, leaders involved that you really have to consider yourself. 183 00:11:49,944 --> 00:11:54,846 You are accountable to the, companies go to market leadership team. 184 00:11:55,586 --> 00:11:58,012 Justin Norris: And when you say you have a product, partner, 185 00:11:58,402 --> 00:11:59,812 tell us about that relationship. 186 00:11:59,822 --> 00:12:00,602 Like, how does that work? 187 00:12:02,092 --> 00:12:05,442 Rich Archbold: Yeah, so I have a product partner, Kitty Chu, who is 188 00:12:05,472 --> 00:12:11,155 based in Seattle and Kitty and I, so our mission is to help bring HubSpot's 189 00:12:11,265 --> 00:12:12,765 go to market strategy to life. 190 00:12:13,415 --> 00:12:18,516 And so the, 2 of us will partner with each of the various 191 00:12:18,516 --> 00:12:20,592 different go to market leaders to. 192 00:12:20,863 --> 00:12:24,963 Understand what the company's go to market strategy is, how it's going to be evolving 193 00:12:25,023 --> 00:12:28,063 each year and then use that to break down. 194 00:12:28,102 --> 00:12:30,502 what are the big rock projects? 195 00:12:30,502 --> 00:12:34,172 We need to get our teams to execute in each of the 196 00:12:34,172 --> 00:12:35,302 different parts of the business. 197 00:12:35,682 --> 00:12:38,452 As I said, each of the teams generally have, uh. 198 00:12:39,077 --> 00:12:45,567 Product manager, uh, designer and an engineer and all of the product people 199 00:12:45,607 --> 00:12:49,917 roll up through my product partner and all of the engineering people roll up through 200 00:12:49,918 --> 00:12:50,167 me. 201 00:12:50,447 --> 00:12:50,807 Justin Norris: Got it. 202 00:12:50,807 --> 00:12:55,087 So it really is structured in a lot of ways, like an externally facing 203 00:12:55,187 --> 00:12:57,367 product team would be with engineering 204 00:12:57,407 --> 00:12:57,787 product 205 00:12:57,977 --> 00:12:58,797 Rich Archbold: very much so. 206 00:12:58,797 --> 00:13:04,787 And we share a lot of the same core values around solving for the customer 207 00:13:04,787 --> 00:13:09,685 and making sure that we're, thinking long term and that we're building really 208 00:13:09,685 --> 00:13:15,795 high quality into the product services, workflows and data that we generate. 209 00:13:16,215 --> 00:13:19,425 Justin Norris: So kind of traveling down the tree, if you like, of, 210 00:13:19,447 --> 00:13:22,787 your org structure, beneath you and kitty, how do you structure 211 00:13:22,797 --> 00:13:24,517 those different groups or pods? 212 00:13:24,517 --> 00:13:28,027 Are they around systems or are they around the go to market teams or 213 00:13:28,237 --> 00:13:29,367 what does that structure look like? 214 00:13:30,202 --> 00:13:33,637 Rich Archbold: we try and set up our teams to, try and generate 215 00:13:33,697 --> 00:13:38,207 relatively clean relationships with each of our key stakeholders. 216 00:13:38,217 --> 00:13:41,707 So there's a marketing focused team or a marketing focused group. 217 00:13:41,737 --> 00:13:43,307 There's a sales focused group. 218 00:13:43,687 --> 00:13:46,287 There is a customer support and success focused group. 219 00:13:46,687 --> 00:13:48,467 There's a partner focused group. 220 00:13:48,877 --> 00:13:53,472 And then we have a shared kind of CRM, data, focused, function. 221 00:13:53,882 --> 00:13:54,422 As well. 222 00:13:54,422 --> 00:13:57,662 And then as I said, we have our FinTech, function, which is kind of 223 00:13:57,662 --> 00:14:03,193 like our own homegrown, uh, pricing and packaging, CPQ billing invoicing and, 224 00:14:03,224 --> 00:14:06,377 some of our finance systems, functions. 225 00:14:06,382 --> 00:14:10,662 And all of those individual groups or teams at various different layers would 226 00:14:10,667 --> 00:14:16,687 have a product management leader, uh, design leader, and an engineering leader. 227 00:14:17,552 --> 00:14:20,892 And we have this concept of what we call interlock. 228 00:14:20,902 --> 00:14:25,585 So this would be, a set of regularly occurring meetings where you'd 229 00:14:25,605 --> 00:14:29,495 have members from, like, the go to market systems function and their 230 00:14:29,505 --> 00:14:35,881 relevant counterparts in, rev ops or, the various different in field 231 00:14:35,901 --> 00:14:39,581 leadership functions, like a sales leader or a marketing leader or, uh. 232 00:14:39,978 --> 00:14:44,973 support leader, and we, kind of realized that this is like a fast moving space. 233 00:14:45,033 --> 00:14:46,993 It's very cross functional. 234 00:14:47,367 --> 00:14:51,527 we have a concept of hashtag 1 team that even though we all roll up to 235 00:14:51,527 --> 00:14:55,587 different leaders, you have to think of yourself as like 1 cross functional team. 236 00:14:55,632 --> 00:14:59,272 It's up to you all to make the decisions and make sure 237 00:14:59,272 --> 00:15:01,262 that there's minimal friction. 238 00:15:02,022 --> 00:15:07,872 Between Rev Ops and engineering or Rev Ops and product or sales and Rev Ops, we 239 00:15:07,872 --> 00:15:13,321 try and think of ourselves as just one, cross functional team, working together 240 00:15:13,321 --> 00:15:16,331 to help bring our go to market strategy to 241 00:15:16,331 --> 00:15:16,641 Justin Norris: life. 242 00:15:16,916 --> 00:15:21,946 And in a smaller organization, a lot of the systems ownership, you know, usually 243 00:15:21,956 --> 00:15:26,176 lives within RebOps or marketing ops, you know, this functional ops teams. 244 00:15:26,176 --> 00:15:30,961 Um, How do you think about the roles and responsibilities with your 245 00:15:30,961 --> 00:15:32,761 group and then the rev ops function? 246 00:15:32,771 --> 00:15:33,941 Like what do they do? 247 00:15:34,131 --> 00:15:35,521 They're a stakeholder of yours. 248 00:15:35,521 --> 00:15:36,661 I am assuming. 249 00:15:37,011 --> 00:15:39,306 but how do those lines of responsibility flow, 250 00:15:40,033 --> 00:15:41,113 Rich Archbold: that's a great question. 251 00:15:41,873 --> 00:15:49,369 And what I think of the Product teams that roll up through me as much as possible. 252 00:15:49,379 --> 00:15:53,929 We're trying to build systems and build functions that allow RevOps 253 00:15:54,049 --> 00:15:58,419 to have the right level of agency and control and configuration. 254 00:15:59,319 --> 00:16:02,539 We actually want them to be able to move fast and experiment. 255 00:16:03,149 --> 00:16:08,809 And so I think about it as like trying to keep the cycle times. 256 00:16:09,544 --> 00:16:12,154 Low and keep the agility high. 257 00:16:12,304 --> 00:16:18,774 So in each of our rev ops teams, we do have some that have hands on ability 258 00:16:18,774 --> 00:16:25,185 to make changes or have some work out our skill sets to, do some last mile 259 00:16:25,185 --> 00:16:32,134 Automation and, customization, know, I've been, I've seen organizations 260 00:16:32,144 --> 00:16:37,569 in the past where, people try and put every single thing inside of 261 00:16:37,589 --> 00:16:41,409 that single business systems function or single sales systems function. 262 00:16:42,139 --> 00:16:46,457 And I think, I've seen the cycle times be too high, around that. 263 00:16:46,867 --> 00:16:51,847 And I think you really need to strive to give the business the right level 264 00:16:51,847 --> 00:16:55,177 of agility and control over the things that are happening day to day. 265 00:16:55,597 --> 00:16:57,147 And if there's a small change that. 266 00:16:57,537 --> 00:17:01,512 Can be made, you want it made as close as possible to the person requesting it. 267 00:17:01,582 --> 00:17:05,808 And I think that's why we have powerful, easy to use platforms 268 00:17:05,988 --> 00:17:08,078 like CRM platforms, right? 269 00:17:08,098 --> 00:17:10,377 Like that, I, I think that is some of the value of it. 270 00:17:10,478 --> 00:17:13,409 So I definitely do like the. 271 00:17:13,904 --> 00:17:19,182 Centralized teams to a certain extent, because I think that removes some 272 00:17:19,182 --> 00:17:25,468 siloing and allows you to make bigger, bolder decisions more, quickly. 273 00:17:25,508 --> 00:17:30,928 It allows you to stay focused on customer problems rather than parts of a process. 274 00:17:31,431 --> 00:17:34,721 But I also think it's just really important that the business feels like 275 00:17:34,769 --> 00:17:39,629 they are beholden to you for every single change they want to make, that 276 00:17:40,049 --> 00:17:41,499 they will have the right context. 277 00:17:42,219 --> 00:17:45,829 you just want to be able to have the shortest possible cycle times 278 00:17:45,849 --> 00:17:49,451 for, the categories of change that, that actually makes sense 279 00:17:49,451 --> 00:17:49,731 for. 280 00:17:49,971 --> 00:17:53,581 Justin Norris: what you just mentioned to me addresses what I've observed. 281 00:17:53,581 --> 00:17:57,231 And also what I think is generally perceived as the major risk and 282 00:17:57,231 --> 00:18:00,561 shortcoming of the centralized team is that you essentially recreate 283 00:18:00,561 --> 00:18:02,311 the it dynamic where it's like. 284 00:18:03,031 --> 00:18:06,731 A big queue of tickets, it's sort of this fortress mentality. 285 00:18:06,731 --> 00:18:10,991 They're pushing away work We'll see you in three months and of course that's what 286 00:18:10,991 --> 00:18:14,591 leads to the the shadow it cropping up again or the consultants or we just have 287 00:18:14,591 --> 00:18:20,181 to do it on the side i've also seen to your point that you know inevitably folks 288 00:18:20,181 --> 00:18:25,371 that are coming up through operations that don't necessarily have like Maybe 289 00:18:25,371 --> 00:18:28,701 they develop systems expertise, but it isn't necessarily their background 290 00:18:28,701 --> 00:18:33,346 You Eventually when you're thinking about an enterprise architecture vision 291 00:18:33,875 --> 00:18:38,715 you go beyond what those folks are able to accomplish at least without 292 00:18:38,865 --> 00:18:42,365 Further upskilling and you really do get into a much more technical domain 293 00:18:42,755 --> 00:18:47,408 So it seems like you have this sweet spot dynamic setup do you feel that? 294 00:18:47,898 --> 00:18:51,777 This is just inevitable that, you know, once you pass, I don't know what it is, 5, 295 00:18:51,778 --> 00:18:57,608 000 employees for, I don't know, whatever the number is that you have to kind 296 00:18:57,608 --> 00:19:01,838 of have a centralized business systems function, or do you think that you can 297 00:19:01,838 --> 00:19:07,345 just have functional ownership of tools, you know, within ops teams in perpetuity, 298 00:19:07,345 --> 00:19:11,271 Rich Archbold: You know, the answer is, I think it depends, if you have a, a 299 00:19:11,271 --> 00:19:16,741 relatively simple and stable, business model, and you're not making a lot of 300 00:19:16,741 --> 00:19:21,601 changes to your go to market strategy, I think you can keep things simple and keep 301 00:19:21,601 --> 00:19:23,541 functional ownership, as long as you can. 302 00:19:23,921 --> 00:19:29,406 But I do think there's certainly a level of change that happens, a tipping 303 00:19:29,406 --> 00:19:35,306 point of complexity or tipping point of change where you actually can't make 304 00:19:35,306 --> 00:19:39,556 changes in isolation, where if we're going to start selling a new product, 305 00:19:39,816 --> 00:19:42,676 we need a new skew in salesforce. 306 00:19:43,026 --> 00:19:44,126 We need to be able to meet her. 307 00:19:44,126 --> 00:19:46,936 It's usage in a new, different way. 308 00:19:46,946 --> 00:19:50,056 In our billing system, we need to be able to account for revenue and in. 309 00:19:50,056 --> 00:19:52,196 In a different way inside of our Rev Rec system. 310 00:19:52,216 --> 00:19:55,656 It's going to mean different product usage data flowing into 311 00:19:55,656 --> 00:19:57,096 our customer success platform. 312 00:19:57,116 --> 00:20:02,782 I'm going to mean that we try and drive cross sell upsell renewal a different way. 313 00:20:03,162 --> 00:20:07,516 I think it's really hard to implement those type of transformational projects 314 00:20:07,516 --> 00:20:13,039 or really big step function projects without some sort of, central governance 315 00:20:13,069 --> 00:20:16,469 or, architecture and, management. 316 00:20:16,469 --> 00:20:21,319 So I think, yeah, you just kind of reach a tipping point of complexity where it makes 317 00:20:21,329 --> 00:20:24,919 sense to have a more centralized function. 318 00:20:24,929 --> 00:20:28,371 But, That doesn't mean that every time you want to add a new field inside of the 319 00:20:28,371 --> 00:20:32,831 CRM, it needs to go to that centralized team either, though, you know, I think 320 00:20:32,861 --> 00:20:36,541 that that's where I mean, there's some some types of changes where you really 321 00:20:36,541 --> 00:20:40,431 want to make sure the teams closest to the problem have the right level 322 00:20:40,431 --> 00:20:42,719 of agency and autonomy over solving 323 00:20:42,719 --> 00:20:42,874 them. 324 00:20:43,322 --> 00:20:45,822 Justin Norris: a bit of a, like a hub and spoke model, if you 325 00:20:45,822 --> 00:20:46,722 want to think about it that 326 00:20:46,917 --> 00:20:47,577 Rich Archbold: exactly. 327 00:20:47,947 --> 00:20:50,617 Justin Norris: Yeah, no, that makes makes perfect sense. 328 00:20:51,217 --> 00:20:54,047 Let's talk a little bit about your stack, which is kind of 329 00:20:54,047 --> 00:20:55,177 a fun thing to think about. 330 00:20:55,257 --> 00:20:56,967 I presume HubSpot's in there somewhere. 331 00:20:56,967 --> 00:20:58,619 what else are you folks using? 332 00:20:59,279 --> 00:21:02,429 Rich Archbold: definitely HubSpot is pretty much the center of everything and 333 00:21:02,429 --> 00:21:09,375 we're a massive, marketing hub, sales hub, service hub, and, HubSpot CRM platform. 334 00:21:09,935 --> 00:21:16,755 we use a lot of our own CRM UI extension capabilities in order to build the spoke 335 00:21:16,825 --> 00:21:23,295 and tailored experiences inside of HubSpot and customize the views we provide to, 336 00:21:23,895 --> 00:21:28,765 each of our different reps and our PMs and designers spend a lot of time talking 337 00:21:28,765 --> 00:21:32,525 to our internal stakeholders to make sure we're tailoring those correctly. 338 00:21:33,095 --> 00:21:33,895 one of the. 339 00:21:34,125 --> 00:21:37,396 More interesting ones that we've launched recently was using our 340 00:21:37,396 --> 00:21:42,376 own prospecting workspace to help organize the, prospecting layout and, 341 00:21:42,376 --> 00:21:47,857 uh, and tool tips that We provide to our reps and adoption for that. 342 00:21:47,887 --> 00:21:53,916 And engagement with that has been, very high from A CPQ. 343 00:21:54,051 --> 00:21:57,847 And, and, billing and invoicing perspective, a lot of that 344 00:21:57,852 --> 00:21:59,257 is custom to ourselves. 345 00:21:59,257 --> 00:22:04,797 And we have, uh, quite an artisanal set of, processes and capabilities. 346 00:22:04,797 --> 00:22:07,547 And that's something that our, FinTech organization 347 00:22:07,547 --> 00:22:09,547 takes care of on the back end. 348 00:22:09,557 --> 00:22:14,487 We use NetSuite, from a, call recording and coaching perspective. 349 00:22:14,487 --> 00:22:18,007 We use Gong and are, and we are big fans of Gong. 350 00:22:18,017 --> 00:22:19,547 We think that's a great product as well. 351 00:22:20,124 --> 00:22:20,664 from a. 352 00:22:21,147 --> 00:22:22,057 Data engineering. 353 00:22:22,057 --> 00:22:26,367 So from an analytical data perspective, all of our data flows into snowflake. 354 00:22:26,417 --> 00:22:32,883 We're, big fans of dbt and, looker and airflow from, uh, an automation 355 00:22:32,893 --> 00:22:36,280 and, data plumbing perspective, Yeah, curious, what else, are you 356 00:22:36,290 --> 00:22:38,630 you mentioned WorkAuto a few times as well. 357 00:22:38,670 --> 00:22:42,660 Yeah, so Workado, we're, we're massive, massive fans of Workado. 358 00:22:43,340 --> 00:22:47,505 And, use, that as our last mile automation. 359 00:22:47,505 --> 00:22:50,290 And, in some cases, integration technology. 360 00:22:50,290 --> 00:22:54,651 And, you know, our teams have built some really novel, Automation on top of that. 361 00:22:54,961 --> 00:23:00,539 And I've used it to, create some hooks into chat GPT and, yeah, just some really 362 00:23:00,539 --> 00:23:02,039 interesting use cases there as well. 363 00:23:02,579 --> 00:23:05,889 I come from, the Marketo space, you know, traditionally, although I've 364 00:23:05,889 --> 00:23:10,419 always been a HubSpot respecter, but the conventional wisdom, let's say 365 00:23:10,419 --> 00:23:13,479 on the street, at least in Marketo circles, it's sort of like HubSpot. 366 00:23:13,479 --> 00:23:14,129 Yeah, it's good. 367 00:23:14,139 --> 00:23:18,789 But you know, you might reach a point where you can't scale it and you're going 368 00:23:18,789 --> 00:23:23,219 to need to migrate to, and same thing, I guess, with the CRM to Salesforce. 369 00:23:23,219 --> 00:23:26,129 Here you are obviously a very large enterprise. 370 00:23:26,474 --> 00:23:30,394 Uh, using HubSpot for both CRM and marketing automation. 371 00:23:30,914 --> 00:23:31,684 how would you respond? 372 00:23:31,684 --> 00:23:34,554 Let's say if someone proposed that point of view to you, like, yeah, 373 00:23:34,734 --> 00:23:36,754 it won't necessarily scale with you. 374 00:23:36,764 --> 00:23:37,474 Like you've scaled it. 375 00:23:37,864 --> 00:23:38,814 what are your thoughts on them? 376 00:23:39,929 --> 00:23:40,879 I think that's wrong. 377 00:23:41,106 --> 00:23:47,076 so I've come from a world of, so at Intercom I use Salesforce and, Marketo, 378 00:23:47,636 --> 00:23:52,926 and I would say the bane of my life was dealing with, you know, Duplicate leads 379 00:23:52,956 --> 00:23:58,176 in, Marketo to, HubSpot, uh, syncs and bottlenecks and integration and having 380 00:23:58,176 --> 00:24:03,356 to deal with multi enrichment challenges between, Marketo and Salesforce and trying 381 00:24:03,356 --> 00:24:08,566 to implement ring lead as a solution to try and have, centralized enrichment 382 00:24:08,566 --> 00:24:10,516 and account management and survivorship. 383 00:24:10,566 --> 00:24:14,782 But, when, I left Intercom, I wanted to go to HubSpot because I felt like they 384 00:24:14,782 --> 00:24:19,962 had it all sorted out and I wanted to have one single stack that everything, 385 00:24:19,962 --> 00:24:23,392 was there and present with a single consistent data model that I could have 386 00:24:23,392 --> 00:24:25,862 marketing and sales, both used together. 387 00:24:26,312 --> 00:24:28,212 Didn't have to deal with any integration challenges. 388 00:24:28,282 --> 00:24:30,012 It was just all there natively. 389 00:24:30,432 --> 00:24:33,012 And now I'm living in the promised land, you know, it works. 390 00:24:33,412 --> 00:24:35,912 And so there's a whole degree of challenges that, 391 00:24:35,982 --> 00:24:37,142 I didn't have to deal with. 392 00:24:37,242 --> 00:24:40,902 that now I don't have to deal with because I have that seamless 393 00:24:40,912 --> 00:24:44,922 integration and the partnership between marketing and sales and the handle. 394 00:24:44,962 --> 00:24:48,272 I mean, you're working in the go to market world for a while and you go, what are 395 00:24:48,272 --> 00:24:49,672 some of your hard fought lessons learned? 396 00:24:50,262 --> 00:24:55,301 Handoffs between teams and tools is like where all of the friction is, going to 397 00:24:55,301 --> 00:24:58,651 happen is where a lot of the data quality issues, where a lot of the scalability 398 00:24:58,651 --> 00:24:59,791 bottlenecks are going to happen. 399 00:24:59,791 --> 00:25:03,761 It's going to make problems twice as hard. 400 00:25:04,381 --> 00:25:05,431 I don't have to deal with that. 401 00:25:05,651 --> 00:25:09,421 You know, I've got everybody in the one platform with a shared data model. 402 00:25:09,651 --> 00:25:10,981 They've got the same source of truth. 403 00:25:11,482 --> 00:25:12,612 That does, sound nice. 404 00:25:12,680 --> 00:25:17,850 let's think about, innovation on the platform in general. 405 00:25:17,850 --> 00:25:21,700 I assume you've had to push the boundaries in some cases to. 406 00:25:22,090 --> 00:25:24,495 You know, solve interesting challenges that you've had. 407 00:25:24,785 --> 00:25:28,285 What are just some cool things, I guess, that you're doing on your own platform 408 00:25:28,695 --> 00:25:29,885 that might be interesting to folks, 409 00:25:30,698 --> 00:25:34,835 as I said, probably the most fun for us at the moment is that prospecting 410 00:25:34,835 --> 00:25:40,621 workspace and feels like we have, you know, we're really able to, partner deeply 411 00:25:40,621 --> 00:25:44,772 with our reps and understand what is the absolute ideal workflow you want to have. 412 00:25:44,832 --> 00:25:48,042 Like we can do lots of rep shadowing and really build that empathy for our 413 00:25:48,042 --> 00:25:50,613 reps and go where do you wish you had? 414 00:25:50,632 --> 00:25:52,322 what's your ideal layout here? 415 00:25:52,512 --> 00:25:54,502 How would you like things to be prioritized? 416 00:25:54,665 --> 00:25:57,397 if you could wave a magic wand, how would this work for you? 417 00:25:58,027 --> 00:26:02,667 And the HubSpots, prospecting workspace layout, and then the CRM, 418 00:26:02,667 --> 00:26:07,398 UI capabilities give us the ability to really bring that to life. 419 00:26:07,869 --> 00:26:12,294 Pretty quickly and easily, which has been, just wonderful to see, I guess. 420 00:26:12,714 --> 00:26:16,294 I'm just trying to think of, like, some of the other things that we're that 421 00:26:16,604 --> 00:26:17,514 we're doing that 422 00:26:17,764 --> 00:26:20,884 maybe just on the, on the prospector workspace, because I'm super interested 423 00:26:20,884 --> 00:26:23,954 in that feature and I've, I've read a bit about it, but let me just tell you, 424 00:26:23,994 --> 00:26:25,694 give you my read on what I think it is. 425 00:26:25,694 --> 00:26:30,134 You can tell me if I'm right or not, but it kind of solves that perennial 426 00:26:30,134 --> 00:26:34,184 challenge of, you know, I've got one lead or contact or person record, whatever we 427 00:26:34,184 --> 00:26:36,174 call it within that system's nomenclature. 428 00:26:36,584 --> 00:26:41,334 but that person may go through a buying process or a funnel trip Multiple times, 429 00:26:41,374 --> 00:26:45,734 and it's very difficult to, report on that, to capture that because the data 430 00:26:45,734 --> 00:26:47,494 model is, kind of one dimensional. 431 00:26:47,854 --> 00:26:51,364 And so the prospecting workspace sort of introduces this idea of many, I 432 00:26:51,364 --> 00:26:54,284 don't know if you call them leads or what they're called exactly, but many 433 00:26:54,294 --> 00:26:57,914 different entities that can relate to that single person that represent 434 00:26:57,924 --> 00:26:59,914 those iterative buying journeys. 435 00:26:59,914 --> 00:27:00,794 is that what it is? 436 00:27:01,059 --> 00:27:04,031 the problem, that we use it to solve is 437 00:27:04,031 --> 00:27:04,761 slightly different. 438 00:27:05,071 --> 00:27:09,541 And the way I describe the problem is I'm a sales rep and I have 439 00:27:09,781 --> 00:27:12,751 hundreds of companies under my name. 440 00:27:13,321 --> 00:27:19,904 And, some of these companies are, already customers and I need to, Think 441 00:27:19,904 --> 00:27:23,814 about account management and account maintenance and cross sell upsell. 442 00:27:24,094 --> 00:27:28,984 Some of them are cold prospects, and some of them are warm prospects. 443 00:27:29,024 --> 00:27:32,424 And I've got hundreds of these inside of my capacity like that 444 00:27:32,424 --> 00:27:34,464 are assigned to me and every day. 445 00:27:34,464 --> 00:27:36,994 I need to come in and figure out what's the best way for 446 00:27:36,994 --> 00:27:38,134 me to spend my time today. 447 00:27:38,804 --> 00:27:40,364 there's undoubtedly been. 448 00:27:40,614 --> 00:27:42,504 Maybe a lot of signals that have happened. 449 00:27:42,514 --> 00:27:48,289 Maybe there's been new enrichment events, or, new activities on our marketing sites 450 00:27:48,289 --> 00:27:50,489 that might have contributed to events. 451 00:27:51,149 --> 00:27:55,629 Maybe the companies that are actually customers of mine, there's been 452 00:27:55,629 --> 00:28:01,719 some new usage data that has flowed into the system and I'm a rep with. 453 00:28:02,629 --> 00:28:04,379 to meet what should I do today? 454 00:28:05,129 --> 00:28:11,079 And so what we use our prospecting workspace is a way to, break up the 455 00:28:11,099 --> 00:28:16,449 companies segment, the companies that reps own into kind of like cold, warm, 456 00:28:16,789 --> 00:28:21,038 maybe hot, existing customers then we can use various different types of, 457 00:28:21,548 --> 00:28:23,218 machine learning models in the background. 458 00:28:23,518 --> 00:28:30,258 To help prioritize the activities for the rep and make it transparent to the rep why 459 00:28:30,308 --> 00:28:32,438 we have prioritized different things in. 460 00:28:33,253 --> 00:28:36,513 Different ways to just make it much easier for the rep when they come in 461 00:28:36,513 --> 00:28:41,107 in the morning, not to be hit with, just a search list of here are hundreds 462 00:28:41,147 --> 00:28:45,387 of companies that you are responsible for looking after and for them having 463 00:28:45,387 --> 00:28:49,207 to think about lots of searching and filtering to actually come in with a 464 00:28:49,207 --> 00:28:55,818 beautiful, tailored, high quality, UI that, fits natively inside of HubSpot, 465 00:28:56,118 --> 00:28:59,598 where there has been a lot of, you know, thoughtful engineering in the background 466 00:28:59,648 --> 00:29:02,528 to make sure that we're showing them the. 467 00:29:03,068 --> 00:29:07,568 Most actionable things for them to do and making it easy for them to 468 00:29:07,568 --> 00:29:08,378 understand why 469 00:29:08,881 --> 00:29:09,191 Justin Norris: Got it. 470 00:29:09,191 --> 00:29:13,561 So it's more about prioritization, sort of task management or activity 471 00:29:13,561 --> 00:29:15,891 management and, uh, and directing them. 472 00:29:16,191 --> 00:29:20,571 And you've alluded a few times to the UI customization capabilities, and I'll 473 00:29:20,571 --> 00:29:24,981 confess, I'm, I'm a little bit ignorant, actually, of HubSpot's capabilities in 474 00:29:24,981 --> 00:29:26,311 this area are actually a lot ignorant. 475 00:29:26,671 --> 00:29:28,326 what can you tell me? 476 00:29:28,326 --> 00:29:32,001 Is it akin to like a Salesforce lightning page layout or like a 477 00:29:32,136 --> 00:29:32,666 Rich Archbold: very much. 478 00:29:32,706 --> 00:29:34,276 So yeah, very much. 479 00:29:34,276 --> 00:29:38,576 So, so like a lot of the flexibility and customization you have with that, 480 00:29:38,626 --> 00:29:44,643 there's lots of kind of like low code ways that you can customize it, 481 00:29:44,653 --> 00:29:49,853 but we can go as far as embedding an iframe directly inside of a particular 482 00:29:49,853 --> 00:29:51,793 portion of one of those windows. 483 00:29:51,843 --> 00:29:52,463 And that can. 484 00:29:52,943 --> 00:29:58,834 Be backed by some of our own, fully bespoke and custom built, web applications 485 00:29:58,834 --> 00:30:02,831 that our own quoting experience being one of those examples of where we 486 00:30:02,831 --> 00:30:07,476 can embed, uh, our own custom CPQ application directly inside of the 487 00:30:07,476 --> 00:30:07,986 HubSpot 488 00:30:07,986 --> 00:30:08,196 app. 489 00:30:08,583 --> 00:30:14,558 one of the The great things about this and one of our, I guess, 490 00:30:14,578 --> 00:30:19,892 overriding philosophies is that we ask our reps every quarter. 491 00:30:20,342 --> 00:30:22,592 How do you feel about the amount of tools you have to use? 492 00:30:23,093 --> 00:30:26,053 you want to keep reps on the same pane of glass inside of the 493 00:30:26,063 --> 00:30:27,603 same app as much as possible. 494 00:30:27,603 --> 00:30:31,244 You want to have, Unified data models inside of your CRM. 495 00:30:31,274 --> 00:30:34,934 So this is one of those things that we consistently look at is 496 00:30:35,194 --> 00:30:37,904 how many different applications are we asking our reps to work in? 497 00:30:38,214 --> 00:30:39,324 How can we cut that down? 498 00:30:39,324 --> 00:30:42,654 Is there something else that we can move natively inside of the HubSpot 499 00:30:42,654 --> 00:30:47,219 app and that we can have the data, uh, authoritatively stored for 500 00:30:47,299 --> 00:30:48,919 directly inside of HubSpot as well? 501 00:30:49,389 --> 00:30:51,899 because if it is a rep productivity is improved. 502 00:30:51,943 --> 00:30:57,013 The amount of context switching they do is minimized, but also having that 503 00:30:57,023 --> 00:31:03,562 data, source of truth inside of the CRM in a nested custom object format 504 00:31:03,970 --> 00:31:09,464 allows all of our work out of folks to generate additional, last mile. 505 00:31:09,570 --> 00:31:15,651 Automation and, customization in, um, kind of safe and scalable way then as well. 506 00:31:16,328 --> 00:31:18,028 Justin Norris: Let's dive into that one a little bit. 507 00:31:18,158 --> 00:31:20,008 I'm also a big fan of work. 508 00:31:20,008 --> 00:31:23,719 Um, how do you think about it from a roles and responsibilities 509 00:31:23,749 --> 00:31:25,069 point of view within the stack? 510 00:31:25,069 --> 00:31:29,649 Like when might you use HubSpot's internal automation capabilities, if at all, versus 511 00:31:29,919 --> 00:31:33,129 saying this is where we need to layer in a work order recipe to achieve a goal. 512 00:31:33,905 --> 00:31:38,225 Rich Archbold: so I think that work was a great tool for ops teams. 513 00:31:38,580 --> 00:31:44,445 To use to automate their workflows, I think when you're doing anything 514 00:31:44,455 --> 00:31:48,351 that HubSpot customer scale, that's actually going to scale with the 515 00:31:48,351 --> 00:31:50,451 amount of customers that we have. 516 00:31:50,491 --> 00:31:55,941 It's kind of hard to use, uh, work just from a cost perspective. 517 00:31:55,941 --> 00:31:57,951 If you're doing something that's going to be running, you know, 518 00:31:58,111 --> 00:32:01,531 hundreds of thousands times a day, growing at scale with our customers. 519 00:32:01,531 --> 00:32:06,682 And those are the things that, Generally, we would use more scalable software for. 520 00:32:07,282 --> 00:32:09,532 I also think you get beyond the level of complexity. 521 00:32:09,532 --> 00:32:14,732 Like, Ricardo is great for automating things, but it's really hard to do. 522 00:32:15,402 --> 00:32:19,942 Unit testing or integration testing, there's kind of like a size of complexity 523 00:32:19,942 --> 00:32:24,122 that once you actually go beyond it, maybe you want to use some more traditional 524 00:32:24,122 --> 00:32:29,117 software engineering processes and best practices for, but I think it's 525 00:32:29,117 --> 00:32:32,632 a great tool for ops teams to use to. 526 00:32:33,005 --> 00:32:36,665 Automate their processes and yeah, if you're operating at a 527 00:32:36,665 --> 00:32:38,695 smaller scale, I think it's fine. 528 00:32:38,795 --> 00:32:40,425 I think it's a great integration tool. 529 00:32:40,932 --> 00:32:42,512 I generally do believe in that. 530 00:32:42,574 --> 00:32:47,579 citizen automator model Work auto use, but I just think there's a point of scale 531 00:32:47,579 --> 00:32:51,999 and complexity where it makes sense, both from a financial perspective and also from 532 00:32:51,999 --> 00:32:57,579 a scalability and operational excellence perspective That you will want to convert 533 00:32:57,579 --> 00:33:02,849 it into software, but we would often start with, hey, we have this idea for something 534 00:33:02,859 --> 00:33:05,119 that we think might be valuable to reps. 535 00:33:05,799 --> 00:33:11,419 Let's build it as a prototype in workado and roll it out to a subset of our reps. 536 00:33:11,899 --> 00:33:14,609 And if it proves valuable, then we can. 537 00:33:14,809 --> 00:33:18,219 think about scaling it up and turning it into a fully fledged software solution. 538 00:33:18,259 --> 00:33:21,729 So it ends up being like a really valuable prototyping and fast 539 00:33:21,729 --> 00:33:23,129 paced prototyping tool for us 540 00:33:23,647 --> 00:33:25,967 Justin Norris: I had a fascinating conversation with a fellow 541 00:33:25,967 --> 00:33:27,647 named Niles Fote, from Trey. 542 00:33:27,992 --> 00:33:31,667 so we're Cotto's competitor, but, using Trey as part of their go to market. 543 00:33:32,127 --> 00:33:36,197 And he, uh, has developed a fairly sophisticated model where 544 00:33:36,197 --> 00:33:40,217 it kind of all their, lifecycle processing is happening in Trey. 545 00:33:40,267 --> 00:33:42,887 So they're doing like the event capture from the website. 546 00:33:43,642 --> 00:33:47,182 All of that sort of enrichment scoring MQL stuff. 547 00:33:47,642 --> 00:33:52,052 And just, I thought made a compelling case around why that was more scalable 548 00:33:52,062 --> 00:33:56,512 and, um, overcame some of the limitations that you get, like with, you know, 549 00:33:56,512 --> 00:33:59,762 in Marketo, you're capturing fields onto the person objects, so it can be 550 00:33:59,762 --> 00:34:03,082 really hard to manage race conditions because those events can get overwritten 551 00:34:03,082 --> 00:34:04,472 before other processing happens. 552 00:34:04,852 --> 00:34:06,912 There's like a limit, beyond which you can't go. 553 00:34:07,432 --> 00:34:09,212 What are your thoughts about that? 554 00:34:09,212 --> 00:34:11,502 Or maybe just tell us a bit more how you run that. 555 00:34:11,871 --> 00:34:14,922 call it operational backbone of your system. 556 00:34:14,922 --> 00:34:17,072 Are you doing that in HubSpot or have you written sort of 557 00:34:17,072 --> 00:34:18,552 your own software for that? 558 00:34:18,661 --> 00:34:19,242 How does it work? 559 00:34:20,542 --> 00:34:25,012 Rich Archbold: so we have a homegrown bespoke lead pipeline system, given 560 00:34:25,012 --> 00:34:28,222 the, given the scale that we're at. 561 00:34:28,422 --> 00:34:33,233 And so we have some custom software that allows us to capture All of 562 00:34:33,233 --> 00:34:39,382 those events and send them through a homegrown enrichment territory 563 00:34:39,382 --> 00:34:41,864 assignments, and, routing system. 564 00:34:41,925 --> 00:34:46,275 And so that really is all homegrown custom software for us. 565 00:34:46,275 --> 00:34:51,855 And we have various different levels of operational dashboards, and pay, like, 566 00:34:51,855 --> 00:34:54,324 a lot of attention to making sure that. 567 00:34:54,790 --> 00:34:58,850 A lead that enters the system actually gets routed to, a rep, 568 00:34:59,446 --> 00:35:03,186 and we pay a lot of attention to when it actually gets to the rep. 569 00:35:03,766 --> 00:35:09,716 Did the rep think it was a good lead or did they end up disqualifying it? 570 00:35:09,746 --> 00:35:11,111 Because some of the. 571 00:35:11,271 --> 00:35:15,921 Enrichment data didn't seem like it was right, or some of the segmentation 572 00:35:15,921 --> 00:35:20,949 data, or some of the territory data, or, that's some of the things that we 573 00:35:20,949 --> 00:35:24,865 thought made it actually a qualified lead actually weren't a qualified lead. 574 00:35:24,875 --> 00:35:27,245 And those are some of the metrics that I paid most attention 575 00:35:27,275 --> 00:35:28,955 to, to be honest with you. 576 00:35:28,993 --> 00:35:33,873 I looked to see, did the process from capturing the lead. 577 00:35:35,113 --> 00:35:37,763 To qualifying it and getting it in the hands of the rep. 578 00:35:37,913 --> 00:35:38,913 What did the rep think? 579 00:35:39,253 --> 00:35:40,673 Did the rep think it was good or bad? 580 00:35:40,763 --> 00:35:41,343 And why not? 581 00:35:41,774 --> 00:35:45,863 And like, are they policy issues or are they software issues? 582 00:35:46,823 --> 00:35:50,103 And for the ones that are software issues, do we make sure that we have 583 00:35:50,593 --> 00:35:55,603 the right teams thinking about, how to improve our enrichment systems or how 584 00:35:55,603 --> 00:36:00,153 to improve our segmentation systems or how to improve our assignment systems. 585 00:36:00,323 --> 00:36:03,953 And for ones that are policy issues, are we making sure that 586 00:36:04,013 --> 00:36:05,563 we're giving that feedback? 587 00:36:06,045 --> 00:36:11,745 And that the ops teams are getting all that feedback, do they feel like they have 588 00:36:11,745 --> 00:36:13,735 the right configuration tools out there? 589 00:36:14,367 --> 00:36:18,577 and do they feel they have the right agency to make changes to 590 00:36:18,697 --> 00:36:21,957 tweak things that they want, or are those features, We need to 591 00:36:21,957 --> 00:36:22,397 build, 592 00:36:22,977 --> 00:36:26,037 Justin Norris: that makes perfect sense and you've alluded to data a number of 593 00:36:26,037 --> 00:36:30,356 times that's also within your purview So maybe we'll turn to that This is a broad 594 00:36:30,356 --> 00:36:34,866 question, but how do you think about data strategy at the scale that you're at? 595 00:36:34,876 --> 00:36:38,976 Like, what are the sorts of first level concerns that you're dealing with 596 00:36:39,296 --> 00:36:40,656 when you think about HubSpot's data? 597 00:36:41,213 --> 00:36:41,333 Rich Archbold: I 598 00:36:41,363 --> 00:36:42,813 think it's the most important thing. 599 00:36:43,153 --> 00:36:47,445 and again, if you said to me, what are some of those hard fought lessons 600 00:36:47,455 --> 00:36:51,505 learned that you pick up as you go from working in infrastructure to 601 00:36:51,755 --> 00:36:54,652 working in, the go to market world. 602 00:36:55,332 --> 00:36:58,683 I think as a product person, as an engineer that builds a products 603 00:36:58,683 --> 00:37:03,143 for customers to buy, you generally take data quality for granted and 604 00:37:03,143 --> 00:37:04,563 you focus on building features. 605 00:37:05,218 --> 00:37:07,558 you have full control of all of the databases. 606 00:37:07,558 --> 00:37:09,498 You've got to pick the database technology. 607 00:37:09,927 --> 00:37:14,507 if it's my SQL, you can rely on nice, clean, simple, my SQL replication, 608 00:37:14,507 --> 00:37:17,867 or even if you need to stream it into some other sort of a search, elastic 609 00:37:17,867 --> 00:37:21,027 search database, there's like nice clean patterns for doing that, and 610 00:37:21,027 --> 00:37:22,297 you're all about building features. 611 00:37:23,097 --> 00:37:25,977 And then when you come into the go to market world, you realize it's the exact 612 00:37:25,977 --> 00:37:28,538 opposite You get to buy your features. 613 00:37:28,878 --> 00:37:30,078 HubSpot is going to give you features. 614 00:37:30,098 --> 00:37:31,618 Salesforce is going to give you features. 615 00:37:31,618 --> 00:37:32,958 Marketo is going to give you features. 616 00:37:33,358 --> 00:37:34,658 You need to build your data. 617 00:37:35,188 --> 00:37:40,718 you're actually, the more systems you have, you end up with a heterogeneous 618 00:37:41,088 --> 00:37:47,418 multi master database replication system with, no good consistency checking. 619 00:37:47,488 --> 00:37:52,038 And so you've multiple sources of truth, data replicating, left, right, and center. 620 00:37:52,656 --> 00:37:55,756 it's a native integration here, and then it's a workato integration 621 00:37:55,756 --> 00:38:00,116 over there, and they're all point in time integrations, and nobody's 622 00:38:00,116 --> 00:38:02,116 written a data checking thing. 623 00:38:02,639 --> 00:38:06,997 there's no, primary keys anywhere, there's duplicates all over 624 00:38:06,997 --> 00:38:08,137 the place, and you're going. 625 00:38:08,742 --> 00:38:12,583 Well, you have a new, B2B SaaS software rep going to sell you some 626 00:38:12,613 --> 00:38:16,473 new features to solve your problem, and so people will sell you features. 627 00:38:16,473 --> 00:38:17,583 You can buy your features. 628 00:38:17,963 --> 00:38:19,043 Features are not the problem. 629 00:38:19,393 --> 00:38:20,873 The problem is the data quality. 630 00:38:20,950 --> 00:38:24,190 and so that's where I spend, again, and. 631 00:38:24,555 --> 00:38:29,530 Inordinate amount of my time, thinking about, how do I make sure people 632 00:38:29,570 --> 00:38:34,650 understand the hierarchy of needs of data and that my company object is the single 633 00:38:34,650 --> 00:38:38,230 most important thing I need to have good governance and quality over followed 634 00:38:38,280 --> 00:38:43,480 closely by my contact object as my, as my 2nd, most important thing and then 635 00:38:43,500 --> 00:38:48,530 flowing down to deals or opportunities and then select contracts or. 636 00:38:48,530 --> 00:38:53,840 Subscriptions to invoices and understanding that hierarchy of of 637 00:38:53,840 --> 00:38:56,460 data and making sure that we have. 638 00:38:57,860 --> 00:39:02,992 Some sort of a governance process on each, like the, Schema management of 639 00:39:03,428 --> 00:39:09,528 each of those different core objects that we have some semblance of what does 640 00:39:09,878 --> 00:39:11,998 good mean for each of the attributes? 641 00:39:12,628 --> 00:39:14,078 Inside of these individual objects. 642 00:39:14,078 --> 00:39:18,482 So, like, how do we uniquely identify a company or an account? 643 00:39:18,922 --> 00:39:23,222 And do we have the right semantic and syntactic safeguards in place 644 00:39:23,402 --> 00:39:25,112 to make sure that that remains? 645 00:39:25,662 --> 00:39:26,822 A unique identifier. 646 00:39:27,553 --> 00:39:29,403 how do we think about company size? 647 00:39:29,763 --> 00:39:34,363 if we are enriching a company from 7 different sources, how 648 00:39:34,363 --> 00:39:37,303 do we think about survivorship rules around each of these things? 649 00:39:37,733 --> 00:39:40,153 How do we think about hiding the mess from reps? 650 00:39:40,833 --> 00:39:45,143 So that reps only see 1 value rather than the 7 values, but they have the right 651 00:39:45,143 --> 00:39:47,763 level of, lineage and discoverability. 652 00:39:47,793 --> 00:39:48,103 So. 653 00:39:48,403 --> 00:39:52,323 Even though we're only showing them one they know why it's only one. 654 00:39:52,863 --> 00:39:56,773 and so, yeah, I spend a massive amount of my time thinking about and evangelizing, 655 00:39:58,543 --> 00:40:02,573 operational data quality inside of our CRM and making sure that each of 656 00:40:02,573 --> 00:40:04,663 the different groups and teams are. 657 00:40:05,048 --> 00:40:09,006 Thinking about it, that we've got the right schema management strategy, 658 00:40:09,006 --> 00:40:11,506 that we've got the right data ingestion strategy, that we've got 659 00:40:11,506 --> 00:40:16,096 the right data, processing strategy, that we've got the right safeguards 660 00:40:16,096 --> 00:40:18,246 along the way, that all of this. 661 00:40:19,171 --> 00:40:23,401 It's so easy to get caught up in data quality for data quality's sake. 662 00:40:23,421 --> 00:40:25,177 And you're like, I do, data quality. 663 00:40:25,647 --> 00:40:29,617 No, you're here to help the company bring its go to market strategy to 664 00:40:29,617 --> 00:40:32,460 life, which means reps doing their jobs. 665 00:40:33,260 --> 00:40:34,330 That's what you're here to do. 666 00:40:34,930 --> 00:40:37,340 And one element of it is you need to keep the data, right. 667 00:40:37,630 --> 00:40:39,220 So that all of that can happen. 668 00:40:39,690 --> 00:40:42,270 And so you can get caught up in a world of like where. 669 00:40:43,025 --> 00:40:44,865 Data quality, I'm going to remove some duplicates. 670 00:40:45,175 --> 00:40:48,705 And you go, well, you could remove 75 percent of the duplicates, but it 671 00:40:48,705 --> 00:40:52,895 could have zero impact on a reps, work. 672 00:40:53,385 --> 00:40:56,115 And so you need to be talking to your reps and talking to your 673 00:40:56,125 --> 00:40:59,225 RevOps leaders and go, whereabouts are you feeling your pain points? 674 00:40:59,785 --> 00:41:05,485 And where do you think, Is your problem, generating net new business is your 675 00:41:05,625 --> 00:41:07,485 problem doing cross sell upsell? 676 00:41:07,485 --> 00:41:09,625 Is your problem doing forecast accuracy? 677 00:41:10,045 --> 00:41:12,805 is your problem, doing life cycle marketing because you don't 678 00:41:12,805 --> 00:41:14,065 have enough product usage data? 679 00:41:14,281 --> 00:41:15,081 where's your problems? 680 00:41:15,091 --> 00:41:16,401 I'm here to solve your problems. 681 00:41:16,841 --> 00:41:22,161 And odds are there's a CRM data quality challenge in there that 682 00:41:22,221 --> 00:41:23,391 we're going to need to figure out. 683 00:41:23,931 --> 00:41:25,811 But yeah, just making sure that. 684 00:41:26,145 --> 00:41:31,056 Whatever we do is in service of those, business problems and 685 00:41:31,326 --> 00:41:35,997 business opportunities rather than, polishing our data quality 686 00:41:36,377 --> 00:41:37,607 because you can spend forever. 687 00:41:37,747 --> 00:41:38,177 You can spend 688 00:41:38,227 --> 00:41:38,677 all of your 689 00:41:38,687 --> 00:41:39,137 time 690 00:41:39,462 --> 00:41:40,012 Justin Norris: And it's never 691 00:41:40,427 --> 00:41:40,947 Rich Archbold: CRM data 692 00:41:40,947 --> 00:41:41,997 quality and it's never done. 693 00:41:42,427 --> 00:41:43,147 and it's never right. 694 00:41:43,649 --> 00:41:47,252 but we're not here to generate good data quality we're here 695 00:41:47,252 --> 00:41:49,960 to, delight our customers and. 696 00:41:50,222 --> 00:41:54,112 generate leverage for the business and we focus on those two things 697 00:41:54,112 --> 00:41:56,632 first and data quality is a means to 698 00:41:56,632 --> 00:41:57,022 an end. 699 00:41:57,777 --> 00:42:00,717 Justin Norris: feel like we could do a whole show just on data because, 700 00:42:00,717 --> 00:42:03,817 yeah, there's so much in what you just described, both in terms of 701 00:42:03,857 --> 00:42:07,524 the current state of things and mess that we generally all inhabit. 702 00:42:08,207 --> 00:42:11,107 and accept as normal and the different things that you can do to 703 00:42:11,107 --> 00:42:13,187 try to mitigate that just for fun. 704 00:42:13,187 --> 00:42:16,767 I want to double click on maybe just one of them to see how you solve for it. 705 00:42:17,367 --> 00:42:20,937 Tactically you mentioned about like the data lineage and you might have, 706 00:42:20,957 --> 00:42:25,662 you know, seven different, data sources for a particular data point. 707 00:42:26,050 --> 00:42:29,784 you have some means of, Consolidating that, displaying only one to the 708 00:42:29,784 --> 00:42:32,674 rep, but in the background you can still track what you got and from 709 00:42:32,674 --> 00:42:35,924 where, like how do you solve that specific problem, to take an example. 710 00:42:37,001 --> 00:42:40,456 Rich Archbold: probably maybe the most applicable way was, how we were solving 711 00:42:40,606 --> 00:42:45,086 it at Intercom and how we were bringing in, ring lead, or I think like zoom 712 00:42:45,086 --> 00:42:49,536 info ops OS, what we were able to do was plug in multiple enrichment sources 713 00:42:49,606 --> 00:42:55,676 into ring lead and program some pretty complex survivorship rules for these 714 00:42:55,696 --> 00:43:00,491 things that then, ultimately updated this, single field in Salesforce. 715 00:43:00,531 --> 00:43:05,517 And we could say, like survivorship rules of where you have linked in data. 716 00:43:05,517 --> 00:43:10,428 Um, Always use linkedin data where you don't have linkedin data if 717 00:43:10,428 --> 00:43:16,948 you have, let's say zoom info data and some other data provider. 718 00:43:16,978 --> 00:43:23,197 And if it's in North America default to, zoom info, but if it is in Europe default 719 00:43:23,197 --> 00:43:29,054 to luscia, Data, let's say, like, I don't think there's any, 1 size fits all here. 720 00:43:29,564 --> 00:43:33,154 The different data providers will have different strengths in different 721 00:43:33,164 --> 00:43:35,834 regions and different segments. 722 00:43:36,414 --> 00:43:39,014 I think that the key thing is, you've got to keep talking to your 723 00:43:39,014 --> 00:43:43,542 reps and getting feedback from reps on what's actually working well for 724 00:43:43,542 --> 00:43:46,215 them and what's not working for them. 725 00:43:46,715 --> 00:43:52,835 I think that, the secret for me, or the key is that you're, rarely ever going 726 00:43:52,835 --> 00:43:54,715 to have somebody articulate to you. 727 00:43:55,895 --> 00:43:58,915 Hey, your priority zero problem is CRM data quality. 728 00:43:58,975 --> 00:44:02,425 You need to go and, I'm going to allow you down tools and not integrate 729 00:44:02,435 --> 00:44:06,155 any new software for me or not build any new workflows for me and just 730 00:44:06,555 --> 00:44:10,605 go spend 80 percent of your time cleaning up the data inside of our CRM. 731 00:44:11,015 --> 00:44:12,625 that's pretty much never going to happen. 732 00:44:13,075 --> 00:44:13,485 And. 733 00:44:13,486 --> 00:44:13,620 Okay. 734 00:44:14,630 --> 00:44:17,140 If you don't know any better, or if you haven't done up the battle 735 00:44:17,140 --> 00:44:20,300 scars, it's very easy to listen to your internal stakeholders. 736 00:44:20,320 --> 00:44:21,740 And they'll say, I want this tool. 737 00:44:21,740 --> 00:44:22,700 I want this workflow. 738 00:44:23,840 --> 00:44:25,540 I want you to launch this product. 739 00:44:25,790 --> 00:44:29,790 I want this new enablement source and you end up spending 120 percent 740 00:44:29,790 --> 00:44:34,690 of your time, adding new to the system and adding new complexity. 741 00:44:36,410 --> 00:44:39,660 Quickly, as you can, and that's the path to getting out of control. 742 00:44:40,150 --> 00:44:47,597 And I think that the real secret to us is having the conviction to know that, 743 00:44:48,284 --> 00:44:49,674 this is where you're going to go wrong. 744 00:44:49,684 --> 00:44:50,544 You're going to go wrong. 745 00:44:50,564 --> 00:44:54,884 If you're not constantly gardening and gatekeeping, uh, some of the data 746 00:44:54,884 --> 00:44:56,834 inside of the CRM that you aren't, um. 747 00:44:57,624 --> 00:45:04,637 Preaching this to your team that you aren't putting those guardrail metrics in 748 00:45:04,664 --> 00:45:07,224 place that allows you to get a sense of. 749 00:45:07,892 --> 00:45:13,422 this is kind of how good or bad it is that you're continuously talking to reps and 750 00:45:13,422 --> 00:45:18,715 that you're listening out for these type of keywords, that were, and you're able to 751 00:45:18,715 --> 00:45:22,555 tie it back to, I'm hearing data quality, but it's actually a prospecting thing. 752 00:45:22,575 --> 00:45:25,745 I can now go sell it to the business and go, Hey, here's how we can improve 753 00:45:25,745 --> 00:45:29,025 prospecting, or here's how we can move the numbers you care about. 754 00:45:29,615 --> 00:45:33,927 it's by investing In this thing, and I think as engineering leaders, it's up 755 00:45:33,927 --> 00:45:39,770 to us to champion that and to have that mindset and to not, unknowingly, walk 756 00:45:39,770 --> 00:45:45,196 ourselves into a corner of not necessarily technical debt, but Data debt, I think, 757 00:45:45,356 --> 00:45:49,196 again, if you're building products for external customers, you're all about 758 00:45:49,196 --> 00:45:53,546 the technical data and know that like software isn't being properly reused. 759 00:45:53,546 --> 00:45:57,306 And we need to take the time to refactor this software so that 760 00:45:57,306 --> 00:45:58,976 we're carrying less software. 761 00:45:59,326 --> 00:46:01,466 I think the same is true in the go to market world. 762 00:46:01,476 --> 00:46:02,376 It's in the data space. 763 00:46:02,406 --> 00:46:08,819 It's like, are we taking the time to refactor our, data, eliminate data 764 00:46:08,859 --> 00:46:11,699 that's now duplicate or unnecessary. 765 00:46:11,719 --> 00:46:14,512 And for me, difference between building product and building go 766 00:46:14,512 --> 00:46:16,152 to market is just a role reversal. 767 00:46:16,162 --> 00:46:19,653 One, you build products, the other is that you build data so, 768 00:46:19,653 --> 00:46:21,003 that you can buy your features. 769 00:46:21,653 --> 00:46:25,273 Justin Norris: And maybe the last question we have time for, but you've 770 00:46:25,293 --> 00:46:29,503 mentioned a few times about, this push and pull with your stakeholders, 771 00:46:29,573 --> 00:46:31,493 identifying what work you need to do. 772 00:46:32,748 --> 00:46:34,298 figuring out your priorities. 773 00:46:34,408 --> 00:46:38,348 I think this is perhaps the most challenging and an important job, you 774 00:46:38,348 --> 00:46:39,928 know, for any leader in the space. 775 00:46:39,948 --> 00:46:42,846 Cause if you make the wrong decisions, all the other work 776 00:46:42,846 --> 00:46:44,836 downstream, loses its impact. 777 00:46:46,016 --> 00:46:47,896 How do you think about that problem? 778 00:46:48,106 --> 00:46:48,846 how do you manage it? 779 00:46:49,416 --> 00:46:50,096 Rich Archbold: I think you're right. 780 00:46:50,176 --> 00:46:52,246 I think it is one of the hardest things. 781 00:46:52,995 --> 00:46:57,565 so at HubSpot, we have an excellent annual planning process that happens each year, 782 00:46:57,605 --> 00:47:03,380 which, that's where we kind of set out a lot of our, uh, Big rock goals, and we 783 00:47:03,380 --> 00:47:08,210 try and make sure we're generally hyper aligned with our business stakeholders 784 00:47:08,270 --> 00:47:13,390 on what are the biggest strategic needle moving projects that we need to do. 785 00:47:13,450 --> 00:47:17,172 And we make sure that we set aside capacity for those things. 786 00:47:18,307 --> 00:47:21,819 But we also know the business is, agile, the world changes around 787 00:47:21,819 --> 00:47:25,479 us, and we need to be nimble and responsive to those changes. 788 00:47:26,362 --> 00:47:30,422 the first port of call for being able to be nimble and agile to those 789 00:47:30,439 --> 00:47:35,899 changes is those, technical BSAs that we have embedded inside of rev 790 00:47:35,899 --> 00:47:40,769 ops, who we're continuously trying to build features and capabilities that. 791 00:47:41,184 --> 00:47:43,544 they can tweak and respond to. 792 00:47:44,324 --> 00:47:48,174 We also have work that enables us to, deliver some amount of agile 793 00:47:48,174 --> 00:47:49,987 automation, in that manner as well. 794 00:47:50,897 --> 00:47:52,747 And then we have our. 795 00:47:53,542 --> 00:47:56,982 Various different interlock meetings, our sales interlock, our support 796 00:47:57,175 --> 00:48:01,225 partner interlock where we have an ongoing intake process where, 797 00:48:01,845 --> 00:48:03,455 people could submit new requests. 798 00:48:03,775 --> 00:48:07,085 And we review those interlock meetings are happening on a 799 00:48:07,735 --> 00:48:09,465 bi weekly basis at the moment. 800 00:48:09,485 --> 00:48:13,015 I'd love to say they're frictionless, but they're not, sometimes we will 801 00:48:13,525 --> 00:48:17,285 discover dependencies that we didn't realize we had, or dependencies that 802 00:48:17,285 --> 00:48:18,475 were maybe bigger than we thought. 803 00:48:18,695 --> 00:48:21,115 Um, we need to adapt to them. 804 00:48:21,819 --> 00:48:27,511 it's, definitely not always perfect, but, some of the really interesting 805 00:48:27,521 --> 00:48:32,917 things are, What do you do when sales ops wants to do one thing, but your 806 00:48:32,917 --> 00:48:37,187 reps want to do something else or maybe the priorities aren't quite aligned 807 00:48:37,197 --> 00:48:41,377 where the reps will obviously be the ones to see the paper cuts and the 808 00:48:41,377 --> 00:48:43,807 friction with the existing processes. 809 00:48:44,117 --> 00:48:44,787 They all like. 810 00:48:45,167 --> 00:48:50,497 See and feel them every single day, every single deal they work, whereas 811 00:48:50,497 --> 00:48:53,977 the, sales ops or rev ops folks might be 1 step removed from that. 812 00:48:54,127 --> 00:49:00,946 And they're, more hyper focused on the bigger swing, strategy plays or supporting 813 00:49:00,946 --> 00:49:04,245 some of the new product launches or supporting maybe a bigger Segmentation 814 00:49:04,245 --> 00:49:05,255 change or something like that. 815 00:49:05,825 --> 00:49:08,045 And that's actually where it gets really interesting for me, 816 00:49:08,685 --> 00:49:13,185 where your first desire is, I want to make those reps happier. 817 00:49:13,234 --> 00:49:15,884 I want to fix those paper cuts for those reps, but maybe it's the same 818 00:49:15,884 --> 00:49:22,134 group of people that would be working on executing the larger strategic 819 00:49:22,164 --> 00:49:24,704 project, those are the really tough ones. 820 00:49:24,732 --> 00:49:28,942 the philosophy I preach is to try and set aside, no more than 70 821 00:49:28,942 --> 00:49:33,202 percent of your capacity for your, Big rock strategic goals and leave 822 00:49:33,262 --> 00:49:39,192 30 percent of your capacity, free to respond throughout the year and to. 823 00:49:39,757 --> 00:49:40,847 Address those paper cuts. 824 00:49:41,382 --> 00:49:45,699 And then my other tip, is, the more closely you can connect your engineering 825 00:49:45,699 --> 00:49:50,045 teams and your systems teams to the reps, the more rep shadowing you do, the more 826 00:49:50,045 --> 00:49:52,315 empathy you can build with those reps. 827 00:49:53,006 --> 00:49:57,496 The teams will just find a way to go, Oh yeah, we know these people. 828 00:49:57,746 --> 00:49:58,756 We're talking to them a lot. 829 00:49:58,796 --> 00:50:00,298 We know they're feeling this pain. 830 00:50:00,521 --> 00:50:04,131 We'll find something that we'll find a way to address some element of it. 831 00:50:04,131 --> 00:50:07,628 Just so it's not a sharp, but if you say we're primarily here to 832 00:50:07,638 --> 00:50:10,673 execute the strategy, but we measure the rep friction and we really 833 00:50:10,673 --> 00:50:12,543 care about rep friction as well. 834 00:50:12,983 --> 00:50:17,407 and you set aside some capacity for it and you get, The engineers and the PMs 835 00:50:17,447 --> 00:50:21,097 and the designers meeting regularly with the reps, everything just gets easier. 836 00:50:21,137 --> 00:50:24,777 That's the secret, the closer you get to reps, the more rep shadowing you 837 00:50:24,787 --> 00:50:28,277 can do without actually getting in the way, the more empathy you can develop, 838 00:50:28,310 --> 00:50:34,190 for them, the more you can help see around corners and fix things before 839 00:50:34,190 --> 00:50:36,440 they break or fix things before you're 840 00:50:36,440 --> 00:50:36,600 even 841 00:50:36,630 --> 00:50:36,870 asked 842 00:50:36,870 --> 00:50:37,080 to. 843 00:50:37,520 --> 00:50:39,880 Justin Norris: It's knowing your customer, you know, right? 844 00:50:39,980 --> 00:50:40,740 Rich Archbold: 100%, 845 00:50:41,040 --> 00:50:42,900 Justin Norris: closer you are to your customer, more empathy you 846 00:50:42,900 --> 00:50:46,910 have, the more you'll intuitively be drawn to fix those problems. 847 00:50:47,480 --> 00:50:48,940 Rich, this was so, so interesting. 848 00:50:48,950 --> 00:50:51,340 Uh, could have probably booked a three hour session. 849 00:50:51,340 --> 00:50:56,650 We'd still have more to cover, but really grateful for you joining us today and 850 00:50:56,780 --> 00:51:00,070 just being generous, sharing all your insights and what you folks are doing. 851 00:51:00,100 --> 00:51:00,990 I think it's fascinating. 852 00:51:00,990 --> 00:51:02,050 So thank you so much. 853 00:51:02,456 --> 00:51:03,236 Rich Archbold: Thank you for having me.