Transcript: Disrupting Ourselves in the Built Environment: Brickschain

I think a lot of people beat us up being in construction or construction tech. They keep on talking about the productivity gap and all of these things. Ultimately say that I think that we are innovative, hardworking industry that people don't think of enough because really everywhere you go, everywhere you drive, where you live, where you work is all part of the built world. We're all in this together and hopefully we can start breaking down the walls between the key players in the processes so that we can make it better for everyone.

You bring up a good point with IWMS solutions. The second owner, where are they really getting that information? The problem is that we start every asset procurement, like when you buy a building, we have to go and find out what's in this building. We have to do laser scans and asset audits and all of these things because we have no idea what we bought. The previous owner is not being malicious.

You can't take a pack saw and cut out of the IWM database the previous owner's data and send that over and nobody wants to give everything over. There needs to be something that sits above all that, this blockchain model. That's what we want BricksChain to be. I do see a multi-chain universe out there. I don't think BricksChain will be the only construction blockchain player in North America, but I do believe that a large part of what we want to focus on is continued interoperability amongst other chains and other software packages and other key players so that we can really drive in the trust, integrity, transparency and openness that a blockchain provides.

Hello and welcome to the Constructor Podcast, The Best Way to Build It, episode number 86. I'm your host, Brittany Campbell-Turner, and this podcast is dedicated to helping property owners have certainty in their decisions about their construction projects. We talk about fostering trusting relationships, help you to understand how to lower risk, be under budget and on schedule, and most importantly exceed your end user's desires. Over the past couple weeks, we've been speaking about how we should be able to support our industry by working on it from within.

We've been talking with startups who are doing this by disrupting the industry by taking the way we want to interact with each other and aligning that with technological solutions that can support that behavior. So over the next couple weeks, we'll continue to speak with companies that understand that we need to disrupt from within. So last week, we spoke with Chao Shang Shoreland, CEO of ShelterZoom. It's a blockchain-based online offer solution to make offers for real estate online. It streamlines the process of making real estate offers, reducing paperwork and bringing greater openness and transparency about when offers have been made and the acceptance, making it available for MLSs to simply plug into.

Chao talks about how this solution will help buyers, sellers, landlords and tenants with the upfront offer process just prior to the legal documentation process. They actually have plans to enable a global real estate market. So if you haven't listened to that episode yet, check it out at constructor.com slash ep85. This week, we are talking with Basim Hamdi, CEO and co-founder of BricksChain, a blockchain-as-built data handover and chronicle solution. He has been serving this industry by providing tech solutions for the AEC industry for 19 years, and his passion is in providing owners with more information about their built asset.

Ultimately, increasing value in the long term for resale, providing key information on projects and consensus-driven operations and maintenance manuals. He wants to make using project data after your complete project easy, transitioning into managing your built asset and for future owners. With that, let's get into the interview. Today we're talking with Basim Hamdi, CEO and co-founder of BricksChain. He has 19 plus years of construction tech experience, and he says that 95% of project data gets lost.

The complexity of budgeting, planning and managing a construction project leave major gaps in recording transactions in a permanent and coordinated manner. Basim, I'm really happy to get you on this podcast today. Thank you. First things first, just to kind of baseline with the audience here and share a little bit about you, could you give us a brief history of how you got into construction tech? You know, how I got into construction tech is I really didn't like banking.

So my first job at a school was at a Royal Bank of Canada in London, England, and spent a year doing that. I came from a family of engineers, civil engineers, so my uncles, my dad, my grandfather, and they were all wondering why I went to business school. And then I came back and I said, well, let me try this tech thing. And of course I end up in their industry basically. I think it was kind of meant to be.

But yes, 19 years, believe it or not. Luckily I started when I was 13, so that's fine. Oh, that really helps, doesn't it? Oh man. It's funny how things kind of come full circle and you find your passion there.

You know, we're going to be talking a lot about facilities management and asset management post-project. I just want to, for starters, what the state of the industry is on that front, and then we'll dig into Bricks Chain and how it helps. Let me first ask you, what do owner operators need from their project data for facilities management or asset management purposes? I think there's an interesting turn when you talk to big owner developers, big owner operators. We don't build projects.

We build facilities. We build buildings. We build the physical, but we've broken it down to these concepts of projects. And a project in itself is like, you know, they talk about three blind people touching an elephant. A project is different for the general contractor, from the engineer, from the subcontractor.

