Most people think the trap is the job.

It is not. The trap is the story you tell yourself about why you cannot leave it.

Daniel Vassallo had the $511,000 salary. The promotions. The respect of every engineer in the room. The clear path to principal engineer and then beyond that. He had everything the system promised you if you worked hard enough and waited long enough.

He left anyway. Not for another job. Not for a funded startup. Not for anything with a guaranteed outcome.

He left because he stopped believing the next year was going to feel different from the last one.

What happened after he left is one of the cleanest demonstrations of what happens when someone with real expertise stops trading that expertise for a salary and starts building small things from it instead.

A book he co-wrote in a few weeks made $140,000. A 100-minute video course he put together in 16 hours made $310,000. A Discord community he built as an afterthought generated over $800,000 in its first two years. In April 2025 he sold that community to Gumroad for $3.6 million.

None of it was a startup. None of it had venture capital. None of it required a team.

Every single thing he built started as a small bet. And the small bets kept compounding.

The Setup

Daniel Vassallo grew up in Malta.

Small island in the Mediterranean. Population around 500,000. The kind of place where your options feel defined by geography before you are old enough to question them.

He got hooked on computers at five years old. Started programming early. Spent his childhood on hardware and magazines and whatever he could afford to keep learning. Dropped out of university in Malta partway through a physics and computer science degree and shifted to a correspondence program through the University of London instead. Took whatever work he could find between studying. Waiting tables. A school lab. Sales for laboratory equipment. QA for a winery.

His first real programming job was part-time at a sports betting company in Malta. Around 2005. He walked in with a fake-it-till-you-make-it approach and found the problem immediately. Their developer had let them down and the team was manually inputting massive amounts of data every day. He automated it. Saved them hours of work before anyone expected him to.

That moment told him something important. The people who make themselves genuinely useful do not have to wait for permission to matter.

In 2010 he joined Amazon. Entry level developer. Building tools for AWS, Amazon's cloud infrastructure division. Within three and a half years he had been promoted twice to senior engineer. The track to principal engineer was essentially guaranteed if he stayed.

He stayed for eight years.

His salary started at $75,000. By his final year it was $511,000. Most of that in Amazon stock, because Amazon caps its cash compensation at $160,000 and pays everything above that in RSUs that vest and land in your account like cash.

$511,000. A family in Seattle. Two small kids, two and four years old. By any reasonable external measure, the story was going well.

The Constraint

Here is the thing about a $511,000 salary at Amazon.

It is not just money. It is a set of decisions that have already been made for you. Where you live. How you spend your days. What problems you work on. Which promotions you pursue. Which meetings you sit in. Which bureaucracies you navigate.

Vassallo was good at all of it. That was part of the problem.

He had been promoted. Respected. Listened to. He was regarded as an expert and a leader in his field. People looked up to him. And none of that was making him want to show up anymore.

He looked at the people above him. The managers. The senior executives. The people on the path he was supposed to want. He did not admire their lives. He did not want to become the version of himself that arrived there.

"I wasn't motivated enough to do another year. Despite getting rewarded repeatedly with promotions, compensation, recognition, and praise."

The motivation problem is not something a promotion fixes. It is something a promotion reveals. Every new level brings more reward and the same emptiness, which means the problem is not the level. The problem is the system.

He had saved approximately five and a half years of living expenses before he left. He is honest about that. The savings made the decision easier. But he has said plainly that he believes he would have left even without them. That if the savings had not existed he would have found a part-time remote arrangement to cover bills while he figured out what came next.

He left Amazon in February 2019.

He left almost a million dollars in unvested stock options on the table when he walked out the door.

The Opportunity

Vassallo did not leave Amazon with a plan.

He left with a direction. And there is a real difference between those two things.

The direction was this. Stay self-employed. Build things from what he already knew. Do not bet everything on one outcome. Keep the downside small enough that a failure does not end the experiment.

His first attempt was Userbase. A SaaS product for developers. End-to-end encrypted user authentication that made it simple for developers to build secure web apps without managing the complexity themselves. Technically interesting. Real problem. He got 1,000 people on the waitlist. Hit number one on Product Hunt on launch day. Made the front page of Hacker News.

And then almost nothing.

The product made around $10,000 a year. Not per month. Per year. For something that launched at the top of every developer platform simultaneously.

A different kind of person doubles down here. Raises money. Hires a team. Runs the playbook. Pushes through because the alternative is admitting that the first bet did not work.

Vassallo did something different. He accepted the evidence. He kept Userbase running as a small side thing and did not let it become the thing that consumed him.

While building Userbase he had been sharing everything on Twitter. The process. The decisions. The numbers. The problems he was hitting and how he was trying to solve them. He was not doing this as a marketing strategy. He was doing it because transparency was the natural way he processed what he was building.

His Twitter following grew. The audience he was building was not fans. It was people who recognised themselves in what he was sharing. Employed engineers. Developers with expertise and a job they were not sure about anymore.

That audience was not a business yet. But it was going to be.

The Playbook

He packaged what he already knew and sold it before he had time to overthink it.

By mid-2019 Vassallo had been building on AWS for over eight years. He knew which services actually mattered and which ones were noise. He knew how to make technical decisions without getting paralysed by optionality. He knew things that took a decade inside Amazon to learn and that most developers outside it were guessing about.

He and his former Amazon colleague Josh Pschorr turned that knowledge into a book. They called it The Good Parts of AWS. 173 pages. A deliberately opinionated take on which AWS services you would be foolish not to use and which ones you could safely ignore. Not a comprehensive reference. A specific, experienced perspective.

They launched it on Gumroad on December 25, 2019, priced at $65.

In the first 14 days it made over $45,000.

Total lifetime revenue crossed $140,000. Over 13,000 copies sold. For roughly 160 hours of work between two people.

The Christmas Day launch was not accidental. Developers are off work. They are online. They have time to read. They are thinking about what they want to do differently next year. The timing was a small deliberate decision that most people would not make because it feels wrong to launch something on a holiday.

Most right decisions feel slightly wrong before you make them.

He built his Twitter audience by sharing the work instead of talking about the work.

