Case Studies

One workflow engine, many businesses.

Different businesses represented with the same execution primitives — states, requirements, rules, human controls, and actions.

Reference implementation means the workflow has been designed and, where noted, built as a real executable definition — but it has not been deployed for a client. Anything actually deployed is labelled Deployed and names the business it was built for.

Reference implementations

Document Operations

Concept

A document package is received, extracted, validated against what the process requires, and chased until it is actually complete.

Reference implementationView →

Service Operations

In development

An inbound service request becomes a triaged, scheduled, tracked job — with missing information collected before work is committed.

Reference implementationView →