Bluebeam Max Explained: AI Markups, Takeoffs, and Connected Workflows with Luke Prescott: täielik transkriptsioon

won't work to the couple of the different places, still within construction technology, then I came back to Bluebeam about two and a half years ago. 04:00.004 --> 04:05.409 [SPEAKER_00]: So now I lead the product and design team here, a huge advocate of our technology. 04:05.549 --> 04:08.392 [SPEAKER_00]: I love seeing the work that our teams are actively pursuing, 04:09.072 --> 04:18.837 [SPEAKER_00]: I'm going to say this evolution of where it's come from 2008 till now is unreal and I just feel incredibly lucky to be a part of it and to observe it. 04:18.937 --> 04:27.781 [SPEAKER_01]: Yeah, so it's awesome because you've got that history right swing in the hammer and getting the respect for actually doing it and then having a sip behind a computer and figure out what you want me to do here. 04:28.562 --> 04:34.825 [SPEAKER_01]: And that transition kind of sunk in and then if you fast forward and you look at you know you were here. 04:35.365 --> 04:44.167 [SPEAKER_01]: You did all that work, then you did go and look at the other half and other places and that's just a good valuable mix of learning, right? 04:44.207 --> 04:46.028 [SPEAKER_01]: That's how we get better and then come back. 04:46.068 --> 04:48.608 [SPEAKER_01]: So unbelievable to me, but it's still true. 04:49.108 --> 04:52.229 [SPEAKER_01]: There are still a lot of folks out there who don't understand blue beam. 04:52.349 --> 04:53.929 [SPEAKER_01]: So and you kind of said it, right? 04:53.969 --> 04:55.110 [SPEAKER_01]: Like we all call it blue beam. 04:55.410 --> 04:59.751 [SPEAKER_01]: I am guilty of this year and a half in and I haven't gotten good enough at calling it the right thing. 04:59.811 --> 05:01.371 [SPEAKER_01]: So explained to folks who may 05:05.472 --> 05:06.292 [SPEAKER_01]: How do you explain Bluebee? 05:06.513 --> 05:10.174 [SPEAKER_00]: Bluebee is the tool for every one in the industry to solve problems. 05:10.434 --> 05:18.157 [SPEAKER_00]: You can think of it as one of the most probably highest abstraction ways of referring to it is would be a tool to empower intent. 05:18.378 --> 05:24.920 [SPEAKER_00]: You know, if I'm a electrical contractor and there's something that needs to change, I have intent to get that changed and coordinated. 05:24.940 --> 05:29.422 [SPEAKER_00]: Well, that might have three or four other people that need to be involved in solving that problem. 05:29.802 --> 05:31.963 [SPEAKER_00]: I'm not even going to necessarily call that an RFI. 05:32.183 --> 05:33.364 [SPEAKER_00]: Maybe it is, maybe it isn't. 05:33.604 --> 05:46.031 [SPEAKER_00]: I just simply need to be able to communicate the intent of that problem either graphically or through annotations or within context of the specs or the submittals, the shop drawings, the drawings, whatever it might be, blue beam empowers all that. 05:46.152 --> 05:52.475 [SPEAKER_00]: Technically, it's a series of applications that run on desktop window machines on iOS, on Android, on a web app. 05:52.535 --> 05:56.578 [SPEAKER_00]: It's got some live collaboration pieces that let people do this in real time together. 05:57.158 --> 06:04.480 [SPEAKER_00]: It's got tools that connect into large document management systems, called the Enterprise DMS to use the acronym. 06:04.520 --> 06:07.040 [SPEAKER_00]: But at the end of the day, it's tool and the way our users use it. 06:07.080 --> 06:15.142 [SPEAKER_00]: It's, you know, they open up outlook, they open up, blue being review, they're in blue being tools all day long, solving different problems for different use cases. 06:15.442 --> 06:19.783 [SPEAKER_00]: We see it all the way through the early planning phases with owners and architects, all the way through, 06:22.704 --> 06:28.409 [SPEAKER_00]: even to the extent moving into other broader organizations that are trying to manage space and land. 06:28.570 --> 06:33.714 [SPEAKER_00]: A lot of our world is represented in the context of PDFs and drawings of record. 06:34.415 --> 06:37.698 [SPEAKER_00]: Bluebeam's the tool to manage that is really what it comes down to. 06:37.838 --> 06:42.723 [SPEAKER_00]: It's the best way to visualize the world around us in a very simple and accessible way. 06:42.863 --> 06:58.275 [SPEAKER_01]: Yeah, and I think that simplicity is key because this is a complicated process so you hit on this from the beginning and it's something that I took for granted until I got into the industry was that the world around us is built by people and people who are doing hard work. 06:58.755 --> 06:58.915 [SPEAKER_01]: Right? 06:58.935 --> 07:00.355 [SPEAKER_01]: This is not easy stuff. 07:00.435 --> 07:08.998 [SPEAKER_01]: It's getting more automated in ways like you said and I like the way you say that like we love to call things robots and I'm like they're really just tools in most cases. 07:09.158 --> 07:11.938 [SPEAKER_01]: So I think we're it's not it's hard work. 07:12.078 --> 07:16.760 [SPEAKER_01]: And so the management of that work needs to be simple and straightforward. 07:16.920 --> 07:18.540 [SPEAKER_00]: These people may not work at the same company. 07:19.542 --> 07:20.202 [SPEAKER_00]: No, that's true. 07:20.222 --> 07:21.203 [SPEAKER_00]: Some of them do, right? 07:21.283 --> 07:29.605 [SPEAKER_00]: It's easy if you and I are at the same company, we can solve problems, but try doing it when there's 10 people from five different companies that all have to try to solve the same problem. 07:29.805 --> 07:30.845 [SPEAKER_00]: I mean, it's not easy. 07:31.005 --> 07:35.087 [SPEAKER_00]: I'll say we've got to just not to get into the details, but we're here to get into the details, so let's do it. 07:35.307 --> 07:35.867 [SPEAKER_00]: We've got this. 07:36.747 --> 07:41.751 [SPEAKER_00]: functionality in our technology called Studio that allows for people to mark up documents together. 07:42.112 --> 07:46.135 [SPEAKER_00]: Watching a user in Studio is kind of fun to watch. 07:46.155 --> 07:47.716 [SPEAKER_00]: I

