I/1Institutions
of One
← Explore all 41 people

Owned vs rented

Pieter Levels

Independent software creator and entrepreneur

TechCreator-led workReviewed July 2026Research depth: claim-levelVerification: not yet verified
What this career helps us understand

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

Follow the story, inspect the structure, test a dependency, compare the case, and verify the evidence. This is analysis of a public record—not a rating of the person.

Documentation status: This record has been researched to claim level, meaning each statement is tied to a source. No case on this site has yet completed independent verification review, so treat every statement as sourced reporting rather than a verified finding. See what completion requires →

01 · Understand

The human story—and the structural question

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

The immediate payoff

What this case changes

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.

02 · Trace

The turn that changed the structure

Before

The career depended on the roles, institutions, platforms, or fields described above.

Turning point

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

What changed

The question becomes what Pieter Levels created, what could move with them, what they could govern, and what work, systems, relationships, or authority could persist when an essential dependency changes.

This is a structural chronology, not a résumé. Exact dates and claim-level events appear in the verified public record below when available.

03 · Examine

Build, Carry, Control, Continue

These are four different questions. Public visibility alone does not answer any of them.

Build

What did the person create?

Reputation, methods, relationships, products, teams, companies, public capacity, or a recognizable body of work.

Look for: rights, customer relationships, audience access, data, products, and operating systems.
Carry

What can move with them?

Knowledge, credibility, relationships, proof, or an audience may travel even when data, teams, rights, and budgets do not.

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

What can they govern?

Legal ownership, practical decision rights, access, influence, and visibility are not interchangeable.

The record must establish control; prominence cannot substitute for evidence.
Continue

What work, systems, relationships, or authority could persist when an essential dependency changes?

Examine what remains possible when a role, platform, employer, administration, distributor, founder, or other essential dependency changes.

Unknown where succession, contracts, governance, or operating capacity are private.

The principal interpretation

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.

04 · Test

Change one dependency

Use a counterfactual to expose the architecture. Your answer stays in this browser; nothing is scored or stored.

Thought experiment

Which audience relationships, rights, products, and revenue routes remain?

Visibility can travel while access, data, and distribution remain rented.

Use the record, not intuition: identify what the sources establish, then check the unresolved questions below. This tool does not predict what Pieter Levels will do.

The missing evidence that matters most: How concentrated are revenue and maintenance duties?

05 · Compare

Do not interpret this career alone

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

Same fieldKunal ShahWhat survives when a founder steps from leading his own company into a platform role?Same fieldMo GawdatHow does authority change when an executive identity becomes an independent public voice?Same tensionMrBeast (Jimmy Donaldson)How much of a creator empire is truly owned when its attention still begins on someone else’s platform?
Open the full comparison tool →

06 · Verify

Inspect the evidence and its limits

This record uses 2 linked sources: 1 independent and 1 first-party or institutional. First-party sources establish what a person or organization announced; they do not independently prove performance, ownership, causation, or impact.

  1. Wired: Pieter Levels and the digital-nomad economy · Independent reporting
  2. Levels: Nomad List founder account · First-party or institutional source
What this case establishes

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.

What it cannot yet establish

How concentrated are revenue and maintenance duties?

The question to carry forward

Can a creator build the infrastructure other creators use without becoming another gatekeeper?

Sourced case record

What happened, what it may mean, and where the evidence stops.

Reviewed 2026-07-27 · 8 sources

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: levels-12

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: levels-launch, levels-remote

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: levels-bootstrapping, levels-deviance, levels-startups

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

Sources: levels-deviance, lex-transcript

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: lex-transcript

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: lex-transcript

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: levels-home, lex-transcript

Structural interpretation

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.

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?

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 this case teaches

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.

Sources used in this record

How to read these links: this site does not continuously check that its citations still resolve. Each link was checked by hand when the record was last reviewed. If a link is broken or does not support the statement it is attached to, that is a defect in the record — please report it.

Source-precision warning: 1 inherited link leads to a publisher or organization landing page rather than the exact supporting item. Those links identify a research lead, not claim-level verification.

  1. Founder announcement of the twelve-startups experimentprimary · Pieter Levels · 2014-03-01
  2. First-person account of Nomad List’s initial launch and distributionprimary · Pieter Levels · 2014-08-16
  3. First-person account of building the remote job boardprimary · Pieter Levels · 2014-08-31
  4. Founder account of product development, monetization, and trafficprimary · Pieter Levels · 2016-09-22
  5. Founder presentation on the portfolio’s business modelsprimary · Pieter Levels · 2018-01-24
  6. Founder disclosure of revenue, traffic, paid users, concentration, and solo operationprimary · Pieter Levels · 2020-12-10
  7. Long-form independently hosted interview transcript covering products, revenue volatility, automation, AI infrastructure, and operating modelindependent · Lex Fridman Podcast · 2024-08-20
  8. Current founder-controlled publication and product indexprimary · Pieter Levels · Current record