Zenn: A Solo-Built Dev Community Transferred to Classmethod 4.5 Months After Launch

The standard exit for an indie project is “grow it for years, then sell.” Zenn reached a business transfer to a major company just four and a half months after launch, and the reason was not “it isn’t growing” but “it grew too much.” The seller himself published the entire decision-making process in writing, so this reads as a rare field record of publicly soliciting a transfer partner.

Timeline

What the Business Is

Zenn is a tech knowledge-sharing service where engineers publish technical articles for free, bundle multiple articles into structured “books” for paid sale, and receive support (tips) from readers. The concept: “compensation for engineers who share knowledge.” It was built by indie developer catnose (operated through his company CodeBrew), and grew rapidly right after launch as users flowed in from existing services. Revenue came from fees on C2C transactions.

The “Help” Post, Nine Days After Launch

Just nine days after launch, catnose published a post seeking support, “Zenn needs help.” The reason was not a shortage of money, closer to the opposite.

• Users were growing at a pace far beyond expectations
• The structure had an individual holding money moving between users (paid books and tips), a heavy financial responsibility
• Support and moderation load was exceeding one person’s processing capacity, requiring a switch to organizational operations

What stands out is that at this point he had already organized his options into three and articulated his stance on each.

1. Raising money from VCs (he stated plainly he was “not very keen.” Incorporating, handling pitches, regular business reporting, demands for rapid scaling, management) too much of the work fell outside the “I like building things with my hands” range of what he is good at and enjoys
2. Acquisition of the service (business transfer) (“the option that wraps up most cleanly.” But with conditions: the company must be “close in philosophy with a matching tech stack,” and “I want to run Zenn together for at least one year,” “I don’t need a top position) I’d be happy as long as I have time to build”
3. Hiring members with personal funds and continuing, a plan to work furiously until revenue could cover payroll for a small team of 3–4. He also called this “the exciting option,” so it was not merely the leftovers of elimination. He added the caveat: “if I’m to lead, I want the team small”

Before entering any negotiation, he fixed in a public document what he could and could not concede, and that ordering became the baseline for the subsequent negotiations with 20 companies.

20+ Offers, and a Selection Not Made on Price

Over the four months following the public call, more than 20 companies made contact, including operators of major services and companies he had admired, with several offering large sums. “Every company’s offer was attractive and I agonized,” but the one he chose was not “the company that offered an astonishing amount”. It was Classmethod. The deciding factor, he says, was his meeting with CEO Satoshi Yokota.

• On monetization, a long-term posture: “if it comes around eventually, in some form, that’s fine”
• Rather than business strategy, user acquisition, or monetization, Yokota showed interest in Zenn’s quality, users, and technology
• Fit with the know-how of running the tech media “DevelopersIO” (25,000+ articles) since 2011 — a growth playbook suited to this industry

After the Transfer — Designed Not to Be Absorbed

catnose joined Classmethod on February 1, 2021, and has continued developing Zenn after the transfer. Not “sell and walk away,” but moving to the acquirer together with the development environment. Classmethod, for its part, explicitly committed to running DevelopersIO and Zenn as separate services for the long term rather than merging them. If the typical fate of an acquired service is to be absorbed brand and all, Zenn’s transfer was designed as “welcoming the creator along with the philosophy.” The announced plan, Classmethod’s resources going to user support and feature development, also corresponds precisely to the pain points catnose had listed in his public call (support load, financial responsibility).

What Was New About This Exit

“Growing too much” is a hidden failure mode of indie development, and a transfer is one of its solutions. The usual indie worry is “it won’t grow,” but a service involving payments and C2C sees its legal, financial-custody, and support burdens spike the moment it takes off. Zenn did not “grow first, figure it out later”. It began considering outside capital nine days after launch. The lesson: if you build a service that holds other people’s money as an individual, exit planning needs to start before launch.

Being able to say “help” publicly became negotiating leverage. The 20+ offers came from the service’s momentum plus the competitive environment the public-call format created. The conditions he extracted (continued development, respect for the philosophy) would not have emerged from a one-on-one negotiation; they required comparators. The “goodwill” in Warary!‘s pricing rule of thumb only becomes visible when there are multiple buyers.

Putting “how I want to work” into the transfer terms is the most reproducible part. Turning down higher offers to insist on “one year running it together” and “keep building” was a decision reasoned backward from life after the transfer. Maximizing the sale price and maximizing happiness are separate problems, a framing that matches MENTA’s Shingo Irie, who also kept developing inside the acquirer’s group after his transfer.

If You Were to Apply This

• What is reproducible: “publishing a call for support” is something anyone can do. Whether offers arrive depends on the service’s momentum, but the structure — terms improve versus talking privately with one company — is universal. So is the procedure of “fixing your non-negotiables in a public document before entering talks,” which works even for services without momentum
• The limits: Zenn was an exceptional case with clear product-market fit from launch; the speed of “transferred in 4.5 months” itself does not generalize. With the price undisclosed, the economic return cannot be evaluated either. And the buyer side had an unusual receptacle — “ten years of running a tech media” — a reproduction condition easy to overlook: the same public call does not guarantee a philosophically aligned buyer exists in the market

Related Cases

• Shingo Irie, who sold his 30th indie project MENTA to Lancers — the same type of exit, continuing development after the transfer
• The Warary! sale and “monthly profit x 24 months + goodwill” — pricing sense for indie service sales
• Tony Dinh’s snap decision to sell for $128K amid the Twitter API crisis — a sale decision triggered by platform risk