Case Study:
Operations & Process:
Regional Logistics Firm
Overview
Building the systems that let a logistics firm run without the need for its owners in day to day operations
Documented the core workflows and onboarding, automated manual customer service, and gave the business the systems to run without the owners in daily operations.
The Problem
The owners reached out because they intended to retire, but the business was not positioned to operate or transfer without them.
The company had scaled without formal operational systems. Core processes were undocumented and dependent on the owners and a small number of key employees. Onboarding was informal and relied on shadowing. Recurring daily tasks still required the owners' direct involvement. As a result, the business could not function — or be sold — independently of them, which blocked any path to retirement.
The Solution
I was brought in to build the operational infrastructure the business had grown without. The work ran in two phases.
1. Discovery: Mapping how the business actually ran
Most core processes were undocumented and lived with individual employees. I worked directly with the people running each function over two weeks to map every core workflow end to end, capturing how the business actually operated rather than how it was assumed to.
2. Documentation & Onboarding: Turning knowledge into systems
I converted each mapped workflow into a standardized SOP using process mapping to ensure each document reflected the actual process rather than an idealized one. SOPs were formatted by task type for linear processes and flowchart-based for processes with conditional logic, such as customer service resolution. Each SOP was validated with the employees performing the work before being finalized. I then built a structured, competency-based onboarding program off those SOPs, so new hires trained against a defined standard and were assessed on performance rather than shadowing individual employees.
Outcome: The business reached a point where it ran without the owners in daily operations. This cleared the path for them to retire earlier.
The Proof
Problem
Action
Result
Zero core processes were systematized
Documented 30+ core workflows, turning them into SOPs
Time owner spent resolving issues reduced by 40%
New hires were trained by shadowing whoever was available
Built a standardized onboarding program
Average onboarding time went from one month to three days
Customer service resolution was handled manually, case by case
Automated customer service resolution
4 hours of weekly customer service resolution time eliminated
Summary
This engagement removed the business's dependency on its owners. Undocumented processes became standardized SOPs, informal shadowing became a defined onboarding program, and recurring manual work was automated out. The result was an operation that ran on systems rather than on specific people. This made the owners' retirement possible.
The same principle applies to any owner-operated business. A company that depends on a few key people to function is harder to run, harder to scale, and worth less when it comes time to sell or step back. One that runs on documented systems is more stable, easier to grow, and holds its value without the owner in the middle of it.
The same approach applies to any business that can't yet run without its owner. It starts with an audit.