FIELD NOTES · BUILD PHILOSOPHY
By Brian Phetteplace · May 25, 2026 · 7 min read
I've sat through more software demos than I care to count. Every vendor uses the same word: configurable. They say it like it means custom. It doesn't. After running Reliable Oilfield Services in the Permian Basin and watching three different "configurable" platforms fail to fit how my crew actually works, I built ReliableTrack to solve a different problem — and the difference matters more than the marketing makes it look.
The word "configurable" is doing a lot of heavy lifting
When a vendor calls their software configurable, what they almost always mean is: we built one workflow, and you can rename some fields. Maybe you can drag a column to a different spot on the work-order screen. Maybe you can hide the parts of the form your crew doesn't use. That's it.
Underneath the surface, the data model is fixed. The screens are fixed. The reports are fixed. If your business has a quirk — a specific compliance form, a regulator who wants ticket data in a peculiar shape, a customer who insists on a unique invoice format — you're stuck. You either bend your business to fit the software, or you wait for the vendor's roadmap to maybe address it in some future release.
"Configurable" usually means: we built the software, you live in it.
What "custom in 48 hours" actually means at ReliableTrack
When a Permian operator signs up, here's what physically happens: I get on a 30-minute call with them. They walk me through how a ticket flows today — paper, email, whatever it is. They tell me which fields matter, which forms regulators want, who signs off, what the invoice has to look like.
Then I rebuild the relevant screens in our codebase. Not "toggle a setting" — I write the actual UI, the actual form logic, the actual PDF template. Inside 48 hours, the operator logs in and the software already looks like their business. Custom field names. Custom forms. Custom reports. Their workflow, in code.
That's only possible because the platform was built by one operator (me) on a code generation stack that turns short specs into shippable screens in hours, not weeks. It's not magic — it's just an honest reckoning that field service is too varied to ship one workflow and call it done.
Where configurable breaks down in the oilfield
Three places I've personally hit the wall on "configurable" field service software:
- Compliance forms. EPA Method 22 observations, OOOOa storage tank inspections, PSV testing logs — every regulator wants the data in a slightly different shape. Configurable platforms force you into their generic inspection form and you end up keeping a parallel spreadsheet anyway.
- Multi-step jobs. A heater treater PM isn't one task. It's an arrival check, a burner inspection, a thermocouple test, a pressure relief verification, then the customer signature. Configurable platforms model that as one "job" with notes. You lose the audit trail.
- Customer-specific invoicing. Every operator in the basin wants something different on the invoice. AFE numbers. Cost-center codes. Well IDs in a particular column. Configurable platforms give you "custom fields" that don't actually map to the printed PDF.
"But custom software is risky" — the old argument doesn't apply anymore
For thirty years, custom software meant a six-month build, a $200k bill, and a system nobody could maintain after the original developer left. That math is dead. With modern code generation and a multi-tenant architecture, custom screens can be built in hours and maintained alongside the core platform.
The risk of not going custom is much higher: paying month after month for software your crew works around. Every "workaround" — the spreadsheet on the side, the texted photo, the paper backup ticket — is a sign the software didn't fit. And the cost shows up as missed downtime targets and compliance exposure, not as a line item.
The honest tradeoffs
Custom isn't a free lunch. A few things to know:
- You need to know what you want. If you can't describe how your business works in plain English, no amount of custom code will save you. The 30-minute spec call is where the work happens.
- Iteration replaces upfront design. The first build won't be perfect. The point is you can change it next week, not next quarter.
- The vendor relationship matters more. You're not buying a shrink-wrapped product anymore. You're buying ongoing tailoring. Pick a vendor who picks up the phone.
A quick test for your current software
Ask your crew one question: "What's the workaround you do every day because the software doesn't quite fit?" If they have an answer in under five seconds, you're paying for configurable when you needed custom.
If you want to see what custom-in-48-hours looks like for your specific workflow, start with the pricing page and book a spec call. We'll walk through your tickets, your forms, your reports — and you'll know inside an hour whether ReliableTrack fits.
Stop bending your business to fit the software
ReliableTrack ships a custom build in 48 hours — your forms, your reports, your workflow. Built and proven by an operator in the Permian Basin.
Frequently asked questions
What does "configurable" field service software actually mean?+
Configurable means you can flip pre-built settings on or off, rename a couple of fields, and maybe add a custom column. The underlying workflow is fixed. If the vendor didn't ship the feature you need, you're stuck waiting for their roadmap.
How is custom field service software different?+
Custom means we change the actual code to match how your crew works. New screens, new forms, new logic, new reports — built specifically for your business. ReliableTrack ships a tailored build in 48 hours.
Won't custom software break when the vendor updates it?+
No. Your custom build lives in your tenant. Core platform updates roll out underneath without overwriting your tailoring. You get the best of both worlds — your workflows plus continuous platform improvements.
How much does custom field service software cost?+
ReliableTrack's custom build is included in the standard subscription — no separate implementation fee, no per-form charge. We tailor it in 48 hours, then iterate as you grow.
What if my workflow changes six months from now?+
You email us, we rebuild the affected screens, you have the update inside 48 hours. That's the whole point — your software adapts to your business, not the other way around.