Case orientation
Organise around the case — the shared reality where people, organisations and AI work together — and the case role through which each takes part.
Read →The thinking behind CaseFlows
Three ideas carry the platform: organise around the case, go from intent to a running system, and learn from your own work. Short reads — the reasoning, not the pitch.
Organise collaboration around a case. Describe how it should work in an open specification that runs as it is written. Improve that specification with signals from real work. Each idea answers its own question — around what, how, and when to change — and together they are how CaseFlows works.
Three ideas, one way of working
What it makes possible
Your back office, your choice
Build what you need and keep what already works: the caseflow organises the new work, your CRM, ERP and planning supply the data and services.
Read →Control in an AI-powered organisation
Give AI work to do and keep responsibility where it belongs: an agent gets a case role with enforced limits, and every action can be traced.
Read →Working across organisations
One case, several organisations, each in control: a partner takes on a case role with clear limits and an agreement both sides confirm, without sharing a system.
Read →Open specifications, portable processes
Your way of working belongs to you: written down in an open specification you can read, take with you, adapt and share.
Read →An ecosystem that grows with you
From one partnership to a network of organisations and providers, one relationship at a time, each on its own platform.
Read →Five words, one meaning
- Case: something that has to be brought from a trigger to an outcome, such as a permit application. It has an accountable owner and connects everyone who takes part.
- Case role: a responsibility in one case, with what it may see and do in each phase. Not a login or a job title. A person, a team, another organisation or, within limits, an agent can hold it.
- Caseflow: the lifecycle of a kind of case: its phases, its roles, and how work and responsibility move between them.
- Specification: the written-down description the platform runs: the caseflow, plus the information, rules and services it uses. Open files, JSON and markdown.
- Runtime: the part of CaseFlows that executes the specification and enforces its limits while cases run. The screens are built separately, as code.
Want to see it on your own process?
CaseFlows is in private beta, onboarding our first customers. Start small — one process, one team — next to your existing systems.
Request early access