Solutions Consultant

The reason automation projects fail is almost never the technology. It is that nobody wrote down how the work actually runs, including the fifteen percent of cases that break every rule. Finding those is this job.

What the work actually looks like

You spend the first weeks of a project asking people to describe what they do all day, and then asking what happens when it goes wrong. That second question is the one that produces the useful answers, and it is the one most consultants skip because the answer is messy.

Out of that comes a document: the process as it really is, and a boundary that says what an agent may decide on its own. That document gets signed off before anything is built, and it is what the engineers work from.

The part that makes this different

You are expected to tell a customer that a process is not worth automating, even when they have budget and enthusiasm. A project that removes four hours a month and creates six hours of checking is a failure that takes a year to become visible, and by then it is your name on the map.

How we hire

A conversation about an operation you have worked in, then a session where you map one of our own processes with us. You will see how we work and we will see how you ask questions.