stood over the shoulder of a user. 07:48.297 --> 07:55.262 [SPEAKER_00]: They'll get a notification in their email, the click a link, immediately they're in the session, they mark it up, they close it, they can get another notification. 07:55.463 --> 08:01.828 [SPEAKER_00]: It's like a 15 second, 30 second flow of, and they're interacting with people that aren't at their organization. 08:02.048 --> 08:11.717 [SPEAKER_00]: They've never maybe never even really interacted with, but they've got the knowledge or the intent that they can communicate by just clicking a link notification, launching the app, marking it up, closing. 08:11.797 --> 08:17.203 [SPEAKER_00]: It's really a think of beauty, I would say, watching that happen in ways in which I think it, 08:17.623 --> 08:23.770 [SPEAKER_00]: Today there's more technology barriers to communicating externally outside of the organization just due to various requirements. 08:23.950 --> 08:29.977 [SPEAKER_00]: It's fun to see that the blue him has had such an influence on the industry to promote that level of connection. 08:30.078 --> 08:33.822 [SPEAKER_00]: I'll call it collaboration, but just connection, intent, communication. 08:33.842 --> 08:34.743 [SPEAKER_00]: It's fun to be part of that. 08:34.883 --> 08:49.607 [SPEAKER_01]: Yeah, and I agree that's one of the things that drew me in early early on is like a lot of software was there to capture certain things, but they weren't really there to get a decision made and get done and get moving and that's really what a lot of what we need is 09:03.351 --> 09:27.464 [SPEAKER_01]: We can even talk about that that like this tool works for architects, it works for engineers, it works for GCs and CMs, it works for trade contractors, it works for material suppliers like everybody's in it using it in different ways and so there's all these, there's gaps, you know, there's basics where people, you know, oh, I use it to open up my PDF so use it to use things, but there are so are tools like that right where you can hit a session. 09:28.004 --> 09:29.506 [SPEAKER_01]: Open it up and I don't think a lot of people know that. 09:29.546 --> 09:43.563 [SPEAKER_01]: If you are that person and you're that electrical contractor and you have that, you know, intent that question, right, you can open up a session, draw them right to it, go right to maybe it's the electrical engineer that needs to answer a question. 09:44.003 --> 09:46.224 [SPEAKER_01]: Maybe it's just GC these answer question. 09:46.304 --> 09:47.906 [SPEAKER_01]: Let's get her answered and let's go. 09:48.006 --> 09:50.567 [SPEAKER_01]: It might not be material in that it has to be an RFI. 09:50.607 --> 09:51.688 [SPEAKER_01]: It's just a quick question. 09:51.808 --> 09:52.809 [SPEAKER_01]: But it's in contact. 09:52.849 --> 09:54.450 [SPEAKER_01]: A lot of email lacks context. 09:54.610 --> 09:58.272 [SPEAKER_01]: So this is a contextual idea to dive in there. 09:58.372 --> 10:02.715 [SPEAKER_00]: We do this exercise with new folks that come onto the product team where we'll say, 10:03.055 --> 10:21.943 [SPEAKER_00]: take a determine the industry to take a condition right but take a condition in your home or take a place in your home whatever it might be your kitchen or your living room your front door describe it to be in an email and tell me something about that you need to change whatever it might be and then do it again with in blue beam on a p-out with a photo using our capture tool and a call out 10:22.063 --> 10:25.525 [SPEAKER_00]: Let's see how close I get to what your intent actually is. 10:25.665 --> 10:26.566 [SPEAKER_00]: And it's just kind of funny. 10:26.586 --> 10:34.211 [SPEAKER_00]: Could you imagine doing construction through a comet's field, that through a status field, or through a free tax box? 10:34.912 --> 10:36.453 [SPEAKER_00]: And it's like, of course not. 10:36.553 --> 10:41.596 [SPEAKER_00]: You have to go for much further beyond that and provide the visual context in the relationship that we're understanding. 10:41.616 --> 10:43.217 [SPEAKER_00]: What's the baseline that we're talking about? 10:43.338 --> 10:44.999 [SPEAKER_00]: What's the problem that we need to solve on top of that? 10:45.019 --> 10:46.500 [SPEAKER_00]: And then what's our Greek upon solution? 10:47.000 --> 11:05.787 [SPEAKER_01]: I mean, and that it's funny because there's still a lot of people out there doing that and then a lot of other parts of my life I would like a blue beam types solution to because again communication lacks context unless you have those kinds of things around it and again we're trying to build something that's highly coordinated and requires. 11:06.187 --> 11:28.321 [SPEAKER_01]: collaboration and communication more and it's funny because you'll hear the word coordination used and a lot of my BIM and VDC folks listening will think coordination in the form of like clash detection and I'm like no slurly like coordination of where are you what are you doing like there's physical coordination to what has to happen for crews to work together. 11:28.441 --> 11:28.661 [SPEAKER_01]: I don't 11:30.622 --> 11:45.404 [SPEAKER_01]: If you think back, you know, now more than ever, the coordination of different trades on to job sites by the GCs and knowing the order of events in which things have to happen is way more complicated when we started this thing. 11:45.544 --> 11:48.426 [SPEAKER_00]: He's probably even just worth calling out Bluebeam loves 3D. 11:48.546 --> 11:50.927 [SPEAKER_00]: Like we're not like they're a weeded on the product team. 11:50.967 --> 11:55.790 [SPEAKER_00]: Here, Bluebeam, we don't view it as like a 2D versus 3D reality of like which one's going to win. 11:56.030 --> 11:58.011 [SPEAKER_00]: They both solved different problems at different times. 11:58.091 --> 12:01.913 [SPEAKER_00]: We actually had a great guest speaker at our unbound event in Cologne, Germany. 12:02.033 --> 12:06.856 [SPEAKER_00]: He was

interestingly enough working on a BIM project in North Africa. 12:07.076 --> 12:10.018 [SPEAKER_00]: And he said, this quote will probably stick to be forever. 12:10.058 --> 12:13.320 [SPEAKER_00]: He said, 3D is where the design happens, 2D is where the decisions are made. 12:13.920 --> 12:25.690 [SPEAKER_00]: And it was just such a sort of a clear moment where it was around the 2D table that they were solving these complex problems together of how the geometry within the structure relates to each other. 12:25.790 --> 12:28.252 [SPEAKER_00]: With that said, we just released with Blooming Max. 12:28.272 --> 12:30.574 [SPEAKER_00]: We just released what we call connected sessions to Reddit. 12:31.254 --> 12:44.964 [SPEAKER_00]: So up until that point, every markup that you ever placed within Bluebeam was had to be viewed within one of our four client apps, which is Bluebeam review, which most people know on a PC, our web app, our iOS, our Android app. 12:45.384 --> 12:50.088 [SPEAKER_00]: What we did is we built a sort of a middleware or conversion tool that will take a markup. 12:50.788 --> 12:54.650 [SPEAKER_00]: out of the 2D space and convert it to 3D geometry within Revit. 12:54.830 --> 12:58.851 [SPEAKER_00]: So what you can do is you can now connect a studio session to your model. 12:58.991 --> 13:00.012 [SPEAKER_00]: You know, produce those sheets. 13:00.192 --> 13:05.074 [SPEAKER_00]: You can then mark them up in 2D, just like you would regularly water clouds and call outs and all the stuff you do. 13:05.414 --> 13:08.655 [SPEAKER_00]: And those markups now convert right back into the model in Revit. 13:08.735 --> 13:10.796 [SPEAKER_00]: They show up on the 2D sheets and 3D sheets. 13:11.016 --> 13:11.917 [SPEAKER_00]: It's a really cool 13:12.477 --> 13:13.017 [SPEAKER_00]: technology. 13:13.057 --> 13:17.180 [SPEAKER_00]: All that to say, that's new in the last three, four months with the launch of Blubi Max. 13:17.360 --> 13:29.048 [SPEAKER_00]: So we're certainly very much supportive of the future of 3D and the connection between accessibility, the broader workforce, 2D and also the rich information with the 3D model. 13:29.128 --> 13:38.234 [SPEAKER_01]: I mean, again, coming from the outside in, there was this feeling like Bim had to win or, you know, or 2D had to win and there was having to be a winner and 13:38.694 --> 14:00.865 [SPEAKER_01]: And when I got here, you know, and by the way, during my time in the 10 years I've been doing this in construction tech, I've moved from oh yeah, we're going to go full 3D life's going to be 3D to realizing that's just not feasible it's not feasible because of the technology and the other things because of what you said, it's a right person, the right format, the right time and to get things built. 14:01.105 --> 14:03.707 [SPEAKER_01]: And so this is what we're doing, but it is. 14:04.327 --> 14:05.868 [SPEAKER_01]: can we connect all of that? 14:06.128 --> 14:09.549 [SPEAKER_01]: And can we