Here is what Vassallo did not do on Twitter. He did not post motivational content about entrepreneurship. He did not write threads about how to be successful. He did not build a persona around having escaped corporate life.

He shared what he was actually doing. Revenue numbers. Product decisions. Things that worked and things that failed. The real texture of trying to stay self-employed when you have two small children and you just walked away from $511,000 a year.

That specificity is what built the audience. Not volume. Not consistency for its own sake. Specific, honest, observable detail about a life people wanted to understand.

By the time he launched his Twitter course in April 2020 he had over 24,000 followers. Not tens of millions. Not even hundreds of thousands. But a very specific group of people who had been watching him figure this out in real time and trusted exactly what he would teach.

He made $310,000 from a 100-minute video he recorded in one take.

In April 2020 Vassallo released Everyone Can Build a Twitter Audience on Gumroad. Priced at $25.

He put it together in 16 hours. One take. No editing. No production studio. A screen recording of him talking through exactly what he had done to build his audience from zero to 24,000 followers.

It made $100,000 in the first two months.

Total revenue crossed $310,000. Over 13,000 sales.

Sit with the arithmetic for a moment. $310,000 from 16 hours of work. That is more money per hour than almost any knowledge worker on the planet earns from a salary, including the $511,000 Amazon salary he left behind.

The product did not succeed because it was polished. It succeeded because the person selling it had built the exact thing they were teaching in real time, transparently, in front of the people buying it.

The credibility was already established before the product existed. The product was just the packaging.

He failed at SaaS and accepted it fast enough that it did not cost him everything.

The Userbase story is the one most people skip because it is the uncomfortable part of the Vassallo narrative.

He built a technically sophisticated product. It launched at the top of every relevant platform simultaneously. And it did not work. Not in the way a business needs to work to justify the hours and the focus.

He did not hide this. He shared the numbers publicly. $10,000 a year. Not enough. Moving on.

That transparency did three things. It kept his audience's trust. It freed him to move resources to the things that were actually working. And it became the most concrete possible proof of his core thesis. That the portfolio approach protects you from any single failure. That a SaaS that does not work is just one bet that did not pay off. It does not end the experiment.

He turned a course into a community by accident and it became his biggest bet yet.

In November 2021 Vassallo ran a cohort course. A Portfolio of Small Bets. Six live Zoom sessions over two weeks. Around 30 people per cohort. Teaching exactly what he had learned about building small things from expertise instead of swinging for big outcomes.

He ran 29 cohorts.

As demand kept coming he realised the value was not in the six sessions. It was in what happened between them. The Discord. The community. The members who stayed and kept sharing and building together.

He packaged it differently. Join the community. The course is included. Lifetime access, one-time fee.

Between November 2021 and October 2023 the Small Bets community generated $824,000 in revenue. $600,000 in profit. Over 4,500 members. Growing by word of mouth from people who had built real things and attributed the thinking to what they learned inside the community.

In April 2025 he sold Small Bets to Gumroad for $3.6 million. Cash and options. He kept running it.

The Amazon job paid $511,000 a year and required 8 years to reach.

The Small Bets community made $3.6 million and required approximately four years to build from a cohort course he started as one more small bet.

Tools Used

Gumroad for distribution of every product. No custom checkout. No complex e-commerce setup. The product was the expertise. The platform was chosen for its simplicity.

Twitter as the primary audience-building channel. Not for virality. For transparency. Daily sharing of real decisions and real numbers over years, not weeks.

Discord as the community infrastructure once the cohort course evolved into something people wanted to stay inside of beyond the six sessions.

Zoom for the live cohort sessions. Not a sophisticated platform. The simplest tool that let him teach in real time to a small room.

A word processor and PDF export for the AWS book. No design agency. No publisher. A document saved as a PDF and put on Gumroad for $65.

Screen recording software for the Twitter course. One take. 100 minutes. No editing.

The pattern across every tool Vassallo chose is the same. The minimum amount of infrastructure that lets the expertise reach the buyer without adding complexity he had to manage.

Timeline

2005: First programming job at a sports betting company in Malta. Automates manual data entry. Realises that genuine usefulness does not require permission.

2010: Joins Amazon as an entry-level developer. Builds tools for AWS.

2013: Promoted twice to senior engineer within three and a half years. Compensation growing consistently.

2019, February: Leaves Amazon after eight years. Salary had reached $511,000. Walks away from approximately one million dollars in unvested stock options. Begins building Userbase.

2019, December 25: Launches The Good Parts of AWS on Gumroad with Josh Pschorr. Priced at $65. Over $45,000 in the first 14 days.

2020, April: Launches Everyone Can Build a Twitter Audience on Gumroad. Priced at $25. 16 hours to create. $100,000 in the first two months. $310,000 total.

2021: Userbase acknowledged as a failed bet. Making roughly $10,000 per year. Vassallo pivots focus. Begins freelancing. $220,000 in income that year.

2021, November: Launches the first cohort of A Portfolio of Small Bets. 29 cohorts total.

2022: Small Bets community transitions from cohort course to ongoing community. $720,000 in revenue that year.

2023, November: Small Bets community crosses $824,000 in total revenue since founding. $600,000 profit. Over 4,500 members.

2025, April: Sells Small Bets to Gumroad for $3.6 million. Continues operating it.

Mistakes and Lessons

The Userbase failure is worth examining beyond the surface level conclusion that SaaS is hard.

Vassallo has talked about what went wrong there clearly. The product was technically sophisticated. The launch metrics were strong. But the business model required acquisition, retention, and recurring revenue at scale. It required him to compete in a market where the incumbents had years and resources he did not.

He had picked a big bet disguised as a small one.

Userbase demanded the kind of commitment that SaaS demands. Long development cycles. Customer support infrastructure. Ongoing maintenance. It was not a product he could build in days and let run. It was a product that needed him fully and constantly and still produced $10,000 a year.

The lesson he took from it is the one that became the core of everything he built afterward.

A good bet has limited downside. It requires a small investment of time that you can actually afford to lose. It produces something that can earn money without requiring your constant active management. And it does not require you to be right about a specific large outcome. It just requires you to place enough small bets that one of them catches.

