← Explore all 41 people

Pieter Levels

Independent software creator and entrepreneur

  • Owned vs rented
  • Tech
  • Creator case
  • Case 20 of 41
  • Record last updated July 27, 2026

The case question

How little infrastructure does one person need to operate products with global reach?

What this case shows

Levels shows that a person can own meaningful software, domains, direct payment relationships, and product decision rights without building a conventional organization. The unresolved question is whether radical founder control creates an institution, or a highly productive practice whose continuity is still concentrated in one operator.

Sourced to public records8 sources (0 independent)Not independently reviewedHow we check

The career in brief

Levels publicly documented building small internet products rapidly, including Nomad List and Remote OK, while keeping teams and infrastructure unusually lean.

Why the case matters

The case makes direct operation unusually legible, while first-person reporting and dependence on software, search, payments, and personal labor still limit what outsiders can verify.

Build · Carry · Control · Continue

Four separate questions. Public visibility alone answers none of them.

Build

What was built

Turning point

The projects converted a visible personal experiment into recurring digital services and communities not tied to an employer.

Carry

What can travel

Test

Ask what continues if the largest outside channel changes its rules.

Control

What can be governed

Open question

What privacy, security, deletion, moderation, data-provenance, and model-risk controls govern Nomad List, Remote OK, Photo AI, and related products?

Continue

What persists if a dependency changes

Open question

What documentation, access control, disaster recovery, delegation, or succession would allow the portfolio to operate if Levels were unavailable?

The tension in this case: here, owned vs rented means which parts of the work are directly controlled and which depend on access supplied by platforms, distributors, retailers, or partners. Look for rights, customer relationships, audience access, data, products, and operating systems.

What happened

  1. March 2014

    Levels publicly committed to launching twelve startups in twelve months, using repeated small releases as a search process rather than beginning with a single scaled company.

    Sources: 01

  2. July–August 2014

    He launched Nomad List from a crowdsourced spreadsheet and used Product Hunt and Hacker News for distribution. He then spun a remote-jobs page into what became Remote OK.

    Sources: 02, 03

  3. 2016–2020

    Levels developed memberships, paid job listings, data products, and automation around Nomad List and Remote OK. His own disclosures report that the products reached more than $1 million in annual revenue while remaining mostly solo-operated.

    Sources: 04, 06, 05

  4. 2020–2021

    Remote-work demand sharply increased job-board revenue, demonstrating both operating leverage and exposure to macroeconomic hiring cycles.

    Sources: 06, 07

  5. 2022–2024

    Levels launched AI products including Interior AI and Photo AI by building on third-party model and cloud infrastructure. Photo AI became another material revenue source according to his public account.

    Sources: 07

  6. August 2024

    In a long-form interview, Levels described the portfolio’s revenue, automation, product failures, platform distribution, minimal staffing, and sharp post-boom decline in Remote OK revenue.

    Sources: 07

  7. 2024–2026

    The portfolio continued as a founder-controlled collection of web products with direct paid transactions and recognizable domains, while remaining dependent on search, social platforms, payment processors, hosting, APIs, model providers, user-supplied data, and Levels’s continued operation.

    Sources: 08, 07

What it may mean, and where the evidence stops

Levels’s case is unusually close to the popular image of an institution of one: he repeatedly converts personal problem selection, software skill, public building, and direct web products into revenue without conventional venture funding or a large permanent staff. Yet small headcount does not mean independence from infrastructure, and founder control does not answer whether the portfolio can continue without its operator.

Evidence that complicates the first reading

  • Most financial, traffic, staffing, and ownership claims are self-reported. Public product pages and interviews verify visible operation, but private accounts, tax records, processor statements, entity records, and audited revenue are not available.
  • The portfolio is not literally produced by one person alone. Users contribute city data and community value; employers supply job inventory; contractors and moderators may contribute; model providers, payment processors, hosts, app stores, search engines, and social platforms supply essential infrastructure.
  • Repeated launches produce useful selection effects but also survivorship bias: the visible winners can obscure discontinued products and the labor invested in unsuccessful experiments.
  • Remote OK’s large revenue decline after the remote-hiring boom is adverse evidence that an automated, owned product can still be highly exposed to an external labor market.
  • AI products increase product velocity while introducing dependencies on model licenses, training data, compute pricing, content and likeness rules, and upstream technical changes.
  • A deliberately lean operating model may maximize autonomy and profit while limiting redundancy, governance, customer support, moderation, security review, and succession capacity.

What remains unknown

  • Which persons or legal entities own each domain, trademark, codebase, database, customer relationship, and payment account?
  • What revenue, expense, refund, tax, and profit figures can be independently corroborated for each product?
  • Which contractors, moderators, data contributors, or service providers perform recurring work, and under what IP and data terms?
  • How dependent is each product on Google search, X, Product Hunt, payment processors, hosting vendors, external APIs, and AI-model providers?
  • What privacy, security, deletion, moderation, data-provenance, and model-risk controls govern Nomad List, Remote OK, Photo AI, and related products?
  • What documentation, access control, disaster recovery, delegation, or succession would allow the portfolio to operate if Levels were unavailable?

Change one dependency

Use a counterfactual to expose the architecture: answer first, then compare your reasoning with the record.

Write a sentence or two before you look at the record. Your answer is kept only in this browser; nothing is sent, scored, or stored on a server.

Read it against another career

Hold the tension constant across different careers, or hold the field constant and inspect a different path. A comparison is useful because it can challenge the first explanation.

Open the full comparison tool →

Sources and their limits

8 sources: 0 independent and 8 other (primary, institutional, subject interviews, self-authored, or republished reports). First-party sources and interviews establish what a person or organization said or announced; they do not independently prove performance, ownership, causation, or impact. This is analysis of a public record and makes no rating of the person.

Each link was checked by hand during the record’s source review; the site does not continuously re-check them. A broken link, or one that does not support its statement, is a defect in the record. Please report it. 1 link leads to a publisher or organization landing page rather than the exact supporting item, so it identifies a research lead rather than a claim-level citation.

  1. Founder announcement of the twelve-startups experimentPrimary source · Pieter Levels · March 1, 2014
  2. First-person account of Nomad List’s initial launch and distributionPrimary source · Pieter Levels · August 16, 2014
  3. First-person account of building the remote job boardPrimary source · Pieter Levels · August 31, 2014
  4. Founder account of product development, monetization, and trafficPrimary source · Pieter Levels · September 22, 2016
  5. Founder presentation on the portfolio’s business modelsPrimary source · Pieter Levels · January 24, 2018
  6. Founder disclosure of revenue, traffic, paid users, concentration, and solo operationPrimary source · Pieter Levels · December 10, 2020
  7. Long-form independently hosted interview transcript covering products, revenue volatility, automation, AI infrastructure, and operating modelSubject interview · Lex Fridman Podcast · August 20, 2024
  8. Current founder-controlled publication and product indexPrimary source · Pieter Levels · Current record

Part of RN Collins, selected work (opens in a new tab)

Turn the lens on your own work

The same four questions (Build, Carry, Control, Continue) apply to any career, including yours.

The I/1 Edit

One sharp idea. New editions arrive by email.

One argument about work, power, and ownership, made concrete through a real case. Sources and tools live on the web edition.