Energy Bytes

Jeff Hughes, founder of PointFlow shares his journey from accountant to tech expert and explains how his contrarian approach to traditional systems led to the creation of PointFlow. The conversation explores the impact of low-code software solutions like QuickBase, the debate between cloud services and on-premise setups, and how energy companies can stay ahead by modernizing their technology.

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 - Podcast Introduction
1:13 - Guest Introduction: Jeff Hughes
7:45 - Launching Revolution Resources
10:48 - Cloud Technology vs On-Premise Solutions
12:24 - Field Operations in Energy Sector
15:52 - Understanding Unique Well Identifiers
22:25 - Accounting Practices in Oil & Gas
23:44 - Operating Challenges in Oil & Gas
27:10 - Standardization Issues in Oil & Gas
29:20 - Introducing PointFlow Software
33:39 - Cloud vs On-Prem Revisited
39:20 - Analyzing Energy Sector Costs
42:50 - Energy Data Security Concerns
47:45 - Exploring Quickbase Platform
51:18 - Quickbase: An Overview
53:46 - Speed Round with Jeff Hughes
55:54 - Jeff's Book Recommendations
56:40 - Jeff's Top Social Media Picks
57:50 - Favorite Databases in Energy Tech
57:58 - Preferred Cloud Services
58:10 - Connecting with Jeff Hughes

https://twitter.com/collide_ai
https://www.tiktok.com/@collide.io
https://www.facebook.com/collide.io
https://www.instagram.com/collide.io
https://www.youtube.com/@collide_io
https://bsky.app/profile/collide-ai.bsky.social
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. All right. Well, welcome to another exhilarating episode of Energy Bites. Got my I'm Bobby Neland. I got my trusty co-host John Calan the Rad Dad with me. What's up everybody? And uh excited to have on uh Jeff Hughes. I mean, if you would have asked me a couple years ago um or a year or two ago, people probably wouldn't have thought I would have Jeff Hughes on a podcast because the way we go back and forth on [laughter] LinkedIn, but uh Oh, absolutely. But uh actually become really good friends. Um Jeff is the founder at at PointFlow Technologies. Is that your point? Yeah. Point pointflow.co. Pointflow companies is the parent company to four or five shoot off. Yeah, I know. I know you're work kind of working on that uh that structure a little bit, you know, how to can't really put yourself in a box, but um but yeah, [clears throat] no, super excited to have him on. I mean, Jeff's got a lot of great experience in the energy industry and a lot of opinions, too, which uh which we like. We do. So, especially especially because they don't uh they don't always go with what everybody else is doing, which is I I typically like to go the opposite way too much. swimming upstream makes you stronger.

