How work becomes a product

Three stages, no shortcuts.

Nothing moves to the next stage because it would be convenient to sell.

01

Build it for ourselves first

Every product starts as a system we actually run. If it does not survive our own use, it does not get packaged.

02

Package only what is repeatable

A method becomes a product when the steps, the output, and the support burden are all understood.

03

Publish with the status attached

Available, packaging next, or research. The label appears next to the work everywhere on this site.

Publishing standards

What we will and will not say.

These rules apply to product pages, portfolio entries, and every preview on this site.

Available means deliverable

A working purchase or intake path, a defined output, and a support route.

Research stays labelled

Internal systems can be shown without pretending they are ready for customers.

Data stays grounded

No market-size claims, dates, or performance promises without evidence.

Demos say they are demos

Every figure in a preview is marked illustrative, because it is. Archived prototypes stay on the archive page.

Founded
2026
Products available
One
Launch dates promised
None