Peing: Built in 6 Hours, 200M Monthly PV in One Month — Sold at the Breaking Point of Virality

Rereading the “Fastest Indie Exit” from the Record

Indie project sales normally come after years of operation, priced at some multiple of dozens of months of profit. Peing breaks almost every one of those conventions. Six hours of development, one month from launch to sale, and a 200-million-monthly-PV pace in between. In the history of Japanese indie development, you will struggle to find a shorter “start of development → business transfer” on record. What makes this case interesting is not the success story — it is the documentary record of what happens when virality exceeds an individual’s operational capacity. The sale was less a victory declaration than an evacuation from a burning building.

Timeline

The Business in Brief

Peing is a service that lets Twitter users receive anonymous questions. Seseri implemented a “version fit for Japanese Twitter culture” of Sarahah, the anonymous messaging service then going viral worldwide, in about 6 hours. Twitter integration made it “startable in 5 seconds,” and the design of sharing questions to Twitter as images generated the spread. The product itself functioned as its own advertising: a textbook viral loop. Users were not limited to ordinary people. The service spread to celebrities and politicians, because a place to ask what can’t be asked openly delivers more value the more followers you have.

Breaking Down the Numbers

Line up the published figures and the abnormality of the growth becomes clear.

• 100,000 daily PV on day 5 after launch, 400,000 on day 6. PV quadrupled in a single day
• The 200M monthly PV pace at the time of sale works out to over 6.5M daily PV — another 16x on top of the 400,000
• Question submissions were growing at 300,000 per day; at peak, over 30,000 people were accessing simultaneously per minute

The acquisition channel was effectively Twitter alone, zero ad spend, zero SEO. Questions and answers flowed through timelines as images, and people who saw them created their own question boxes. A design where every single answer generates exposure no ad budget could buy is a textbook viral success, and that success itself became the crisis.

Why It Sold — Growth Outran One Person’s Limits

Seseri described the situation at the time: “Questions were growing at 300,000 a day. At peak, over 30,000 people per minute in real time. I was terrified every single day.” Server load, incident response, and moderation had completely exceeded one person’s processing capacity, and he cited “feeling the limits of the existing development structure” as the reason for the transfer.

The buyer was Jiraffe (Nakano, Tokyo), operator of a price-comparison site for used goods. The reasons Seseri trusted them: “the speed, 60 hours from first contact” and “they immediately committed people.” The price was undisclosed. After the transfer, Shunsuke Sasaki, founder of the social gaming company Pokelabo, took over as head of the business, and Seseri remained as an advisor. Peing went on to expand globally (the service ended in 2025).

Why “Letting Go After One Month” Was Rational

Decompose the decision and three asymmetries emerge.

The cost asymmetry: the infrastructure bills, incident response, and abuse moderation needed to support 6.5M daily PV balloon faster than ad revenue ramps up. For an individual, page views arrive as invoices before they arrive as revenue.

The time asymmetry is harsher. Virality does not wait. If users churn through outages or controversy during the months it takes to build an organization, the asset value itself evaporates. That is why “a buyer who can move in 60 hours” beat “a month spent shopping for the highest price.” That the deciding factor in choosing a buyer was speed, not price, matters as negotiation practice: the optimal buyer profile changes depending on whether the seller is in peacetime or in a fire.

The return-on-investment asymmetry closes the set. The total investment was 6 hours of development and one month of operation. Even if the sale price was small, the return on invested time was overwhelmingly positive. “How many months you spent building” and “how much it sells for” are unrelated, market timing and viral design decided everything.

Bundle the three together and you get: six hours to build, sixty hours to let go. The heart of this case lies not in the flashy 200M monthly PV figure but in how those two short spans balance each other.

What Went Wrong, and What Came After

This case is also a record of risk. The testimony that hypergrowth itself was terrifying for the operator, “I was terrified every single day”, carries weight as a first-person account from inside a viral event. The anonymous-question format breeds harassment, and moderation load scales with size. The legal and psychological risks were too large for one person to carry.

And in the long view, Peing itself shut down in 2025. Even under corporate management and global expansion, the product lifespan of an anonymous-question fad could not be extended indefinitely. The frenzy at the moment of sale guarantees nothing about a product’s lifespan, a caution for buyers wary of overpaying, and at the same time retroactive vindication of Seseri’s decision to let go at the peak of the frenzy.

What This Case Teaches

The biggest lesson: viral products should be built on the premise that if they succeed, an individual cannot hold them. Zenn, which sought support 9 days after launch because of payment-processing risk, followed the same pattern. Peing reached the same conclusion via traffic risk. Our verdict is blunt: the virality was luck, and the sale was skill. What Seseri did well was not landing the hit but admitting, within a month, that the hit had outgrown one person’s hands. Selling a hypergrowth indie project is not “giving up”. It can be the only way to keep the service alive. Thinking through “if this hits, who do I hand it to?” at the design stage is not pessimism, it is design.

What Can and Cannot Be Imitated

• What transfers: “ship the fastest localized implementation of something going viral overseas, tuned to your language and culture” is a repeatedly effective pattern. The speed of releasing within 24 hours of seeing Sarahah, the design that shaved signup friction to “5 seconds” via Twitter login, and output formatted for SNS sharing (images, cards) are all general-purpose techniques
• What doesn’t: the occurrence of virality itself is uncontrollable, and aiming for it and missing is the norm — countless services with the same design never took off. Anonymous services also live next door to harassment risk, so moderation load and reputational risk must be priced in from day one. And a buyer “able to decide in 60 hours” only appeared because 200M monthly PV gave the seller negotiating power

Related Cases

• Zenn — the same pattern of transfer caused by “growing too fast”
• TypingMind — fastest release right after a platform shift
• Warary! — the “slow and steady 2.5 years” variant of the indie sale