Agreeing one set of lead-management terms across the country subsidiaries.

The situation

Every country had a word for lead, and none of them matched.

Hoval builds complete systems for heating, cooling and ventilation and exports them to more than 50 countries. Lead management had grown up locally: generation and follow-up ran decentrally, with different tools, at different locations, in whatever shape each country subsidiary had settled on.

The data behind it was not maintained digitally in a uniform way and many steps were carried out by hand. Comprehensive reporting was therefore not possible: the group could not see its own lead management as one picture.

A service technician in a red Hoval polo shirt works at the control flap of a red Hoval UltraGas boiler while a red Hoval.com van stands in the foreground.
Two project slides on a red background show a calendar-week timeline running from a group as-is view to the start of the blueprint definition, and a detailed process diagram with annotations.
A swim-lane diagram on a red background splits one customer trigger into separate step sequences for call centre, marketing and sales.
A hand draws structural details onto a sheet of hand-drawn plans with a black fineliner.
A man in a red polo shirt holds a handheld service device at an opened red heating unit.
A hand reaches for the control display of a red Hoval boiler, which shows a flow temperature of 54 degrees beside a house symbol.
Two men sit across a meeting table in conversation, a laptop between them and a large screen showing a red-branded product page behind.
A man in red workwear holding a red folder talks with a colleague in front of a red Hoval boiler in a plant room.
A service technician in a red Hoval polo shirt works at the control flap of a red Hoval UltraGas boiler while a red Hoval.com van stands in the foreground.
What we settled first

An evaluation first, and a target process instead of a rollout.

The work was an evaluation. Standardised group-wide lead- management processes were evaluated across the national companies, and what came out of it was a described target process rather than a system switched on.

A defined set of common lead-management terms was one of the four things the work produced. A standardised group-wide process has to be written in one vocabulary, and the terms are that vocabulary.

The as-is summary was written in German and English. The people who have to recognise their own work in a process description do not all work in one language, and workshops and interviews deliberately took in participants in different positions and from different countries.

Two men sit across a meeting table talking, with a laptop between them and a large screen behind showing a red-branded product page.

Workshops and interviews

The as-is picture came out of workshops and interviews in the national companies.

A man in red workwear with an open red folder explains something to a colleague standing beside a red Hoval boiler.

Lead sources counted

The analysis went through the various lead sources and marketing measures already in use.

Two project slides on a red background show a calendar-week timeline from the group as-is view to the blueprint definition, and a process diagram covered in annotations.

One target process

A single standardised target process was developed out of what the countries described.

A hand redraws details on a sheet of hand-drawn plans with a black fineliner.

Central and digital

The target process was built for a central, digital and complete data basis.

A project slide on a red background lays out a calendar-week timeline ending in the start of the blueprint definition, above an annotated process diagram.

Written to be checked

The as-is summary was produced in German and English so every subsidiary could recognise its own work in it.

What we changed

The group got a description of its own processes it could argue with.

The as-is processes were written up in German and English, so every subsidiary could check its own

The summary exists in both languages because the people who had to confirm it do not all work in one. It describes what each national company actually does, in the words that company uses.

A common set of lead-management terms was defined, so comparable figures became definable

Comprehensive reporting was out of reach because the data is not maintained uniformly and digitally and many steps are done by hand. Neither of those was changed here. What the agreed terms give is a basis on which a comparable figure can be defined in the first place.

As-is and target processes were visualised and revised repeatedly, so the target process was agreed rather than announced

The visualisation went back and forth in close exchange with all project participants until it matched what people actually do.

An action plan closed the work, so implementation had a starting point

The plan sets out the steps for implementing the target process. What it does not do is start them: the engagement ended with the plan.

Two men talk across a meeting table, with a laptop between them and a large screen behind showing a red-branded product page.
The outcome

Hoval ended the engagement with its own processes on paper.

At the end of the engagement Hoval had four things: a summary of its as-is processes in German and English, a defined set of common lead-management terms, a visualisation of the as-is and the target process, and an action plan for implementing that target process.

Three things carried it: workshops and interviews with participants in different positions and from different countries, analysis of the various lead sources and marketing measures already in use, and a process visualisation revised repeatedly in close exchange with everyone involved.

Next Project
Transport System Bögl
What we do

The Agentic Growth Stack in four phases.

Four phases that build on each other. Each one ends in something usable rather than a presentation — a roadmap you can budget, a platform in production, an operation the team carries, and agents working inside the process.

Plan

We establish where you stand, sharpen the goals and set a roadmap that fits your data, your processes and your organisation.

Explore Plan services
A woman with a tablet at a window-side table talking to a colleague standing by the window.

Build

We build the platform: CRM, custom software and the data flows between them, properly integrated instead of side by side.

Explore Build services
Two people at a standing desk, one typing on a laptop, the other turning a monitor on a stand towards her.

Operate

We embed operations, adoption and security in everyday work, so the platform is carried by the team after the rollout.

Explore Operate services
A woman at her desk looking up at large wall-mounted monitors.

Automate

Agents take over recurring work, monitored and measurable, with clear rules for governance and compliance.

Explore Automate services
An empty desk after dark, a monitor and a docked laptop still awake, the chair pushed aside.
first step

The first step towards an agent-native company.

In the Enterprise Discovery Workshop we develop a clear target picture and a business case that holds up, in a matter of days. Fixed price, no open-ended day rates.

Smiling man in a dark blue suit in a bright office.
Rather talk first?
We get back to you personally.
Request a workshop
bg-leftright-cta