The AWS book took 160 hours across two people. The Twitter course took 16 hours. Both made six figures. The SaaS took years of full commitment. It made $10,000 a year.

He was not smarter when the bets worked. He was betting with a structure that let the wins compound without requiring the failures to be catastrophic.

The second mistake he identifies is waiting too long to believe the numbers.

When the AWS book made $45,000 in 14 days most people would have treated that as luck. He watched it carefully and then built the Twitter course using the same logic. Package specific expertise. Sell it to the audience that has been watching you build. Keep the production simple enough that the downside is 16 hours of your time. Let the market tell you if it was worth doing.

The market told him. He listened.

The Psychology

Three things drove Vassallo that most breakdowns of his story miss.

He optimised for optionality, not outcomes.

He did not leave Amazon to build the next billion-dollar company. He left to remain self-employed. That sounds like a smaller ambition. It is actually a more sophisticated one.

When you are optimising for staying in the game, every decision changes. You do not double down on a failing bet because doubling down might end the experiment. You build in small units so that no single failure can eliminate you. You choose structures that generate income while you sleep so that you are never one bad month away from having to go back.

The $3.6 million exit was not the goal. It was the output of hundreds of small decisions made while optimising for a completely different thing.

He used transparency as his compounding asset.

Every number he shared publicly was a deposit in an account that earned interest over time.

The person who watched Vassallo post about Userbase failing and then saw him launch the AWS book and make $45,000 in two weeks had context no advertisement could create. They had watched him try something real, fail at it, adapt, and try something else. When he put a product out they already trusted the man behind it.

That trust is not something you can manufacture. It is built slowly through honesty about the full picture, not just the wins.

Most people only share the good parts. Vassallo shared the spreadsheet that showed Userbase making $10,000 a year. That honesty is what made the Twitter course worth $310,000.

He understood that randomness is not the enemy. It is the game.

The Small Bets philosophy is not a productivity framework. It is a theory about how outcomes actually work.

Most people believe that if they pick the right idea and execute it with enough effort they will get the outcome they are aiming for. Vassallo decided early that this is not how it works. That there is too much randomness in the world to predict which specific bet will pay off. That the correct response to that randomness is not to make bigger, more confident bets. It is to make more, smaller, better-structured bets.

When the game is random, you win by being in the game longer with more positions. Not by betting everything on one outcome you have convinced yourself you can predict.

That insight is worth sitting with longer than it takes to read it.

The 2026 Builder Translation

Vassallo's story is from 2019. The tools he used are still available. The principles underneath them are even more powerful in 2026 than they were then.

Here is what the same playbook looks like if you started it today.

The expertise you have is more valuable than you think it is.

Vassallo had eight years of AWS experience. He packaged a fraction of it into a 173-page PDF and made $140,000.

You have expertise from your job right now. Domain knowledge that took years to accumulate and that people outside your industry are actively trying to find. The question is not whether you have something worth selling. It is whether you believe it is worth selling. Most people do not. That is why the market for specific, hard-won expertise is not saturated.

Pick one thing you know better than 95% of people who have not done your job. Write it down. That is the first version of your product.

The production bar is lower than it has ever been.

In 2019 Vassallo recorded a 100-minute screen recording in one take and made $310,000 from it.

In 2026 you have AI-assisted writing tools that compress the time from expert knowledge to finished document dramatically. You have short-form video platforms where a 60-second clip can build an audience faster than a year of blog posts. You have platforms that handle payment, delivery, and customer communication for a small percentage fee. The infrastructure that used to take months and a team to build is available to a solo builder in an afternoon.

The 16-hour course is now closer to a 6-hour course. The 160-hour book is now closer to an 80-hour book. The production constraint that once made this feel impossible has almost disappeared. What remains is the expertise. Which you already have.

Building in public on X is the highest-leverage thing you can do before you launch anything.

Vassallo did not have an audience when he left Amazon. He built one by sharing what he was actually doing. By the time he had a product, thousands of people were already invested in whether it would work.

In 2026 X has more people looking for exactly what he was sharing than it did in 2019. The feed moves faster. The competition for attention is higher. But a person sharing real numbers, real decisions, and honest failures in a specific domain still cuts through because that kind of content is still rare.

Start posting before you have a product. Document the expertise. Share the decision-making. Let the audience form around the process. Then the product launch is not a cold start. It is a delivery to people who have been waiting.

Replace the goal with a direction.

This is the one that sounds simple and is genuinely hard.

Vassallo did not leave Amazon to make $3.6 million. He left to stay self-employed. That direction gave him permission to fail at Userbase without it meaning he had failed at the larger project. It gave him permission to try a book and a course and a community course and a Discord without any single one of them having to be the answer.

In 2026 most builder content tells you to define your goal, reverse-engineer the steps, and execute the plan. That is how you build a career inside a company. It is not how the best small builders have built things from nothing.

Pick a direction. Stay self-employed. Keep the experiment running. The specific outcome emerges from the attempts, not the plan.

Modern Opportunity Radar

If this playbook is making you think about what to build, here are three real opportunity spaces that share the same DNA as Vassallo's small bets approach in 2026.

Expertise-as-product in overlooked professional domains.

Vassallo sold AWS knowledge to developers. The same model applies to any professional domain with complexity that takes years to understand from the inside. Logistics. Healthcare operations. Manufacturing supply chains. Regulatory compliance in any industry. The people inside these fields assume their knowledge is too boring or too specific to sell. That assumption is wrong. The more specific the expertise, the smaller the competition and the higher the willingness to pay.

One-take video knowledge products.

The production quality of a one-take video course is no longer a disadvantage. It is increasingly a signal of authenticity. A polished corporate training video feels like a company. A one-take recording of someone who actually did the thing feels like a mentor. The market for the latter is growing and the tools to produce and sell it have never been more accessible to a solo builder.

Community as the product, not the add-on.

Vassallo built his Discord community as an afterthought to a course and it became his most valuable asset. In 2026 the same pattern is available in every professional niche. The people who are building things, struggling with specific problems, and looking for others who understand their situation are on Discord and Slack and Circle right now. A well-curated community around a specific domain of expertise, with real events and real practitioners sharing real experience, is a product with higher retention than any course and higher perceived value than any book.

