Alex Hormozi's $7M Roadmap Is Right, and It Skips the Part That Breaks You

Alex Hormozi sat down with Kaleb, a roofing contractor, and handed him a step by step roadmap to a $7 million per year business. Ninety days later Kaleb went from just under $32,000 to $250,000. The advice works. I want to be clear about that before I add anything.

My job is the layer underneath. Every lever in that room raises demand, and not one of them raises the number of roofs that can actually get built this week.

The best asset in the business is also the constraint

Hormozi names the strongest thing about the business early: it is Kaleb. He can knock twenty doors and come back with a deal. That reliability is real and it is rare. But two minutes before that, Kaleb says the thing holding him back is more salespeople. Sit with both of those at once. The owner is the closer, the estimator, the quality check and the escalation path, and the plan is to send him more work. Alex is right about the offer. He is early on the delivery.

Sixty to eighty jobs a month, and one repair tech

Here is where the math stops being abstract. Kaleb went from fifteen to twenty services a month to sixty to eighty. The demand side is solved. Then listen to the very next line: repair techs run three to five jobs per day, and he has one. That is the whole delivery system, one person. One tech at five jobs a day is twenty five jobs a week. Eighty a month is about twenty a week. He is already at the ceiling. Selling more from here does not add roofs, it adds backlog and callbacks.

Finish the door-to-door math

Ten dollars a door is a clean incentive and I genuinely like the mechanic. But finish the arithmetic. Every fifty doors knocked creates one job somebody has to climb up and complete. Four reps knocking two hundred doors a day sell four jobs a day. One repair tech can build five. Add a fifth rep and you are underwater. Nobody in that room asks how many roofs the crew can finish this week. You can pay for doors. Nobody has ever paid a roof to go faster.

A script for the close, nothing for the crew

Front end VSL, back end VSL, a script, a menu close. That is a good list, and every item on it makes more people say yes. Not one item says who delivers the yes, or to what standard. The person answering the phone gets a written script. The crew gets nothing written down at all. I write the repair checklist before I write the close. Same afternoon, opposite order. A close you cannot deliver is just a refund with a longer delay.

He says supply constrained, then waves the fix away

This is the moment. Hormozi says it plainly: the business is supply constrained, meaning more people want the work than there is capacity to do it. That is the definition of a delivery bottleneck, and he names it. Then the whole plan gets summarized as debriefing with the team and putting systems in play. Simple. Very. That is the hardest part of this business, waved off in four seconds. A debrief is a meeting. A system is what survives the meeting. A named owner, a written standard, and a weekly capacity number. That is what simple actually costs.

What actually moved the number

Ninety days later the revenue is real, and Alex earned that. But hear what Kaleb credits when he explains it. He bought an ERP system, and he hired a repair tech. Both of those are delivery. Neither one was on the roadmap. And then the detail that proves the whole point: his only repair tech had meniscus surgery, and his brother filled in on the route. That is not grit. That is a delivery system one person deep, and it held by luck.

Sell the offer, absolutely. Just answer one question before you turn the demand up. You sold it. Who builds it?