The people behind your Concur system

The most expensive thing that happens to an expense platform is not a failure. It is a departure. Someone who understood why the system was built the way it was moves on, and what they knew goes with them. The platform carries on working, and gradually nobody can say why it does what it does.

This is the failure mode we see most often, and it is the reason we structure the way we do. Configuration knowledge is not written down anywhere useful. It lives in the heads of the people who made the decisions – why this expense type exists, which audit rule was added after which incident, why the workflow branches where it does. None of that is in the system. It is only ever in someone.

Why we assign named consultants

Every organisation we work with is assigned a consultant who learns that environment, rather than whoever is free that week. It sounds like a small operational choice and it is not.

A consultant who knows your platform can answer a question in a sentence that would otherwise require someone to go and read the configuration for an hour. More importantly, they notice things. A request that seems reasonable in isolation but conflicts with a decision made two years ago is only obvious to someone who was there for both.

It is also, frankly, the reason we stay a specialist team rather than growing into a generalist one. Named consultants only work if there are enough of them who genuinely know SAP Concur, and that constrains how fast you can sensibly grow.

Small tips, repeated

Our Concur implementation manager, Murray Cooper, runs a short quick-tips series for the same reason. Most of what makes a platform pleasant to use is not a project. It is a series of small things nobody was ever told – a setting that removes a step, a shortcut that saves a click a hundred times a month, a rule that stops a recurring query at source.

None of these are worth a meeting on their own. Collectively they are the difference between a system people tolerate and one they get on with. The series exists to put them somewhere people can find them, and the invitation is genuinely open: if you have a Concur question that has been quietly annoying you, ask it.

Culture is not a poster

We run team sessions that are, deliberately, not about work – the July one had a carnival theme and a costume round that some colleagues committed to considerably harder than others. It would be easy to be cynical about that, and we would be, if it were a substitute for anything.

It is not. It is what makes people stay, and people staying is what makes named consultants possible. A team that turns over every eighteen months cannot offer continuity to anyone, whatever it says in the proposal. The connection between the two is more direct than it looks from outside.

The point

When you are choosing a partner for a platform you will be living with for years, the useful question is not what they can build. Most competent firms can build it. The question is whether the person who built it will still be reachable when you need to understand it.