How You Can Replicate This

You have expertise from your job. Real expertise. The kind that took years to develop and that most people outside your field do not have access to.

Here is the sequence that works.

Write down the single most useful thing someone could know in your domain that they cannot learn from a Google search. The insight that took you years to understand. The mistake everyone in your field makes that you learned to avoid. The framework you use that nobody taught you because you built it from experience.

That is your first product. Not the full system. Not the comprehensive guide. The one thing.

Open a free Gumroad account. Write it down. Make it a PDF. Price it at $29 to $49. Share it on X to however many followers you have, including if that number is small. Let the people who buy it tell you what they want more of.

While you are doing that, post on X about the process. What you know. What you are building. What the numbers look like. Not the highlights. The full picture.

Do this for ninety days before you evaluate whether it is working. Ninety days of one thing at a time. No pivoting at week three because the numbers are small. The numbers are small at week three for everyone.

When something gets a signal, the next bet gets clearer. Vassallo's AWS book told him his audience would pay for specific expertise. The Twitter course told him they would pay for expertise about building the audience itself. Each small bet made the next one more accurate.

You do not need to know what the fifth bet is when you are making the first one. You just need to make the first one small enough that you can afford to find out.

Related Playbooks

The Elston playbook covers how a JP Morgan employee built a web hosting business by finding the specific audience the giants were ignoring. The distribution mechanics are different from Vassallo's but the structure is identical. Pick a specific group of people being failed by what currently exists. Build exactly what they need. Charge before you have finished building it.

The Minecraft playbook covers how Markus Persson used community as a distribution engine. Vassallo did the same thing with Twitter. Different platform, same principle. The people who watched him build in public became the people who bought what he built.

Every playbook in this series starts with the same question. Who has expertise that the market is not currently reaching. And what is the smallest possible way to package that expertise and find out if someone will pay for it.

Premium Insights

Here is the number most retellings of Vassallo's story get wrong.

The Twitter course did not make $310,000 because it had a sophisticated launch strategy. It made $310,000 because of what happened in the two years before anyone bought it.

Vassallo had been posting on Twitter about the Userbase experiment. About the AWS book. About every failed small bet and every successful one. By April 2020 when he posted the Twitter course for sale he had an audience of 24,000 people who had watched him try to stay self-employed in real time for over a year.

Those 24,000 people were not followers in the conventional sense. They were witnesses. They had watched him fail at Userbase and keep going. They had watched him make $45,000 in 14 days from a book. They had watched him share every spreadsheet and every decision with the kind of transparency that most people are too afraid to attempt.

When he released a product about how to build exactly the kind of audience they were already a part of, the purchase was almost a foregone conclusion.

The lesson is not about the product. It is about the two years before the product.

In 2026 you can start building that audience today. Not after you have something to sell. Not after you have figured out what the product is. Now. By sharing what you are actually doing and thinking and learning in whatever domain you understand from the inside.

By the time you have the product, the audience will be waiting. By the time you launch, the trust will already exist. The 16 hours of work will produce $310,000 not because 16 hours of work is worth $310,000. But because the two years of transparency before it were worth every minute.

The second insight is about the word self-employed.

Vassallo has said clearly that he did not leave Amazon to build a bigger thing than Amazon. He left to remain self-employed. That is a completely different optimisation target than the one most entrepreneurial content tells you to aim for.

When your target is self-employment rather than scale, a $140,000 book is a win. A $310,000 course is a win. A SaaS making $10,000 a year is a data point, not a catastrophe. The metric is staying in the game with your autonomy intact.

That reframe changes every decision you make about what to build, how big to let it get, and what success actually means when it arrives.

Most people aim at a number. Vassallo aimed at a life. The number turned out to be $3.6 million but that was never what the bet was about.

Your Move This Week

Open a blank document. Write down the single most valuable thing you know from your job that took you more than a year to fully understand. Not a topic. One specific insight. One framework. One mistake and the correct way to avoid it. Write it down in full. That document is the first version of your first product. Give it a price between $29 and $49. Do not edit it for more than two hours. Put it on Gumroad. Tell ten people. See what happens.

* * *

Vassallo did not leave Amazon because he was brave. He left because he was honest enough to admit that the next promotion was not going to fix the thing that the last one did not fix.

The salary is never the trap. The story you tell yourself about what you would lose by leaving is the trap.

He stopped telling that story in February 2019. What came after is the record.

Before you jump in. Every playbook follows the same structure. The Setup. The Constraint. The Opportunity. The Playbook. Mistakes and Lessons. The Psychology. The 2026 Builder Translation. The Modern Opportunity Radar. How You Can Replicate This. And your move for the week.

We do this because most people only see the $2.5 billion number and stop there. Nobody shows you the evenings in Stockholm. The week it took to build the first version. The 40 people who paid before it was finished. The year where nothing seemed to be moving but something enormous was quietly compounding underneath. That is what this is for.

The Setup

Picture this.

It is 2008. A programmer named Markus Persson is sitting at a desk at a small Swedish game studio called Midasplayer in Stockholm.

His job is to make Flash games. One every couple of months. He builds it. Hands it over. Moves to the next brief. The company will later become King, the studio behind Candy Crush, the one that eventually lists on the New York Stock Exchange for billions. But right now it is just a small office, and Persson is just the guy who finishes the games on time and goes home.

He has been doing this since 2004. Five years. Around 20 to 30 games built and shipped to someone else's roadmap.

He does not hate it. He is genuinely good at it. His bosses are happy. The salary arrives on time.

But here is what nobody tells you about creative people working jobs that do not belong to them.

The instinct does not disappear. It just waits.

Persson had been coding since he was seven. His father brought home a Commodore 128 in Stockholm and he sat down and never really got up again. He wrote his first game at eight. A text adventure. No graphics. Just words and decisions and a kid who could not stop making things from nothing.

That drive runs in the background quietly while he makes Flash games for Midasplayer. It is there at lunch. It is there at 10pm. It never clocks off.

Slowly he starts feeding it. Building small things on the side. His colleague and friend Jakob Porsér is doing the same. The bosses notice. They do not like the attention these side projects are getting. The tension builds.

