Vollständiges Transkript von AI Failures in Construction for Business Leaders to Fix Workflow Gaps with Connor and Hugh

the end. 04:10.030 --> 04:11.513 [SPEAKER_02]: So there's going to be some marketing hype. 04:11.553 --> 04:15.161 [SPEAKER_02]: And that's why, you know, I think what's interesting here is that you brought Connor with you. 04:15.201 --> 04:22.457 [SPEAKER_02]: So Connor talk a little bit about the end to the Yang with you and what you're up to it at quantum rise and a little bit about yourself. 04:22.505 --> 04:23.486 [SPEAKER_00]: Yeah, absolutely. 04:23.587 --> 04:29.855 [SPEAKER_00]: So we work with a ton of construction clients that we work from general contractors, asphalt paid in subcontractors, et cetera. 04:30.256 --> 04:33.200 [SPEAKER_00]: And as you said, these clients come to us and say, we want to do AI. 04:33.520 --> 04:37.346 [SPEAKER_00]: But there's clients all over the place on where they are in their AI journey. 04:37.366 --> 04:42.353 [SPEAKER_00]: You've got people that have started experiment with POCs or get cuts stuck in POC mode. 04:42.753 --> 04:45.117 [SPEAKER_00]: They don't know where to start or can't even spell AI. 04:45.137 --> 04:48.922 [SPEAKER_00]: So it's a lot of education, just instilling the fundamentals in these organizations. 04:48.982 --> 04:50.284 [SPEAKER_00]: So these teams from 04:50.264 --> 05:10.602 [SPEAKER_00]: the back office, project management, core operations, just understand the basics of how to use some of these tools, whether it's copilot, chat, GPT, Gemini, or other AI tools, and then really helping them understand their processes deeply, their data, their systems, and how we can actually make this a reality for them, because a lot of the clients will think that AI is just a magic one. 05:10.622 --> 05:20.271 [SPEAKER_00]: It's going to solve all their problems, but it's only going to work if it's purpose fit 05:20.251 --> 05:36.336 [SPEAKER_02]: minimal disruption is possible in the work flows because otherwise you're going to have a change management nightmare down the road so keeping those those users in the loop so you're using some of those now I know I brought you using some of those sexy words like proof of concept change management not really that's not what the high folks like to hear 05:36.316 --> 05:41.124 [SPEAKER_02]: that it's hard to do, and it takes time, and maybe even some POC. 05:41.465 --> 05:42.887 [SPEAKER_02]: How did you get here, though, Connor? 05:42.907 --> 05:46.273 [SPEAKER_02]: Because you know, everybody listening in likes to know a little more about our folks. 05:46.293 --> 05:47.775 [SPEAKER_02]: So what's your history like? 05:47.795 --> 05:52.603 [SPEAKER_02]: Because you're running the sort of the vertical obstruction over there, but how did you get here? 05:52.583 --> 06:08.063 [SPEAKER_00]: Yeah, so I've spent most of my career in the consulting, technology, digital transformation world started my career at KPMG and of doing off to the CFO work, everything from large scale ERP implementations, some RPA work, operating all designed to help back in the

day. 06:08.123 --> 06:12.128 [SPEAKER_00]: So labor arbitrage moving companies, operations to share services and centers. 06:12.108 --> 06:16.552 [SPEAKER_00]: From there, worked for a FinTech startup and brought me to Quaramrise. 06:16.572 --> 06:17.453 [SPEAKER_00]: I'm just a problem solver. 06:17.493 --> 06:22.097 [SPEAKER_00]: So I like getting deep, really understanding the clients, problems of processes, getting their trust early. 06:22.137 --> 06:27.542 [SPEAKER_00]: So because if you're just coming at them with outside ideas, with no understanding of the business, they're never going to want to work with you. 06:27.582 --> 06:33.888 [SPEAKER_00]: So really becoming kind of one with the client to integrate yourself within their operations and understand what's going on. 06:33.908 --> 06:42.115 [SPEAKER_00]: So we can make the right recommendations, but then move those recommendations into real outcomes down the road and help them implement or build these solutions that are solved in the right problems for them. 06:42.095 --> 06:58.416 [SPEAKER_02]: Yeah, I mean, you said this pre-call, you know, I get it, you know, Connor's got to cash the text that you write over there on what you guys can do and how it can help companies because I think, you know, in your journey here, that's what you've spent the last couple of years, especially just 06:58.396 --> 07:07.426 [SPEAKER_02]: I'd say, you know, learning and educating like it's a strange moment right where you're you're learning and educating at the same time and identifying the problem. 07:07.486 --> 07:13.333 [SPEAKER_02]: So talk a little bit about, you know, last couple of years of this process and sort of what drove you here. 07:13.573 --> 07:16.456 [SPEAKER_02]: Where are you on the correct problem set? 07:16.677 --> 07:22.463 [SPEAKER_01]: That's a great point and, you know, one of the things that kind of brought up that I'll kind of tease out is, you know, 07:22.882 --> 07:30.031 [SPEAKER_01]: We're finding, not surprisingly, that AI implementations are more about the non-AI part than they are about the building. 07:30.631 --> 07:44.869 [SPEAKER_01]: You spend 80% of the time, I don't know if that's quite right, but you spend a lot of time getting in and understanding what people actually do and where they want to go and how do you get from where they are now with what they currently have to where they want to be. 07:44.969 --> 07:49.935 [SPEAKER_01]: And I think to answer your question about how the past couple years have gotten me here, 07:49.915 --> 07:58.146 [SPEAKER_01]: I've been doing things with AI for a decade now, and it kind of went quiet because it became normal software, and that's interesting because I think it'll happen again. 07:58.186 --> 08:01.150 [SPEAKER_01]: Somebody smart said, we call it AI when it doesn't work. 08:01.591 --> 08:14.609 [SPEAKER_01]: I think that's a bit of an over-claim, but the point is it's all, you know, the educating while learning is because it's changing so fast, and if anything, the last quarter has been remarkable and how busy it's been in terms of new things and new changes. 08:14.669 --> 08:16.311 [SPEAKER_01]: Even the last two weeks, 08:16.291 --> 08:26.187 [SPEAKER_01]: What Claude Code has shown itself to be able to do, it's been around a little longer than that, but you're starting to hear some pretty interesting comments about how this is just different from what was there before. 08:26.207 --> 08:28.390 [SPEAKER_01]: And this isn't the last time you're going to hear that. 08:28.510 --> 08:33.578 [SPEAKER_01]: So there isn't a body of knowledge that you can study up on and then off you go and teach people. 08:33.638 --> 08:34.620 [SPEAKER_01]: You have to be 08:34.600 --> 08:41.426 [SPEAKER_01]: really paying attention to what's going on now and asking yourself what it means and building things yourself and trying to do things and so on and so forth. 08:41.466 --> 08:47.191 [SPEAKER_01]: So we're at a place now where it's good enough that you can do real things, you can get through reliable things. 08:47.632 --> 08:50.354 [SPEAKER_01]: But to do that, you need to understand the problem really well. 08:50.394 --> 08:59.182 [SPEAKER_01]: And again, that's where someone like Connor comes in to spend a lot of time listening and a lot of humility to say, we don't have a hammer and we're going to go find the nails. 08:59.402 --> 09:02.625 [SPEAKER_01]: It's what are you doing and let's spend a lot of time on that. 09:02.905 --> 09:04.607 [SPEAKER_01]: It's the difference between 09:04.587 --> 09:22.170 [SPEAKER_01]: Where, you know, you see some folks out there who maybe have a team overseas and they'll build some stuff for you and that's wonderful But maybe they build a thing you don't need or maybe they build a thing that doesn't quite work or they build a thing that no one's ever gonna use Getting all that right to make sure it's a priority, make sure it fits with what you're doing now That's the key thing for AI now. 09:22.310 --> 09:24.233 [SPEAKER_01]: We're past the part where 09:24.213 --> 09:50.288 [SPEAKER_01]: It's, you know, cool custom GPTs, that may be a solution for the point is we're past cute little magic tricks and now it's it's industrializing so at CES this year we really saw that that it's industrializing in a way that it just hadn't been before it was actually kind of Nvidia's show where they talked a lot about this being another another kind of stage where we spent last year realizing we needed to do a lot more tooling to make things work. 09:50.268 --> 09:54.335 [SPEAKER_01]: That's not in the rear view, but it's pretty established how to do some of that stuff. 09:54.756 --> 09:57.661 [SPEAKER_01]: So now we have to make it so that it's a lot cheaper to use. 09:58.041 --> 10:00.926 [SPEAKER_01]: It's a lot more reliable in kind of every part of the stack. 10:01.387 --> 10:02.749 [SPEAKER_01]: And this year there's going to be more of that.