make this a better world for construction? 14:09.589 --> 14:18.813 [SPEAKER_01]: And I think if you go to the core of what Bluebeam is, you know, we were here to help solve problems for the industry that the industry was facing. 14:18.833 --> 14:22.914 [SPEAKER_01]: That's why, you know, it started in 2017 on the show with connecting workflows. 14:23.074 --> 14:27.816 [SPEAKER_01]: We have been a part of that process and that sort of fabric that connects 14:30.997 --> 14:39.844 [SPEAKER_01]: And even owners to hand over at the end along the way and solving problems in there as well, which is gives us something that most don't have that width, right? 14:39.864 --> 14:43.727 [SPEAKER_01]: We're really wide and have multiple areas that we help. 14:43.967 --> 14:50.392 [SPEAKER_01]: So it's really a cool growth then to see like, hey, we don't want to take away what's right for you. 14:50.412 --> 14:51.233 [SPEAKER_01]: We want to connect to you. 14:51.333 --> 14:52.474 [SPEAKER_00]: I know we're just kind of jumping around. 14:52.514 --> 15:02.260 [SPEAKER_00]: This just makes me think about where we're going from an even an AI perspective, come to find out, shocker, AI is a really good at reading data and writing to data. 15:02.441 --> 15:08.585 [SPEAKER_00]: And so one of the core functions within 2D workflows is the rich commenting and markup data. 15:09.212 --> 15:11.214 [SPEAKER_00]: connecting that into the 3D data. 15:11.474 --> 15:14.076 [SPEAKER_00]: I would argue six months ago that was really hard to do. 15:14.557 --> 15:22.724 [SPEAKER_00]: You now can import data in using AI agents into BlueBean and pull those out in and out of 3D models and vice versa. 15:22.884 --> 15:24.245 [SPEAKER_00]: It's this whole new world. 15:24.425 --> 15:25.766 [SPEAKER_00]: And some of it's very early. 15:26.027 --> 15:30.631 [SPEAKER_00]: It's the direction we're going in which their candy agents to monitor activity 15:31.491 --> 15:35.474 [SPEAKER_01]: that move data between 2D and 3D in different applications. 15:35.734 --> 15:54.785 [SPEAKER_00]: Very early days of that, but we're starting to see the early implications of that even some proof of concepts that I've seen from early customers have been really fascinating in ways that just honestly, we're not even technologically possible a year ago and now that is available through self-service technology right off of our web store, right? 15:54.885 --> 15:55.906 [SPEAKER_00]: I mean, that's where we're like 15:58.318 --> 16:17.175 [SPEAKER_01]: Yeah, we've really come into some I've been doing this to and it's you know, we had that poor if PDF right portable document format and I don't think people realized and I know they didn't that there is all that rich data we call it markups right but they are physical things that might represent almost anything it can be a measurement it can be. 16:17.976 --> 16:25.558 [SPEAKER_01]: a question, it can be all sorts of different things, but we're generating data and

so I'm now going to call it the perfect data format. 16:25.639 --> 16:38.763 [SPEAKER_01]: The PDF is now the perfect data format because it's now unlocked in a way that I could not have imagined 18 months ago in any shape or form and then sitting here and you know being a part of this and realizing 16:39.643 --> 16:41.103 [SPEAKER_01]: what that's going to unlock. 16:41.283 --> 16:42.104 [SPEAKER_01]: And who knew? 16:42.124 --> 16:58.587 [SPEAKER_01]: I mean, maybe some of you guys did back there knew that someday that what we call the markups would become seriously important data over time and drives valuable insights into the execution of building, the decision making in the process. 16:58.647 --> 17:00.327 [SPEAKER_01]: But you have a hard problem, right? 17:00.367 --> 17:03.708 [SPEAKER_01]: Because people love bluebeats. 17:03.988 --> 17:10.813 [SPEAKER_01]: Let's just be honest, we have some of the coolest fans out there, but this is their baby. 17:10.913 --> 17:18.138 [SPEAKER_01]: So how is that sitting in your seat where you're trying to move ahead, right? 17:18.218 --> 17:21.500 [SPEAKER_01]: And stay up, but you're messing with people's baby. 17:21.640 --> 17:23.121 [SPEAKER_01]: So how's that been? 17:23.862 --> 17:26.384 [SPEAKER_00]: It's good, like we want to do right by our users. 17:26.784 --> 17:31.227 [SPEAKER_00]: And our users have a very visceral approach to our technology. 17:31.467 --> 17:33.369 [SPEAKER_00]: It solves big problems for them. 17:33.389 --> 17:36.391 [SPEAKER_00]: It gets them out of some binds and various ways. 17:36.611 --> 17:42.276 [SPEAKER_00]: It gives them voice in a way to maybe what their trade is or their, again, back to their intent. 17:42.476 --> 17:49.242 [SPEAKER_00]: They love the fact that the colors are so vastly customizable that you can change the hex codes of the fill 17:49.902 --> 17:54.723 [SPEAKER_00]: to a certain opacity of your callouts and text boxes to align with your standards in some way. 17:55.224 --> 17:57.724 [SPEAKER_00]: Great, that's Bluebeak, that's what it's intended to do. 17:57.764 --> 17:58.784 [SPEAKER_00]: It just goes that deep. 17:58.905 --> 18:06.967 [SPEAKER_00]: I've seen drawing sets that are look to be works of art in terms of the graphical and visual and colorization that's being done. 18:07.227 --> 18:09.507 [SPEAKER_00]: We don't take any of that lightly at all. 18:09.948 --> 18:15.549 [SPEAKER_00]: Like we view our role as product managers and designers and engineers with the utmost respect. 18:15.929 --> 18:18.070 [SPEAKER_00]: And we also understand where stewards 18:18.818 --> 18:24.261 [SPEAKER_00]: of this technology and the industry that has a lot of people banking on it on a daily basis. 18:24.461 --> 18:26.222 [SPEAKER_01]: I'll tell you one of the big conflicts. 18:26.282 --> 18:27.483 [SPEAKER_01]: I'll say that we sort of live in. 18:28.103 --> 18:39.089 [SPEAKER_00]: It's this reality of someone's going to open that app today and expect it to do the exact same thing it did yesterday because that's how they're running their business and that's what they need to do. 18:39.902 --> 18:44.965 [SPEAKER_00]: Secondly, there's also a side of them that want to open that app and it to do a new thing. 18:45.565 --> 18:49.027 [SPEAKER_00]: And whatever that new thing is, the next evolution of the, it's a paradox in a way. 18:49.207 --> 18:51.709 [SPEAKER_00]: But at the same time, it's just a reality that we live in. 18:51.989 --> 18:55.431 [SPEAKER_00]: One thing where I'm happy to share it here, we're shipping bullet points and numbering. 18:55.631 --> 18:57.973 [SPEAKER_00]: And like, that's been something that people have asked for a long time. 18:58.233 --> 19:01.735 [SPEAKER_00]: And you know, like, you know, this is sound off the alarm from the fireworks. 19:01.795 --> 19:05.477 [SPEAKER_00]: And there's a lot of technical reasons that we had to go into that to be able to build that out. 19:05.657 --> 19:09.299 [SPEAKER_00]: I've seen it, I've seen all I own eyes, it's great, works, looks just like you would want it to work. 19:09.379 --> 19:12.922 [SPEAKER_00]: But it's that's type of stuff that users are like, great, bold points of numbering. 19:13.242 --> 19:17.385 [SPEAKER_00]: I wanted that forever, Blooming's finally got it, great, cool, users are going to love it. 19:17.505 --> 19:20.407 [SPEAKER_00]: And then there's questions of like, okay, what about AI intelligence? 19:20.427 --> 19:24.950 [SPEAKER_00]: And how can it understand everything about my drawing and create these relationships across all my files? 19:25.370 --> 19:28.792 [SPEAKER_00]: And you're just like, okay, these are the realities of what product development, 19:30.313 --> 19:30.473 [SPEAKER_00]: is. 19:30.593 --> 19:37.819 [SPEAKER_00]: And those two things aren't necessarily in conflict with each other, but the very different approaches to where the product needs to go and how we're going to get there. 19:37.919 --> 19:45.264 [SPEAKER_00]: So I would argue that innovation for us is both in the practical realm and also in the more conceptual board leaning. 19:45.365 --> 19:49.608 [SPEAKER_00]: So lots of great stuff on the horizon, but I'll say I crew that I that I work with. 19:50.148 --> 19:53.449 [SPEAKER_00]: They have the utmost respect for our users for the industry. 19:53.589 --> 19:56.150 [SPEAKER_00]: They don't take their job lightly in the slightest. 19:56.350 --> 20:03.633 [SPEAKER_00]: And I'll say, I am constantly amazed at the level of respect they have for what they're doing. 20:03.673 --> 20:07.034 [SPEAKER_00]: That this just isn't like another PM job or another design gig. 20:07.214 --> 20:14.257 [SPEAKER_00]: This is literally dealing with the tools and the structure that power a global industry on Blooming. 20:14.377 --> 20:17.298 [SPEAKER_00]: And that's not lost on anybody here within the Blooming ranks. 20:17.585 --> 20:22.727 [SPEAKER_01]: Well, and that's what's great about being here

