Welcome back everybody. We are here for another exhilarating episode of uh Energy Bites here with my good good buddy and co-host Bobby Nean. How you doing Bobby? Doing great. How are you? I'm doing great. Rad dad is is rad as always. And today we're here with uh Ronnie Giles from from uh Bit Out CEO and co-founder. Appreciate you uh joining us today. Yeah. Hey, thanks for coming on guys. So, it's great to uh it's great to be on the show. Yeah. I I uh I don't know. I don't know if it's because I've done so many RFPs and RFQS and all of that stuff in my past that I appreciate the [ __ ] out of [laughter] what you guys are doing and it gets me excited. But, um let's just kind of jump into it. you know, starting briefly. We you've been on some of the podcasts and stuff before, so I don't want to get too deep into, you know, your full history, but kind of walk us through, you know, how did you get into you've got an interesting story as far as like just randomly how you got into tech and stuff, but when did you really start getting into the, you know, kind of tech side of things just in general, whether it's energy or not? tech probably going back I was 13 14 years old just fascination with computers and the internet in the mid 90s and uh but really more so trying to solve the current um problems that we're trying to solve with Bitout uh probably about three years now um I had a co-founder of Bitout was great business partner went to high school with really went to junior high with him as well um he really reconnected with me had an ideal was running some oil field service companies on the sales and op side and kind of explained to me the challenge all that was going on. I was just in the process of exiting my second uh cloud venture at that time and um wanted to build a pure SAS business. Wanted to build a very niche business most likely oil and gas. I've got some previous um time spent in oil and gas uh back in maybe 10 years ago and uh so know a little bit about it. Family's been around it. Um and uh so when Tyler came kind of with the idea, we we jumped into it. really started trying to figure out what the problems were. Met early on with some majors um that explained that, you know, they they went out and did this this bid. Um all the suppliers sent different formats of bid responses, different unit of measurements, different you know, contract terms, everything. And there was no uniformity for them to truly compare these six or seven suppliers. Yeah. Um, she even explained to me that one of the one of the suppliers um took a screenshot of Excel, printed the screenshot out, filled it in with like a pen, took a picture of the of the screenshot and texted it to them and said, "This is our bid submission." And that was actually the one he did for like a multi-million dollar water hauling job. Like the least surprising thing. That's the most oil seal thing I've ever heard. And it's not surprising at all. It's not surprising. So it's uh for us we wanted to build a we wanted to build it so simple that the suppliers loved it and we didn't want to build this complex tool that you know some someone like SAP or Oracle would be involved with. We wanted to make it simple and that's what we've done and actually making it simple is actually a lot harder than it [laughter] sounds um because it still has to be comprehensive enough to use you know to have the majors use it and so forth. So um that's what we've done and um we do it really well. We we try to stay in that in the lanes of procurement and focus on other procurement challenges for our customers and we've since kind of evolved the product into more than just bidding. Um but uh that's what we're focused on all day is procurement. you say uh you know you're 13 14 whatever you want to dive into that like kind of what that look because we you know we'd like to kind of get get your evolution as a technologist even like well and that's I mean that's like the heyday of tech to me right is the late 90 the mid mid to late 90s early 2000s when it was just like the wild west and every like AOL and Netscape and chat rooms and Napster like it was oh I I remember it heavily um it's uh you know it's my father He um he worked for probably mid his career for uh some smaller operators and then went out and um he was probably about 40 at the time. I was probably seven, eight, started his own small business and a small operator and uh ended up growing it pretty well to you know probably thousand wells or so and sold it off to um a group. But so I was always fascinated with small businesses. I was fascinated with being being an entrepreneur being a um being the head of a org. And so that really had started the fascination early on. 13, 14 years old, I started mowing the lawns to make money. Um, I learned very quickly instead of me mowing the lawns, I could charge somebody like 25 bucks, I could pay somebody 10, 15 to go do it and I could keep the rest and just kind of go be the sales guy. So started growing very very early on that way. Probably 13, 14 years old. I remember I had a few hundred bucks saved up. I went to Comp USA back in the day and uh I was looking at some sort of video game. I don't remember which one it was, but I bought QuickBooks instead. And uh [laughter] I was so fascinated with like making invoices and like it was so cool. And uh so eventually kind of back in the days there started um um CDROM probably. I was going to say was it on a true floppy? It was CDROM, but I do remember having I do remember having floppies, but I remember having zip drives. Remember those? 100 megs. So bad because it had so much more storage. Yeah, we had to have them. I took a computer science class in high school and they gave us zip drives to store everything on but I didn't have a zip drive at my house so I couldn't do anything with it. [laughter] But um the uh started hosting websites. So I started making websites for people um but realized if I could host them I could get the recurring business and um that business started growing and by the time I graduated high school I probably had um you know half a dozen employees maybe a dozen employees working for me and um we grew that business over the next 10 years. What time frame are we talking here? Um, so started the business in 2003. Um, I was a senior in high school. I skipped school to go meet with a lawyer to incorporate. Didn't tell my parents. Um, it was a kind of cool story. And, uh, grew the business over the next 10 years to 150 employees, 150,000 websites. We had offices all over the world. Um, sold that business to a investment firm out of California. And um since after that point um kind of backing up a little bit um when I got started there I was I was programming all night long uh PHP my SQL um used to lampstack I guess lampstack absolutely and uh would do all that myself. Uh you know loved to program and eventually I grew into kind of more just managing the business but remained very very technical along the way. um you know was managing you know even when I sold the business I was still managing you know hundreds of servers um at any time that I was you know logging into daily or things like that. I was very involved on the technical side of the business. Did y'all own the servers? Correct. Yeah, we we owned all of our own servers. Um we uh so when you say like because you you know you said a couple times you owned cloud businesses like you were literally I mean in the sense of like hosting your own servers as a service for people. I mean that was kind of really ahead of it time. We would we would lease data center space. Uh we had data centers in Dallas, we had data centers in Singapore, we had data centers in London. Um and we owned all the servers there. We would, you know, it was a nightmare to ship stuff to Singapore. Um figure out all those things. Um so did that and uh sold the business. Um and actually went in and bought a bunch of oil and gas production. Uh bought some working intros, bought some operated wells up in East Texas. And uh um the uh thought I would kind of do that for a little while. played a bunch of golf and uh realized uh I'm a lot better at the tech side than I am at oil and gas. Um for me it was just there was nothing to do. It was just kind of a waiting game. Yeah. Once you deploy the capital, you know, it was multiple years until you would see a great return or commodity price would have to shift heavily. You'd have to get a big swing to really Exactly. So um the uh at that point I had an opportunity to uh really build a data center here in Houston. uh partnered with some folks um invested a little bit of money and they had a lot more of the experience on the physical data center side than I did, but also took over a existing cloud business out of Atlanta, grew that to New Jersey and San Francisco and Dallas and ultimately Houston and uh exited that about five six years later um to start bid out. So um and then uh you know really uh you know very involved from the technical side along the way and uh really led the product and architecture side from bid out from the start um you know I don't we've we we made the decision to hire developers from day one you know I probably have written 5 10% of the code on bid out but um you know still very involved from an architecture perspective from a data structure perspective but um you I'm not doing all the day-to-day heavy lifting so so like what are some you you know, because we kind of want to share what people are doing and like what's working and so I mean what were some architectural kind of decisions that you made early on so that you could scale it and like what were some things that you evaluated and you know I think we looking back we would have done things a lot different than probably where we've ended up we had a little bit of technical debt over the last year or two we had to work ourselves out of um for us it was a let's try to build this as cheap as possible until we can get our first client and it took a while to get our first clients So, um, you know, there was a number of things that, you know, I think Tyler and I, my co-founder, we we kind of guessed this is how the customers would like it. We didn't truly know. Um, our our initial pilot client that we kind of started working with, right about the time that we had the minimal viable product done, they put their assets for sale and basically told us like, "Hey, we can't work with you guys. We're going to sell everything." And uh so we were kind of scrambling to go back and figure out well crap who can we work with and will like kind of believe in us early on enough to try us out. Um and so there was a lot of changes but um you know uh going back to your question I think um I think you just got to go. Yeah. I mean you can you can plan and plan and plan forever but if you don't ever get anything done Sure. Um I think that's the thing that holds people back the most when [clears throat] it but like was there a cloud versus onrem you know kind of it was always cloud. So that's that's part of the reason why why I decided to exit and leave my my previous cloud company is we were building like hybrid enterprise clouds in our own data centers um based on VMware buying our own servers buying our own storage and although we were selling it and my goal was to evangelize that that was the way to do it I knew deep down inside that going all native cloud was really the right way to do it. Sure. So we went native cloud on day one and um you know we we built everything from a serverless environment. We didn't want to be dealing with you know operating systems and you know patches and upgrades and all that. So you know we've got a full CI/CD environment um set up um you know we can deploy code you know press of a few buttons back up and explain CI/CD for people who don't know what CI/CD is. Well, it really just allows you to do just like continuous development and uh you know continuous deployment of features and uh makes the process incredibly easy and testing of the code, right? The CI part is well it's yeah continuous integration, continuous deployment, right? I mean, you know, you can test your code before it gets deployed to certain environments and um yeah, I mean, at scale, right? And it's really focused around kind of the agile development [snorts] style generally speaking, right? Is you're constantly moving and pivoting and stuff and so being able to just click a button and theoretically at least and you've been on both sides of I mean like there's that that's part of like DevOps, you're right because traditionally it was like you had developers and then operations had to deploy the code for them. But now with these tools like to your point like you know you don't necessarily need the IT ops on the other side. No, that's right. I mean we um once you get it set up right, I mean it really developers just take over at that point and uh so I do a lot of the DevOps stuff and I've got everything really set up from the security perspective there. Um and it's better to keep the developers hands out of that. Yeah. But um the uh you know makes it makes your life so much easier. You know, you're not ever dealing with like crap, why isn't VMware working? Why isn't IU working? It's just just works. Yeah. Sweet. So um and you know, if you're willing to is that on AWS, Azure, Google? We use both AWS and GCP. Okay. And uh we kind of have like front end on one, we fail over to the other, back end on another, fail over to the other. So we actually kind of utilize both for good reasons for each. Sure. Hybrid cloud. Well, [laughter] are like a crosscloud I call it. So, um the uh you know, I do think that's a big risk that people have with going all in on cloud is they talk about security and all this stuff and it's like well if your if your if your login gets compromised I mean what good is having all your backups in one spot and things like that. Yeah, I mean like just because it's in your closet doesn't mean it's any more secure than I mean and again like you know because what people don't realize too there's like security of the cloud which is you know AWS or GCP's responsibility but then like it's your responsibility in the cloud you know right you need to set up the proper firewall rules and you know security and everything like that. You know, and that's the thing too that um you know, I was involved in a lot of these data centers and we would have clients come in, you know, hospitals and some of the large cloud companies too that would they would want like the bolts on their cage like welded shut where nobody could like unscrew the bolts like very high level security stuff. But, you know, I also would guess that a lot of these data centers in town and so forth, if I just go get like an AT&T shirt on eBay and show, they'll let you ride in. And uh so it's uh I think a lot of the security on some of these things is just a big dog and pony show. So I want to I want to dive into we get pegged a lot on security for bit out and it's like I have to tell our clients sometimes like especially when dealing with our IT departments like the whole goal of using us is to send your data out, right? So um like yes security is a big thing for us. We take it very seriously but we also are sending it to everybody. [laughter] Yeah, literally a request for a proposal that you're sending to all of your vendors. It's got to leave the [laughter] that's I want to I want to unpack like the architecture side because I feel like you know a lot of our guests so far have primarily been on the the dev side but you know the back you can't run a software if you don't have hardware to to run it on. So I'm very curious like what is what is what is that like coming from you know your prior uh company where that's all you were focused on to now you're focused basically on the software and you know how involved are you on the the hardware side? All of my previous cloud companies we we had a very heavy software development focus internally mostly to improve our internal operations to automate our a lot of our internal workflows. So my first company I built um most things we did were automated. So our employee count compared to revenue of peers was a lot higher. Yeah. Um or really was a lot lower on employee count but um it was mostly because we we had a lot of automated. Now the problem is when we sold those companies we weren't valued for the software. We were still valued at like a multiple VBA or things like that. So um nobody ever appreciated the software that we built in the past. And uh so [snorts] that's why I really wanted to jump in and do like a pure play SAS business. I've had a lot of the extensive experience in building that [clears throat] in the past and building the product, but a lot of times the product was only used by a handful of people for good purposes. So, so what were you all what kind of stuff were you developing internally for those those things? Is it Well, we were doing um automated provisioning of servers where we would like pixie boot a server. We would reboot a server and it would you know the the MAC address would get deployed to a configuration file and load an operating system remotely without everybody touching it and so forth. And so a lot of things before a lot of softwares that were doing that, you know, 15 years ago, we were doing that kind of manually and built those processes ourselves and kind of engineered the whole thing. Um, so you know, we uh I've been able to do, you know, a lot of things like that almost like your own CI/CD pipeline, but just for your infrastructure to an extent. Yeah. Or Yeah. Well, I guess infrastructure is code in a way. Yeah. Yeah. Absolutely. So, but you've got to be a good person to talk about containers and virtual machines and Kubernetes have to. Yeah. So, I know a lot about virtual machines. I know a lot about VMware. I know a lot about um I'm not that wellversed Kubernetes and really never gotten to it. I mean, it's still very new. Yeah. Yeah. Buzzwordy, but I mean I I guess he wouldn't necessarily need to because when you're utilizing the serverless stuff, I mean like true AWS or GCP is handling that under the hood for you. There's that whole shader responsibility model. I mean, yeah, you can go all the way down and I just need an EC2 instance or there's all those kind of intermediate steps where an RDS instance somewhat, but I mean when you're going pretty much the full serverless with lambdas and all that kind of stuff like they're hosting. I mean, there probably are containerizing your code and putting it absolutely scaling it. But again, that's the beautiful thing. you don't have to worry about any of that or have people on it makes it so much nicer to not have to worry about like in the past you knowve I've upgraded my SQL I've upgraded Postgress the actual database server you know hundreds of times but I haven't done any of that in the last three or four years because I don't need to and the fact that you don't have to worry about any of that has saved us immense amount of time and sleep not only us but from our developers would a lot of times be bottlenecked waiting on something and things like that and now we just shut things down to patch it or you know like no it's a beautiful It's I think it really allows us to move probably twice as fast as dealing with the actual infrastructure layer. So So like what um what language are you using then? Like I mean obviously there's a handful you can probably use with serverless but I mean probably JavaScript.NET. Yeah. So so everything we do is kind of on a front and back end um architecture. So our backend's all noode.js. Um we we have some um cloud functions in Python for various reasons. Um but uh and then we use MongoDB as our as our database. Um we were originally using a platform called Firebase DB and that was our that's on GCP, right? Yes. Yeah, it was on GCP and allowed us to move really fast on the get-go, but it had a lot of limitations with like searching database fields and doing like multi joins and um a lot of issues that we had to work our way out of. Switching to databases was super complex and um the because they're both those are both no SQL, right? their own like they're unstructured and yeah so it actually the actual migration was not hard um kind of what happened for us is we had to spend we probably spent two or three months of having a single senior backend developer focused on the data structure okay and going through like the initial migration and then once we kind of had things figured out we had to throw a whole dev team on it like 10 guys and basically just say nobody can do any other feature except getting this across the finish because we've got to end toend test every single thing out there. We wanted to keep all the endpoints the same, but um we couldn't for some things because like [ __ ] would use like underscore ID, right? Where Firebase was like ID. So there was a lot of things that had to be changed and we had to go and test a million times. And uh for us our our software is so time critical like if we can't submit a bid and the bid's ending in 45 minutes, [laughter] that doesn't give them enough time to fix it. Like the bid will fail. So, um, we've got to make sure things absolutely work. And, uh, you know, we we did the migration around July 1st and zero issues and, uh, so I was very happy with our team margaritas after that one. It was a, it was a, it was a good thing. It was a good thing. So, um, you know, very nervous going into that, but, um, I mean, we spent by the time we finished our final kind of development side of it when we probably tested it for eight weeks solid with, you know, almost 10 guys testing day in and day out. So um it really went off well and since then it's allowed us to just take off from a feature development perspective because everything's been kind of on pause for quite a while before that. So um and then on the front end side we use Vue umJS and um you know we um you know that was an early decision that was made by one of our initial developers. Um [clears throat] I didn't put any thought into that. I knew I wanted to use [ __ ] Sorry I knew I wanted to use node on the back end. I was doing some of the backend development, some of the initial data structure. Um, probably, you know, I could have gone with React. Um, probably would be easier to hire more developers. That's the thing. But I mean, like I think Vue has a better developer experience like, you know, using it, but like there's so many people using React. Correct. Like Yeah. From like from your side, like when you want to hire, you can find a lot more. I think we get probably about a 40% smaller pool by by using Vue. But I'm very happy with it. There's no reason that I would want to move away. Yeah. And um so we um we just developed a um kind of a sidebar app that um that we did use react on and some of our de developers know it and they all actually came back and said we wish we had used Vue on. So um that's the uh but these are all like Vue guys as well. So for sure. But I mean I that's generally what I've heard because even when I was doing my web development boot camp like React was a big thing is a big thing but like anyone who touched or did a little project with Vue was like man this is so much easier to use but it's just that you know that momentum gets behind certain things and it's like yeah there's so many more people you know again when you need to onboard someone you know maybe easier to find those people and cheap cheaper because there's more supply of them. But no, that's that's a big I I feel like that's kind of an overlooked thing in software development when you're, you know, architecting or whatever. It's like, oh, let's go use this thing because it's new or shiny or whatever or it fits the bill, but then also make sure you go through and take the steps to look at, you know, talent pools of those, right? Like my at hivesell, you know, our whole thing was you can run Kubernetes at the edge. there's only like 50 Kubernetes experts in the world or whatever it was at that time and they're all making you know quarter of a million dollars plus at least and it's like well [ __ ] that limits your development quite a bit especially if you're selling to customers on the fact that they're going to be able to run it in Kubernetes and none of them have run anything in Kubernetes before right make sure that you look at [laughter] you know if you're going to be choosing a software looking at hey can I find developers that are actually affordable for that and also you know depending on what your hiring pool Is it you know are you willing to hire outside of you know because in Houston I'm sure you're if you want to hire exclusively in people like local then your Vue.js JS or even ReactJS, you know, like pool is very small. Whereas like if you went more like .NET, you know, or something like that, you know, there's a lot bigger um pool of people, you know, you know, for those. But um but I think another thing to highlight there too is like in the end your clients don't give a [ __ ] whether you use React or Vue or Vanilla.js. They just want to work, you know? So I mean like I think as long as you're able to provide that good user experience, I mean most of them couldn't care less what you're using on the front end. Yeah. Yeah. No, I think you're right. So it's uh absolutely. But what about I'm curious also to to pick your brain on I'm a software startup. I'm looking at figuring out how I architect this. How what is like your what would your approach be? And now having kind of both sides of the coin, both the backend and the the software side or the SAS enterprise facing side. What would your kind of advice be to people around evaluating, you know, do I want to like we've had people we've have had people on the show already that just they everything they do is ex executable there's no cloud or very limited cloud to everything's in the cloud. we don't you know it it's all managed by somebody else to the Jeff Huses of the world who have their own servers and they maintain and manage their own all the way to you know the collocation type stuff that it seems like a lot of the big companies are starting to move to because the cloud is also very expensive as you scale up and out right sure so I I think for us
it it's it's really what you want to focus on so um for me, we've got to focus on sales and um sales cycle in the oil and gas space is very long. So for us, it's uh you know, we had to keep our cost low. For us, we don't have um you know, billions of records in our database. We don't have um you know, we're we're growing rapidly fast. We've got several of the top 10 majors using our platform every day. Um however um you know even five years from now I can't envision a a server bill being hundreds of thousands a month uh you know on the cloud. Yeah. So I don't think it would make sense for us to kind of repatriate that back into a data center to try to save a little bit of cost. For us it's all about time savings right. Um if I want to deploy you know we've got everything microsered and you know redundant across multiple regions. um you know failing over from AWS to GCP you know it's designed very well from an architecture perspective but if I were to try to replicate the same thing buying my own servers in a data center I we would talk several hundred,000 of of equipment um you know and you know obviously probably a much larger bill then you've got to figure in time to go deal with all that crap um it's the time is the biggest part so for us um it doesn't make sense um the uh [clears throat] I I don't know why starting out you would want to do anything but the cloud. Um I think once you get to some scale and have some consistent use cases, it might make sense at that point to take some of those consistent use cases. Uh but I don't know what's going to happen in two years from now. I don't I don't know what's going to happen next month. So yeah. Um the uh um you know for us I think one thing I've seen a lot of startups fail is that they'll they'll come in with a great idea. I want to build XYZ for the for their whole business. I don't know anything about technology. So, we're going to go find a dev shop somewhere and we're going to pay them a couple hundred thousand bucks and we're going to touch base with them once a month for the next six 12 months and hopefully at that point we're going to go live and launch. And what happens is the it's the drift of the product starts to shift where the founder doesn't really know what's going on and they get to the point of finishing it and it's nowhere right it was that they wanted close to what their initial vision was. Yeah. And then they they'll scrap it and start over. Yeah. So, I think it's really important to be um to follow the process along the way, to be involved. Um I think it's important to have a pilot kind of beta client that will work with you along the way and will be forgiving um and uh kind of test the product out and uh um I think that's super important. So, but that's one of my favorite books is uh Crossing the Chasm. And you know, I don't know if you you've ever read it or not, but it it basically walks you through kind of the whole idea of it is this is how you introduce technology products into the market and this is what the market is comprised of, right? And it's this bell curve and it's like the very front of that bell curve is like the tinkerers and just the the nerds like ourselves that like to mess with stuff, right? Like it doesn't matter if it works great or if it works bad. like it's this new innovative thing and it's exciting to you because it's new and innovative even if it is kind of you know has bugs and some things. And then you've got the visionary which is that second part of the leg which is the kind of the the individual or group of individuals that can generally understand the technology but then they see how they can use that technology in the business in whatever form or fashion that may be how it can help optimize improve cost whatever it may be. And then there's the chasm which that's what where most startups fail which is from that point to get into the 67% of the market the main majority of the market is a big jump right and so the whole book talks about all that and it's a it's a great read if uh for anybody that hasn't read it but it really helps just validate like all the [ __ ] that you go through when you're building software and deploying software and all of this stuff. Um but yeah I completely agree with you. I don't think enough people find those early tinkerers, early adopters that, you know, are okay with, well, hey, this thing looks weird or it's not as sexy as it could be or there's this bug that they're the ones that report the bugs and those are the people that you want using your stuff out of the gate because that's how you get that feedback loop going and you continuously improve it. And ultimately, that's kind of the whole idea of the book is you have enough of those and you build out a full feature product that that mass majority actually would be willing to go and pay for now at that point. Right. Yeah. No, I think it's important and I I think because that's got to be cloud-based. Um it's I'm a huge proponent of it. I don't know I don't know what what really good pieces of software out there are not right now. Um the it's tough for me to think of anything that uh would be great without being fully cloud-based. So and hand varying demand of you know clients and absolutely I mean I think doing things inside of a browser is incredibly powerful and uh so um the uh you know the browser is getting insane what you can do it's getting more and more powerful by the day. Absolutely. So I think by by doing it that way you can keep your cost low um you can build a powerful tool. you can um don't have to worry about supporting multiple you know operating systems and so forth and um you know makes it really easy. So but so me coming from the data analytics side um what kind of requests are you guys getting from say operators to to do data analytics and are y'all looking at you know employing that you know within the app or are you how are you or are you supporting like you know do they have API access or how are you looking at like data sharing and all that? Yeah. So we do have some we do have some data um integration done with existing clients through really private APIs that were built specifically for them. We are in the process of rolling out a full feature filled you know documented API that's going to be available to everybody for really everything across the board. Um it allows you to you know create your own data lake of all the data and so forth. Um, we're putting a lot of efforts into trying to figure out how we can use, you know, AI and chat GPT and so forth to really automate a lot of these processes, ingest data. Um, you know, early on we didn't have enough data to really do it all right and uh, you know, really try to figure out a nice data set. We didn't have a lot of data to build to [clears throat] build reports. Yeah. Um, so a lot of that's kind of forthcoming. A lot of that our team's really working on right now. And um so um you know we we've got like two types of operators that use us. We've got some that do so many bids. I mean they're building you know so many every day that I don't think they really care about the data side of things. And then we've got some that do you know very fine-tuned bids and they are really analyzing the data. They're spending time to analyze it and understand it and look at you know previous bids and so forth. And um you know, shockingly enough, you've got some on each side that are almost the same size, some operators. Yeah. So um I don't know why some operate one way or another, but um Yeah. Yeah. And I just think I mean even within it if you're able to come up with some you know good models but I guess it it's got to be you got to be careful with what data you can even like technically even kind of share between but like if you're able to like identify like you know is this I guess you could say relative to historical bids from them like this is outside of couple standard deviations contractually we're allowed to anonymize um data. going to say it seems like it would be like a bad choice from an operator to say no don't aggregate all the frack bids that you get in a basin and give me a report that shows that we're paying more than what the average is right like that's that would be a value ad in my opinion although I also could see people can reverse engineer some of that too if they know like clients are always we use we use workable to um do all of our hiring it's like an application tracking system it's really great but they've now got kind of a oneb button wizard to build the job description And um when you type in like the title, you'll type in like inside sales rep, it'll go I guess it goes to your website, it goes to other sources and builds like a full like you know four or five paragraph job description and it takes stuff from our website. And so we're we're looking at how can we do that on certain bids and uh you know kind of automatically build some of that based on historical bids and based on how people are doing things. Um and uh you know hopefully make that process a lot easier. But no, I mean that's uh when the first rack company I worked for in the office once I got out of the field, that was one of the things that I was responsible for doing is maintaining our internal. It was a spreadsheet, but every time we sent out a frack bid, I would put in the basin, the operator, the sand, chemical volumes, fluid volume, like all that stuff, right? And just tracking that in a spreadsheet. Did we win it or did we lose it? And you can actually come up with a pretty damn good understanding of where market prices are or stage prices are in each basin just by looking at that stuff. So I think sure as long as the uh the operators can get over themselves and in a little bit of sense as far as being able to share or let you aggregate that as a whole I think there's a huge amount of value there. I'm very curious. This is just a personal pain point for me in the supply chain uh process is has there has there been any like requests around um like not only just the RFP and stuff but then past the RFP because this is where it gets frustrating from the services side is you know a lot of the RFP process is very like impersonal right and you've got all these sales guys that have relationships with the engineers but then the supply chain person gets wedged in between them during any kind of RFP and everything has to go through them. But most of the time those people may or may not know anything about what a frack job is or the chemicals or all that stuff. And then so of course their job is to optimize for cost in most cases. And so okay, yeah, great. We got the best cost, but then the service on the actual job for the next year or six months or whatever sucks. And so it's like that's one of the frustrating things about supply chain in general to me is that there's It's hard to like weight the value of like the service, the actual service piece with the cost piece that's associated with it because it seems like once the RFPs and stuff get done, the supply chain person moves on to the next thing that they have to bid out. They're not responsible for the [clears throat] actual performance of the vendor. When you take things like like true commodities like pipe and things out of the bidding equation, when you go to actual services, we see that like 60% of the services are not awarded to the lowest cost really. And uh and a lot of that's because they're taking into consideration past performance and reputation and um so forth. And so I think it's really important. But what it also does is it also by going through a real formalized supply chain process um we see that typical operators saving 18% across the board. we can back those numbers up with real data. And um because what happens is when you're not consistently bidding these things out, the incumbent bidder knows they can start to creep a little bit. They can start to raise the prices up and next thing you know, you're paying substantially more. So, um we and we had a midstream company come to us with a certain product and said that, you know, there's no way you're going to save us money. We've got the best price out here. You know, it's it's not even worth doing it. And his boss said, let's go ahead and try to bid it out. So, um, we saved him $180,000 on his first purchase. They were buying these things every single month. Yeah. And for the last, you know, 18 months, they've almost been spending $180,000 more. And, um, you know, it just it the all the suppliers know when they're bidding against other people when they have the job. Um, probably our most uh requested feature right now from several of our clients is they want engineers to not be able to see the pricing because what happens is suppliers call the engineers and say, "Hey, I'm about to submit the pricing. Where we at here? Where do I need to be?" I've had that conversation many times. you know, it's really it's really just being good fiduciary um you know, with the capital that the companies have employed you with um and really using that in the best way possible, running a fair process on it. And um I think just by doing that and you know, we we allow it to be so simplified where you can do a formalized bid in 60 seconds. Yeah. Um you can tell your investor base that, you know, we're being prudent with the capital. It helps on the the ESG side on the government side to show that you're actually um have controls in place, right? Um you know, we've it's the stories we hear about day in and day out are just they're just not even believable at times. Um we've got a a company we talked to recently that um they sent out a memo to their engineers and said, "We've got to start getting three bids on everything." Um yeah. So they sent a they actually found this email going to a supplier saying, "Hey, sorry to tell you this. We've got to start getting three bids." the supplier emailed the engineer back and said, "Don't worry, I'll set up two more LLC's and I'll set I'll [laughter] send you all three and for two or three years he was doing this." Wow. And uh so but I mean I love second order consequences though. Like I mean hey that is a hustle if I have ever seen one and I I appreciate but it's also so trivial. I mean for what few hundred bucks to set up an L's each time it's so easy. I mean no it's true. Well, and it but it's I was this one thing I was going to say. I remember in my M's program uh that I'm very much so talking about in the supply chain side of things. You it's it is uh bad or poor fiduciary responsibility not to have at least two to three vendors for every single service that you have because you don't know what the market is if you don't Right. Like it in it encourages competition, right? Absolutely. But they should probably be vetted, you know, history, you know, like [laughter] Yeah. Make sure they're not owned by the same company. Yeah. Yeah. No, I fully agree. Yeah. Yeah. Yeah. But again, it's like the best laid plans. I mean, yeah. No, unintended consequences are so such a real thing. Yeah. Have you had any requests or anything from the operators because this is I think just personally, I think it'd be interesting. You know, of course, operators have so much data coming from so many places. is probably pretty tricky to execute, but uh being able to, you know, not only have your bids, but then being able to tie that back to the actual jobs on the back end, right? Like, so currently we we stay away from that. And um you know, from what from what we find out, it's just the implementation time to actually execute and follow through with that ends up bogging down the whole organizations. Most of the companies we deal with right now, um they love that we're able to stand them up in, you know, very just a few hours. um where a lot of the software I think one of the initial hurdles they see before we can talk to them is well we don't have six months to implement it we don't have all this time we're too busy and that's what the first thing we have to let them know is that you don't need it time you don't need um you know extensive amount of resources to do a deployment so um that's uh that's uh I think pretty important what about uh working with people who like to use Excel I mean how how have you guys worked worked with that I mean it's not a problem I We have the ability to import and export to and from Excel and uh so we've got all that already built in and um our clients use it all time. We've got kind of internal stats that sees how often that's being used and it's very frequent. So yeah, um it still makes it to where you know we standardize the process and we've got repository of all the data that people can search and analyze a lot easier than um trying to figure out. I mean, we've got a we've got a top 10 operator right now that um you know, we we deal with. They have no repository of any of their data. That's why they that's why they moved to us. Yeah. They have no approved vendor list. Um it's all in people's emails. They're trying to find it, [snorts] you know, a long period of time. It's really just kind of being pieced together. So, um I think that's a lot of times how some of these operators have um have worked in the past and um so I think we have a you know really simple solution to make it a lot easier for them going forward. So yeah, and I you know I remember where you talked to us and it's like even just the auditability is like a huge feature in and of itself. Huge. Yeah. Yeah. That's I mean there's so much of that especially historically in the oil field, right? where it's like, you know, the guys buying the the field foremen, you know, guns or bringing cases of whiskey out every month or taking them to concerts or buying cars and all of that fun [ __ ] that you don't we don't stop that, right? But having an audit trail and having, you know, the ability to see that, hey, multiple vendors did bid on this and here's all the pricing and here's who touched it and or opened it and who messed with it and all that stuff. I really also don't want to gloss over the fact that how much I personally appreciate the fact that you'll have your own platform but you have this direct integration into Excel which is the tool that most of these people deal with every single day and so you're not trying to force square peg round hole like hey you got to change your entire workflow over to this thing. Sure. No, we can integrate direct. Like there's that's kind of like an art to me as far as like the software dev side is being able to get the right data to the right person and the right tool where they need it and what they're used to and comfortable with. That's really cool. What what do you see I want to know your opinions just personally on you know VMs versus containers versus we don't even have to get into Kubernetes but just VMs and containers in general because being at Hivesell you know again our whole pitch was containerization Kubernetes and there were still so many op people that I talked to not just operators but companies in general that are still running VMs that you know might be looking at containerization but aren't necessarily sure or it's you know new so of course it's new and intimidating and you know well it's worked this way so long why are we going to yeah break it right you're the first person I so I I think I I think it's not a I think it's not a one or the other I think you really more look at like legacy applications and more like serverless or really the next generation of applications I think those legacy applications are going to have to continue to live on VMs Yeah. Um until they essentially are deprecated over time. And uh I think in certain use cases it makes sense where um let's say you have a SAS environment but you need to connect to a SCADA system or something behind a firewall. Maybe you need like a connector device or like a bridge device that can do that. And that's where a future VM would make a lot of sense. But I do think as you continue to upgrade and evolve software, I do think it's removing that whole infrastructure or virtual machine layer, removing those additional administrative burdens that come along with it is incredibly important, but it's not a rip and replace. It's going to have to be a gradual scale down and you know scale down on the VM, scale down on the and really scale up in the Y. Yeah. So yeah, I mean and technically probably most containers are being deployed on VMs if you I mean EC2 instance is a VM. It's like it's not just one server, it's a partition, you know. Yeah. Yeah. But I still kind of look at them different where it's like when you're running like a true serverless environment. Yeah. It's it's like look at Office 365 and like there used to be like Exchange administrators that were at like these even small companies. I remember I used to maintain SharePoint was hosted on prem and oh of course like in 2000 when I was 2002 2003 I remember I used to manage a veterinarian's u clinic in Cyprus they probably had 40 people there they had their own exchange server and uh I mean it was a it was a 30hour a month job to administer that exchange server and like you know all of that's been ripped and replaced now with office 365 you've got your front desk receptionist can manage it now it's so easy and I think apps will continue shift that way. Um and uh you know I think that's uh I think that's the future of uh you know I mean just you know how powerful Salesforce I mean the amount of apps that have been built around that ecosystem is insane. So I'm also curious about just the the uh data center stuff especially in Houston, right? Like I worked for very briefly I worked for a uh basin modeling reservoir modeling uh software company and one of their big like uh you know unique value props was you know in patrol they were limited to how many CPU I don't even remember if it was CPUs or GPUs back then but they were limited to what eight that they could run their basin model on right and these basin models are insane right like it would take weeks to run a model on patrell and we could we had an infinite number theoretically of CPUs that they could run on and they could run them very quickly. But I did I had no idea until I worked at that job that there were all these data center like high power high performance compute centers in Houston. Oh yeah. And like there's so much compute infrastructure in Houston that people have no idea. It used to be called Cyrus 1. I don't know if it's still called that or not but that was Yeah. It's changed to datab bank and uh but uh the uh yeah I mean there's a ton in Houston. you know, there's still a great need for data centers that on the local side, on the colo side. Um, it's a it's a great it's been great to me. Um, but I think where it's really great at, it's great for the for the local hospitals. They're not going to, you know, there's no point for Houston Methodist Memorial Herman to have their data in, you know, a Virginia um [laughter] AWS region, right? Um, you know, have it here, have it with dark fiber. You can maintain the security presence that you need. And uh where it's also really great at it's great for the governments, municipalities because they're able to buy all the server equipment with bond funds, okay, as a big capital purchase and depreciate it. Well, it's the thing is it's hard for them to spend operating in. It's hard to spend operating expenses. It's really easy for them to spend money through a bond and uh so for them it's better to pay all that money up front. Yeah. And uh they don't really care about the cost. Um, but if you have that monthly cost to the cloud, I think a lot of the employees would prefer for their infrastructure to be on the cloud. Sure. But it's it's really more buying model. So yeah. Um, but uh yeah, I mean there's some huge facilities here. There's one I know in West Houston here that's got um I forget the name of the company, but you know they've got all these mineral oil cooled um servers. Oh yeah. And uh you know they it's a it's a big hypers scale yeah facility there. No that's I mean we talk about it in the office a lot. A lot of people are you know at least with all the energy transition stuff, energy conservation stuff and Chuck's been talking about it quite a bit lately. It's just like with with all the AI stuff that we're currently using and God knows what's to come. All of that requires GPUs and server infrastructure which guess what all requires electricity and power like it's [clears throat] and needs transmission too. all the infrastructure around that. And so it's one of those things that's like energy demand is not going anywhere. Like computers alone are going to continuously, you know, scale that up and out beyond just what individual uh and businesses are going to anyway. But it's or countries, right? Like it's, you know, when you're start when you hear how much it costs to run GPT every day and all that stuff, no one thinks about like, oh yeah, there's also a shitload of power going into all these things. It has to come from somewhere. Yeah. Electricity comes out of the wall and just, you know, the internet just works, you know, right? Yeah. my daughter, we there was like a random pop-up storm that came through Katie last night and it was we got all of like 4 seconds of rain uh unfortunately, but there was just a bunch of wind and our power went out for like 30 minutes and my daughter was just having like a legit panic attack like she was already doesn't like the dark and then of course she's like you mean there's no there's no white noise for me to sleep with and I can't yeah like all this stuff and I'm like yeah welcome to life before the [laughter] internet like you know just the internet alone being down was just such a culture shock to her that it's crazy. You got anything else? Uh, no, I don't think so. I would I would ask about data, but I assume y'all's data is probably pretty general and not super uh nothing too crazy about it. Yeah, there's really nothing I would say that's crazy about. So, interpret seismic data or any of that. I was talking to another co-founder recently that I I forget exactly how many rows of data he was telling me they had, but I mean it was several billion and I was like I'm glad we don't have that problem. Yeah. [laughter] Yeah. I mean I guess my only question would be like on the database selection side obviously Firebase and then to [ __ ] and both those are unstructured. I mean was that to provide the flexibility early on when you didn't really know what the schema was going to look like or Yeah, it was really to provide the flexibility. you know, going forward, we've got like very strict models around it where it's not um you know, we we we don't have the ability to um kind of iterate on the fly anymore. We do have models that kind of define the data in a sense, but um that's really the initial reason was, you know, not I mean that between you know having to do it kind of the old fashioned way with a no we've got a new product that's forthcoming that's a sister company been out I can't talk all about yet but we went through the whole process. We're using we're still using node we're still using Vue but we're using Postgress DB on that. Okay. So we kind of decided to give that a shot on the yeah well I mean all these have started adding more kind of uh JSON blob support and everything too. So um you know you can make things fit fit things into rectangular box now. Exactly. You couldn't before but yeah otherwise I think we probably jump into speed round. Speed round. So, ask you some random questions about you and in general, just short quick answers, but uh I'm very curious to know this one. Favorite video and board game. [laughter] Video. So, video game I don't play a lot. Uh probably Mario Kart with my kiddos. So, I've got a we got eight and 10-year-old sons and that's probably our Friday night. And on what platform? Switch. Switch. Switch. Yeah. My I don't even know why we just I think when we moved in the house I set it up because I had my electronics box right with the entertainment center and my wife's Wii was at like the OG Wii was in there and it sat there for years and then my daughter started getting into like Mario Kart on the iPad or something. And so I was like, "Oh, we've got Mario Kart on the Wii, you And then I got down this entire rabbit hole of like, I think you can jailbreak the like I was going to buy games for the Wii and stuff and I was like, I started looking. They're just as expensive as brand new games are. I'm not going to spend $60 a game for my kids to play once potentially. And uh but if you can find an OG Wii, jailbreaking them can literally be done from the Wii directly. [laughter] Like it's it's crazy. And then you just plug a flash drive in, download the the the games, and go from there. So it's it's pretty fun with young I've got the I've got the old OG um Nintendo back from like the Okay. But I'm I'm so nervous it's like going to catch on fire one day. [laughter] Um you know, it's like I've got it I pull it out around Christmas time, but I'm like I always tell my wife like do not make do not leave it plugged in. We're [laughter] going to come home and uh you know, things getting old, but I always hate having to blow in the things. And uh but um yeah, board game Monopoly, but we usually play it on the Switch. So that way it's mostly so my kids can't cheat because they [laughter] start trying to shift rules and so forth, but um it that's about two and a half hours it takes us. We do it a couple times a month. So yeah. Um so yeah, I usually hand handle more of the kind of technical questions, but um what's your favorite managed service?
Uh I man I think S3. I mean it's uh it's incred. It was the first really AWS service ever. Yeah. and uh to not ever I mean I used to have to deal with full hard drives all the time like on hundreds of cases so it makes it real nice. Yeah. Know it's really flexible but cooler advanced services out there of course but but I mean that's a what a lot of it the foundation is built on. I think it's what accelerated a lot. Yeah. So I mean you look out even how many different you know even like what Google storage is or their equivalent of blob or whatever they call that is Google cloud buckets. Yeah. And those are S3 compliant as well right. Yeah. Yeah. Same. And then even like I think some of the even onrem you know solutions now are S3 compliant like cloud storage. So it's pretty crazy. Yeah. What is do you have a uh just a a favorite or recent person or git repo that you found that you really like or found really useful by chance? Um I've just started using gb. It's a uh Google email backup service. Okay. Oh, nice. That um was a uh was on a git repo and uh it was kind of an interesting thing to uh um be able to back up Gmail instances. I've got in my personal email account, I've got all my emails going back from like 1998 and it's well over a million now and uh I had to do a migration and uh that was about the only feasible way to do it. So, no, it's pretty sweet. Um what's a um piece of technology you're most you know excited about, you know, in the next, you know, five ten years, um next year really. goes, you know, it might be a long answer, maybe not for lightning round, but you know, everybody's been saying blockchain's going to be big, and I never really thought it was going to be big because nobody's really ever found a real use for it yet. Um, I think AI is going to be huge. And uh, but what I'm worried about is I'm worried about like like AI generating like a 10-page document and then communicating back with an AI and giving us a 10-page document response. At what point do we need something that's 10 pages long if AI is generating it and AI is going to comprehend read? So um that's the one thing that I'm kind of confused about but um I think it's going to be I think it's going to catch on. Yeah. And then where does liability lie you know with some of that stuff like absolutely. So um you know I I don't know. Yeah. So, no, that's I I know I've said it before, but when the first few times I used GPT and the language models, that was the first time since like Napster that I had felt that same like, holy [ __ ] this is going to change everything kind of feeling, you know, almost 20 years later, right? Like definite inflection point. Yeah. Um, what what is what is one we'll wrap it up. What is one piece of advice that you would give to somebody either starting out looking to get in to break into energy tech or transitioning into the energy tech development space that that you wish you knew when you kind of started your your journey? Uh sell cycles are long. Find a find a pilot to work with uh and just jump in and do it. Um I've got way too many people I know that just talk about doing something for years and years and years and never actually do it. No. read the book uh build by Tony Fidel very early on and you know his approach is you know get out there and get feedback quickly and innovate and uh uh move forward and uh that's uh that's one thing I think we've done real well. We've done plenty of things wrong but that's one thing that I think we did real well. So yeah 100%. Yeah. No, the sales cycle one [laughter] that needs to be its own clip. If you're coming from the valley or whatever it's not going to you're not going to get full adoption. It's not self-service on the on the whole oil and gas industry. Everybody's so nice and like on the previous industries I've been in, people will just very frankly tell you no, I'm not interested. Yeah. Hang up on you, whatever. Oil and gas industry, everybody's incredibly nice and they'll take a meeting. They they'll obviously hear you out and uh that's a that's a great place to be. Yeah, for sure. Although there are times where I felt like in my sales path, it's like I wish someone would just tell me to f off so I quit like waste my time or not like you know. Yeah. But yeah, get off the pot. No, it's it's very true though. Like if if you're most people are willing to take a meeting and just have a conversation out of the the blue even in most situations. So, where can people find you? How do they learn more about Bitout? I'm on LinkedIn. I'm Rodney Giles. I'm on Twitter, Rodney Giles. Um bit out.app is our website. And uh check us out there. We're all over LinkedIn, too. And uh you know, feel free to reach out if you have any questions. Perfect. Awesome. Awesome. Thanks for showing on. Yeah.