Energy Bytes

Ryan Rice, Founder of ResNet explore how gamification is transforming the energy industry. Ryan shares his journey from the oil fields to creating ResNet, emphasizing the role of AI and digital tools in improving operational efficiency. The discussion delves into the challenges of energy independence, the innovative tech stacks driving change, and ResNet’s mission to deliver user-friendly solutions. Ryan also offers insights into the future of gamification and its potential to enhance industry performance.

Join the conversation shaping the future of energy.
Collide is the community where oil & gas professionals connect, share insights, and solve real-world problems together. No noise. No fluff. Just the discussions that move our industry forward.
Apply today at collide.io

0:00 - Introduction to Energy Bytes Podcast
3:58 - ResNet Founding Story
9:49 - Motivations Behind Starting ResNet
12:20 - Pioneering Energy Tech Innovations
19:20 - Enhancing Industry Transparency
26:25 - Tech Evolution in Energy Sector
28:32 - Citizen Developer Impact
31:13 - Navigating Business Uncertainties
34:07 - Role of Empathy in Tech
36:40 - Technology Decision Making
42:50 - Arps Decline Curve Customization
44:40 - Distribution Normalization Techniques
46:40 - Machine Learning Explainability
47:57 - Simplifying Non-Linear Equations
49:40 - Comparing Physical and Statistical Models
52:30 - The Need for Model Explainability
55:20 - ResNet Business Insights
56:45 - Design Philosophy of ResX Platform
59:54 - ResX Platform Benefits Overview
1:06:45 - Gamification in ResFrac's Design
1:07:28 - Importance of User Experience
1:08:28 - Gamification Experience at Rice Energy
1:17:57 - Quick-Fire Question Round
1:19:49 - Social Media Recommendations
1:20:28 - Favorite Coding Packages
1:20:52 - Personal Preferences: Mountain vs Beach
1:21:16 - Career Advice in Energy Tech
1:23:00 - Connecting with Ryan Rice
1:23:33 - Contacting ResNet

https://twitter.com/collide_ai
https://www.tiktok.com/@collide.io
https://www.instagram.com/collide.io/
https://www.facebook.com/collide.io/
https://www.linkedin.com/company/collideai

What is Energy Bytes?

Welcome to Energy Bytes with John Kalfayan and Bobby Neelon. Your essential guide to the intersection of data and energy. This podcast dives deep into the world of energy, shedding light on how data, AI, and technology are revolutionizing this sector. Each episode equips listeners with insights into the most efficient tools and resources, paving the way for a data-driven future in energy. From technical nuances to broader industry trends, Energy Bytes offers an unparalleled perspective on the evolution of the energy industry. Join us as we decode the algorithms of energy, one byte at a time.

All right, everybody. Welcome back to uh to another episode of Energy Bites. Rad here with my trusty co-host, Bobby Neland. What's going on? Repping the socks today. Absolutely. As long as it's not the Yankees, we're never the Yankees. #Never Yankees. We're uh we're here today with with Ryan Rice, founder and self-proclaimed janitor at uh ResNet AI. Appreciate you coming on, Ryan. Thanks for having me, guys. I appreciate it. Yeah, I'm excited to have you on. I'm excited that you left your hat so I can uh taunt you with it on this episode. I don't know if you noticed me changing it. My favorite hat. Usually uh usually I'm always wearing it to to rep the uh Unleash USLNG. Well, I figured forgot it. I figured I'd rep it for you since you left it in the studio. Oh, you're wear Are you wearing it? Maybe.