10:02.769 --> 10:08.399 [SPEAKER_01]: There's going to be more real things being done because we've we've passed some of the early uncanny valley points. 10:08.920 --> 10:10.943 [SPEAKER_01]: And now we're ready to actually do stuff. 10:10.923 --> 10:20.601 [SPEAKER_02]: Yeah, and I kind of want to double down on that because I've been saying that for a while and I've said it with a few other things with the easy analogy is like We don't talk about our cars as diesel engine. 10:20.621 --> 10:22.224 [SPEAKER_02]: You don't talk about it as a gas engine. 10:22.244 --> 10:23.386 [SPEAKER_02]: You just call it a car, right? 10:23.707 --> 10:24.228 [SPEAKER_02]: It's a thing. 10:24.268 --> 10:26.011 [SPEAKER_02]: You don't think about the thing that runs it. 10:26.452 --> 10:29.337 [SPEAKER_02]: You know, you put gas in it, but it's not a gas 10:29.317 --> 10:31.280 [SPEAKER_02]: power, you know, definitely you talk about it. 10:31.360 --> 10:39.494 [SPEAKER_02]: That's when AI gets to that point where you're just using x, y, or z, then it's we've reached that moment and that's an important moment. 10:39.875 --> 10:54.379 [SPEAKER_02]: But I really want to to double down and talk to Connor about this part because the biggest failures that I've seen and the biggest problem through this art that I've seen is organizations feeling that 10:54.359 --> 10:56.143 [SPEAKER_02]: And we want to do AI. 10:56.183 --> 11:00.592 [SPEAKER_02]: And they gather a very expensive team together. 11:00.632 --> 11:06.424 [SPEAKER_02]: And they solve for a problem that just doesn't have the return. 11:06.524 --> 11:08.007 [SPEAKER_02]: You're like, why did you solve that? 11:08.047 --> 11:09.550 [SPEAKER_02]: Well, because we could. 11:09.749 --> 11:38.743 [SPEAKER_02]: Okay, I could solve a lot of problems, but should I that that so Connor I want to I want to hear from you because I by the way to the listeners out there this is not just in construction like I've heard it in construction quite a few times, but I have a preview outside and I've seen it in other large organizations I've you know had people pull me aside and say wow my company's doing this and we're trying to automate an AP process that takes me five minutes. 11:39.095 --> 11:42.364 [SPEAKER_02]: And really, there's all this stuff, there's stuff like I didn't need it. 11:42.384 --> 11:44.068 [SPEAKER_02]: And it doesn't work all the time. 11:44.088 --> 11:50.025 [SPEAKER_02]: So talk to me about Furma construction perspective, you know, what are some of the big misses? 11:50.285 --> 11:54.657 [SPEAKER_02]: And then how are you resetting people to go down this process with you? 11:54.687 --> 12:19.243 [SPEAKER_00]: As you hit on, there's so many companies out there that think they're behind, some might be, some might not be because there's so many organizations that are in the same spot of just starting to toy around with some of these, but again, to your point, they don't know where to start, and they just latch on to a problem and go try and solve it and, oh, well, it failed, it didn't realize the value, the users didn't like it, and then people get they get pissed off, the organizations a little averse to change. 12:19.223 --> 12:25.429 [SPEAKER_00]: So where we typically start with this is we do what we call rapid AI breakthrough assessment. 12:25.649 --> 12:32.256 [SPEAKER_00]: And it's you kind of said it's it's not just an AI strategy it turns into a business strategy. 12:32.756 --> 12:38.762 [SPEAKER_00]: We sometimes don't even talk about AI solutions until week two of these products that we do with these clients. 12:38.782 --> 12:43.187 [SPEAKER_00]: So we start casting a pretty wide nut understanding okay from a business perspective. 12:43.207 --> 12:46.750 [SPEAKER_00]: What are your top 10 top 20 problems that you're trying to solve or 12:46.898 --> 12:50.626 [SPEAKER_00]: metrics or KPIs that are lagging, that could be an AP process. 12:50.646 --> 12:53.412 [SPEAKER_00]: It could be an Estabating issue, it could be a scheduling issue. 12:53.452 --> 12:56.258 [SPEAKER_00]: It could just be, you got a bunch of turn across the organization. 12:56.298 --> 12:57.741 [SPEAKER_00]: We don't know why our employees are turning. 12:57.782 --> 13:00.147 [SPEAKER_00]: So it's not just construction field operations. 13:00.187 --> 13:02.011 [SPEAKER_00]: It's just core-back-off operations, too. 13:02.111 --> 13:02.612 [SPEAKER_00]: So. 13:02.592 --> 13:24.550 [SPEAKER_00]: Once we typically gather a ton of not a ton but leaders across the organization so we can speak the common language and it's not just a mandate from the CEO or the board of directors so then everybody feels like they're part of this process and kind of co-shapian and co-building this the strategy where we want to attack and then once we understand those important KPIs or business outcomes at those. 13:24.530 --> 13:32.961 [SPEAKER_00]: our clients are trying to improve that's when we would all it down to start to go deep with the client stakeholder subject matter experts, the people who are actually doing the work. 13:33.041 --> 13:45.357 [SPEAKER_00]: So getting deep and understanding the processes, the systems, where things fail, where there's a kind of a gut decision or maybe we can't trust the data and then work backwards from there to figure out what that best fit solution is for them. 13:46.079 --> 14:12.711 [SPEAKER_02]: I then we build it and then you build it right yeah, and then we build it But that's and that's the that's the magic sauce, but the what I like there is you hit two huge things The gut I've said this from the beginning and and you really I'm like I want to take us back into like a time machine Because you said it you like pre internet and then the internet I like to use the SaaS kind of rise of SaaS because I was so ingrained in that and I went through it 14:12.691 --> 14:14.754 [SPEAKER_02]: where it was the same thing. 14:14.774 --> 14:16.317