In 2009, Persson leaves Midasplayer.

He moves to a smaller Stockholm company called jAlbum, a photo sharing platform, as a programmer. The work is lighter. The profile is lower. And nobody there cares what he builds after hours.

He has not quit to start a company. He has not handed in his notice with a plan. He has moved sideways to buy himself the one thing that matters more than anything else at this stage.

Time. And the freedom to use it honestly.

The Constraint

Most people think the job is what holds you back.

Persson's story says something different.

He was not building Minecraft with a team or a budget. He was building it between shifts. During lunch. In the evenings. On weekends. Alone. In Java, because that was the language he already knew. On whatever hours were left after a full working day.

Every single constraint he operated under became a decision that turned out to be exactly right.

He could not spend six months polishing so he shipped fast. He could not run a QA team so he released early and let real players find the problems. He could not afford proper marketing so he had to build something so genuinely interesting that people would tell each other about it without being asked.

The constraints did not limit the product. They shaped it into something the market actually wanted.

And there is something else worth sitting with.

The five years at Midasplayer where he built a game every one to two months taught him something most developers spend careers trying to learn. How to actually finish things. How to make fast decisions under pressure without losing quality. How to ship and move on.

"The most limiting factor was that we were making them so fast. It was kind of intense. We spent one or two months on each game. The thing I learned there was how to actually finish projects, which was very, very valuable."

The day job was the training. The constraint was the curriculum.

He could not have built Minecraft the way he did without those five years of grinding out games under pressure. The boring job gave him the skill that made the exciting thing possible.

Sound familiar?

The Opportunity

Here is how the idea actually happened. And this part matters more than most people realise.

Persson had been working on a personal project called RubyDung. A 3D building game he was experimenting with in his own time. While building it he experimented with a first-person view but thought the blocky graphics looked too rough and abandoned it.

Then he found Infiniminer.

Infiniminer was a brand new indie game built by a developer named Zachary Barth. Block-based. First-person. You mine, you build, you place things. Clean chunky visual style. Immediately understandable. Anyone could sit down and know what they were doing within sixty seconds.

Persson was part of the TIGSource community, an independent game developer forum where he had been reading and posting for years. That is where Infiniminer was being played and discussed.

Then the source code leaked. Barth had not encrypted it. Exploits spread through the community. Barth chose to open source the whole thing and walk away.

The moment Persson saw Infiniminer die, something clicked.

He had also been deep in Dwarf Fortress. A simulation game of almost incomprehensible depth. Entire civilisations generate from scratch. Rivers change course based on underground geology. A fortress develops its own living history. Extraordinary. But the interface was pure ASCII text, looked like a computer error from 1983, and getting started required reading documentation longer than most novels. Most people bounced off it within twenty minutes.

He could see the gap clearly now.

Infiniminer had the visual language and the accessibility. Dwarf Fortress had the depth and the open-ended world. Neither had both. Nobody had built the version that combined them.

He went back to RubyDung. Brought in the first-person view. Brought in the blocks. Added survival and exploration. Called it Cave Game.

He built the first working version over a single weekend in May 2009.

That weekend is where the best-selling video game in human history started.

The lesson here is not about gaming. It is about how to find an idea worth building. He did not invent something from nothing. He saw two things that each had half of what someone needed and asked what would happen if one product had both. That question is sitting inside every category you understand right now.

The Playbook

He posted it before it was ready. Intentionally.

On May 17, 2009, Persson shared the first version of Cave Game on TIGSource. Not to the world. Not to journalists. To a forum of independent game developers who had the context to understand what they were looking at before it had any marketing or polish.

He did not announce a finished product. He shared a prototype and let people respond.

Within hours the thread was alive. Screenshots of things people had built. Suggestions pouring in. Real energy from real people who got it immediately.

He had genuine feedback from real humans the same day he posted. Most builders sit on things for months trying to make them perfect before showing anyone. By then they have made hundreds of decisions in silence. Persson made almost none alone. From the very first day he was building in direct response to real people in real time.

He charged before it was finished and the market told him everything.

On June 13, 2009, Minecraft accepted its first pre-orders at approximately €9.95, around $13 at the time. For an explicitly unfinished game with no tutorial, no proper menu, and a developer most people had never heard of.

Within the first month he had over 1,000 paying customers and more than 20,000 registered players.

Sit with that for a moment. Strangers found an incomplete game on an indie developer forum and opened their wallets. That is not a small signal. That is proof. The market confirming the idea is real before you have spent a year finishing it.

Most people wait for the finished thing before charging anything. By then they have lost the most important signal available. Persson had it in the first four weeks.

He released no instructions. On purpose.

No tutorial. No guide. No onboarding flow. No explanation of how anything worked.

Without instructions, players had to figure it out together. They went to forums. They made YouTube videos. They wrote guides and wikis. They formed entire communities around the shared experience of discovering what the game could do.

And Persson fed that loop constantly. New features based on what he was reading and hearing. Things players asked for on Tuesday appearing in the game by Friday. That speed built something no marketing budget can manufacture. Players felt ownership. They were not just users. They were participants in something being built live.

When you are part of building something, you do not just use it. You tell everyone you know about it.

His players became his entire distribution engine. Without him designing it. Just by listening and responding faster than anyone expected.

He stayed employed until leaving became the obvious conclusion.

While Minecraft was growing, Persson still had a job.

He moved from full-time to part-time at jAlbum as sales increased. He did not quit on excitement or conviction. He watched the numbers, kept shipping, and waited for the mathematics to become undeniable.

On June 30, 2010, the Alpha released. Sales did not just increase. They accelerated past the point where his payment processor could handle it quietly. PayPal froze his account because the incoming transaction volume flagged as fraud. A part-time programmer at a Stockholm photo sharing company was not supposed to have that kind of money moving through a personal account.

He left jAlbum later that year. Not as a leap of faith. As an obvious conclusion to a simple arithmetic problem.

He turned down Valve and said no to venture capital.

In September 2010, Persson visited Valve Corporation in Bellevue, Washington. Met Gabe Newell. Participated in their technical exercises. Valve wanted him on the team.

He turned them down.

