The Same Story, Different Company

Over the past few years, I’ve spent every day talking with companies in industrial field service: maintenance contractors, crane and rigging operations, power generation teams, industrial construction crews. The work is different from one company to the next, but the operational challenges are almost identical. And I keep hearing the same story.

It usually starts with something like what Mike told me on a call not long ago. He runs the industrial services division of a growing construction company. Three crews, about 65 employees, plants and job sites scattered across the region. Here’s how he described his current setup:

“We have just an Excel spreadsheet with a list of purchase orders. My lead guys come in, they figure out what’s urgent, what can wait, and they go out and perform the work just off of that basic list.”

Scheduling? Done that way for eight years. Communication with crews in the field? Text messages, phone calls, emailed photos. Back-office data entry? His words:

“Every bit comes to me. Every bit.”

He said something that stuck with me:

“We don’t have any automation for anything at this junction. That is one of our goals.”

He’s not alone. I have this conversation almost every single day.

 

How We Got Here

Everything started on paper. Then the internet arrived and software companies started building apps to digitize individual pieces of that paper world: one app for clocking in and out, one for scheduling, one for inspection reports, another for expenses. None of them were built to talk to each other.

The result is that most field service companies today aren’t operating on paper, but they’re not truly operating digitally either. They’re operating in a patchwork of apps and paper processes that don’t share information, require manual data re-entry to connect, and create more workarounds than the paper they replaced.

Chris, a service manager I spoke with recently, described his workflow this way: scheduling in Microsoft Projects, dispatching by email, timesheets submitted on paper, scanned, and emailed to HR, where someone manually calculates overtime for each person, by hand, every single month.

“I have to go through and dictate what each service consultant gets each week for overtime. It’s kind of just hand calculated, signed off on, and then scanned in and emailed over to HR.”

That’s a company with software. It’s just that none of it talks to each other, and the people in the middle pay that cost every single day.

 

The Real Price of “Good Enough”

The price on the invoice is not the price you’re paying.

The actual cost is in the labor that connects disconnected systems: the back-office manager re-entering the same time data in three places (once to bill the customer, once for job costing, once for payroll). It’s the dispatcher calling a crew member because the scheduling tool doesn’t surface job details. It’s the change order that goes undocumented because work expanded on a verbal agreement and nobody got a signature before the crew left the site.

Chris put it plainly:

“It’s either a verbal handshake, ‘Yeah, I’ll pay for it, get it done,’ and it’s either shortcoming on our part or their part of not signing a document, or it just gets lost in the shuffle. And trying to work back into that invoice is challenging.”

Change orders lost in the shuffle. Overtime miscalculated. Billing delayed because paperwork hasn’t made it from the field to the office. This is where the real money goes.

ProcessBarron, an Alabama-based company that designs, installs, and repairs industrial fans and material handling systems, was spending roughly half a million dollars a year managing their patchwork of apps and manual processes. Their billing cycle ran five to six weeks from job completion to invoice. Within the first month on a unified platform, they cut manual labor costs by 75% and reduced their billing cycle to 48 hours. By capturing change orders digitally on-site with instant signatures, they recovered over $1.6 million in their first year that they say they would have otherwise lost.

That’s not a technology story. That’s a business operations story.

 

Solving a Problem vs. Changing How You Work

There’s a meaningful difference between fixing a symptom and improving how your business actually runs.

When you buy an app to solve a problem, you treat the symptom. Your crew hours are hard to verify, so you get a timekeeping app. The headache eases, but the underlying issue remains. The data doesn’t connect to scheduling. It doesn’t connect to job costing or billing. It still has to be manually moved from one place to another.

The companies scaling cleanly aren’t asking “what app fixes this problem?” They’re asking: what does our entire workflow look like from the moment a job comes in to the moment we get paid, and where are the gaps? When you add tools one problem at a time, you end up with data scattered across systems that don’t talk to each other, and people in the middle manually connecting the dots. That’s not a technology strategy. It’s just a more expensive version of the paper it replaced.

 

Your Tools Need to Grow With You

Both Mike and Chris told me some version of the same thing: we want to grow. Mike wants to double his industrial services revenue. Chris’s company is scaling and taking on more accounts.

That’s exactly when the patchwork breaks. Every piece of manual work you’re doing today gets multiplied when volume increases. If billing runs slow now, it gets slower. If overtime is hand-calculated for ten people, imagine doing it for twenty.

DeShazo, one of the country’s leading crane manufacturers, came to us with this challenge. Fifty-plus years in business, 23 service locations across the U.S., and tools that had served them adequately for years, but weren’t going to scale. Their payroll process took two to three days every cycle. Their biggest concern was practical: modernize without disrupting a skilled workforce, many of whom had been doing things the same way for a long time.

All 23 locations were rolled out in under 90 days. Payroll dropped from three days to four hours. In the first year, they serviced and inspected over 20,000 cranes on the platform. They didn’t lose a single skilled tradesman in the transition.

That last point matters because I hear it constantly: “Our guys aren’t tech savvy.” That concern is real. But if the worry is that your experienced field crew won’t adopt the technology, the problem usually isn’t your crew. It’s the technology.

 

What It Looks Like When It Works

The field service operations winning today have something in common: one place where work lives.

Their crews use one app. When they clock in, it’s attached to the job. Safety checklists are gated, the system won’t let a job close until they’re done. Change orders get signed on-site. Everything flows to the back office automatically, without anyone chasing paperwork.

Their leadership can see what’s happening right now, not last month’s numbers pulled from three different exports. Which jobs are in progress. Which crews are idle. Where margins are tracking. The data is clean because everyone’s working in one system.

 

The Question Worth Asking

Before you add the next app to the stack, ask yourself one question: what does it actually cost to run your business the way you’re running it right now?

Not just in software subscriptions, in the hours spent reconciling data, the change orders that slip through, the billing lag, the overtime errors, the calls trying to find out what’s happening in the field. Most companies I talk to have never done that math. When they do, the conversation changes quickly.

The companies positioning themselves to lead their markets aren’t patching problems one app at a time. They’re building the operational foundation that lets them actually grow. That decision, to stop treating symptoms and fix the workflow, is the one that separates the companies that scale from the ones that stay stuck.