And And for the uh I guess the audio listeners, it's Marcelus over Moscow. Yeah, it's%it's a great cap. Yeah, I need to give me one of those. I know. Anyway, and our our development team loves it, too, because our our development team's 100%Ukraine. Oh, yeah. So, they're like all about it. So, we have a we have a saying, you know, one of our our higher missions at ResNet is to beat the hell out of Russia with respect to regaining energy independence, making up for all of their lost market share. That seems to inspire the guys when they think about how much, you know, Russia's GDP comes from energy. Yeah. Yeah. So, yeah. I mean, last company I worked for, all of our dev team was in Ukraine as well. And when the war started, that really changed lives a lot. Yeah. Yeah. That uh there was about six weeks. Yep. Unfortunately, right, where kind of things slowed down obviously and you know a few weeks where we can hear bombs going off in the background. Limited connectivity, just power, all that fun stuff. Total totally wild. Really kind of puts things into perspective. Yeah. Of like what matters in life where, you know, my guys are, you know, fleeing their homes, their villages, you know, staying out in the middle of nowhere. They're afraid for their their lives. Yeah. Um puts things into perspective of what truly matters. For sure. Yeah. Need more of that. No, no, it's uh Well, more perspective, not more war. But yeah, for sure. Unfortunately, that tends to be the It's always the bad things that trigger that perspective typically. But um appreciate you coming on, man. We uh I think the first time we met was at uh was at Fuse last year when when we did the pitch competition. That was They got might have got some champagne on you. I love it. That's what I want. We're celebrating. That's what I uh I was really trying to get those uh champagne guns that they they have to uh spray everybody with, but we couldn't couldn't get those in in time. You know what was funny is uh I had bought like a t-shirt cannon for that. It was like, you know, give the people what they want. But I I showed up to Fuse and like this thing was like a legitimate like device where you know I'm like man the cops like the cops stopped us when we were coming in with it because it looks like a sniper rifle like rocket launcher. Had to explain to him like no like this is a really dumb idea I had with shooting people with the t-shirt and then like I'm putting the I'm putting the thing together and it's like you need a CO2 canister. I don't have a CO2 canister. I go to like I run down to like the sports outdoor like no man like you got to go to the gun, you know, we don't have that, you know, on stock. So, didn't get to use the t-shirt cannon, but it's sitting in my closet, you know, for the next time. Yeah. Yeah. We'll uh we'll have to make some find some ways to make use of that. And I think uh that's awesome. I didn't know you had a t-shirt with you. That's incredible. Pro tip for all the all the pitch competitions and tech night guys for next year, right? Yeah. You got to do it. We'll break it off. Next energy technic. Give the people what they want. 100%. Well, Ryan, tell us uh tell us a little bit a little bit about you. How did you uh how did you end up as a a founder at Resin? How'd you get into the kind of energy tech space? Uh that's a great question. I mean, kind of a long journey to this point. Um but you know, our our family, uh my three brothers, myself, you know, we're we're originally from Boston, Massachusetts. Um, and so I broke out into the industry actually when my older brother Toby, you know, founded and started Rice Energy. I I was in high school at the time. Um, ended up moving in with him um to kind of just, you know, it was always cool to hang out with Big Bro. Um, learn what he was doing. So, ended up moving in with him after high school. Uh, I was the lackey intern. Whatever they needed, uh, got done. So, I didn't know what I was doing at that time, but a lot of, you know, mining the court docks, you know, for land owners, that was the name of the game then. I had no idea. They didn't really educate me as far as like why I was doing what I was doing. Just go do this. Um, but kind of started doing that. Got to go out in the field, right, after, you know, business moved from land and developing our land position to actual operations, constructing well sites, the pad, drilling of the wells. So started working roastabout, worked on rig floor, you know, for for a while. Um, got to snub in tubing in our first well without knowing that that's the most dangerous oil field operation. They didn't they didn't tell me that, you know, we we drilled our first well, the X-Man 1V. Um, we had to snub in some tubing and I'll never forget it was like January in the dead of winter, you know, in southwestern PA. It's 0 degrees out, just miserable. And Toby's just like, you know, why why don't you get up there? That's a good experience for you, man. I get up there and, you know, hot water is just blowing in our face and you couldn't get me down from that rig floor cuz it was so much better than being on on the the location freezing my ass off. Um, so after about 2 years of doing that, I realized I was never going to have a girlfriend or a wife living in a trailer in uh Green County. Green County is great in Pennsylvania, but you know, not the not the best, you know, night life or anything for a 19-year-old. Um, so I was very passionate about really working with my brothers. They had, you know, really mentored and guided me my whole life in terms of major life decisions, sports, everything. So I was very passionate about still following in their footsteps. But I decided like, hey, I I need to have a life. I want to be technical. Um, so I want to be a petroleum engineer. I went to Texas A&M. I kind of told the guys uh last week, you know, what that was like. I I'd never seen Daisy Dukes before. Um I go to game day at&m immediately fall in love with it. So I I did my petroleum engineering degree at&m cost of 14. Uh while doing that, I was working for Chevron uh as a drilling and completions consultant. Uh this was you know 2012 2014 industry was really taking off. There was a lack of supply in the market, and you know, being a guy that actually had fundamental like on you know hands-on drilling experience, um, got to had the unique opportunity to kind of work full-time with Chevron um while I was getting my degree, um, the good old days. And then, having having lived that life of like, this is what it's like to live in like you know not for my brothers, um, kind of really got a great gig at Chevron. I was going to go do that, and when my brothers found out that I accepted a full-time offer with Chevron, uh, they flew down toM uh, broke up with my girlfriend for me, physically kidnapped, and dragged me back to Pittsburgh. Um and that's where uh really it was it was similar to my internship like wherever I could be helpful. Yeah. And at that time we didn't we didn't have any you know petroleum engineers in the business. And so naturally you know as we were you know taking the company public focusing on our well results or reserves naturally um I just got into data analytics some production and reservoir engineering work. Um and that's really where I just fell in love um more so with with big data and digital technologies and how we could keep rice energy as lean and mean as like physically possible. Um, and so, that that's really how I broke out. Was just, you know, a journey. Just, you know, following along where where my brothers were were kind of guiding me, and then, honestly, just falling in love with the work and the people, um, you know, that I had that opportunity to do with. Yeah. And then, uh, we did that for a few years. Um, once we kind of, you know, sold the business to EQT uh, in 17, uh, it didn't take us very long to jump right back into the mix. I think we took like six weeks off maybe and then um we started Rice Investment Group, Rice Investment Group, uh private equity, venture capital um where we started to put put some of our money back to work in the energy space around things that we were passionate about. Um you know, when we when we saw like what are the things that we wish we had as operators 10 years ago, let's invest in those solutions. And so we we've invested in traditional private equity style deals backing a few upstream management uh teams. Um companies like Pinion Resources in the Midland. We just had a process of transaction um with Birch that was you know closed a few weeks ago. So that was a good win. And then as well as XCL resources in the Uenta which is a reservoir engineer's dream. Yeah. Right. Some of the best reservoirs in the world um in the Uenta. So that's been great. And then we also you know dipped our toes in the venture capital space with you know putting seed investments in companies like combo curve for instance. Um you guys had Kelvin AI. We're investors in Kelvin. Uh Coldore Technologies. Uh per I can go down. We have 15 about 15 portfolio companies. Um split between like hard assets as well as tech. Um a few great wins under our belt. But in 2020 um you know after we had fully committed and deployed our capital um you know I had the itch uh to start commercializing a lot of the ideas and applications that we had built at Rice Energy um that I was just super super passionate about. Um again thinking that you know there there could be a need for the industry as a whole for this. And so ResNet was born in 2020 during the pandemic, you know, I think like a week after negative 40 oil. Um, with with the thesis there being, you know, oh, oh man, this is the this is the bus that really kills us. You know, we're going to be maybe at $30 oil from here on out. I really need to focus on production operations, you know, maximizing efficiency. Rigs and frat crews are going to be laying down and that certainly wasn't the case, right? So, kind of missed the thesis there. But at the end of the day, making sure that you know we're reducing our downtime um and maximizing our our operational efficiency is still obviously um you know an objective and initiative for every operating company. Those never go out of vogue, right? I mean spend less and make more. Good. I think too like with our generation going through the last 10 15 or so years in the industry, right? Like I think we're we've almost become accustomed to this like the crazy volatility and these swings, right? That like in my mind, why wouldn't you want to move forward with the assumption that hey there's going to be this volatility in the future because of a variety of reasons? Like we need to be optimized all of the time, not just when prices are are low or negative. Just like, you know, historically speaking, that's generally what what happens, right? is, oh [ __ ] we've got to be able to make, you know, break even at $50 barrel. How do we do that? And so everybody's hyperfocused on cost. Then then it gets up to 80 100 plus, you know, when we started in the industry. And it's like no one gives a [ __ ] about cost or spending. It's just get it out of the ground as quickly as you can before it drops back below 100, right? And so it's this weird cycle that the industry kind of lives in. Yeah. And then people are chasing it and by the time they optimize, the prices should back up and then loosen the belts. So Yep. Yep. But yeah, if there's one thing that we can be certain of is that, you know, history repeats itself and there absolutely will be a future bust and another boom and you know, the cycle will repeat and so making sure that you know, we're just putting some of those initiatives top of mind and not changing some of those longer term objectives despite that volatility because the volatility is always going to be Yeah. Well, so let's let's back up a minute, because I mean, when I first started kind of in the technology side, Rice was one of the companies I mean, among like the Devons, the anodaros of the world that, you know, from my firsthand experience working as a sales engineer and stuff, like y'all kind of set the bar, um, early on in my opinion, like industrywide even. Um, y'all were one of the first companies to really set the bar around like pushing things forward, pushing for digital, pushing for, you know, IoT and connectivity and leveraging all of those things. Can you kind of talk uh just talk a little bit about that like in the early days and stuff, right? Because you a lot of people don't have that unique experience of both being at an operator but also being in a startup at an operator where it's like hey we have kind of a a blank slate to start this how we would want to do it versus inheriting you know a bunch of stuff from an acquisition or from you know being at an existing company. So, I'm very curious, you know, cuz I remember my very first job straight out of the field was selling spider gauges. Um, and you know, a few of those. Yeah. And well, we were trying to I was trying to call in Rice and all this stuff. And, uh, you know, the But by that point, you guys either owned your own. I think y'all had your own and y'all were trying to figure out the communications piece of it, like if you could stream them or not. And that's when we kind of initially started talking. But even then, like y'all, the economics aren't that great when when the operator already owns their own gauges as long as they can actually go and execute the tests and the monitoring uh correctly and accurately and stuff, but talk a little bit more about kind of building that from scratch and how you guys did things differently and stuff. And yeah, and it's funny you asked that because um now looking back on it there there's a few instances where I'm I'm going to be probably one of the world's biggest hypocrites. The build versus Yeah, that's exactly what we want to talk about, right? Because it's it's all this stuff is one of those things that like unless you have experience in it, it is so hard to know like, hey, I need to buy this versus building or you know, cloning this repo and well, I'll spend if what you want is on the market. Yeah, that's a whole another which I'm sure 101 15 years ago was probably even harder than it is today. Yeah. So, um it's a great question. Um I I I would it's it's kind of funny, but you know there there's a certain um assumption maybe and to some degree might be an incorrect assumption that like it was all like a master plan um to begin with and none of it was. we we just kind of like stumbled into these things out of pure ignorance to to be quite honest with you. Um pure ignorance around what type of solutions were available in the market, right? Where there were a few instances where we were custom building solutions, where if we just had better education, you know, similar to what you guys were doing at Digital Wildcatterers with helping promote that education in the industry, um, where we might not have have, you know, custom built a few of those solutions. Um but when we you know were on our digital evolution journey, it really just came down to the fact that um we were always in the trenches ourselves, you know, shoulderto-shoulder with with our team members. And so there was a deep empathy for when solutions didn't do exactly what we needed to and we could all agree as a team as far as well, how should this function, right? So an easy example might be around the the reserves um piece. Um, after about an hour of, you know, spent like literally an hour within Aries or Valnav, um, I could not do what I needed to do for the business, right? And I knew exactly what we needed to do for the business, and so it was more along the lines of, "Well, I'm just going to do it," right? Um, and build what works for us at that time. And hence, you know why, why things like Combo Grow make so much sense when we invest in those, you know, as investors at Rice Investment Group. Um, but a lot of it came down to our roots as a family-owned company and having deep, deep level of ownership around our assets and our people at the end of the day where, you know, we we had grew from when it was just the the four of us to when it was, you know, a dozen of us, two dozen of us to our first 100 employees until the point where it was 600 employees. Um and so because of just that deep empathy and level of ownership, um I think it it it set a new standard. Yeah. You know, for the organization in terms of like what what is winning like, right? And we would also simplify to that degree like what is winning? Winning can be something as simply as Toby's able to answer this question um in a in a board meeting, right? Without having to harass, you know, some department head or some tech or analyst for that information. And so a lot of it came down to reducing the pain points and access to information. And that's where um again almost accidentally or serendipitously um we had made the decision um to start building everything within um a customer relationship management platform mind you um called Salesforce right the quintessential CRM the ticker symbol CRM um because the access to information and the transparency it provided the organization as well as just the added layer of accountability right and and what what that I mean is it's one thing if someone's emailing me for something, right? And then perhaps I, you know, the day gets ahead of me, you know, there's a few fires I need to put out. Um, and I just forget, right? And I'm only accountable to that that one person. And, hey, man, I'm sorry. I I the day got ahead of me. I I'll get to it tomorrow. And it's a whole other world if someone is requesting that information like in the equivalent of a Facebook, right? Yeah. page where the entire organization can see that my peer has asked for my help on something and did it take me an hour to get back to him, did it take me a day to get back to him or a week. Um that layer of transparency around like who is helping one another in the fastest bestest way possible. Then you know to some degree gamification which we can talk about as far as ResNet's concerned around social influence. Um but just having that transparency was a lot of the reason why we we made the decision to go to Salesforce. And then really just understanding how we could digitize um quite literally like every business process to understand again like are we winning, right? If we're going to be going into this this quarterly call, how how do we have the confidence that we can answer every question that's going to come to us and that we're proud, you know, to to speak to these results. um because it it just came back to like this our name was on the building and so we we took a deep level of ownership of being the best that we could be and so that that set a new standard for the organization as a whole. Yeah, I think I mean you're spot on. I think the big differentiation between kind of the big companies that have a lot of resources but are kind of difficult to work in versus the the leaner, more innovative companies that kind of set industry standards. is that it's the access to information and you know the the ability to give people the information they need to do their job, right? Like and it sounds so stupid and simple when you just like say that out loud, right? But that's such a hard thing in so many companies because as they get bigger, you get layers of bureaucracy, you've got IT departments, you've got data privacy, security, like got all those things which you get desensitized and they're important. You're totally desensitized. However, yeah, if they're, you know, if they're impeding an employee from doing their job, they're probably not as functional as they they need to be, right? Um, well, and yeah, like I'm glad you brought it up because I was going to bring it up if you didn't, but even just something as simple as Salesforce, right? You talked about, you know, the psychology side of it, but even like as someone who was a vendor of EQTS at one point in time, like having the ability to, you know, have conversations and and essentially Slack channel forum type feeds with not only myself and whoever I was dealing with at EQT, but also any other vendor that was involved in that project. right? Like that happens over like emails at most companies, right? And like that's a horribly inefficient way of doing that, right? Yeah. Yeah, it's a it's a year and you might have like and and that was it's funny but the Salesforce implementation actually started in the most easiest use case which was around land. Right. Right. We we had 100 land man you know that were talking to over 30,000 land owners on any given day and and Toby and his his wife my sister-in-law his wife Eileen um running our our our land program. And so he was always out where's this contract at? Where are we at with this unit over here? And he would and Toby's ability to distill down the the root of the problem is is something that's still to this day extremely impressive to me. He would always distill it down to like listen man, I'm not going to spend 30 minutes going through this file, you know, this public directory path that's like a rat's nest. I don't even know how you guys operate in this. I'm not going through emails. I'm I I need to be able to click by unit and understand exactly where we're at in this process. And so dumbing down the problem to just like we're not going to waste 30, 40, 50 minutes a day, these like we have 600 employees. You add that up over the course of the day, we are literally burning dollars for every minute that it takes someone to find this information. And so it was really focusing on like the foundation, making sure everything was well architected, very well organized, going back to that, you know, access to information, even just the ability to build on top of it too, right? the flexibility of some of I mean we use HubSpot here at DW. When Bobby and I work together, we use a tool called Quickbase which is like a low code ERP platform. Yep. Um and like those tools I feel like a lot of people sleep on them or they think they're exclusively for one like they're for sales or sales and marketing or whatever, right? And it's like the fact that they're customizable actually allows a lot to be able to be done on that, right? Like entire businesses literally built you can create database and you can create a then they can create a front end to it. Um, so yeah, I mean I want to dive in. So were you using Salesforce for any number of things? It sound like maybe that was like almost an owner relations or a land kind of management platform as well. Um, it started it started with land, right? And then um like Salesforce implementation was great, don't get me wrong. Absolutely one of the best solutions, but it also took an insane amount of investment and time and resources to get it to work the way we needed it to work. Right. And and so here here's Borne Resnet around you know building a debundling that to your point you know John we you everyone could build an operating system for an EMP within Salesforce but the time and energy and resources it's going to take is is quite long because it's not specifically designed for you know heavy asset industrial management. I think that's where a lot of people get hung up on those those types of platforms, right? Is it's like oh well, you know, it can do everything, but because it can do everything now I'm scared of it and like yeah well you have to like the upfront cost and the learning curve and all that. You have to probably have a narrow focus like we're going to solve this problem first. You can't say oh I can do these 20 things and I do 20 things halfass. I mean like you got to say like I'm going to make this a really good owner relations platform and then well look we did this and we can do the similar workflow for XYZ. making sure it has those capabilities to go beyond what your first kind of target or scope is so that you're not now stuck is another big piece of it too, right? Like Right. Yeah. So we started and then we just we started in land and then fundamentally the deployment and adoption across the uh across the company was with respect to our business, right? So okay land that is taking that we we have that under control. Now what's the next part in the process as far as the cycle of a well? Okay, permitting. Now we go to permitting. Let's digitize all the permitting processes. Okay, now that's good. What's the next step? Construction. Okay, let's get construction. And so we worked towards towards the wellhead. Got um one by one department to get that adoption to get that buy in from the entire company, right? Respecting everyone's, you know, bespoke nuance edge cases to their flows and things like that. Um, but one by one focusing on the departments, working our way back towards the wellhead. Um, and that was a four-year journey. Yeah. Did it help? It sound because you started with land, I'm assuming you structured and you can tell me as much or as little as you want here but it it sounds like you started where it was structured basically down to, you know, the asset lease kind of level out of the gate, which I probably sounds kind of again obvious, but I don't feel like a lot of people like, because you've...it was founded, the foundation was that moving it from there all the way to, you know, production and operations makes sense because, that's that's what how all those are kind organized and categorized and grouped anyway, right?