[SPEAKER_02]: It's like, there's fundamentals. 14:16.337 --> 14:20.123 [SPEAKER_02]: Understand the problems, understand the systems, understand what's happening. 14:20.224 --> 14:25.973 [SPEAKER_02]: Like, really look for what are we looking for as an organization and then dig on where are the problems? 14:25.993 --> 14:27.696 [SPEAKER_02]: And then none of that is fun. 14:27.897 --> 14:33.586 [SPEAKER_02]: And really none of that has changed right at all in the process of understanding. 14:33.846 --> 14:37.753 [SPEAKER_02]: The tools you're looking at, the things you're dealing with, they're much more advanced now. 14:37.936 --> 14:47.170 [SPEAKER_02]: You know, the way we build is more sure all that's changed, but the fundamentals are still true in understanding and finding those problems and then finding those things that would make sense. 14:47.774 --> 14:49.737 [SPEAKER_02]: in going slow to then figure it out. 14:49.797 --> 14:54.543 [SPEAKER_02]: Now, what we're going to be capable of doing in future with this new technology? 14:54.563 --> 14:59.009 [SPEAKER_02]: Well, I would say that's very powerfully different and game changing. 14:59.390 --> 15:00.151 [SPEAKER_02]: Don't disagree. 15:00.892 --> 15:03.435 [SPEAKER_02]: Just believe fundamentals don't go away. 15:03.475 --> 15:08.702 [SPEAKER_02]: I love that because, you know, one of the places I said in the beginning for analytics. 15:08.682 --> 15:10.625 [SPEAKER_02]: Was you want to know where you need analytics? 15:10.645 --> 15:11.828 [SPEAKER_02]: You want to know where you need data? 15:12.509 --> 15:20.443 [SPEAKER_02]: That is when you're sitting in a room and someone says, I feel like my history here is no. 15:20.463 --> 15:21.364 [SPEAKER_02]: Uh-uh. 15:21.384 --> 15:22.867 [SPEAKER_02]: I feel my gut. 15:22.947 --> 15:24.570 [SPEAKER_02]: They're bad influencers. 15:24.931 --> 15:28.697 [SPEAKER_02]: They're really bad because we're real positive people or we're real negative people. 15:28.738 --> 15:30.360 [SPEAKER_02]: But we go on the spectrum. 15:30.380 --> 15:32.985 [SPEAKER_02]: So I love that you hit the gut. 15:32.965 --> 15:51.430 [SPEAKER_02]: I love that you hit the I'm sure it's where manual entry and stuff is happening right there's the opportunity so and I know I cut you off there you but I wanted to make sure people understood that like you're not the fundamentals are still true it's just the tool sets that we now have available it I mean. 15:51.629 --> 15:57.735 [SPEAKER_02]: You used to use a hammer when you're putting, now I'm watching somebody put in a roof across me, so I'm gonna use this. 15:57.755 --> 16:00.858 [SPEAKER_02]: You used a hammer, you know, a hammer all of that in the nails. 16:01.438 --> 16:06.163 [SPEAKER_02]: That guy's got an impact drill up there or drill, nail gun, I'm watching him. 16:06.643 --> 16:11.368 [SPEAKER_02]: What he's doing didn't change the tool that he's using didn't, he's way faster, I can see it. 16:11.588 --> 16:21.197 [SPEAKER_02]: So talk a little bit about that to you because I think that's important to understand like a fundamentals of true, what Connor and his team 16:21.177 --> 16:26.884 [SPEAKER_02]: What are you seeing as transformational and what are you seeing like the future be able to look like? 16:27.505 --> 16:33.452 [SPEAKER_01]: Going back to in video again, I'm going to quote Jensen Juan, he's been talking, I really like this framework. 16:33.472 --> 16:35.314 [SPEAKER_01]: The difference between a purpose and a task. 16:35.935 --> 16:46.408 [SPEAKER_01]: And I think what you're starting to see is people realize exactly what you just said that AI is tool that will help you to achieve your purpose, often by automating little tasks that are in there. 16:46.388 --> 16:51.417 [SPEAKER_01]: So I think you're starting to see people go past the, you know, the height phase. 16:51.437 --> 16:53.520 [SPEAKER_01]: There's going to be plenty of hype that LinkedIn apparently. 16:53.540 --> 16:54.442 [SPEAKER_01]: That's all it does now. 16:54.983 --> 17:00.672 [SPEAKER_01]: And if anything, people should just recognize that what you're seeing on, especially LinkedIn, but really in a lot of places. 17:01.193 --> 17:02.656 [SPEAKER_01]: It's just people trying to make hot takes. 17:02.736 --> 17:03.617 [SPEAKER_01]: It's not real. 17:03.918 --> 17:05.781 [SPEAKER_01]: You know, there's real work being done. 17:05.761 --> 17:09.247 [SPEAKER_02]: So except the content crews, you know, linked in, am I linked in? 17:09.267 --> 17:14.216 [SPEAKER_01]: Obviously, obviously, everything I put up there is completely legit. 17:14.296 --> 17:22.470 [SPEAKER_01]: But honestly, they're just starting to shift the way it should, which is we're starting to get serious about this and really think about 17:22.450 --> 17:26.714 [SPEAKER_01]: We're not replacing the entire what a person does and what their purpose is. 17:26.734 --> 17:31.458 [SPEAKER_01]: We're saying you could get to what you're really there for a lot faster because you're not messing around. 17:31.798 --> 17:33.620 [SPEAKER_01]: You're not second guessing day to the same way. 17:33.640 --> 17:35.322 [SPEAKER_01]: You're not hunting for things. 17:35.382 --> 17:38.665 [SPEAKER_01]: You're not unsure about something because you can look it up so quickly. 17:39.025 --> 17:40.026 [SPEAKER_01]: But we are still early. 17:40.166 --> 17:42.288 [SPEAKER_01]: It's worth keeping in mind that we are still early. 17:42.328 --> 17:44.810 [SPEAKER_01]: There's a lot of innovation that will be ahead of us. 17:45.291 --> 17:52.457 [SPEAKER_01]: One of the things that we spent a lot of time trying to reap both reassure people, but also in how we engineer things is to say, 17:52.437 --> 18:01.168 [SPEAKER_01]: that whatever we put in now, there's going to be things that slot in later that might make it work even better, whether it's a different model, usually it'll be a different model. 18:01.609 --> 18:06.896

