Whitepaper · Artificial Intelligence in the Trades
How HVAC and plumbing firms can use artificial intelligence to relieve the office, the service department and the job site
Artificial intelligence will not replace the service technician. But it can ensure that less working time is lost to phone notes, follow-up questions, document searches, quote preparation and recurring office work.
This whitepaper shows which applications are realistic in an HVAC and plumbing firm today, which prerequisites they require, where the limits lie, and how a firm can start with a contained pilot project. It is written for managing directors, operations and service managers, commercial leads and anyone responsible for digitalisation.
Overview
The whitepaper is designed as a working document. The first two parts frame the topic, the third part describes eleven use cases along the order chain, and the fourth part provides tools for making and implementing a decision. Anyone who already knows where time is lost in their firm can jump straight to Part III.
Every market figure in this whitepaper is sourced and drawn from publicly available publications by the German plumbing and heating association (ZVSHK), the Federal Statistical Office, Bitkom Research, KfW Research, the German Federal Office for Information Security (BSI) and the European Commission. The cost-effectiveness calculations from page 25 onwards are expressly model calculations based on freely chosen assumptions. Their purpose is to make the reasoning transparent; they are not guaranteed savings.
Management summary
Public debate about artificial intelligence often revolves around autonomous systems, robots or fully automated companies. For a plumbing, heating and air-conditioning firm, the short-term benefit lies somewhere else entirely.
AI is particularly good today at taking in information, structuring it, summarising it and preparing it for the next step in the process. That is precisely where many firms suffer avoidable friction. It is rarely spectacular. But it costs time every day, and it hits exactly the people who are hardest to replace.
In all of these situations, AI can prepare work, organise information and flag missing details. It should not, however, issue technical approvals on its own, nor make binding designs, prices or safety-relevant decisions without oversight. That dividing line runs through the entire whitepaper.
An HVAC and plumbing firm should not begin with a broad question such as "Where can we use AI?". That question almost always leads to a discussion about tools and rarely to a result. A far more productive starting point is:
"Where do our staff regularly lose time because information is missing, has to be entered more than once, or has to be searched for again and again?"
Anyone who can answer that question for their own firm has already done the hardest part of an AI project. Everything that follows – selection, testing, integration, oversight – is craft in the best sense: it can be planned, checked and, if necessary, corrected.
The five key messages
Call handling, order preparation, documentation, knowledge access and customer communication offer improvements that are easier to reach than highly complex technical applications. They are less glamorous, but they are measurable and can be implemented with limited risk.
An unclear workflow does not become better through AI. Often the technology merely accelerates the existing chaos and produces the same gaps faster and in greater numbers. If you have no rule for what a fault report must contain, a phone AI will not give you complete fault reports either.
A sensible pilot solves a concrete problem: incomplete fault reports, late technician reports, quotes left unfinished. If you do not know the baseline, you cannot demonstrate the benefit later and will end up judging the project on gut feeling.
AI can supply suggestions. Assessing an installation, choosing a technical solution and approving a quote remain tasks for qualified staff. That responsibility cannot be delegated to a vendor or a model – and in warranty terms it cannot be delegated at all.
Customer addresses, floor plans, photos from private homes, consumption data and technical system information must not be transferred uncontrolled into arbitrary AI services. Since 2 August 2026, firms using AI in customer-facing contact also have a transparency obligation under the EU AI Act.5
These five statements are deliberately unspectacular. Digitalisation projects in the trades rarely fail on the technology; they fail on unclear responsibilities, missing data and the expectation that a tool can replace a decision.
Market situation
Germany's plumbing, heating and air-conditioning trade closed 2025 at a high level, but with slowing momentum. Orders and utilisation declined, and the business is increasingly carried by repair and maintenance rather than genuine modernisation work. The service and maintenance business, by contrast, remained a reliable revenue pillar. The industry association points to political uncertainty around the building energy act and the subsidy landscape as the central brake; it expects no fundamental turnaround for 2026.1
At the same time, the technology in the installed base is shifting. With around 299,000 units sold, the heat pump was the best-selling heating technology of 2025 for the first time.2 For firms this means not only new products but, above all: more advisory effort, more coordination with electrical and building trades, more documentation and more follow-up questions.
A firm cannot replace missing service technicians with a language model. But it can try to relieve the skilled staff it has of tasks that do not require a master craftsman, a technician or an experienced service engineer. It is precisely in that gap – between what genuinely requires expertise and what is merely legwork – that the realistic contribution of AI lies.
Why the topic matters now
In the German trades, only 4 per cent of the firms surveyed currently use AI, with a further 9 per cent planning to. At the same time, 35 per cent believe that early adoption can create a competitive advantage, and 33 per cent expect AI to fundamentally change business models in the trades. Only 29 per cent of trade firms say they have staff who can work with AI.3
They do not indicate broad maturity but an early market stage. For an HVAC and plumbing firm this means: there is no obligation to adopt every new application immediately. But there is a window in which well-organised firms can gather experience at their own pace, before customers, manufacturers and software vendors set the standards.
In 2025, 26 per cent of German companies with at least ten employees used AI. Among companies with 10 to 49 employees the figure was 23 per cent, among those with 50 to 249 employees 36 per cent, and among large companies with 250 or more employees 57 per cent.4 The most common reasons cited against adoption were a lack of knowledge (72 per cent), uncertainty about the legal consequences (62 per cent) and data-protection concerns (60 per cent).4
Across the wider German SME sector (the "Mittelstand"), adoption stands at 20 per cent according to a special analysis of the KfW SME Panel – equivalent to just under 780,000 companies, a fivefold increase within six years. What matters is less the size than the environment: companies with research and development activity and pronounced digitalisation activity use AI significantly above average. Companies with neither graduates on staff nor any innovation activity use AI with a probability of just 8 per cent.6
| Population | Share using AI | Source |
|---|---|---|
| Trade firms in Germany | 4 % | Bitkom Research 20253 |
| SME sector overall | 20 % | KfW Research 20266 |
| Companies with 10+ employees | 26 % | Destatis 20254 |
| Companies with 10 to 49 employees | 23 % | Destatis 20254 |
| Companies with 50 to 249 employees | 36 % | Destatis 20254 |
The figures are not directly comparable: population, survey period and the definition of AI differ considerably between studies. The gap between 4 per cent in the trades and 26 per cent in the economy as a whole is nonetheless clear enough to serve as a directional signal.
Success is decided not by firm size but by orderly processes, digitally available information, clear responsibilities, a concrete use case, sufficient data quality and acceptance in the office and on the job site alike. The advantage comes not from buying a tool but from better processes, well-maintained data and trained staff.
Clarifying the terms
In day-to-day operations, very different things are grouped under the label "AI". For an investment decision the distinction is worth making, because effort, benefit and risk differ markedly from one category to the next.
A fixed rule triggers a known process. The software interprets nothing; it simply executes.
Example: when a maintenance job is closed, the customer automatically receives an email with the maintenance report.
A language model creates or edits texts, summaries, replies or structured data sets.
Example: a technician's voice note becomes a structured service report listing work carried out, materials and open points.
The application recognises speech, text, images or document content and converts it into data fields.
Example: a system reads manufacturer, type and serial number from a photo of a rating plate. The details are then checked by an employee.
The AI draws on approved company documents and answers on the basis of those sources, citing them.
Example: "Which documents do we need before replacing a gas boiler in a rented multi-family building?"
An agent carries out several steps and uses other systems along the way. For instance, it takes a fault report, checks the customer data in the trade software, requests missing details, drafts an order and proposes an appointment.
Such an agent must not operate with unlimited rights. Write access, appointment bookings, orders and customer messages require defined limits and control points. The decisive question with an agent is not "What can it do?" but "What may it do without asking – and how do we notice when it gets it wrong?".
Vendors often use the word "AI" as a selling point for functions that are, at their core, classic automation – and conversely for generative systems whose output needs checking. A fixed rule is predictable. A language model is not. Both can be correct. Only the required control mechanisms differ fundamentally.
A practical classification
The following classification orders AI applications not by technology but by depth of intervention. The further down the table, the greater the potential benefit – and the greater the effort required for integration, permissions and oversight.
| Level | Function | Example | Risk |
|---|---|---|---|
| 1 | Text support | Draft an email, report or customer note | low |
| 2 | Structuring | Turn a phone or voice note into order data | low to medium |
| 3 | Knowledge access | Search internal documents, checklists and manuals | medium |
| 4 | System integration | Prepare an order in the trade software, transfer data | medium |
| 5 | Semi-autonomous execution | Book appointments, send messages, request materials | elevated |
| 6 | Professional decision | Independently define and approve a technical solution | unsuitable for most cases |
For most HVAC and plumbing firms the commercially sensible entry point currently lies at levels 1 to 3. Level 4 can follow once processes, interfaces and responsibilities work reliably. Level 5 assumes that errors can be detected and undone before they reach the customer. Level 6 is not a realistic goal in the HVAC and plumbing trade, for both professional and liability reasons.
Many firms try to enter directly at level 4 or 5 because a vendor's demonstration was impressive. The outcome is regularly the same: the project gets stuck on interfaces, permissions and data quality, ties up management time and ends without a result. Afterwards "AI doesn't work for us" becomes the verdict in the firm – and the simple, effective levels 1 to 3 are buried along with it.
Analysis
A typical HVAC and plumbing job passes through ten stations. At each one, information is handed over – and it is precisely at these handovers that the errors arise which cost time later on.
1 Enquiry or fault report · 2 Qualifying the request · 3 Scheduling or on-site survey · 4 Costing and quote · 5 Materials planning · 6 Job planning · 7 Installation or service · 8 Documentation and handover · 9 Invoicing and follow-up · 10 Maintenance, repeat business and customer retention
The customer reports "the heating isn't working". Missing: manufacturer and model, fault code, time of the failure, hot-water status, noises or smell, access, type of property, on-site contact, and any note on previous work.
The technician receives an appointment, but no photos, no system history and no information about what has already been discussed with the customer. On site, they start by re-establishing what the office already knew.
The job is done, but material items are missing, an extra service is undocumented, photos sit on a private phone, readings are handwritten, the customer's signature is missing, and a follow-up quote was never triggered.
Quote items, manufacturer documents, delivery times and alternative products are searched for across several systems. The same research is carried out repeatedly over the year by different people.
The experienced service engineer knows typical fault patterns, the weaknesses of certain equipment generations and the peculiarities of individual buildings. None of this is documented anywhere. It is available to the firm only for as long as this person is reachable – and it retires with them.
Suitability screening
A process is especially well suited to AI support when several of the points below apply. Rule of thumb: the more ticks, the more a pilot is worthwhile. Fewer than five ticks is a sign that the process, not the tool, is the first order of business.
If almost every job is individual and requires intensive professional advice before it can even be taken on, the AI finds no pattern to work from.
If system histories, stock or master data are not maintained, even the best application can only offer a plausible guess – and in a technical context that is dangerous.
If the workflow includes no point at which a human sees the result before it takes effect, the use case is too early for AI.
A workflow that occurs twelve times a year almost never pays off – regardless of how annoying it is in the individual case.
For two weeks, have every follow-up question noted that arises because information was missing. Just two columns: what was missing, and who had to ask. This list is usually more informative than any consultancy – and it provides the baseline for the later pilot at the same time.
Use case 1
From a missed call to a structured job.
In an HVAC and plumbing firm the telephone is the central customer interface – and at the same time the biggest source of interruption. Calls come in while staff are working on quotes, ordering materials, coordinating technicians, checking invoices, serving customers at the counter or out on a job themselves. On a Monday morning and after the first frost, this multiplies.
An AI-supported phone assistant can take calls outside business hours or when the line is busy. What matters is not that a synthetic voice sounds as human as possible. What matters is whether usable, complete information reaches the firm in the end – and whether the customer felt taken seriously.
It is standardisation. A phone assistant asks the same nine points on the 40th call of the day as on the first – including at 4:45 p.m. on a Friday. That is exactly the point at which human handling under load regularly slips. Not through carelessness, but because the third phone is ringing at the same time.
Use case 1 · continued
An AI phone assistant must not issue a remote diagnosis as a firm statement, must not quote prices and must not promise appointments that dispatch has not confirmed. In the event of a gas smell, water leak, fire risk or comparable hazard, a fixed safety message must apply – as a rigid rule, not as a language model's free interpretation. This flow must be tested before the system goes live.
Anyone using AI in direct customer contact must disclose that the caller is speaking with an AI system. The corresponding transparency obligations of the EU AI Act (Article 50) have applied since 2 August 2026.5 The notice belongs at the start of the call and in the privacy information – not in the small print.
| Metric | What it tells you |
|---|---|
| Share of answered calls | Reachability from the customer's perspective |
| Missed calls per week | Order potential lost outright |
| Call-back time (median) | Perceived responsiveness |
| Completeness of fault reports | The pilot's core metric |
| Share of avoidable follow-up questions | Friction between office and customer |
| Mis-classified jobs | Quality of the priority rules |
| Feedback from customers and office | Acceptance – the most common reason for abandonment |
Use case 2
Not every enquiry needs an on-site appointment straight away.
Many firms lose time because enquiries are treated as orders too early. Only later does it turn out that important prerequisites are missing – and by then with a site visit, a survey and an afternoon of costing already behind them.
AI-supported enquiry qualification can gather information via a web form, phone or email, check it for completeness and prepare it for the office. It does not replace advice – it ensures that the advice starts with complete information.
Property address · building type · year of construction · heated area · existing heat generator · age of the system · energy source · heating surfaces · hot-water provision · known consumption figures · state of renovation · photos of the plant room, rating plate and distribution · desired timeframe · subsidy status · customer availability
These details produce no reliable technical plan and no heat-load calculation. The AI can identify which details are missing and generate a structured preparation file. The professional assessment begins afterwards.
Suitable when the firm receives many similar enquiries and can specify the initial information required.
Less suitable when almost every job is individual and requires intensive professional advice before it can even be taken on.
Use case 3
From scattered information to a checkable basis for a quote.
Preparing quotes is one of the most time-consuming commercial-technical tasks in an HVAC and plumbing firm. It becomes especially demanding when information has to be brought together from a survey, site photos, customer emails, plans, a schedule of works, a manufacturer quote, wholesale terms, technician notes, earlier comparable quotes and subsidy requirements. That this work happens in the evening in many firms is no accident: it requires uninterrupted concentration.
This rule is not distrust of the technology. It follows from the fact that a quote is a legally binding document. A language model does not bear liability. The firm does.
Worked example
For a heat-pump enquiry, a firm receives the following documents: a customer email, the consumption bills from the last three years, photos of the existing system, a heat-load calculation from a planner, a floor plan and the manufacturer's product documents. Six sources, three formats, one job.
The master craftsman checks the technical plausibility: does the proposed heat pump match the calculated heat load? Are the heating surfaces suitable for the required flow temperature? What about the electrical panel? The estimator produces the commercial assessment. The AI replaces none of these steps. It reduces the effort of reviewing, sorting and structuring – that is, the part that previously took almost an hour without being professionally demanding.
Incomplete details are adopted as facts. If the customer email says "underfloor heating is present", the AI does not know whether that applies to the whole house, the ground floor or only the bathroom. The application must therefore be set up to flag unclear statements rather than smooth them over. A draft that honestly shows gaps is more valuable than one that merely looks complete.
That capturing the installed base is a worthwhile area for digitalisation in the HVAC and plumbing trade is also borne out by research. In the BMBF-funded DiBesAnSHK project (running from 09/2021 to 08/2024), the Fraunhofer Institute for Solar Energy Systems ISE, together with industry partners, developed a method that captures heating components using off-the-shelf smartphones and tablets, classifies them via image recognition and feeds them into a system configurator – with the aim of enabling on-site survey and rapid quotation.7 In the ongoing WESPE project, the approach is being transferred to heat-pump conversions.8
The potential is considerable. In practice, however, quality depends on the image, the installation situation, the equipment generation and the available data. A cramped rating plate in a dark plant room remains a cramped rating plate in a dark plant room.
Use case 4
Better preparation rather than fully automated route planning.
AI can support dispatch when sufficient data is available: staff qualifications, job location, expected duration, required spare parts, van stock, urgency, promised time windows, dependencies on other trades, access conditions, maintenance contracts and emergency-service rules.
Dispatch AI should therefore first produce suggestions and flag anomalies. Binding planning stays with the dispatcher. Their knowledge of customers, buildings and staff is the part that appears nowhere in the system – and it decides the quality of the day.
With several service vans, many short-notice fault call-outs, recurring maintenance appointments, a large service area and frequent rescheduling. For a small firm with two technicians and close personal coordination, clean digital job planning is usually entirely sufficient – the added value of an AI would be hard to demonstrate there.
The most valuable function in this use case is frequently not the planning at all, but the extraction of open points from technician reports. "Thermostat in the bathroom still needs replacing" sits in the free text of many reports in many firms – and is never read again. Anyone who systematically finds these sentences and turns them into a follow-up entry recovers revenue that has already been earned.
Use case 5
Documenting without writing up reports after hours.
Voice-based documentation is one of the most obvious AI applications in the HVAC and plumbing trade – because it starts exactly where the work already happens and creates no additional screen time.
"At the Müller property, the gas condensing boiler was checked. Fault code 227. Ionisation electrode dirty, cleaned and burner inspected. System back in operation. Flue-gas readings within range. Condensate drain was partly blocked and has been cleared. Customer advised that the service was overdue. Recommendation: offer an annual maintenance contract."
From this note the system produces work carried out, cause identified, materials used, readings, customer advice, follow-up recommendation, billable items and an internal note – each in separate fields rather than in a flowing text that someone later has to take apart.
System and starting situation · fault pattern · inspection · cause · work carried out · materials · readings · customer information · open points · follow-up job
The German plumbing and heating association is developing a voice-controlled AI assistance system in the MEISTERWÄRME research project, which supports fault diagnosis in an automated way and optimises service processes in heating maintenance. The project began on 1 May 2025, runs for 36 months, is funded with around EUR 4.6 million and brings together five partners from the association, research, IT development and an HVAC and plumbing master firm.9 Voice-based support is therefore no longer a vendor promise but a recognised field of development within the sector itself.
Use case 6
When the right information exists but cannot be found.
Most HVAC and plumbing firms hold extensive knowledge: installation manuals, manufacturer information, maintenance checklists, price lists, work instructions, references to standards, safety briefings, templates, technical data sheets, earlier quotes, system histories and experience. The problem is rarely a shortage of documents. The problem is their distribution – across drives, mailboxes, folders, messenger groups and people's heads.
A knowledge-based assistant searches only approved documents and answers questions with a source reference. That source reference is precisely the difference between a useful tool and a well-worded risk.
When outdated and current documents sit side by side, filenames say nothing, responsibilities are missing, versions are not marked, sensitive documents are accessible without authorisation, or essential information exists only verbally. An assistant that cites a withdrawn work instruction is worse than no assistant at all – because it is believed.
| Level | Meaning |
|---|---|
| Confirmed answer | The statement is backed by current, approved sources; the source is named. |
| Indication | The sources contain relevant information but leave room for interpretation. |
| No reliable answer | There is no sufficient or current basis. |
Use case 7
Assistance for the expert, not a substitute for expertise.
AI can support fault-finding when it can access suitable information: fault code, equipment type, system history, readings, manufacturer documents, checks already carried out, known fault patterns and maintenance status. From this it can suggest possible causes, a sensible testing sequence or the right document.
It does not know the actual state of the system. It does not know installation errors, the local hydraulics, the electrical readings, changes made by other trades, and certainly not undocumented modifications. It can therefore supply a hypothesis but never a finding. In the field, the difference is not academic: turning up with the wrong spare part means a day lost.
Not in the diagnosis itself, but in access to what the firm has already solved. If, faced with a fault pattern, a technician can see that a colleague had the same problem on an identical system seven months ago and how it ended, that saves more time than any list of causes from a language model. The prerequisite, though, is that the colleague documented it at the time – see use case 5.
Use case 8
Less searching, fewer unnecessary trips.
Material problems cause considerable knock-on costs in the field: missing spare parts, wrong items, undocumented withdrawals, overloaded vans, obsolete stock, unresolved returns and spontaneous trips to the wholesaler. Every one of those trips costs not only diesel but an appointment.
Without an interface to inventory and supplier data, it remains at the level of recommendations.
A firm analyses twelve months of field jobs. The analysis shows which small parts are needed particularly often, which fault patterns regularly cause extra trips, which items are constantly reordered, which stock is barely used – and which technicians use different materials for the same standard case.
From this, a coordinated basic stock per van emerges. This is not a spectacular AI application. It is an analysis that never happens in many firms, because no one has the time to look through twelve months of order data.
This analysis requires that materials were recorded against the job. Anyone who bills small parts as a flat rate or does not book withdrawals will receive an analysis of booking discipline – not of material demand. In that case the right first step is not AI but a decision on how materials will be recorded in future.
Use case 9
Complete records are part of the value created – not its afterthought.
A technically flawless job can become a commercial problem if the documentation is incomplete. Extra work goes unbilled, the client disputes the scope, photos are missing, deviations from the order are undocumented, concerns were raised only verbally, commissioning documents are incomplete, the invoice cannot be issued – and in the event of a complaint the job history is missing.
From voice notes and site reports, the AI can detect indications of extra work. A sentence such as
"Concealed cable was unusable contrary to the plan. Additional core drilling required."
leads to an internal note: Possible variation – commercial review required. The AI should on no account send a binding variation on its own. Whether a variation is justified and enforceable is decided by the contract, not by sentence structure.
Of all eleven use cases, this is the one with the most direct link to the result: a completeness check that finds one forgotten extra service per week has, in many firms, already paid for itself on paper before anyone has even mentioned time savings.
Use case 10
Explaining technical matters clearly.
HVAC and plumbing firms communicate daily with very different counterparts: private owners, tenants, property managers, architects, energy consultants, developers, commercial clients, municipalities and care facilities. Not every recipient understands terms such as spread, heating curve, hydraulic balancing, return temperature or flow rate. And not every technician has the patience to translate them at 6 p.m.
From the technical report, a clear explanation emerges: "The system shut down because the condensate drain was partly blocked. We cleared the drain, checked the system and returned it to operation. To avoid similar faults, we recommend regular maintenance."
The AI prepares an overview: starting situation, proposed solution, necessary ancillary works, points the customer must provide, a possible sequence and outstanding decisions. The customer then knows what to expect – which reduces follow-up questions and rescheduling.
The application produces a matter-of-fact message based on the actual reason, without the employee having to word it afresh each time. A clear, early cancellation is better than a late apology.
Complaints, liability questions, deadlines, formal notices of concern and legally relevant statements must not be sent without review. A politely worded sentence can give up a legal position the firm never intended to give up. The AI writes well. It does not know what is at stake.
Use case 11
Good work is not enough if it cannot be found online.
Customers increasingly inform themselves online before contacting an HVAC and plumbing firm. Personal recommendations remain important, but they are supplemented by search engines, map services, reviews and, increasingly, AI-supported answer systems. Anyone who does not appear in these systems, or appears with contradictory details, is simply not considered.
In the Bitkom survey of the trades, 85 per cent of firms stated that they offer at least one digital service – such as online appointment booking, online advice or electronic invoicing. Messenger services are used by 62 per cent and online meetings by 36 per cent.3 The basic equipment is therefore in place. The difference arises in consistency.
Arbitrary bulk text creates no credible positioning. A firm does not become visible by publishing a hundred similar pages – neither with search engines nor with AI systems, which increasingly look for verifiability.
Good content needs real services, concrete service areas, expertise, own photos and projects, identifiable contacts, clear contact details, genuine reviews and consistent information across all platforms.
AI can prepare job adverts and content. But the real advantage only emerges when the firm credibly shows what technology it uses, how training is organised, what development opportunities exist, how site and office work together, and what values apply. According to the Bitkom study, more than half of the training firms in the trades let their own apprentices help them with digitalisation.3 That is a remarkable finding: the next generation often brings the competence with them – if the firm lets them.
Where to draw the line
Not every technically possible application makes business sense. The following seven applications call for particular caution – not as a matter of principle, but because errors there are expensive, hard to detect or legally relevant.
Heat-load calculation, pipe-network and drinking-water planning, or sizing without professional review and approval.
Prices depend on purchasing, installation effort, site conditions, risk, utilisation and customer agreement. These factors cannot be reliably derived from free text.
Rules change, not every source is current – and a language model states a wrong rule just as convincingly.
Whether there is a defect, an operating error, third-party interference or a warranty case requires a professional and, where applicable, legal assessment.
AI for performance evaluation, behaviour analysis or automated staffing decisions is sensitive in employment-law terms and regularly falls into the high-risk category under the EU AI Act.5
Staff should not copy customer documents, photos, contracts or costings into freely available services on their own initiative.
Automatically triggered orders can cause considerable costs if wrongly assigned – and they only come to light when the invoice arrives.
"Please show me what happens when your system misunderstands something." Vendors who answer this with confidence have thought about failure cases. Vendors who dodge it have not.
Cost-effectiveness
Monthly benefit = processing time saved × the firm's fully loaded cost rate + error costs avoided + additional contribution margin − ongoing operating costs (licence, usage, integration, upkeep, quality control)
The three examples below are model calculations based on freely chosen assumptions. They show the calculation method, not a guaranteed result. Use your own case numbers and cost rates – a firm with 200 calls a month reaches a different decision from one with 600.
600 relevant calls per month, on average 2 minutes less office time per call through structured pre-qualification.
600 × 2 min = 1,200 min = 20 hours
20 h × EUR 45/h = EUR 900 per month
8 field technicians, 10 minutes saved per working day, 20 working days.
8 × 10 × 20 = 1,600 min ≈ 26.7 hours
26.7 h × EUR 55/h ≈ EUR 1,467 per month
80 quotes per month, 15 minutes saved per quote through structured preparation.
80 × 15 min = 1,200 min = 20 hours
20 h × EUR 60/h = EUR 1,200 per month
Minutes saved appear in no set of accounts. They only become economic when the freed-up time is actually used to handle more jobs, issue invoices faster, clear backlogs, reduce overtime, serve additional customers or relieve expensive skilled staff.
Anyone who saves 20 hours a month and then produces the same revenue with the same overtime has gained nothing but a slightly calmer office. That is not worthless – but it is not a business result, and it should not be sold as one.
In practice, the greater lever often lies not in time but in what is currently simply lost: the extra service that is not billed, the missed call on a Monday morning, the follow-up quote that was never written, the invoice that goes out three weeks late. These effects are harder to quantify – but they are the ones that make the difference.
Prioritisation
| Criterion | Weight | Your score 1–5 |
|---|---|---|
| Frequency of the process | 20 % | ___ |
| Time required today | 20 % | ___ |
| Error and follow-up-question rate | 15 % | ___ |
| Availability of digital data | 15 % | ___ |
| Scope for human oversight | 10 % | ___ |
| Integration effort (score inversely) | 10 % | ___ |
| Staff acceptance | 10 % | ___ |
Use cases with high frequency, good data and low risk belong at the front. Integration effort is scored inversely: low effort yields a high score.
Typical bottlenecks: the managing director works operationally, the phone interrupts ongoing tasks, quotes are left unfinished, knowledge sits with a few people.
Suitable entry points: email and text assistance, structured phone notes, voice documentation, a central knowledge store, quote checklists.
Less suitable: complex agent systems, extensive custom development, elaborate data platforms.
Typical bottlenecks: handovers between office and technicians, dispatch, incomplete reports, quote backlogs, inconsistent workflows.
Suitable entry points: AI phone assistant, enquiry qualification, documentation-driven invoicing, a knowledge assistant, quote preparation, follow-up-job detection.
Typical bottlenecks: several teams and sites, complex permissions, varied process variants, extensive document holdings, high integration needs.
Suitable entry points: company knowledge with role permissions, integrated service assistance, analysis of order and service data, automated quality checks, AI-supported dispatch, standardised customer communication.
1. Which bottleneck causes the greatest effort today? · 2. How often does the process occur? · 3. What data is available digitally? · 4. Who is responsible for the professional quality? · 5. What happens if the answer is wrong? · 6. Can a member of staff check the result before use? · 7. What software needs to be connected? · 8. How is the benefit measured? · 9. Who maintains the rules and content after the pilot? · 10. Can the project deliver a verifiable value within three months?
Technical prerequisites
An HVAC and plumbing firm needs no IT department of its own. But it does need a traceable architecture – and the knowledge of where each piece of information arises. The typical system landscape comprises trade software or ERP, order and customer data, document storage, email, calendar, telephone system, a mobile field solution, accounting, time recording and, where applicable, stores and purchasing.
| Stage | How it works | Advantage | Disadvantage |
|---|---|---|---|
| 1 · Separate assistance | The AI produces texts or summaries; staff transfer the results into the leading system. | quick entry, low risk | the media break remains |
| 2 · Controlled handover | The AI produces a structured draft; a member of staff confirms the transfer into the trade software. | less transfer, oversight retained | an interface is required |
| 3 · Process integration | The AI reads from and writes to several systems within defined rights. | high degree of automation | more effort, greater risk |
public product information, published service descriptions, general templates
internal processes, costing logic, supplier information, work instructions
customer data, quotes, contracts, floor plans, system histories, photos from buildings, staff data
health information, access and security data, data from sensitive facilities, access codes, information about critical technical installations
Data export: can the firm take its content, rules and histories out at any time in a usable format? Ability to switch off: does the firm keep running without the application – and how long does the return to a manual process take? Anyone who asks these two questions only after two years asks them too late.
Legal framework
The EU AI Act entered into force on 1 August 2024 and takes effect in stages. With the so-called Digital Omnibus, the timetable was adjusted in 2026: the European Parliament approved the text on 16 June 2026, and the Council gave its final approval on 29 June 2026.510
| Date | What applies |
|---|---|
| 2 February 2025 | Prohibited practices (Art. 5) and the AI-literacy obligation (Art. 4) apply. The Omnibus reformulates Art. 4: firms must now support the development of AI literacy rather than ensure it. The substance remains. |
| 2 August 2025 | Obligations for providers of general-purpose AI models (GPAI). |
| 2 August 2026 | Transparency obligations (Art. 50) and the start of enforcement. Anyone using AI in customer contact must disclose this; AI-generated or manipulated content must be labelled. |
| 2 December 2026 | Extended deadline for the machine-readable marking of synthetic content for systems already on the market beforehand; two new prohibitions take effect. |
| 2 December 2027 | Obligations for stand-alone high-risk systems under Annex III – including AI in recruitment and in employee evaluation (postponed from 2 August 2026). |
| 2 August 2028 | Obligations for high-risk AI embedded in regulated products under Annex I. |
Most of the applications in this whitepaper – text assistance, voice documentation, knowledge access, quote preparation – fall into the minimal- or limited-risk categories. An HVAC and plumbing firm generally operates high-risk AI only if it uses AI in recruitment or for employee evaluation. That is precisely why this area appears on page 24 among the applications to be avoided for now.
From August 2026, enforcement begins. In Germany, the Federal Cabinet adopted an implementing act on 11 February 2026 designating the Federal Network Agency (Bundesnetzagentur) as the competent market-surveillance authority where no specialist authority is responsible.10 Anyone who still does not know which AI tools are used in the firm, nor has trained their staff, has two already-applicable obligations open.
The legal situation continues to evolve. The information reflects the position as at July 2026 and does not replace legal advice. Check the current position before an implementation, and if in doubt with legal support.
AI governance
A table is enough: application · purpose · responsible person · data processed · provider · approval status. This list is the basis for everything else – and it regularly reveals that more AI is in use in the firm than was known.
Permitted applications, prohibited data, review requirements, labelling, access rights, responsibilities and how errors are handled. Two pages are enough, provided they are read.
Management: approval, budget, risk responsibility · IT or service provider: operation, access, interfaces, security · Data protection: personal data and contracts · Subject-matter lead: rules, templates, professional content · Users: checking results, reporting errors
Mandatory review for quotes, prices, technical recommendations, complaints, orders, appointment commitments, and for safety-relevant and legal statements.
It should be traceable which data was processed, what answer was produced, who checked it, what action was triggered and which version of the rules applied at the time.
An AI project decided over the heads of staff fails regardless of its technical quality. Anyone who informs the technicians only on the day of introduction will receive voice notes seven words long. Involve the affected staff in the choice of use case from the outset – they best know where time is lost.
Where a works council exists, systems capable of monitoring behaviour or performance are regularly subject to co-determination (section 87(1) no. 6 of the German Works Constitution Act). This applies even where no monitoring is intended – objective capability is enough. Early coordination is not a formality; it prevents a finished project from being stopped shortly before launch.
The German Federal Office for Information Security (BSI) notes that generative AI brings new IT-security risks and can amplify known threats – among them manipulation of inputs, leakage of confidential information and faulty outputs.11
Implementation
The plan is deliberately short. A project that delivers no verifiable statement after three months will deliver none after nine either – it will merely become more expensive.
Select a concrete bottleneck, capture the current workflow, determine case numbers and time required, record errors and follow-up questions, name a responsible person, set target metrics.
Outcome: a defined use case with a measurable goal, for example: "We want to raise the share of complete fault reports from 55 to at least 85 per cent within three months."
Define mandatory details, capture special cases, review documents, determine data sources, set permissions, describe risk cases.
Outcome: a target process with professional rules. Often it becomes clear here that the problem needs no AI at all – that too is a result.
Select a suitable solution, set up a test environment, run through sample cases, check answers and handovers, document errors, adjust rules.
Outcome: a working prototype with no uncontrolled production actions.
Train a small user group, handle a limited number of real cases, check results, measure time, gather feedback, deliberately test failure scenarios.
Outcome: reliable insights from your own firm, not from a vendor presentation.
Compare metrics, assess the error rate, calculate costs and benefit, check acceptance, make a final assessment of data protection and security, decide on expansion, adjustment or discontinuation.
Outcome: a documented operating decision.
Practical examples
The following examples are generalised constellations of the kind that regularly arise in HVAC and plumbing firms. They describe possible approaches and expected directions of effect – not measured results from individual reference customers.
Situation: 40 to 60 calls a day, two people in the office. Calls are lost particularly on Monday mornings. Fault reports often contain only: "The heating isn't working."
Solution: an AI phone assistant takes calls when the line is busy and outside business hours. It asks about the system, fault code, hot-water status and hazard indicators.
Control point: the system produces only a draft order. Dispatch decides on urgency and appointment.
Expected effect: fewer missed calls, more complete jobs, fewer follow-up questions, better-prepared technicians.
Main risk: incorrect urgency rating. Emergencies are therefore handled via fixed rules and not via free interpretation.
Situation: the managing director prepares quotes in the evening. The documents are spread across emails, phone photos and paper notes. On average, quotes go out eleven days after the site visit – often after the customer has already signed elsewhere.
Solution: a structured intake process collects all information in one place. From it, the AI produces a project overview and flags missing details.
Control point: sizing, quantities, prices and the specification are checked by the master craftsman and estimator.
Expected effect: less searching, faster quote turnaround, fewer follow-up questions, more consistent documents.
Main risk: incomplete details adopted as facts. The application must therefore explicitly flag missing information as unresolved rather than plausibly filling it in.
Practical examples
Situation: service reports are sometimes completed only in the evening or the following day. Extra work is occasionally missing from the invoice. When queried, no one remembers exactly – and in case of doubt the decision goes in the customer's favour.
Solution: after the job, technicians record a guided voice note. The AI structures the report, materials and follow-up recommendations along the firm's report structure.
Control point: the technician confirms the report before it is finalised. The office checks the billing-relevant items.
Expected effect: timely documentation, faster invoicing, fewer forgotten services, a better system history.
Main risk: misrecognised technical terms and part numbers. A company glossary and mandatory confirmations reduce this risk considerably.
Situation: new staff frequently ask experienced colleagues about internal workflows, products and forms. Each such question interrupts two people: the one asking and the one answering.
Solution: an internal knowledge assistant draws on approved process documents, checklists and manufacturer information.
Control point: answers show the sources used. Where there is no basis, no confident statement is produced.
Expected effect: faster onboarding, fewer interruptions, more consistent workflows, better use of existing documents.
Main risk: outdated documents. Each source is therefore given a responsible person and a review date – without this upkeep, the assistant decays within a year.
In no case does the AI make a professional decision. In every case there is a named control point. And in every case the main risk is not the technology but the AI's readiness to fill a gap rather than show it. If you can specify only one requirement to a vendor, choose this one: show gaps rather than close them.
Self-assessment
Rate each statement with 0 points (not present), 1 point (partly present) or 2 points (sufficiently present). Do not answer the questions alone – the assessment by management and by the office typically differ.
| Assessment question | Points |
|---|---|
| We have selected a concrete operational bottleneck. | ___ / 2 |
| The current workflow is known and documented. | ___ / 2 |
| Case numbers and time required can be determined. | ___ / 2 |
| The information needed is largely available digitally. | ___ / 2 |
| A professionally responsible person is named. | ___ / 2 |
| Critical decisions remain with staff. | ___ / 2 |
| Data protection and information security can be checked. | ___ / 2 |
| The affected staff are involved. | ___ / 2 |
| Success and errors can be measured. | ___ / 2 |
| Time and budget are available for the pilot. | ___ / 2 |
| Total | ___ / 20 |
Do not begin by selecting an AI platform. First capture the process and organise the information needed. In this situation, an AI project would mainly make visible what is already known – at a high price.
A contained use case can be prepared. Focus on clear goals, controlled data access and a small user group. Resist the temptation to expand the scope during the pilot.
The firm has suitable prerequisites for a structured pilot. The focus should now be on integration, quality control and cost-effectiveness – and on the question of who will maintain the rules and content after the pilot on a lasting basis.
Closing remarks
The economic value of an HVAC and plumbing firm continues to arise from proper planning, skilled workmanship, reliable service, responsible decisions and the trust of the customer.
Artificial intelligence is worthwhile when it supports these tasks. It can take in information, prepare documents, make knowledge findable and speed up documentation. But it cannot assume responsibility for safety, technology, price or workmanship – and it should not try to.
The best entry point is therefore not a large transformation programme. It is a concrete, frequently occurring task whose improvement becomes measurable in day-to-day work. Anyone who starts there gains two things: a result and experience. Anyone who starts with the platform question gains a presentation.
A structured initial review examines, among other things:
A prioritised selection of realistic use cases with a recommendation for a contained pilot – including the cases we advise against. If no commercially sensible use case emerges, we say so.
AI consultancy and
digital products for small and medium-sized enterprises (SMEs) in the
German-speaking region. Data protection in accordance with the EU GDPR.
krambergai.com
A possible next step: assess the use of AI for your HVAC and plumbing firm · identify a suitable AI use case · request an AI potential report · arrange an initial conversation about introducing AI.
Appendix
All sources last accessed on 15 July 2026. The information reflects the position published at that time. Publication titles issued in German are quoted in the original with a translation.
Publisher: KrambergAI GmbH · krambergai.com
Disclaimer: This whitepaper is for general
information. It replaces neither professional planning nor legal, tax or
data-protection advice in an individual case. The cost-effectiveness
calculations are model calculations based on freely chosen assumptions
and constitute no guaranteed properties or savings. All brand and
product names belong to their respective owners.