CLOUD PAPER: Shingo Irie’s Other Sale — an Estimate/Invoice SaaS Sold via M&A Two Months After the MENTA Transfer

Where this case fits

Public cases of Japanese indie development reaching M&A are still few, and most are records of “selling the flagship.” What makes this case unusual is that the product sold was not the flagship (MENTA), and it sold just two months after the flagship’s own sale. As a record of one indie developer completing two exits in the same year, it is a rare sample in Japan.

CLOUD PAPER was an estimate/invoicing SaaS that Irie built for his own billing work during his freelance days. It had been running since before MENTA became his 30th-product hit, the “steadily ticking along” side of his portfolio.

The seller’s track record — 30 products since 2008

Based on the Lifehacker Japan interview, here is the seller’s journey.

For MENTA, a call for 50 test users drew 200 applicants, and the spread on Twitter gave him the conviction that “there was light.” His selection criterion for services has been consistent: “If it’s a service I’d want to use myself, it can’t be wrong. If I’m the user, the problem is crystal clear.” CLOUD PAPER is the archetype of that criterion, born from a problem that definitely existed, his own invoicing work. That origin translates into a practicality that resists churn.

An exit for the “non-flagship product”

Even the non-flagship products in a portfolio have exits. In the shadow of MENTA the flagship, a practical SaaS like CLOUD PAPER also finds a buyer. Even without flashy growth, the never-disappearing demand of invoicing work plus an existing user base gets valued as a business asset. Call it the small domestic version of DashThis’s “unglamorous workflow automation worth over ¥1 billion”.

The nature of the estimate/invoicing domain also matters. Billing work recurs every month for as long as a business exists, and once embedded in a workflow it generates little motivation to switch. There is no need to ride trends; users stay put and the service quietly ticks along. From a buyer’s perspective, this is the type of asset whose post-acquisition operating costs and revenues are easy to forecast. What is “unglamorous” to the seller is “predictable” to the buyer.

Managing a portfolio of 30

Irie has built 30 products in total and openly says 29 of them didn’t hit. Within that set, CLOUD PAPER was a middle-tier product, “not a jackpot, but real demand, steadily ticking along.”

In portfolio-style indie development, products naturally sort into three tiers: “flagship-class,” “steady earners,” and “experiments/failures.” The important point is that each of these three tiers has a different exit. Flagship-class: share transfer (MENTA → Lancers). Steady tier: business transfer (CLOUD PAPER). Experimental tier: shutdown. Not forcing every product into a single success/failure binary is part of why he could keep building for 30 products. Indeed, even during the early stretch when “all 10 apps flopped,” he says “even those failures weren’t wasted”, the app portfolio brought in contract-development work, a recovery channel that paid the bills. Even the failure tier had an indirect return path.

Exit experience compounds on the second deal

CLOUD PAPER’s sale closed just two months after the MENTA transfer (October 2020). That speed is no coincidence. The first deal taught him, hands-on, valuation instincts, contract pitfalls, migration logistics, and how to work with specialists. The second deal was a rerun.

To an indie developer, M&A looks like a once-in-a-lifetime event, but in reality it is a repeatable skill set of negotiation, legal work, and migration, and once experienced, the psychological and practical costs drop by an order of magnitude. Even if the first sale is small, its value must be assessed inclusive of this experience dividend, CLOUD PAPER’s “small sale with an undisclosed price” reads as a textbook example.

The sequencing matters too. Having first completed a share transfer with a listed-company group (Lancers) must have functioned, for the second buyer, as a credit signal: “this seller can carry M&A execution all the way through.” What buyers fear most in acquiring a business from an individual is the process stalling mid-migration, and a recent completed deal directly neutralizes that fear.

The working style that sustained 30 products solo

Clues to how parallel operation of multiple products was possible appear in the same interview’s discussion of his work habits. Task management runs on Todoist. Next-day tasks are set by the day before, and must-finish tasks are capped at three. His most focused three hours in the morning are blocked on his calendar, during which he touches neither email nor chat. On Slack he uses scheduled sending so as not to break others’ focus either. He describes his own style as “action-oriented, single-point focus.”

A 30-product portfolio and “no more than three things at once” seem contradictory, but the reality is the opposite. Precisely because a mechanism forced his attention onto a few things at all times, a low-maintenance product like CLOUD PAPER could be maintained as “low-cost operation” rather than “neglect.” An operation that pours equal effort into every product could never build 30.

What this record cannot tell us

The sale price, the buyer, and CLOUD PAPER’s post-transfer trajectory are undisclosed, as are its revenue scale and user numbers. So this case cannot yield a benchmark for “how much an estimate/invoicing SaaS sells for.” What can be verified here is structure, not price: (1) a buyer existed even for a solid non-flagship product, and (2) one person completed two M&A deals two months apart. If you need pricing benchmarks, you would supplement with overseas disclosed cases like DashThis, where the breakdown was published.

Conditions for reproducing this

What generalizes: the selection criterion of “build from your own work problems,” an operating model that sorts products into three tiers with a different exit per tier, and the compounding value of getting the first sale done even if small. It also confirms that a SaaS targeting “work that never goes away,” like billing and estimates, can be a business-transfer target even for indie developers.

On the other hand, Irie had 12 years and 30 products of accumulation since 2008, with the track record of MENTA as a flagship running ahead of him as credit. This is not a story of an unknown first product selling at the same speed. And since the sale price is undisclosed, no monetary expectation can be attached to this playbook.

Related reading

• MENTA — the share transfer of the same developer’s flagship product
• DashThis — the overseas version of the “unglamorous workflow SaaS” exit