So when we talk about what does an owner need when a building is being completed construction, they need to know what's in their building in detail. They need to know what's behind the wall. And I think those are the interesting conversations we have with owners. I remember sitting with one early on in the days of Bricks Chain and we're talking about what to do, getting some discovery done. The guy said, very frankly, he goes, if you can tell me why that wall is leaking, you've just solved the billion dollar problem.

Because they really don't know. We have a joke around Bricks Chain. You could buy a 2002 Toyota Tercel, put the VIN number in Carfax and get more information than you'd get buying a 300 million dollar building. Wow. It's nuts, right?

Yes. Forget about the first owner of that building. What about the second and third owner? What do they actually have? Problem case is dire in a lot of cases.

What if a material is known to cause cancer and is emitting something? Right now, we don't know if it's in our facilities. I think we could do better as an industry as well. Just telling people what they're actually buying. I think this litigation game tries to keep everybody hiding their cards.

When in reality, these are life and death decisions that we're making every day. They need everything. Not the most minutiae. I don't think they care that Joe worked on March 23rd for three hours. I don't think they necessarily need that, but they need to know what Joe installed and how it was connected.

Look at a picture of what was done versus going through reams of data. Right now, the alternative is just going through PDFs. For one of my clients, I went through a scenario with them where they wanted to just get a handle of all their assets or their portfolio of real estate buildings. Breaking that down into grave detail without, say for instance, getting their CAD drawings. Lots of owner-operators don't even have the software for them drawings.

That's exactly right. We have this system, IWMS system, that we want our CAD drawings to be uploaded, but it still doesn't detail it out per the type of asset and the detailed level that they may be looking for. It's a real problem. We went back and we asked the architect and engineer for something high level, but it's pulling teeth. Yep.

Quite honestly. Yeah. I just came from AIA, so I have a lot of war stories around that. I go to the AIA National Conference, which is a very funny side story talking about what's in a building. Three weeks before that, I was at FutureTech, primarily a general contractor's top 100 show, talking about technology, large engineer, large EPC.

Then I go to AIA. In one breath at FutureTech, everybody's talking about their amazing specification parsing tool, how they read specs into lines in a database. I fly to AIA, I'm talking to the guys that create those specs, and they're like, we have the best security around our PDFs. Nobody can take data from our PDFs. We could never be blamed for anything.

I'm like, you should probably pick up the phone and call somebody at the other side, because they're parsing your data. They're like, no, they're not. Yeah, they are. Oh my goodness. That's incredible.

Yeah. It's nuts. It's just nuts. That just speaks to why it's needed. People want that information in that level of detail, and it's helpful.

That's why they're doing it. It's so interesting. We kind of talked a little bit about how it's done now. Are some of the owner operators talking to you about the challenges that they're facing specifically because they don't have this data at their fingertips? There's a couple of main areas where they see ROI, and there's an investment, obviously, so they want to know where the return is.

Couple of things. A piece of equipment is about to approach end of life, being able to understand when that's happening to more properly manage their portfolio. The other side is when something is under warranty. When you're given a handover document in PDF, and it's one year apart, five years late, whatever that breaks out to be, it's a very complicated model in some cases, and they sometimes don't even know that their assets are under warranty still. If there is a warranty product for 10 years, but they don't know and they just call a contractor to come fix something, that's a big loss on their site, and they simply don't have the data.

We talk about second owners. The second owner, where are they really getting that information? You bring up a good point with IWMS solutions. The problem is that we start every asset procurement. When you buy a building, we have to be like Colombo.

We have to go and find out what's in this building. We have to do laser scans and asset audits and all of these things because we have no idea what we bought. The previous owner is not being malicious. It's just you can't take a hacksaw and cut out of the IWM's database the previous owner's data and send that over, and nobody wants to give everything over. There needs to be this blockchain model, and I know we're kind of melding into it, but there needs to be something that sits above all that, and that's what we want Brickschain to be.

You definitely hit the nail on the head. I think that there are a number of stages where people need data. There's the maintenance of the building. It has to have the right maintenance schedule, and you have to understand what that is, but you also mentioned end of life. Same thing for those assets, and then even the building infrastructure.

There's just so many layers. Thirdly, you mentioned the second owner or third owner or fourth owner, whoever that may be, and if they don't know what they have, it's going to be a huge investigation period. Why can't it be like a Carfax report where you know exactly what you're getting? Yeah. The data is there on construction.

The data is there on TI. The data is there on IoT devices. The data is poorly coordinated and not put anywhere. We use the stat of 95% of data is lost or thrown away on handover. To protect the innocence, I'm going to change the project name in the construction company.