and being out on the front edge where I get to be in the industry itself. 20:22.767 --> 20:24.427 [SPEAKER_01]: And it's funny, you talk about that paradox. 20:24.487 --> 20:28.249 [SPEAKER_01]: That paradox exists in this industry to the end of degree, right? 20:28.589 --> 20:36.772 [SPEAKER_01]: I will sit in a room and I will be talking to an advanced group that is really looking for how are you gonna automate things? 20:36.852 --> 20:38.612 [SPEAKER_01]: How are you gonna help me collect data? 20:38.672 --> 20:45.175 [SPEAKER_01]: How are you gonna help me close loops and really advance by business and really move my entire business forward? 20:46.575 --> 20:51.076 [SPEAKER_01]: at a foundational layer of that along with my other tools that I'm bringing in. 20:51.216 --> 21:03.260 [SPEAKER_01]: And then, honestly, 10 minutes later, I could be sitting down with a small contractor that's got 10 people, two trucks and wants to deliver and wants to be better. 21:03.400 --> 21:05.581 [SPEAKER_01]: Not that they don't care, they're not there, right? 21:05.841 --> 21:08.962 [SPEAKER_01]: And, but yet, the same tool they're going to open up. 21:10.095 --> 21:12.197 [SPEAKER_01]: And in some respects, the same tool, right? 21:12.217 --> 21:17.721 [SPEAKER_01]: It might be review, somebody might open Macs, you know, whatever, they're going to see this logo. 21:17.741 --> 21:18.842 [SPEAKER_01]: And they're going to go blooby. 21:19.823 --> 21:23.305 [SPEAKER_01]: And so we, again, that's a huge piece. 21:23.766 --> 21:27.408 [SPEAKER_01]: And I want to roll this back, because I want to get to talking about Macs. 21:27.508 --> 21:32.952 [SPEAKER_01]: But something that I felt before I came on board was like, what is blue beam up to? 21:33.353 --> 21:34.654 [SPEAKER_01]: What are they doing? 21:35.174 --> 21:37.536 [SPEAKER_01]: And exactly that, like release over release. 21:37.556 --> 21:38.636 [SPEAKER_01]: So like, what are we doing? 21:38.897 --> 21:43.620 [SPEAKER_01]: You had to address the past and really refactor. 21:43.800 --> 21:59.930 [SPEAKER_01]: I know you don't want to give away the secret sauce, but talk a little bit about that extended process because I don't think, first of all, as somebody who's done this before in another world, refactoring and keeping something working that people love without breaking it. 22:00.150 --> 22:02.091 [SPEAKER_01]: That's a really hard to do. 22:05.220 --> 22:07.981 [SPEAKER_01]: If you do your job really, really well, nobody notices. 22:08.161 --> 22:08.801 [SPEAKER_01]: That's the beauty. 22:09.241 --> 22:11.482 [SPEAKER_01]: You don't want them to notice. 22:11.522 --> 22:13.582 [SPEAKER_01]: So if they're noticing, something's wrong. 22:13.802 --> 22:19.363 [SPEAKER_01]: So talk a little bit about that refactor path and maybe open people's eyes to what it took. 22:19.483 --> 22:20.304 [SPEAKER_01]: And why we did it? 22:20.444 --> 22:23.464 [SPEAKER_00]: To take in all of that, you have to put yourself back in 2002. 22:23.524 --> 22:25.945 [SPEAKER_00]: July and next year, we'll be our 25th anniversary. 22:26.085 --> 22:28.267 [SPEAKER_00]: Tekken only was a very different time back then. 22:28.627 --> 22:36.274 [SPEAKER_00]: You know, I can't really, you know, we'll see something on YouTube or whatever from 2002 is like kind of grainy footage, they kind of flutty like a glism like, I remember that. 22:36.294 --> 22:40.117 [SPEAKER_00]: I was like out of college at that point, but it feels like such a long time ago. 22:40.398 --> 22:41.639 [SPEAKER_00]: That's when Bluebeam started. 22:42.219 --> 22:45.522 [SPEAKER_00]: So we're about to go into work in our 25th year here. 22:45.882 --> 22:47.824 [SPEAKER_00]: And what we've had to do is, 22:48.865 --> 22:57.776 [SPEAKER_00]: do exactly what you describe by taking technology that is used every day in his value and it has a level of expectation and evolve that to solve problems in a new way. 22:57.897 --> 23:04.725 [SPEAKER_00]: What we didn't want to do is, as I say, for the baby out on bathwater or completely rewrite things beyond what some... 23:05.466 --> 23:09.388 [SPEAKER_00]: users, or maybe even what some industry extras might have expected us to do 10 years ago. 23:09.428 --> 23:13.710 [SPEAKER_00]: So for example, 10 years ago, obviously huge push to go web and mobile makes a lot of sense. 23:13.930 --> 23:16.852 [SPEAKER_00]: We too have also gone web and mobile, I'll describe that in a moment. 23:17.072 --> 23:21.034 [SPEAKER_00]: But there's also a separate superpower that comes along with local processing. 23:21.374 --> 23:31.897 [SPEAKER_00]: So by being able to put the power of a local proprietary library that we've developed onto a local machine, you start to unlock new possibilities. 23:31.917 --> 23:43.540 [SPEAKER_00]: In fact, I've seen some early releasing this, but we've since really interesting examples of local AI models running on fairly high-powered yet accessible devices. 23:44.160 --> 23:46.821 [SPEAKER_00]: And you think there's an interesting future here where 23:47.721 --> 23:50.184 [SPEAKER_00]: What if there is a component of AI that runs local? 23:50.304 --> 23:59.074 [SPEAKER_00]: The compute gets to certain point, the cost gets to certain point, and the parameters of them all get to certain point, then all of a sudden you're doing some really interesting things locally. 23:59.154 --> 24:05.602 [SPEAKER_00]: So the whole idea of technology moving exclusively web-emobile, I would actually say it is an anti-patter. 24:05.762 --> 24:08.283 [SPEAKER_00]: It's not necessarily what is required to be now. 24:08.543 --> 24:15.507 [SPEAKER_00]: I will say that there are very important pieces of local technology that need to be connected into web-based sources. 24:15.527 --> 24:17.488 [SPEAKER_00]: So, for example, we talked about Studio. 24:17.988 --> 24:21.390 [SPEAKER_00]: We're working on a couple really interesting things that are going to launch next

