Process Consulting
Process Consulting: Analyze, Structure and Measurably Improve Business Processes
Process consulting focuses on the workflows a company uses to organize its day-to-day operations: order processing, approvals, handoffs between departments, documentation, and responsibilities. It usually becomes necessary not because of a single error, but because a process has evolved over the years around its exceptions—until no one can say which process actually applies, and processing takes longer even though no one is doing anything wrong. This requires a robust picture of the actual current state, a target process developed in collaboration with—rather than over—those who execute it, and a clear answer as to who will own the process and be authorized to change it in the future. Without this clarification, no new process will last longer than until the next reorganization.
Leading companies trust our network
What Process Consulting Delivers — and What It Does Not

The term carries two meanings, and that regularly causes misunderstandings. In organizational development, process consulting has stood since Edgar Schein for a stance: the consultant does not deliver a finished solution but enables the organization to find its own — in contrast to expert consulting, which brings a result with it. In everyday business language, process consulting means the work on the business processes themselves: mapping, analyzing, modeling, documenting, improving. We work in the second sense, but with the method of the first — not out of conviction, but because a workaround never shows up in any evaluation.
It separates the process as lived from the process as documented. In organizations that have grown over time, years lie between the two. A process assessment that reads manuals describes a workflow that no longer exists in that form. It only becomes reliable once throughput times, waiting times and exception cases are measured on real transactions and the exceptions are counted instead of being set aside as special cases — frequently they account for a third of the volume and two thirds of the effort.
It starts at the interfaces, not at the individual steps. In administrative workflows most of the time is not lost in the processing but in the handover: between sales and order management, between the business unit and IT, between site and headquarters. Speeding up single steps moves the queue rather than dissolving it. That is why the end-to-end process comes before the optimization of individual activities.
It settles roles before tools matter. A large share of the cases that begin as a tool problem end as a question of accountability. As long as it is unclear who owns a process, who may change it and who maintains the documentation, no amount of clean process modeling will hold. That decision is uncomfortable, and it is the reason why some initiatives only carry on the second attempt.
What it does not do. It does not write a target process over the heads of the people who run it — a workflow created that way is not lived, it is worked around. It is no substitute for a software rollout when the workflow fails because of the system, and it is not a staffing decision: where a role stays vacant or an accountability stays disputed, no process description can absorb that.
Two boundaries are worth naming. Where the question is throughput on the line, setup times, equipment availability and lean methods in manufacturing, our operations and process improvement consulting is the right entry point. Where it concerns procurement and supply chain workflows, the route leads to supply chain consulting. Where a workflow stalls mainly because the system landscape does not carry it, digital transformation consulting is the fitting frame. Internationally the same work appears under the labels business process consulting, BPM consulting and business process improvement consulting.
When External Support Moves Process Work Along Faster
If the process is documented, someone is responsible for it, and a process has already been successfully restructured within the organization, then the organization’s own capacity is sufficient. Some starting points are different—and the reason is usually the same: Those who work with a process on a daily basis no longer see it as a process, but as a given. An outside assessment raises the questions that no one inside the company asks anymore, because the answer has been clear for years.
1. Nobody Can Describe the Whole Workflow
- Each department knows its part, but no one knows the entire process.
- Without a shared understanding, the group discusses symptoms instead of causes.
2. The Handoff Between Two Units Costs Days
- Processing takes minutes, but the process still takes a week.
- Dwell times aren't recorded in any system—they only become visible when you track actual processes.
3. A System Change Is Coming Up
- An ERP, CRM, or workflow tool is implemented—and the processes remain unclear.
- If you digitize an unclear workflow, you’ll end up paying for custom solutions that nobody wanted.
4. The Documentation No Longer Matches Reality
- Manuals, work instructions, and process maps are years old.
- New employees learn the workflow from their colleagues, not from the documentation—and with each time it’s passed on, it drifts.
5. Growth or an Acquisition Calls for Standards
- Two locations, two companies, two ways of doing the same process.
- The longer work is carried out in parallel, the more expensive it becomes to harmonize the processes later on.
6. A Certification or Audit Is Approaching
- ISO 9001, an audit, or a regulatory requirement calls for verifiable processes.
- Documentation created solely for the audit is not maintained afterward—it must be part of day-to-day operations.
Do any of these starting points sound familiar? Twenty minutes are all it takes to determine whether the right next step is to conduct a process assessment, develop a target concept, or first clarify responsibilities.
From Process Mapping to Governance: The Service Range
These services can be booked individually or in combination. As a rule, the first three steps—capture, organize, and define—build on one another, and only then do digitalization and automation become worthwhile. Those who reverse this order end up paying for custom solutions.
Process Analysis and Process Mapping
Mapping the current state based on actual processes: Who does what, when, using which system, and where do wait times and idle times occur? We measure throughput time, processing time, and error rates rather than estimating them, and clearly distinguish routine cases from exceptions—which are what actually drive costs. The result is a robust process analysis that all stakeholders agree on.
Process Map and Process Modeling
A process map shows on a single page which core, management, and support processes exist and how they are interconnected—the foundation for any prioritization. Below that, we model the relevant workflows using BPMN or a more streamlined notation, depending on who will be working with them. Clarity takes precedence over completeness.
Process Documentation and Process Governance
Documentation that is maintained because it’s useful in day-to-day work: work instructions written in the language of those carrying them out, a clear approval process for changes, and designated process owners. This includes the uncomfortable task of determining who is authorized to change a process and who is not—without it, any process management system will fall apart within a year.
Process Digitalization and Automation
Set up workflows, bridge media gaps, and automate where it makes sense. Automation only works for processes that have been simplified first: A seven-step approval process doesn’t become better just because it has seven digital steps. We evaluate every automation initiative against its implementation and maintenance costs—and explicitly identify the cases where the effort isn’t worth it and a clear set of work instructions is more effective than a tool.
Interfaces and End-to-End Processes
Looking beyond departmental boundaries: from order receipt to invoicing, from request to acceptance, from onboarding to the first day of work. We determine what information is truly needed at each handoff and eliminate the follow-up inquiries, returns, and duplicate entries that result from missing information.
Enablement, Roles and Responsibilities
To ensure the new process continues to run smoothly without us: define roles, assign responsibilities, train teams, and establish the key metrics that will guide the process going forward. This is the part that’s most often cut when time is tight—and it’s what determines whether the new process will still be in use twelve months from now.
Which of these services your project requires depends on how thoroughly the current situation has been assessed. We can clarify this in a brief conversation.
Four Engagement Scopes for Process Initiatives
Process projects differ less in scope than in the extent to which we are involved: whether we go as far as the target concept, through implementation, or into the period afterward, when a process may gradually fall by the wayside. Our network covers four different scopes; a change in course during the process is the norm, not the exception.
A Clearly Bounded Short Assignment
An experienced professional for a clearly defined task: a process assessment in a specific area, a review of a proposed concept, or a second opinion before selecting a system. Two to six weeks, a clear assignment, a clear result.
Implementation Team With Your People
Two to five external specialists work inside one team with your own people, under internal subject-matter leadership. This is the scope for larger changeovers: the knowledge about the new workflow builds up where it will later be used — instead of leaving the building together with the project.
Process Ownership for a Fixed Period
A person assumes a line or program role for the duration of the project—which is useful when there are vacancies, in special situations, or when decisions regarding process restructuring must be made quickly and with mandate.
Support Beyond the Go-Live
After the rollout, at regular intervals: track key metrics, discuss any deviations, and update the documentation. Just a few days each quarter—this prevents a gradual slip back into old routines.
Process Consulting by Industry: What Drives the Workflow
Administrative workflows look alike on paper and differ considerably in practice. In logistics the shipment sets the pace; at IT service providers it is the ticket process with agreed response times; in healthcare it is the documentation duty attached to the patient case; in public administration it is the binding of deadlines and legal bases. Anyone who does not know what sets the pace designs a target process that breaks at the first exception.
That is why we staff with specialists who have worked in the industry in question and who know its usual evidence duties, systems and role cuts — from ITSM processes along ITIL through quality management to ISO 9001 to approval chains in regulated environments. The selection comes from 25 functional areas with more than 300 role profiles on file. We work regularly in the industries below; each tile names what drives the workflow there.
Logistics & Transport
In logistics, timing is everything: A process that is recorded two hours late costs an entire delivery run. Typical issues include the order workflow from notification to billing, the interface between scheduling, warehousing, and billing, and the question of which data actually needs to be recorded at each stage—and which data is only being recorded because someone requested it at some point.
We track processes using actual shipments, measure dwell times rather than processing times, and eliminate follow-up inquiries resulting from incomplete handoffs. When it comes to the supply chain itself—network design, inventory strategy, and supplier integration—our supply chain consulting services are the right place to start.
IT and Technology Service Providers
For IT and technology service providers, the bottleneck rarely lies in the technology itself, but rather in the surrounding service processes: clearly separated incident, change, and problem management; a request workflow that doesn’t start in three different places at once; and a release process that doesn’t hide agreements in chat histories. ITIL provides the framework for this—the key is determining how much of it fits the size of the organization.
We align service processes with what was actually promised to customers, clarify escalation paths, and define the metrics used to verify those commitments. You’ll find relevant profiles in the IT Service Management section.
Healthcare & Pharmaceuticals
In the healthcare sector and the pharmaceutical industry, strict documentation requirements clash with limited staff time. The administrative workload—intake, scheduling, documentation, billing, and approvals—ties up capacity that is lacking elsewhere. At the same time, no simplification should come at the expense of documentation required by regulations.
We therefore take a two-step approach: first, we distinguish between what is mandatory and what is merely routine; then, we integrate the mandatory elements into the workflow so that they are completed as part of the process rather than having to be caught up on at the end of the day. We treat validated processes and quality-related documentation as a separate category with its own approval logic.
Banking & Insurance
For banks and insurance companies, the process is the product: application, review, decision, contract, claim. Regulatory requirements create checkpoints, and each checkpoint creates a handoff. The typical observation is not that too much is being checked, but that the same information is being collected three times.
We redesign the workflow around these checkpoints rather than bypassing them: automated processing for clear-cut cases, defined exception paths for the rest, and traceable documentation that stands up to scrutiny. We incorporate statements regarding regulatory requirements into this framework—their binding assessment in individual cases remains the responsibility of your legal and compliance functions.
Public Administration
In public administration, processes are legally defined yet still flexible: the sequence of steps, responsibilities, media transitions, and the question of where a document is actually needed are left to our discretion. This is precisely where the majority of processing time is spent—not on the technical review.
We map application and decision-making processes end-to-end, distinguish between legally required steps and established practices, and describe the target process in a way that serves as a solid foundation for implementing a specialized workflow. The goal is not to reduce diligence, but to minimize the time spent waiting between each careful step.
Energy & Utilities
Energy and utility companies operate using high-volume processes governed by market rules: switching suppliers, meter reading processing, billing, and grid connection. The volume of cases is high, deadlines are set externally, and a single process error isn’t just costly—it multiplies ten thousandfold.
Here, we rely more on key metrics than on workshops: the rate of cases requiring clarification, deadline violations, and manual rework show very precisely where the workflow breaks down. This analysis leads to standardization, clear exception handling, and the decision as to which cases requiring clarification can be automated and which must be reviewed by a person.
Logistics & Transport
In logistics, timing is everything: A process that is recorded two hours late costs an entire delivery run. Typical issues include the order workflow from notification to billing, the interface between scheduling, warehousing, and billing, and the question of which data actually needs to be recorded at each stage—and which data is only being recorded because someone requested it at some point.
We track processes using actual shipments, measure dwell times rather than processing times, and eliminate follow-up inquiries resulting from incomplete handoffs. When it comes to the supply chain itself—network design, inventory strategy, and supplier integration—our supply chain consulting services are the right place to start.
IT and Technology Service Providers
For IT and technology service providers, the bottleneck rarely lies in the technology itself, but rather in the surrounding service processes: clearly separated incident, change, and problem management; a request workflow that doesn’t start in three different places at once; and a release process that doesn’t hide agreements in chat histories. ITIL provides the framework for this—the key is determining how much of it fits the size of the organization.
We align service processes with what was actually promised to customers, clarify escalation paths, and define the metrics used to verify those commitments. You’ll find relevant profiles in the IT Service Management section.
Healthcare & Pharmaceuticals
In the healthcare sector and the pharmaceutical industry, strict documentation requirements clash with limited staff time. The administrative workload—intake, scheduling, documentation, billing, and approvals—ties up capacity that is lacking elsewhere. At the same time, no simplification should come at the expense of documentation required by regulations.
We therefore take a two-step approach: first, we distinguish between what is mandatory and what is merely routine; then, we integrate the mandatory elements into the workflow so that they are completed as part of the process rather than having to be caught up on at the end of the day. We treat validated processes and quality-related documentation as a separate category with its own approval logic.
Banking & Insurance
For banks and insurance companies, the process is the product: application, review, decision, contract, claim. Regulatory requirements create checkpoints, and each checkpoint creates a handoff. The typical observation is not that too much is being checked, but that the same information is being collected three times.
We redesign the workflow around these checkpoints rather than bypassing them: automated processing for clear-cut cases, defined exception paths for the rest, and traceable documentation that stands up to scrutiny. We incorporate statements regarding regulatory requirements into this framework—their binding assessment in individual cases remains the responsibility of your legal and compliance functions.
Public Administration
In public administration, processes are legally defined yet still flexible: the sequence of steps, responsibilities, media transitions, and the question of where a document is actually needed are left to our discretion. This is precisely where the majority of processing time is spent—not on the technical review.
We map application and decision-making processes end-to-end, distinguish between legally required steps and established practices, and describe the target process in a way that serves as a solid foundation for implementing a specialized workflow. The goal is not to reduce diligence, but to minimize the time spent waiting between each careful step.
Energy & Utilities
Energy and utility companies operate using high-volume processes governed by market rules: switching suppliers, meter reading processing, billing, and grid connection. The volume of cases is high, deadlines are set externally, and a single process error isn’t just costly—it multiplies ten thousandfold.
Here, we rely more on key metrics than on workshops: the rate of cases requiring clarification, deadline violations, and manual rework show very precisely where the workflow breaks down. This analysis leads to standardization, clear exception handling, and the decision as to which cases requiring clarification can be automated and which must be reviewed by a person.
Process Initiatives and Their Success Metric
A few recurring types cover the majority of what is actually commissioned in process projects. Each one is associated with a metric that is agreed upon in advance—without it, the evaluation of a process project boils down to opinions about whether it feels better than before.
Preparing a System Rollout or ERP Change
Starting point: a new system is coming, and the question “how do we actually do this today?” has no answer. We settle target processes and master data logic before the configuration instead of deciding both inside customizing. Measured by the number of special requirements filed after go-live and by the time to stable operation.
Building a Process Map and Documentation
Starting point: knowledge sits with individuals, onboarding takes months, and an absence brings a case to a halt. We build the process map, document the core processes in a form that gets maintained, and name the owners. Measured by the onboarding time of new colleagues and by how many processes are still current twelve months later.
Standardizing Workflows Across Sites
Starting point: after growth or an acquisition, two units handle the same case differently and the key figures are not comparable. We work out which differences are genuinely required, standardize the rest, and fix what may be decided locally. Measured by comparable figures per site and by the effort for consolidated reporting.
Automating an Approval or Request Process
Starting point: a case travels through several mailboxes and its status can only be found by asking. We simplify the workflow first, digitalize it second, and automate only the steps whose upkeep pays for itself. Measured by throughput time, query rate and the share of cases that pass through without manual intervention.
From Process Mapping to Process Governance: Frequently Staffed Profiles
Map, Organize, Embed: How a Process Initiative Runs
It starts with observing the actual process and ends with embedding it in the workplace—the step that is most often skipped and that determines whether the new process will take root. The duration and depth depend on the number of departments and the level of documentation, but the sequence does not: A target process without a solid foundation is nothing more than a guess backed by a flowchart.
1. Process Mapping
2. Analysis and Prioritization
3. Target Process and Responsibilities
4. Implementation and Enablement
5. Measuring and Adjusting
6. Embedding in Daily Operations
From Daily Rate to Budget: What Process Consulting Costs
A process initiative can be budgeted in three stages, and each stage has its own order of magnitude. The mapping stage — bounding the scope, recording the as-is workflow along real transactions, evidencing times and system breaks — is the smallest one and the only one that can be planned precisely in advance. The target process — modeling, accountabilities, key figures, approval logic — depends on how many units the workflow crosses: for a process spanning three departments, the alignment weighs more than the modeling. Implementation is the most open stage, because it follows not the process but the systems, roles and habits that are changed along with it. Anyone who prices all three stages up front in a single sum prices the third one wrong. It is more robust to decide again after the mapping — by then there is recorded evidence instead of an estimate.
Billing is per day rate. The ranges below are the ones published on our own role pages (as of August 2026); they are orientation, not a quotation. Profiles for mapping and process documentation sit at the lower end:
- Freelance Process Improvement Manager: €650 – €1,100
- Freelance Quality Manager: €650 – €1,150
- Freelance Lean Manager: €700 – €1,200
- Freelance Six Sigma Black Belt: €750 – €1,300
- Freelance Operations Manager: €750 – €1,300
- Freelance ITSM Process Consultant: €750 – €1,050
- Freelance ITIL Consultant: €750 – €1,100
- Freelance IT Governance Consultant: €750 – €1,100
- Freelance IT Change Manager: €700 – €1,000
- Freelance ERP Change Manager: €700 – €1,300
- Freelance Change Management Consultant: €800 – €1,400
- Freelance Business Transformation Consultant: €900 – €1,600
Within these ranges four things move the rate: whether somebody describes a workflow or pushes it through against resistance; how tightly the initiative is bound to a system, because ERP, ITSM or industry software knowledge narrows the pool of eligible specialists; whether evidence has to stand up to third parties, in an audit, a certification or a regulator; and whether the work is done on site or distributed. All figures are net, plus VAT and, where presence is required, travel costs.
A one-off analysis or a supported rollout — this is where the larger cost question sits. An analysis ends with a finding and a recommendation. It is plannable, available in the low double digits of days, and on its own it produces no change. A supported rollout ties up part of a person’s capacity over months, often two to three days a week, and costs a multiple of that — in exchange it shifts the risk: what is paid for is that the new workflow arrives in daily operations, not that it has been described. Anyone commissioning the analysis alone should have settled beforehand who takes on the rollout internally.
Which staffing a process initiative needs depends on the maturity of the documentation. An overview of the roles we staff in process initiatives sits in the Operations & Production area; process-related IT roles are listed under IT Service Management, roles for organizational change under Transformation & Change Management. If you are looking for a process consultant or a business process consultant for a clearly bounded task, entering through the role pages is usually faster than through this one. Where several initiatives have to be steered in parallel, the profiles under Project Management are the better starting point; the discipline itself we describe under project management consulting.
Those Who Do Not Actively Maintain Their Workflows Get Slower Without Doing Anything Wrong
€64bn
€146bn
+€16.8bn
Frequently Asked Questions About Process Consulting
A daily rate is not an extrapolated hourly wage, but rather the price for one day of work, including preparation and follow-up. Three factors determine this rate: the rarity of the desired profile, the level of responsibility associated with the role, and the duration of the mandate—longer-term mandates generally have a lower daily rate than short-term mandates, where the ramp-up period is limited to a few days. In our portfolio for process projects, the reported ranges extend from €650 to €1,600 per day. The range for each specific role is listed on its role page; the rate for a specific assignment is agreed upon before it begins and does not change during the assignment period.
It’s the daily rate that’s comparable, not the model behind it. A management consulting firm calculates a team and allocates experience accordingly: a few senior days, many junior days, resulting in an average. Through an expert network, you book the expertise directly—the per-person rate is higher, the number of days is lower, and there’s no need to train an entire team on your industry. For a clearly defined process, the comparison therefore usually favors the network. For a multi-year program spanning many locations and countries, however, the project management capabilities of a single firm—which we deliberately do not offer—are a stronger argument in its favor.
Excellent. We are not the only ones who think so.
consultingheads has received several awards from leading trade magazines and independent third parties.