He also turned down venture capital. Mojang was built on revenue from the beginning. No external debt. No investors in the room. No board telling Minecraft what it needed to become.

The willingness to say no to genuinely great alternatives in order to protect the specific thing you are building is one of the most consequential skills in this entire story. Most people cannot do it. The offer feels too good. The validation feels too real.

Persson said no. Four years later Microsoft paid $2.5 billion for what he refused to give away.

He built the company around what he actually was.

When Mojang was formally founded in 2010 with Jakob Porsér and Carl Manneh, Persson understood something clearly about himself.

He was a builder. Not a CEO. Not an operator. Not a manager. Carl Manneh, a former colleague from jAlbum, came in as CEO. That decision protected the thing that had made Minecraft what it was. Persson's time and energy went to building. Not to managing.

By January 2011, Mojang had one million registered accounts. By November 2011, the official release at MineCon in Las Vegas with 4,500 attendees, the game had already sold over four million copies before launch day.

Four million copies sold before the product was officially finished.

Tools Used

Java programming language. Not because it was optimal. Because it was what he already knew. He did not wait to learn something better. He built with what he had.

TIGSource forums for the initial post and early community. A specific room full of people with the context to understand the idea before it had any polish.

The Word of Notch, his personal development blog on Tumblr. Daily posts. Screenshots. Problems he was working through. New features in progress. Not a content strategy. A habit of transparency that built trust at scale over time.

YouTube, where players made videos nobody asked them to make. The absence of official instructions created a vacuum the internet filled voluntarily and enthusiastically.

Reddit and independent gaming communities where word spread without any coordination. No ad spend. No PR firm. No launch campaign. Player to player. Community to community.

Timeline

2004: Joins Midasplayer. Builds around 20 to 30 Flash games over five years. Learns how to finish things fast under real pressure.

2009: Tension with management over side projects. Leaves for jAlbum. Drops to part-time to free up evenings.

May 16 to 17, 2009: Builds the first version of Cave Game over a single weekend. Posts publicly on TIGSource on May 17. Immediate community response.

June 13, 2009: First pre-orders open at approximately €9.95. Over 1,000 paying customers and 20,000 registered players within the first month.

2009 to mid-2010: Continuous updates driven by community feedback. YouTube videos made by players reach audiences Persson never targeted. Word spreads organically. 20,000 downloads across the entire first year.

June 30, 2010: Alpha releases. Sales accelerate dramatically. PayPal freezes his account. Persson leaves jAlbum. Mojang formally founded.

September 2010: Visits Valve headquarters. Turns down the job offer.

January 2011: One million registered accounts.

November 18, 2011: Official full release at MineCon in Las Vegas. 4,500 attendees. Four million copies already sold.

April 2011: Persson estimates Minecraft had made approximately €23 million in revenue by this point.

June 2014: Posts on Twitter. "Anyone want to buy my share of Mojang so I can move on with my life?"

September 15, 2014: Microsoft acquires Mojang for $2.5 billion. Persson is 35.

2023: Minecraft surpasses 300 million copies sold. The best-selling video game in human history.

Mistakes and Lessons

The mistake Persson made was not in the building. It was in not understanding what would come after.

Microsoft paid $2.5 billion. He bought a home in Beverly Hills for $70 million. He had more money than he could spend in ten lifetimes.

Within a year he was posting publicly about depression and isolation.

He wrote it plainly himself.

"I love games and I love to program, but I don't make games with the intention of them becoming huge hits, and I don't try to change the world. I've become a symbol. I don't want to be a symbol, responsible for something huge that I don't understand, that I don't want to work on."

He had spent his life building things. That was the substance of his days. The problem to solve. The forward motion. The quiet satisfaction of shipping something real. When the company sold, the building stopped. What was left was the noise.

The lesson is not that he was wrong to sell. He was burning out under the weight of what Minecraft had become. The scale was real. The exhaustion was real.

The lesson is about knowing what you are actually optimising for before you start building.

If the work itself is what makes your days feel real, protect the work. Design the business to keep you close to it. Not around the most impressive exit number available. Because when you reach the number, the work will already be gone and the number will not replace it.

Know that before you start. Not after you arrive.

The Psychology

Three things made Minecraft spread the way it did. All three are patterns you can build into whatever you are working on right now.

The blank canvas activates something no scripted experience can.

Every game in 2009 gave players a story, a mission, a correct way to win. Minecraft gave them nothing except a world and the ability to change it. No instructions meant no wrong answers. Players filled that space with their own imagination and what they created felt like theirs in a way no narrative game can replicate.

When people make something inside your product, they stop being users. They become creators. Creators do not churn. They recruit everyone they know.

Uncertainty is more addictive than guaranteed outcomes.

Every Minecraft session is different. Every cave system is unknown. Every world generates from scratch. You never know what the next ten minutes will produce. That unpredictability is not a design flaw. It is the engine that keeps people there.

The brain does not attach to things that always give the same result. It attaches to things that might surprise it. Persson built this loop into the game without designing it as a retention strategy. He was just building the world he personally wanted to explore.

Community turns a product into an identity.

The players around Minecraft did not just play it. They made it part of who they were. YouTube channels. Dedicated servers with their own economies. Schools using it as a teaching tool. Families playing across generations.

You do not cancel your relationship with something that is part of how you see yourself. The retention Minecraft had was never mechanical. It was psychological. And that kind of retention cannot be purchased. It has to be earned by building something genuinely worth caring about.

The 2026 Builder Translation

Minecraft's success was not about gaming. It was about a set of principles that work in any market in any year.

The tools Persson used in 2009 are different from what you have access to today. But the principles underneath them are identical. Here is what the same playbook looks like if someone started it in 2026.

Building in public.

Persson used TIGSource forums and a Tumblr blog. Today you would use X, YouTube devlogs, or a public build thread on a relevant subreddit. The principle is the same. Show the work before it is ready. Let the right people find it early and shape it with you. The platform changes. The transparency is what builds the trust.

Prototyping faster than feels responsible.

Persson wrote Java by hand in 2009. Today you have AI-assisted coding tools that can compress the time from idea to working prototype dramatically. A solo builder in 2026 with Claude or Cursor can build in days what would have taken Persson weeks. The constraint of time still matters. The tools to work within it are radically more powerful.