Yep. And and and you know there were some some growing pains, right, where you know how we architected things for land was was not how things needed to be architected, you know, for the lease operator working on that. Well, right. But you're absolutely right. We would start on like a unitization lease level basis getting all of our land owners, the contacts into those leveraging cases, you know, to digitize the work. That way, Toby, the brothers can understand, like, who's doing what you know, how are we winning today? Um, and then eventually working towards, you know, where Salesforce served as, you know, our asset management system. And so, um, with ResNet, I'm working backwards now, right? Focusing at the wellhead production operations. And then, as there's potentially other use cases within DNC or things like that we, we could look at that, but right now our our primary focus as a startup ourselves is is on production ction operations. Sweet. So, how about if we want to pivot and make it you know a little more about your personal journey with tech and everything? When did you get into I mean do you code or when did you start getting into even some light development or I mean was this something did you ever touch it in high school or was it just kind of as you got into it and had problems you needed to solve you kind of figured it out?

Yeah. Yeah. it the latter right a as we had problems just figuring out you know selfeaching myself um I don't do as much deep development work today just given my current role as um janitor um but at at rice very much so you know punching in the key strokes um coding a lot of our solutions um I I I started off uh you know in VBA even if you want to call that yeah but some of the things that we we're doing but that really kind of opened my eyes. Yeah. And then um you know from VBA to to more actual you know programming um Python some R um spent a lot of my time in R um just given the the nature of some of the bigger data projects. Yeah. Um that I was running on our exploration side. Um, but then within within ResNet, um, more so helping guide and and mentor, you know, our development team around the context, right, of the data, and then myself learning, right? I I, personally, I've never, you know, coded, you know, in JavaScript as much, and so I'm learning that side of the business, you know, with NodeJS and React and React Native, um, but a lot of it was much more bespoke purpose, you know, functions, um. ETL routines a lot of data driven workflows where we were using Python and R to do that. Um, little shout out for a company called Ultrix. I'm not sure if you guys have heard that, but that's a great citizen development type of tool um around empowering everyone in the organization to potentially be data engineers to some degree. Um, so we were big fans of that at Rice. Um but yeah, So let's talk about that a little bit, because I mean the kind of the citizen developer side of it, because you know there's pros and cons. Like, it mean, because you can it can turn into the Wild West, you know? You get too many, you know, hands in there. But at the same time, you want to allow people to solve problems and do them in a robust way, because again, people are going to find a way. If you put up too much friction, they're going to find a way around what you're doing, and you know they're going to create workflows that you didn't want anyways. But, um, can you talk about kind of that citizen developer program, even if it was kind of unintentional per se, you know, at Rice, but like how you all managed that from even, like I say, a governance standpoint, but then like pros and cons that you saw with it? Yeah, sure. Um, so at, so at Rice Energy, we we call them the wizards, um, which were individual team members, usually, you know, uh, engineers, much like yourselves, to be honest, you know, that understand the context, some of the technical nature of the work, um, but had some type of programming, data engineering experience, um, and so we embedded, you know, a wizard in each kind of department, and then. um I worked with with our wizards to help communicate cross department you know priorities priorities and why things had to be a certain way to respect, you know, the needs of your customers, right? If if drilling and completions is a customer of of construction and permitting or if production operations is a customer of DNC, right? Helping kind of illuminate that empathy that needed to to be present in the architecture, you know, from end to end from land to permitting all the way, you know, to to the wellhead. And so, we embedded, um, you know these, these individuals in each department; and then, you know, just kind of typical project management you know, weekly type of scrums standups, to understand where different objectives were and how all of those puzzle pieces came towards, uh our, higher order objective as a company, right? So, um, digitizing some processes where we knew we were, you know, spending hundreds of hours, you know, between multiple different people to get these proc processes done every month or every quarter. and focusing you know where there was a lot of juice to be squeezed. Absolutely. I mean that doesn't sound too dissimilar to what we're doing. We've got a kind of a you know you call them wizard we got an analyst in each different group and then you know they kind of sync up with my group and I don't manage them per se. They they report to the you know production engineering manager or the DNC manager but you know they we sync up every week. what what are you working on and making sure there's no overlap um that again that they know what's going on in the other groups so that they can leverage what other other people are doing. So no, it's you know at least encouraging maybe to know that we're on a on a good track or something that's been done before. So yeah and and and and to your other question in terms of like sometimes it can be chaos, right? Um absolutely. I think there's a certain level of chaos we have to be comfortable with if we're going to be moving at the velocity that we need to be for the business. And so, managing that now, it's a separate problem how do we manage this chaos, right? And so, we fundamentally, you know, had the opinion at Rice: we need to empower every single one of our of our team members, of our employees, of our partners to get their job done at the end of the day. Yeah. And you know, I I would always joke like, "How dare I tell someone what tool they can use to get their job done?" Amen. It's not my job to tell you what tool you should be using to get your job done. Um what should be my job is how can I empower you to use the best tool for your job and make it work for your customers, right? So my philosophy um has always been using the best solution to get the job done and treating the integration of it as a separate problem. Yeah. And so I see a lot of organizations today um this might be like a little bit in the weeds but um you know uh Bobby you mentioned you know data analytics at Grayson right and you know you're doing some work in spotfire. Y um I see a lot of organizations right now where there's there's an internal fight with it to get the entire business into PowerBI. Why? Because PowerBI is is much easier to manage. Um it's cheaper. It's also cheaper free because they're giving them all the credits for an Azure shop, right? But um we hear a lot of organizations that are forcing users into PowerBI without actually listening to some of their customers, right? Yeah. Like in Reservoir where we're doing these massive big data projects where PowerBI is just honestly not the best tool for some of those problems. But now you have this tension between it and the business where they want everyone in PowerBI and you have the engineers that are actually doing you know the work every day saying like I can't do what you need me to do in this other tool and then there's this constant friction around like everyone's mindset of wanting to get like everything in one place. Yeah. Rather than perhaps you know viewing it like perhaps we could have one middleware integration place that everything connects to but we can use pinpointed solutions you know the best hammer to nail that nail when we need to. No, 100%. Amen. That's where I spend a lot of my time on is on the integration kind of middleware front trying to empower the teams. Yeah, cuz I mean that's kind of when we're using Snowflake and that's our data warehouse, but um and we've talked a lot about this, but say our accounting department, I'm not going to pry Excel out of their cold dead hands like so I can either fight it, good luck, or I can help them and so I mean and now they're pulling data in whether it's directly from a PowerBI data set or from an ODBC connection to Snowflake and they're getting reproducible workflows, but they get to work in something that they're comfortable with and everyone wins. Um, it's funny. I mean, because you've mentioned empathy quite a bit and I was uh kind of going back and forth with a guy on the on the baseball Twitter side, but he kind of asked a question about meeting what is meeting people where they're at, you know, mean to you? And I kind of brought up that example. And he's like, well, why do you think that is? And I was like, I think a lot of people, you know, kind of like you say in it, telling people this is what you have to use. And it's like it's because they don't have any empathy. They're not on the ground floor. They're not there trying to close the books at the end of the month. Like, you know, my revenue accountants, yeah, maybe they could be better if they could learn some Python and do some things like, but they they don't have the time. They're trying to close things out. Like, that is the la last thing they want to do is learn a new tool. They know they can get the job done. So, why don't I help them where they're at and, you know, make their life better, make make it easier and everyone wins because the company, you know, gets to do things more efficiently, too. Yeah. Well, and it's like if you're if you're forcing PowerBI in for whatever reason, but let's make let's make the assumption that it's because you're getting a hell of a deal on it compared to Spotfire because that's their it is. I just reuped our Spotfire subscription. That's it. Yeah, you're getting a better quote unquote deal, right? Well, that's what I was getting at, right? Like, so the Okay, the per seat license is cheaper or free, whatever. But then now these people that are Spotify experts have to spend hours if not weeks learning all of this new stuff and refactoring. If you're if you're going to get off Spotify, you have to refactor and then migrate opens up and then there's no investment. There's no return on that investment. Like what like this is working for us today, right? Why why are we going to refactor everything to res to for some you know unbeknownsted reason as to just the idea of getting everything in one place Like, if it's not performance, if it's not showing that like, "Hey, this is going to save you hours and hours of time," where there's like a very tangible difference there, then like, I could not agree with you more. And I think, you're, a lot of the stuff you've talked about today is just like, it's so simple, again, but like focusing on the amount of time that an employee spends doing something if you can reduce that or eliminate that or automate it, right? Like how much more time you're that, you know, six figure employee that you're paying to sit there and the entire staff of those six figure employees in the accounting department or wherever. And it's like that compounds incredibly quickly when you start thinking about how much they get paid per hour and how many hours every single one of them is wasting on this stupid step and then they can focus on strategic work. Exactly. Right. Like they're actually subject matter experts in, you know, you're not paying them because they're good at Excel. you're paying them because they understand accounting or they understand reservoir engineering. Yeah. Like so um just let them work on more higher value work. What and I'm always very cautious about this but I think it does resonate for a lot of folks lately um around like the build versus buy which is I just like asked the question like hey are we an oil and gas company or are we a software company? Oh yeah right. And we are not in the business of building the best software solutions. we're in the business of building and delivering the the best economic wells and production to our shareholders. And so, um, to your point, once we start thinking about the cost of everyone's time, um, we we emphasize that a lot in the decision to build versus buy, right? How how quickly can we do this internally versus externalizing this? Um, are these the best players on the field to be doing this? And so there are companies like EQT today. um EOG comes up a lot where they have some amazing talent, right? And they very much should be continuing to to build internally because they've acquired that talent over the last 10 and 15 years. However, for other organizations like I think we're kidding ourselves if we think that we're going to even remotely get the best software talent because the best software talent is going to Silicon Valley. They're going to work for Facebook, right? And we're kidding ourselves if we think that the software talent that we're hiring, you know, for a West Texas Perian company is even really remotely be able to compete with a software company where that's their sole focus and their sole job, and they're going to be the best tool or player on the field to solve that problem. And so, being a little bit, um, less, less egotistical or prideful around, you know, what we're the best at, and really just encouraging people :like "You need to focus on what you're the absolute best at and surround yourself with other individuals that are the best players on the field for those specific, you know, use cases and problems." Yeah. Uh that's so spot on because uh there's I mean there's so much there, right? like the the