When I was working with my first job, I was 25 years old, and I closed out a stadium project because I quote unquote knew the computer, and it's like 2000, and we're using Microsoft Access 97. God knows what's happened to that data. It really is a challenge that we build great things that endure, yet we don't let them endure properly. Yeah. You got a great point here talking about Microsoft Access.

How often is that type of software used now, but that data still exists somewhere on some server somewhere. It's a matter of time where different applications are going to phase out because it wasn't useful anymore, and the data is still going to be sitting somewhere but not accessible anymore because now you've transitioned out of that system that's outdated and antiquated. Exactly. But that information is still super valuable, especially for companies. Even if it's just 10 buildings and they've had them between 10 and 30 years, it doesn't take a lot in order for that information to no longer be accessible.

That's crazy. Yeah. If you think about it, my father still has a VHS cassette recorder because he likes VHS videos, but the reality is that as the format changes, so does the data loss percentage. Owners may not own Revit or AutoCAD or Bluebeam, any of these other solutions. They probably don't, and they probably don't need to own a copy of Revit.

They just need the data inside of Revit. They don't care that it's a fancy looking 3D model. They just need to know what the specifications are from maintenance on an air handling unit is. We keep on trying to force them to use BIM, and BIM's becoming like a warm blanket. If only we could get to level whatever BIM, but the reality is, once that thing is delivered and if I own a building, I'm not opening up that BIM model.

I just want the data. I just want to look at stuff. We keep on trying to force people to use these super expensive solutions that will eventually no longer work because that's just the history of technology. Every company that's listening to this knows there's one PC in their office that has Windows on it because there's some form of data that they can't get off that PC. Every IT guy knows that story.

It's an unfortunate story because there's nobody that coordinated the data in something like a blockchain. Well, and it takes that 10 minutes to start it up and everything like that. You know that story. It's like, I've got to use the XP machine. You mentioned BIM, and that's an interesting subject.

We can dig into that more. That same client I mentioned earlier who wanted the drawings handed over and put in their IWMS system, they actually were somewhat savvy and wanted to update their drawings because of like furniture moves and like some minor moves that aren't necessarily done by a general contractor. Just curious as to your thoughts about integrating those types of changes and how that data will be pulled in. I always break everything down to the physical world because it's a physical world business we're in.

So if a furniture moves, it has actual coordinates that have changed, so that's data. If a room has gotten bigger or smaller, the dimensions have changed, that's data. That's more important to me than dragging a wall or putting on a HoloLens and looking through it and seeing something. It's the data. Yes, whatever visual UX you like to get that data into a system, then use that UX.

I like command line. I like typing, going fast. Other people like using the mouse and going slow, whatever works for you. But get the data in. A good owner, what you're specifying, that's a great owner.

They want to know what they own, what their space is. The fact that they do it in 2D, 3D, or on an Excel spreadsheet, fine, whatever, as long as the data gets in there. But once the data is captured, it's what happens once it's captured. What stops it from being changed or lost? You use the example of making a room smaller or changing the furniture.

That directly infects things like maintenance and how many tiles you need to order. And if they don't have that data, they're overordering. So there's so much to it. But collect the data. That's where I would start.

I mean, it's so simple, right? Let's start digging into Bricks Chain. What is it? Just kind of break it down for us. What is it meant to do?

A couple of things about Bricks Chain. The first thing we said to ourselves when we started developing it is, we do not want it to be a transaction creator. We want it to be a transaction holder. Basically, I didn't want to train end users how to use a mobile app anymore. That was a big thing.

We want to be the underlying layer of data, the keystone of data, if you will. So that's the first thing that we talked about. The second thing is, we wanted it to be technology skill agnostic to integrate with. We created about six lines of code that it takes to create a block in our Bricks Chain. So not a transaction creator, easy to integrate with.

And then finally, to be construction aware. So 19 years of construction technology, building actual tools used by a lot of companies in the field today. I've probably personally touched out of that trillion dollars that the industry does, $400 billion a year running on technology that I either wrote, designed, or sold them. I wanted to use that knowledge and not just keep on creating the same mousetrap. That's why we started with geometry rather than project.

The basics of facility, building, floor, room, system, asset. We focused on that rather than capturing project data. So the core of Bricks Chain is a distributed ledger that captures data during and after the construction process in order to drive a building to be more sustainable, to be cheaper to maintain and to really be a transferable asset with providence. So our goal is to map out assets. It's the great building genome project of our time.

