Andrew Thompson

Before the truck

A kid with a computer, a single mom, and no map for what came next.

Andrew grew up in a small Colorado town with a single mother. Around age eleven, a computer opened a door that his surroundings could not. He became consumed by websites and code, left high school at seventeen, and learned to make his own opportunities on the internet. At eighteen, a Google check for roughly $180,000 arrived. By nineteen, he says his websites had generated more than $2 million.

Then came the part most entrepreneurial origin stories edit out. He spent too freely, watched momentum disappear, and lived through a foreclosure and short sale. Later ventures produced another run of money and another education in what revenue cannot fix. Across dozens of websites and at least eighteen startup attempts, there were real wins, expensive failures, and a growing realization: being able to create demand is not the same as building something durable.

The restart

When the venture-backed dream died, a rented box truck became the next move.

Before junk removal, Andrew poured himself into Gypsy, a travel app he believed could become the next chapter. He had raised about $150,000 and was preparing for launch when COVID shut travel down. The product lost its moment almost overnight. At home were two young children, including a newborn, a partner counting on him, and savings moving in the wrong direction.

A friend showed him the junk-removal model. The partnership they discussed never materialized, so Andrew launched alone. The first truck was a rented fourteen-foot box truck with roughly 270,000 miles. Its transmission failed. There was no glamorous launch sequence, only signs, shirts, business cards, lead platforms, Google, Craigslist, and a willingness to answer the phone and do the work. The software engineer who had built digital products was suddenly learning disposal costs, estimates, routing, truck capacity, and what a customer's trust feels like at the front door.

The climb and the cost

The numbers became impressive. The truth underneath them became more useful.

The early progression was fast: roughly $10,000, then $15,000, then months in the $20,000s, followed by a month around $43,000. Andrew pushed paid acquisition hard, added trucks and people, moved off the truck in about six months and off the phones a few months later, and eventually built a three-truck, multi-location operation. Jedi Junk Removal reported about $1.059 million in revenue in 2022.

Andrew also published the math that makes the headline honest. He reported spending roughly $304,000 on advertising that year. Labor, landfill fees, fuel, equipment, repairs, and the cost of scaling took their share. A rough operating-profit calculation looked healthy, but truck purchases and maintenance brought his own take-home closer to barely six figures. The business had a million-dollar year. It did not hand him a million-dollar life.

That distinction is central to how he coaches. He understands why an owner turns up ad spend, why the phone can feel like oxygen, and why a full calendar can still produce a cash problem. He learned to ask a better question than 'How big is the revenue?' The better question is 'What did the machine require from you to create it?'

From chaos to a system

He sold the trucks. He kept the problems worth solving.

The operation forced Andrew to confront the parts of business that code alone cannot solve. Trucks failed. Tools disappeared. Employees needed standards, not wishes. Andrew says a former operations manager caused roughly $10,000 in losses across missing tools and devices plus unauthorized card charges. Each painful episode exposed another place where a process, permission, checklist, number, or accountability loop should have existed.

After two years and four months, Andrew sold Jedi Junk Removal for $225,000. The price was lower than the headline valuation he once imagined, in part because the company had a short tax history and buyers struggled to finance it. He documented the due diligence, broker fees, asset transfer, and closing friction so other owners could build with the exit in mind much earlier than he did.

Then he returned to the craft that had been waiting underneath the whole story. He began building Autopilot around the operating gaps he had lived: fragmented tools, missed calls, disconnected follow-up, scheduling friction, payment workflows, reporting, and the endless copy-and-paste work that steals an owner's attention. Today he teaches from both sides of the screen. He knows what the software should do because he remembers the day the truck broke, the phone kept ringing, and the business still had to move.