again it just boils back down to that time piece, right? Like if you can subscribe to a software that's $10,000 a year that prevents you from hiring someone that's $50,000 a year, that's a pretty easy like back and forth, right? Like it's but yet that becomes such a like difficult thing for you know generally speaking the industry to kind of think like just you got to change the way you think about it, right? And then to your point too, right? Like, not only are we not getting the we're not going to be able to compete for that talent; but even then, it's like, "Okay, they're looking for it, they can pay them .if" If, let's just say hypothetically speaking, everything's on par as far as compensation and stuff, but then it's like, "Oh yeah, but you need to be in Houston or you need to be here," right? Like just the mentality, the mindset of the the way they approach it, right? is It's like, why would I live in Houston if Facebook's willing to pay me the exact same amount of money to let me live wherever the hell I want to, right? Like, and there's just that much little extra nuance there and all those little things too, and so it's uh. yeah and then on top of that even if you built the software you still have to maintain and retain that person even if you got that unicorn yep there's nothing to say that you're not going to get recruited by Silicon Valley or you know what yeah and we always what happens if that person gets hit by a bus. I think um I think it going back to like when we started um I see a lot of desensitization in the industry right now and it's a function of just having like inferior type of solutions that we've just gotten accustomed to like oh there there isn't anything best. This is just the way it is. I'm okay waiting for my Pelaton well view to take 15 minutes to load or the fact that every click is another minute or two to load in this somewhat archaic legacy style interface like why are we still working in in you know folder directories Right, um, and it just comes down to education of where I feel like, if, if the industry had understood like there's other solutions out, there's what they feel like, then I think a lot of people would almost have, you know, um, the analogy I use is like we're walking on a treadmill that's like at an 8%incline. Although we have no idea we're at an 8%incline. Until you get off that treadmill and you have no incline, you're like, "Holy [ __ ] I was on hard mode for the last three years. This is easy mode now." Um and you know, reinstilling that belief um that that there's always a different way to do things and sometimes the way we're doing it today isn't absolutely the best. And it comes down to, like, okay, if we can quantify how much time that's costing the organization or the things that we can't do, then then we can determine: is this something work is the juice youth worth the squeeze? Or is it truly, like, "No, this works for us and we don't need to focus our time," versus instances where thousands of hours are being allocated to it but our mindset is, like, "Well, that's just the way it is, that's the way it's always been," versus, like, "No, we should actually be thinking about this differently because this is unsustainable." If we lose these two key point in the process, the process is going to slow down dramatically by 60% because of that tribal knowledge. And so all goes back with with Salesforce, it was getting the tribal knowledge out of our team members. That way we could be the most efficient operator, right? Let's not take eight weeks to on board a new technical member. Let's take a week, right? And to do that digitally as far as nope, all you need to do is, you know, go to this one page here, not these eight different applications or 15 different bookmarks in your browser. Um, here's the dispar system. Everything's linked directly in the guide, just like a notion page or something like that and it takes you directly where you need to go, right? Like that's uh Yep. Well, and to your point too, right? Like y'all use Salesforce, but you didn't get rid of everything else, right? Like Salesforce is the repo and you still had the end users using the tools that they knew or wanted or liked or were best or whatever uh on that end. So it's I I completely agree like that this kind of centralize the important information, make it easily accessible to everybody who needs it. So yeah, you're not having to build dashboards for people to be able to see, you know, all these things. It's like it's accessible to anybody in the company and it's accessible the exact same way every single time, right? Um, I'm curious actually on some of your your uh experience and and both good and bad on kind of R and Python tools and libraries that you used during your time and some of the the different projects you were working on.