Find out what's in these things and make sure that we track it going forward. And in itself, that's a currency data, but we are not a currency play. We are not an ICO play. I respect some of those folks out there that have done token sales and such. But in a lot of cases, they've detracted from the concept of blockchain.

So sometimes I have to kind of mumble, yeah, we're a blockchain play. At the end of the day, a distributed ledger locks things in so they can't be changed and are highly secure and highly efficient on how it holds data. It's not even up for debate. It is a better technology than a centralized database. The reality is that we have to get over this kind of Bitcoin hump in order to explain that.

I actually have a slide in presentations that I've done over the past, I don't know, four or five months that literally says blockchain is not Bitcoin. Sometimes people really do get that confused. Blockchain is definitely the technology that supports cryptocurrencies. It's the technology that allows for that immutability. It allows for that level of security.

It allows for you to trust the data because the transactions are verified, some level of consensus. Fortunately, we've been talking about blockchain for the past, I don't know, 10, 11 months now on the Constructor podcast. So I would hope that the audience is becoming more acquainted with it. It is something to wrap your head around for sure. But at the same time, it's good to understand a lot of the different applications that are being made available.

I want to jump into about your two products that you've released, Handover and Chronicle, Bricks Chain Handover and Bricks Chain Chronicle. Could you explain what both of them are? A handover is a process of creating consensus driven O&M manuals. I call it blockchain light because it's really collecting data after the installation and basically bringing that to consensus via more traditional approval methods. The outcome of the blockchain is an O&M manual.

It's taking what was designed to what was built and what is installed. Handover is generally focused on the general contractor walking in a meeting and saying, hey, I have some value add for you. Two things. A, I can hand over this building digitally and B, I can give you the ability to put in warranty claims over the next year on this system so you don't have to send me an email or form and triplicate. So there's a lot of value add there.

Basically provides the owner a great amount of information. It digitizes and takes out cut sheets so it actually parses cut sheets. They know the warranty and the lumens that were installed and what is this thing, right? And pictures of the product. In the case of Chronicle, Chronicle is much more engaged and that is the actual tracking of either a construction project or a building.

And that is the idea that there is a blockchain component for almost every major shared output. If you think of it as a large whiteboard essentially, what do you as a subcontractor, a contractor, an AE owner want to put on that board that everybody can see you put your stake in the ground and say, this is done? And so that really is what Chronicle is. So handover basically is, hey, the reality is these projects start too early and too late. Maybe they didn't find bricks chained in time.

So let's work with the industry to hand over these buildings at the end with them. And then Chronicle is let's work together to track everything from the beginning. So in that case, how would you describe then how Bricks Chain Chronicle then would enable project managers to specifically record transactions of information? Say for instance, let's use an example, like a request for information. Could you break that down for us?

So one of the great questions of our industry is why do we ask questions in RFIs? I think it's one of the things that we ask ourselves still. But the reality is, what is the system of record for an RFI? And so the system of record for an RFI is not the originating system of record, which is generally the subcontractors. It's probably not the GCs, although the GC is legally liable for that RFI.

Is it the AEs? Because then we forward it to the AE, right? Is that owner system the system of record? So who owns the question? Well, the person asking the question, who owns the answer, the suggestion, the cost impact?

What happens is it's all denormalized. With Bricks Chain, we've actually integrated through Zapier with Procore, for example. So you could put in an RFI in Procore and it will be an immutable block in the blockchain that can be then used via a webhook or an API call, which is a simple plug, to get pushed to the next system. So it can be driven like you would a financial transaction. Basically, you put in the RFI.

It gets pushed to this other system, who is this other company's system. And once it's pushed in there, it's marked as an immutable block as well. And then they answer it and it goes back up to the blockchain and back down to Procore, that part of the connection we're still working on. But the ultimate workflow is you want to record those questions in the blockchain. So there is no argument over when that email was sent or whether it was opened or did they download the drawing because it's being listened to on a format that is the blockchain, that is the background.

So in an ideal world, then, and I'm just thinking about my experience over the years, right? We've had the RFI, an RFI document submitted via email. That's not the scenario that we're specifically tracking, recording the transaction. It's more an integration than with a project management system like Procore, for instance, that already has this data tracking and approval tracking mechanism that can then have these pushes essentially recorded on a block. Is that correct?

Well, that's one side of it. But the other side is we integrate with Google Sheets as well. So if somebody was keeping an RFI log in Google Sheets or Excel, they added a new row with a question, we could consume that RFI information as well. So it's really any electronic means that can push the data into the blockchain or we, as the blockchain, can pull the data out. So a Google Sheet is a great example.

