— Case Study
An owner who couldn't take a Tuesday off — and the engagement that gave it back.
- Industry
- Petroleum Services
- Operation size
- ~50 employees
- Engagement
- Multi-year embedded operations rebuild
Anonymized: Client name withheld pending written approval. Details abstracted to protect proprietary processes; the operator outcomes are reported faithfully.
Summary
A regional petroleum services operator with ~50 employees was running its compliance, dispatch, financial reporting, and field workflows out of personal drives, paper forms, and one person's memory. Over a multi-year embedded engagement, TNDS rebuilt the operational backbone in plain Google Workspace tooling, automated the recurring reporting work, and put real-time visibility in front of the owners. Manual reporting time dropped an estimated 50 to 70 percent. Field data accuracy improved. The owners stopped being the bottleneck on every report.
What the operation looked like before
Operational and financial information lived in personal drives, shared folders, and inboxes. Leadership waited several days each week for reporting to be assembled by hand. Field crews communicated through a mix of paper forms, text messages, and email — which meant data got re-entered three times before it landed somewhere useful. The information that mattered most lived in a few people's heads. If those people were out, the operation slowed down. The owners knew the operation was working, but they couldn't see how well or where the friction was.
The five things that were actually broken
Fragmented data
Operational and financial information lived across personal drives, shared folders, and spreadsheets. No single source of truth. Decisions were made on whichever copy of the data the owner happened to be looking at.
Manual reporting
Leaders waited several days each week for reporting to be assembled by hand from multiple sources. By the time the report arrived, the data was a week old.
No real-time visibility
The organization had no dashboards. Leadership couldn't tell what was happening in the field today without picking up the phone and calling someone.
Inconsistent field processes
Paper forms, text messages, and email created re-entry work and errors. Field crews and office staff each maintained their own version of the truth.
No path to scale
The existing processes did not support growth or workflow automation. Every new hire required someone to explain the unwritten parts of the system.
What TNDS did
This was an embedded engagement, not a software install. TNDS spent time inside the operation — shadowing the dispatchers, sitting with the bookkeeper, riding along with field crews — before recommending or building anything. The fix was sequenced over time, by severity, with the operator's input at every stage.
Step 1
Workspace consolidation
Rebuilt the shared file structure, set up consistent document workflows, and standardized the tools the team used to communicate. The tools were already paid for — Google Workspace was already in place. The work was in using them properly.
Step 2
Real-time dashboards
Built dashboards that updated automatically from the operational data: productivity, throughput, financial summaries, and a small set of operations-specific KPIs. Leadership could finally see what was happening today, not last week.
Step 3
Workflow automation
Automated the recurring tasks that ate hours every week — reporting assembly, notifications, approval routing, summary distribution. The work didn't disappear; it just stopped requiring a human to do the assembly step.
Step 4
Field digitization
Replaced paper forms with mobile-friendly applications for field logs, safety forms, job checklists, and incident reporting. Same workflow the field crews already knew — just no longer on paper, and no longer requiring re-entry back at the office.
Tools used
The toolkit was deliberately conservative. Every tool the operator already paid for, used to its real capability. Nothing exotic. Nothing that locked the operator into a vendor relationship they couldn't maintain after the engagement ended.
- Google Workspace (Drives, Docs, Sheets, Apps Script for automation)
- Looker Studio (real-time dashboards)
- AppSheet (field-data applications)
- Firebase (custom application data layer where AppSheet wasn't a fit)
What changed
- An estimated 50 to 70 percent reduction in manual reporting time
- Real-time operational visibility for leadership — no more waiting on Friday to see what happened Monday
- Field data accuracy improved because crews entered data once, in the field, on the device they already had in their hand
- New employees were productive faster because the processes were finally documented
- Process governance and consistency held up under owner absence — the operation kept running when the owner took a day off
- A foundation for further automation and AI work, because the underlying data was finally clean and structured
Why this engagement looked the way it did
Most small operators in regulated industries do not need a software project. They need someone who has run an operation, who can sit inside the existing workflow long enough to see what is actually broken, and who can fix it using the tools the operator already pays for. The work was operational. The toolkit was incidental. The outcome was that the owner stopped being the bottleneck on every report — and could finally take a Tuesday off.
If your operation looks like this
An Operations Assessment is the first step. Two weeks, paid, walk-the-floor diagnosis, written report with priority order and quote for fix work. No commitment to embed afterward.