[SPEAKER_01]: But knowing that, you're able to architect things in a way that there is future proof as they can be. 18:06.996 --> 18:07.537 [SPEAKER_01]: Certainly not. 18:07.557 --> 18:10.701 [SPEAKER_01]: You're not going to wake up in nine months and be like, oh my gosh, what I just spent money on. 18:11.162 --> 18:12.844 [SPEAKER_01]: There's a limit to how much you can promise that. 18:13.384 --> 18:19.913 [SPEAKER_01]: But I think that you can't we have enough history with AI now to have a pretty good sense of how good it'll be in a year. 18:19.893 --> 18:24.663 [SPEAKER_01]: If anything, some of the pieces that they could good now will make it better later. 18:25.164 --> 18:29.552 [SPEAKER_01]: As opposed to, again, you waking up and saying, oh my god, we got to swap it out and we got to change the model. 18:29.953 --> 18:31.817 [SPEAKER_01]: You're not installing software. 18:32.318 --> 18:32.739 [SPEAKER_01]: You know what I mean? 18:32.759 --> 18:37.969 [SPEAKER_01]: You're building a solution that has pieces to it that are as modular as they can be, which is pretty modular. 18:38.354 --> 18:47.445 [SPEAKER_02]: Yeah, that's, I mean, that's one of the critical components is to why, you know, I think specialty groups like yours that are designing and implementing and working with them. 18:47.886 --> 18:55.315 [SPEAKER_02]: And aren't selling one individual thing, you're selling a set of solutions to a set of problems that are customized. 18:55.335 --> 18:57.958 [SPEAKER_02]: You said this and I want to really, really focus on it. 18:58.138 --> 19:02.944 [SPEAKER_02]: Like you said, automating little tasks. 19:02.924 --> 19:15.876 [SPEAKER_02]: So much of that height that you hear on LinkedIn or I mean, LinkedIn's I'd say it's a little better than say like a Facebook or an Instagram or an X, where they're like, you'll wake up tomorrow. 19:15.896 --> 19:19.099 [SPEAKER_02]: We need universal income because the bots will do everything. 19:19.799 --> 19:20.880 [SPEAKER_02]: Yeah. 19:20.900 --> 19:21.921 [SPEAKER_02]: That's not true so much. 19:22.321 --> 19:25.184 [SPEAKER_02]: No, and it's actually, maybe sure. 19:25.785 --> 19:32.931 [SPEAKER_02]: I'll sit with some of the great people and they could probably convince me that in 50 years that's where we might be. 19:33.164 --> 19:37.914 [SPEAKER_02]: In fact, those big, big things, it doesn't do them, and it doesn't do them well, and you can't trust it. 19:38.395 --> 19:39.136 [SPEAKER_02]: And you nailed it. 19:39.938 --> 19:44.487 [SPEAKER_02]: I love, I think it was quick-banks, who did a study last year or the year before. 19:44.548 --> 19:52.945 [SPEAKER_02]: And it was 75% or more of people in the field don't trust the data that they're looking at. 19:53.870 --> 19:55.733 [SPEAKER_02]: That's a huge problem. 19:56.454 --> 19:57.796 [SPEAKER_02]: That creates uncertainty. 19:57.976 --> 20:06.189 [SPEAKER_02]: Construction hates uncertainty, just solving for little things together stacked makes for future. 20:06.209 --> 20:15.844 [SPEAKER_02]: So I wanna bring it to Connor, like maybe you have some examples of those little things that like free somebody up to A, have trust and B, make decisions. 20:16.111 --> 20:16.912 [SPEAKER_00]: Yeah, absolutely. 20:16.932 --> 20:21.659 [SPEAKER_00]: And I think I saw similar to your commentary on the little tasks of AI's great at the boring tasks. 20:21.679 --> 20:26.966 [SPEAKER_00]: So sometimes it might, our clients will try and latch on to the fancy problems. 20:27.046 --> 20:30.211 [SPEAKER_00]: But if you really decompose the problem, it's like what's actually the root cause of it. 20:30.231 --> 20:37.461 [SPEAKER_00]: So one example here in our work to actually talking about the other day is subcontractor via subcontractor prequalification process. 20:37.441 --> 20:47.742 [SPEAKER_00]: kind of a check the box, but manual effort for legal and finance teams today to just make sure yeah, our subcontractor is financially liquid, they're being our safety requirements, et cetera. 20:48.202 --> 20:54.575 [SPEAKER_00]: But if you're if you're leveraging the data, it could be more of a strategic advantage for you on your projects, your risk, et cetera. 20:54.595 --> 20:59.044 [SPEAKER_00]: If you're pulling in, subcuse drywall company has been 20:59.024 --> 21:04.131 [SPEAKER_00]: His head and his with any change orders, they're always hitting their schedule and they're always on time and on budget. 21:04.571 --> 21:13.283 [SPEAKER_00]: Let's use that for more of a subcontractor performance reporting so we can use it as a strategic advantage of what subcontractor is going to be the best trade and partner for us on this job. 21:13.383 --> 21:24.998 [SPEAKER_00]: So being able to leverage that data and you might not be able to trust 75% of the data, but there's a lot of data there that is under leverage today to help the business make better decisions at the time of estimating at the time of buyout. 21:24.978 --> 21:54.124 [SPEAKER_02]: So moving up more from just to check the box activity to more of a competitive advantage for you as you're going to bid and preparing your project plans and schedules their fear of the data or their unsure of the data is that they're not seeing it all right they're not getting it all they're only capturing like a little bit of it so they don't they don't trust it they want to know that it's the entirety so they want to know that like that drywall contractor didn't actually you know just like we didn't notice that the two times they defaulted or they were later whatever 21:54.492 --> 22:08.569 [SPEAKER_02]: And so that's the point is that you're giving them the understanding that we have it in it's entirety and now we're making it available to you and it's entirety to make a really well informed decision and drive your business and that's ultimately what we want, right? 22:08.589 --> 22:18.762 [SPEAKER_02]: This is that I love that it's great at boring

tasks because we don't have enough people, we don't have enough time and we certainly don't have enough experience. 22:18.742 --> 22:24.829 [SPEAKER_02]: to go around to make those informed decisions and that's what, you know, things like this do. 22:24.869 --> 22:34.500 [SPEAKER_02]: And I mean, there's so many things in what construction companies do that are menial little tasks that are necessary. 22:34.560 --> 22:37.684 [SPEAKER_02]: Like, I think people hear that and they think, oh, it's unnecessary. 22:37.704 --> 22:39.106 [SPEAKER_02]: We'll just, you can't skip it. 22:39.146 --> 22:40.227 [SPEAKER_02]: It's necessary. 22:40.207 --> 22:41.288 [SPEAKER_02]: But that doesn't mean it's fun. 22:41.769 --> 22:48.196 [SPEAKER_00]: It's so funny on that too, because I'll talk to so many like superintendents, project managers, guys that are in the field to start off our projects. 22:48.256 --> 22:50.158 [SPEAKER_00]: And they'll be so resistant to start. 22:50.178 --> 22:51.860 [SPEAKER_00]: They'll say, hey, I can't help you with my job. 22:52.200 --> 22:54.603 [SPEAKER_00]: And then I ask them a question because what's corporate bugging you about? 22:54.643 --> 22:57.426 [SPEAKER_00]: Or what annoys you about the information that corporate's bugging you for? 22:57.486 --> 23:05.414 [SPEAKER_00]: And the floodgates open up and they start listening off 10, 20 different ideas of things that can potentially make their lives easier, because they want to be in the field building. 23:05.434 --> 23:08.037 [SPEAKER_00]: They don't want to have to do all the paperwork, the status updates. 23:08.017 --> 23:10.681 [SPEAKER_00]: financial reports and budgets and stuff like that. 23:10.761 --> 23:12.865 [SPEAKER_00]: So it's eye open for some of them sometimes. 23:13.065 --> 23:21.519 [SPEAKER_01]: And Jeff, that speaks to where we look at the role of AI is to elevate the human judgment, intelligence, not replace it. 23:21.959 --> 23:27.308 [SPEAKER_01]: Is you're saying we want to pull away the stuff that stops you from doing what you're really there for. 23:27.288 --> 23:30.774 [SPEAKER_01]: It's necessary for the project and for the company to run. 23:31.435 --> 23:32.597 [SPEAKER_01]: But it isn't building. 23:32.617 --> 23:33.539 [SPEAKER_01]: It isn't adding value. 23:33.559 --> 23:34.761 [SPEAKER_01]: So how do we pull that away? 23:34.801 --> 23:36.984 [SPEAKER_01]: So you have more time to think about what you're doing. 23:37.024 --> 23:38.026 [SPEAKER_01]: Talk to your teammates. 23:38.066 --> 23:38.908 [SPEAKER_01]: Talk to your subs. 23:38.948 --> 23:42.714 [SPEAKER_01]: Whoever might be, but really elevating the human not replacing them. 23:42.934 --> 23:44.297 [SPEAKER_01]: I mean, it's really funny. 23:44.317 --> 23:48.604 [SPEAKER_02]: You go to it's been a lot of attempts at this over time to make us more human. 23:48.668 --> 23:53.593 [SPEAKER_02]: And it's really interesting because, you know, there's so many people that AI makes us less human. 23:53.793 --> 23:55.114 [SPEAKER_02]: I think done correctly. 23:55.154 --> 23:56.656 [SPEAKER_02]: It makes us more human. 23:56.676 --> 23:59.698 [SPEAKER_02]: What is construction based off of relationships? 23:59.718 --> 24:01.120 [SPEAKER_02]: Always has been always will be. 24:01.440 --> 24:02.321 [SPEAKER_02]: It's a face-to-face. 24:02.801 --> 24:06.805 [SPEAKER_02]: It's a hand-to-hand putting work in getting things built. 24:07.145 --> 24:09.368 [SPEAKER_02]: And I used to say this like, it's so crazy. 24:09.388 --> 24:13.692 [SPEAKER_02]: Because maybe this is 10 years ago where I was like, you're pushing too much to the field. 24:13.932 --> 24:17.275 [SPEAKER_02]: And you're really, you're inundating them. 24:17.457 --> 24:24.546 [SPEAKER_02]: They're dabbling in all of your things, but, you know, somebody in finance in a CFO and others in operations were like, we need that. 24:25.127 --> 24:28.592 [SPEAKER_02]: And I'm like, you're not wrong, but, gosh, is there easier way to do it? 24:28.612 --> 24:38.505 [SPEAKER_02]: We've tried so many of you things along the way that now I think we're in a position where we have an opportunity to deploy a set of tools that can achieve that. 24:39.106 --> 24:42.250 [SPEAKER_02]: And then ultimately, hopefully help the relationship building 24:42.230 --> 24:44.916 [SPEAKER_02]: help the decision-making problems. 24:45.116 --> 24:46.479 [SPEAKER_02]: It's not going to hear rid of a problem, right? 24:46.560 --> 24:53.094 [SPEAKER_02]: If your AI stack tells you that your switch gear is late, it can't fix that. 24:54.177 --> 24:56.121 [SPEAKER_02]: The key is it tells you that. 24:56.287 --> 25:03.099 [SPEAKER_02]: you have to decide as a team, how you're going to adapt to that and handle that. 25:03.539 --> 25:08.187 [SPEAKER_02]: And the earlier the signals happen, the sooner you can do that. 25:08.287 --> 25:11.693 [SPEAKER_02]: And man, that's where this stuff is truly transformative. 25:12.214 --> 25:18.565 [SPEAKER_02]: And I want to dig back to one thing about the future-proofing hue, cause I want, 25:18.545 --> 25:45.582 [SPEAKER_02]: You know, there's there's a lot of this like am I going to go to one big am I going to go buy open AI and I'm going to do all that or I'm going to build it all you know there's always been that build first by right talk about the difference here because you talked about switching out models and I think that may have gloss over for a few people what that even means so talk about how you guys are approaching this problem of the rapid change that's going to happen. 25:45.562 --> 25:46.705 [SPEAKER_02]: it's happening today. 25:46.785 --> 25:48.228 [SPEAKER_02]: It's happening tomorrow. 25:48.750 --> 25:54.182 [SPEAKER_02]: How are you stacking this to solve that, you know, sort of, you're not fully future proof. 25:54.203 --> 25:55.546 [SPEAKER_02]: Nobody, you know, you didn't say that. 25:55.566 --> 25:58.713 [SPEAKER_02]: You just said future proof fish,

