Philosophy
A short explanation of how Ryoka decides what to build, what to hold, and what to let go.
Patient capital
Most software gets built to be sold. Ryoka builds software to be used, for as long as it's useful, run by people who care whether it keeps working. Capital here is patient by design: no fixed exit timeline, no pressure to flip a product before it's proven itself.
Deliberate ownership
Every product Ryoka holds is a decision, not a default. A small portfolio chosen on purpose beats a large one collected by accident. If something doesn't earn its place, attention, revenue, or genuine use, it gets sold, shut down, or handed to someone who wants it more.
Build, then decide
Not every project starts as a company. Some begin as an experiment: a weekend build, a small tool, a test of an idea. What survives contact with real users earns further investment. What doesn't gets archived without ceremony, the failure rate is how the good ones get found.
Small teams, real stakes
Ryoka runs lean on purpose. Small teams, direct ownership, no layer of management between the person building and the person deciding. That's slower in some ways, and faster in the ones that matter.
In practice
See the current portfolio or, if you're building something small worth continuing, get in touch.