Customer Case Study
Why Morgan’s Field Crew Said “That’s It?” to crewOS
The biggest fear with any field software rollout is adoption. Morgan’s crew went from five disconnected systems to one app, and the hardest question was two words.
“That’s It?”
Ricci Halbrook, Morgan Site Services Operations Manager, had been preparing himself for the pushback.
He’d seen it before. New software rolls out, the field guys groan, someone refuses to download the app, the foreman keeps a paper backup “just in case,” and three months later you’re running two systems instead of one. That’s how it usually goes in crane service. These are technicians who work 60 feet in the air rewiring hoists, not people who get excited about software updates.
So when Halbrook sat down with his crew in Houston to walk them through crewOS for the first time, he expected questions, resistance, at least a few crossed arms.
He showed them how to clock in. How to see tomorrow’s schedule. How to open a work order, fill out a service report, and get a customer signature, all in the same app.
The room was quiet. Then one of his guys looked up and said:
“That’s it?”
“That was the best response I could hope for. That’s it. Okay, great. You can go do this.”
Ricci Halbrook
The Fear Every Operations Manager Has
Morgan Site Services is the field service division of Morgan Engineering: a 163-year-old crane manufacturer with branches in Ohio, Michigan, and Texas. Halbrook built the Houston branch over four years, hiring every technician individually.
Before crewOS, Morgan ran on five disconnected systems. InspectAll for inspections. Spreadsheets and OneNote for timekeeping. Separate payroll software. GP for accounting. Text messages and phone calls for scheduling. Every technician entered time in three different places every single day.
Halbrook knew they needed to consolidate. He also knew that the hardest part wouldn’t be picking the software, it would be getting his team to actually use it.
“Sometimes a mobile app might as well be written in a foreign language for certain people. Not everybody’s at the same technical skill level.”
Ricci Halbrook
This is the fear that keeps operations managers up at night. You can buy the best platform in the world, but if the guys in the field won’t touch it, you just added a sixth system to the pile.
What Made It Different
Morgan didn’t flip a switch and go live overnight. They rolled out gradually, pulling a few team members in first to test, then expanding to the broader group. But what surprised Halbrook wasn’t the timeline, it was how short the learning curve turned out to be.
“People of all technical skill levels have been able to walk into it, understand it, follow the workflow.”
The key was that crewOS didn’t ask technicians to change how they work. It just digitized what they were already doing, clocking in, checking their schedule, going to a job, filling out a report, getting a signature, clocking out, and put it in one place. The workflow on the app mirrors the workflow in the field. There’s no translation step.
“We were expecting maybe, hey, we’re going to have some glitches, guys doing the wrong things or not knowing where things are at. That period was extremely short. That period of ‘here’s the app in my hand’ to ‘can you show me all my time?’, it’s like, yeah, it’s all right here.”
Ricci Halbrook
Within days, technicians weren’t asking how to use the app. They were asking to see their own data.
Replacing Three Steps With One
The fastest adoption win was timekeeping. Before crewOS, every technician logged hours three times a day, once on the work order, once in a OneNote document, and once in a payroll app. It was the kind of redundancy that nobody questioned because it’s just how things were done.
“Reducing redundancy was one of our system pain points for sure.”
Ricci Halbrook
crewOS collapsed that into a single entry. Clock in on the app, and the hours flow to the work order, to payroll, and to accounting automatically. The technicians didn’t have to learn three new things. They had to learn one thing, and it replaced three old ones.
That math lands immediately with a field crew. Less paperwork. Less time at the end of the day doing admin. More time doing the work they were hired to do.
The Service Report Upgrade They Didn’t Know They Needed
The old process: fill out a PDF service report by hand, get a signature, save it into the right SharePoint folder with the right naming convention. If the technician was tired after a 12-hour shift, and he usually was, the handwriting got worse, the details got thinner, and the file ended up in the wrong folder or no folder at all.
crewOS replaced that with structured digital forms tied to specific assets. The crane is already in the system, and the fields are pre-built. The technician taps through the report, adds photos, captures a signature on screen, and submits. No guessing on file names. No hunting for the right Teams directory.
“It was mostly the human condition, the biggest obstacle, not the file structure. Hey, where’s the service report from this day? Rather than an automated system where you got paid, I’ve got that paperwork in my folder because you were on a work order that day.”
Ricci Halbrook
The technicians didn’t resist this change. They welcomed it. Turns out, nobody enjoyed handwriting service reports at 7 PM after a full day on a crane. Giving them a faster, simpler way to close out their day was the easiest sell Halbrook ever made.
The Inspection Question That Answers Itself
One unexpected side effect of easy adoption: Morgan’s inspection reports got dramatically better, because crewOS made thoroughness the default.
In the old system, a tired technician might skip a photo or shorthand a description. In crewOS, the inspection template walks them through every component. Photos are custom-sized and embedded. The asset summary page populates automatically. The report that comes out the other end is so detailed that Morgan now uses it as a sales tool in prospect meetings.
“Anytime that we put our report down, it’s noticeably different than what the customer’s seen before.”
Ricci Halbrook
The quality of the output went up, not because the technicians suddenly got more diligent, but because the tool removed the friction that made cutting corners easier than being thorough. The app did the organizing. The technician just had to do the inspection.
What “That’s It?” Really Means
When Halbrook’s technicians said “That’s it?”, they weren’t being dismissive. They were relieved.
They’d been entering time in three places. Filling out paper forms at the end of long days. Texting their schedules back and forth. Saving files into folder structures nobody could remember. And someone was finally handing them a tool that made all of that simpler, not more complicated.
“That’s it” is what adoption sounds like when the software is built for the people who actually use it.
Morgan Site Services is a division of Morgan Engineering: 163 years in heavy industry, three branches, about 45 field technicians, and a rollout that started with “That’s it?” and never looked back.
See how crewOS fits your crane operation
Book a walkthrough to see how crewOS supports scheduling, field reporting, inspections, job tracking, and billing flow for crane and industrial service companies.