Comment by jcox06

Comment by jcox06

I actively look for interesting companies to write case studies on and spent the last week going through everything public on Plenty of Fish (the dating site). Here are the biggest takeaways that I thought I would share with y’all.

The Numbers

12 years from idea to exit.

No outside capital raised

2.8 billion page views per month.

Over 100 million registered accounts at sale.

75 staff at the time of the sale.

Approximately $100 million (est) revenue per year at sale.

Sold for $575 million to Match Group in 2015.

Lessons

1. He wasn’t trying to start a company.

In 2003, Plenty of Fish founder Markus Frind was unemployed after the dot-com crash and wanted Microsoft’s ASP.NET on his resume. Instead of saying he knew how it worked, he figured why not just build something instead.

It was built in just two weeks with his development expertise and published as a free site (since it wasn’t to start a business). He posted the site to dating forums where people often complained about the sign up fees charged by other sites at the time.

2. Free was the competitive advantage.

Match and eHarmony charged up front before a user could even start to use their site, meaning the funnel failed at step 1. Those who didn’t want to pay automatically were pulled to Plenty of Fish. So really, his competitors were his acquisition strategy because his positioning was free instead of paid for essentially the same services.

Just a few months after introducing the site, Google introduced AdSense which was ultimately what allowed the site to cash flow.

Revenue grew from $1k the first month to over $200k in January 2005 just 18 months after launch. When the monthly revenue hit $4k in October 2003, Markus stopped looking for work.

3. He worked solo for much longer than others I have studied.

From idea in 2003 to 2008 when the site was driving $10 million in annual revenue, Markus ran everything himself. He then hired very slowly and those he did hire were expected to be jacks of all trades.

The interesting thing about Markus was the remarkable understanding of cost. Most other founders I have written about see headcount as growth rather than a quick route to bankruptcy if growth stagnates. Markus solely focused on the revenue per employee.

4. A bias towards action.

Markus has always been a proponent of taking action. He has publicly stated that he would rather try something and fail rather than read a book because the feedback loop is shorter and much more effective for retaining information. Action first, then problem solve for a solution.

5. Leverage a growing company

Markus turned down many offers from Match Group over the years (sometimes they also declined because prices he quoted were often more than 10x annual revenue). He wasn’t holding out for a better price so much as he had no reason to sell. It was just him with nobody to answer to and a company that paid him handsomely each month.

The thing I love most is how he treated doubters. When people called him a liar online when he claimed to be running a free online dating site and making seven figures per year, he uploaded a Google AdSense check for over $900k. Probably the biggest flex IMO.

6. Ruthlessly omit everything not linked to growth

The other thing I found inherently fascinating was the obsession with narrowing the field of view around growth. Markus was famous for working one hour per day. He would walk into his office around noon, walk around and then go home to play video games. What a legend.

In interviews he has said that he focuses on four or five things per year that really move the needle and omits everything else. Being a solo founder and nobody to answer to seriously cut down the time that would otherwise occupy a founder and he didn’t fill it with busywork.

A lesson for some of us workaholics out there.

Replies jcox06 · 2026-09-15
Open on HN
Loading the discussion…

Domain filters

Stories from these domains are hidden from every list. Subdomains match too: blocking substack.com also hides danluu.substack.com. Type a domain, or paste a link to block its site, and press Enter.

New collection

Delete this collection?

About YAVCHN

YAVCHN is a reader for Hacker News and Lobsters, with articles and discussions in separate windows or Classic pages.

Created by Paul Parks and built with PUDL.

YAVCHN source code on GitHub

Privacy policy · Terms of use

Help

Keyboard

j / k
Move down and up the story list. The arrow keys scroll whatever has focus.
Enter
Read the marked story in the article reader.
[ / ]
Read the story above or below in the list, in the same article reader. Back returns to the story you came from.
p
Pin or unpin the marked story, which keeps it in Pinned.
n / N
Move to the next or previous top-level comment in the window in front.
c
Collapse or expand that comment.
f
Hide or show the story list.
Esc
Close a menu or this help.
Access key m
Go to the menu bar. Most browsers take it with Alt on Windows and Linux, and Safari with Control and Option.
?
Show this help.

Windows

Each story opens in a window holding its article above its discussion; drag the bar between them to share the room differently. A window can be moved by its title bar, resized from any edge, snapped to a half or a corner by dragging it there, maximised, or minimised to the bar at the foot of the page. Use Window > New reader window to open an empty reader, or Story > Open in new reader window to open another reader for the current article. Docked readers keep their articles when you select another story from the sidebar. Minimized readers can be restored and reused for their site. A window's Previous and Next buttons read up and down the list in the same window.

A link in a comment or an article to another Hacker News or Lobsters thread opens that thread in a window too. A link to a single HN comment opens the comment above its replies.

While a story's window is in front, the Story and Discussion menus in the menu bar hold its commands: pinning, Previous and Next story, sorting, collapsing every thread, jumping to the first new comment. Each window also remembers where you were in its article and discussion, so a reload, or Back to a story that Next took you past, finds your place again. Closing a window forgets it.

The whole arrangement lives in the address, so a bookmark or a shared link brings it back, and Back undoes the last change. Moving between Hacker News, Lobsters, their lists, Pinned and Find changes only the list, and leaves the windows open.

The list

The pin at the start of a row keeps the story in Pinned, and the cross at its end hides it. Pinned can be narrowed by words in the title, site or author, by source, and to the stories you haven't opened yet, and ordered by when you pinned them, by points or by comments; the filters are part of the address, so a filtered view can be bookmarked. Scroll past the end of the list to load more. Domain filters, in the View menu, hide every story from a site.

Collections are named lists of stories. Story > Add to collection files the story in front into one or more of them, and the Collections feed shows them all or one at a time; the menu that chooses collections also creates, renames, and deletes them. A note is your own text on a story. Choose Add note in a story's toolbar to write one; it saves as you type. Rows with a note carry the note mark, and the Notes feed lists every noted story and searches the text of your notes.

Browsing view

View > Windowed and View > Classic select the browsing view and save your default in this browser. Window view reuses a reader for each feed. Classic view opens stories and applets as pages. Open as a page is a one-off action that does not change your saved default. Use the Windowed selector to return an article to a window. Direct page links always open as pages.

Applets

The Applets menu in the menu bar holds three tools, each a window of its own. Replies to me takes your Hacker News user name and lists the replies to your last thirty comments and stories, checking again every three minutes while it is open, and marking what is new since you last marked them read. Look up a user opens a profile on Hacker News or Lobsters, with their submissions and recent comments, as a commenter's name in any discussion does; the bar at the top of a profile looks up someone else in the same window, and Back returns to the one before. Who is hiring? filters the posts of HN's monthly hiring threads by the words you type.

They read only what the sites publish to everyone, so none of them asks for a login, and your user name stays in this browser anonymously and is included in retained applet state when signed in.

Find

Find takes any link and lists every time it was submitted to Hacker News and Lobsters, so you can read each discussion of it.

About

YAVCHN never sees your Hacker News or Lobsters login. The discussion is fetched from each site's public API; to vote or reply, follow the link above the discussion, or the arrow beside a comment, to the source's own site. Without a YAVCHN account, your data stays in this browser. When signed in, pins, collections, notes, blocked domains, and retained reading state are stored with your account and synchronized across devices. Hidden stories and layout stay in this browser. The privacy policy has the details.

Open source: github.com/paulmooreparks/yavchn. Built with PUDL.