Peing: Built in 6 Hours, 200M Monthly Pageviews in Weeks, Sold in a Month
In November 2017, 26-year-old developer Seseri cloned an anonymous-Q&A concept for Japanese Twitter in six hours. Five days later it hit 400K daily pageviews; within a month it was pacing 200M monthly PV — and was sold to Jiraffe Inc. (price undisclosed).
This is a translation of the Japanese original. The Japanese version and cited primary sources are authoritative for all figures.
Timeline
| Date | Event |
|---|---|
| Nov 21, 2017 | Seseri tweets he could build a Sarahah-like service “in about 6 hours” |
| Nov 22, 2017 | Ships it in under a day |
| Nov 26 | 100K daily PV |
| Nov 27 | 400K daily PV, #1 trending on Japanese Twitter |
| Dec 21, 2017 | Sold to Jiraffe one month after launch — then pacing 200M monthly PV |
Why it exploded — and why he sold
Peing let Twitter users receive anonymous questions, with answers shared as images to the timeline — the product output itself was the ad. Zero marketing spend, all Twitter virality.
The success became the emergency: “Questions grew at 300K per day; at peak, over 30,000 concurrent users per minute. I was terrified every day.” Server load and moderation had exceeded what one person could operate. He chose Jiraffe because of speed — “from first contact to decision in 60 hours” and immediate staffing.
Lessons
1. Viral products must be built assuming you can’t keep them if they win. Same conclusion as Zenn: for an individual, selling a runaway success is how you keep the service alive.
2. In a crisis, buyer speed beats buyer price. A month of price discovery is worth less than 60 hours to a rescue.
3. Six hours of build time, one month of operation. Whatever the undisclosed price was, the ROI per hour is off the charts — proof that build time and sale value are unrelated. Timing and distribution design decide everything.
Related cases
Sources
- J-CASTニュース「1か月で急成長の『Peing - 質問箱』買収 月間2億PVでサーバー負荷過大」
- TechCrunch Japan「ローンチ1ヶ月で月間2億PVペースの『Peing – 質問箱』をジラフが買収」
This article summarizes and analyzes the public sources above. Please refer to the primary sources for details.