year. 24:21.410 --> 24:23.250 [SPEAKER_00]: We're going to announcement on bound. 24:23.591 --> 24:24.351 [SPEAKER_00]: See you in Vegas. 24:24.631 --> 24:27.953 [SPEAKER_00]: Really cool stuff that does not use local compute. 24:28.113 --> 24:29.914 [SPEAKER_00]: But uses the power of the interwebs. 24:30.094 --> 24:30.654 [SPEAKER_00]: So to speak. 24:30.754 --> 24:32.515 [SPEAKER_00]: Some really cool stuff that's on the rise of the so. 24:32.775 --> 24:34.717 [SPEAKER_00]: All that to say, we've had to do that evolution. 24:34.737 --> 24:39.381 [SPEAKER_00]: So again, it's a yes and it's not, you know, this is the end of local desktop. 24:39.481 --> 24:41.042 [SPEAKER_00]: It's what does it also mean? 24:41.443 --> 24:50.911 [SPEAKER_00]: If I'm looking at a file on my local desktop, how can I in a matter of two clicks view that on my mobile device, send that to you and have you access that on web? 24:51.392 --> 24:52.993 [SPEAKER_00]: Got to even a couple of things beyond that. 24:53.253 --> 24:54.835 [SPEAKER_00]: I don't want to go into too much detail on it, but 24:55.135 --> 24:59.537 [SPEAKER_00]: Where could you then see a here or there or do this or that with these people in this context? 24:59.657 --> 25:16.963 [SPEAKER_00]: That's who us is this broader thing we've been calling Louie Menneware and it's the whole idea that I can get to the people, the information, the documents I need, regardless of the device them on, the security requirements them on, if I'm offline or online, that is, that's the story of Louie Menneware. 25:17.084 --> 25:23.426 [SPEAKER_00]: We've got a lot more work to do, by no means is that done, but we've made some incredible progress and a lot of hats off to the team for that. 25:23.546 --> 25:30.654 [SPEAKER_00]: We just recently launched a whole series of updates to our web and mobile applications, specifically iOS and Android for tool sets and measurements. 25:31.095 --> 25:34.138 [SPEAKER_00]: War that's coming here in the near future Studio Sessions. 25:34.719 --> 25:39.805 [SPEAKER_00]: And Studio Projects is now fully supported across our web, iOS, and Android applications. 25:39.865 --> 25:44.270 [SPEAKER_00]: So you can start a Studio Session, send out a URL, and even if the person isn't 25:44.710 --> 26:08.298 [SPEAKER_00]: Even a paying subscriber, they can log in with a no cost blew me my D and access the files on their Android device Mark it up and if that's a connected session you've got a no cost user On an Android device marking up 2D drawing that pipes immediately back into a 3D model That's what blew me anywhere is that that's available today actually so that's what blew me anywhere means for us So we're gonna continue to expand along all those lines 26:08.572 --> 26:12.857 [SPEAKER_01]: Yeah, you're going to go down that line and to everybody who's listening, you've heard me say this for years. 26:13.057 --> 26:24.130 [SPEAKER_01]: And now I think you'll start to see the connection and why

