How Nomad List and Remote OK Validated Niche Boards

Pieter Levels, an independent, self-taught developer widely known for building and publicly documenting a series of bootstrapped products, built Nomad List and later Remote OK following a sequence directly relevant to anyone considering a niche job board: build genuine audience and utility first, using tools simple enough to launch fast, and only introduce paid listings once real traffic and trust already exist. According to his own public, build-in-public accounts — shared extensively on Twitter/X and his personal blog over the years — this audience-first sequencing, not a sophisticated go-to-market plan, was the actual mechanism behind these products' traction.

Quick Answer: Levels built Nomad List first as a simple, useful tool (originally reported as a fast-built ranking of cities for remote workers and digital nomads, evolved from a much simpler initial version), grew a genuine following by sharing the building process publicly, and only later added Remote OK as a companion job board — introducing paid employer listings once real candidate traffic already existed, rather than trying to monetize before an audience was proven.

What Happened: A Timeline From Public Accounts

According to Levels' own frequently shared public account of his early projects, Nomad List began as a much simpler tool than its later, more developed form — reportedly built quickly, in an early version that was closer to a structured spreadsheet or basic ranking than a polished product, focused on ranking cities by cost of living, internet speed, and other factors relevant to remote workers and digital nomads. Rather than a large upfront build, the early emphasis was on getting something real and useful in front of people fast, then iterating based on actual usage.

Levels built a public following largely through consistently sharing his building process, revenue figures, and lessons — a "build in public" approach that itself became a significant driver of his audience and, by extension, of traffic to his products. Remote OK, a job board focused specifically on remote positions, followed as a related but distinct product, benefiting from the audience and credibility Levels had already built through Nomad List and his public presence, rather than starting from zero audience the way a founder without that existing following would have to.

Decision Points: Niche Choice, Aggregation, and Monetization

Niche choice. Rather than building a generic job board, Levels focused specifically on remote-friendly roles and, with Nomad List, specifically on the digital nomad and remote-worker lifestyle — a genuinely underserved niche at the time relative to mainstream job boards and city-ranking resources, which were not designed with this specific population's priorities in mind.

Aggregation before a full platform. Consistent with the general pattern covered in validating a niche job board idea, the early versions of these products relied on straightforward, fast-to-build aggregation and structuring of information rather than a fully custom-built platform with extensive features — getting something real in front of the target audience quickly mattered more than technical sophistication at the start.

Monetization timing. Paid job listings on Remote OK, and any monetization elements added to Nomad List over time, came after genuine audience and traffic already existed — employers paying to post a job listing were buying access to an already-proven, already-trafficked audience, not betting on an unproven new platform, which is a meaningfully easier sale than asking employers to be early adopters of an unproven board with no track record.

What the Validation Framework Says About This Sequence

This sequence maps directly onto the audience-first validation approach covered in validating a niche job board idea: build genuine candidate-side utility and traffic using free, fast-to-launch aggregation, prove that audience is real and returning, and only then approach the employer side of the marketplace with real numbers to show rather than a hypothesis to pitch. The build-in-public element adds a specific, transferable mechanism worth naming explicitly: publicly and consistently sharing the building process itself became a genuine audience-acquisition channel in its own right, distinct from and complementary to the product's core utility — worth considering for any solo founder without an existing large following, since it's a channel that doesn't require significant capital, only consistency and genuine transparency.

Transferable Lessons for Solo Marketplace Founders

Solve the harder, less monetizable side of a two-sided marketplace first. Candidates (or in Nomad List's case, remote-work-curious users generally) are typically easier to attract with free, genuinely useful aggregation than employers are to convince to pay upfront — building real audience density on the harder side first, then approaching the easier-to-monetize side (employers) with real traffic already in hand, reduces the two-sided cold-start problem considerably.

Speed to a real, usable version beats a polished, slow build. The reported pattern across Levels' public accounts of his various projects is consistently favoring fast, simple, real launches over extended private development — a discipline directly transferable to any solo founder tempted to over-build before testing whether an audience actually wants what they're building.

Building in public can be a genuine acquisition channel, not just a transparency exercise. For a solo founder without an existing following, considering some version of public building — sharing progress, decisions, and even struggles openly in a relevant community or platform — can compound into real audience and trust over time, a pattern worth studying even for founders in categories very different from remote work and travel.

A Caution on Replicating an Individual Founder's Specific Path

This case study describes one publicly documented, widely referenced path, and it's worth being direct about a real limitation: much of what's publicly known comes from Levels' own self-reported accounts of his projects, shared through his own channels, which is valuable, genuine signal but not independently audited financial or usage data in the way a public company's disclosures would be. That doesn't make the underlying lessons less useful — the sequencing principle (audience and utility before monetization, speed over polish, solve the harder side of a marketplace first) holds up as sound, generalizable advice regardless of the exact specifics of any one founder's numbers.

What's harder to replicate directly is the specific combination of timing (entering a genuinely underserved niche early), platform-building skill (moving fast enough to test ideas cheaply), and the compounding effect of a public following built over a long, consistent period — a founder starting today, in a more crowded content landscape, following the same general sequence should expect the audience-building phase specifically to take real, sustained effort rather than assuming the exact same trajectory will repeat quickly just because the underlying method is sound.

Key Takeaways

Frequently Asked Questions

Do I need an existing large following to replicate this audience-first approach?

It genuinely helps, since an existing following (built through building in public or other means) accelerates the audience-building phase considerably, but the underlying method — fast, simple, real utility offered to a specific niche, followed by monetization once traffic is proven — doesn't strictly require a pre-existing following; it just takes longer and requires more deliberate, patient channel-building to reach the same audience density without one.

How risky is it to launch a simple, unpolished first version of a marketplace product?

Based on this pattern, less risky than the alternative of over-building before testing real demand — a simple, fast version that gets real usage and feedback teaches you far more, far faster, about whether the underlying idea has genuine traction than a more polished version built in isolation without real user contact.

What specifically made "build in public" work as an acquisition channel here?

Consistency and genuine transparency over an extended period — sharing real progress, real numbers, and real decisions, not just curated wins — appears to be what built genuine trust and following over time, rather than any single viral moment; treat it as a long-term, compounding practice rather than a quick marketing tactic.

Is this audience-first sequence applicable outside of job boards and travel/remote-work content?

Yes — the core sequence (build genuine utility for the harder-to-monetize side of a market first, prove real usage, then approach the easier-to-monetize side with real traffic in hand) generalizes to many two-sided marketplace ideas, not just job boards, provided the specific niche and audience-building channels are adapted to the actual target market rather than copied literally.