In a lot of cases, filling out a submittal log is still the job of a subcontractor and done primarily in Excel. Contractors have a very hard time getting their specialties to log into their system to enter that data in, but they could give them a Google Sheet that will become immutable in the blockchain. So we're trying to democratize technology on the construction site by allowing any types of system, both generic like Google Sheets or a Smartsheets or a Slack even, or even the more complex construction specific apps like Bluebeam and Procore.

This is the way I'm understanding it. Your hope is to be able to record those transactions and make it easy for people to operate in the way that they already do. We want to change some behavior. We don't want to change all behavior. I think, again, talking about FutureTech, one of the VCs were sitting up on stage smiling and saying, hey, we have 2,500 construction tech startups.

That means we got enough apps in construction right now. There are enough apps forever. However you want to get data into the system through a user interface, do it. That's what you do and that's how you record things, but just know certain pieces of that data needs to be shared with the supply chain. Those pieces will be pre-plumbed, regardless if it's Excel or a database driven system, pre-plumbed into the blockchain so it can be made available to all other members of the chain.

We're trying to impact the end user the least. We don't want to have a huge day's worth of training or learn how to use a new solution. That makes a lot of sense. And so we talked a little bit about the integrations with other software platforms. You said Slack, Google Sheets, Procore.

What are some of the other integrations that you guys have? Sure. Sharefile is one that's used. That's a big one for a lot of folks because a lot of people use Sharefile. MySQL, Oracle Database, so database driven stuff.

We have integrations with force.com so that information driven through kind of a Salesforce or a service Mac style interface can be brought into our blockchain. Dropbox, Google Drive. Just a whack of different integrations. I think we have 26 with about seven more on a roadmap. Curious about, I mean, we talked about BIM a little bit earlier.

Like Autodesk products is granular level of detail sort of on the roadmap. Do they have a roadmap for integration at all? We're doing investigations with Autodesk and Revit. We're working on integration with UBIM who has a Revit plugin. Great guys.

We're talking about how can we get the data out of Revit into Brickschain. Unfortunately, a lot of the models aren't data rich or data rich enough to provide any real value beyond geometry, but we're working on that side. There are also web hooks that we can utilize using the Forge platform for further integration. We have to see where that goes. We actually have not talked to Autodesk specifically.

We have reached out once, but haven't received a lot of feedback from them. We'll see where that goes. Well, when the audience is listening to the podcast, push this to Autodesk. It's good to hear that you guys are thinking about how to integrate BIM. And it's unfortunate that it's not data rich.

That's again, a behavioral change that we'd love to have take place down the line so that we can take advantage of the data in this way. I totally hear you. So the Foundry platform, could you tell us what that is, what it looks like and how it can be used? Foundry is in my mind, everything here. It's a combination of two different blockchain technologies that we utilize and a graph database.

So it's really the engine of learning and of processing and of on the big data scale, the ability to really drive the industry forward. Because we're creating a common language around buildings by collecting the handover data and chronicling construction and facilities management, we are actually helping the industry come up with a standard, at least in North America, that's been very elusive. Foundry allows you guys, hopefully long term, to predict failures of buildings and predict other issues that may come up with the real assets we have in the world.

Obviously, right now, it's early days. So those are forward looking statements. But ultimately, I talk about machine learning and AI quite a bit. And one thing that we talk about is how do you get machines to learn about construction? It's so chaotic.

Well, it's even more chaotic that we don't have a singular vernacular to talk about. So companies like SmartFit are really crushing it in the machine learning side around the concept of safety and analyzing photos and looking at things. But on the bigger scheme of how do we process whether a project is going to result in a bridge falling down, it's been, like I said, very elusive. And I liken it to trying to teach a child how to read by randomly walking in the room every once in a while and screaming at the kid because we don't have any data standardization or data collection standardization.

So how will we teach a machine what we can't teach each other? So Foundry ultimately is trying to be that great equalizer, taking data, normalizing it using plain English tags like company and subcontractor, not xbf underscore sc underscore name, like try to keep the tags very plain English and then normalize the data so that we can report on it effectively. And so things like, you know, one of the early projects we undertook with Foundry is the merging of the recall database, the national product recall database with products that are installed in buildings.

So we do a fuzzy logic match on things that have been recalled. And you'll be amazed how many products have been recalled that are still installed in buildings. So that's a great example of just mashing up the data and getting a really easy thing once you're on the blockchain, an easy thing to produce, but a very difficult thing to do now. That seems so valuable is taking the data that you have and making it tangible, if you will, so that you understand, you know, on a deeper level what to do next.

