How we work. What we will not compromise on.
Values that are not specific enough to create discomfort are not values — they are slogans. These are ours.
Every company publishes values. Few of them mean anything, because they are chosen to reassure rather than to define. Words like “integrity”, “excellence”, and “innovation” appear on so many walls that they have stopped carrying weight.
We have tried to write ours differently — as specific, testable principles that we actually use to make decisions. If a value doesn’t occasionally cause us to turn down business or push back on a client request, it isn’t a real value.
01
TRANSPARENCY
We tell clients what they need to hear, not what they want to hear.
If a proposed migration path is risky, we say so — clearly, with specifics, before the contract is signed. If a client’s existing process models are in a state that will make the project harder than anticipated, we surface that in the assessment, not six months into delivery.
We have seen what happens when consultants paper over problems in order to win engagements. It damages clients. It damages the industry. We don’t do it.
In practice, this sometimes means recommending a smaller or slower project than the one a client is ready to fund. We consider that a feature, not a flaw.
02
CLIENT SOVEREIGNTY
Your data and your process knowledge belong to you. Full stop.
We build on open standards — BPMN, XML, standard APIs — because we believe vendor independence is a right, not a premium feature. We will never design a solution that makes a client more dependent on CaseAgile than they were before we arrived.
Our success is measured by how capable and independent our clients become, not by how much they need us to maintain what we have built.
We actively train client teams to operate and extend the frameworks we deliver. A client who no longer needs us for routine operations is a successful engagement.
03
DEPTH OVER BREADTH
We are specialists. We do not pretend otherwise.
CaseAgile operates at the intersection of BPM, enterprise architecture, and platform migration. These domains are deep enough that genuine expertise takes decades to develop. We do not chase every technology trend or expand into areas where we cannot bring that depth.
When a client’s needs extend beyond our domain, we say so and refer them to the right people. When a problem is in our domain, we bring the full weight of thirty years of global practice to it.
04
LONG-TERM THINKING
We design for the organisation five years from now, not just for the deadline next quarter.
Short-term solutions in enterprise architecture have a way of becoming long-term problems. The migration that was “good enough” in 2020 becomes the legacy crisis of 2026. We have seen this cycle many times.
Our frameworks are designed for continuity and evolution — not just to solve today’s problem but to make the next transition easier and the one after that easier still. We push back when project constraints would compromise that durability.
This occasionally makes our proposals more expensive in the short term. We explain why, and we let the client decide with full information.
05
EARNED AUTHORITY
We lead with evidence, not credentials.
Our team has accumulated decades of experience across global enterprise transformations. We are proud of that record. But we do not expect clients to accept our recommendations on the basis of seniority alone.
We show our reasoning. We document our assumptions. We make our methodology transparent so that clients can evaluate it, challenge it, and ultimately own it. A client who understands why we made a recommendation is in a far better position than one who simply trusted us.
We encourage hard questions during assessments. The ones that make us uncomfortable are usually the most important ones to answer.
06
CHANGE AS STRENGTH
We do not sell fear. We build capability.
Much of the enterprise software industry profits from organisational anxiety about change. Vendors make switching expensive. Consultants make projects sound more complex than they are. The result is organisations that are more afraid of their technology than empowered by it.
We take the opposite position. Our measure of success is not how much a client dreads their next platform transition — it is how much they have stopped dreading it. Organisations that have worked with us should feel more capable and more confident, not more dependent.
If a client tells us at the end of an engagement that they feel ready to handle the next migration themselves, we consider that the best possible outcome.
07
THE DEFINING DIFFERENCE
We design ourselves out of the equation.
Most migration tool vendors follow a familiar pattern: they solve one lock-in problem by creating another. Their tools require ongoing subscriptions to keep migrated content current, properly patched, and functional. The client has moved platforms — but they have simply exchanged one dependency for another. And if that vendor goes out of business, raises prices dramatically, or discontinues support, the client’s content may be left broken, with no path to maintenance.
We take a fundamentally different approach. Every engagement we deliver is designed to produce a clean, complete result with zero future dependency on CaseAgile tools or support. When we finish a project, the client owns the outcome entirely — no subscriptions required, no ongoing licence fees, no risk of being stranded if circumstances change.
This means our clients return to us for new projects — not because they are contractually bound or technically trapped, but because they trust our approach and our attitude to their interests. That trust is the only kind of relationship we want.