Community as the distribution engine.

Minecraft spread through YouTube videos players made without being asked, through forums they built without Persson managing them, through wikis they wrote without any official guidance. Today this same pattern plays out on TikTok through gameplay clips, on Twitch through live streams, on Discord through community servers that form around products with genuine depth. The channel is different. The mechanism is identical. Build something people can play with, not just consume, and they will spread it for you.

The freemium loop.

Persson charged €9.95 for an alpha. He gave just enough free to create demand and charged for the deeper experience. In 2026 this looks like a free tier that demonstrates real value and a paid tier that delivers the full depth. The tools to build this, Gumroad, Stripe, Lemon Squeezy, are all available to a solo builder with no team and no funding.

The creator platform advantage.

Persson had no platform when he started. He built one from scratch through forums and blog posts. In 2026 you can launch into an existing platform that already has millions of people looking for things worth their attention. X, YouTube, TikTok, LinkedIn. The distribution infrastructure that took Persson years to build from nothing is available to you before you build your first version. Use it before you launch, not after.

What Persson would do differently in 2026.

He would probably not start with Java. He would use whatever tool let him test the idea in the shortest possible time, including AI-assisted development, no-code game engines, or rapid prototyping platforms. He would post the prototype on X and YouTube the same day it was playable. He would build the Discord community before the product was finished. He would charge for early access inside the first two weeks. And he would say no to the Valve job offer even faster, because in 2026 the tools available to a solo builder have made independence more viable than it has ever been.

The game has changed. The principles have not.

Modern Opportunity Radar

If this playbook is making you think about what to build, here are three real opportunity spaces that share the same DNA as Minecraft's early growth in 2026.

AI-native creative tools with community depth.

The market is flooded with AI tools that generate things for you. The gap is AI tools that let you make things, where the output is yours, where the creative act is yours, where you can share what you made with a community that cares. That blank canvas principle Persson used is almost completely missing from AI products right now. The builder who creates an AI tool where the user is the creator, not the consumer, is sitting on the same kind of gap Persson saw in 2009.

Community-owned game economies and modding platforms.

Minecraft's most durable community came from players who could modify and extend the game. Modding communities created entire sub-industries. In 2026, creator-owned gaming platforms and games built explicitly for community extension are an enormous and underserved space. The founders of the next Minecraft are probably thinking about the modding layer first, not last.

Niche simulation tools for specific professional communities.

Dwarf Fortress had extraordinary depth for a specific kind of player. That model applies to professional communities. A simulation tool built with real depth for architects, urban planners, logistics managers, financial analysts, where the interface is actually accessible, where community can form around what people build inside it, is sitting in the same gap Persson identified between Dwarf Fortress and Infiniminer. The gap between deep and accessible is everywhere if you look for it.

How You Can Replicate This

You have a day job right now. That is not a problem. For Persson it was the training ground and the runway simultaneously.

Here is what you can actually do with what this story contains.

Find the gap between two incomplete things. Go into any category you spend real time in and look for the product that has the right audience but frustrates them, and the one that has the right functionality but nobody can actually access it properly. The version that combines both is your idea.

Post the first version to the smallest room that will understand it. Not the world. The specific community of people most likely to get it before it has any polish. Every industry has one. A subreddit, a Discord, a Slack community, a niche forum. Show them the rough version first and let their response tell you whether the idea is real.

Charge before it is finished. Not to make money but to get evidence. If people will not pay for an incomplete version, they were probably not going to pay for the finished one either. Find out early.

Leave deliberate gaps. The places where your product is silent are invitations. When people have to figure things out together they talk to each other. When they talk to each other the word spreads without you running a single ad.

Stay in the job until the revenue makes leaving obvious. Not until you feel ready. Until the money from your evenings makes your salary arithmetically irrelevant. That moment comes faster than you think when you are building something people genuinely want.

Related Playbooks

The Tiiny Host playbook covers how Elston built a real business inside one of the most crowded markets on the internet by finding the exact audience the giants were ignoring. The distribution mechanics run parallel to what Persson did with Minecraft's community. One ignored non-technical website owners. The other ignored players who wanted depth without a manual. Same principle. Different market.

Both stories start with the same question. Not what should I build but who is being failed by everything that already exists.

Premium Insights

Here is the detail that gets skipped in every surface-level version of this story.

Minecraft had no publisher. No commercial advertising. Not one paid ad across its entire rise from a TIGSource forum post to the best-selling video game in human history. By the November 2011 official release it had already sold over four million copies. Every single one through word of mouth, community, and organic distribution built by players who cared more about telling people about Minecraft than any marketing team could have.

That outcome was not designed. But it was enabled by specific product decisions.

No instructions created the need for community. Community created the content. Content created the distribution. Distribution created the sales. The sales created the company. Every step in that chain was the direct result of decisions Persson made about the product itself. Not about the marketing around it.

The best distribution strategy is not a channel. It is a product people cannot help talking about because using it makes them want to show other people what they made inside it.

The second premium insight is about the compounding nobody talks about.

At 20,000 downloads in the first year, Minecraft looked like an interesting indie project. Nothing more. The growth was invisible from outside the community. Most people who heard about it in 2009 assumed it was a niche thing for developer types.

Then the Alpha released in June 2010 and the 20,000 per year number became 20,000 per day almost overnight.

That is not a different trajectory. That is the same trajectory reaching the compounding stage. The community Persson had been building for a year, the YouTube ecosystem that had formed without his management, the word of mouth chain that had been running quietly since the first TIGSource post, all of it hit a threshold at the same moment and the growth stopped being linear.

Most builders quit before that threshold. The work looks the same from the outside whether you are three months from compounding or three years from it. The only thing that carries you through is genuine belief in the idea and evidence from real users that the thing is working even when the numbers do not show it yet.

Forty people paying €9.95 in the first weekend was that evidence for Persson. He held on because of it.

Every builder needs their version of that evidence. Go find yours before you need it to keep going.

* * *