Uh I didn't realize real realize too that's kind of a pun, you know, upstream oil and gas. So touche. I like it. Hey, you got to have the bad jokes. Awesome. Well, uh but either way, let's just jump right into it and uh Jeeoff, you know, first off, let everyone know who you are and then kind of start, you know, how how did you get into, you know, maybe technology in general? Did you do any coding as a kid? And then just, you know, your background, how you got into oil and gas and, you know, what what got you to this point? Sure. Yeah, it's kind of a kind of a crazy career path. I have a degree in accounting. Um, stayed at from Oklahoma State and stayed there. Got my MBA. I had the perfect setup with scholarship and a roommate that was a bartender. So, I was not planning on leaving that anytime soon. Um, so stayed there, degree in accounting, jumped to One Oak and Tulsa. And, um, my first kind of interaction with coding was I was actually an engineering major for a couple years. And like all of the engineering majors on my fraternity, we dropped out and became accountants. Um, but in the engineering class, there was an engineering computer programming. It was a a VBA behind Excel and how to build apps and how to kind of I laugh cuz I took the same class. At least you had that. At least that was useful. Like I my engineering math was mat lab. It was awful. Well, I mean I loved it, man. I I it was it was awesome. But uh I got I got to one oak and um I was a credit analyst. So sitting on the energy trade floor, which was awesome. I wanted to be an energy trader so bad. They were like yelling deals and I mean they got an argument one day about who had the best barbecue ribs. So they sent a guy to go get all the ribs in Tulsa and they had a taste testing and it was just an awesome environment. And I So they would propose a deal with certain company. and they'd be like, "Hey, credit team, how much risk do we or exposure do we have and how much can we go?" So, I would open up the 10K on these clients and key all this information in to a financial model and it would spit out an answer and I started thinking I was like, "Man, this is inefficient and ridiculous." [snorts] So, I there's an empty Blueburning terminal and I connected that to their model and then built it where you could just type in the ticker and it autopop populated the model and gave the decision. And my boss at the time was like, "Well, I don't have any more work for you now, so just kind of hang out." So, I literally just hung out for a couple months. And they make got made or made me an offer to move to a different company or a different department. And at the time, my girlfriend now wife had moved to OKC. So, I jumped down to Chaparel in the finance department and um kind of did the same thing is was drawn towards the tech side. our um our forecast software is called TM1. It was a cube-based uh IBM product. It was actually really cool, but pulled from Aries, pulled from Inertia, pulled from all these different sources and um gave our finance team the ability to kind of manipulate data and present the forecast. Well, the CIS admin of it left and they were like, "Hey, Jeff, you know this pretty well. Like, do you want to run this system?" I said, "Sure." So, I kind of took over that and kept my tech path going. Um, fast forward a little bit, a guy named Scott Vanickle was an engineer over there and kind of [clears throat] got word of me and at the timeout I was just as argumentative. So I would [snorts] Yeah, shout out to Scott. I think at some point we we bonded over a uh Oh yeah, he's a he's he's a good he he's a he's a genius man. He's he was kind of the reason for my data um love. He just quick note he uh at the company we started together he's the CEO and we basically stood up his own SQL server so he can write his own scripts and do his own coding and build his own spotfire. It's it's wild how much he gets that piece but um so he kind he poached me over to the engineering team to help run well view and data and all that kind of stuff. Um, so we worked together for two or three years there and um, I was kind of at the I was an engineering tech supervisor and um, kind of at the top of that career path, nowhere else to go and had talked to him about and I was like, "Hey, I'm looking for other jobs." And he was like, "Hey, we uh, potentially got this deal coming up." So, we left Chapperel and started Revolution Resources in 2018. Um, which was kind of wild cuz I was having my first kid and told my wife I was like, "Hey, I'm quitting this job and starting a company and she was like, "What? [laughter] Yeah, yeah, we're going to start a um start a oil and gas company." But it was it was it was an awesome ride, man. We uh we got funding from Mountain Capital out of Houston and bought an asset from Gastar, the West Edund Hunting Lime unit. And um it was it was fun. It was four of us. It was like that that small office, you know, the startup casual feel. You're playing playing Smash Brothers at 2:00 and sometimes you're working till 11:00 p.m. kind of thing. But it was it was a fun ride. So started Revolution in 2018. Grew from us four um to we had three acquisitions and we ended up buying Jones Energy and we had like 65 people at that time. And my initial role was IT, accounting, uh, gas and oil marketing, basically everything non-engineering. And I loved it. And by the time we were big enough, it was [snorts] my role was they like, "Hey, you got to you got to wear less hats." Um, so I became IT director. Did that for a couple years and um, got bored with it, honestly. And I was like, I want to start start my own consulting company. And that's where point flow was born is I was like I still want to do accounting and I still want to do it and I still want to build data warehouses and I still want to kind of take on the well views of the world and that was the genesis of it. No, that's that's a common theme on the uh with pretty much all of our guests is there is not like a traditional route to getting into data or or data science or technology at all. And I think that's it's fascinating. Yeah, I think the one constant is just like a curiosity and then like I got a problem, I need to solve it. Efficiency and obviously computers are a huge part of Right. I mean, it sounds like you engineered your job away [laughter] the first, you know, the first time you went to work when you when you automated the uh the reporting stuff, you're like, "Oh, we don't need an analyst to analyze all this stuff anymore. It just happens." Yeah. I was like, "I don't why am I why am I combing through a 10K and keying this stuff in?" So I mean [snorts] this is a connected Bloomberg terminal but let's just use technology. So I mean and I do want to get into point flow but let's step back to revolution. I mean like so you got to stand this up right? I mean like I mean so from the tech and the data side I mean like talk about like what you chose why you chose it. I mean what worked you know heck what would you do do different if anything? I mean, just kind of and then how and then we can kind of parlay that into how has that influenced what you're doing at at Point Flow. There's a lot of a lot of people out there that, you know, oh, if if I could rearchitect it today, this is what I would do. You know, they inherit all this architecture tools and stuff and they hate them. And so, I'm sure that was fun on your end, being able to Well, it's fun and daunting all at the same time, right? Like [laughter] you're like, well, I think this is the right decision, but So, yeah, explain explain some more on that. Sure. Sure. Yeah, we were we were lucky enough to be um at Chaparel for long enough to kind of be ingrained with the IT department and kind of see what they were doing right and what they were doing wrong. So our um our thought and plan was a to be super costefficient because that's kind of what we sold ourselves as a team on was that we were um super not I mean cheap if you want to call it but so we had some experiences with um efforts to build applications internally that costs ran away and it just never worked. So we um had kind of had the mindset of let's find solutions that are out there that are affordable. So we started with um kind of the production software and we were like we demoed a few and we picked we ended up picking iell um mainly because they had an API. It was like, "Yes, here's the app. It looks good. It's clean. You can collect data." But my concern as the IT guy was like, "Can I pull data from this and manipulate it and push it back?" Yeah. I was like, "Do I have that capacity?" So, we picked we picked from the kind of pumper standpoint. We picked Wellview for the same reason is I can as long as you don't move over to that Wellview cloud, you can keep Wellview on prim and kind of manipulate your data and and control your own destiny. So we we did that and that's when we we kind of debated and went back and forth on and this is what Bobby and I always argue about is cloud versus on prim and I I will say what his major counterpoint is always uh like infrastructure or your office and we have the office we found had a great server room had um independent air conditioning and a natural gas generator for backup. So it was a perfect set we had a server rack just sitting there. So, we decided to do on prim. We bought um four Dell R720s just refurbished from a guy named TechMike New York. Um we got those four. We set them up in a little clustered environment and we spun up our virtual machines on that. Bought some ubiquity switches and gateway and kind of that was our that was our uh onprim network setup. Um at at first we were I think for the first 8 months we were just it was about I don't know inu probably 300ish wells. So we were just running kind of the the PDP analysis and how do we cut LOE how do we get production up? So it was just kind of those softwares. It was IWwell well view uh spotfire we threw spotfire on and then our kind of on prim infrastructure. Oh, and Aries. We picked up Aries just cuz. And was I will handling like production accounting like that that was say instead of like America or something like that or No. Yeah, kind of. So pumpers enter the tank gauges, meter readings, all that kind of stuff. And then I pulled it into SQL and ran any type of allocations to because we had some shared batteries that we had to allocate to. Um, and I just wrote the allocations in SQL to then dump to our um outsourced accounting team, Finley and Cook. Um but but yeah and Aras is I mean the banks demanded it at that time so we went with Aries and again SQL back end so you can kind of manipulate it and keep it updated and all that kind of stuff but hindsight I don't know that we would have done much different. It was it was super affordable and um I had it it's funny I had it set up in my living room before we even found an office. We had the servers kind of set up next to my bed and I got a picture of like all these boxes in my uh in my foyer and my wife was not exactly thrilled with it, but [laughter] I was like we'll eventually find an office that we can move all this to. But hey, but man, it was it was a blast. I would I'd do it all again in a heartbeat. It was a great learning experience and um really fun. I think one story you've told and probably just a good one to have on here. I mean, let's talk about maybe going out into the field. Um, but I think you had some said something. I don't know if you were out on a rig or something and they they pulled you up or Oh, yeah. Yeah. I did again being the mindset of cheap is I went out to the field and handled stuff as much as I could cuz that any type of skate consultant or any consultant is pretty expensive. So, I would when we brought a new we eventually started drilling after those eight months. We hired a drilling engineer and geologist and once we did I I kind of did the the IT in the field and hooked up the um comm devices for SCADA. Then I also we ran the internet for the drilling rig. So we we had a consultant out there who was doing I can't remember it was like 100 bucks a day for internet and it was the slowest we couldn't sync on it. The guys couldn't stream anything and the rig's like um about eight miles from our office and we had a threetory fourstory building. history story. And I was like, I bet we could put a horn up here and just shoot it to the rig. So, we bought a little $60 Ubiquity antenna and put it up there and I went and held it out there and I was like, oh yeah, it works. So, [laughter] we we did our own internet and then they had like full streaming high-speed internet out there. Um, that's awesome. So, I would I'd hook that up each location and then we had one location where they were down in a little hole and we could not get the the horn to communicate at all. and um the com the company man was like hey you can climb up the Derek there and uh hook it up and I was like I don't really want to do that [laughter] I'm pretty afraid of heights and he was like I'm not going to do it and I was like okay um like why don't you go ahead and do it and our our drilling engineer was there too and he was like I will he said we'll I'll call you and we'll each get airpods in and I'll tell you like if if the horns can see each other and how to line them up. I was like, "Okay." Well, I told I'm I'm afraid of heights. Definitely afraid of heights. And so we get up to the the Derek to climb it and he asked me how much I weigh. I'm like, "Oh, I weigh 185." And he's like, "All right, cool." And he's like, "All right, strap in." And I'm like, I strap in. He's like, "All right, let let him go." And it it just starts like pulling me up. Okay. Like, "What the hell?" And I'm like halfway up and I just kind of like lock in and Miles is on the phone and he's like, "Ah, the horns can see each other. Go ahead and mount it there." Oh. So, I mount it and got good connection, good speed, and I'm to get down. I'm like having to like do curls to pull myself down. And I get all the way to the bottom. I'm like, "Matt, lever it was the company." I was like, "Matt, what did you do?" He was like, "Well, you told me you're afraid of heights, so once you said you were 185, we set the climb assist to like 215 to make sure your ass got up that rig." [laughter] I was like I was like, "Oh, okay." He's like, "Cuz if you got stuck, I would have to climb it without the climb [laughter] assist and get you down." It's like, fair enough. So, that was my one and only time to climb climb the rig. And I didn't even climb. It just pulled me up. I thought you were going to be going towards the other direction where it was like, "Oh, the harness is rated for 200, so you're good by 15 pole [laughter] pounds like that." Yeah. You know, nope. [snorts] They just yanked me all the way up. But that's it was it was that kind of stuff, right? Oh, yeah. Yeah. I'm sure every safety man would have approved. [snorts] we got it was just a really cool experience to kind of start a operator from the ground up and be involved in that kind of stuff. Um, I want I want to hear some more thoughts because we've talked about this prior. For those that don't know, Jeff does a energy and whiskey day to night. Um, that or most of last year we've had tons of conversations on, but um I think one [snorts] of the big ones that was really interesting to me just because you know I've always been on the ops side is all the account like y'all had a conversation at one point about what is a unique well identifier? How do you actually come up with that? Because there are so many different ways. And of course, that's just like a really interesting question to me as someone who understands all of that, but has never had to, you know, have the day-to-day hands-on with it. So, I uh I want to pick your brain on that. So, when y'all were setting because you again, you got to set it up from scratch, which is, you know, most people grass is always greener, right? I hate whatever services I'm using or I hate how we use identifiers or whatever. So, I'm curious how y'all went about doing that, you know, because again, I think of it from just like the operations data side of things, but then when you get into accounting, it's a whole another You're thinking of I mean, most people I mean, it's I think of it almost like a catch in the NFL. Like, I know what a catch is when I see it. I mean, like, right, but then like, oh, wait, I guess. That's a great analogy. [snorts] Um, but like [clears throat] I think a lot of people think of it there's a surface hole, but then there's just so much more below the surface. No pun intended. Uh, I could just but I mean I'll let Jeff jump in and talk about how they set it up and kind of even just your thoughts on it now. Yeah, that that's my big I think we even talked about it what about a month or two ago, Jeeoff? Like you you were asking me like how do you guys do it cuz [laughter] it's just fascinating you were gaslighting me. Yeah. Well, there's so many opportunities for ways to do it, right? So, it's I think it's fascinating to ask people especially when they can do it from scratch like what was your mindset going into it? What were you trying to make sure didn't happen? Um, and things like that. Yeah, I mean I think we um again we were involved in the data warehouse build out of Chapperal. So we had we had a pretty good idea of what we wanted to do and I kind of still stick to that same thing is we we use you to me you pick a software. Yeah, we picked Well, you could pick Aries, you could pick uh your accounting ERP, whatever it is and to me that becomes your um unique well identifier. You just have to make sure that you push the wells into that software. And I think Bobby and you and I have talked and I'm pretty anti-API on this. I mean, I think the API is useful for a lot of things and a lot of joins like API 10 especially which you get well API numbers. Yeah. UI API like the API standard or whatever which is not even set by the actual API now I don't think. And Oh, really? Yeah. And then I think I just heard too that like is it the state of Virginia which I didn't know they had oil wells but like they still don't use the API number or something. It's by state isn't it? Yeah because even like I think you know part of the North Dakota will give an API 14 but it's just the four zeros. So then like you're at the mercy of what IHS thinks the API 10 and versus what invar thinks it is and you know so on and so forth. But it's a good like hey this is probably the well identifier. Yeah, the API 10, but we we we did like we picked well view and well view generates an ID well for each well. So whether it's kind of a a potential planning well in Aries, we push that to well view or an extra asset in accounting, we push it to well view and then we just label it in well view as a type is not a well. Right? So then your engineers their view is only a filter to wells but we we use that well header in wellview as our central database and so it's just a relationship there. Yeah it's just a relationship. So then you've got cross references I think they've in well view they call them like well IDA well IDB C D and that's where you kind of cross reference between your systems is you you put in your Aries propnum as one or your inertia bolo ID or your cross land. Yeah. Yeah. So then you you kind of use that as your I don't know your quarterback if you will. Everybody comes there and links back out. But and that's anybody I build a kind of a data warehouse for is um I build the same way is I I push towards hey let's let's pick a system because to me the whoever the kind of person that can see that UI makes it a ton easier than having to rely on someone who knows SQL like hey can we go add this well to this? It's like yeah your your system is Aries right? So go add a well to Aries or go add a well to well view. Um it just gives you a cleaner UI than having to put a help desk ticket in and have the IT guy make it SQL. Yeah. And and yeah, I mean we we roll with Aries kind of as the spine of our kind of you know golden record, you know, but a mainly just because like a well has to be created in Aries, you know, well before it even ever gets an API number or or for us ever gets put into open wells for us, you know. Um, but I guess to your credit, what y'all were saying was as soon as you would create a stick in Aries, it would get created as an inventory type asset in Wellview. Yep. Yeah. Yeah. So, we've got we ended up building kind of um AF workflows in Wellview. We also built uh nonop proposals. So nonop proposal comes in, you generate the well and well view kick it to go and reservoir and they put their approval comments or deny comments and then you've got a a PDF that generates from it to uh whether we elect in or not. So it's kind of the and like you said you could do that in areas. You could do that in any system. You just need to pick in my mind you pick one and then use that unique identifier from the system to be your UWI. Um, you can, and I've seen companies do it where they integrate all of these systems into a separate data table and then they autogenerate UWIS, which you can. To me, it just it you now rely on an IT guy to have to create that and that's the the downside of it. Well, and I think because we were talking too, but I mean we did an MDM implementation at University Lands and it's like then you can you can have that MDM platform create that, but I mean there's a lot of overhead there. And what we ended up finding and I think I've mentioned this before on the podcast is like half time it wasn't actually the software. It was like this by implementing the software it forced you to actually have the conversations you should have just had right you know otherwise because you end up just doing you know 98% of the time you're doing just coales statements that oh no if it comes from you know well view that first if it comes from right you know then use area you know and then you spent you know $200,000 for something that you just if you just would have had the right conversations um you know all that to get a you know unique well identifer a unique line but um I think one thing and I think Jeff's really um you know the right person to talk to about this because you come that come from that accounting background but one thing I didn't understand or appreciate until I got to GME was you know we do a lot of refracts and the thing with like horizontal refrac is they don't necessarily count as another completion in the traditional sense of say even an API 10 or 14 you know I mean I think that those last four digits have been well thought through by different groups at different points um but you know you would have a completion record part of the API 14 well for horizontal Well, like it's not like you're completing another zone. You're just re It's more of really a workover. Yeah. Actually, but but then say for any of these like capital workover type things or a refrac, it creates another payout deck that you have to jib back, you know, or see if people want to consent to to that work. Well, from an accounting side, now I've got the original cost center that we still need to track payout against, but then this, you know, different people could elect to be in on drilling original drilling completions, but then say, "No, I don't want to participate in the refrac." Yeah. So now it's like you actually have two different cost centers that you're bouncing in your accounting system, which are the same well, but they're two different things that need to be allocated. And so then that creates a whole another level of Yeah. confusion. That's a good that's a good point. Jeeoff, can you just briefly touch on like the whole this whole idea just for the people that are like purely data science or technology or whatever that might not understand what it actually looks like operating an oil and gas well um about like how that works as far as you know the AFS and the overrides and your work working interest and all that stuff and with these types of things as far as like just your initial drilling and completion and then oh I've got a workover or you know a refra or things like that like the average person on the technology side has no idea how that works or you know royalty interests and all of that fun stuff. So if you could just like briefly because I'll I'll take 30 minutes to try and explain I was say yeah that's a loaded loaded question but just like quickly right like you've got all these investors essentially and then they get the ability to opt in or opt out. Sure. Right. And then answer questions. Yeah. On that side. Yeah. I mean, that was um [clears throat] kind of the genesis for point flow accounting was I've I've watched people spend $200,000 on an ERP and then they track payouts in Excel. It's just like why why are we doing this kind of stuff? Like I feel like I can do it better. And so we're trying to build and we have we have four or five operators that we're running through our accounting system that we're building ourselves. Um but yeah, it's it's a different animal, man. got I like I graduated with accounting degree and I tried to explain to my friends I'm like the credit card charge that you put driving to a drilling site is not just one entry, right? It gets now allocated to the three wells on this pad and those three wells have 400 owners. So then it gets divided again to those owners. So you've got these one this one cost line item that ends up as three cents to all of these guys who's participated in this. Well, and it becomes I don't know like 800 ledger entries just by by allocating and then billing out. You jib it out whether they pay it back or not or whether you net it. So, um each well has like the interest owners, right? You've got a hey, we're we're a working interest owner. We participated in this well. We gave you capital or we're paying our capital piece. And then it's got the royalty owners who own the minerals and they just have a right to a certain percentage of the profits. So you've got to track in addition to the well, you've got to track all the owners and they're called decks, all the division order decks of these wells. And then you take all the costs, allocate them out. And then on the revenue side, it gets even crazier when you've got allocations coming in. You've got one sales meter that feeds 20 wells, right? So you've got to go allocate that to the owners and then divide it up. But the accounting side gets super super messy. And then you add on kind of what Bobby's talking about. You've got, and this is [snorts] falling back to chaperral again, we had a lot of um vertical wells that weren't even, like you said, you came in and recompleted. These weren't even recompleted. They were just initially completed and the owners, the mineral owners had depth rights, so they owned to a certain depth and [snorts] the next owner owned this depth. So you had to set up essentially you could do it two cost centers where these are this one well is actually two wells or you could figure out an allocation between the two and set it up that way for two different decks. But yeah, I mean that's all of that is what makes the oil and gas industry very very hard to standardize. We've talked about it is like we can't even agree on what is a well and I think I've gone to like four PPDM meetings and every sing it's always that conversation like can we define a well? It's like no you really can't because to every company it's complete like some companies don't have that. They don't have that vertical well that has two different ownerships. So they don't care. They're like well that doesn't that's not a situation we care about. We're going to we're going to we only drill new wells. We're going to trust the API. Like that's fine until you like you said go back into a recmplete. And technically your recomplete you should just be a different deck where you let you track participation because the first deck would then be um inactive until this one pays out. But yeah, both ways doing. But I think even for us, like there's a certain period where there's still stuff rolling in for the other deck, you know, like so from the, you know, there's still costs and stuff rolling in from the previous, you know, cost center, right? So you've got on the activity date, right? Certain date, but then depending on your ERPs, maybe you can't have, you know, the same [laughter] thing active and inactive at the same time. Um, you should have them both active. You should just have like effective date and effective date beginning. But accountants like to they'll deactivate the deck completely so it doesn't get any codes hitting it. Exactly. It's like that's not really how the ERP is built to do. Yeah. But people don't understand even like to your point just like the depth rights, right? Like that's a stateby-state thing. People don't get that. Like on one hand it's great that each state has its own you know independence and can vote on different things but there's not a nationwide governance of a lot of this stuff especially on the data side so hard so much harder right like there's there's both sides of that right like hey if we had a standard but also who made that standard and is controlling it and pushing it forward and stuff but [snorts] it's uh yeah it's so complex like you know oh yeah we have to do all that stuff just on this zone and then the zone below it, it's a completely different working interest and mineral owners and like everything else is it's but it's all coming out the same hole, right? Yeah. [laughter] Yeah. Oh yeah. And then the production is comingled too. So then that gets even more fun. Um so yeah, let's just um let's jump towards point flow now. I mean we've kind of touched a little bit. You've got a little bit what what you do, but let's talk about you know really more what what was the genesis of that. I know you talked a little bit about it and then maybe why the name and then just kind of what what you guys do. Tell us about it. Yeah. And it was it was born out of kind of two main uh drivers in my head was one I was to a point where I was kind of bored at Revolution is I I was just the IT director and we had automated everything. So, I kind of come in and check and um if everything ran successfully the night before, which was I don't know 80% of the time, then I I didn't have a whole lot to do. And I don't like to be bored. I have the kind of a knack to go argue with people or like try to fix or change things. So, um it didn't sit well there. And then the other piece is um Revolution's kind of kind of unique where they've kept their team really small and they've started to use uh outsourcer contractors for a lot of things and I kind of saw some inefficiencies in that realm. I was like man I can I can do that better like the so many especially in accounting is um I'd watch like the marktomarket calculations and they pull pull the price decks in and compare it against hedges and kind of calculate this mark to market. I was like, man, if you pull, you should have an auto feed to the pricing. You should database your trades and then your mark tomarket is a button push, right? I was like, same with acrruels is you're you pull in your whatever field estimate software you're using and write the code to say, okay, here's where they should be. Here's where they're at. Like, let's book this adjustment acral boom button. And I get the accountants like ah that we got took us three days to generate the acrruels. How? Why? Like so born out of like hey I think I can do it better and then also I was a little bored my role and I remember when I told Scott I was leaving he was like are you crazy like you have solid salary you kind of got it made down there and I was like that's not really what I I want to keep I loved the I love the fourperson atmosphere when it was just us four kind of hanging out and and doing stuff we had never done before and challenging ourselves. So that was I was like oh I'll break out and do that. So, uh, the name was just made up. I was just kind of talking to my wife and throwing out names and I was like, "What about point flow?" She's like, "Oh, that sounds good." So, [laughter] no real no real significance behind it. But the idea, my my thought has always been I would love to have five or six or seven companies where I can wake up in the morning and then tackle whatever problem that company is having. Right? So, that's not that's the variety I'm looking for. That's the why I was like, let's do point flow accounting, let's do point flow technologies, which is kind of a low code software spin-off, point flow consulting. And then I've got uh as I've talked to you, Bobby, that Lux pool cleaning. We started a pool cleaning company that's underneath Point Flow. Well, like it was was like 30 some degrees a month or so ago, you texted me and Tal and you're like you got your beanie on like guess I'm my guy's not showing up. Guess I'm going out. Like Yeah. Yeah. I had to go clean some pools that day. It was it was so cold by like the third I was like using the pole and I kind of stretched my hand back out and my middle finger didn't stretch back out and I was like oh god but yeah it was but yeah I mean you own the company we had one guy on vacation went out with co like well we got to strap up and go clean. So yep those are the fun things about entrepreneurship no one talks about it and fun at the same time you know like yeah it's it was a blast that one day I don't want to do it the next day I don't want to do it every day. Yeah. Come back to the computer, do a little bit of accounting, and close it down and flip over and do some data. Yeah. No, I mean, that's that was that's the idea. That's that's honestly why I feel like I like startups so much is because in those early days or in those growth modes, right, there's just so much [ __ ] that needs to be done and there's such a dynamic like there's always something to be done, right? And so, and it could be sales, marketing, data, whatever. But just being able to have that like I'm not sitting and doing the same exact thing every single day for the rest of my life part of it is uh is one of the reasons I love it so much. I mean obviously there's plenty more there but um I'm very curious about your thought. I mean I know your thoughts on on kind of cloud and and things like that but I want to understand I I just want you to tell people about kind of that journey for you because I do think I mean obviously the last decade plus right everybody everybody's pushing cloud cloud cloud cloud cloud you need to move to cloud blah blah blah and obviously there's lots of benefits to the cloud there's also lots of drawbacks right like when Bobby came in this morning I was I literally had a uh a little build your own PC wizard pulled up because I'm sick of trying to figure out which cloud instance we're going to set up our machine learning model on. And I'm like, screw it. We're just we're just going to build a gaming PC and call it a server and it's going to run our machine learning models. Go find a refer one, man. They're cheap. Well, the problem I mean the specs he thinks he needs the specs. Yeah, I was looking at the specs just for like the the Mistral 7B one and it's like 96 gigs of VRAM. It's like, oh well, I'm probably gonna need a server for that if uh Yeah. Yeah, you can definitely buy like a a Z820 or something. I guess they're now like what are they? Z8s reb the Nvidia GPU that he was using. He was like, "Oh, yeah." And Nvidia was nice enough to hook me up with this, you know, uh RTX 6000. And I was like, "Oh, it's like n grand." Yeah, it's a n [laughter] it's on Amazon for $9,000 right now. I was like, "Oh." But I mean we were talking about it and like I think one of the applications like I'll always say that people probably should evaluate if you're run on the cloud is like this whole machine learning deep learning like where there's continually turnurning and the models like take this really re I mean people pay a ton of money on the cloud for that and like and there's some infrastructure for big companies like as far as like Sage Maker and pushing things in and out but like for your it gets so expensive. I mean like you're saying like you could what you were complaining about as far as price you could what you would probably pay per month you know for you know yeah the Google I think it was the Google vertex estimates of what I would have paid per month for a llama model on Google which I still have yet to be able to stand up on Google please fix that take it off or fix it one or the other like I I don't understand the point of your nice gooey wizard AI studio if it you have models on there that literally won't work on your infrastructure Um, but you know, like, yeah, it gave me the estimate it was going to be like 30 grand a year or a month. Not a year, a month. I was like, "Oh, well [ __ ] 10 grand server doesn't sound too bad at all and I can depreciate it and write it off." But, so just kind of tell, you know, tell people about your strategy, your thoughts, like the pros and cons of it. Um, you know, because it's not made for everybody, right? Like it's not going to be something that works for every single person out there. But I do think it is just so overlooked these days. uh especially when you know we're talking about billion-dollar publicly traded companies that probably have a lot of their own infrastructure just historically they've always had it um to just kind of tell us a little bit about the you know the why some of the the really big benefits that you have obviously cost is going to be one of those but then also you know areas where you would see this being like problematic for if you know flipping the script if you were watching somebody talking about this and you were interested in doing it yourself and you had never done it yourself or [snorts] uh if you're on your if you are on a big cloud and you're kind of evaluating that. Yeah. I mean ours was again kind of born out of experience is we when we stood up Revolution we knew we were spoiled at Chaparel and we had awesome computers. So we like we want these same computers. We looked them up and [snorts] same thing they're $10,000 new. We're like well damn we can't afford that. Um found the same computer reurb for like $1,200. Let's try this. So we bought the reverb and it was just as good. So same concept as we started with Azure and I'd spun up a kind of VM and really hadn't done anything and I get a bill for the first month and it's like $300 like that's ridiculous. Like I can buy a server for $1,600. Why would I pay $300 a month for this VM? And so that was the kind of the first taste of it. And funny you say that. Yesterday I got a um email from Azure. So we point flow technologies is another one of the verticals is we build kind of our target is the small to midsize operator and we've got um we got a pumper app that we've built on power apps and we've got a kind of a wellview competitor that we've built on QuickBooks or Quickbase. Y um and we've explored the idea of building it ourselves um coding an independent app. So, we stood up an an Azure VM and um kind of built had a guy help us and built it on there just just a kind of a framework demo. Well, this was six months ago and I turned that VM off in uh November. I just got an alert that was like your December bill was $70 for the storage. It was $70. Yeah, that's what I It was like the static IP and the storage and the It was like you got to be an expert to go in and like configure this thing to when you rip it down that it turns off all the billing, right? And it was like I if if I could turn the camera around, I've got three computers here sitting next to me that are running different things for different clients. And I think the most I spent was 350 on uh this Zbox here, this mini forum. But I bought a $200 refurb that's running my kind of SQL for the accounting and I don't know that that was my my genesis was like the cost and I can do and and I can spin up several VMs on these not just one. So can separate that and so it really was cost. It was it was hey I can kind of do the same thing control locally here for a lot cheaper. Yeah. And when you're setting something up from the ground like you're talking about, right? Like and you also have so much domain and just real life experience with all the things that you know you're going to have to do, right? I know I'm going to have to have Spotfire. I know I'm going have to have Wellview. I know I'm have to have all these things. And it's like, oh well, they offer, you know, oh, you can store it in ArtCloud. And it's like, yeah, they do that to make it easy, but they are going to be charging you for it as well. Well, those ones you're paying a super premium for, too. Yeah. Oh, yeah. Anytime you're buying storage or you're making concessions. I mean, Spotfire Cloud, I mean, I haven't tried it in the last couple years, but it's always been inferior in my experience to Spot. That was a post. You remember that post, Bobby, when they when I found that I could access everybody else's analysis on Spotfire Cloud? No, I don't I don't think I saw that. Oh, I post that LinkedIn cuz like if you went to the public folder, you could see anybody out there who had saved a uh a public thing and I could see like other people's other operators losses. That's insane. Wow. Yes. Spufffire wouldn't respond to me and they finally got like a VP who called me and he's like what are you seeing and I showed him he was like oh man yeah I think they've since corrected it but yeah the cloud versus on prim is is cost and like you said John is control is one of my we we did try like an Azure SQL database and I not first thing I saw was like they don't have SQL agent which to me I live in SQL agent is I can schedule jobs I can use SQL agent to execute PowerShell kind of use it as like my windows uh task scheduler, but I've got it under one hood because I'm opening SQL management studio every day anyway and I can just click my job activity monitor and tell me what's ran and what hasn't. And the Microsoft answer is uh at that time is go use flow. Flow can do all this. It's like well that's now another window I've got to go open and flow can't run a local PowerShell script if I'm say downloading a uh price strip and pushing it to a database. So, I've got to kind of go build those connectors. And it was it was ease, but mainly cost. Like $200 reurb computer that I've had sitting here for three years is 10fold paid off versus what a a VM would have cost. I think that's the other big thing too, just in compute in general, right? Like when you say server, everyone thinks of a rack server and there's so many server there's just towerbased servers out there that look like that, right? Yeah. look like desktop PCs that, you know, everybody used to have and they just sit next to your, you know, on your desk or wherever you want them to be. Computers getting ridiculous. I mean, you were selling cheap, you were selling edge, you know, computers that were basically little servers. I mean, like, I mean, you could probably run half the [ __ ] on nukes. I mean, if you needed to. I mean, like um Yeah, especially if you're just doing database. So, I mean, yeah, things are getting, you know, cheap. I mean, again, you get old laptops, old PC. I mean if you're and again sometimes it's knowledge like Jeff you've set up I think for me is more the security you've set up firewalls and all this stuff and it's not probably rocket science but like some of those things again I can I can spin up a AWS or Azure resource and I can lock it down you know I know how to configure all that stuff I mean I mean there's time how fast you need to spin things up and um you know and there's those different pillars of cloud of you know different service tiers but you know the shared responsibility model where it's what you're doing right now. It's all you have all the responsibility which again if you have the expertise and can do it that's great but like for me generally like unless it's super costre I'd rather focus on the business you know logic um you just focus on that more immediately but um again there's definitely trade-offs with that for sure well because even like you mentioned the security thing right like and I can't tell you how confusing I feel like all AM security management on every cloud platform is out of the gate and it's like I'm not saying it's better or easier. I mean like I mean you're an expert at it point but I think yeah I agree with you like one they're both they both have their own nuances right like but yeah I I do agree that it really boils down to just like how comfortable are you being able to roll your sleeves up and figure this [ __ ] out and if you got time like when you're in your I mean sometimes maybe you did or didn't have time for that you you can tell me how it was at say when you stood up revolution but if you've got some time like all right we're making this acquisition but you know we're building So there's not really actual like operator work to do yet, you know, I mean like there's time to, you know, hey, let's let's get in here and stand up, you know, stand up these services, stand up these machines, you know, you're already operating and then you go acquire a bunch of acorage and then you have to figure out how to integrate all of it, right? [snorts] Yeah. I got I mean I I I I agree with your kind of initial thought. I got a whole lot less worried about or placing importance on security once I realized I can drive out to a well site and open the [laughter] computer out there and it's got the password on the written on the door and I can actually just like get into whatever operator's network just like that and half the time it's just the default admin password right but it's like again we I kind of debate like you said I like to swim upstream so my my MSP brethren are very big on endpoint protection and firewall. And I'm like, you can do that all you want, but Joe in accounting is still going to click on the the free BassPro gift card and he's going to type in his email and password. And now he's been fished. Yep. Well, they got his login credentials, so now they can get your cloud server there. I mean, sure, Microsoft's got a great firewall, but when they have direct access to it, it's no more secure than people [clears throat] are always going to be the weakest link. I mean, I mean, when I was first messing around with the cloud, I mean, I look back now, I'm like, that was not good. Yeah. But I was like, I wanted this to work. So, let's just set it, you know, 0000 on the [laughter] Yeah. IP. Now I can access it. All ports open. Yeah. Public IP. Yeah. No, I mean, [ __ ] Bobby and I got uh Bobby at one point when we were working together got a bill from who was it? AWS we were on for like $1,100 one month and he was like, "What the hell is this?" We were literally still developing the the platform. So, like everything was in staging. There was nothing that should have been remotely close to that being attacked or something like Azer Bjan was mining Bitcoin or something. Our our uh the developer in his test environment had not changed the password. Yeah, the Postgress password I think or and uh got in there and yeah, spun up a bunch of instances on AWS for their highest compute running mining bitcoin. So AWS did refund us. So there was that. But yeah, it was a Well, that's nice of them for your mistake. Yeah. No, it's props to them for that. Yeah. But yeah, we'll I mean, same thing. We we'll watch we'll watch skated devices. You got I don't know. I think Revolution has like six or 700 of them now that are all through uh one of their assets. And every now and then you'll see one modem just go crazy because someone's hacked it or they ping it ping attack it and try to get in and um but yeah it to me that stuff happens far far less than someone clicking on an email and typing in their password and and or to your point have you seen the news new scams where they're even good enough to get your your two-factor off they'll either call you or text you and be like you should have had a code pop up enter that here. Yep. Or I mean, [ __ ] people get get their phones spoofed. I mean, Colin Colin has uh made a very good point internally when we were talking about he's like, you've got a hourly kid working at, you know, the phone store setting up new phones and it's like he could literally spoof your SIM when he sets it up for zero effort and then go steal everything he wanted from you. But yeah, and then there's the flip side. Like it doesn't even have to be that sophisticated. to your point. How many times do you go out in the field and there's, you know, a company field laptop with a sticky note underneath the the lid with the password on it, you know, like that happens so much. So, it is it is a very valid uh argument on the security front because I wholeheartedly agree with you. The most efficient way to get into a company isn't from the outside, it's from fishing and spoofing and trying to get it from the inside of it. Yeah. Yeah. I think you're you're not wrong by I think at the same time two wrongs don't make a right you like I mean like just cuz most people are doing it wrong. I mean like but yeah this could be a whole episode in of itself just cuz like setting up too many walls or firewalls or things people are going to find a way around it like whether they're trying to do something internally and they can't do it they're going to find a a shitty hack I mean or someone trying to get in like they're going to find that weak point eventually if it exists. But um but we're we're kind of running up a little bit on time, but there's two things I would like to Well, we can get into the speed round the last five minutes, but real quick, can you talk about QuickBase and what it's enabled? I mean, John and I actually used QuickBase back in the day at RDS and um I don't know if I've known anyone else using it in our industry till you started using it. Um yeah, but yeah, so Marshall Hall um kind of came to me. So we point flow accounting started doing his accounting at Malor and Energy is a operator that he spun up and we kind of got to know each other and voiced frustration over um some of the lack of innovation and the um well asset software and he was like hey I've got this thing I've been working on and he showed it to me and I was like that's really cool and he's like the awesome thing is it's it's cheap and super customizable. So the problem I've experienced is kind of like we talked about with the UWI and API is every single operator has a little bit different way of doing things and a little bit different fields they want to track. So the thing that I thought was really cool about this and why I jumped in to partner with him was he was like I can change this well card in three minutes to put whatever field you want in it and start tracking this piece of data um because it's low code. Yeah. And I was I was kind of like like in your camp Bobby is again I was like you really want to have and more so [snorts] it's law like you really don't want to do low code as a long-term solution. And the more I got to thinking about it I was like everything kind of is low code if you're pulling in pack pre-built packages that are supported by XYZ libraries. Yeah. Yeah. Eventually they might not be supported anymore. Then you got to go rebuild that and kind of scramble. So, I jumped in with Marshall and what we've done is we've kind of built a well view for the small to midsize operator who can't afford the well view. And we think it does more than Wellview because we've got we've got the daily reporting costs, um, vendor tracking, but we also have, flip all the way over to the other side. You can track your vehicles, your vehicle miles, your spills and incidents, um your pipelines, your compressor, um testing, maintenance, work orders, all that kind of stuff. It's got 101 different tables now that we've built in this thing and it all comes under one hood. You can you can set up your partners to get automatic emails. Um, but yeah, our our goal is is that is is we're trying to build a solution for the small to mid-size operator who potentially a little bit cashstrapped and want to get out of Excel or the guys who can't quite afford the the price tag of the the bigname softwares and even they might be midsize with the thousand wells um and like man we're spending a lot of money on this and all we're doing is tracking uh workovers and daily costs and sending reports. just like okay we can provide that to you for 25% of the cost. So that was the genesis of it. It's been really cool to watch uh grow and we kind of continue to develop it and I think we have seven different customers on it right now. But um yeah it's all built on QuickBase. So QuickBase is a a low code provider um of software and there's a couple different add-ins that we run for like the PDF generation and and email and QuickBase is always innovating which is cool to see. They've got uh now pipeline to Microsoft. So you better since we Yeah. Right towards the end of our time at RDS like they did they get bought or did they got some new they had sold into it owned it then they sold and then they got bought by somebody else or they brought so they've got more funding now and like they revamped the API and all that stuff and it was yeah they started doing quite I mean like offline capabilities. So just for reference, Bobby and I uh when we were working together, that was our internal basically ERP CRM. We built the entire company workflow around it. So everything from our jobs to the maintenance, all of our assets, all of our equipment, all of the mileage, all of the, you know, the daily rentals and all of that stuff all the way through to pushing everything out to, you know, QuickBooks for accounting and stuff. But it uh I personally I also highly recommend QuickBase just because it is one of those where it's it's not so complicated that you need a whole another you know six months of training on how to do it but it's so flexible when you think of the fact that like to me most of the internet most apps most things on the internet are literally just relational databases pointing to each other in APIs right like you've got relationships between data and then it's just how you end up displaying that on a screen. And so the way that QuickBooks does it or uh QuickBase is it's essentially you just set up tables for those processes that you want and those different things that you're doing and then you can relate them all to each other and there's all these additional plugins. They've got the API. They've got they're constantly developing on it. But it just allows people to, to your point, it's like everybody has the same general workflow, but then you've got all these nuances for this one thing or this other thing. And it's like, well, if the software isn't customuilt for that, then you're going to have to get it customuilt or find something else. It's like, well, or you can just do it yourself. That was the beauty of it. um on our end cuz it you know it's like I I mean I'm not again a developer but I was one of our admins on it at at RDS and I you know we needed something I could very easily add a new field spin something up add a relationship add a new table like whatever it needed to be I could literally go do it in minutes um and I think there's a lot to be said about that that people don't really appreciate about the low code stuff is it's like it gives theme the ability to go build or fix or solve their problem without having to get it involved most of the time. And [snorts] so that that's a really powerful thing in a lot of cases. Yep. And that's what our customers love is they're like, "Hey, we um I don't know example, but we want to track this certain data point or we want to allocate cost this different way." And Marshall and I will knock it out in like 20 minutes and you'll be back like, "Okay, that's done." Wow, this that was fast. And right, you don't have to go refactor the entire codebase. You don't have to do like it's a very very straightforward piece of time, [clears throat] right? And with the API, you could pull data out, right? Manipulate it, push it back in if you wanted to. Yeah. And pull data in via APIs, too. I mean, that was one of the the big things that we did finally was we tied our our well list for all the jobs that we did back to a public data source. We were using Energent Group at the time. It just got bought again. Did you see that? Yeah, I saw that. I I actually need to ask Todd about that. Um, [snorts] but they uh, you know, and then because our field guys would get the well name and it would just be whatever the hell the company man told them the well name was, not what the public well name was or full circle the API number, right? Yeah. Because we didn't have API numbers like in there, right? When I got there, I was like, "Oh, you guys aren't using API number, you know, you know, or something to identify the well." We couldn't even get the API number because we couldn't get the full damn well name from, you know, the actual well name. It's like, oh yeah, it's a UL 24 and I think it's in Lee County, New Mexico. It might be an have a number sign a space dash. Yeah, exactly. And so like I was able to get it. So they put in the state and county and then that autofiltered the well list and then as they typed it dropped down recommendations and they clicked on it and then it pulled in all the well header information automatically and it completely changed data. Yeah. Yeah. I really wanted it mainly for the latl longs and just so we had a normalized naming convention for all. There was even stuff I don't know if it ever got there but we were talking about trying to do like some geo fencing around it. So like when they came with the geotab and they got within you we could almost calculate how much time we were on location and all that kind of stuff. Yeah. Cuz we also had trackers on all the company vehicles so we knew where all the vehicles were. Like being able to tile all that data together [clears throat] is so valuable and a lot of people don't like low code tools like that really help accelerate a lot of that stuff. But we've got four minutes left. So we've got to jump into the the speed round. I need I need like a button drop. I'm going to see if this will There we go. [laughter]