Um, spent a lot of time and it all goes back to uh our passion for backing combo curve. uh spent a lot of time mutating libraries um specifically the ARPs DCA package within our Derek Turk just by the name former guest. Yeah, sorry. Derek Turk was on the one of our first guest author. Yep. Yep. Yep. So, um, that's really where I cut my teeth in program. And we had a a big project where it was my brother's expectations that we could put an EUR on every single well producing in the country because, they're they're not the smartest guys in the world that I know, hands down, but not petroleum engineers that like understand that, oh, like you can put a function in Excel that will tell you the EUR well. No, like that that is an analysis and an interpretation. And so I cut my teeth when I had my big project to forecast an EUR every single well in the country because the mindset was how do we know that the dollars we're investing in the Marcelus is the best use of dollars in the country. We're very mindful getting the best return for our shareholders. So we need to be ultra ultra confident that we should be continuing to invest in the Marcelus versus some other play. And to do that we needed to understand what is our interpretation and viewpoint on every single play in the country. And fundamentally that comes down to every single well. So spent a lot of time kind of custom tuning, fine-tuning our ARPs DCA packages, a lot of our our modeling um and then leveraging some of the stats packages there. I spent a lot of time um learning about distribution normalization models. I see a lot of I'm not going to throw rocks here because I think there are specific use cases for that, but see a lot of black boxes. Yeah. on the market around predicting well performance. And the thing that really resonated for me was when I I I I started off on that path, you know, doing some type of random forestry modeling, right? And it would it would spit back to me some answer and um my my brothers Toby and Derek would be like, "Okay, now show me three instances that like I can see on a scatter plot or some other bar chart that like communicate that trend." And then that's where I had empathy for my customers which was like ah [ __ ] like I I can't show a simple scatter plot that communicates um stage length has a higher order variable influence on wellp performance intensity. Right. I got it. And so and I didn't have that that luxury with my brothers. They they held me to a higher standard in terms of being able to communicate and get everyone on the same page. like why are we focusing on our stage and our Perf design rather than pumping 4,000 pounds per foot, you know, where with what the the market is, you know, trending. And so I needed to be able to put things that everyone could understand. And so I went from more, you know, blackbox ML models that I I couldn't explain why they were saying what they were saying and I went more towards it a hardcoded um distribution normalization angle. So when I look at a distribution of wells of a population that have these type of features, right, and I compare it to a different sample set of wells with a different set of features. Now I can understand how performance is related and I can scale the distribution of one set to another set. And that gave me the cold comfort of being able to explain um well why do you think this well would have had a 40%uplift if we did this other completion design? Well, here's that sample set of wells and their performance as to why I'm scaling this well up or down 50%of what it otherwise could have done if we did this other completion design. If that makes sense. Yeah, 100%. And I mean explainability is a huge piece and that's why I mean everyone wants to rush to their like you said random pores or xg boost or whatever but it's like I mean sometimes again linear regression if you can make that work if if it's within a similar amount of uh properties um you know what I might miss the word but like accuracy. Yeah. Um, then, you know, it's gonna be much better because, again, most people can look at a a plot and see, "Right, here's a line, here's how it, you know, fits, fits the points." I mean, like, they can understand that, but if you just give them, "Well, this is, you know, 5% better," but as a deep learning model, like... so what I don't even know what the heck happened in there and then you don't even know if you're overfitting you there's just so much that goes into it yeah and and I always just thought back to one of my professors at&m he he would joke like you know what a resour engineer those guys and like you know we get all these technical answers that were like super in the weeds and he would just dismiss all of them. He's like no we draw straight lines through things that are not straight linear. Yeah, that that's what we do. And so I took that like to heart in terms of how can I linearize all these nonlinear equations. And so my passion for data analytics it it actually started in um 134 um around uh quantitative multivaried analysis. I had a project at Chevron that I proposed which was how can we understand uh these completion design trends. So this was Delaware basin. There there was less than a thousand wells drilled in the Delaware basin at this time. And so you know cut my teeth with data mining um the railroad commission and the New Mexico putting all that into an Excel sheet. And then my mentor at that time um Bryant Folk you know educated me on like this is what I don't want to see Ryan. And he would show me examples where there was just like a shotgun scatter plot. He's like, you know, here's this this arbitrary straight line fit with an R squared less than 02. Uh, but I can draw a vertical line through these data points that has a stronger R fit. And so I better not see this, you know, in six months. Ryan, this is this is an example of what I'm looking for. And I took that to heart and really just started chasing down how do we start normalizing our data sets um to account for that peripheral variable influence. And so, um those, those are some of the services that we do at ResNet even today around intelligent flow control and helping engineers understand the multivaried, uh, problems present when we're thinking about, "How do we, how do we optimize our asset development program, right? Should I be focusing on well spacing? Should I be focusing on completion design? Or, alternatively, should I just be focusing on optimizing my drill schedule to mitigate against future children infill loss?" if that's the if that's the one thing I can do that's an easier problem for me to solve than um you potentially come up with a new theory around modeling the subsurface that you know tells me this completion design variable is more important than the other. Yeah, I think one of the big like challenges that a lot of people have in our industry, especially because we've full of engineers, is uh one, everyone has to know how things work, right? So like blackbox AI not going to cut it, even if it is better, um, most of the time. And then, you know, the other part of that is, you know, this kind of back and forth between physical and statistical models and analysis, right? Like you've got, and typically it's very divide Ed; you're either in one camp or the other most of the time. Excuse me. But I think a lot of uh my observation so far has been it's like the best solutions end up being a hybrid of both, right? being able to statistically model the physical characteristics or statistically model, you know, the things that you believe are going to happen based off all this historic stuff so that you can quickly turn around and make, you know, if it's for an operational decision. It needs to be fast, right? You can't go run a basin model for two weeks and then come back and be like, "Oh, yeah, okay. This is uh now we've got the answer, right?" Like, "Thanks, Sherlock. I needed the answer two weeks ago." And so, like, I think that's where a lot of people struggle because you, you know, oh well, you know, like we were talking about frackets and parent child stuff, right? Like, we've known for a long time that we've been getting communication and stuff like that, but people struggled so long with, like, how do we model that and stuff. And, like, one of the best solutions that came out of all of that was Devons, where they're monitoring, you know, offset wellhead pressures at the surface with, you know, better gauges, higher resolution gauges. But it's a pure statistical model because it's b My understanding of it is it's mostly just based off forces, right? Like, it's a very basic thing because, at the end of the day, even if it's, you know, the nanodaries are slightly different or the Young's modulus or the brittleleness or whatever are slightly different, when you look at everything on a net scale, the rock, generally speaking, acts exactly the same, right? They might fracture in different ways. They might do different things, but within a reservoir, within a field, the rock is low perm nanodarcy rock. It it doesn't matter what what parameters change 100 feet out from the well board generally speaking, but like you have to start normalizing some of those things to do statistical models which a lot of people like at the core struggle with where it's like but the rock's different. It's heterogeneous, right? Like my you know all of those things. It's heterogeneous if we're if we're comparing two grains in the rock but on a 1,000 square mile basis. this is the most homogeneous type of rock that you would get cuz it's it's variable in the same degree um you know section to section. So you're absolutely right. I think really focusing on what's in our control and then focusing on what's in our control versus what's out of our control. And you're absolutely right. We've had the most success with a hybrid type of solution that is going to be founded in physics. Right. Right. But then mutated and invented with respect to statistics and probabilities. Yeah. Cuz I think you saw a lot with like type curves as well. I mean, I know like when I was at Kico, was like, I think they went and tried to do all the traditional, you know, physical models. And the technology group and, it was like, "No, if we just do a P10, P50, P90, and again, group like wells together in, you know, certain G based on certain parameters, we can actually get a really good prediction of what the next wells are going to do." Well, yeah, that's the whole thing is it's like it you having explanability is a good thing, right? Like being able to have a logical reason for why you made a calculation or went through a workflow is like where all of this should be started at the end of it, right? Like because you know, one blackbox, there's no way to explain the logic of how it ended up with that answer. But then two, it also helps you figure out how you're going to get there, right? Like, hey if, if I need a real time or near realtime answer, a model, a physical model, is not going to work unless we throw a [ __ ] ton of, you know, compute horsepower at it. And then where do you do that, and how do you pay, and it's expensive and all this other stuff? Versus, hey, you know, like the, the speed of your data is important, and a lot of people don't even think about things in that term, right? Like. yeah you know your production data do you need it more frequently than 15 minutes maybe at times if you're doing a specific test are you making up a decision Right. Exactly. Right. Like are you actually going to make a decision if we get one minute data or is that just actually going to complicate that's going to 15x everything? Right. Um and so like you mentioned um Devon's approach with interference modeling. Um we're actually working with Devon around um one of ResNet's services around what what we do is flowing well interference tests. Uh and it is empirically statistically based. um and being able to have that explanability, right? Um and so we've taken that approach because well spacing, communication, child infill is is absolutely kind of the highest order variable when we think about optimizing the development program. Um the problem that we have um fundamentally with something like a child pressure group or in this case even more bespoke with the with the GQI is I have to shut in a well, right? So, I either have to shut in a well or I have to do it opportunistically with respect to I'm going to be shutting this vault because of an offset crack. Well, um I can empathize with engineers with respect to like well I'm not going to get this data for every single well. So, how much should I be trusting this insight? Because it's one data point, um, across dozens potentially. And fundamentally, I would like to have a solution that I could theoretically apply to every well. And if we can solve the production deferment problem without having to shut in wells, that's interesting, right? And so, um, that's one of the ways, you know, as any bootstrap startup, we need to work with operators to understand fundamentally what are the true problems. But we also need to stay alive, right? Be able to keep the lights on and make sure that everyone can pay their bills. And so, we spend a lot of time on the services side of our business with these bespoke, um, flowing well interference tests. Yeah. Um where we're making very small minor control changes with the chokes on service. Those are making pressure disturbances between all the wells and we developed at Rice Energy, you know, a workflow to be able to take that pressure data to quantify the level of communication between wells. Um and so that's been a lot of fun. But in some instances, I still see some engineers where, you know, because they can't model it in their reservoir simulation model, they they write it off. Yeah. Whereas it's like, hey, man, but if we all look at this data right here, we would all fundamentally agree that there is something going on. And if we can all agree as to what that variable is, I necessarily don't need my reservoir simulation model to be able to replicate that. Yeah. Right. Even though you come up with different data, you'll come up with different models theoretically if you did if you both did the same, you know, reservoir model, right? Like you might use different inputs, you might tweak something here or there versus, hey, here's the statistical data. We would literally all draw draw. Data is king. Yep. Yep. So, let's make sure we take some time to talk about reson. Yeah. No, that's exactly where I wanted to go right now. So, let's talk about some of the design choices because I mean, I think there's two sides of it. I mean it sound like again you said at Rice y'all were working from you know the lease to the wellhead. Now you're talking about working backwards from there. So there's that side of it but then also um about like design choices like again you got to start in 2020 again clean slate modern technology like what did you choose why I mean did you go cloud I mean onrem you like all these different kind of um design choices. what what DBs, what cloud, and what uh language stack or whatever. Yeah. What's your what's your stack generally? Sure. Um everything's on AWS. Um that was a rather easy decision just seeing where a lot of startups were were heading. They were heading there for a reason, right? And I wasn't going to an overanalyze that as to why are you making the decision? Maybe I should be looking at Azure instead. Um AWS just had kind of a better reputation from all of the actual tech guys. Yeah, that was so they're not in oil and gas. They're in traditional ERP gas unequivocally all like no you're going we built everything in AWS as far as our backend goes. Um similar solution as I try to approach alls is usually a hybrid is going to yield you the best results. So we have both a NoSQL backend through [ __ ] Um we do that for a lot of our our containers and our document management. um just an easier it's the best hammer for unstructured data. Um so we'll use [ __ ] for a lot of our containers with respect to dialogue. Dialogue and communication is a huge component of our solution. Um and then we'll also just fundamentally you need to have a relational database right so uh we started with Postgress SQL just very easy breezy something we know is going to work right um but recently migrating to a more uh better solution which is redshift serverless through AWS which is essentially just Postgress like on mega steroids yeah that's um because like the data wear out so I mean so so you're using that more for the data like warehousing or data analysis side of it. I mean because um you know typically you use Postcrest you know with a web app for some of the transactional type data but you were using it to you know chew through the data and everything as well. So using like Redshift to you know chew through lots of data and do do it quickly. Yeah. So anything that I would say is is um more of like a a digital tool to replace something that we would otherwise be doing in person. like communication, we're going to use a lot of [ __ ] for that. But anything more technical, which would be like more of an analytic tool or a model or something that needs to run a scenario on, that's going to be more structured relational database that's going to be usually living in Redshift. Cool. And then what uh what language did you build it in? No.JS is on the back end, so JavaScript. Y um and then the front end is going to be React and React Native for the mobile app. So, I'm an engineer in the industry. What what do I come to uh to ResNet for? What is ResNet going to change for me? What does it do for me, so to speak? How's it going to make my life easier?

