Pieter Levels, known online as levelsio, is one of the most studied indie developers on the internet. He is often cited in “build in public” conversations, but many summaries of his story are either shallow or full of recycled claims with no source.
This article is intentionally fact-based. It focuses on what can be verified from his own published pages and interviews, then translates those facts into practical lessons for founders who want to build profitable products without venture capital.
If you are researching how a solo builder can run multiple internet businesses at once, Levels is still one of the strongest real-world case studies.
Who Is Pieter Levels?
Pieter Levels is a Dutch indie hacker and bootstrapped founder best known for:
- Nomad List
- Remote OK
- Photo AI
- Interior AI
He became widely known after publicly documenting his “12 startups in 12 months” challenge. In a Wired profile, Levels explained that most of those attempts failed, but the process helped him discover ideas that later became meaningful businesses. That framing matters: his story is not “one perfect idea,” but repeated shipping and filtering.
What He Actually Built (With Verifiable Context)
One of the most useful primary sources is the projects section on his own site, where he lists products, start dates, and self-reported annual revenue figures.
Nomad List
According to levels.io, Nomad List started in 2014. In interviews and profiles, Levels describes its early version as very lightweight: initially assembled with simple tools before growing into a full product. Wired also reported that it was profitable on day one, which aligns with his long-standing bootstrap philosophy: start charging quickly, then improve.
In a recent self-reported monthly snapshot, this asset layer (listed there as Nomads.com) was around $15k/month, which helps explain why his community/data products remain strategically important even after the rise of his AI products.
The tactical insight is not “build a massive app first.” It is:
- Find a clear user pain.
- Ship a narrow first version.
- Ask for payment early.
- Expand features only after demand is proven.
Remote OK
Remote OK is listed on levels.io as launched in 2015. It is one of the best examples of compounding within a focused market: global remote work. Instead of treating product and audience as separate projects, Levels built around adjacent user intent. People searching for remote lifestyle insights naturally overlap with people seeking remote jobs.
That durability also shows up in his self-reported monthly numbers: RemoteOK was about $36k/month, a meaningful contribution from a long-running product launched years before the current AI cycle.
That adjacency strategy is a pattern indie developers can copy:
- Build in one niche.
- Reuse distribution in that niche.
- Launch adjacent products that serve the same audience at a different step in their journey.
Photo AI and Interior AI
On levels.io, both products are listed as started in 2022, during the rapid rise of generative AI tools.
In the same self-reported monthly snapshot, PhotoAI was about $102k/month and InteriorAI about $39k/month, indicating that these newer AI products became major revenue drivers in his portfolio. Levelsio.com itself was also listed at roughly $17k/month, showing that his personal distribution layer still monetizes alongside product revenue.
For readers using this site as a directory, the two relevant internal pages are:
- Photo AI for AI-generated photos and avatars.
- Interior AI for AI-powered interior redesign concepts.
The key strategic point is timing plus execution speed. Many people saw the AI wave in 2022. Fewer shipped practical consumer products quickly, then iterated in public with pricing, examples, and user feedback loops.
The Core Operating Model Behind Levels’ Results
When founders discuss Levels, they often focus on revenue screenshots or product names. The more valuable layer is his operating model.
1. Fast Validation Over Perfect Architecture
Levels repeatedly prioritizes market validation over technical perfection in the first version. The Wired profile about Nomad List highlights how minimal his early build was. This mirrors a durable bootstrap rule: if users will not pay for a rough v1, technical polish alone will not solve the business problem.
For indie developers, this means:
- Design your first build around proof of demand.
- Keep initial scope tight enough to launch in days or weeks.
- Delay complex infrastructure until usage justifies the cost.
2. Build in Public as Distribution
“Build in public” is often misunderstood as personal branding content. In Levels’ case, it functions as:
- Continuous user research
- Lightweight marketing
- Trust creation through transparency
- A direct feedback loop for prioritization
Because users can watch product progress in real time, launch-day marketing pressure is lower. Distribution accumulates while the product is being built.
3. Cash Flow Discipline
Levels is a strong example of the bootstrap preference for profitability over vanity metrics. Publicly available interviews and his own project pages emphasize paid products, recurring usage, and sustained operation rather than “growth at all costs.”
This shifts decision quality:
- Features are evaluated by user value and retention impact.
- Hiring remains intentional because fixed costs are real.
- Product scope is constrained by actual economics, not pitch decks.
4. Portfolio Thinking, Not Single-Product Identity
A lot of early founders become emotionally attached to one product identity. Levels has historically treated product work more like a portfolio: ship, test, keep what works, and let weak ideas die.
That does not mean random idea hopping. It means disciplined experimentation with a clear kill/continue framework.
A practical framework inspired by this style:
- Give each new idea a strict validation window.
- Define success metrics before launch.
- Shut down or pause projects that do not hit thresholds.
- Reinvest attention into proven products.
Why His Approach Still Matters in 2026
The tooling landscape is different now. AI coding assistants, template stacks, and API-first services make shipping easier than ever. But easier shipping also means more noise. In this environment, Levels’ approach remains relevant for three reasons.
Reason 1: Execution Speed Is Still a Moat
Ideas are cheap and visible. Execution speed with real users is still scarce. Levels’ history shows that repeated shipping plus public iteration can beat slower, more polished competitors.
Reason 2: Distribution and Product Cannot Be Separated
Many builders still treat marketing as a post-build activity. Levels’ body of work shows the opposite: audience, feedback, and product direction should evolve together from day one.
Reason 3: Profitability Gives Strategic Freedom
Bootstrapped profitability creates optionality. Founders can choose roadmap direction based on users and long-term conviction rather than investor timelines. Levels’ long-running independent path is a practical demonstration of that freedom.
What New Indie Founders Should Copy (And What Not to Copy)
It is tempting to copy surface-level behavior: frequent launches, bold posts, big claims. That is not the useful part. The useful part is system design.
What to Copy
- Ship small and validate paid demand quickly.
- Pick markets where you understand user pain firsthand.
- Build distribution while building product.
- Use portfolio logic: test, measure, prune, and double down.
- Keep business models simple enough to understand cash flow early.
What Not to Copy
- Launching many projects without clear validation criteria.
- Confusing social engagement with product-market fit.
- Ignoring support and reliability once revenue starts.
- Assuming speed alone can replace taste and user empathy.
In short, copy the decision process, not the aesthetics.
A Practical 30-Day Levels-Inspired Plan
If you want to apply these lessons immediately, use this short plan:
Week 1: Problem and Offer
- Choose one painful problem you understand directly.
- Write a one-sentence promise and a paid offer.
- Create a simple landing page with pricing and a waitlist or checkout.
Week 2: MVP and First Users
- Build the smallest working version.
- Onboard 5 to 15 users manually.
- Track one core outcome metric (time saved, output quality, or revenue impact).
Week 3: Public Iteration
- Share progress updates and user learnings publicly.
- Publish before/after examples.
- Improve onboarding friction points first.
Week 4: Decision Gate
- If users pay and retain, continue and deepen.
- If not, either reposition sharply or stop.
- Document what failed so your next launch starts smarter.
This cadence is unglamorous, but it is close to the real mechanics that made Levels’ body of work possible.
Final Takeaway
Pieter Levels is not useful as an internet myth. He is useful as an operating case study.
The verifiable thread across his projects is consistent:
- Start narrow.
- Ship early.
- Charge early.
- Iterate publicly.
- Keep what works.
- Maintain independence through revenue discipline.
For builders in 2026, that remains a high-signal model. Tools have changed, but market truth has not: users pay for outcomes, not ideas. If you focus on outcomes with fast feedback loops, you do not need to look like a startup to build a serious business.