If your income stops the day you stop working, working harder won't fix it. What's missing is anything that keeps being useful after you've finished making it. The fix is to put some of your hours into things a thousand people can use as easily as one: an article, a template, a small tool, an email sequence, an ebook.
The idea has a name, "permissionless leverage", and it comes from the investor Naval Ravikant. It's a good idea that gets oversold. These assets take real time to build, plenty of them earn little or nothing, and every one of them needs upkeep. This guide covers what counts as a leveraged asset for one person, what each kind costs, and how to pick the first one to build.
Where the idea comes from
In his 2018 thread "How to Get Rich (without getting lucky)", Naval wrote that business leverage comes from capital, people, and "products with no marginal cost of replication (code and media)". He called capital and labor permissioned leverage: someone has to hand you the money or agree to work for you. Then came the line most people remember, that code and media are permissionless leverage, because you can make software and media that work for you while you sleep without asking anyone first.
He expands on it in a short podcast episode on products with no marginal cost, and Eric Jorgenson collected the thread and related interviews in The Almanack of Naval Ravikant, which is free to read online.
Two things the quote doesn't tell you. Only the making is permissionless. Getting found still runs through Google, social platforms and app stores, and they decide who sees your work. And "while you sleep" describes a good week for an asset that's already working. It says nothing about the months before that, or the maintenance after.
What counts as a leveraged asset for a solo operator
The test I'd use: can this serve the next person without me doing the work again? A consulting call fails it. A written answer to the question you get on every consulting call passes.
Here's what that looks like at a one-person scale. The time estimates are rough and depend heavily on your topic and skill.
| Asset | Rough build time | Upkeep |
|---|---|---|
| Article that ranks in search | Hours to a few days | Refresh when facts change or rankings slip |
| Template or checklist | An afternoon to a few days | Low; update when the tools it relies on change |
| Email sequence | A few days | Check links and offers a couple of times a year |
| Ebook or short course | Weeks | New editions, buyer questions, refunds |
| Small tool (calculator, script, plugin) | Days to months | Bug fixes, security and dependency updates, hosting |
If most of your income is client work, you don't have to jump straight to this list. Packaging a service with a fixed scope and price is a halfway step, and the guide to productized services covers how that works.
What leverage costs
You pay first and find out later. A freelancer gets paid within weeks of doing the work. An article can take months to rank, if it ranks at all, and a tool can launch to nobody. That's why I'd build these alongside paid work at first, so one asset failing doesn't touch the rent.
Then there's upkeep, which is the part "passive income" pitches skip. Content decays: prices and product details go out of date, competitors publish something better, and search results shift under you. An article left alone for two years is usually a weaker asset than it was. Code decays in a different way. The libraries it depends on get updated, security holes get found, the platform or API it plugs into changes its rules, and users email you when it breaks.
Upkeep is still far less work than serving every reader or user by hand, which is the whole point. But budget for it. A sensible habit is to put a review date on every asset the day you publish it.
