Founder, responsible for consulting and agents

Vincent Croes, founder and change manager

Vincent has spent fifteen years in change programmes. He founded a digital agency, sold it, and then built the team at Gravity whose job was to find the question behind the question. At Back From the Future he does the same work with different tools: finding out how the work actually flows, before anything gets built.

Plan an introduction

Who

Saving time is the easy part

The same moment comes up in every engagement: a process has been found that costs hours a week, and everyone wants to start building. That is when Vincent asks the awkward question. What will those hours do once they are freed up? Without an answer the gain evaporates into other reactive work, and six months later there is a tool nobody misses. So his analysis never ends at a list of automatable tasks, but at what the organisation will earn with the time it wins back.

Track record

Why he can say this

Vincent has not been making this argument since AI came along. He has been making it for fifteen years, in three roles where the consequence grew heavier each time: first as an entrepreneur paying the bill himself, then as the person who had to prevent it, and finally as the person who also had to sell it.

01

Built an agency and sold it

Vincent founded Tjuna, a digital strategy agency, and sold it to Gravity. That is a different starting point from advising on change: he has paid the bill himself for choices that did not work out.

About discovery
02

The team that looked for the question behind the question

At Gravity he founded the Business Designers team, which did the strategy for every client and made sure the right thing got built. The reasoning was blunt: something users never asked for but that gets built anyway never pays back. That is not a disappointing margin, it is a disinvestment.

03

Commerce and design under one lead

He then became Head of Commerce, with Business Design, Marketing, Sales and Design reporting to him. That is where the argument came full circle: anyone selling what gets designed cannot maintain that the user question is a detail.

The standard

How the work gets done here

At Back From the Future the question has stayed the same; only the tooling is now called AI. An agent automating a process nobody asked for is exactly the same disinvestment as a feature nobody uses. Vincent is responsible for the consulting work and for building agents, and this is the way of working the team runs on.

01

Look first, build second

Interviews at every level: the leadership describing the process, and the people running it. Where those two diverge is usually where the friction sits. Six weeks per department, with a validated pilot plan as the outcome. At Veris the redesign that followed freed up to 20% of the working week.

02

Findings with their evidence attached

Every finding carries its source: who said it, at which level, and whether several people raised it independently. Where the evidence is thin, it says so. And the solutions employees raised themselves are kept separate from what we propose, so people see their own words reflected. That reads less smoothly than a polished advisory report, and it is exactly why a board dares to decide on it.

03

Build so you can take it over

From use case to an agent that genuinely takes work off people’s hands, with a human at the decision points. The agency runs over fifteen of them across seven departments itself, so what gets proposed here has been tried on ourselves first. The handover is part of the work, not something that comes after.

How an engagement starts

A twenty-minute introduction

No presentation, just a conversation about where things chafe. That usually makes it obvious which department lends itself to discovery first.

Or take a look yourself first

The AI Quick Scan gives an honest starting point in a few minutes, including what is still missing. Free, and with no follow-up call unless you want one.

What Vincent doesn’t do

  • Sell an AI solution for a problem that is not one. Discovery regularly finds that a process problem is just a process problem, and then that is the outcome.
  • Build something nobody takes over. If there is no one to maintain the agent after handover, the agent is a time bomb rather than a saving.

Over fifteen agents across seven departments. What we propose to clients, we tried on ourselves first.

We automated our own agency first

What that looks like, including what went wrong, is written up. Read the piece

Frequently asked questions

01 Why discovery first instead of building right away? +

Because the documented process is rarely the process people actually run. Build on the paper version and you automate something nobody does that way. If you already know exactly what you want to build and why, discovery is a detour and we skip it.

02 Do you work with our own systems? +

Yes, that is the starting point. An agent running alongside the existing stack does not get used. Which integrations are feasible depends on what is there, and that is one of the first things discovery surfaces.

03 What happens after handover? +

A handover with knowledge and quality secured, so you can run it yourselves. That is also what we steer towards: the goal is that organisations can do this without us.

Curious where your time is leaking?

In a twenty-minute introduction we look together at which department lends itself first.

See how discovery works