this was such a cool thing for me to get to do is that it's right person, right place, right time, right information. 26:24.191 --> 26:27.334 [SPEAKER_01]: And that was never to be owned by anyone. 26:28.055 --> 26:34.801 [SPEAKER_01]: application, and that's exactly what you're talking about, a detailer sitting there in rev it and needs this. 26:34.821 --> 26:40.887 [SPEAKER_01]: And a person in the field is looking at something that's been installed and needs that answer. 26:40.967 --> 26:44.830 [SPEAKER_01]: And they're on a scaffolding or they're on a lift. 26:44.931 --> 26:45.011 [SPEAKER_01]: And 26:45.491 --> 26:51.796 [SPEAKER_01]: How can we make all this quick and for the right person in the right place and these technologies are doing it? 26:51.876 --> 26:58.742 [SPEAKER_01]: And I love that you went to the idea of, hey, desktop, there's certain things you can do. 26:59.302 --> 27:04.606 [SPEAKER_01]: I want everybody to take a step back and just think, like, I have been saying this for a very long time and so is this show. 27:05.147 --> 27:07.348 [SPEAKER_01]: There's a sign curve to the way this goes, right? 27:07.368 --> 27:11.291 [SPEAKER_01]: We're always going out to the web, onto the desktop, because 27:12.212 --> 27:15.995 [SPEAKER_01]: the reality is there's power in different places at different times for the right thing. 27:16.355 --> 27:21.238 [SPEAKER_01]: If you think about it to my IT geeks, we went all sass and everybody said, it's all cloud. 27:21.338 --> 27:26.521 [SPEAKER_01]: And I even had a guy tell me stop doing your job as an IT person because it's going to be gone, right? 27:26.541 --> 27:27.662 [SPEAKER_01]: Because everything's going to be in the cloud. 27:27.682 --> 27:28.522 [SPEAKER_01]: You don't need to do anything. 27:28.783 --> 27:29.803 [SPEAKER_01]: We all know that's not true. 27:30.183 --> 27:34.586 [SPEAKER_01]: So, but a lot of that power was then brought in local models for computer 27:37.388 --> 27:37.968 [SPEAKER_01]: there, right? 27:38.068 --> 27:45.512 [SPEAKER_01]: And the computer can do those things now, especially with, you know, processing the way it is in that future of being both. 27:46.012 --> 27:48.473 [SPEAKER_01]: It's not, yes, this only. 27:48.553 --> 27:53.395 [SPEAKER_01]: It's yes, and then I think it ties to your PD, you know, to your 2D and 3D. 27:53.415 --> 27:53.755 [SPEAKER_01]: That's right. 27:53.975 --> 27:55.996 [SPEAKER_01]: Yeah, ties to the edge into the cloud. 27:56.056 --> 28:00.778 [SPEAKER_01]: It ties to like stop thinking and absolutes, think in possibilities. 28:01.198 --> 28:01.358 [SPEAKER_01]: Yeah. 28:01.458 --> 28:03.739 [SPEAKER_01]: And don't cut yourself off from a possibility. 28:03.839 --> 28:04.460 [SPEAKER_01]: And I think that's 28:05.140 --> 28:25.566 [SPEAKER_01]: important to that, you know, as a leader in the industry, and we've been around for a very long time, and I do believe that, you know, it's funny because we had connected workflows, and then we had, I had Usman come on and really talk about, respecting the intelligence, respecting the industry, respecting what it knows, in order to keep delivering. 28:25.706 --> 28:32.428 [SPEAKER_01]: I think we hold that responsibility, you talked about it, our product folks hold that responsibility. 28:33.148 --> 28:40.611 [SPEAKER_01]: our customer success, our customer delight, our count managers, everybody holds that at heart. 28:40.651 --> 28:48.135 [SPEAKER_01]: There's this driving force that we play a significant role and have a duty to keep that up for the industry. 28:48.235 --> 28:50.376 [SPEAKER_01]: It's so cool to see it permeating. 28:50.716 --> 28:51.096 [SPEAKER_00]: I love it. 28:51.236 --> 28:57.619 [SPEAKER_00]: So I, this might be a little bit of a original story but growing up in the Los Angeles area a few years back. 28:57.679 --> 29:01.381 [SPEAKER_00]: So folks got together and decided to build the tallest building west of the Mississippi. 29:01.401 --> 29:02.641 [SPEAKER_00]: It's the Wilshire Grand, right? 29:02.941 --> 29:04.562 [SPEAKER_00]: And it's now the Korean air towers. 29:04.582 --> 29:07.823 [SPEAKER_00]: I think it's 72 stories is in downtown Los Angeles. 29:08.123 --> 29:13.446 [SPEAKER_00]: Some really powerful tools, a lot of brain power and intelligence and experience. 29:14.206 --> 29:17.529 [SPEAKER_00]: and they built a prototype that will probably never get built again. 29:17.729 --> 29:19.190 [SPEAKER_00]: It's that one spot in time. 29:19.230 --> 29:27.816 [SPEAKER_00]: I think they did it in 36 months and they could do it again, Jeff, if you had a few billion dollars or whatever to hire, then they'll put one in your backyard, right? 29:27.836 --> 29:41.547 [SPEAKER_00]: It's like these are incredibly talented, educated, skillful, experience, crafts people, architects, designers, engineers, all the way up and down, that can do this and they can do it all day long. 29:42.634 --> 29:45.977 [SPEAKER_00]: And yet, we hear these stories about construction slow to adopt technology. 29:46.477 --> 29:48.339 [SPEAKER_00]: That's a construction technology problem. 29:48.459 --> 29:49.760 [SPEAKER_00]: That's not a workforce problem. 29:49.860 --> 29:51.261 [SPEAKER_00]: That's not the user's problem. 29:51.482 --> 29:58.248 [SPEAKER_00]: It's because if you look a lot of technology that's out there, it's not solving a real problem that customers need. 29:58.868 --> 30:04.073 [SPEAKER_00]: And so the truth is, I think our customers have demands that they will continue to build our 30:07.035 --> 30:10.239 [SPEAKER_00]: We have customers that have been around for 150 years. 30:10.539 --> 30:12.341 [SPEAKER_00]: They've been doing this since the 1800s. 30:12.641 --> 30:15.584 [SPEAKER_00]: And they will continue to do that for the next 150 years. 30:16.025 --> 30:20.129 [SPEAKER_00]: We just have to be able to provide them tools that are better than the status quo. 30:20.149 --> 30:21.571

