Where does this idea come from and what goes into it? This is one of your key recommendations in your advisory note.

Yeah, so I'm also old enough to remember Lotus Notes, and I have worked with Lotus Notes, yeah.

I had the pleasure, yeah, kind of.

Defined pleasure, yeah.

And I also, like, I know a lot of organizations who are still struggling today to kind of get rid of it, yeah, because it's kind of so woven into the organization, yeah.

But as you said, key issue today is the ownership and the lack of documentation.

It does things and is necessary still to work.

HR, HR, HR,

Of course, the one with the money." So isn't the cheapest extension the one that we never built? So shouldn't we really look at the very initial part of this process, the requirements definition, and the moment that people come up to us and ask, "Can you do that?"

Yeah, totally.

So the thing is, building it, yeah, or customizing it inside the platform is the last step you, you undertake kind of.

And there are, in, in my advisory note, I propose seven steps where you have actually questions that you should ask yourself before you are implementing, not to make it like an over-sophisticated process, yeah.

But if someone arrives at your desk and says, "I need this particular custom form or something," you should ask some questions before you rush to the implementation or rush to give it to Claude to implement it or whatever LLM you have behind it, yeah, uh, to, to actually implement it.

So I would start first with adjusting the requirement, yeah, or the first step that we have is adjusting the requirement.

Yeah.

HR, HR.