Some clients arrive with a clear request: I want to automate the invoicing process, I want a dashboard that updates me every morning, I want the team to stop losing time in follow-up meetings.

Other clients arrive with a feeling: something isn't working well, but I'm not sure exactly where. Or: I know I should optimise something, but I don't know where to start.

Both starting points are equally valid. What changes is the journey.

When clients know what they want, the process is relatively linear: we understand the context, validate that the solution makes sense, and execute. When they don't know entirely, we need a prior step: building together a vision of what should exist.

In practice, we lay all the visible pieces on the table — current processes, friction points, what's already working — and let the patterns emerge. Often this is the moment when clients say for the first time: "Ah, actually what I need is this."

It doesn't always match what they originally asked for. And that's normal.

It's not that they were wrong. It's that without seeing it in operation, it's hard to know exactly where the knot is. Our job is to create the conditions for what they need to become visible.

When clients don't know what they want until they see it, the problem isn't lack of clarity. The problem is that they skipped the exploration step. We exist to make that step possible.

→ Why we don't work with everyone · The difference between delegating and trusting