When The CEO Said ‘My Son Needs Your Office’ I Said ‘Of Course!’ And Worked From Home. Permanently. 1 Week Later, He Realized I Was Never Coming Back…
The CEO gave my office to his son after 13 years of relying on me to keep his company running behind the scenes. I simply said, “Of course,” because he had no idea what would happen once I stopped sitting in that office.
Tap LISTEN TO THE FULL STORY below to reveal the narrated video and start listening.
The CEO gave my office to his son while I was elbow-deep in fixing our ERP system, and he delivered the news as casually as if he were asking me to move a coffee mug. For 13 years, I had been quietly keeping Hartwell Industrial Solutions from falling apart. Yet Michael Hartwell walked into my office, barely looked up from his phone, and announced that his 25-year-old son Austin would be starting Monday—and Austin needed my office. There was no discussion, no warning, and apparently no question about what moving me might mean.
My name is Bob McKenzie. I’m 47, and I’d been running systems at Hartwell since leaving the Army. Before entering civilian life, I’d worked as a logistics specialist at Fort Campbell, managing supply chains responsible for keeping thousands of soldiers equipped with what they needed, when they needed it. That experience taught me the importance of planning, reliability, and understanding how every part of a complicated operation connects.
When I joined Hartwell in 2010, those lessons became essential. The company manufactured industrial components—gears, bearings, and hydraulic parts for heavy machinery—and employed roughly 200 people. They knew their trades, but the company’s technology was another matter. Its ERP software dated back to 1998, vendor management depended on Excel spreadsheets, and compliance reporting often meant somebody remembering to file something before a deadline.
🎧 Listen to the Complete Story
Press ▶ Play below to enjoy the full narrated story.
I spent my first two years simply learning how everything worked.
Manufacturing systems aren’t isolated. Change one process and three others can suddenly stop functioning. Instead of tearing everything apart, I built connections around what Hartwell already had. I wrote custom scripts linking the ancient ERP system to vendor portals, created automated inventory alerts, and developed manual overrides for suppliers that repeatedly changed their data formats.
Then there was compliance.
Hartwell had reporting obligations involving OSHA, the EPA, state safety boards, and other agencies. Missing a deadline or submitting incorrect information could create serious problems. I spent three years building a system that tracked requirements, deadlines, and necessary forms.
By 2015, the operation ran smoothly.
Vendors liked working with us because orders were accurate, payments moved properly, and someone answered when problems appeared. Over time, I built direct relationships with the people behind those companies. They knew they could contact me when something went wrong or when an opportunity appeared.
But Michael Hartwell didn’t see most of that.
From his perspective, the company simply worked.
Orders were filled. Reports were submitted. Vendors were paid. Computers appeared to handle everything automatically.
What he couldn’t see were the countless hours of custom coding and manual maintenance hiding behind those apparently automatic processes.
Even something as ordinary as vendor payments wasn’t truly automatic. Our ERP couldn’t communicate properly with half the vendors’ systems. Invoice formats changed. Delivery confirmations arrived through email, fax, phone calls, and sometimes handwritten notes from truck drivers.
I manually verified transactions to make sure the numbers actually matched.
One steel supplier alone used three invoice formats depending on the type of order. Their purchase-order numbers didn’t match ours, so I had built a lookup table connecting the two systems. When they changed accounting software, I spent two weeks rebuilding the integration.
Austin knew none of this.
To him, I was probably just an older guy sitting in an office typing on a computer.
Now the CEO gave my office to his son, and Michael stood there looking almost surprised that I wasn’t arguing.
I looked at the man whose company I’d quietly helped hold together for more than a decade.
“Of course,” I said.
That was all.
And Michael walked away without realizing what those two words actually meant.