Um I I would probably start out with a discovery. Um we as a platform we have a lot of different products and features for different flows or problems and pain points. A lot of where our current partners are leveraging some of our solutions um start off more on the the data and the dashboarding piece. And so when we think about the digital evolution of an operator um Toby came up with this and then I refined it a little bit just being the little brother always have to you make it a little bit better as an engineer. Um, but we think about providing engineers and your field force with what we call a 4D experience, right? And so when we kind of survey the landscape, I think we would all agree that for the most part operators today have fundamentally a strong data foundation, right? B, you guys are using Snowflake and everything and you're managing the data analytics. Uh,

there's no doubt that you guys understand how you need to be structuring and accessing and, you know, transforming your data set. Um, but in instances where that's a problem, we can be helpful. Then, when we think, "Now we need to be able to visualize our data ,and" and so the second D of the 4D experience is our dashboards, right? And we pride ourselves on making something beautiful, something that you like to use every day, that's very self-intuitive. Um, a lot of operators, you know, especially the larger ones, feel very confident around their dashboarding capabilities. Um now where we see the world getting very small very quick are operators that feel that they have great data, great dashboards infused with dialogue and a communication and so our journey with a lot of our partners starts off with providing a more robust um insight foundation. Right? Right. So it goes back to I feel the pain points of the engineers especially in instances where like they might be having to migrate from Spotfire to PowerBI. But if I can give a tool to those engineers that respects what it is looking for in terms of centralized repository as far as those analytics. We found that it is a little bit more open to allowing the engineers to use the tools that they that you use. So we have an integration middleware solution where a lot of our engagements start around centralizing your analytics and your insights and then a lot of our features are going to come down to taking that insight and driving it to action at the end of the day. Um and so on the office side it's about organizing our systems, our processes when we think about production operations and how do we get the right person to the right job at the right time. How do we have the accountability that, you know, our managed scheduled maintenance issues are being taken care of in conjunction with emergent issues, right? A pad is esding the second; that's a higher priority than me perhaps greasing this wellhead that can wait a few hours, right? And so, a lot of our tools and features are going to be centered around, ultimately at the end of the day, driving insight to action. And how do we organize that in the best way possible such that it's transparent to the entire organization? How do we, how do we maximize our GNA efficiency, right? Um, what we want to stop is two engineers potentially doing the same problem, right? Unbeknownst to one another. Well, that that's a conflict for the business. We are allocating double the resources to the same problem. But if we can have something as simple as a combine board that a lot of software developers use, right? Well, now I know what my peers are working on. And so a lot of the from there once we help build a more uh better data foundation and insights um that's where the journey starts. And so we we have a lot of skill sets with respect to centralizing all the different data tables insights that production operations teams have to use to get the the job done day-to-day right and there's 12 plus different systems and and data um sets that go into that. Right? as a production engineer. Um, I care about, you know, obviously what is this well doing today and what is this well doing in rel relative to how I might model it from an from an operational perspective. I care about what our forecasts are, right? Because um, you know, we might have a certain um, we might be graded in terms of how we're compensated as employees around budget versus actual, right? With respect to what we're communicating to the street, right? So, we need to have our reserves and forecasts. We need to have our costs in one place. Yeah. When we think about prioritizing that work, um, we need to have good dialogue. Um, so that way we can understand, well, why did we make this decision in the last workover? What did the tubing look like when it came out of the hole? You're saying there's a lot of holes in the tubing due to H2S. How do I know it wasn't wear and tear from the pump? Right. Right. Well, let me see the actual pictures that came, you know, from that workover. And so a lot of it's just fundamentally focused on communication and providing conduits through which engineers can better organize their technical work, better prioritize work orders that need to be executed out in the field. Um, and then from there we we have a wide suite really depends on who I'm talking to as far as some of those other feature sets go. Um but whether it's operational campaign management right and being able to understand we have 80 different initiatives out in the field and where each one of these initiatives progressing right and seeing that in real time. Uh a good example of that might be the pressure that we are feeling as an industry to respect the recent uh inflation reductant act right um starting in now 2025. They they've punted the the start date on when we start getting fined, but starting in 25, we're going to start getting charged $1,000 per ton of fugitive methane emissions. So, I see a lot of startups focusing on the detection of those methane emissions. Um, but fundamentally, we need to execute on something, right? So, great, I have emissions coming from this facility. Well, I need to replace the pneumatic devices within this facility and I have to also replace pneumatic devices across all of our facilities. And that's where I see, um, not a lot of organizations having the visibility that I think that the shareholders deserve to have, which is: all right, we have 3,000 pneumatic devices that we need to retrofit or replace over the next 18 months, and hopefully management has the visibility to communicate to our shareholders as far as how we are progressing on that campaign, so that our shareholders can sleep easy at night that we're not going to get hit in the face with a thousand done per thousand dollar per ton charge. And so that's where we focus a lot of our workflows and our features and our tools which is allowing the engineers to do what they're going to do. You guys are we're never going to stop building new solutions, new custom bespoke code or dashboards. But what I want to be able to do is give you tools where you can connect those tool sets, democratize that across the entire industry and then digitally execute on that work and provide that transparency to upper management. And you've you've also added a layer of gamification to it too, right? Like cuz that's as a I became a mechanical engineer because I wanted I hated how things were designed and how like poorly how poor the user experience was and this literally started with my car in high school. But um you know like so many people don't and lots of users of oil field software especially legacy softwares understand this but like the UX and the user experience of traditional oil and gas software is so bad. And so being able to add things like gamification and just a modern UI to things can just completely change how people use your stuff. So I just want to give you a second to kind of talk about the gamification piece before we have to wrap up. Yeah. Yeah. Um to your point, I think that was the first thing that we focused on at ResNet. Um for me it was out of the empathy of like I never had a tool that I actually fundamentally liked using at other than Salesforce. Yeah. And Spotfire and and Altrix, right? I had my tools that I loved because they actually fundamentally helped me with my day. But other than that, it was always like a chore, right? And so that was the first thing that I wanted to solve for this industry is providing a platform that people love to use and it has to look good. It has to feel great. Um, if I'm going to love using it every single day and if that's my expectation is this is something you will use every day, well, it better look and feel great, right? So, it started off on the design front. I think that that's something that we has allocated a lot of resources and investment towards um making sure that you know this this feels great. It looks great. I like working in this. And then it came down to the gamification. The gamification actually um like a lot of the things that we're building at ResNet came from some observations that I had made at Rice Energy. Um and the story that I tell is and I I'm repeating myself here because I was telling Colin and Jake it last week. Um, but we had just made a large acquisition at Rice Energy. This was in 2016 2017. You know, we had bought out Vantage for for 4.4 billion. And, uh, you know, Toby's, you know, on CNBC telling the street, you know, these promises, uh, like any great founder, you know, does around, um, what we're going to be able to do with these assets, and really stresses that we were so efficient at Rice with our digital tools and our architecture that we were going to be able to absorb these assets with no new hires, period. And you know being one of the guys like in the trenches shoulder-to-shoulder with the team members I'm just like what what did you just promise man? uh that is physically impossible and let me tell you why. Right? And I'm looking at our work orders and how many issues we're having every single day, and the typical number of issues that we're able to take care of every single day. And out of, you know, thin air, here's another 200 sites and almost a BCF a day of gas that we need to manage, and somehow, someway, be able to manage this with no new people. Um and Toby just like laughed at me when I was just like, "Why would you do that, man?" And he was just like, "Well, this sounds like a you problem, Ryan. this sounds like a technology problem. And I was just like, what the [ __ ] Okay, so you know, I'm for 6 weeks, you know, plugging away at my keyboard trying to, you know, automate these data transfers, these processes, working on these form fills, you know, to save the guy an extra 10 seconds every day, thinking like that somehow is going to influence how many work orders he can do. But the end of the day, nothing's going to influence how much time it takes to move that wrench. Yeah. Right. And during that time um Salesforce had had released its first and one of its only um gamification features around custom badges. And um culture is something that you know is very important to me but more importantly to to our family and and the businesses that we run. And so, um, you know, after a hard day's work, instead of, you know, going home to our wives and family you know, who would do that?you know, we were, you know, ordering pizza at the office, and we would just be like,"Okay, what are some other KPIs and milestones we can digitize for these badges?"And so every night we're creating all these different badges: you know,"Oh, execute 10 work orders in a single day,"or for drilling, you know,"Drill 10,000 feet in a single day,"or complete"10 10 stages per day." We just started thinking for every department, how can we start digitizing these badges? And it it was just fun at that point, something fun for us to do that was still related to work. Um, but during that journey, I I I started to notice in some instances maybe Toby and he wasn't walking around the office as often and, you know, shaking people's hands and giving him a you know, hey, good man, good job, man, on that. And um you know I came to him I was like hey man I I don't think we should be replacing you know that that face tof face you know recognition that kind of makes us special with these badges. I I don't know if we're going to get the same results. And he just like dismissed me. He's like no man the people are going to love it. This this is awesome. And I was just like no no like this is bad. But then you know I was looking at our actual work orders right this was something that I was focused on and everything I was doing wasn't actually moving the needle. Um, but then as I started to look at the data, um, I noticed a peculiar trend where for our top 20%of our field operators right, kind of paro's principle, you know, the top 20 people do 80%of the work um, I noticed about a 30 to 40%uplift in their work order efficiencies. Um, and it was statistically significant, right? I had four years of very consistent data from, you know, guys that were just absolute workh horses. Um, and for to see a step-wise change in their efficiency, that was interesting to me. And so I called um, one of my one of my buddies, one of my best friends up, I said, is Kenny G. I was like, Kenny G, you got to tell me what what is your secret? I'm noticing that you are absolutely killing it lately, man. You're up 40% in the last six weeks alone. Are you taking steroids? Are you juicing? like, "Do we need to juice the rest of our fields?"And he was just like, he started laughing at me. And this guy, you know, mind you, he's he's in his late 50s. He's laughing at me and I'm like,"Why are you laughing at me, Kenny?"And he's like,"I think it's I think it's those stupid badges that you and your brothers keep making every night."And like I was I was literally jaw-dropped like,"Wait, what?"Cuz I'm thinking like I'm giving Toby grief about this and I'm totally wrong in this point and Toby's right type of thing. But he's like,"Yeah, you know, see, I yeah, I used to wake up in the morning. I look at this long laundry [ __ ] of stuff I got to do in Salesforce, and you know, it's great. I know I know exactly what I need to do and when and where, and you know, it makes my life easier, but it's still a laundry list of [ __ ] I got to do every day. But now, um, the first thing I do is I go to Chad's profile page and I look at the last badge that, you know, you or Derek gave, and it becomes my life mission to get that badge, Ryan, cuz, you know, I'm the number one field operator in Green County. you know that, right, Ryan? And like I'm just on the phone with him. I'm just like, "Oh my god." Like I I I I thought I found like a cheat code, right, in a game or something. And so that that was the first insight um that got me interested in perhaps approaching problems differently. Right. Right. To that point, I'd been very technical like, hey, we have to have good code, has to be well organized, we have to process to this. And it started my open my mind a little bit more to like the human element of the business and the cultural element of the business. And if if we can provide a system, a workforce recognition system that fundamentally taps into those drivers, right, that motivate people, how can we motivate people in the best way possible? And so that was one thing that we've really taken to heart with ResNet around our gamification. And so, um, you know, uh, my experience with gamification has just been like most other guys in girls in the industry with, you know, video games, right? So, I had my ideas of like, oh, we can do this and this and then um it wasn't until we hired our head of um product experience. Her name's Aaron Fair. Um you know, she's dedicated her life to gamification studying um you know, social behavioral psychology. Um she's an adject professor at Westminster University. And so, she opened my eyes into no there's like this is not only an art, but there is a science to it and here's why. And so that's something that we have allocated a lot of resources um towards building which is a native gamification system that really is essentially tapping into the different personality types that that are that make every human you know a unique snowflake to some regards. Um but in gamification lingo it it's um your player archetype. Yeah. So you know you could do these personality tests that you know sometimes they use colors or you know animals or whatever. Um, in gamification land, it's what player archetype are you? Are you a killer, like you like playing Call of Duty, or are you more of an explorer, like someone that likes playing RPGs, you know, by yourself? Or are you more of, you know, a social gamer where you can't be bothered to play single player game modes by yourself? You only get enjoyment out of a game with playing with your friends. Um, and it's taking all of the different player archetypes and what features, what behavioral um, tendencies can we inject into the system to understand, you know, what makes this individual tick? How are we going to be able to tap into that person to motivate them intrinsically, not only exttrinsically, but intrinsic motivation? Um, because that's the number one driver at the end of the day, right? If you don't if you don't love what you do, you're you're probably not going to be the best player on that field. But if you fundamentally love what you do, it's very easy for you to be a competitor and to be the best player on the field. And I think that that's, you know, kind to some degree our higher mission is to provide everyone the opportunity to be the best player on the field. Um, and so things like, you know, um, bespoke field data collection initiatives, right? Um, as an engineer, I have deep empathy for all the [ __ ] the field has to do on a given day. They're the ones keeping the lights on, keeping the gas flowing, keeping the oil flowing. Um, If I, as an engineer, opportunistically want to understand if there's casing hangers on a wellhead, I I don't I don't know about you guys, but I'm reluctant to ask my field operator like, "Hey, when you guys get a chance, can you take a picture of every single wellhead and then put it in this, you know, folder and also, you know, name it this way?" That way we can, you know, hook all of our systems and it all works great." Like, no, I'm never going to ask my guy to do that. But if I could gify some of those initiatives without, you know, it being a a specific initiative, something that we opportunistically do. In this case, we'll implement a playlist, a challenge playlist where we can digitize some of these behaviors like taking pictures. And so if I want to get updated pictures of all my wellheads, because that, you know, on an inspection basis, that's just something fundamentally good to have, right? For our engineers to know what the wellhead looks like in the office, they're not going out to the field. Well then rather than force my field just another thing they have to do perhaps it can be more opportunistic like hey you'll get extra XP points today if you take a selfie you know buy you know a wellhead and you tag the well And so they get XP, and then we can tie those XP to not only ex exttrinsic rewards, but then it ends up fundamentally becoming intrinsic once people can compete and see where they're standing on certain initiatives. Um, and so we can track all of that, and we can make these, you know, initiatives a little bit more fun. I think you are you're on to something really big just because it's I mean as you mentioned right it's in video games it's on Reddit it's on you know more and more every new app there's you know an onboarding checklist or you know you get points for onboarding and filling out your profile and all these things right and it's It's think about your career development, right? Like,"here's all, here's my resume," right? And so, um that, that's not our focus right now. But when I think about collaborating ating with Digital wildcatterers around, you know, potentially jobs and workforce, right? Well, if I can provide tools that do this intrinsically for, you know the, the employees for the, for the team, right? It makes it really easy to provide a world in which, you know, you can see fundamentally: what is the experience of person A versus B? Here's exactly where their skill sets lie. You know he, he's specialized in these specific types of workovers versus these other types of, you know, facility upgrades and maintenance, things like that. Um, and so really just comes down to providing easier tools that we can use to illuminate these data sets right now, um, that aren't being measured. They're not being tracked. Yeah. No, that's that's awesome. Um, we are right out of time, which is crazy how quick that went. Um, cuz I Time flies when we're having We're going to be We're sit here for like three hours, but no one wants to listen to us talk that long. Uh, no, we'll be having some some more conversations as we start uh putting together all of the gamification stuff that we're working on with Collide. So, I'm excited about that uh that. But, we'll roll into to wrapping it up. We typically end it with just a speed round. We'll kind of pepper you with a couple questions. Just give us your your gut answer, your short answer. Short answer, and then we'll uh wrap things up. You want to kick us? Yeah. Uh, so who's your favorite uh social media follow?