you know, what's much as you can. 25:58.773 --> 26:00.918 [SPEAKER_01]: There's a few things in there that are worth talking about. 26:00.959 --> 26:02.001 [SPEAKER_01]: One of them is. 26:01.981 --> 26:08.736 [SPEAKER_01]: Basically every month, whether it's Google or it's OpenAI or it's someone else, there's a new model that's coming out. 26:08.956 --> 26:11.682 [SPEAKER_01]: And model, by that I mean, it's kind of like the engine of AI. 26:11.722 --> 26:13.065 [SPEAKER_01]: It isn't what you're using. 26:13.226 --> 26:16.212 [SPEAKER_01]: It's the thing under what you're using back to your car analogy. 26:16.272 --> 26:18.718 [SPEAKER_01]: It literally is like the engine of the car, but you don't drive the engine. 26:18.758 --> 26:19.720 [SPEAKER_01]: You drive the car. 26:20.071 --> 26:39.666 [SPEAKER_01]: So what we're doing a lot of is building all of the things that make it functional and useful and then you can swap the engine out easier than you can swap a real engine out and it will still work and it's still interconnected the way you know the old one was but it'll be a little faster a little smarter a little bit more capable or often what you're really going to see. 26:39.646 --> 26:43.751 [SPEAKER_01]: Because the models now are good enough that most of what you need them to do, they're probably good enough already. 26:44.092 --> 26:45.453 [SPEAKER_01]: They're going to start to get a lot cheaper. 26:45.834 --> 26:48.838 [SPEAKER_01]: So the running costs, the gas, is going to be cheaper and cheaper. 26:48.878 --> 26:51.401 [SPEAKER_01]: And I think dramatically so over the next couple of years. 26:52.082 --> 26:59.832 [SPEAKER_01]: The other thing though, is because our team has been doing this, in some cases for 20 plus years, I'm much more on the technical side. 26:59.812 --> 27:03.797 [SPEAKER_01]: Everything isn't in LLM and every solution doesn't mean you need a chatbot for it. 27:03.837 --> 27:08.722 [SPEAKER_01]: There's vision models, there's this kind of model, there's analytics models and so on. 27:09.203 --> 27:12.166 [SPEAKER_01]: And asking yourself, do I need to use the big OpenAI one? 27:12.186 --> 27:15.630 [SPEAKER_01]: And honestly, people often don't want to use one that's public for a number of reasons. 27:15.991 --> 27:18.253 [SPEAKER_01]: And not so much public, but you know, pinging API. 27:18.314 --> 27:21.417 [SPEAKER_01]: Maybe you want to have one that's hosted, it's just for you, probably hosted or whatever. 27:22.018 --> 27:25.342 [SPEAKER_01]: Or maybe you needed a tune, something so that it works with the data you've been given. 27:25.562 --> 27:28.165 [SPEAKER_01]: There's a bunch of different ways to look at this. 27:28.145 --> 27:36.673 [SPEAKER_01]: The LLMs have really given everybody a lot of focus and a lot of energy, which is great, but honestly, we've had pretty good models for certain things for a long time. 27:37.153 --> 27:45.901 [SPEAKER_01]: So depending on what you need, it may or may not

be a model that's ever going to change, because it's already as good as you need it to be, and why mess with it later, or it works, let's just move on. 27:46.021 --> 27:49.965 [SPEAKER_01]: Just keep in mind that there's a lot of different engines, just like there are with engine engines. 27:50.005 --> 27:56.110 [SPEAKER_01]: There's electrical ones, there's gas ones, there's two 27:56.090 --> 28:01.842 [SPEAKER_01]: And you're starting to see even for the big frontier models people hear about, they're getting their own personalities as well. 28:01.942 --> 28:09.057 [SPEAKER_01]: So, Claude has a ton of its own, a chatchipit has a ton of its own, and some areas where it's better and worse. 28:09.117 --> 28:12.144 [SPEAKER_01]: Claude has been making a lot of progress in the coding area. 28:12.164 --> 28:13.166 [SPEAKER_01]: Now, so is OpenAI. 28:13.246 --> 28:16.613 [SPEAKER_01]: But the point is, depending on what you're trying to do, 28:16.593 --> 28:19.338 [SPEAKER_01]: They're not interchangeable as much as maybe they were a year ago. 28:19.959 --> 28:25.069 [SPEAKER_01]: So a lot of that goes into what Connor and the technical team will do is, what do you really need here? 28:25.109 --> 28:32.222 [SPEAKER_01]: And the other thing I want to touch back on the role of humans is and this idea of data that you don't trust. 28:32.202 --> 28:36.532 [SPEAKER_01]: If it's opaque, you're not giving them any more trust, even if there's AI in there. 28:37.014 --> 28:44.291 [SPEAKER_01]: So a lot of what we also do, and that's this humility of talking to people, is how we're building in verification, so you can look at the source documents really quickly. 28:44.752 --> 28:46.476 [SPEAKER_01]: And maybe they're highlighted or whatever it might be. 28:47.038 --> 28:50.025 [SPEAKER_01]: But understanding that a human is using this, 28:50.005 --> 28:53.129 [SPEAKER_01]: is what makes a really good engine into a really good car. 28:53.690 --> 28:54.331 [SPEAKER_01]: You know what I mean? 28:54.371 --> 28:59.739 [SPEAKER_01]: Like how many times have you seen when people tricks out, people trick out and not so great car with an amazing engine? 28:59.779 --> 29:02.663 [SPEAKER_01]: It's like, oh, okay, I don't want to drive that thing, but golly, it's fast. 29:02.963 --> 29:09.853 [SPEAKER_01]: That's a rough analogy for what you might do here is if you're not giving people the comfort to use the thing. 29:09.833 --> 29:11.055 [SPEAKER_01]: doesn't matter how good the tech is. 29:11.115 --> 29:17.083 [SPEAKER_01]: And we've seen that in SaaS to where people over automate and you feel like I don't have a handle on my risk. 29:17.103 --> 29:21.909 [SPEAKER_01]: So there's you're automating too much and I don't want to decide at the end or approve at the end. 29:22.450 --> 29:23.932 [SPEAKER_01]: I wasn't part of the work along the way. 29:23.972 --> 29:25.895 [SPEAKER_01]: I don't have contexts to make that decision. 29:25.935 --> 29:30.441 [SPEAKER_01]: I can't

