About
Time. Space. Trucks. Trust.
RouteContractor.AI is operator-built back-office software for FedEx Ground contractors — payroll, fuel-theft detection, a driver handbook, and more — built by someone who runs the routes, not someone selling to people who do.
It started as the tools I built to run my own operation. The field notes came alongside them, because there is a gap between how the FedEx Ground contracting business actually works and how it gets talked about online.
Most of what you find on YouTube, Facebook groups, and broker websites falls into one of two buckets: cheerleading from people trying to sell you something, or grievance posting from people who got chewed up by the business and want company. Neither bucket helps you make a better decision.
The field notes are the third bucket: candid writing from an active operator, drafted with AI tools and reviewed line by line before it goes live.
Who runs this
Curtis Cox, operator at Cox Logistics Inc.
I run a multi-station FedEx Ground operation out of Oklahoma and Kansas. I live in Houston, Texas.
My background is in physical energy trading. It has more in common with FedEx contracting than most people would guess. In both, the job is to move products from point A to point B in as few moves as possible.
When I first stumbled on a FedEx route for sale on a business brokerage website, I thought it had to be a scam. This is either the most interesting business I could ever hope to own, or it’s a literal scam. So I started researching.
That’s how I found Spencer Patton’s Route Consultant. Spencer had built his businesses into a work of art: a very large FedEx contracting business, a route brokerage, and a consulting practice, all stacked. He ran a weekly webinar that I tuned into without missing one, and a YouTube channel I watched for hours and hours. When I got to the point where I could answer his questions before he did, I figured I was ready.
I went hunting for routes and found a listing in Kansas. The owner was retiring. He had started in the early 2000s with a single truck and built the fleet to over 30. My family is from Kansas, and I’d been going back every year. The broker tried to talk me out of it. He said I should look at routes closer to Houston. Then he mentioned he owned his own FedEx routes in both Oregon and Arizona, and ran them remotely. I called him back the next day, a little insulted. He was a remote owner across two states himself, but he didn’t think I could run a single fleet from Houston?
The Kansas routes were the ones I wanted.
The first stretch as a contractor was humbling. I micromanaged everyone and everything. I told myself I was being a hands-on owner: in touch with every problem, leading from the front, showing the team how much I cared. What I was actually doing was forcing every decision through me, and the operation could only move as fast as I could think. I had become the constraint.
I kept thinking about Spencer. How was he running 100+ trucks AND doing webinars AND consulting? Obviously he wasn’t running the day-to-day himself. The people he had hired were doing the work I was insisting on doing personally.
Delegation requires trust. Real trust, not “I’ll let you do this and then audit you on Tuesday” trust. Trust like “this is yours, here’s what good looks like, come to me when you’re stuck.” Earning that capacity to delegate forces you to understand your own business well enough to teach it, and your people well enough to predict where they’ll struggle. As soon as you stop being the constraint, the operation can grow.
Being a remote owner from Houston hardcodes that discipline. I can’t shoulder-tap a driver about a late stop, and I can’t walk into the station to defuse a BC dispute. Every problem gets handled the way an owner handles problems, not the way a manager-employee would. You’ll see that thesis run through nearly every article on this site.
FedEx is a great customer to contract for. If you read me long enough, you’ll notice I keep coming back to that line. It’s not flattery. It’s the result of working with FedEx personnel across multiple stations and multiple generations of station management, and consistently finding that when I ask for help, they help or they point me where to find help. That’s not a small thing in any vendor relationship, much less one this large.
Why this site exists
A few years into running the business, I noticed I was answering the same questions over and over for new contractors, prospective buyers, and small operators who reached out. Some of those questions had quick answers.
RouteContractor.AI is where I wrote them down once and made them searchable.
The articles are organized around a small number of operator principles that I keep coming back to in my own decision-making:
- Time and space are the only two real constraints. Every other “constraint” you hear about (stops, miles, packages, SPRD) is a function of those two.
- The contractor’s real job is to build an operation that runs without them. Working on the business, not in it.
- Trust is given, not earned. Operations at scale literally require extending trust to people doing the work in your absence. You can’t deliver a FedEx contract’s worth of packages alone.
- Fast pay makes fast friends. Drivers, mechanics, vendors. The opportunity cost of a sidelined truck dwarfs almost any bill you might be slow-paying.
- Good BCs are crucial. The single highest-leverage hire you make.
If those principles resonate, you’ll find a lot here you can use. If they don’t, you probably want a different site.
Why I’m building the tools
I wanted to streamline the operations I do every week. These are high-stakes tasks that must be done correctly, but they can be mind-numbing.
Payroll is a great example. I built a program to run payroll for me automatically. Then I expanded that program to include fuel theft detection, and then added handbook creation and tracking for new hires. At some point I realized I could package this for other contractors, and that it could be as helpful to them as it had been for me.
How the content gets made
Every article on this site is drafted with AI tools and reviewed line by line by an active FedEx Ground operator (me) before it gets published. That review is not a formality. AI-drafted articles routinely get sent back for rewrites when they read like a content marketer rather than an operator, when they recommend the conventional wisdom over the operator-correct answer, or when they miss the nuance that comes from actually having done the thing being described.
“Drafted with AI, reviewed by an active operator” is the production model. It’s how we can publish at a volume that traditional one-operator-one-blog setups can’t match, without giving up the operator credibility that makes the content useful in the first place.
I’ll never claim the content is “AI-powered” or use that phrasing to puff up the brand. AI is a drafting tool, the same way a research assistant or a junior writer would be a drafting tool. The judgment and the operator perspective are mine.
What this site isn’t
- It isn’t legal, tax, or financial advice. I’m an operator, not an attorney or a CPA. For decisions that need professional guidance, hire a professional.
- It isn’t affiliated with FedEx. RouteContractor.AI is an independent publication. FedEx hasn’t reviewed any of this content and doesn’t endorse it.
- It isn’t a place to find routes for sale. I link to brokers as a service to readers, but I’m not brokering routes myself.
- It isn’t a complaints forum. If you want grievance content, there are plenty of Facebook groups for that.
Cox Logistics
Cox Logistics Inc. is my FedEx Ground contracting business. It operates out of multiple FedEx stations in Oklahoma and Kansas.
RouteContractor.AI is currently operated as a service of Cox Logistics Inc.