[SPEAKER_00]: They're better than what they're able to do. 30:21.631 --> 30:27.157 [SPEAKER_00]: And look, that's the type of thing that keeps us up a night that we're making sure that we're actually building that level of expectation. 30:27.717 --> 30:32.799 [SPEAKER_00]: I actually do fully reject the notion of this industry is being maybe behind or slow to adopt technology. 30:33.119 --> 30:39.322 [SPEAKER_00]: That actually may be true in the surface, but I think the reality is they have very high expectations for what technology can actually do for them. 30:39.462 --> 30:44.184 [SPEAKER_00]: It's incumbent on us as technology providers to actually meet that level of expectation. 30:44.475 --> 30:46.057 [SPEAKER_01]: Yeah, I mean, I've been saying this for years. 30:46.118 --> 30:47.680 [SPEAKER_01]: Look around at the world around you. 30:47.840 --> 30:49.563 [SPEAKER_01]: It is not less complicated. 30:49.583 --> 30:51.986 [SPEAKER_01]: It is not less technologically advanced. 30:52.087 --> 30:54.751 [SPEAKER_00]: It is far more and there was people who built that. 30:54.871 --> 30:58.336 [SPEAKER_01]: And so it's our it's a definitional issue and how we define what. 30:59.598 --> 31:20.550 [SPEAKER_01]: You know innovation and technology adoption are right we see it as an app on our phone we see it as an app on our computer it is not that it is integrating fabrication it's integrating manufacturing mindsets it's changing to new tools right the tools if you look at them are so advanced I've towards some of the tool facilities and just see the new advancements in them and what they can do. 31:20.770 --> 31:32.019 [SPEAKER_01]: And it's really funny that you went in the wheelchair grand because MEP innovation was there a couple years ago and while it's an incredible building and I've been to the top I was also stuck in their elevator for 30 minutes. 31:33.044 --> 31:36.807 [SPEAKER_01]: Because they have a one of the kind that I know of, there's probably a few about there. 31:37.047 --> 31:38.228 [SPEAKER_01]: They are dual level. 31:38.868 --> 31:42.711 [SPEAKER_01]: So they actually have two cars per elevator shaft. 31:43.231 --> 31:45.453 [SPEAKER_01]: And you touch a button and then you get in. 31:45.833 --> 31:51.817 [SPEAKER_01]: What you don't know is if somebody gets out and you're not paying attention and you get into the one they got out, that might not be the one. 31:52.157 --> 31:54.959 [SPEAKER_01]: And then you just ride up and down for 30 minutes. 31:55.540 --> 31:58.522 [SPEAKER_01]: And yours truly was in there and went flying out as soon. 31:58.642 --> 31:59.763 [SPEAKER_01]: And let me tell you. 32:00.263 --> 32:07.111 [SPEAKER_00]: Whew, so sometimes the giant intent is great, but sometimes users' user experience is very different. 32:07.172 --> 32:14.400 [SPEAKER_01]: To anybody else who's had that experience there, but also an absolute marvel when it comes to what they actually built. 32:14.601 --> 32:15.682 [SPEAKER_01]: I wanna talk max. 32:15.922 --> 32:22.287 [SPEAKER_01]: I'm going to put you on the hot seat later for a rapid fire and some other stuff, but first and foremost, what's max? 32:22.647 --> 32:23.127 [SPEAKER_01]: What is it? 32:23.367 --> 32:24.328 [SPEAKER_01]: What are we doing? 32:24.708 --> 32:25.469 [SPEAKER_01]: What is it? 32:25.489 --> 32:26.309 [SPEAKER_01]: What is it doing? 32:26.509 --> 32:27.610 [SPEAKER_00]: That's a great place to start. 32:27.710 --> 32:30.032 [SPEAKER_00]: I could give you the big story, but let me give you a small story. 32:30.212 --> 32:34.835 [SPEAKER_00]: Every markup that's ever been placed in the Blooming World for the last, let's call it 25 years. 32:34.855 --> 32:37.437 [SPEAKER_00]: I'm rounding up six months, but let's let's call it that. 32:37.597 --> 32:46.859 [SPEAKER_00]: Every market that's ever been placed when placed by a user, sitting in front of a machine with a mouse, clicking, vertices, you know, points creating this object, cool, fine, fair enough, good enough. 32:47.179 --> 32:50.780 [SPEAKER_00]: Max is the first time that you be actually now I have an AI, create your markers for you. 32:51.000 --> 32:51.600 [SPEAKER_00]: What does that mean? 32:52.320 --> 32:53.000 [SPEAKER_00]: What AI? 32:53.280 --> 32:54.121 [SPEAKER_00]: Where are the markups? 32:54.201 --> 32:54.901 [SPEAKER_00]: What are they targeting? 32:54.941 --> 32:55.661 [SPEAKER_00]: What do they say? 32:55.721 --> 32:56.641 [SPEAKER_00]: What's the data coming in? 32:56.661 --> 32:57.401 [SPEAKER_00]: What's the data coming out? 32:57.761 --> 33:00.542 [SPEAKER_00]: All that gets to be defined by the user in the work process. 33:01.650 --> 33:02.991 [SPEAKER_00]: simply put that's max. 33:03.291 --> 33:10.755 [SPEAKER_00]: It's a new evolution on top of what we have done for the last two decades in a way to unlock new ways of working. 33:10.795 --> 33:12.316 [SPEAKER_00]: I'll give you another very specific example. 33:12.416 --> 33:16.199 [SPEAKER_00]: This features we've talked about the connected sessions and other things we can kind of go through that. 33:16.879 --> 33:20.420 [SPEAKER_00]: But for many years, we were kicking around the idea. 33:20.440 --> 33:26.283 [SPEAKER_00]: We're gonna go super deep here on a few layers of product management and review workflows. 33:26.383 --> 33:29.924 [SPEAKER_00]: We always wanted to do an Excel import into Markup data. 33:30.044 --> 33:35.827 [SPEAKER_00]: Now, there were some Excel imports that you could do into various tools that types, like our punch key symbols and things like that. 33:35.907 --> 33:42.069 [SPEAKER_00]: But being able to bring data out of an external source, let's just call it an Excel spreadsheet into your Markup data. 33:42.089 --> 33:43.770 [SPEAKER_00]: It was actually a really hard problem to solve. 33:44.210 --> 33:59.321 [SPEAKER_00]: It's a data mapping issue where you have to sort of map all of the cells and rows and columns you have to

analyze your spreadsheet and then you have then have to go to your markups and analyze your markups list, would you have to add more columns or whatever it might be, it was just something that that was very challenging to solve. 34:00.102 --> 34:04.784 [SPEAKER_00]: and something that a number of us had been kicking around for frankly years, just trying to think how to do it. 34:04.884 --> 34:08.285 [SPEAKER_00]: Come to find out, AI is really good at mapping data. 34:08.966 --> 34:20.050 [SPEAKER_00]: That's so, back to the whole idea of we introduced a couple basic commands in Macs that essentially let you update market properties and create custom columns. 34:20.590 --> 34:24.252 [SPEAKER_00]: And it's very sublime on the surface if you think, well, update custom columns, what does that mean? 34:24.272 --> 34:24.812 [SPEAKER_00]: Because he's well, 34:25.372 --> 34:32.374 [SPEAKER_00]: You can now pick any external data source and have that map and create new columns within your markups list to assign data against. 34:33.195 --> 34:34.516 [SPEAKER_00]: We'll update market property. 34:34.536 --> 34:35.357 [SPEAKER_00]: What does that mean? 34:35.377 --> 34:39.101 [SPEAKER_00]: You can change your market from red to blue, okay? 34:39.261 --> 34:46.067 [SPEAKER_00]: But you can also now assign any amount of additional data to those markets from an outside source. 34:46.888 --> 34:47.589 [SPEAKER_00]: I'll give you an example. 34:47.609 --> 34:50.532 [SPEAKER_00]: Like I was doing this plan or else of stuff. 34:50.652 --> 34:55.537 [SPEAKER_00]: I view it as my job to spend at least 30 minutes a day in some form of our technology. 34:55.557 --> 34:56.458 [SPEAKER_00]: Be it an integration. 34:57.078 --> 34:59.080 [SPEAKER_00]: or our technology. 34:59.140 --> 35:07.107 [SPEAKER_00]: It's one of my commitments to our customers that in my role, I feel it's very important that I'm actually clicking on our tech using our stuff. 35:07.127 --> 35:09.910 [SPEAKER_00]: So that's something, and it also sort of brings me joy. 35:09.930 --> 35:17.076 [SPEAKER_00]: It kind of fills up my meter, so to speak, where I could I can go and feel like I'm staying very close to the technology still. 35:18.089 --> 35:23.271 [SPEAKER_00]: So one thing that you can do is you can go into a document. 35:23.291 --> 35:28.413 [SPEAKER_00]: There's a takeoff, and just a single length, and that length might be like, we'll call it 100 meters. 35:28.873 --> 35:34.215 [SPEAKER_00]: You can then go into an AI tool and say, look at that length of 100 meters. 35:34.315 --> 35:40.358 [SPEAKER_00]: And I want you to build out all the assemblies of a concrete masonry unit, a CMU wall. 35:41.398 --> 36:06.310 [SPEAKER_00]: according to typical standards and create columns for the the bags of of of cement that I need that total linear feet of grout the weight of grout the labor hours according to standard known labor factors for that type of wall and then you just simply add in a height

