Engineering Viral Business Books Through Obsessive Writing & Testing

The table of contents is the hardest part and becomes the entire game plan.

Hormozi spends disproportionate time on the TOC because once it’s locked, the rest is execution. Each chapter follows a fixed structure: story → short definition → plentiful examples → “Alex notes.”

Why: A clear TOC acts as a decision filter; if an idea doesn’t fit, it’s cut, preventing scope creep.

"the table of contents is the hardest thing that I spend my time on. Once I have that, that's like basically the game plan"

Schedule entire days with zero obligations to enter a flow state.

He writes only on calendar days that are completely empty, using earplugs, headphones, and closed windows to avoid the Zeigarnik effect of open loops.

Why: Uninterrupted deep work maximizes words per unit of time and preserves cognitive load for creativity.

"I almost exclusively write on days where I have nothing on my whole calendar"

Test every high-impact variable with ruthless A/B experiments.

He ran 100+ split tests on titles, subtitles, imagery, and even single words like “strangers” vs. “more people,” letting data—not ego—decide.

Why: Book buyers judge in a split second; micro-optimizations compound into massive conversion differences.

"I A-B tested the hell out of this... 71% to 29%, like just one word"

10× effort on quality yields 100-1000× word-of-mouth.

The difference between gold medal and fourth place is tiny in effort but enormous in outcome; the 16th coat of paint makes the asset evergreen.

Why: In a globally connected market, winner-take-all dynamics reward extreme quality with exponential reach.

"if you put in 10 times more work into a book... you end up with 100 or 1,000x the word of mouth"

Pain is the pitch—describe the prospect’s pain better than they can.

Instead of over-promising, he lists hyper-specific moments of pain (e.g., thigh chafing, avoiding photos) to establish credibility and trigger action.

Why: Accurate pain description signals deep understanding, making the promise believable without further persuasion.

"if you can accurately describe a prospect's pain in their own language... you can persuade them to buy"

A good framework must be both valid and useful (MISI).

He applies McKinsey’s MECE (mutually exclusive, collectively exhaustive) test: if one counter-example breaks it, the model is wrong.

Why: Invalid or non-exhaustive frameworks fail under real-world stress, destroying trust and utility.

"if I can think of an example that doesn't fit in this, the model's wrong"

Back-test principles 2,000 years to ensure timeless utility.

Rather than predict the future, he checks if the concept worked in ancient markets (e.g., risk-free, fast, easy offers).

Why: Human behavior constants create evergreen assets that sell for decades without updates.

"does this make sense 2,000 years ago? People still want things to be risk free"

Use socialized feedback as a diagnostic, not a prescription.

If many readers flag the same section, delete or rewrite it; ignore isolated comments. He once cut three core chapters after draft 12.

Why: Clustered feedback reveals structural flaws; fixing symptoms wastes time versus removing the root.

"if many people have different comments about one section... it's more that there's something wrong with the section"