TL;DR: CapTech Services ran dozens of Texas oil wells on scattered Excel sheets until Designli spent real time learning how the business actually worked before writing a line of code. What came out of it was a purpose-built system: well tracking, GPS-tagged job logs, and same-day customer reports, built around how CapTech's crews and customers actually operate, not a generic template with the company's name on it.
Where CapTech Started
CapTech Services runs dozens of active wells across Texas, and until recently, the wells themselves, the maintenance work, and the customer updates all ran through the same tool most small businesses default to when they haven't built anything yet: a stack of Excel sheets. It worked, in the sense that CapTech was a real, running business. It just wasn't built to scale past whatever one non-technical owner could track by hand.
Brandon Patterson, CapTech's co-owner, wasn't in a position to build that system himself. He needed a technical partner willing to learn an industry it had never worked in well enough to design something the field crews would actually use.
The oil and gas software market alone is on track to grow from about $12.88 billion in 2026 to $26.75 billion by 2035, and roughly 68% of oil and gas companies have already adopted some form of automation or analytics software. Field service management, the broader software category built to coordinate crews, jobs, and reporting across industries, is growing even faster: about $6.7 billion this year, projected to hit $13.8 billion by 2033. Plenty of vendors are chasing that market with generic tools. Fewer of them bother to learn a specific operator's business before they start building.
The Practice We Follow
Understanding an industry and having worked in it aren't the same thing, and founders in specialized fields are usually the first to notice which development partners skipped the first part.
Before we write a line of code for a business we don't have direct experience in, we spend real time learning how the operation actually runs: who does what, where the bottlenecks are, and what a non-technical owner needs to see without needing anyone to walk them through it.
Why This Matters
A tech development partner that treats every client's operation as a generic workflow ends up shipping generic software, and generic software is exactly what CapTech was trying to get away from. Owners running specialized operations, oilfield services, medical practices, construction, whatever it is, can tell almost immediately whether the team building their system actually understood the job or just skimmed a requirements doc. Get that wrong and you end up with a system nobody in the field wants to use, which means people quietly go back to the spreadsheet.
How It's Done in Practice
- Learn the operation before designing anything: Designli started with a SolutionLab, working directly with Brandon to map out how CapTech's crews actually service wells today: the recurring jobs, the one-off client requests, and where the Excel-based tracking was breaking down.
- Design around the field team, not a template: The UX/UI work was built around two very different users at once: the crews doing the physical work in the field and the office side managing schedules and client relationships, rather than a single generic dashboard.
- Build proportionate to the business: Instead of a fully custom database, Designli used Airtable as the backend, keeping the system's complexity and cost in line with what a business like CapTech's size actually needs. On top of that, they built a well-management tool for tracking recurring jobs and custom requests, manager-level work logs for field coordination, GPS logging with automatic photo tagging tied to each job site, and customer-facing daily reports listing the parts used, photos included.
- Stay in it past launch: A dedicated product team, a Product Owner, developers, designers, and QA stayed on CapTech's system full-time for six months, then moved to a lighter support plan once things were stable.
So What Does This Practice Actually Get You?
CapTech went from tracking dozens of active wells across scattered spreadsheets to a system built specifically around how their crews and customers actually interact. There's no load-time percentage or revenue chart to point to here, just a business that finally has real software built for how it actually works, instead of picking between something generic and nothing at all.
What Brandon noticed most wasn't a feature. It was that a team with zero background in oil and gas still got it: "Although Designli isn't related to the oil industry, they can still visualize and understand what we're trying to accomplish. Designli has exceptionally understood our scope and how our company works."
CapTech's Evolution with Designli's Platform
That system didn't happen all at once. It followed a specific roadmap: SolutionLab first, to map out how CapTech's jobs actually flow before any design work started. Then design and development in parallel, building the well-management tool, the manager work logs, and the customer reporting around that map on an Airtable backend sized for the business. Then a dedicated product team, in place full-time for six months, to build it out and fix what didn't work on the first pass. Then a lighter support plan once the system held up on its own.
Here's what that roadmap actually produces on a given day: a tech shows up at a well, opens the app, and logs the job against a checklist built around CapTech's own recurring work, not a generic maintenance template. The GPS location and job photos tag themselves. By the time the tech is back in the truck, the customer already has a report with what got done and what parts got used, without needing a phone call. The manager back at the office sees the same thing in real time instead of waiting on a spreadsheet update at the end of the week.
FAQs
What is SolutionLab, and why did Designli start there for CapTech?
SolutionLab is Designli's five-day, $6,900 product roadmapping engagement, run by a Solutions Architect and a Senior UX/UI Designer. For CapTech, it meant digging into how wells actually get serviced today, before any design or development work started, so the resulting plan was based on how the business runs rather than a generic template.
How does a dedicated product team work for a small, non-technical-founder business like this?
It's a full unit: a Product Owner, developers, designers, and QA, that stays with the product for as long as it's needed rather than a handful of contractors rotating through tickets. For CapTech, that team stayed on full time for six months before moving to a lighter, ticket-based support plan once the system was live and stable.
Why build on Airtable instead of a fully custom database?
Because CapTech didn't need the overhead of a fully custom-built database to solve the problem in front of it. Airtable gave the team a reliable, flexible backend without adding cost or complexity that a business this size doesn't need yet.
Why is SaaS the future of oil & gas software?
Cloud adoption is moving fast in this industry; roughly 62% of large oil and gas operators have already embraced cloud tools for core operations, and the oil and gas cloud computing market is on track to roughly triple by 2034. It's the same cloud-first approach Designli builds toward: hosted, accessible from the field, with nothing for the operator to maintain on their own.
What Designli Actually Sells for Specialized Operators
CapTech didn't come to Designli asking for oilfield expertise. It came asking for a team that could take the time to understand a business it had never touched before and build something that fit it instead of something generic.
What Designli actually sells is the discipline to learn a business before designing for it and a team that sticks around long enough to keep that understanding current as the business changes. CapTech got a real system built around how it actually runs, not a template with its name on it.
If your business runs on spreadsheets because nobody's built you something better yet, schedule a consultation.
Related Topics:
How Designli Helped Scale a Logistics SaaS Platform
How We Build: Designli’s Full 2026 Development Process, Pricing, and Services