Next wave EFT. Yeah, that's a good one. What? Yeah, I don't know if you got to follow him. He's got some very strong technical but also, you know, funny content saying what I think a lot of people are thinking. Has to be Next Wave EFT. Those are those are the best where they know what they're talking about. And that's on Twitterx for people who are not aware. Yeah, they're not. He's a he's an anonymous. Um, but shout out to Next Wave because his content is absolutely fire. Um, here's a good one. What are some of your favorite uh R Python packages libraries? Arps DCA. That's just probably my number one. Shout out Shout out Derek. Yep. Yep. And then just the basic stats package. So, not a good answer. probably. I mean, it makes it makes sense. But what's your uh what's your favorite place to go on vacation?

Mountain, beach, or my wife my wife would say I don't go on vacation. I I work. Uh it has to be snowboarding though. Love to board. That that's one thing where I can I can actually unplug and Yeah. kind of an adrenaline junkie to that degree. So, probably boarding. Well, we'll wrap it up with this last one. What uh what's some advice you'd give to someone getting looking to either transition into the energy tech space or coming out of school trying to get into the the energy tech side of things?

Number one, that's a great question. Number one piece of advice or just some advice that you've kind of picked up along the way from your your experience.

Be okay being uncomfortable. Yeah. Um that's usually when when you're growing the most. um have empathy for your peers, right? Um there there's a lot of ego in this industry. U I think we'd all collectively agree with that. You know, hear people talking about pissing matches and I think that's just the nature of our business, right? Because it is a dog eat dog world. Um, but having empathy for your team members because if you can be a good team member, I think that probably when I think about advice for someone coming into the industry, probably going to open the most doors for you in terms of being helpful because this industry is so small. You don't know if you know the good Samaritan act you did for someone is probably going to pay you 10 to 100 times return on investment at some point in your career. Um, and so just always trying to be helpful to your team members and understand where are they coming from and how can I meet them halfway. Yeah. Or vice versa too, right? Like I've I've known many sales guys that, you know, overpromised and underdel just because they knew they were going to get that commission on their whatever and then do like do what you say you're going to do, right? Um, I think fundamentally everyone needs to do that, right? And and have that accountability. Um, cool. No, that's a good one. Probably stick with the empathy. That's a good one. Where can uh where can people find you? LinkedIn, Twitter, ResNet.

Not the best social media guy. Um never never have that. You've been posting pretty but I am on LinkedIn. I'm on LinkedIn. Been trying to learning learning from the greatest here. Um I'm on I'm on LinkedIn. I'm on X. Uh my handle's uh do you even frack, bro? Um same same handle on Collide. I got your notification the other day. Yep. I'll be uh you know creeping on Collide seeing some good content and some good questions from the community coming on there. How can people find out more if they're uh interested in chatting about ResNet? Um they can go to our website and if they fill out a form, I can promise you that goes directly to me. Um and we will reach out within five minutes. Um unless it's, you know, at 2 am in the morning, then I'll get to it the first thing in the morning. But they can quite simply go to our website, fill out the form, fill that goes directly to me or you um alternatively you can DM me on LinkedIn. Um I try to check that probably once a week. Um or they can email me quite simply at just ryanresnet.ai and it's renet.ai. Correct. Correct. Cool. We uh we appreciate you taking the time, man. Yeah. No, thanks so much. Appreciate you guys having me. No, this is excellent. A lot of fun. We'll do it again. Take it easy, Ryan. Appreciate it. Thank you.