Start with one process.

Why we start small

A platform about how organisations work isn’t something you get to know by rolling it out. You get to know it by using it, on one process, with the people who actually do that process.

That’s why we keep the first group small on purpose. Not because we can’t handle more, but because every first customer shapes something that then holds for the next. What you run into changes the platform — and that only works if we keep enough attention per customer to take that feedback seriously.

What joining means

No big project up front. You start with one process, alongside the systems you already have, and grow from what works. Scope, costs and commitments are agreed with you before implementation starts.

We read every request ourselves and contact you to talk about your process. If it’s a fit, you get a platform of your own, with a login link by email, and from then on the conversation continues inside that platform — not by email.

What happens next is up to you. If it works, a second process follows. If it doesn’t, you’ve tried one process and rebuilt nothing.

Getting started, step by step

1. Choose one process. The one people work around every week, because the systems you have make it hard to change. If it also crosses into a partner, that partner can join through a case role. Together we decide the scope, who is involved, and how you would see that it got better. Everything else goes on a list for later; we don’t build half of it now.
2. Connect what’s already there. Your AI keys first. Then only the systems this process needs: each one is read once on the development environment before anything is built on it. Where your back office is the source of the data, it stays the source.
3. Describe the case and its roles. Your process owner describes the work to the CaseFlows coach: the phases, who does what, and what each role may see. A code assistant builds it as an open specification. The first version is deliberately small: a few phases, one or two roles.
4. Try it, decide, improve. You walk through test cases on the development environment, taking the role of a customer, a colleague or a partner yourself. Production only gets what your process owner approved. Once real cases run, we look together at where the work waits, and every change follows the same route: proposed, tried, approved.

From your side that takes a process owner with time to describe and try the work, a few of the people who do it, your AI keys, and access to the systems the process needs. From ours: we set up the platform with you and stay alongside during the pilot.

What it costs

Taking part in a case is free: a customer or partner who works in your case pays nothing. Running your own platform is a subscription, and building your own caseflows is the higher one. During the private beta we agree the terms with each customer, before you commit to anything.

If you work with partners

A partner can take part in your case through a case role, without a platform of its own and at no cost. A partner that wants to assign the role to its own people and manage it itself does that from its own CaseFlows platform. In both cases you agree together what the role may see and do.

You bring your own AI keys

CaseFlows runs on your organisation’s own AI keys, not on ours. So the first step of every start is collecting your keys: for the code assistant that builds your platform, and for the language models your caseflows use.

That way model use runs on your contract and under your terms, and our price doesn’t move with a model vendor’s. You choose the provider: a large AI platform, a European host, or a model you run yourself.

What we need from you

Two things, and the second matters most.

Who you are and which organisation you work for. And: which process hurts the most. Not the tidy description from an annual plan, but the thing people work around every week:

• the overview that lives in a spreadsheet,
• the approval that always stalls,
• the information that sits in four systems and is right in none.

That’s where we start. After we’ve talked, a first version of your platform is set up around that process, so the first thing you see is about your work, not ours.