wouldit.work

SaaS

Remote OK: a one-month MVP job board that became a single PHP file making $101,101 in a month

Pieter Levels launched Remote OK in 2015 as a free aggregator of remote jobs, one of his '12 startups in 12 months'. He later sold job posts, raised the price from $1 to $300, and kept it as a tiny one-file PHP app.

Product
Remote OK
Founder
Pieter Levels
Launched
2015-02
Model
Paid job posts plus ads

Published · 2 min read · 4 sources

Key takeaways

  • Remote OK launched in February 2015, reached #1 on Product Hunt with 1,000 upvotes and collected 3,723 email signups.
  • Levels moved from a $1 job post to $200 in 2016 and $300 in 2018, selling close to the same number of jobs.
  • In April 2021 he said the single index.php file was generating $101,101 that month (self-reported).

What it is

Remote OK started as an aggregator that collected remote jobs from other job boards' RSS feeds and APIs into one site, with credit and links back to each source (levels.io). It was one of Pieter Levels' "12 startups in 12 months", each an MVP "built to see if they can get market fit in a month" (levels.io).

Timeline

  • 22 February 2015: Levels submits Remote OK to Product Hunt and Hacker News (levels.io).
  • Launch: it reaches #1 on Product Hunt and becomes the #15 highest-voted product of all time with 1,000 upvotes; 3,723 people sign up for emails, 3.5% of users (levels.io).
  • April 2015: Levels says it would be "unethical" for an aggregator to charge for job posts and plans sponsorships instead (levels.io).
  • About 2015 to 2018: he starts selling job posts at $1, then raises the price to $200 in 2016 and $300 in 2018, "close to the same amount of jobs sold as w/ $1 pricing" (Indie Hackers).
  • May 2019: Nomad List and Remote OK together pass $83,333 a month in revenue, with 11,996 customers, 1 VPS and 0 funding (self-reported) (levels.io).
  • April 2021: "remoteok.io is a single PHP file called 'index.php' generating $101,101 this month", which he broke down as about USD 92k plus USD 9.5k in ads (self-reported) (levels.io).

Why it worked

  • A real discovery problem. Major job boards had no real categories for remote work, and niche boards had few listings (levels.io).
  • Aggregation that helped the sources. Instead of asking him to stop, job boards asked to be indexed and some made custom feeds (levels.io).
  • An existing audience. Levels already had Nomad List and a #nomads chat community of 2,500+ members (levels.io).
  • Pricing up over time. Demand held as he raised prices (Indie Hackers).
  • Tiny costs. "No frameworks. No libraries (except jQuery)" (levels.io).

What to learn

  1. Launch fast and capture emails from day one; Levels added the signup box minutes before leaving for a party (levels.io).
  2. Start pricing low to learn, then test higher prices. Going from $1 to $300 didn't cost him volume (Indie Hackers).
  3. Boring tech is fine if it ships. One PHP file carried a six-figure month (levels.io).

Risks and what didn't work

  • Missed basics at launch. He forgot Google Analytics, so first-day traffic was estimated, and the promised job emails were "a lie" until a month later (levels.io).
  • Normalizing messy data with "loads of if statements and regular expressions" took weeks and "still doesn't get it right always" (levels.io).
  • Self-reported revenue. All revenue figures are posted by the founder (levels.io).
  • Job market cycles. Revenue depends on companies paying to hire, which this article does not have data on beyond 2021.

FAQ

Short answers drawn from the sections above.

What is Remote OK?

Remote OK started as an aggregator that collected remote jobs from other job boards' RSS feeds and APIs into one site, with credit and links back to each source (levels.io). It was one of Pieter Levels' "12 startups in 12 months", each an MVP "built to see if they can get market fit in a month" (levels.io).

Why did Remote OK work?

  • A real discovery problem. Major job boards had no real categories for remote work, and niche boards had few listings (levels.io).
  • Aggregation that helped the sources. Instead of asking him to stop, job boards asked to be indexed and some made custom feeds (levels.io).
  • An existing audience. Levels already had Nomad List and a #nomads chat community of 2,500+ members (levels.io).
  • Pricing up over time. Demand held as he raised prices (Indie Hackers).
  • Tiny costs. "No frameworks. No libraries (except jQuery)" (levels.io).

What can indie builders learn from Remote OK?

  1. Launch fast and capture emails from day one; Levels added the signup box minutes before leaving for a party (levels.io).
  2. Start pricing low to learn, then test higher prices. Going from $1 to $300 didn't cost him volume (Indie Hackers).
  3. Boring tech is fine if it ships. One PHP file carried a six-figure month (levels.io).

What didn't work for Remote OK, and what are the risks?

  • Missed basics at launch. He forgot Google Analytics, so first-day traffic was estimated, and the promised job emails were "a lie" until a month later (levels.io).
  • Normalizing messy data with "loads of if statements and regular expressions" took weeks and "still doesn't get it right always" (levels.io).
  • Self-reported revenue. All revenue figures are posted by the founder (levels.io).
  • Job market cycles. Revenue depends on companies paying to hire, which this article does not have data on beyond 2021.

Sources

Every link cited above, in order of first use.

  1. 1.levels.io (levels.io)
  2. 2.Indie Hackers (indiehackers.com)
  3. 3.levels.io (levels.io)
  4. 4.levels.io (levels.io)

Related case studies

More in SaaS →