Two Failures → $5M ARR → an 8-Figure All-Cash Exit: ScrapingBee's Complete "By-the-Book" Journey

(Yen figures for dollar amounts below are rough conversions at ¥150 to the dollar.)

The numbers across the full journey

Stage	Figure
Prehistory	Two failed startups
First month	$1K MRR
Year 1	$8K MRR
14 months	$100K ARR
At $10K MRR	Reached “same salary as previous jobs + profitable”
Under 2 years	$500K ARR
At a team of 4	$1.5M ARR
Final	$5M ARR → sold to Oxylabs in 2025 for eight figures, all cash

The business in brief

ScrapingBee is a web scraping API that handles proxy management and browser rendering for you. Founders Pierre de Wulf and Kevin Sahin grew it via the classic content → developers → API billing route: writing a large volume of technical blog posts for developers (scraping how-tos) to build search traffic, then converting those readers directly into API customers. The customer base exceeds 2,500 companies worldwide.

Our editorial take

The placement of the interim goal — “$10K MRR = previous salary + profitability” — was masterful. Rather than shooting for $1M from the start, they set “enough for two people to live on” as the first goal. Once reached, the business could continue indefinitely, and all growth beyond that point became a bonus. This is best practice in goal-setting for indie developers.

The all-cash, eight-figure sale is the polar opposite of earnout hell (Tweet Hunter). Precisely because it was a profitable company with no reason to sell in a hurry, they could negotiate without compromising on terms. The strongest negotiating chip is “being in a position where you don’t have to sell.”

“Two failures → finishing the race on the third try” is a replay of a recurring pattern on this site. Bannerbear’s seven straight failures, Irie’s 29 straight failures — the same story, differing only in the number of failures.

Implementing “content → developers → API billing”

ScrapingBee’s acquisition stood almost entirely on one leg: relentlessly writing technical articles on web scraping (Python scraping how-tos, anti-bot countermeasures, using headless browsers, and so on). People searching in this domain are “developers who are writing scraping code right now and stuck” — and if, just beyond the article’s solution, there sits “an API that takes all this hassle off your hands,” they convert into customers with zero ad spend.

The important point is that the two founders chose this strategy not because it was cheap but because they could write it themselves. Technical blogging can’t be outsourced without losing quality, so for founders who can write, it becomes a barrier to entry. Conversely, the moment a small team centers its acquisition on a channel its founders cannot execute themselves, it gets dragged into a capital fight.

What it meant that the buyer was Oxylabs

The acquirer, Oxylabs, is the largest group in proxy and scraping infrastructure. ScrapingBee’s customers (developers and SMBs) complement Oxylabs’ main battlefield (enterprise), making this an acquisition that broadens the customer base while keeping the brand intact. An infrastructure company buying an API company follows the same “adjacent slot in the same wallet” logic as Semrush buying Prowly.

The timing is telling too: in the generative AI era, demand for “pulling data from the web” is structurally growing, and ScrapingBee sold mid-growth, to a well-matched buyer — not at the peak of demand. That is why they could command such strong terms: eight figures, all cash.

What Japanese developers can take home

Set the interim goal at “previous salary + profitability.” $10K MRR (¥1.5M/month) works as-is in Japan as the independence line for a two-person team
Technical-blog SEO is the most well-trodden path in the English-speaking world, but practitioners at that level are still scarce in the Japanese-language sphere — the opportunity remains
Selling pays best not “because you’re tired” but from “a position where you don’t have to sell.” Profitability and growth are negotiating power itself, prior to any decision about whether to sell