Persson did not win because he was the most talented developer in Stockholm. He won because he saw what two incomplete things were each missing, built the version that had both, shipped it the same week he finished it, and trusted the community that showed up to do what communities always do when something is genuinely worth caring about.

The gap was always there. He just looked.

Before you jump in. Every playbook follows the same structure. The Setup. The Business Model. The Distribution. The First Sale. What You Can Apply. And your move for the week.

We do this because most people only ever see the highlight reel. The revenue numbers. The success story. Nobody shows you how it actually happened. That is what this is for.

The Setup

Elston was working at JP Morgan. He planned to stay six months. Four years later he was still there. Restless. Building on the side. Trying to find a way out.

Sound familiar?

This is where most of you are right now. Stuck in a 9 to 5, not realising how much time you actually have to build something. In 2026 it has never been easier to start. The tools exist. The platforms exist. The only thing missing is the decision.

Now here is where it gets interesting.

Elston did not pick a fresh untouched market. He chose one of the most competitive on the internet. Web hosting. Dominated by GoDaddy, Bluehost, Namecheap. Companies spending millions on marketing alone.

Most people would run from that. But a crowded market is a signal. It means the idea is already validated. People are already paying. The demand is proven. You are not guessing.

I validate ideas in an evening. I will show you exactly how in a later issue. But the lesson here is this. Before you build anything, validate. That is step one. Always.

"If you take something that already exists, make it better, make it more legitimate. You have got a winner on your hands."

Everyone told him the space was done. No room for a solo developer with no budget and no audience.

He did not try to beat the giants. He found the people the giants were ignoring.

That is exactly what you should do too.

The Business Model

Who was being ignored? Non technical people. Designers. Students. Restaurant owners. Real estate agents. People who just needed a website live without reading three pages of documentation.

Simple idea. Yes. But simple is not the same as easy. And simple is not the same as stupid.

The best ideas are usually the ones that make you think: why has nobody done this properly yet.

Tiiny Host did one thing. You drag. You drop. Your site is live. No panels. No jargon. No complexity. A website up in minutes for someone who has no idea what FTP means.

The model was not new. Hosting existed everywhere. What was new was who he built it for. That gap, the non technical audience, was sitting wide open. Nobody was talking to them properly. That is the whole game sometimes.

Find who is being ignored. Build the simpler version for them. Speak their language.

Now here is where it gets clever.

He added a free plan. Not because free users make money. Because every website hosted on Tiiny Host had a small powered by Tiiny Host link at the bottom. Every site became a billboard. Every user became part of the distribution.

That is a viral loop built into the product itself. Your product spreading on its own every time someone uses it.

Most builders never think about this. How does your product spread when nobody is watching? If you do not have an answer to that question, you are doing all the marketing yourself forever.

We will go deeper into pricing and monetisation models in later issues. For now just note this. Elston thought about distribution before he thought about revenue. That order matters.

The Distribution

This is the part most people skip entirely.

They build. They launch. They wait. Nothing happens. Then they blame the product.

The product was usually fine. The distribution was missing.

You need to be thinking about distribution before you have an MVP. We do not want crickets at launch. We want people already waiting.

Elston did not launch with a splash. He started with SEO.

SEO is a long game. It will not work in 30 days. But in 6 to 12 months, if you do it consistently, it compounds into something nobody can take from you. More on this in later issues.

He targeted low competition keywords. How to share a PDF as a link. How to host a website without coding. Small searches. Real intent. Real people already looking for exactly what he built.

Then YouTube. Not polished studio videos. Just screen recordings. Short tutorials answering the exact questions his customers were typing into Google. One video on sharing PDFs as links. Thousands of views. Still bringing in users years later. Made once. Works forever.

That is how powerful the right distribution channel can be.

There are many distribution channels available to you. SEO, YouTube, X, Reddit, TikTok, LinkedIn, newsletters, communities, podcasts, partnerships. You do not need all of them. You need to find one that works for your audience and then go deep on it.

Elston found Reddit. He did not spam. He showed up honestly. Told the story of what he built. Asked for feedback. Gave early users a discount code as a thank you.

Note that. Discounts for early users. Transparency about what you are building. Asking for feedback instead of just selling. That combination works every single time.

20.6 million Google impressions in 12 months. No marketing agency. No ad spend. Just SEO, YouTube, and showing up honestly in the right places.

Building the product is 20% of the work. What Elston did here is the other 80%. This is what every issue of The Real How is going to cover. Not just the idea. The full machine.

The First Sale

He lowered his prices until people started paying.

That is it. That was the strategy.

Not because you should always lower your prices. But because getting that first sale matters more than margin at the start. The first sale is proof. Proof that someone values what you built enough to give you money for it.

He ran a lifetime deal. Made $1,000 in a couple of days.

That money was not the point. The proof was.

Once revenue starts coming in it must never stop. That is a mindset shift. From builder to operator. You stop asking will anyone pay and start asking how do I keep people paying. We will cover retention and sustainment in later issues.

For a year the MRR was low. But the feedback was good. Users were praising it constantly. He held on.

Then the compounding kicked in. SEO started working. Word of mouth spread. The business found its rhythm.

The year where nothing looks impressive from the outside but something real is building underneath. Most people quit here. Elston did not.

This is the part nobody talks about honestly. Success is usually a lot of quiet, invisible work before it becomes a visible number.

What You Can Apply

You do not need a new idea. You need a better version for a more specific person.

Find any product with bad reviews. Read those reviews. The most common complaint is your product. Rebuild it simpler, cleaner, for the niche the big players are ignoring.

Start marketing before you are ready. Every week you wait is a week your SEO is not running. Every week you wait is a week someone else is showing up in those communities.

Build a viral loop into your product before launch. How does using your product naturally spread the word about it? Answer that question early.

And get that first sale fast. Not to get rich. To get proof.

Your Move this Week

Go to G2 or Trustpilot. Pick any software category that interests you. Read the one star reviews for 20 minutes. Write down the three most common complaints. That list is your next business idea. Takes 20 minutes. Saves you months.

* * *

Elston did not win because he was the best developer in the room. He won because he understood exactly who was being ignored and then showed up for them consistently.

Simple product. Specific audience. Patient distribution. That is the whole game.