approve this because I don't really know what you were looking at and I don't really know what's being worked on. 29:30.421 --> 29:38.293 [SPEAKER_01]: So all of that kind of comes together in one big thing, what you're saying, how am I creating something that gives the user comfort that there's no new risk? 29:38.754 --> 29:45.024 [SPEAKER_01]: And then senior management comfort that they didn't just make an investment that they're going to have to, you know, replace in 12 bucks. 29:45.324 --> 29:45.585 [SPEAKER_02]: Yeah. 29:45.925 --> 29:55.180 [SPEAKER_02]: I mean, you hit on a couple of things that I want to pull over to Connor, and I'm going to use my own analogy in here because you talked about the trick-out car that doesn't look good, but goes fast. 29:55.160 --> 30:00.389 [SPEAKER_02]: I just had this experience where it was traveling in a rented car, we we got upgraded. 30:00.429 --> 30:05.098 [SPEAKER_02]: I did not just rent this car straight out, but it was a it was a it was a range Rover sport and it was too much. 30:05.498 --> 30:17.640 [SPEAKER_02]: There was a number of features that I could not free I mean it was like I got to get where I'm going like what the heck I know it's got it's got to have a heated wheel it's got to have this it's got. 30:17.620 --> 30:46.969 [SPEAKER_02]: I got my kid in the back trying to figure it out and I will tell you like my experience was not great because it was just like yeah, I mean I'm in a captain's chair and it's comfy in this thing's a giant but what is it doing how do I make it and and I got this giant screen I got to look at the road like so I'm with you you can go both ways right you can underdo it and you can overdo it so it corner how do you make sure that it's that creamy middle just right because people have to use it. 30:47.152 --> 30:52.883 [SPEAKER_00]: It's exactly the importance of us trying to understand the processes what the outcomes they're trying to do because it's a classic. 30:53.304 --> 30:54.145 [SPEAKER_00]: I might need a Toyota. 30:54.165 --> 30:56.770 [SPEAKER_00]: I don't need a Ferrari or in your case a Range Rover Sport. 30:56.850 --> 30:59.996 [SPEAKER_00]: I just need a reliable basic car to get me from point A to point B. 31:00.497 --> 31:10.155 [SPEAKER_00]: So once we really understand the processes, it's, okay, this might be AI isn't just an LLM or the latest and greatest reasoning model from OpenAI or Clot or Gemini. 31:10.135 --> 31:30.304 [SPEAKER_00]: It could be a simple automation of just moving data around or transforming data or trying to use all the rich history that you have to predict the potential outcome, so it could be schedule risk, it could be labor run rates, or to want to use the engine example we built a predictive maintenance or predictive diagnostics model for heavy equipment for paving companies. 31:30.284 --> 31:41.190 [SPEAKER_00]: helping use that rich work order history, fault codes, engine failures, resolutions, et cetera, to help when maybe an engine is about to fail, or when something does fail, what parts do I need to go fix that? 31:41.210 --> 31:45.280 [SPEAKER_00]: Because we want that machine back up and running, otherwise it's going to really impact our project timeline. 31:45.561 --> 31:48.107 [SPEAKER_00]: We're going to eat a lot more costs, maybe more rental costs, or. 31:48.087 --> 31:52.413 [SPEAKER_00]: something else that we need to do because we need to get that very important piece of equipment up and running. 31:52.473 --> 32:05.550 [SPEAKER_00]: So it's really trying to decompose what that problem is and then we'll come back and say, okay, it might be a mix of an automation, an LLN, and maybe a predictive model, or it could just be a basic automation and move data from one place to the other, help to make decisions. 32:06.291 --> 32:15.023 [SPEAKER_02]: Yeah, and to say with the car analogy, now you put them in the driver's seat, how do you make sure they drive the car and they don't just get out and go do it the old way, walk to where 32:15.678 --> 32:15.958 [SPEAKER_00]: Yeah. 32:16.099 --> 32:28.319 [SPEAKER_00]: I mean, we're working with these guys week over week every time we make a new update to the solution we're building or making sure that what the user experiences and user journey is something that they would actually use. 32:28.359 --> 32:30.303 [SPEAKER_00]: So it's not just you give us a problem. 32:30.383 --> 32:33.568 [SPEAKER_00]: We go away for a few weeks and come back with a solution and say use it. 32:33.548 --> 32:43.826 [SPEAKER_00]: We're going to cheat back from them along the way, call it an iterative or agile process to make sure that this is up to their standards, it's muting the expectations and outcomes that they expect this thing to do. 32:43.846 --> 32:47.151 [SPEAKER_00]: And then once we give them the keys, they're ready to drive it. 32:47.171 --> 32:52.300 [SPEAKER_00]: They don't have to go figure out the fancy touchscreen on the Range Rover Sport and actually what capabilities are. 32:52.499 --> 32:55.144 [SPEAKER_01]: But also, there's a change management piece to this. 32:55.204 --> 32:57.368 [SPEAKER_01]: That's also part of a lot of engagements. 32:57.528 --> 32:59.391 [SPEAKER_01]: We have actually an instructional designer. 32:59.511 --> 33:03.819 [SPEAKER_01]: We went that far to say, how are we creating materials? 33:03.879 --> 33:06.043 [SPEAKER_01]: So people can onboard and get going quickly. 33:06.624 --> 33:10.932 [SPEAKER_01]: It's not just the test group that you want to get moving. 33:10.952 --> 33:12.134 [SPEAKER_01]: You want the whole organization. 33:12.594 --> 33:15.199 [SPEAKER_01]: So not only are you starting with, 33:15.179 --> 33:25.400 [SPEAKER_01]: a pretty rigorous analysis of what people have said or they need, what the tech team has said, here's our current stack, here's the software that we already used that we want you to connect with. 33:26.221 --> 33:31.973 [SPEAKER_01]: Also

