Framework operational · v0.9

SaaO / SaaO community

SaaO cases

A SaaO case is not a marketing success story: it is the documentation of an operation. Every published case follows the same structure so cases can be compared and learned from.

Structure of a case

  1. Context

    The business, its problem, and why neither a generic SaaS nor traditional development solved it.

  2. Blueprint

    Which blueprint the work started from and what it ships with by default.

  3. Adaptation

    What was parameterized and customized, and who did it (humans, gated agents, governed agents).

  4. Operation

    Metrics of the running system: availability, incidents and their resolution, evolution of the software over time.

  5. Evidence

    What the client can verify without trusting the provider. At Level 3, the Software Passport.

Case directory status

The first documented cases will be published here during 2026. If you operate software under this model and want to document your case with this structure, reach out through the contribution page.

/en/cases