1 00:00:14,507 --> 00:00:17,117 Justin Norris: You know, the classic way of describing rev ops 2 00:00:17,127 --> 00:00:19,767 is people process and platforms. 3 00:00:19,767 --> 00:00:22,467 And while that may not be a perfect formulation, it's a 4 00:00:22,467 --> 00:00:23,837 pretty accurate description. 5 00:00:24,327 --> 00:00:28,937 Of what we do, what they don't tell you in RevOp school is that the people pillar 6 00:00:28,937 --> 00:00:33,647 is by far the hardest one to manage building and systems, creating processes, 7 00:00:33,657 --> 00:00:37,057 you know, those are challenging, but they're ultimately rewarding things to do. 8 00:00:37,097 --> 00:00:39,937 You get a big payoff at the end when there's a finished product 9 00:00:40,297 --> 00:00:41,627 and you have a lot of control. 10 00:00:42,467 --> 00:00:45,957 On the other hand, getting other people to actually do something is 11 00:00:45,957 --> 00:00:47,777 a whole other story, and it can be. 12 00:00:48,087 --> 00:00:52,907 Maddening to work with revenue teams that seem determined to do anything but follow 13 00:00:52,947 --> 00:00:56,957 the process that you've designed I'm, not suggesting anyone is out to get us, but 14 00:00:56,957 --> 00:01:01,712 it does point to the fact that enablement Is a huge part of our job and rev ops. 15 00:01:01,712 --> 00:01:03,762 And it often doesn't work very well. 16 00:01:03,772 --> 00:01:05,772 We create documents that no one reads. 17 00:01:05,772 --> 00:01:07,692 They sit in knowledge bases that no one visits. 18 00:01:08,022 --> 00:01:11,382 We spend our time responding to Slack messages from confused users 19 00:01:11,382 --> 00:01:15,622 or sending chatter reminders, asking people to just please follow the 20 00:01:15,622 --> 00:01:18,092 process for like the 500th time. 21 00:01:18,947 --> 00:01:21,867 And I may be exaggerating a bit to make a point, but not by much. 22 00:01:22,097 --> 00:01:25,827 So today's guest thinks that there is a better way to do software enablement. 23 00:01:26,307 --> 00:01:28,537 And he helped found a company to deliver on that promise. 24 00:01:28,577 --> 00:01:29,747 It's called Tango. 25 00:01:30,146 --> 00:01:33,307 And our guest is the company's COO, Dan Jovachini. 26 00:01:33,847 --> 00:01:35,087 Dan, so glad to have you here. 27 00:01:35,622 --> 00:01:39,205 Daniel Giovacchini: Great to be here, Justin, and, really well articulated 28 00:01:39,205 --> 00:01:43,120 opening on, a lot of the challenges I think that, you know, folks face out 29 00:01:43,120 --> 00:01:45,783 there with, with change in management, and that's exactly what we spend 30 00:01:45,783 --> 00:01:46,913 most of our days thinking about. 31 00:01:47,093 --> 00:01:50,183 Justin Norris: I spend a lot of my day dealing with those exact challenges. 32 00:01:50,183 --> 00:01:51,616 So they hit close to home. 33 00:01:51,827 --> 00:01:56,667 and I'm wondering, Dan, as I was looking through your background, I saw you 34 00:01:56,667 --> 00:01:58,657 spent about seven years in the VC world. 35 00:01:58,657 --> 00:02:02,567 So before we pivot into Tango and enablement and all that, I want to 36 00:02:02,567 --> 00:02:05,926 be opportunistic and just get your perspective, putting your VC hat on 37 00:02:05,926 --> 00:02:08,166 again for a minute, what is going on? 38 00:02:08,175 --> 00:02:10,686 You know, we've experienced a fairly strange. 39 00:02:11,141 --> 00:02:14,911 reset in the market over the past few years, it's impacting a lot of SAS 40 00:02:14,921 --> 00:02:16,751 companies, things have really changed. 41 00:02:17,381 --> 00:02:19,481 The old playbooks don't work the same anymore. 42 00:02:19,781 --> 00:02:22,781 What are you thinking about as, as kind of a founder? 43 00:02:22,781 --> 00:02:26,101 What should other founders be focused on to survive and thrive in this 44 00:02:26,101 --> 00:02:27,531 environment and that kind of thing? 45 00:02:28,308 --> 00:02:29,158 Daniel Giovacchini: Yeah, it's a great question. 46 00:02:29,158 --> 00:02:32,608 I mean, you for so long, it seemed like there was finally a sense of 47 00:02:32,618 --> 00:02:37,398 normal and bull market and, you know, it was just bigger fundraising 48 00:02:37,398 --> 00:02:39,528 rounds happening year after year. 49 00:02:39,528 --> 00:02:42,138 And, and then suddenly we, we hit this new bear market. 50 00:02:42,428 --> 00:02:44,737 and some ways. 51 00:02:45,772 --> 00:02:48,182 Tightening and economic slowdown. 52 00:02:48,393 --> 00:02:51,624 it's part of what precipitated that, but it was also, we were probably just 53 00:02:51,624 --> 00:02:57,656 overheating on, a number of areas of, of software spend in particular, and, 54 00:02:57,656 --> 00:03:01,468 uh, markets that kind of founders and VCs both looked at and said, Oh, 55 00:03:01,898 --> 00:03:03,348 we've seen this happen somewhere else. 56 00:03:03,348 --> 00:03:04,695 And why can't it happen here? 57 00:03:04,705 --> 00:03:08,524 Like the Uber for, for X playbook or something for every market. 58 00:03:08,554 --> 00:03:12,054 And, kind of where that got us, I think is starting to. 59 00:03:12,564 --> 00:03:14,794 Really get back to me. 60 00:03:14,794 --> 00:03:17,624 Think about the customer, what are their organizational 61 00:03:17,624 --> 00:03:20,884 level challenges and problems? 62 00:03:20,884 --> 00:03:23,794 And, you know, what are their operating hurdles that, that they need to get 63 00:03:23,794 --> 00:03:28,364 passed and no matter if you're a founder, your company, you know, working on 64 00:03:28,364 --> 00:03:33,124 a, an end user focused tool and the marketing stack, or if you're something 65 00:03:33,124 --> 00:03:36,224 that helps, you know, org wide for HR. 66 00:03:36,474 --> 00:03:41,344 You really all have to tie back to some organizational level initiative. 67 00:03:41,374 --> 00:03:46,114 And if you can't map to a customer OKR, you should stop 68 00:03:46,114 --> 00:03:47,640 and think about how you can. 69 00:03:47,640 --> 00:03:52,038 and so, you know, I think that, slow down in funding and, difficult fundraising 70 00:03:52,038 --> 00:03:59,792 environment kind of 2021, uh, 2023 started to reinforce probably some healthier 71 00:03:59,792 --> 00:04:04,056 innovation behaviors and healthier, really like product marketing and sales 72 00:04:04,056 --> 00:04:06,498 pitches from, from founders and companies. 73 00:04:06,498 --> 00:04:11,993 And, then I has obviously just become the theme of the moment and. 74 00:04:12,853 --> 00:04:17,143 It's, there's never been a better time to be insanely curious about what's 75 00:04:17,143 --> 00:04:21,663 possible, if you're an operator within a company and, and all these new tools and 76 00:04:21,663 --> 00:04:25,753 technology that's available, or if you're, you're a vendor yourself or a founder or 77 00:04:25,753 --> 00:04:31,483 VC and think about your product and, and your longterm, value creation path, right? 78 00:04:31,963 --> 00:04:34,332 at the same time, that's a lot of noise. 79 00:04:34,393 --> 00:04:36,633 And, and so, you know, how do you cut through the noise? 80 00:04:37,508 --> 00:04:42,388 Make sure that you're, you're building a product or a business or a service 81 00:04:42,388 --> 00:04:44,388 that matters, for a long time. 82 00:04:44,388 --> 00:04:49,178 that's getting back to that probably, you know, healthier behavior of saying, Hey, 83 00:04:49,178 --> 00:04:54,013 how do we map to real organizational level challenges and problems for our customers? 84 00:04:54,143 --> 00:04:58,977 Justin Norris: it 10 years, you know, it was almost like a crazy, 85 00:04:58,977 --> 00:05:00,487 drug trip or something like that. 86 00:05:00,487 --> 00:05:02,537 And now things have kind of come back down. 87 00:05:02,907 --> 00:05:07,617 to reality in the sense that, customer acquisition costs that are completely 88 00:05:07,617 --> 00:05:11,267 untethered from business fundamentals, we're sort of normalized software 89 00:05:11,267 --> 00:05:15,112 purchasing behavior that, doesn't really make sense economically. 90 00:05:15,492 --> 00:05:16,292 It's kind of normalized. 91 00:05:16,292 --> 00:05:20,092 So I definitely see what you're saying as a, as someone who's often 92 00:05:20,092 --> 00:05:23,032 a software buyer and is having to make business cases for software. 93 00:05:23,472 --> 00:05:26,402 The rules of that game have definitely changed for me. 94 00:05:26,582 --> 00:05:30,722 And I think for a lot of my peers, how have you found the discussion 95 00:05:30,732 --> 00:05:36,473 around your category of, kind of like enablement and, digital adoption, have 96 00:05:36,493 --> 00:05:38,063 the dynamics there changed at all? 97 00:05:38,676 --> 00:05:41,226 Daniel Giovacchini: You know, they really have changed with AI, especially 98 00:05:41,226 --> 00:05:42,936 in the last year or two here. 99 00:05:42,936 --> 00:05:49,277 And, chat GPT came out and a lot of founders and a lot of VCs looked at 100 00:05:49,407 --> 00:05:53,707 the underlying models, chat GPT used and said, okay, this is amazing. 101 00:05:54,052 --> 00:05:55,332 What else is possible? 102 00:05:55,602 --> 00:06:00,453 And, you know, I'd say we were still in the middle of a big discovery phase 103 00:06:00,453 --> 00:06:05,653 here for where's the application layer value going to accrue and, where are 104 00:06:05,653 --> 00:06:10,083 we going to start to see, the massive productivity improvements that, people 105 00:06:10,133 --> 00:06:13,283 are sensing that are possible, but, you know, we're still waiting to 106 00:06:13,283 --> 00:06:14,893 come to fruition in a lot of cases. 107 00:06:14,893 --> 00:06:19,273 And, a couple of early examples of, areas that you've seen the impact right away. 108 00:06:19,303 --> 00:06:23,103 certainly data analytics tools, certainly customer service 109 00:06:23,143 --> 00:06:27,203 conversations, and you can point to vendors and those categories that. 110 00:06:27,643 --> 00:06:33,332 I've started to do just show ROI cases that have kind of never been seen before. 111 00:06:33,633 --> 00:06:37,433 but as you think about enablement and process and, you know, a lot 112 00:06:37,433 --> 00:06:41,753 of the world that both you and I spend a lot of time in, what you're 113 00:06:41,753 --> 00:06:48,013 starting to see is potentially two paths to take an enablement. 114 00:06:48,332 --> 00:06:54,421 And one is, somewhat, Search focused query focused, and you can think chat, GBT. 115 00:06:54,421 --> 00:06:55,831 You can think chat UX. 116 00:06:56,091 --> 00:07:00,531 You can think, glean as a, company that's, been more, more and more talked about 117 00:07:00,531 --> 00:07:06,001 on the, the venture scene, but okay, we can be really information centric 118 00:07:06,011 --> 00:07:11,813 and, center our enablement initiatives around, unstructured text knowledge. 119 00:07:11,813 --> 00:07:12,093 Right. 120 00:07:12,093 --> 00:07:13,373 And we're just going to bet that. 121 00:07:13,623 --> 00:07:15,953 Operators are going to know the right questions to ask, and they're going 122 00:07:15,953 --> 00:07:18,363 to be able to go retrieve answers. 123 00:07:18,723 --> 00:07:21,703 And we were able to suddenly index all that information in a much more 124 00:07:21,703 --> 00:07:25,323 powerful way, and AI is going to help serve results, you know, and that's 125 00:07:25,323 --> 00:07:26,781 going to improve how people work. 126 00:07:27,231 --> 00:07:31,656 There's another path that's probably more, We're going down, right? 127 00:07:31,656 --> 00:07:34,046 Which is just in the flow of work enablement. 128 00:07:34,076 --> 00:07:38,346 And so that's almost betting that, Hey, instead of being information 129 00:07:38,346 --> 00:07:39,946 centric, let's be process centric. 130 00:07:39,956 --> 00:07:40,756 Let's think about. 131 00:07:41,186 --> 00:07:45,956 Where a user operator is spending time, what tools they're in, what 132 00:07:45,976 --> 00:07:50,486 information might they need, when might they need it, and let's try and 133 00:07:50,486 --> 00:07:55,496 serve it to them proactively or make it available at their fingertips in 134 00:07:55,496 --> 00:08:00,243 such a way that We're not actually requiring them to go and, understand 135 00:08:00,243 --> 00:08:04,533 the right query to be asking to unblock themselves or to do their job better, 136 00:08:04,563 --> 00:08:08,323 to find answers to serve a customer, you know, kind of whatever it might be. 137 00:08:08,323 --> 00:08:10,733 So I think that's kind of where. 138 00:08:11,273 --> 00:08:14,423 there's two paths in front of us in the enablement space. 139 00:08:14,423 --> 00:08:17,723 And you're seeing companies take kind of two different approaches 140 00:08:17,723 --> 00:08:19,103 if you want to be simplistic. 141 00:08:19,103 --> 00:08:22,573 And, you know, there's going to be a place for both, but it's sort of 142 00:08:22,573 --> 00:08:25,803 within, if you're an operator, you kind of start to think about, you 143 00:08:25,803 --> 00:08:28,673 know, which, which one makes most sense For your situation for your company. 144 00:08:29,243 --> 00:08:32,732 Justin Norris: You know, when we think about the sorts of rev ops 145 00:08:32,732 --> 00:08:37,212 use cases, we often encounter CRM enablement or some other sort of tool 146 00:08:37,212 --> 00:08:41,533 enablement, or, you have a revenue or marketing sales CS user needs to do 147 00:08:41,533 --> 00:08:43,283 a certain thing in a certain place. 148 00:08:43,993 --> 00:08:49,633 The, in the flow of work model just seems commonsensically the way to go, because 149 00:08:50,123 --> 00:08:53,133 nobody cares to go, like you said, ask a question or know the right question. 150 00:08:53,193 --> 00:08:54,833 There's so much more room for error. 151 00:08:55,103 --> 00:08:56,503 There's so much more user discretion. 152 00:08:56,773 --> 00:08:59,773 Why not just show them what to do in the moment that they need 153 00:09:00,083 --> 00:09:03,133 To know that information most and in the place where they are. 154 00:09:03,633 --> 00:09:06,553 And we'll get a bit deeper into tango itself, but I'm just curious, like 155 00:09:06,553 --> 00:09:09,723 what's the, at the market level, what's the argument against doing that? 156 00:09:09,723 --> 00:09:11,773 Cause it just seems that is the way that you should do it to me. 157 00:09:12,435 --> 00:09:12,705 Daniel Giovacchini: Yeah. 158 00:09:12,705 --> 00:09:15,476 I mean, different information types, right? 159 00:09:15,476 --> 00:09:21,686 So there's a lot of the unstructured conversation that happens about product, 160 00:09:21,716 --> 00:09:28,626 customer market, competitor, internal strategy, decisioning, and a lot of 161 00:09:28,626 --> 00:09:31,546 that just fundamentally lives within. 162 00:09:32,316 --> 00:09:35,926 A slack, a teams, a knowledge base, email. 163 00:09:35,946 --> 00:09:41,016 and so, you know, there is golden knowledge that lives there. 164 00:09:41,016 --> 00:09:44,266 And you know, how do you potentially surface that in ways? 165 00:09:44,266 --> 00:09:48,990 And if we think, Hey, you're a seller and you're talking to a 166 00:09:48,990 --> 00:09:50,820 new account for the first time. 167 00:09:51,208 --> 00:09:55,692 and there's been some new, product developments that perhaps you should 168 00:09:55,702 --> 00:09:58,732 be aware of for that account, or there's been some new competitive 169 00:09:58,732 --> 00:10:00,582 Intel that's been discussed somewhere. 170 00:10:00,822 --> 00:10:04,162 If you actually want to surface that, that information, you know, for 171 00:10:04,162 --> 00:10:07,462 that seller, You're going to want to potentially search against a lot of 172 00:10:07,462 --> 00:10:09,959 these other, knowledge repositories. 173 00:10:09,999 --> 00:10:14,479 And, you know, it's not to say you can't serve that up, in the moment. 174 00:10:14,489 --> 00:10:19,769 But, right now we're in the flow of work enablement where that technology is. 175 00:10:19,769 --> 00:10:23,629 And that that thinking is it hasn't quite incorporated all That general 176 00:10:23,629 --> 00:10:26,169 market company, customer information. 177 00:10:26,169 --> 00:10:30,369 So that's probably just still a bridge that kind of needs to 178 00:10:30,379 --> 00:10:33,679 be crossed technologically to start to make that all available. 179 00:10:33,689 --> 00:10:38,284 But I totally think, the end vision, if we put our heads together, it should be 180 00:10:38,574 --> 00:10:42,734 less proactively serve this up when people need it and not require them to search for 181 00:10:42,854 --> 00:10:43,314 Justin Norris: Got it. 182 00:10:43,635 --> 00:10:43,895 Cool. 183 00:10:43,935 --> 00:10:48,245 Well, we'll dig a bit more into that, but maybe first we'll just turn back the 184 00:10:48,245 --> 00:10:53,475 page a little bit and just talk about founding a company, starting with this 185 00:10:53,475 --> 00:10:57,335 idea and how you go from there to MVP. 186 00:10:57,905 --> 00:10:59,905 Daniel Giovacchini: There's a lot of thoughts and literature out 187 00:10:59,905 --> 00:11:04,515 there on founding a company and, the best way to go about early product 188 00:11:04,515 --> 00:11:06,265 development, problem discovery. 189 00:11:07,097 --> 00:11:10,597 You know, there's a couple things that I think have stood true as far as, 190 00:11:10,720 --> 00:11:14,970 the test of time And just fundamental truths about good innovation practice. 191 00:11:14,970 --> 00:11:16,810 And I think there's a couple of things that are pretty outdated. 192 00:11:16,820 --> 00:11:23,412 So, for starters, first trap to fall into is feeling like you have a great idea 193 00:11:23,452 --> 00:11:29,857 and you have a solution that the market just needs and you Go just build it. 194 00:11:30,070 --> 00:11:35,086 it's how a lot of founders and it's how a lot of stories get told about companies 195 00:11:35,086 --> 00:11:39,006 is you have this sudden golden insight about something that, you or others have 196 00:11:39,006 --> 00:11:40,606 experienced and you just go build it. 197 00:11:41,586 --> 00:11:43,566 It's so often not the case. 198 00:11:43,606 --> 00:11:49,098 And you go look at the actual evolution stories of, companies 199 00:11:49,098 --> 00:11:50,208 in their earliest days. 200 00:11:50,208 --> 00:11:50,568 And. 201 00:11:50,963 --> 00:11:54,423 You can start with an idea, but it's going to iterate so much. 202 00:11:54,463 --> 00:12:00,293 It's going to change based on the first time you go and actually ask 203 00:12:00,293 --> 00:12:04,293 about, what are those organizational level OKRs that you have? 204 00:12:04,293 --> 00:12:08,143 What are actual problems that are top of mind, for this ICP that you 205 00:12:08,143 --> 00:12:11,783 thought you understood what, other competitive products are out there 206 00:12:11,783 --> 00:12:12,983 that maybe you weren't aware of. 207 00:12:13,543 --> 00:12:15,684 And so, the quick lesson there is just. 208 00:12:16,204 --> 00:12:20,224 You should really think about entering a problem space and not 209 00:12:20,254 --> 00:12:22,794 entering into building a solution. 210 00:12:22,804 --> 00:12:26,894 And the more you can be curious about your problem space early on and be 211 00:12:27,144 --> 00:12:32,024 open and flexible to iterating and serving true North on your compass as 212 00:12:32,234 --> 00:12:36,244 how do we provide the most value for customers that, you know, they uniquely 213 00:12:36,244 --> 00:12:40,344 do not have somewhere else, that's, what's going to really guide you down 214 00:12:40,344 --> 00:12:42,989 the I think the most successful path. 215 00:12:43,359 --> 00:12:46,559 the other one is, is related to building too. 216 00:12:46,839 --> 00:12:52,064 And this could apply for products or services, but lean startup method came 217 00:12:52,064 --> 00:12:56,234 out and this minimum viable product concept came out, pretty early on 218 00:12:56,354 --> 00:12:58,254 and, sort of entrepreneurial lore. 219 00:12:58,284 --> 00:12:58,714 And. 220 00:12:59,494 --> 00:13:03,774 What still stands true about it is you should absolutely be going to 221 00:13:03,774 --> 00:13:05,874 get feedback as fast as possible. 222 00:13:06,324 --> 00:13:11,124 What has changed is you should not be launching half 223 00:13:11,124 --> 00:13:13,264 baked versions of a solution. 224 00:13:13,264 --> 00:13:16,454 So, you know, as you get through that problem space discovery, and 225 00:13:16,454 --> 00:13:20,248 as you figure out, something that you have a strong hypothesis is, is 226 00:13:20,248 --> 00:13:25,438 going to be a game changer for, for your customer, you really need to 227 00:13:25,438 --> 00:13:27,068 take advantage of your launch moment. 228 00:13:27,108 --> 00:13:28,838 And this is due to. 229 00:13:29,289 --> 00:13:32,179 the cost of starting a company of creating a product, all of that 230 00:13:32,179 --> 00:13:33,929 has, being driven down to zero. 231 00:13:33,929 --> 00:13:36,619 And, you know, even with AI, right, people are going to create products and 232 00:13:36,619 --> 00:13:39,909 software and services, you know, way faster than they ever had historically. 233 00:13:39,909 --> 00:13:44,443 And if you're a, an individual contributor, if you're a buyer, 234 00:13:44,468 --> 00:13:48,608 user champion, no matter what you are at a company, there's just. 235 00:13:49,158 --> 00:13:52,768 Hundreds and thousands of products that you can be going to try every day. 236 00:13:52,778 --> 00:13:57,686 And, the excitement of something new it's very much become noise and less 237 00:13:57,706 --> 00:14:00,446 become a delightful moment in your day. 238 00:14:00,456 --> 00:14:04,936 So if you're going to come out and launch a new product or service to the world, 239 00:14:06,066 --> 00:14:07,936 really try and get your launch right. 240 00:14:08,015 --> 00:14:12,028 so we read this article early on from first round review. 241 00:14:12,078 --> 00:14:14,958 They put out amazing content, you know, especially For builders of 242 00:14:14,958 --> 00:14:16,208 companies in the early stages. 243 00:14:16,208 --> 00:14:19,278 And the title of the article is don't serve burnt pizza. 244 00:14:19,418 --> 00:14:22,690 And it hit us just at the right moment in time. 245 00:14:22,690 --> 00:14:26,758 And we sort of made it, one of our, manifestos, but, think about creating 246 00:14:26,758 --> 00:14:31,969 a minimum lovable product, not just a minimum viable product, and, that means 247 00:14:31,979 --> 00:14:33,619 first impressions really do matter. 248 00:14:33,929 --> 00:14:37,969 take the extra six months to really get your product marketing, right. 249 00:14:39,069 --> 00:14:43,009 Put that extra design touch if you are a product company to really think 250 00:14:43,009 --> 00:14:44,639 through that, that service offering. 251 00:14:44,901 --> 00:14:47,461 so when you launch, you can take advantage of that and that early 252 00:14:47,461 --> 00:14:51,671 momentum is what you're going to need to propel you in those early days to 253 00:14:51,871 --> 00:14:56,139 then be on the path to, whatever it is, securing more funding or reaching more 254 00:14:56,139 --> 00:14:57,949 customers or hiring more of your team. 255 00:14:58,109 --> 00:15:02,379 Justin Norris: You know, that narrative around, iteration has been a constant, 256 00:15:02,459 --> 00:15:06,659 I think with every founder that I've spoken to that has come on the show. 257 00:15:06,669 --> 00:15:09,269 I think Eloqua started as a chat product. 258 00:15:09,579 --> 00:15:12,409 Marketo started as some sort of AdWords interface. 259 00:15:12,409 --> 00:15:16,099 Like the ideas changed really drastically. 260 00:15:16,619 --> 00:15:21,709 I'm curious, how did you know when you had iterated to the place where 261 00:15:21,709 --> 00:15:24,719 you had something that was a minimum lovable product, as you put it? 262 00:15:25,078 --> 00:15:25,788 Daniel Giovacchini: Yeah, awesome. 263 00:15:25,788 --> 00:15:27,618 So, we actually set out to solve this. 264 00:15:28,928 --> 00:15:32,348 Be curious in this problem space of learning on the job and solve 265 00:15:32,348 --> 00:15:37,423 this, kind of, problem we felt was out there of just, it takes too 266 00:15:37,423 --> 00:15:39,333 long to get good at what you do. 267 00:15:39,333 --> 00:15:44,733 And this is really from a, tactical perspective of how do I be successful 268 00:15:44,733 --> 00:15:46,453 in my new role at a company? 269 00:15:46,463 --> 00:15:51,917 And, we did more discovery and we, we kind of traced this, path to, well, 270 00:15:51,927 --> 00:15:57,132 learning the tools that you use is actually this like Kind of fundamental 271 00:15:57,142 --> 00:16:02,896 barrier to contributing to job performance and, getting past that ramp or nesting 272 00:16:02,896 --> 00:16:07,756 period into, you know, okay, I'm actually taking inbound volume for the 273 00:16:07,756 --> 00:16:11,926 first time, or I'm, you know, answering chat conversations, you know, that 274 00:16:11,966 --> 00:16:14,596 are real, real live, live customers. 275 00:16:14,945 --> 00:16:16,535 but we. 276 00:16:16,790 --> 00:16:22,820 You know, for us, it was, okay, we think there's an interesting hypothesis 277 00:16:22,820 --> 00:16:27,460 or idea around the best people on your team have figured out something 278 00:16:28,260 --> 00:16:32,180 unique to your company about how to be successful and how they work. 279 00:16:32,230 --> 00:16:36,610 And, we borrowed this a little bit from gong and chorus in the. 280 00:16:36,690 --> 00:16:40,610 The sales tech stack where they figured out that, you know, Hey, there's a lot 281 00:16:40,630 --> 00:16:47,080 of golden insight for teams and companies in the conversations of your top sellers, 282 00:16:47,440 --> 00:16:50,430 and they're doing things on those sales calls that everybody could learn from. 283 00:16:50,980 --> 00:16:54,510 And so, we went around and got curious about, Hey, learning 284 00:16:54,510 --> 00:16:55,400 on the job is really hard. 285 00:16:55,400 --> 00:16:58,464 Is this a problem, for you as a VP, is this a problem for you 286 00:16:58,464 --> 00:17:02,294 as a new hire, we got a lot of certainty and learned that, Hey, this 287 00:17:02,294 --> 00:17:03,614 would be a problem worth solving. 288 00:17:04,049 --> 00:17:07,628 And then we had this hypothesis of like, if you could actually understand what 289 00:17:07,628 --> 00:17:12,569 makes Susie from Scottsdale so good at what she does, and then make that the 290 00:17:12,569 --> 00:17:16,438 basis for, training and enablement, would that potentially be interesting? 291 00:17:16,938 --> 00:17:17,933 And, we. 292 00:17:18,278 --> 00:17:19,548 Kept pulling on that thread. 293 00:17:19,548 --> 00:17:24,396 And, so we did get into product development and what we realized is 294 00:17:24,656 --> 00:17:32,426 that, you know, whoa, this, wasn't just something for customer support or for, you 295 00:17:32,426 --> 00:17:38,926 know, BPOs and call centers where learning the actual, click process or click 296 00:17:38,936 --> 00:17:41,336 stream of how do I navigate my tools. 297 00:17:41,651 --> 00:17:44,871 Was valuable and actually spread to way more functions. 298 00:17:44,871 --> 00:17:46,591 And it was way more of a horizontal. 299 00:17:47,104 --> 00:17:47,684 Problem space. 300 00:17:47,684 --> 00:17:51,529 Then, then we kind of initially realized, and, the moment it clicked 301 00:17:51,529 --> 00:17:56,649 for us that we were close to something that was minimum lovable was we 302 00:17:56,649 --> 00:18:00,299 went and did these controlled pilots with five or six different teams 303 00:18:00,329 --> 00:18:05,282 at, five or six different companies, different functions, and, it was free. 304 00:18:05,412 --> 00:18:08,922 we tried to charge initially, but that was even difficult. 305 00:18:08,932 --> 00:18:10,632 And so we just made it free. 306 00:18:11,072 --> 00:18:14,402 And it was the moment where, instead of us just like begging people to 307 00:18:14,402 --> 00:18:17,960 use it, they started to use it on their own and they started to ask 308 00:18:18,090 --> 00:18:19,760 about, Hey, would this be possible? 309 00:18:19,760 --> 00:18:21,440 Would there be more features here? 310 00:18:21,630 --> 00:18:23,370 Hey, could I get somebody else on? 311 00:18:23,790 --> 00:18:25,940 And so, you know, we use this like kind of controlled beta 312 00:18:25,940 --> 00:18:30,460 environment to sort of assess some of that minimum lovable component. 313 00:18:30,498 --> 00:18:32,910 and, we said, okay, we think we have something here. 314 00:18:33,200 --> 00:18:38,520 Now let's take the three to six months extra to go get this ready for a launch. 315 00:18:38,820 --> 00:18:42,710 And, you know, we're going to make a bet that we can really land a first 316 00:18:42,710 --> 00:18:46,950 impression based on these early learnings with a broader audience. 317 00:18:47,120 --> 00:18:48,950 And we were fortunate that, that we did. 318 00:18:49,366 --> 00:18:51,626 Justin Norris: When you mentioned those horizontal use cases, I'm 319 00:18:51,626 --> 00:18:53,917 curious, what are some good examples? 320 00:18:53,917 --> 00:18:58,393 Cause was mentioning before we hit record, I've used Tango a few times in my 321 00:18:58,393 --> 00:19:03,107 company but it's been mostly focused on, software navigation, click stream stuff. 322 00:19:03,147 --> 00:19:05,767 Like you said, where would you go from there? 323 00:19:06,061 --> 00:19:06,371 Daniel Giovacchini: Yeah. 324 00:19:06,371 --> 00:19:10,710 So, You kind of look at it and we realized that like, Hey, the target 325 00:19:10,710 --> 00:19:15,350 market for trying to teach other people how to use software, it's really anybody 326 00:19:15,350 --> 00:19:19,350 who's tried to take a manual screenshot, paste it into Google doc and write out 327 00:19:19,350 --> 00:19:23,570 some steps and send that to somebody to tell them how to do something right. 328 00:19:23,680 --> 00:19:27,080 Or in a Slack thread or in a, you know, email conversation. 329 00:19:27,550 --> 00:19:29,040 And so. 330 00:19:29,505 --> 00:19:34,075 we really thought it was like going to be customer support and, 331 00:19:34,305 --> 00:19:36,325 potentially call centers again. 332 00:19:36,635 --> 00:19:41,515 But, it was every function, from engineering to, consultants and 333 00:19:41,515 --> 00:19:44,905 consulting firms to HR professionals. 334 00:19:44,935 --> 00:19:47,845 You're trying to learn how to use the performance management software. 335 00:19:48,165 --> 00:19:52,268 And I guess, we just didn't totally realize that this friction 336 00:19:52,278 --> 00:19:54,568 really does exist as, as much as. 337 00:19:54,883 --> 00:19:59,823 software has, improved, the ability to go get tasks done. 338 00:19:59,897 --> 00:20:03,963 we take it for granted and a lot of cases, and, especially from an 339 00:20:03,963 --> 00:20:07,373 ops and enablement perspective, you know, people are very familiar 340 00:20:07,373 --> 00:20:09,373 with tools, very, very tech savvy. 341 00:20:09,623 --> 00:20:13,723 Um, you know, especially if you're in a venture backed company, but you think 342 00:20:13,723 --> 00:20:18,723 about other people who choosing technology is not the central component of their job. 343 00:20:19,002 --> 00:20:24,466 and it's frustrating and people don't want to, spend the time, going and 344 00:20:24,466 --> 00:20:29,126 learning and the help docs, how to use the software, navigate it and try and. 345 00:20:29,416 --> 00:20:30,786 trial and error on their own. 346 00:20:31,056 --> 00:20:33,726 so, that's kind of what I was referencing 347 00:20:33,726 --> 00:20:37,286 when, you know, horizontal, it's just this, peer to peer teaching 348 00:20:37,286 --> 00:20:38,276 of, of how to use software 349 00:20:38,506 --> 00:20:41,316 Justin Norris: Across more functions, more teams, sort of 350 00:20:41,316 --> 00:20:42,636 anywhere in the organization. 351 00:20:43,055 --> 00:20:43,605 Daniel Giovacchini: Exactly. 352 00:20:43,630 --> 00:20:47,100 Justin Norris: so you have that magic moment where you're like, oh, this is 353 00:20:47,100 --> 00:20:51,520 something that people want to use And I can imagine that's a very interesting 354 00:20:51,520 --> 00:20:55,540 feeling as a founder who's gone through this Sort of hero's journey of building 355 00:20:55,540 --> 00:20:59,780 a product and iterating on it Then you start to think about go to market and 356 00:20:59,780 --> 00:21:04,169 how to commercialize it at a at a bigger scale What was the dialogue there? 357 00:21:04,434 --> 00:21:07,650 Daniel Giovacchini: you basically have two to three choices when you're 358 00:21:07,650 --> 00:21:12,830 launching a product and thinking about go to market motion today's day and age. 359 00:21:12,830 --> 00:21:13,110 Right. 360 00:21:13,120 --> 00:21:13,340 And. 361 00:21:14,195 --> 00:21:20,246 you have a bottoms up version, where you say, Hey, you think anybody can use this? 362 00:21:20,276 --> 00:21:24,176 You think that your products can somewhat teach itself. 363 00:21:24,466 --> 00:21:30,286 And then you have a top down version where, You're saying, Hey, the value 364 00:21:30,286 --> 00:21:34,887 of this software, the benefits of this, service need to be explained. 365 00:21:34,897 --> 00:21:37,248 They can't be taught or discovered. 366 00:21:37,558 --> 00:21:41,534 and then maybe you have something in the middle where, there's interactive 367 00:21:41,534 --> 00:21:44,874 demo experiences started to become, more popular, and you can use 368 00:21:44,874 --> 00:21:49,054 that to divert people into sales conversations or a self serve journey. 369 00:21:49,054 --> 00:21:50,486 So, maybe that's a new one. 370 00:21:50,486 --> 00:21:53,519 That's, kind of emerging more, but, you know, for us. 371 00:21:54,074 --> 00:21:58,658 We looked at it and, again, we had initially thought, okay, 372 00:21:58,658 --> 00:22:02,027 this is very targeted, at a couple of specific functions. 373 00:22:02,157 --> 00:22:05,165 but when we realized that, you know, Hey, this is more horizontal than we 374 00:22:05,165 --> 00:22:10,265 thought really the litmus test for should you go bottoms up or should you go. 375 00:22:10,660 --> 00:22:16,520 Horizontal PLG is how quickly can you provide time to value 376 00:22:16,810 --> 00:22:18,940 and get users to an aha moment? 377 00:22:19,443 --> 00:22:24,303 that's basically referring to Can they get something of value from using your 378 00:22:24,303 --> 00:22:26,513 product in a single player fashion? 379 00:22:26,973 --> 00:22:34,092 in more or less 60 seconds or or under right around there and if you can you're 380 00:22:34,092 --> 00:22:38,992 gonna see a lot of benefits of bottoms up and plg You People are going to go in, 381 00:22:39,042 --> 00:22:42,942 understand your product, get something from it, be so wowed that they're 382 00:22:42,942 --> 00:22:44,482 going to want to tell people about it. 383 00:22:44,701 --> 00:22:47,821 they're going to want to potentially come back to it and think more about how 384 00:22:47,821 --> 00:22:49,861 they could use it in a bigger fashion. 385 00:22:50,176 --> 00:22:51,506 make it part of their routine. 386 00:22:52,226 --> 00:22:57,186 If you can't, then you're very likely just to get a bunch of tire kickers early on. 387 00:22:57,206 --> 00:22:59,626 Maybe they're interested in checking it out, but you're 388 00:22:59,626 --> 00:23:00,826 not going to get people hooked. 389 00:23:00,926 --> 00:23:03,229 and that could be for a couple reasons. 390 00:23:03,249 --> 00:23:03,989 It could be. 391 00:23:04,614 --> 00:23:06,744 Do you have a fundamentally multiplayer experience? 392 00:23:06,744 --> 00:23:09,064 Do you need multiple people involved? 393 00:23:09,074 --> 00:23:12,434 You know, a team to actually get value from your products. 394 00:23:12,534 --> 00:23:17,224 If you do, it's going to be very hard to convince that first person who finds you 395 00:23:17,514 --> 00:23:19,964 to invite a team to try something out. 396 00:23:20,291 --> 00:23:23,921 it's too much to ask without having ever proved anything to them or 397 00:23:23,931 --> 00:23:25,441 given value to them up front. 398 00:23:25,811 --> 00:23:27,598 or, if it's not multiplayer. 399 00:23:27,873 --> 00:23:31,863 But the product experience actually just fundamentally is more complex 400 00:23:31,963 --> 00:23:36,393 or requires more configuration or set up, then you're really going to need 401 00:23:36,393 --> 00:23:39,238 to teach them why they need to do it. 402 00:23:39,288 --> 00:23:42,568 And super unlikely you're gonna be able to do it in a self serve fashion. 403 00:23:42,848 --> 00:23:45,699 You're gonna want to talk to them and have somebody really experienced 404 00:23:45,699 --> 00:23:49,359 sell the benefits and get them into a trial or a sales process. 405 00:23:49,722 --> 00:23:52,429 Justin Norris: So you, I'm, I'm making an educated guess, the 406 00:23:52,429 --> 00:23:54,389 bottom up motion is where you land. 407 00:23:54,389 --> 00:23:56,409 At least that's how I've encountered your tool. 408 00:23:56,409 --> 00:24:01,016 And I will say to your credit that it is pretty easy, to go through it. 409 00:24:01,036 --> 00:24:04,516 Maybe it's a good time to just, I'll describe to you my experience as a user 410 00:24:04,946 --> 00:24:06,646 of a tool like this, like what I did. 411 00:24:07,456 --> 00:24:11,183 Tell me if I'm wrong, but, you sign up, you go and you hit 412 00:24:11,183 --> 00:24:14,033 record, you do a thing like in CRM. 413 00:24:14,463 --> 00:24:15,413 Click, click, click, click, click. 414 00:24:15,443 --> 00:24:17,593 And it just captures those steps for you. 415 00:24:17,603 --> 00:24:21,773 Like screenshots, each one sort of automatically describes what you're doing. 416 00:24:22,123 --> 00:24:25,283 And then you can go through and beautify the descriptions and tweak them. 417 00:24:25,293 --> 00:24:27,789 But, that to me was the aha moment. 418 00:24:27,799 --> 00:24:30,009 It's like, Oh, it just sort of captured it all right there. 419 00:24:30,379 --> 00:24:35,529 And this kind of, magical way and created a, an experience for the user consuming 420 00:24:35,529 --> 00:24:40,209 that, that I think is objectively just much better a Google doc with screenshots 421 00:24:40,209 --> 00:24:42,589 or even like a loom, which I also really like, but a loom you have to like kind 422 00:24:42,589 --> 00:24:44,719 of hunt and search and start and stop. 423 00:24:45,039 --> 00:24:47,559 And this really does have it broken out in a very nice way. 424 00:24:47,559 --> 00:24:49,659 So is that the typical experience that your users are going 425 00:24:49,659 --> 00:24:50,549 through what I just described? 426 00:24:50,825 --> 00:24:52,065 Daniel Giovacchini: that's the typical experience. 427 00:24:52,104 --> 00:24:55,604 a hundred percent of our users go through that exact experience you just described. 428 00:24:55,634 --> 00:25:00,334 And, what we intentionally designed into that experience actually borrowed 429 00:25:00,334 --> 00:25:01,924 on a lot of game design principles. 430 00:25:02,214 --> 00:25:05,001 And we recently actually put out a little. 431 00:25:05,121 --> 00:25:11,408 piece about this, but there are specific mechanics built in to ensure that you as a 432 00:25:11,408 --> 00:25:14,348 user are going to get something of value. 433 00:25:15,283 --> 00:25:19,043 Within that, that 60 seconds and we're not going to let you go 434 00:25:19,143 --> 00:25:21,873 necessarily on side quests early on. 435 00:25:22,183 --> 00:25:26,303 So we're not actually going to give you power user features as you're going 436 00:25:26,303 --> 00:25:28,133 through and capturing your process. 437 00:25:28,153 --> 00:25:32,647 We're not going to let you edit it while you're in that recording session. 438 00:25:32,887 --> 00:25:37,346 We're not going to let you, turn on audio video and actually make a video out of it. 439 00:25:37,636 --> 00:25:40,656 It's very intently designed to get you to. 440 00:25:41,151 --> 00:25:46,651 A near finished state or an actually over 60 percent of cases, it's an already 441 00:25:46,701 --> 00:25:49,850 finished state, really without ever. 442 00:25:50,466 --> 00:25:54,444 Getting tempted to do anything other than, do your process with tango 443 00:25:54,444 --> 00:25:57,934 capturing it and then we're showing you the process you're capturing and 444 00:25:57,934 --> 00:26:01,444 we're sort of teaching you how the product works as you go through that. 445 00:26:01,444 --> 00:26:03,364 first capture experience. 446 00:26:03,394 --> 00:26:05,194 So, it's very intentional. 447 00:26:05,204 --> 00:26:08,720 We put every user basically through that capture journey. 448 00:26:08,955 --> 00:26:11,985 and they, at the end of it have something of value and they've 449 00:26:11,985 --> 00:26:13,385 learned how the product works. 450 00:26:13,668 --> 00:26:17,957 and that's part of what fueled our, bottoms up motion and why 451 00:26:17,957 --> 00:26:20,907 a lot of people refer to it as very intuitive and easy to use. 452 00:26:21,353 --> 00:26:25,423 Justin Norris: And the challenge I imagine, or I'm curious about is, so 453 00:26:25,423 --> 00:26:29,643 if I take my company, for example, like I said, we probably have one or two or 454 00:26:29,643 --> 00:26:35,433 a small handful of tangos in our, or whatever we have obviously underneath, 455 00:26:35,493 --> 00:26:40,443 under the free plan of what you offer, what's the moment of truth that is going 456 00:26:40,443 --> 00:26:45,673 to get a user to go from that stage to actually, we need to put up a credit card 457 00:26:45,943 --> 00:26:47,403 to get the value that we're looking for. 458 00:26:47,708 --> 00:26:48,018 Daniel Giovacchini: Yeah. 459 00:26:48,038 --> 00:26:48,568 Great question. 460 00:26:48,568 --> 00:26:53,043 So I mean, the first aha moment is, is getting you excited as a free user. 461 00:26:53,053 --> 00:26:56,035 It's, capturing your, first workflow on your own software. 462 00:26:56,405 --> 00:26:58,541 And, number one and sort of our. 463 00:26:58,721 --> 00:27:03,661 Activation journey, there's, sort of two separate paths we want you to go down. 464 00:27:03,691 --> 00:27:07,011 You know, if you're a smaller company, if you're a freelancer, you're an SMB, 465 00:27:07,447 --> 00:27:12,147 we potentially want you to, swipe your credit card and become a paid user. 466 00:27:12,267 --> 00:27:16,437 we strive that say, Hey, if you're a power user, you know, 10 percent 467 00:27:16,437 --> 00:27:21,237 of the free users in that market, we think should sort of, be paid users. 468 00:27:21,267 --> 00:27:29,472 And, the ones where we want that to be true are if you have needs around branding 469 00:27:29,832 --> 00:27:31,972 or if you have needs around security. 470 00:27:32,402 --> 00:27:36,772 And so we say, Hey, if you're using this in a power user fashion, it's 471 00:27:36,772 --> 00:27:38,392 likely that you're using Tango. 472 00:27:38,802 --> 00:27:41,606 To build, your own service or product, right. 473 00:27:41,646 --> 00:27:48,183 Or to like offer tango to a customer, or you are using it within. 474 00:27:48,728 --> 00:27:53,829 Your team in a way that, you really do need, more privacy or more branding. 475 00:27:54,309 --> 00:27:58,399 And if you're just otherwise using it, casually, or, it is more of a, a 476 00:27:58,399 --> 00:28:01,856 one off thing for you, then we want it to be free because we want you to 477 00:28:01,856 --> 00:28:05,813 share more tank creates more tangos, share them, and not feel inhibited. 478 00:28:06,223 --> 00:28:12,183 So privacy and branding are the two where we want you to pay as a 479 00:28:12,223 --> 00:28:15,582 SMB or, freelancer user of Tango. 480 00:28:16,012 --> 00:28:19,042 If you're within a larger company, we want to convert you on what's 481 00:28:19,052 --> 00:28:23,247 possible with your team and within a larger organization. 482 00:28:23,527 --> 00:28:24,867 Software training initiative. 483 00:28:24,877 --> 00:28:29,587 So if you're creating documentation, it's likely because there's some bigger 484 00:28:29,597 --> 00:28:30,857 effort happening at your company. 485 00:28:30,857 --> 00:28:35,367 You're either bringing on new hires, you're rolling out new software, you're 486 00:28:35,397 --> 00:28:37,077 doing a process improvement project. 487 00:28:37,217 --> 00:28:39,957 You're teaching reps, I mean, you know, you're in rev ops, you're teaching reps 488 00:28:39,957 --> 00:28:44,457 about how to use, some new functionality, some new field perhaps within the CRM. 489 00:28:44,717 --> 00:28:49,001 so we want to then convince you that, Hey, there's a really powerful. 490 00:28:49,331 --> 00:28:53,431 Team based experience here where, this is our, our newest offering. 491 00:28:53,461 --> 00:28:57,911 Actually, if you actually get your whole team on board, we're going to let you 492 00:28:58,281 --> 00:29:02,721 pin these updates and these processes right on top of the software that people 493 00:29:02,721 --> 00:29:04,571 are using, and it's no longer gonna. 494 00:29:04,966 --> 00:29:10,441 Be a link that you send them, in Slack or, living in an LMS or a knowledge base. 495 00:29:10,451 --> 00:29:13,769 So, you talked about, you guys use it as a free user. 496 00:29:14,099 --> 00:29:14,859 that's great. 497 00:29:14,889 --> 00:29:17,719 We want you to get excited about, what Tango can do. 498 00:29:18,039 --> 00:29:20,762 To potentially help here and there with, the process. 499 00:29:21,152 --> 00:29:24,712 at some point we would want you to be convinced that, Oh, Hey, we do 500 00:29:24,722 --> 00:29:28,912 have these larger software training initiatives and there's suddenly a 501 00:29:28,912 --> 00:29:31,652 powerful team based experience where we should talk to the Tango sales 502 00:29:31,652 --> 00:29:36,035 team about how we could set that up on top of our CRM or on top of our, core 503 00:29:36,035 --> 00:29:38,045 business software And benefit even more. 504 00:29:38,445 --> 00:29:41,045 Justin Norris: So let's pivot in a bit deeper into that product experience 505 00:29:41,065 --> 00:29:45,865 because that what you just described that overlay Wasn't something I'd seen 506 00:29:45,865 --> 00:29:49,225 before I saw it on your website just well prepping for this interview and 507 00:29:49,225 --> 00:29:54,576 I thought oh, that's really cool it's kind of like those like onboarding 508 00:29:54,586 --> 00:29:58,956 wizards that you get sometimes when you first sign up for a product But those 509 00:29:58,956 --> 00:30:02,053 are often very annoying because they constrict you a little bit and they you 510 00:30:02,053 --> 00:30:05,963 must feel like you're not Like they're mediating between you and the product. 511 00:30:06,403 --> 00:30:10,433 Whereas this, at least in the example that I watched, it was quite fluid. 512 00:30:10,433 --> 00:30:14,013 Like it's actually, just guiding you along through what you need to do. 513 00:30:14,553 --> 00:30:18,093 So maybe just talk about that and, what you've seen so far, perhaps 514 00:30:18,093 --> 00:30:20,983 in the market or what your vision is for how people would implement. 515 00:30:21,148 --> 00:30:22,218 Do 516 00:30:22,325 --> 00:30:22,945 Daniel Giovacchini: Yeah, totally. 517 00:30:22,945 --> 00:30:27,305 So we're big believers that for learning process or learning 518 00:30:27,305 --> 00:30:28,605 software, you should learn. 519 00:30:29,345 --> 00:30:33,903 While you're using it, you should learn, actually in, this case, the CRM, right? 520 00:30:33,913 --> 00:30:38,353 So the alternative, the status quo, you know, maybe what a lot of folks do 521 00:30:38,353 --> 00:30:43,035 today, which totally understandable, but what it is, is you're sending out 522 00:30:43,035 --> 00:30:48,345 a Slack update, you're jumping on top of a, team call and screen sharing a 523 00:30:48,345 --> 00:30:51,838 new process, or you're sending out a loom video to talk through something. 524 00:30:52,338 --> 00:30:53,788 And people are going to hear it. 525 00:30:54,152 --> 00:30:59,052 perhaps a couple of people who are particularly good with technology 526 00:30:59,052 --> 00:31:01,348 or savvy, we'll pick it up and there's going to be a lot of 527 00:31:01,348 --> 00:31:02,638 people who kind of just ignore it. 528 00:31:02,928 --> 00:31:06,498 They're going to forget, they're going to listen with one ear and they're not going 529 00:31:06,498 --> 00:31:10,458 to take the new tool or the new process and incorporate it into their workflow. 530 00:31:10,778 --> 00:31:12,028 what do we want instead? 531 00:31:12,358 --> 00:31:16,293 Well, we basically want that the first time you're going to go, you're going For 532 00:31:16,293 --> 00:31:21,860 example, you're creating a new deal in the CRM, a new opportunity, and, there's 533 00:31:21,860 --> 00:31:23,480 a new field that you need to fill out. 534 00:31:23,910 --> 00:31:29,663 We want you at that exact moment to, learn and, be more or less instructed that, 535 00:31:29,723 --> 00:31:31,273 Hey, this new field has been created. 536 00:31:31,483 --> 00:31:32,853 here's exactly how to use it. 537 00:31:32,923 --> 00:31:39,064 And, All you have to do is, and in our case, hover over this, tool tip or, have 538 00:31:39,064 --> 00:31:42,874 this, this process appear, you know, for the first time you're on one of those 539 00:31:42,884 --> 00:31:47,334 sub pages or page, we do a lot with kind of URL detection in our product. 540 00:31:47,574 --> 00:31:49,964 And that's when you're actually going to see it. 541 00:31:50,324 --> 00:31:54,544 And see, okay, well, I now know that this is exactly the new process 542 00:31:54,544 --> 00:31:58,644 update and you're far more likely to incorporate that into your routine, 543 00:31:58,894 --> 00:32:02,494 having learned it right in the moment that you need it or should be doing it. 544 00:32:02,774 --> 00:32:04,646 so that's the kind of fundamental. 545 00:32:05,096 --> 00:32:12,339 argument for, people learning software and process retention and compliance 546 00:32:12,339 --> 00:32:15,489 and adherence is going to be so much higher if it's right there when 547 00:32:15,489 --> 00:32:19,189 they need it versus, done separately and hope that somebody remembers. 548 00:32:19,454 --> 00:32:24,474 Justin Norris: you have any data, like a data point around, adoption is X percent 549 00:32:24,484 --> 00:32:28,494 higher or like how much more quickly someone could learn a process if they're 550 00:32:28,574 --> 00:32:33,184 doing it this way versus reading an article in a knowledge base or seeing 551 00:32:33,184 --> 00:32:36,424 a synchronous training like three weeks ago and then they go to do it and it's 552 00:32:36,424 --> 00:32:37,754 already been forgotten at that point. 553 00:32:38,014 --> 00:32:38,354 Daniel Giovacchini: Yep. 554 00:32:38,374 --> 00:32:40,824 So kind of the easiest thing to measure. 555 00:32:41,534 --> 00:32:48,298 Has been with kind of net new software rollouts and try and compare, either to 556 00:32:48,298 --> 00:32:52,568 a similar rollout at the company that did not use Tango or perhaps the same 557 00:32:52,568 --> 00:32:54,488 software rollout at a different company. 558 00:32:54,498 --> 00:32:57,798 And, I'll mention a case study that, that we just did to help illustrate, 559 00:32:57,808 --> 00:32:59,428 but it was a large workday rollout. 560 00:32:59,448 --> 00:33:04,715 So this is more HR software, less CRM, but, it's a 1500 person company 561 00:33:04,975 --> 00:33:08,599 and had to roll out workday and, teach everybody at the company. 562 00:33:08,599 --> 00:33:12,269 Okay, here's how you use workday to find your pay stubs, submit for 563 00:33:12,269 --> 00:33:16,169 PTO, uh, enroll in dental insurance, et cetera, et cetera, et cetera. 564 00:33:16,539 --> 00:33:21,649 And what they found, with Tango by putting the instructions kind of exactly on the 565 00:33:21,649 --> 00:33:27,423 screen where people needed them, that they saw a 90 percent reduction in internal I. 566 00:33:27,423 --> 00:33:28,013 T. 567 00:33:28,348 --> 00:33:32,978 Support ticket requests and basically going back to those owners 568 00:33:32,978 --> 00:33:36,728 of the software and asking for help or asking for clarification. 569 00:33:37,028 --> 00:33:39,778 so that's one way to measure it is sort of saying, hey, post rollout. 570 00:33:40,098 --> 00:33:43,718 in this case, it's helpful that it was HR software because it's stuff 571 00:33:43,788 --> 00:33:46,078 people had to do for employment. 572 00:33:46,233 --> 00:33:49,394 you know, in a CRM case, the danger is that you actually don't get asked 573 00:33:49,394 --> 00:33:50,814 those questions for support, right? 574 00:33:50,814 --> 00:33:52,654 You don't actually get people circling back. 575 00:33:52,654 --> 00:33:56,184 You just get people who ignore you and, you find out, you know, later 576 00:33:56,184 --> 00:33:57,424 on that they weren't doing it. 577 00:33:57,711 --> 00:33:59,231 but we, saw it sort of 90%. 578 00:33:59,456 --> 00:34:01,847 Reduction in support tickets with this customer. 579 00:34:02,187 --> 00:34:07,115 And, that basically goes to, prove that, when the information is, right there, you 580 00:34:07,115 --> 00:34:11,880 are that much more likely to, successfully incorporate that new information and, 581 00:34:11,880 --> 00:34:13,531 completing your, task or your process. 582 00:34:13,806 --> 00:34:17,367 Justin Norris: One of the things that I thought was novel was it seemed 583 00:34:17,367 --> 00:34:21,871 that there is some, kind of what, at least one of your AI features. 584 00:34:22,221 --> 00:34:25,851 And that there was some intelligence to allow for flexibility in the 585 00:34:25,851 --> 00:34:27,591 process that the user would carry out. 586 00:34:27,681 --> 00:34:30,041 Cause sometimes these things are rigid where it's like, you have to 587 00:34:30,041 --> 00:34:33,311 click on this and you have to click on this and it's like, click on a lead. 588 00:34:33,311 --> 00:34:34,331 Well, it could be many leads. 589 00:34:34,341 --> 00:34:35,710 It could be many different things. 590 00:34:36,308 --> 00:34:39,088 how did you solve for that problem of, having a structure, but creating 591 00:34:39,088 --> 00:34:40,378 flexibility at the same time, 592 00:34:40,777 --> 00:34:41,197 Daniel Giovacchini: Definitely. 593 00:34:41,197 --> 00:34:44,761 So, there's certainly complexity and how you configure process 594 00:34:44,761 --> 00:34:49,379 instruction based on, you take a CRM, for instance, you have parent. 595 00:34:49,379 --> 00:34:55,475 URL pages and you have, kind of children sub pages and we'll take a company record. 596 00:34:55,485 --> 00:34:59,755 And if you want process instruction to only show up for one specific company 597 00:34:59,925 --> 00:35:03,065 because they're very unique versus do you want process instruction to show 598 00:35:03,065 --> 00:35:06,885 up for every company and all of those sub pages and all those sub URLs. 599 00:35:07,225 --> 00:35:09,205 So that's one example where. 600 00:35:09,500 --> 00:35:13,560 that's a power user feature that we help people learn how to modify and create. 601 00:35:13,580 --> 00:35:16,920 And it's actually very easy and practice, but it is a complicated, 602 00:35:17,120 --> 00:35:21,146 nuanced part of the technology and part of the delivery of the products 603 00:35:21,161 --> 00:35:23,251 when you configure it right, it can be. 604 00:35:23,536 --> 00:35:27,086 much more powerful or you've also realized there's many more edge cases. 605 00:35:27,096 --> 00:35:30,714 So, this is why this experience, we actually work much more in a 606 00:35:30,714 --> 00:35:35,354 sales and success led fashion versus product led because figuring out 607 00:35:35,384 --> 00:35:36,964 something like that is difficult. 608 00:35:37,337 --> 00:35:41,992 but yeah, you essentially want to say, Hey, Ask yourself a few questions about 609 00:35:42,072 --> 00:35:43,942 either a process or enablement tip. 610 00:35:43,942 --> 00:35:48,752 Is this something I want everybody to globally see on every instance 611 00:35:48,782 --> 00:35:50,710 of, a page just like this? 612 00:35:51,000 --> 00:35:55,347 or is it something we, only want them to see uniquely on a specific page? 613 00:35:55,537 --> 00:35:56,627 So that's one question to ask. 614 00:35:56,867 --> 00:36:00,547 Another question to ask is, is this something we want people to see every time 615 00:36:00,547 --> 00:36:05,213 they come, or is this something we only want them to see one time, and it really 616 00:36:05,213 --> 00:36:07,853 is just like a, see it for the first time. 617 00:36:07,883 --> 00:36:09,273 And we don't want to show it again. 618 00:36:09,583 --> 00:36:16,246 so, those are usually the main kind of, okay, if we're gonna do real 619 00:36:16,246 --> 00:36:18,506 time enablement in the flow of work. 620 00:36:18,711 --> 00:36:22,401 those are the two main questions along with user groups and permissions. 621 00:36:22,551 --> 00:36:26,711 So do we want just new hires to see this or, you know, experienced team members, 622 00:36:26,711 --> 00:36:30,501 or we want just the sales team to see this versus just the success team. 623 00:36:30,759 --> 00:36:34,188 those are the main questions to ask and you're on your way to 624 00:36:34,428 --> 00:36:36,637 providing like curated enablement. 625 00:36:36,638 --> 00:36:37,268 So 626 00:36:37,372 --> 00:36:38,384 Justin Norris: then in terms of. 627 00:36:38,384 --> 00:36:42,818 The place of a tool like Tango within a bigger knowledge management ecosystem. 628 00:36:42,888 --> 00:36:46,996 So like I have a knowledge base, for instance, we use confluence, and 629 00:36:46,996 --> 00:36:48,656 that's very important for some things. 630 00:36:49,026 --> 00:36:53,326 And then we also like the company that I work for in my day job, we sell an LMS 631 00:36:53,946 --> 00:36:57,170 and mostly, targeting the L and D buyer. 632 00:36:57,195 --> 00:36:59,795 but some, similar overlapping use cases. 633 00:36:59,795 --> 00:37:02,535 And so that has another repository of knowledge. 634 00:37:03,145 --> 00:37:04,685 Do you aim to. 635 00:37:05,240 --> 00:37:09,246 eat all those things eventually subsume them in your broader vision 636 00:37:09,246 --> 00:37:12,996 of where you'll be in like five or 10 years or play alongside them. 637 00:37:13,386 --> 00:37:14,286 What will that look like? 638 00:37:14,719 --> 00:37:18,579 Daniel Giovacchini: knowledge bases and LMS is serve very important functions 639 00:37:18,614 --> 00:37:20,604 that aren't necessarily going to go away. 640 00:37:20,604 --> 00:37:20,654 Okay. 641 00:37:20,999 --> 00:37:25,799 and that's really that general information about, what is our industry, what is 642 00:37:25,799 --> 00:37:29,263 our product, who are our competitors, of this information that you would 643 00:37:29,263 --> 00:37:34,581 need as context and background to be successful at then, you know, using 644 00:37:34,581 --> 00:37:36,671 your tools and completing processes. 645 00:37:36,671 --> 00:37:40,114 So, that's very much, still critical and important. 646 00:37:40,164 --> 00:37:41,504 What we would argue is that. 647 00:37:41,769 --> 00:37:45,776 You should not be teaching how to use software, how, to complete 648 00:37:45,776 --> 00:37:50,246 tasks, how to go about process from within a knowledge base or an LMS. 649 00:37:50,336 --> 00:37:53,686 And if you want to reference it there, that's great. 650 00:37:53,896 --> 00:38:00,770 So we very much believe in deep linking process, instruction, deep linking. 651 00:38:01,115 --> 00:38:07,105 tango workflows or folders, from within knowledge bases or LMS is, and you 652 00:38:07,105 --> 00:38:11,645 can then go learn in the tools, and actually experience the process through 653 00:38:11,645 --> 00:38:16,611 the tools instead of, within a scorn file or something, embedded in LMS or 654 00:38:16,731 --> 00:38:22,989 knowledge base, So that to us, makes a lot of sense, to reinforce tool based 655 00:38:22,989 --> 00:38:26,889 learning systems, learning in there, but actually trying to teach through a 656 00:38:26,889 --> 00:38:30,759 PowerPoint or, put a video inside the knowledge base, you expect people to 657 00:38:30,759 --> 00:38:34,974 watch and memorize that's actually what we would expect to completely go away. 658 00:38:35,424 --> 00:38:39,108 Justin Norris: And do you see yourself again, thinking about your product 659 00:38:39,108 --> 00:38:42,714 vision, could you ever be a complete knowledge management solution, and 660 00:38:42,714 --> 00:38:45,654 have like your knowledge base, or do you always imagine yourself partnering 661 00:38:45,664 --> 00:38:49,764 alongside other vendors like that in the knowledge management stack? 662 00:38:50,222 --> 00:38:53,173 Daniel Giovacchini: I think and this is very much a, partnership 663 00:38:53,193 --> 00:38:55,473 driven, vision, I believe. 664 00:38:55,513 --> 00:39:00,463 So if we do say, Hey, there's many types of knowledge, 665 00:39:00,813 --> 00:39:02,243 there's many types of learning. 666 00:39:02,773 --> 00:39:07,463 Some tools are going to be much more specific and well suited for, this type. 667 00:39:07,483 --> 00:39:09,543 And some are going to be more suited for that type. 668 00:39:10,313 --> 00:39:11,693 the question for. 669 00:39:11,693 --> 00:39:15,583 real time enablement for what Tango is trying to do and help, you know, it really 670 00:39:15,583 --> 00:39:17,473 is a kind of like co pilot vision, right. 671 00:39:17,473 --> 00:39:21,423 Of how people, while they work, while they're doing, can we partner with other 672 00:39:21,423 --> 00:39:26,438 tools to surface their information in the flow of work when that's relevant? 673 00:39:26,918 --> 00:39:28,828 And, bi directionally. 674 00:39:29,468 --> 00:39:33,578 For LMSs, for example, you're always going to have cohort based onboarding. 675 00:39:33,588 --> 00:39:37,168 You're always going to have crops of new hires starting, and they're going 676 00:39:37,168 --> 00:39:42,328 to need, some hand holding in their first number of weeks that's probably 677 00:39:42,328 --> 00:39:44,448 always best delivered, through an LMS. 678 00:39:44,488 --> 00:39:48,958 And, so there's their bi directional, um, instruction then where stuff 679 00:39:48,958 --> 00:39:53,398 that might live in software and tools can also be, served through the LMS. 680 00:39:53,648 --> 00:39:57,608 it's all about, I think, designing the best upfront learning experience and 681 00:39:57,608 --> 00:40:01,578 the best sort of knowledge management, serving knowledge when people need it. 682 00:40:01,828 --> 00:40:05,570 And that's likely going to be through a combination of tools. 683 00:40:06,535 --> 00:40:07,555 Justin Norris: Makes perfect sense. 684 00:40:08,905 --> 00:40:14,005 I want to pivot to you for a second and like your role in the org. 685 00:40:14,385 --> 00:40:18,539 You're the COO, which, like all operations, jobs, it can mean 686 00:40:18,539 --> 00:40:19,919 many different things I find. 687 00:40:20,359 --> 00:40:24,459 So I'm curious about you see your role, your place within the org, the 688 00:40:24,459 --> 00:40:26,519 sorts of responsibilities you have. 689 00:40:27,051 --> 00:40:28,601 Daniel Giovacchini: if you actually go back and look at, you know, 690 00:40:28,761 --> 00:40:31,001 Fundamentally, what is operations? 691 00:40:31,071 --> 00:40:38,611 It is helping your company deliver and support your product 692 00:40:38,611 --> 00:40:40,411 or service offering, right? 693 00:40:40,451 --> 00:40:43,451 And be most efficient as possible in doing that. 694 00:40:43,791 --> 00:40:48,221 So operations to me is really everything outside of. 695 00:40:48,841 --> 00:40:52,971 Core product development or like core service delivery. 696 00:40:53,401 --> 00:40:57,721 And then if you think back office operations about how does our company 697 00:40:57,981 --> 00:41:02,351 be efficient to then ultimately deliver this product or service. 698 00:41:02,601 --> 00:41:05,911 And then you think about, and especially the last, 10, 15 years, right? 699 00:41:05,911 --> 00:41:10,271 Like rev ops is the fastest growing job and certain 2023 700 00:41:10,271 --> 00:41:11,921 reports, according to Forbes. 701 00:41:12,151 --> 00:41:15,121 a lot of these other, function specific operations. 702 00:41:15,131 --> 00:41:15,151 Yeah. 703 00:41:15,631 --> 00:41:20,125 groups are really about, okay, how do we make, their efforts more efficient? 704 00:41:20,172 --> 00:41:24,885 so as, we're fast growing, kind of early stage company by all means. 705 00:41:25,115 --> 00:41:26,325 but what does that mean? 706 00:41:26,335 --> 00:41:27,825 It's, it's how do we. 707 00:41:29,055 --> 00:41:33,966 Most efficiently operationalized around bringing, our core products, to market. 708 00:41:33,996 --> 00:41:38,489 And so that's, a little bit of back office, in the early days is 709 00:41:38,489 --> 00:41:42,635 overseeing some of that function, but also very much sales marketing. 710 00:41:43,090 --> 00:41:47,695 Support, success and, the enablement of those really customer 711 00:41:47,695 --> 00:41:49,385 facing people on those teams. 712 00:41:49,545 --> 00:41:53,922 How do we set up structures and make sure all these, groups and functions are 713 00:41:54,162 --> 00:41:57,812 speaking the same language, drawing on the same philosophy as they make their 714 00:41:57,812 --> 00:42:00,282 decisions and as fluid away as possible. 715 00:42:00,282 --> 00:42:03,082 And it's chaotic early on. 716 00:42:03,116 --> 00:42:06,816 but certainly as you hit milestones, you get more certainty and you 717 00:42:06,816 --> 00:42:11,065 build more foundation in different areas and you're able to get more 718 00:42:11,085 --> 00:42:12,415 precise and more prescriptive. 719 00:42:12,777 --> 00:42:17,156 Justin Norris: As a COO, there's a pretty broad scope of activities 720 00:42:17,156 --> 00:42:19,126 that fall under your purview. 721 00:42:19,676 --> 00:42:23,796 And as a consequence of that, there are like a million things that 722 00:42:23,796 --> 00:42:27,846 you could be thinking about or doing at any given point in time. 723 00:42:28,366 --> 00:42:31,446 And I'm really interested in the problem of prioritization 724 00:42:31,456 --> 00:42:32,936 in a situation like that. 725 00:42:32,946 --> 00:42:36,136 Because I think that's something that many operators can relate to at any level. 726 00:42:36,546 --> 00:42:38,706 So I'm curious, How do you making those decisions day to day? 727 00:42:38,706 --> 00:42:41,736 Like I need to move this company forward relatively early stage. 728 00:42:41,736 --> 00:42:43,066 As you said, it's chaotic. 729 00:42:43,646 --> 00:42:44,826 What am I going to do today? 730 00:42:44,906 --> 00:42:46,836 It's a hard question to answer sometimes. 731 00:42:47,408 --> 00:42:49,988 Daniel Giovacchini: It's the ultimate question to answer. 732 00:42:50,651 --> 00:42:55,451 starts with working backwards from where are we in our product market fit 733 00:42:55,451 --> 00:42:57,783 journey when you're in early stages. 734 00:42:57,813 --> 00:43:00,893 And if you're an early stage company, whether your product or 735 00:43:00,893 --> 00:43:02,613 service, you're, you're racing to. 736 00:43:02,786 --> 00:43:07,346 best version of product market fit that you can, optimally achieve within, 737 00:43:07,346 --> 00:43:11,945 your timeframe and, working backwards from that, that helps you prioritize. 738 00:43:11,955 --> 00:43:16,806 So in certain weeks, it's, we're not learning fast enough, right? 739 00:43:16,846 --> 00:43:20,336 Or like we are not the feedback loop. 740 00:43:20,646 --> 00:43:26,484 Between sales and marketing is not strong enough to the point where we're putting 741 00:43:26,484 --> 00:43:31,564 out effective messaging or positioning because we're not understanding, you know, 742 00:43:31,574 --> 00:43:33,504 what's actually happening on, sales calls. 743 00:43:33,684 --> 00:43:37,494 And so that's like, okay, crap, we have to use call recording technology better. 744 00:43:37,494 --> 00:43:39,354 We have to set up a different meeting structure and a meeting 745 00:43:39,364 --> 00:43:40,934 cadence to achieve that. 746 00:43:41,234 --> 00:43:42,704 But it all comes from like, okay. 747 00:43:43,034 --> 00:43:45,654 You know, we're not learning fast enough to help us get to product market fit. 748 00:43:45,682 --> 00:43:47,702 or it could be like, Hey, we're not having the right conversations. 749 00:43:47,702 --> 00:43:52,942 And so, we really have to go look at what we're doing from a marketing perspective. 750 00:43:53,059 --> 00:43:56,689 so once you're kind of in the sort of more post product market fit 751 00:43:56,689 --> 00:44:01,303 phase, I think the North star then is, you have your, six, 12 months. 752 00:44:01,363 --> 00:44:01,743 Okay. 753 00:44:01,743 --> 00:44:03,103 Ours or strategy. 754 00:44:03,133 --> 00:44:07,030 That's kind of the timeframe, that feel like is, more in vogue now for all 755 00:44:07,030 --> 00:44:11,020 stage companies is three months is, too little more than a year is, too much. 756 00:44:11,260 --> 00:44:14,777 but you have your company level priorities and, um, what's going 757 00:44:14,777 --> 00:44:16,249 to help you hit those the fastest. 758 00:44:16,249 --> 00:44:22,389 and so going and finding, being maniacal about removing friction or blockers 759 00:44:22,389 --> 00:44:26,089 or organizational, lethargy, right? 760 00:44:26,089 --> 00:44:28,149 How do you go find that stuff and, blow through it? 761 00:44:28,180 --> 00:44:32,209 that's kind of the, next prioritization function in my mind. 762 00:44:32,237 --> 00:44:36,917 And the last thing I'll mention is you do need a longterm mindset, right? 763 00:44:36,937 --> 00:44:39,599 So one of our values actually is, this, leave it better. 764 00:44:40,013 --> 00:44:42,933 and we highlight people, within the company, within the team 765 00:44:43,493 --> 00:44:45,497 every month, and, it's basically. 766 00:44:45,972 --> 00:44:51,759 who is making sure that as we build and as we stand up, new process or new 767 00:44:51,759 --> 00:44:55,909 functionality or a new go to market motion for the first time, who's thinking 768 00:44:55,909 --> 00:44:59,953 about the systems mindset, who's thinking longterm, that we're making decisions and 769 00:44:59,953 --> 00:45:01,523 we're implementing things in such a way. 770 00:45:01,748 --> 00:45:05,668 That, they're going to endure and we're not just cutting corners and 771 00:45:05,678 --> 00:45:07,964 hastily, saying we completed tasks. 772 00:45:07,974 --> 00:45:10,001 So, that to me is more a mindset. 773 00:45:10,001 --> 00:45:13,253 That's a culture of values thing you need to build harder to work 774 00:45:13,253 --> 00:45:15,003 into a prioritization structure. 775 00:45:15,163 --> 00:45:17,633 So we think about that one from a values perspective, 776 00:45:17,934 --> 00:45:20,464 Justin Norris: Really appreciate you coming on, sharing a bit about 777 00:45:20,464 --> 00:45:23,644 your journey and about how you're thinking about this problem. 778 00:45:24,186 --> 00:45:27,755 it's certainly, as I mentioned to you earlier, like I just nerd out about 779 00:45:27,755 --> 00:45:32,685 this stuff, because it's so hard and I think so annoying when it doesn't work. 780 00:45:33,115 --> 00:45:35,427 it's really cool, to find some ways to make it work better. 781 00:45:35,427 --> 00:45:37,337 So big fan of what you folks are doing. 782 00:45:37,337 --> 00:45:39,356 We'll include a link in the show notes for, anyone. 783 00:45:39,811 --> 00:45:43,071 listening, who wants to check you out and yeah, thanks for 784 00:45:43,071 --> 00:45:44,011 spending some time with me. 785 00:45:44,349 --> 00:45:46,530 Daniel Giovacchini: of course, love having the conversation and, uh, love 786 00:45:46,530 --> 00:45:48,009 learning from you and the other guests as 787 00:45:48,009 --> 00:45:48,239 well. 788 00:45:48,529 --> 00:45:48,889 Justin Norris: Cheers.