though the financial side of what's the ROI, but then you're saying after we've gone through all that. 33:31.953 --> 33:37.183 [SPEAKER_01]: We have a lot of material to go to the rest of the company and say, Fred really liked it. 33:37.683 --> 33:38.385 [SPEAKER_01]: You know what I mean? 33:38.405 --> 33:42.873 [SPEAKER_01]: And we talked to 20 of your people, here's how to use it, here's what to expect and so on. 33:42.953 --> 33:48.443 [SPEAKER_01]: So it isn't just here the keys, it's also here's the map, how's that beating up a metaphor. 33:48.423 --> 33:51.047 [SPEAKER_01]: But the point is, you can't just leave people with that. 33:51.188 --> 33:56.256 [SPEAKER_01]: It's that everybody has had that problem with SAS, where you dump it on people and they get frustrated. 33:56.436 --> 34:02.727 [SPEAKER_01]: Happily, what we create tends to be the point of it a lot of times is it's already a lot easier, because it's automating little pieces and so on. 34:03.207 --> 34:05.852 [SPEAKER_01]: But also just making sure that people aren't left to figure it out. 34:06.092 --> 34:09.638 [SPEAKER_01]: Number one reason for churning SAS is lack of adoption. 34:09.618 --> 34:28.234 [SPEAKER_02]: 100% they just they never get past the point of using it never get past pilot you never get full saturation it just doesn't work and and that's why it's critical to have you know a group like yours that you're not tied to anyone particular thing and when I you know we were talking really specifically about AI agents and. 34:28.214 --> 34:44.772 [SPEAKER_02]: LLMs and computer vision and other things, but ultimately you're working side of a stack too, so you're working with their PMIS systems, you're working with their financials, you're working with what other, you know, maybe other tool sets that they have and you're sticking in the middle there, right? 34:45.578 --> 34:54.632 [SPEAKER_01]: And connecting dots, I mean, a lot of what we'll do with, you know, great example is one of the projects was cost to complete like, where are we, you know, we're in the middle of the project. 34:54.912 --> 35:02.604 [SPEAKER_01]: I don't know how many, you know, other change orders outstanding are through this or that and everybody's, you know, nervous about where are their surprises lingering. 35:03.064 --> 35:06.089 [SPEAKER_01]: And some of that information or all that information is somewhere. 35:06.509 --> 35:13.560 [SPEAKER_01]: It's just not usually in the same place and that usually in a way that you can do something with it. 35:13.540 --> 35:40.763 [SPEAKER_02]: And I'll steal from that, too, is that like there's a lot of computer vision out there that we know is a lot further along than some of the other stuff, but it doesn't actually work really well with the data right now to say, okay, what is the computer vision saying we are where we are and how does that relate to the financials in the billing and other things so I can really get to a true, like, I feel pretty good about a cost to complete or a percent 35:40.743 --> 35:52.374 [SPEAKER_02]: Well, we build 50, so we're 50, you know, uh, you know, that's what you're combining systems together, Connor, and that's part of, you're not just working with people, you're working with the tech stack, too. 35:52.774 --> 35:54.916 [SPEAKER_00]: Like the computer vision examples, perfect. 35:54.936 --> 35:59.860 [SPEAKER_00]: There's great computer vision capabilities out there, but I think a lot of the clients that we talk to, it's like, oh yeah, cool. 35:59.880 --> 36:00.881 [SPEAKER_00]: We're doing some drone photos. 36:00.901 --> 36:10.530 [SPEAKER_00]: We're doing some walkthrough videos with the helmet cans and stuff, but we're not actually using the information from those, those videos and actually the computer vision 36:10.510 --> 36:24.707 [SPEAKER_00]: update the project plan, update the schedule, update the budget, go get a change order because we thought this is going to be 50% done by month three of the project and oh, we're only 25% done based on what the computer vision and lock-throughs are telling us. 36:24.807 --> 36:36.180 [SPEAKER_00]: So, that's the important key I think moving forward is how do we actually leverage all these great tools that are being used in the field, but they're kind of just sitting in silos and that's a lot of valuable information to get me fed back to the teams. 36:36.278 --> 36:51.199 [SPEAKER_02]: Well, I think that's critical too, because we've seen this in litigation too, because some things that I've heard recently are like, I don't think I want to do that walk anymore, because by the way, when something goes wrong down the road and I go back and I go crap, I had it. 36:51.517 --> 36:54.760 [SPEAKER_02]: And I didn't know it, that I'm liable for it. 36:55.321 --> 36:57.763 [SPEAKER_02]: And that is not a reason to not doing. 36:58.224 --> 37:00.526 [SPEAKER_02]: That is a reason to connect it. 37:00.987 --> 37:02.849 [SPEAKER_02]: So it can signal sooner. 37:02.889 --> 37:13.840 [SPEAKER_02]: That's the thing that the computer vision hook to the other things connected together can create signals that tells that, soup, PM, superpowers. 37:14.260 --> 37:18.064 [SPEAKER_02]: Hey, floor three, west wing, 37:18.382 --> 37:23.110 [SPEAKER_02]: way off early, early signal, we're going to be in trouble. 37:23.174 --> 37:23.755 [SPEAKER_02]: What do you do? 37:23.775 --> 37:25.196 [SPEAKER_02]: You get out there and you look at why? 37:25.576 --> 37:27.738 [SPEAKER_02]: Why might be a number of different reasons? 37:27.798 --> 37:36.427 [SPEAKER_02]: Oh, my lift's been down for a few days or I don't have the material or the framer, the drywall or the, you know, the crews behind. 37:36.747 --> 37:39.029 [SPEAKER_02]: Whatever it might be, but we can even know it. 37:39.369 --> 37:42.773 [SPEAKER_02]: And we need to early signal to it because that's what we truly want. 37:43.193 --> 37:45.716 [SPEAKER_02]: I don't want

people to chuck things away, but I've heard it now. 37:45.836 --> 37:50.380 [SPEAKER_02]: So, you know, these are real, real solid 37:50.360 --> 38:00.697 [SPEAKER_00]: And even from a safety perspective to using some of those drone surveys to identify where there's main material that's dangerously stacked in a hydrophic area or something like that to avoid those problems before it becomes an issue. 38:00.717 --> 38:06.006 [SPEAKER_00]: Like it's those early signals of what's figured out day off rather than when the incident actually happened. 38:06.104 --> 38:23.168 [SPEAKER_02]: Well, I mean, how about trenching, you know, like how many trench collapses do we see how awesome would it be if that drone was picking that up and just, you know, it's an easy measurement right it's height, it's length, those two things, the walls collapse like sound the alarm, you know, and people think, oh, 38:23.148 --> 38:29.218 [SPEAKER_02]: just read another report of, you know, unfortunate accident with another group in a trenching incident. 38:29.258 --> 38:33.065 [SPEAKER_02]: Like, these things happen and we have these tools that can protect people. 38:33.585 --> 38:45.966 [SPEAKER_01]: But they gotta be all working together and connected and, you know, and coming back to the point we made earlier about automating the staboring stuff, you have time to process those signals when you're not burning up time on paperwork. 38:46.587 --> 38:49.931 [SPEAKER_01]: You know, like you have time to think about your project, people are worried about it already. 38:49.951 --> 38:58.660 [SPEAKER_01]: It's not like they're not doing their jobs, but if you're overwhelmed with all this stuff, you blow a couple of days on paperwork or whatever it might be, you know, things stack up. 38:58.881 --> 39:04.887 [SPEAKER_01]: So having the time and space for people to do what they're really there for, which is to manage things and execute things. 39:05.368 --> 39:11.194 [SPEAKER_01]: As opposed to doing the back end support, that's essential, but man, it can take a lot of time. 39:11.174 --> 39:16.379 [SPEAKER_02]: Yeah, and if it's taking time away to do that, you're not keeping your eyes on the job and your eyes on the job or what we need. 39:16.759 --> 39:21.583 [SPEAKER_02]: We'd love those computer vision signals to show it too, but then we don't just want to slap those people. 39:21.603 --> 39:31.612 [SPEAKER_02]: I want seasoned foreman to go out and sit down with a team that's digging that trench and say, listen, like when you started, you were here, we're bringing in new workforce, right? 39:31.632 --> 39:34.775 [SPEAKER_02]: We don't have a ton of experience and we need to train them. 39:34.795 --> 39:41.080 [SPEAKER_02]: So this is an opportunity to not worry about your daily report, not worry about the other thing right now. 39:41.060 --> 39:56.003 [SPEAKER_02]: and sit down with some new team members and say, listen, when you start it and you were, you know, 10 feet, you're okay, but you've now continued down your 20 feet long and you're building with the same walls and those walls of the first 10 are putting just as much pressure. 39:56.283 --> 39:58.326 [SPEAKER_02]: You're not giving yourself enough space. 39:58.306 --> 40:15.167 [SPEAKER_02]: Those are things that season and by the way, I would not know that if I had that wasn't a real incident where I actually got talked to by somebody explaining this to me that this stuff this is how this works, so this is valuable learned over time experience that can then be 40:15.147 --> 40:18.492 [SPEAKER_02]: codified and told to people and explained that we can just get up. 40:18.813 --> 40:26.985 [SPEAKER_02]: We can take less time doing paperwork, wartime trading the future, wartime folks on the job, wartime get work in, and that's, you know, that's the power of this. 40:27.106 --> 40:31.232 [SPEAKER_02]: So I just love to see practicality. 40:31.432 --> 40:33.155 [SPEAKER_02]: That's why I said, how do you do AI? 40:33.215 --> 40:35.899 [SPEAKER_02]: But really, we've talked about it as a tool. 40:35.979 --> 40:42.910 [SPEAKER_02]: We've really gone to the fundamentals 40:43.058 --> 40:52.504 [SPEAKER_02]: I do think there's an opportunity here done correctly that you guys are on the forefront of starting to connect our ecosystem in a way that it can effectively change. 40:53.287 --> 40:54.891 [SPEAKER_02]: And that's pretty powerful. 40:55.850 --> 41:02.703 [SPEAKER_01]: That is the plan, one company at a time, but really starting to connect what the potential is. 41:02.763 --> 41:06.309 [SPEAKER_01]: And how does it make you rethink what you're doing? 41:06.350 --> 41:14.685 [SPEAKER_01]: At first, we automate the boring stuff, but then you realize we don't need to do it quite like that in terms of what we do when or what order that we do things in. 41:14.665 --> 41:25.460 [SPEAKER_01]: I mean, that's a little further out, I think there's a lot to do right now, but the ultimate goal in all of this is if you had more time or you didn't need to throw bodies at that problem, what might you do differently? 41:25.681 --> 41:27.283 [SPEAKER_01]: How might you control risk? 41:27.323 --> 41:30.207 [SPEAKER_01]: How might you win bids on time, not just money? 41:30.527 --> 41:43.626 [SPEAKER_02]: Yeah, I mean, those are powerful things because, you know, we talked about this in the SaaS times and I think it's more true now than ever. 41:43.606 --> 42:06.087 [SPEAKER_02]: And we would make this software do those things and now we can make AI do some of those things and connect where it wasn't connecting because I was mainly having to go from E and pick up ABC and put it into F right well okay so now we're solving some of that but what if we have the time to think about what do we really need BC DE maybe we can get from A to F 42:07.703 --> 42:08.504 [SPEAKER_02]: systematically. 42:08.664 --> 42:14.229 [SPEAKER_02]: As long as these are not decisions, these are