and it will go through and map all that information go pull that off the internet and begin creating your columns and then start 36:10.652 --> 36:14.734 [SPEAKER_00]: uh uh material we can pull in that assembly and start calculating that. 36:15.275 --> 36:21.418 [SPEAKER_00]: That was the type of thing it was completely unheard of six months ago and is now just a few prompts away. 36:22.359 --> 36:23.460 [SPEAKER_00]: That's what maxes. 36:23.820 --> 36:32.465 [SPEAKER_00]: It's the ability to take that external information and have that influence uh the the the reality of what either commenting is and estimation the design 36:33.085 --> 36:37.007 [SPEAKER_00]: And then from there, there's that other step of now that I have the state at where do I need it to go. 36:37.587 --> 36:50.452 [SPEAKER_00]: So what we've seen is a lot of great activity in the market from our adjacent partners, application apps, the various companies that we work with that that either build within our ecosystem or also then. 36:50.912 --> 36:56.653 [SPEAKER_00]: Also providing MCPs where that information can now be in context and ages can take that and move that into other applications. 36:56.733 --> 37:03.735 [SPEAKER_00]: We have some early things that we're working on with HCSS and and heavy bid that I think yeah, that's right. 37:03.755 --> 37:05.675 [SPEAKER_00]: You get your HCSS hat there. 37:06.015 --> 37:13.257 [SPEAKER_00]: We have a lot of customers that are doing takeoffs in blue bean, but they're doing their estimates in and heavy bid. 37:13.377 --> 37:17.478 [SPEAKER_00]: How do we make that a little bit easier and how can AI kind of help map that data. 37:17.498 --> 37:18.618 [SPEAKER_00]: So more come on that. 37:19.238 --> 37:28.029 [SPEAKER_00]: You should come join us at either the HSS user group meeting in February or out on bound, but that's all I'll say for now about that. 37:28.364 --> 37:34.711 [SPEAKER_01]: I really like that because something I'm going to call out because I've been out there talking about it quite a bit and I carry two hats, right? 37:34.731 --> 37:35.372 [SPEAKER_01]: Like I do work. 37:35.392 --> 37:39.376 [SPEAKER_01]: My day job is blue beam, but I do, you know, the content group I cast. 37:39.416 --> 37:39.836 [SPEAKER_01]: I do this. 37:39.917 --> 37:50.148 [SPEAKER_01]: I'm out there in the industry, you know, thinking about it for them and a lot of what we're asking, a lot of what this AI has done and a lot of what construction technology has done over years is like add new things. 37:50.648 --> 37:53.271 [SPEAKER_01]: It's like, oh, I want to do that, but I'm going to do it over here. 37:53.291 --> 37:54.192 [SPEAKER_01]: You got to go do it over here. 37:54.212 --> 37:55.273 [SPEAKER_01]: You got to go learn this. 37:55.993 --> 38:00.097 [SPEAKER_01]: And it's one of the powerful things about blue beam is like, we did it on paper. 38:00.818 --> 38:04.101 [SPEAKER_01]: We really, truly held to digitizing that, right? 38:04.141 --> 38:06.603 [SPEAKER_01]: We held to the way you did it on paper. 38:07.404 --> 38:09.265 [SPEAKER_01]: is the way you do it in the plans now. 38:09.405 --> 38:19.790 [SPEAKER_01]: I watch people do take off measurements, markups, the whole thing that they were doing to learn the job and to quantify the job was very much digitized and it was very, it was frictionless. 38:19.930 --> 38:27.314 [SPEAKER_01]: It removed a lot of that friction and exactly what we're doing and I'm gonna have you explain MCP in a second for folks as well. 38:27.394 --> 38:35.458 [SPEAKER_01]: But what we're doing with Max is everything you just said, somebody can do and they can do it by hand, all of it. 38:36.312 --> 38:41.553 [SPEAKER_01]: It's just really tedious and takes a long time, but they can do it. 38:41.833 --> 38:46.914 [SPEAKER_01]: And it's a no thanks because again, it's not the value add. 38:46.995 --> 38:56.977 [SPEAKER_01]: The doing, the value add is the outcome and quantifying it and understanding the scope on the job and what it's gonna take to deliver it and do it and do those things. 38:57.857 --> 39:03.383 [SPEAKER_01]: So we're not asking you to do something that you never did before and learn something completely freaking different. 39:03.983 --> 39:09.009 [SPEAKER_01]: We're aligning it with the way you do it and we're trying to do it very frictionless. 39:09.869 --> 39:11.631 [SPEAKER_01]: And that's a powerful component. 39:11.691 --> 39:14.734 [SPEAKER_01]: And then like you said, we're waking up to things. 39:15.355 --> 39:17.676 [SPEAKER_01]: that we didn't know we're possible in our own tool. 39:17.716 --> 39:21.777 [SPEAKER_01]: Now, Kudos to you and the team for doing a lot of the prep work on it. 39:21.817 --> 39:25.498 [SPEAKER_01]: That again, we're not going to dive in all the refactoring, et cetera, that made it possible. 39:25.538 --> 39:27.818 [SPEAKER_01]: But that's an investment on our end. 39:28.238 --> 39:30.319 [SPEAKER_01]: And I want to be transparent. 39:30.359 --> 39:32.960 [SPEAKER_01]: That investment is because we care, right? 39:33.020 --> 39:41.162 [SPEAKER_01]: Because we're invested in this connected future with everyone, in this built world delivering projects. 39:41.402 --> 39:55.025 [SPEAKER_01]: we know that data centers, hyperscalers, advanced manufacturing are on the forefront right now, but labs and hospitals and treatment centers and housing and commercial real estate. 39:55.045 --> 39:57.446 [SPEAKER_01]: They're all there and they're all going to have their boom again. 39:57.666 --> 39:59.606 [SPEAKER_01]: What we're designing and building is for all of them. 39:59.846 --> 40:10.509 [SPEAKER_01]: And I think that's really important for me as a to align with the goals that I've always had of just helping this industry reach its true potential because it's limitless and it's awesome. 40:10.789 --> 40:23.274 [SPEAKER_01]: I get on a plane, I drive to the plane, I get on a runway, I cross a bridge, I look it, you know, my kids get so fat, look at all the cranes, you look at the construction, stop for a second and they're like, oh God, it's at the core of our company, right? 40:23.294 --> 40:24.395 [SPEAKER_01]: It's this guiding light. 40:24.475 --> 40:27.516 [SPEAKER_01]: To me, that's just important for the listeners to kind of understand. 40:27.656 --> 40:33.779 [SPEAKER_01]: Well, as you can probably tell, we'd a lot to geek out about with Luke Prescott and there was no way we were fitting it into one episode. 40:34.377 --> 40:44.088 [SPEAKER_01]: So we're going to hit pause right here and pick things back up in part two, where we dive even deeper into what's next for Bluebeam, the industry, and the technology shaping how we build. 40:44.389 --> 40:47.933 [SPEAKER_01]: Thank you for tuning in today to geek out for our review with Luke Prescott. 40:48.353 --> 40:53.359 [SPEAKER_01]: To read all our new stories learn more about our guest and listen to the show, visit the contentcrew.com. 40:53.860 --> 40:55.662 [SPEAKER_01]: This is the content crew signing out. 40:55.782 --> 40:59.666 [SPEAKER_01]: Until next time, enjoy the ride and geek out.