CaseFlows
Change how you work as fast as your world changes
Your organisation never stands still. Customers, partners, technology and circumstances keep changing. So why should your back office be set in stone?
With CaseFlows you adapt the work yourself: who does what, with which partners, with which AI and on which systems. When customers ask for something new, when a better language model comes along, when a supplier no longer fits.
You decide what you want to achieve, who you work with and how the work is organised. Not your software.
You set the course. CaseFlows makes it possible.
What changes around you
The world your work depends on keeps moving.
Customer wishes
Customers expect something new, something faster, something different.
Your environment
Rules, markets and partners shift.
Technology and language models
Better and cheaper models keep arriving.
Suppliers
A vendor raises its prices, stops, or falls behind.
CaseFlows lets the way you work move with it, without waiting for your software vendor.
What an organisation wants
Three things, and together they mean deciding for yourself.
Adaptable.
Change how the work is done when circumstances change.
In charge.
Decide for yourself what needs to happen and who is responsible for what.
Independent.
Not tied to a software vendor, an implementation partner or a single contractor.
What you can change
Adapt each part of the work on its own
People
Give work to another colleague or an outside party.
When someone is away, or a specialist is needed.
Organisations
Add a partner, replace one, or leave one out.
When a partner stops, or a better one comes along.
AI
Have a task done by a person, an agent, or both.
When an agent can take routine work off people’s hands.
Processes
Change caseflows, responsibilities and rules.
When customers ask for something different.
Technology
Replace a service, a model or a vendor.
When a better language model or supplier comes along.
Each one changes on its own, without rebuilding your back office.
The positions are examples. Try a switch.Knowing when to change
A back office that keeps learning
Everyone who works in a case sees what isn’t right: an employee, a customer, a partner. In CaseFlows they flag it where it happens, and the case, the role and the moment come with it.
That signal becomes a change request. You decide whether it goes ahead. An AI code assistant then makes the change in your own system, you try it in test cases, and it becomes the next version. So the people who use your back office keep improving it.
CaseFlows gives you the ability to change. The signals tell you when.
“I had to send the same document twice.”
- Change requestThe signal becomes a proposed change, with its context.
- You decideThe process owner judges whether it goes ahead.
- An AI code assistant builds itIn your own system, from the spec.
- You try itIn test cases, before anything changes for real.
- Next versionEvery case knows which version it ran under.
Shared, not central
No central command post
Changing how you work isn’t for management alone. Employees, customers and partners have their own room to change things, within the responsibilities and boundaries you agree on together. Responsibility sits as close to the work as it responsibly can.
Everyone involved takes responsibility, within agreed boundaries.
Design principles
What makes it possible
Organise around cases.
A case is something that has to get from a trigger to a result: an application, an assignment, a customer question. People, organisations and AI work around it, each from a case role with a clear responsibility.
Rights follow responsibility, not a job profile.
What you can see and do depends on where the case stands right now.
The back office stays, but goes back to its place.
CRM, ERP and planning provide services to the caseflow, instead of deciding how the work is done.
AI gets a role, not the keys.
By design, an agent works within the same boundaries as a person in that role.
The people who know the work help build it.
Describe it, have it built, try it, adjust it — without becoming a programmer.
Work together without bolting your processes together.
You hand over a case role, not a system or a file.
Responsibility stays visible.
Who was allowed to do what, when, and on what grounds — at the core, not in a log file afterwards.
Who it’s for
Three situations where CaseFlows fits
Organisations stuck in their back office
Over the years the CRM, ERP or planning system has started to decide how the work is done. CaseFlows sits on top of what you have: the caseflow organises the work, your existing systems supply the data and services.
You don’t have to throw out your back office to get control of it back.
Organisations that want their people to improve how they work
The people who see where a process doesn’t fit are often far from the people who can change the software. In CaseFlows, business experts describe their work with an AI coach, try a first version in test cases and give feedback straight away.
The people who know the work get a say in the software they do it with.
Ecosystems of independent organisations
Cases rarely stop at the edge of one organisation. A case role is the boundary: you give a responsibility to another party without having to know how they work inside.
Work on the same case together without having to become one organisation or one system.
Independent and in control
Hosted in Europe. Your AI is your choice.
CaseFlows is hosted in Europe. And you don’t become dependent on us either: how your organisation works is written down in open specs you can read and take with you. You use your own AI key, and you choose where the intelligence comes from: a European provider, or a model on your own infrastructure. You decide where your data goes and where the computing happens.
- Hosted in Europe
- Open specs you can read and take with you
- Your own AI key
- A European provider or your own servers
Where we stand
Private beta, with room for a few.
CaseFlows is in private beta. We work with a small group of first customers and have limited room for new ones. Want to be among them? Request early access.
Request early access