I. The Absurdity of the Modern Software Toolchain
In the contemporary tech industry, launching a modern web application has become an exercise in bureaucratic engineering madness.Before writing a single line of business logic that solves a user problem, a modern software team will configure:
* A Next.js frontend running React 19.
* TypeScript compilation pipelines and ESLint configuration files.
* Tailwind CSS utility preprocessors.
* Redux or Zustand state management machines.
* Docker containers, Kubernetes orchestration clusters, and Terraform infrastructure-as-code manifests.
* Microservices connected via GraphQL gateways and AWS Lambda serverless functions.
The team spends four months and hundreds of thousands of dollars before a single customer ever views the landing page.
Pieter Levels looks at this modern software ecosystem and laughs.
Levels is a solitary Dutch developer living out of a carry-on backpack, traveling between Lisbon, Bangkok, and Tokyo. He has raised $0 in venture capital. He employs zero full-time employees. He does not use React. He does not use Docker. He does not use Kubernetes.
His entire tech stack across Nomad List, Remote OK, and Photo AI—which collectively generate over $3,000,000 in annual recurring revenue (ARR) at an estimated 88% net profit margin—is powered by:
* A single file: index.php.
* Raw Vanilla JavaScript and jQuery.
* Plain CSS without build steps.
* Direct SQLite and MySQL databases.
* An unmanaged $40/month Ubuntu virtual private server.
Where an over-engineered team burns months setting up microservices and container clusters before generating a single dollar, Levels launches in three days using vanilla PHP and a $40 server, netting multi-million-dollar cash flows.
II. The 12 Startups in 12 Months Crucible (2014)
Levels did not invent this radical technical minimalism in an academic vacuum; it was forged through the desperation of impending financial liquidation.In 2014, Levels was living in his parents' attic in the Netherlands after his first business—a collaborative electronic music network—ran out of money. He had roughly €1,000 left in his bank account.
Facing the prospect of taking a corporate developer job, Levels made an audacious public declaration on Twitter: He would launch twelve independent startups in twelve consecutive months.
The rule was simple:
* Build the product in under 30 days.
* Launch it publicly to real internet users on Twitter, Product Hunt, and Hacker News.
* Charge real money from day zero.
* If users refused to pay within 30 days, abandon the project immediately and build the next one.
The early months were brutal:
* Month 1: PlayMyInbox (An app that extracted songs from emails) — Generated almost zero traction.
* Month 2: Go Fucking Do It (A motivational accountability platform that charged your credit card if you failed your goals) — Went viral, generating thousands of dollars in fees in 48 hours.
* Month 3: Tubing List (A directory of YouTube channels) — Flatlined.
Then came Month 4: Nomad List.
Levels was traveling in Thailand and wanted a simple way to compare cities based on internet speed, living costs, and weather. He didn't build an app; he created a publicly editable Google Sheet and shared it on Twitter.
Within hours, hundreds of digital nomads were adding data. Seeing the explosive demand, Levels spent a weekend writing a single index.php script that ingested the spreadsheet data, styled it with basic CSS cards, and published it as Nomad List.
It became an immediate global sensation. By Month 12, Nomad List was a multi-million-dollar subscription business, providing the bedrock for Levels' solo empire.
III. The Mechanics of the Vanilla PHP Monolith
Why does Levels fiercely defend vanilla PHP in an era where modern developers mock the language as an outdated relic of the late 1990s?His argument is rooted in pure operational velocity:
"When you use modern frameworks, 70% of your time is spent fixing dependencies, updating broken npm packages, debugging webpack builds, and restructuring state logic. When you write plain PHP and jQuery, you save a file and refresh the browser. It works instantly. The code you write today will still work without modification in fifteen years."
— Pieter LevelsConsider the architectural advantages of Levels' setup: 1. Zero Build Steps: There is no Webpack, Vite, or Babel step. The code that Levels writes is the exact code executed by the server and browser. If a bug occurs on production, Levels opens an SSH terminal, edits the PHP script with nano, saves the file, and the bug is resolved globally in under three seconds. 2. Zero Dependency Rot: Modern Node.js and React applications rot quickly. If you leave a React project untouched for eighteen months, running npm install will unleash hundreds of critical security vulnerabilities and broken API deprecations. Levels has PHP scripts written in 2015 that run today with zero maintenance. 3. Extreme Server Efficiency: A single $40/month Ubuntu VPS running Nginx, PHP-FPM, and MySQL can easily handle tens of thousands of simultaneous requests per minute when properly cached, eliminating the need for complex, expensive cloud architectures on AWS.
IV. The Solo Sovereign Operating Model
The most revolutionary aspect of Levels' business is not merely his technical stack; it is his total rejection of corporate headcount.Levels has proven that a single developer with high technical competence, strong aesthetic design instincts, and an understanding of organic distribution can generate more net profit than a venture-backed startup with eighty employees.
How does a solo founder run three global platforms without burning out?
* Aggressive Script Automation: Any task that must be performed more than twice is automated with a cron job. Levels has hundreds of automated shell scripts running in the background—fetching exchange rates, updating cost-of-living metrics, validating job postings, and charging recurring Stripe subscriptions.
* Customer Support via Software: Instead of hiring a customer support team, Levels treats customer inquiries as product bugs. If ten users ask how to cancel a subscription, he doesn't hire a support agent; he redesigns the cancellation button so it requires zero explanation.
* Public Development as Marketing: Levels doesn't spend money on Google or Meta ads. He tweets his raw revenue metrics, his server crashes, his code snippets, and his feature roadmaps publicly on X (Twitter). This radical transparency turns his audience into invested fans who champion his products organically.
V. Actionable Axioms for Builders
For engineers and aspiring indie hackers trapped in the complexity trap, Levels' journey delivers unambiguous lessons:1. The End User Does Not Care About Your Tech Stack: Customers do not pay for your Kubernetes cluster or your elegant TypeScript types. They pay for a solution to their immediate pain point. If a single index.php file solves the problem, it is infinitely superior to an unfinished Next.js application.
2. Ship in Days, Not Quarters: If your MVP takes more than two weeks to build, you are over-engineering. Strip the feature set down to the absolute bare minimum, launch it publicly, and see if people will pull out their credit cards.
3. Avoid the Hiring Trap: Every employee you hire introduces interpersonal coordination overhead, HR compliance, management friction, and payroll stress. Before you hire human headcount, ask if the problem can be solved permanently with twenty lines of automated code.
4. Build for High Gross Margins: Pure digital software businesses should operate with gross margins exceeding 85%. Avoid businesses with heavy physical logistics or low margins unless you possess a massive capital advantage.
