← The collection

Permissionless Leverage.

Split a twelve-hour studio week between service work and a reusable product.

Interactive experimentintuitiveField note ·
Preparing the experiment…
THE SHORT VERSION

Permissionless Leverage, explained.

Permissionless leverage is Naval Ravikant's discussion of scalable code and media output that need not require hiring a new worker for every additional customer. Reusability differs from borrowing to amplify financial exposure.

01 / THE MECHANISM

Why it happens

A reusable product has an upfront creation cost and a lower incremental delivery cost. A larger audience or repeated distribution can spread that cost across more uses. Weak demand, maintenance, and competition can prevent the hoped-for payoff.

Naval Ravikant discusses code and media as forms of leverage that can scale without hiring a worker for every additional customer. Reusable output separates production effort from repeated distribution.

Read the result

Allocate twelve first-week hours, launch, and compare combined net income with an all-service week. Repeat distribution reuses the paid-for product. Change the supplied audience to see how the first build can lose money when too few people use it.

02 / FOLLOW IT THROUGH

A worked example

A reusable tool reaching a supplied audience

  1. Allocate eight build hours and four service hours. Service earns forty and the game's build charge is eighty.

  2. At twenty users, full-quality product revenue is forty and delivery costs two, making first-launch combined net income −2.

  3. Repeat distribution without another build charge. The same small product now adds thirty-eight net tokens per launch, but the audience and low maintenance costs remain assumed.

OPTIONAL DEEPER DETAILGo deeper: inside the model

Inside this model

Service pays 10 tokens per hour. A reusable product costs 10 tokens per build hour; quality rises linearly to full quality at eight hours. Product revenue is users×quality×2 and delivery costs users×0.1. Compare combined first-launch net income with an all-service week; repeat launches reuse the product and omit the already-paid build cost.

03 / BEYOND THE EXPERIMENT

Where this idea is useful

A practical use

A template or software tool can be distributed repeatedly, while a new bespoke service usually needs more delivery time.

CHECK YOUR INTUITION

A common misconception

THE TEMPTING CONCLUSION

“Code or media guarantees passive income.”

THE MORE USEFUL DISTINCTION

Low copying costs do not guarantee demand, distribution, reliability, or profit. The board supplies audiences to isolate scale rather than simulate the difficult process of earning them.

What this explanation leaves out

  • This equation is authored for teaching, not Naval's formula or an income prediction. Audiences are supplied, not earned; demand, competition, maintenance, access, and failure still matter. This is not borrowed-money leverage.
ONE MORE QUESTION

Are these numbers Naval's formula for wealth?

No. They are Modic's original teaching assumptions. The source discusses principles of leverage, while the game makes one narrow production-cost tradeoff explicit.

TAKE THE IDEA WITH YOU

What useful output could you reuse, and what evidence shows that someone actually wants it?

Associated thinkers

Associated withNaval Ravikant ↗

Associations marked provisional are awaiting source review.

Further reading

Explore the original research or the teaching reference behind this experiment.