Hopefully it's not 30 seconds long. There we go. Thanks, Bobby. [laughter] Learning on the fly here. Yeah. Yeah. I actually I scared the [ __ ] out of myself the other day because I accidentally hit one when before we were recording and I was like, where did that come from? I had no idea. They were all programmed. Um, speed routes. So, just short quick answers. Um, what are some books that you either recently liked and and recommend or just generally speaking like and recommend? Oh man, they're going to get deep into my mind here. Um, Overton Window is a good one. Um, Rich Dad Poor Dad. Yeah. And then, uh, the micro books are the three that I read most recently. Yeah. I didn't realize uh until after I read it that Rich Dad, Poor Dad, he went to the Merch Marine Academy. Oh, I didn't know. Yeah. But um Well, you better hurry up, Bobby. Catch up with him. [laughter]

Um, all right. I think I know the answer to this one, but I'm interested to see you say, who's your favorite uh social media follow?

Um, probably a tie between Elon and DHH. Okay. DHH is who I was thinking. So, yeah. I didn't I I think you were the one that even like kind of triggered me on to him, but he he's pretty uh pretty anti- cloud and big on prim guy and for the same reason I brought up his cost. I think people just ignore cost and in the name of convenience and um he he's kind of calling that out so I like it. Yeah. No, and they've been fighting the fight against a lot of people. I mean I think you probably identify because he's you on a much bigger scale like he's taking on Apple. Yeah. Well, I mean I mean you know success is relative, but like I mean you're doing pretty great, but I mean I mean he's taking on Apple like because they wouldn't put his calendar stuff on the you know app store. I mean like he's he's not afraid to you know ruffle feathers. Yeah, that was a fun that's probably what I like about Elon too is he's got great technology and kind of same just say says it's on his mind. Yeah. No, that was a fun Twitter back and forth to watch this this past week. Um last one then we'll wrap it up. What is your I know the answer about your favorite database is going to be SQL. Um favorite cloud service. No. Yeah. No. Answer that question. Postgress. Answer that question. Favorite cloud. I'm going to make you answer that question. I mean I'm a Microsoft guy. Perfect. Yeah. [snorts] Where can uh where can people find you? Where can people find Point Flow? How do they get in touch? Uh pointflow.co is the website. And again, one of those why did you why did you do pointlow.co? It gets caught in spam filters and people mistype it all the time and I don't know. I just picked [laughter] I thought it was I thought it was techy and edgy and it's it's kind of uh cost me a few things. But yeah, pointflow.co um or LinkedIn just search for Jeff Hughes or kind of whatever those jeff pointlow.co is my email. I know. I should should have asked you who your favorite bank is and why is it Chase? [laughter] Oh man, we don't have enough time for that conversation. We'll follow [snorts] up on that with the next episode. I have I have gotten through Oh, man. Uh, two of my four stacks coding these in bank. They picked the wrong accountant to do that, too. [laughter] Had they known you were an accountant and also knew how to code, they would have been like, "Maybe we just figured this out for him." Unbelievable. Awesome. Thanks, man. I appreciate it, Jeff. Um, yeah. Thanks for having me on, guys. Yeah, man. Absolutely.