automations, these are things that would naturally come together. 42:14.269 --> 42:16.331 [SPEAKER_02]: Okay, let's skip to death. 42:16.431 --> 42:29.622 [SPEAKER_02]: As long as we're not removing human decision-making and creating assumptions in there, right, and we're just automating a process, like you said, we can rethink work completely. 42:30.103 --> 42:37.069 [SPEAKER_01]: How many documents in construction were kind of 42:37.133 --> 42:37.814 [SPEAKER_01]: right a lot. 42:38.474 --> 42:40.416 [SPEAKER_01]: So okay, does it still need to be like that? 42:40.516 --> 42:46.061 [SPEAKER_01]: Maybe for legal reasons you need to have that version somewhere, but to someone need to be looking at a PDF specification. 42:47.102 --> 42:47.662 [SPEAKER_01]: Not sure they do. 42:48.323 --> 42:55.750 [SPEAKER_01]: You know, and there's a hundred, I happen to know, specs better than other things, but there's a hundred little things like that where does it really need to be the equivalent of paper? 42:56.290 --> 42:57.671 [SPEAKER_01]: Surely we can do it some other way. 42:57.811 --> 42:59.553 [SPEAKER_01]: And so I think there's a lot of scope for that. 42:59.573 --> 43:05.318 [SPEAKER_01]: It's important to do these things without creating new risks and not overstepping areas that are there for a reason. 43:05.298 --> 43:34.444 [SPEAKER_02]: But that question I think will be something there's no answer to right now it's a process that we're all in the middle of war in some cases the beginning of yeah and I think that's your I mean I could go on forever with you guys about this but I think that's your moment of saying like here's where we are today here's where we can do here's what we're looking down the path of one partner with you and get down there and I think that's what's different about quantum rise is you're not selling me one thing you're selling me a partnership and a relationship and you're going to go down this with me and you know 43:34.525 --> 43:44.624 [SPEAKER_02]: I get to leverage your expertise as an organization to know that you're going to guide me, not just down the right path, but towards the path of my problem. 43:45.005 --> 43:52.819 [SPEAKER_02]: Because you've got general contractors, you've got asphalt papers, you've got drywallers and framers, you've got a little bit of everybody and they're all need different things. 43:52.960 --> 43:57.428 [SPEAKER_02]: So that's also what, you know, there's this, oh, I need to do it in house. 43:57.408 --> 44:00.414 [SPEAKER_02]: Listen, we subcontract for a living in this business, right? 44:01.557 --> 44:02.839 [SPEAKER_02]: At GCCs, you don't build much. 44:02.859 --> 44:06.587 [SPEAKER_02]: You know, you self-perform one or two things, but you outsource a lot of it. 44:06.627 --> 44:14.503 [SPEAKER_02]: So again, find those trusted partners like quantum rise and, you know, on that note, like Connor, where can they go? 44:14.543 --> 44:18.792 [SPEAKER_02]: Learn a little bit more about you, connect with you, and then I'll throw it over to you. 44:18.772 --> 44:22.496 [SPEAKER_00]: Yeah, feel free to find me on LinkedIn, Conner Schmelling, or Link will be shared with this. 44:22.617 --> 44:24.519 [SPEAKER_00]: And then at quantumrise.com, we're here. 44:24.619 --> 44:31.447 [SPEAKER_00]: We're problem solvers looking to make contractors, subcontractors, that's home favors, when their business and transform what they are. 44:32.108 --> 44:33.169 [SPEAKER_02]: I love it, I love it. 44:33.249 --> 44:35.432 [SPEAKER_02]: Hugh, always great to sit down with you. 44:35.492 --> 44:40.718 [SPEAKER_02]: Let people know where they can go learn a little bit more about you and about quantum rise as well. 44:40.738 --> 44:43.061 [SPEAKER_01]: Yeah, LinkedIn, again, is probably the best place. 44:43.081 --> 44:44.823 [SPEAKER_01]: Quantumrise is at quantumrise.com. 44:45.204 --> 44:45.885 [SPEAKER_01]: We've got a lot there. 44:45.905 --> 44:47.867 [SPEAKER_01]: We'll have a lot more about what we're doing. 44:47.847 --> 44:48.969 [SPEAKER_01]: Yeah, excited for it. 44:49.189 --> 44:51.432 [SPEAKER_02]: I was excited to sit down when I heard what you guys were up to. 44:51.452 --> 44:55.158 [SPEAKER_02]: I think this is the type of organization that's type of thing we need in the industry. 44:55.779 --> 45:04.292 [SPEAKER_02]: And I just can't thank you enough for coming on the show and wrapping that was uh that was one of the most sound AI episodes we've done guys. 45:04.332 --> 45:06.435 [SPEAKER_02]: So to both of you, I appreciate that a lot. 45:06.636 --> 45:07.377 [SPEAKER_00]: Thanks for having us on. 45:07.457 --> 45:08.218 [SPEAKER_00]: Appreciate it, Jeff. 45:08.502 --> 45:13.894 [SPEAKER_02]: Thank you for tuning in the day to geek out for our interview with Connor Smelling and Hugh Seaton. 45:13.914 --> 45:19.547 [SPEAKER_02]: To read all our new stories, learn more about our guests and listen to the show, visit the contentcrew.com. 45:19.748 --> 45:22.193 [SPEAKER_02]: This is the contentcrew signing out. 45:22.213 --> 45:26.022 [SPEAKER_02]: Until next time, enjoy the ride, geek out.