Process consulting or implementation? Who actually builds something after the workshop

Most automation projects start with the same conversation. After that, the paths split. A consultancy runs a workshop, maps your processes and hands over a concept with recommendations. An implementer looks at the same process and then builds an agent that does the work. One path ends with a document, the other with something running. If you are weighing process consulting against implementation, look closely at what happens between those two endpoints.

Process consulting vs. implementation: what you have at the end

Consulting produces insight. It shows where time goes, which processes lend themselves to automation and in what order to tackle them. That has value, but it is an intermediate result. To turn it into something that takes work off your staff, you need a second contract with someone who builds.

The handover is where most of the effort leaks away. The implementer reads the concept, asks the questions nobody asked in the workshop and talks to the same people again. You end up paying for the process analysis twice, once as consulting and once as onboarding.

Someone who has to build asks the awkward questions in the first meeting, because tomorrow the answers go into the agent. What does an order without an item number look like? Who decides when the customer isn't in the system? Which ERP field is mandatory? A consultant can ask these too. Nothing forces them to, since the report is finished either way.

An example: one process, two paths

Say a wholesaler wants to stop retyping emailed orders into its ERP.

On the consulting path there's a workshop with sales, inside sales and IT. The output is a process map, a ranked list of twelve automation ideas and a recommendation to start with order entry. Then comes the search for someone to build it: request, quotes, selection. Meanwhile inside sales keeps typing every order by hand.

On the implementation path the first meeting asks a narrower question. Which process goes first, and what access does it need? A fixed-price quote follows, then the build. Order entry from customer emails takes a few hours to build and, with one person from the department at the table, a single day to put in place. Testing with real emails happens the same week. From then on inside sales gets a finished order draft for every email. Fields the agent was unsure about are flagged, and a person approves or corrects the order.

The list with the other eleven ideas gets written on this path too. It just gets written while the first agent is already working.

Three questions that reveal a real implementer

"Implementation" shows up in plenty of consulting offers. Three questions in the first call tell you what's behind the word.

Ask who writes the code. If the answer involves partners, you are buying two companies with a handover in between.

Ask what will be running after the first engagement. An implementer names a process where nobody retypes anything afterwards. A consultancy names a document.

Ask how the price is calculated. Day rates for workshops and concepts pay for time. A fixed price for a working agent pays for a result, and the provider carries the estimation risk.

When consulting is the right first step

If you haven't decided whether to restructure, merge sites or replace your ERP, an implementer is the wrong call. Those questions come before any automation, and that is what consultancies are for. Once you know which daily work is eating your team's time, another concept adds little. At that point you need someone who builds.

How Sophera Consulting works

We implement. Process analysis isn't a separate project with us; it is part of the selection step. There are three steps: selection, quote, pilot. In the free automation check we work out which process suits a first agent and which access we need. You then get a fixed price with a cost-benefit analysis, and we build. An agent is set up in one to two days, and the pilot usually runs within the first week. Every automation comes with a maintenance agent included in the fixed price, and the result belongs to you.

Our recommendation

Hire a consultancy when you don't yet know what should change in the business. Hire an implementer once you know which work your people should stop doing, and use the first call to check that they really build after the workshop.