I run an oilfield service company. I also wrote the software.
My name is Brian Phetteplace. I own Reliable Oilfield Services out of Midland, TX. We do production maintenance in the Permian — PMs on flares, heater treaters, separators, flame arrestors. We run a bilingual crew, mix of English and Spanish speakers, across the basin every day. We are not a tech company. We pump oil and fix equipment.
I built ReliableTrack because I had to. Not because I had a startup idea or found a gap in the market. Because I ran the software everyone said I should run, and it failed my crew in ways that cost real money and real time.
What broke first
We were on GoCanvas for a while. GoCanvas is fine if your tickets are simple and your crew speaks one language. Ours did not qualify on either count. My field techs were submitting tickets with missing fields. Customers were calling me — not to give feedback, but because they had no idea where their tech was or when the work was done. The PDF they got out of GoCanvas was generic enough that it could have been from any company on earth. It had no personality, no field-specific terminology, nothing that said "this came from us."
The Spanish problem was worse. I had techs who were excellent at the work — some of the best in the basin — but they were fighting English-only forms and losing time every single job. That is not a language problem. That is a software problem.
I started building at night
The first version was not pretty. It ran on my phone and nobody else’s. But it did the one thing GoCanvas would not: it let my Spanish-speaking tech submit a ticket in Spanish, and the customer got a clean English PDF the same second he hit Submit. I showed it to one of my techs at the shop. He said, "this is what we needed." That was enough for me.
Over the following months, every feature that exists in ReliableTrack today came from something that broke in the field. The offline-first architecture came from lost connectivity on lease roads where LTE is a rumor. The live ETA tracking came from a customer calling me four times in one day asking where my tech was. The AI captions on photos came from a billing dispute where we had a picture of the problem but could not quickly explain what it showed. The CPA-ready report export came from me sitting across from my accountant trying to explain what every line in a spreadsheet meant.
None of those features were planned in advance. Each one was the fix for something that had already gone wrong.
What we actually run on it
Reliable Oilfield Services runs on ReliableTrack every day. That is not a marketing line. I am not running some other system on the back end and showing you a demo of something different. The same platform you see here is what my techs open every morning in Midland. As of right now, we have filed over 62,000 tickets through it, tracked over $28 million in revenue, and scheduled more than 2,400 preventive maintenance events. The average ticket cycle time is under four minutes.
The bilingual interface is not a language pack bolted on the side. It is built into the core. My crew switches between Spanish and English mid-form and the output is always a clean, professional document on the other end. The AI translation and voice-to-text features came directly out of watching how my techs actually work — hands dirty, in a hurry, in the sun.
What makes it different from other field service software
The honest answer is: I built it with a specific failure mode in mind. Every feature in ReliableTrack exists because I experienced the absence of it in the field. That is a different design philosophy than a product built by engineers who surveyed contractors and built what they described.
Offline-first means the app works on a lease road with zero signal. Not "it retries when you get back online." It works fully offline — form submission, photo capture, GPS coordinates, AI captions — and syncs the moment connectivity returns. Your tech does not know or care whether he has LTE. He just works.
The customer-facing live tracker is something I needed badly before I built it. When a customer calls asking where your tech is, you lose five minutes of productivity per call. Multiply that by a crew of eight running six jobs a day. The tracker gives customers a live link — they can see the tech on a map, see the ETA, get notified when he arrives and when the job closes. My call volume dropped significantly the week we deployed it.
The AI on every page is not a chatbot. It is context-aware. When a tech is on a ticket for a heater treater, the AI knows that context and can auto-caption a photo of the unit, suggest a description of the issue, or help draft a customer note — in Spanish or English. When you export the PDF, it looks like a document a professional company produced, not something a tech typed on his phone in a hurry.
Why I offer it to other shops
I am not trying to become a software company. I still run the oilfield business. What I realized is that the problems I was solving — offline reliability, bilingual workflows, customer-facing transparency, paperless tickets that accountants can actually use — are not oilfield-specific problems. Every HVAC crew, every plumbing shop, every roofing company with six trucks has a version of the same issues.
So I made it available to other operators. Not as a generic SaaS platform where you get a login and figure it out yourself. As a custom build — your terminology, your PDF layout, your branding — deployed and live in 48 hours. I do the customization myself, or with the same small team that maintains our own deployment. You email me, we talk for fifteen minutes, and inside two days your crew is running a version of the same platform mine uses.
There is no sales team. There is no marketing fluff. There is nothing described as "coming soon" on this site — everything described is live in production right now because it runs Reliable Oilfield Services today.
If you want to talk
Email me directly: brian@reliableoilfieldservices.net. No form, no sales rep, no discovery call with someone who has never run a field crew. Just me.
If you want to see what the platform looks like before reaching out, you can read how it runs for oilfield crews or see how it compares to GoCanvas