Field Notes • Systems Architecture

A Laptop in a Tow Truck: Why Field Operations Demand Simpler Systems

By John Loya • Published October 23, 2026 • Author of From Search to Paid Invoice

Much of my early studying and agency work happened in a commercial tow truck. On top of the truck was an orange beacon bar: the warning lights you turn on at the roadside so passing drivers notice you and, hopefully, use caution.

I started my towing business in Chula Vista, California, in 2009. Like every other owner operator, I needed people to find me when they needed emergency roadside service or commercial transport. I hired marketing help, and my experiences left me disappointed. I did not understand search engine optimization well enough to judge the work, and that gap is what pushed me to learn it myself.

I decided to understand the machinery myself. Around 2012, I bought an SEO book in the For Dummies series. Some of the tactical recipes were already dated, but the fundamental vocabulary gave me a bridge to understand how the web structured information. I learned WordPress, took intensive technical courses, and began applying structured layouts to my own company website.

Learning from the Driver's Seat

Soon after improving my own site, a friend running a billiards business asked for help. He became my first client. That engagement led to more word-of-mouth client projects, and eventually formed the core of Orange Beacon Digital, the agency where I now build local search, software, and automation systems. You can read more about my background.

For years, I carried a laptop directly in the cab of the tow truck. I added a cellular hotspot to my phone and worked on client architectures, code snippets, and directory schemas between roadside calls.

There is a particular kind of education in that environment. An owner who works in the field cannot sit at a desk all afternoon discussing marketing theory. Someone needs an emergency tow. A job runs long. Equipment breaks down. The work of running the business has to fit directly around the work the business sells.

Why Most Trade Software Fails

Most marketing advice and software for local contractors comes from people who have never balanced an emergency dispatch call while estimating a job. Estimates stack up, go out days later, and by then the customer has often signed with someone else. I cover that gap in my book and in the follow-up article on where local customers actually get lost.

In the field, any system that adds administrative friction is abandoned. Real operational efficiency comes from stripping away unnecessary steps:

  • Matching effort to actual operating capacity: Never market services or territories you cannot reliably dispatch to within reasonable response windows.
  • Closing the gap between inquiry and estimate: Every minute an estimate languishes in someone's head while driving is an opportunity for a customer to call a competitor.
  • Automating repetitive communication while keeping human judgment: Sending automated dispatch status updates, appointment confirmations, and invoice receipts allows the owner to reserve their focus for pricing accuracy and job execution.

From Search to Paid Invoice

This operational philosophy is the core thesis behind my published field guide, From the First Search to the Paid Invoice: A Practical Guide to Local Visibility, Customer Follow-Up, and Useful Automation.

Related Field Notes: Read Where Local Customers Actually Get Lost to examine the six customer handoffs, or explore Entity-First Visibility for the mechanics of semantic knowledge graphs.

About the Author: John Loya is an author, technologist, and the founder of Orange Beacon Digital. Discover more about his background, military service, and published research on his biography page or connect on Goodreads and Amazon Author Central.