So could you share with us about the blockchain protocol? So we use two protocols. What is you ledger, which is a blockchain that was originally built with Deloitte. It's a great company out of Boise, Idaho, who we have a partnership with, and they provide something called Merkle hashing, Merkle encryption. So it allows a node to come to consensus without having to go back to the entire blockchain.

So it's great for performance. We've introduced hyperledger fabric for smart contracting and other more complex workflow around the blockchain. So let me ask you a quick question about case studies. Yeah, what are some case studies that you have going on right now? We launched about a month ago.

So we've been in stealth mode. We thought it would take us a couple of months to get our five pilot seats and it took seven days. So we filled up all five pilot seats over the last month. Two things that we're working on right now are two pretty hefty handovers. So getting the data out of Word, Excel, shared drives into the blockchain for handover.

And the other one that we're very excited about is with a large owner who wants to manage the entire cycle of the change out of an air handling unit. So just all the way from initial specification through procurement, through logistics, through installation and then ultimately maintenance. So that's not an entire building, but it's one part of a asset. So that's our most interesting case study, if you will, because my network generally is general contractors focused on helping them hand over projects better. Sure.

That makes a lot of sense. And then you're proofing that model, you know, time and time again. It's going to be great to validate that it's very useful. So BricksChain is endeavoring to coordinate data on every asset on the planet. You talked about how quickly you guys were able to seven days to get pilots.

Tell us about what the future looks like. What are the next steps to achieve that asset data tracking on the planet? Right now it's very hands on. All of that great automation isn't coming in handy right now because we're just figuring things out on the data acquisition side. So it's very human intensive right now, but over the next six months, we expect to drop off a huge amount of the manual labor that's required to parse a cut sheet.

So that's the first step. The next step is really focusing on the supply chain and the marketplace focus of getting materials procured, delivered and installed into construction projects. So our focus is really the supply chain side of the game around smart contracting. I do see a multi-chain universe out there. I don't think BricksChain will be the only construction blockchain player in North America, but I do believe that we are kind of first to market and hopefully first to product market fit.

But ultimately, a large part of what we want to focus on is continued interoperability amongst other chains and other software packages and other key players. We would welcome manufacturers being involved at the same level. We would welcome unions to be involved. We're trying to keep ourselves as open as possible so that we can really drive in the trust integrity, transparency and openness that a blockchain provides. That's wonderful.

So is there anything else that you'd like to share with the audience? Overall, having been in this business as long as I can, I know one thing is that we all have amazing intentions. I think a lot of people beat us up being in construction or construction tech. They keep on talking about the productivity gap and all of these things. I think we are an innovative, hardworking industry that people don't think of enough because really everywhere you go, everywhere you drive, where you live, where you work is all part of the built world.

So I think ultimately we're all in this together and hopefully we can start breaking down the walls between the key players and the processes so that we can make it better for everyone. Oh yeah, I love that and I second that. Thank you. Thanks for sharing that for sure. Please tell the audience where they can find you and how they can learn more about BricksChain.

Absolutely. You can find us online at www.brickschain.com or call us at 1-833-BRICKSCHANE. Thank you again, Bassem. This has been great. Awesome.

Thank you so much. If you want to learn more about Bassem Hamdi and BricksChain, check out the show notes at constructor.com slash EP86. If you learned something valuable in this episode, share it with your friends and colleagues. Let me also know if you enjoyed our discussion by connecting with me on Twitter at Brittany underscore CT or find me on LinkedIn. You can just email me too at Brittany at constructor.com.

That's B-R-I-T-T-A-N-I-E at constructsr.com. Next week, we are speaking with Stephen Cutter, Chief Visionary Officer of the Wooji Foundation and the founder of the Landing Eco Institute. While Stephen was at the World Economic Forum, he participated in a hackathon and spoke about how blockchain can be used to help generate quantifiable rewards for the regenerative Earth action. In this episode, we talk with Stephen about the benefits to building awareness of natural habitats for humans and how contributing to it can help businesses and individuals be more successful in their contribution to work and performance.

We talk about incentivization behavior to encouraging a new standard to valuing our built environment and the humans in it. I look forward to sharing this interview with you next week. If you haven't already subscribed to the podcast, you can do so at your preferred podcast player. Please leave a review to show you support and let me know you're enjoying the podcast. I look forward to talking with you next week.