Industry · Construction & Trades

Custom Handwerker App and Construction Software — built around your business

A handwerker app that works in the workshop, the basement boiler room, and on the construction site as well as in the office — that is the bar most off-the-shelf construction software fails to clear. We build custom trade and construction software for mid-sized DACH businesses: mobile-first, offline-capable, cleanly connected to the regulatory reality of 2026 — the e-invoice receipt obligation in force since 1 January 2025 (XRechnung and ZUGFeRD), the BIM Stufenplan moving into regular operation, GoBD-compliant record-keeping. We deliver end-to-end responsibility: architecture, app, backend, operations — no account-manager layer between you and the person writing the code.

Contact

Industry context

As of 31 December 2024, the German trades sector comprises around 1.04 million businesses with close to 5.6 million employees and an annual turnover of roughly €771 billion (source: ZDH Handwerkszählung, published 09/2025). The Central Association of German Trades (ZDH) brings together 53 chambers of trades and 47 sector associations and is the political voice of the industry. Density is regionally uneven — Baden-Württemberg, Bavaria, and North Rhine-Westphalia carry the bulk; in the DACH Mittelstand, 50–500-employee businesses are the norm.

For digitalisation, the Mittelstand-Digital Centre for Trades (operators: ZDH and ZWH, funded by BMWE, €10.3 million over 5 years) has been the central support hub since 1 July 2021 — free of charge, vendor-neutral, nationwide. Project conclusion is the Zukunft Handwerk Congress on 4–5 March 2026 in Munich; the federal Mittelstand-Digital Centre programme phases out by end of 2026, with a successor network tendered by BMWE in late December 2025 and operational from 2027. For trade businesses planning a custom handwerker app or in-house construction software today, this means concrete advisory and pilot building blocks remain available via the existing centres until mid-2026 — after that, having the architecture in your own hands matters more than ever.

On the construction side, the BIM Stufenplan from the Federal Ministry of Transport (BMV) drives digitalisation. The Masterplan BIM Bundesfernstraßen (published 12 October 2021) establishes the BIM method as the standard for planning and construction of federal highways from 2025; as of May 2026 the introduction phase is transitioning into regular operation at the Autobahn GmbH, DEGES, and the länder contract administrations. The supporting body is planen-bauen 4.0 GmbH. For the construction Mittelstand this means IFC interfaces, Open-BIM data exchange, and integration with general-contractor platforms become a hard selection criterion — construction software that cannot do this on day one fails supplier screening.

Typical challenges

Off-the-shelf vs. custom — the Mittelstand bottleneck

The market for trade software is saturated with licensed products — job management, time tracking, on-site measurement, one more module per year. That works as long as your processes fit the software. The moment you need a multi-trade workflow, a specific supplier integration, or a connection into your own ERP, the equation flips: licence cost scales with employees, customisations cost extra per change, and the vendor prioritises the roadmap by market average — not by your business. Custom trade software as in-house development is not the answer at every scale — but above a certain threshold (typically 30+ employees with their own IT ownership), it is the more honest path because code and data model stay in your hands.

No signal is the norm — an offline-capable handwerker app is a must, not an optimisation

A handwerker app without a robust offline mode is an office app dressed up as a site tool. In the basement boiler room, in the stairwell of a 1960s building, in the workshop behind the steel door — internet connectivity is not reliable. The proven pattern is mobile-first with a local event log: every action (hours, measurement, photo, material list, site-diary entry) is written locally as an immutable event. Sync to the backend runs through structured resync points and idempotent APIs — on the next Wi-Fi, without data loss, without the user having to verify "did everything go through". Add conflict strategies for simultaneous changes from office and field — otherwise the last write overwrites the honest one.

BIM connectivity for the construction Mittelstand

Large construction projects require BIM. The general contractor works with IFC models, Performance Level 1 data, AIA specifications — and expects the construction software of its tier-2 or tier-3 supplier to plug in. Mid-sized building and finishing businesses rarely have their own BIM tooling and cannot afford a Solibri or Navisworks stack. The pragmatic path: an open-source-based IFC import pipeline (xBIM Toolkit or IFC.js / web-ifc) that converts the model into your own data structure — components, quantities, properties — and feeds it into job and measurement logic. The Mittelstand business stays BIM-ready without an enterprise-scale stack investment.

E-invoicing 2025 meets manual workflows

Since 1 January 2025, every domestic German trade business in the B2B segment must be able to receive e-invoices in XRechnung or ZUGFeRD format (version 2.0.1+) — even the smallest. The sending obligation phases in: businesses with prior-year turnover above €800,000 must send e-invoices from 1 January 2027; from 1 January 2028 it applies to all B2B transactions. Many Mittelstand businesses still work with PDF email attachments and manual handover to the tax advisor — the jump to a structured ZUGFeRD workflow (XML in a PDF/A-3) and clean DATEV export is an architecture topic, not a tooling click. The receiving side (XRechnung parser) and the sending side (Mustang library or Factur-X PHP) belong inside the construction software or trades app itself, not in a third-party silo.

Material management and supplier integration — the next break

Orders, goods receipt, on-site material lists, returns — the material and supplier layer is the most expensive data break in many trade businesses. An employee calls the wholesaler, who sends a PDF confirmation, which goes to the office, someone enters the line item in Excel — and if the delivery note goes missing, nobody finds the order again. A handwerker app as an isolated tool is only half as valuable when not connected to a supplier portal or an integrated material data model with order and delivery-note status. Integration with wholesaler APIs (e.g. Würth, Sonepar, Stauf), barcode/QR capture at goods receipt, and a clear audit trail of who released what and when — that is the next leverage step after a pure job-management app.

Regulatory framework

BIM-Stufenplan und Masterplan BIM Bundesfernstraßen

The Stufenplan Digitales Planen und Bauen, run by the Federal Ministry of Transport (BMV, formerly BMVI), governs the phased introduction of Building Information Modeling in public construction. BIM Performance Level 1 has been mandatory for new federal transport infrastructure projects since end of 2020. The Masterplan BIM Bundesfernstraßen (published 12 October 2021) establishes BIM as the standard for planning and construction of federal highways from 2025 — as of May 2026 in transition to regular operation at Autobahn GmbH des Bundes, DEGES, and the länder contract administrations. The supporting body for the Stufenplan is planen-bauen 4.0 GmbH. For the construction Mittelstand this makes IFC-2x3 or IFC4 data exchange a hard requirement in supplier selection.

Applicability: Performance Level 1 mandatory since end of 2020 · Masterplan BIM Bundesfernstraßen published 12 Oct 2021 · regular operation from 2025/2026

Stufenplan Digitales Planen und Bauen — Endbericht — BMV
Masterplan BIM Bundesfernstraßen — BMV

E-Rechnungspflicht (Wachstumschancengesetz, § 14 UStG)

The German Wachstumschancengesetz introduces a mandatory e-invoicing regime for domestic B2B transactions. Since 1 January 2025, every German business — including the smallest — must be able to receive e-invoices; an email mailbox is sufficient for receipt only. The sending obligation phases in: from 1 January 2027 for businesses with prior-year turnover above €800,000, from 1 January 2028 for all B2B transactions. Compliant formats: XRechnung (KoSIT standard) and ZUGFeRD from version 2.0.1 (excluding the MINIMUM and BASIC-WL profiles) — both satisfy the EU norm EN 16931. A plain PDF invoice without structured XML data no longer qualifies as an e-invoice. For a handwerker app or construction software this means: XRechnung parser on the inbound side, ZUGFeRD generator (e.g. Mustang or Factur-X PHP) on the outbound side, clean DATEV export.

Applicability: Receipt obligation since 1 Jan 2025 · sending obligation (>€800k) from 1 Jan 2027 · sending obligation (all B2B) from 1 Jan 2028

FAQ E-Rechnung — Bundesfinanzministerium

GoBD (Grundsätze ordnungsmäßiger Buchführung)

BMF directive on storage, completeness, and traceability of digital business records. A handwerker app handling receipts, delivery notes, time sheets, or invoices must guarantee four properties: immutability after posting, completeness of records, timely capture, and machine-readability. Architecturally: append-only event log for postings, separate storage of original receipts with hash protection, documented procedure description. Retention period: ten years for invoices and accounting records. Standard trade software typically satisfies this — a custom development must do the same from day one.

GoBD — BMF

Gebäudeenergiegesetz (GEG)

The Gebäudeenergiegesetz (Building Energy Act, latest update 2024) governs heating and energy-efficiency requirements for new buildings and existing stock — relevant for plumbing, heating, and air-conditioning (SHK) businesses and construction companies. Since January 2024, heating systems in new buildings in new development zones must use at least 65% renewable energy. For existing buildings, the 65% rule kicks in with municipal heat plans (in major cities by mid-2026, otherwise by mid-2028). A planned amendment to a Building Modernisation Act is scheduled from 1 July 2026 — in preparation as of May 2026. For construction software this means installation master data, commissioning documentation, and service logs must hold GEG-relevant fields in a structured way.

Applicability: 65% rule for new buildings in development zones since 01/2024 · for existing stock tied to municipal heat planning (by mid-2026/2028) · amendment from 07/2026 in preparation

Gebäudeenergiegesetz (GEG) — BMWSB

DSGVO

Glossary →

Customer, employee, and supplier data fall under GDPR — even in trade businesses without a dedicated IT function. Concretely in a handwerker app: contact details and job history as personal data, on-site photos (employees in frame), location data of service vehicles. GDPR-compliant software anchors Privacy-by-Default requirements from Art. 25 GDPR in the data model — role separation office/field, retention periods per data category, processor agreements with sub-services (hosting, Sentry monitoring, DATEV export). EU hosting (Hetzner, DigitalOcean Frankfurt) takes the third-country transfer question off the table with public-sector and security-industry customers.

Architecture pattern for B2B apps

Mobile-first app (handwerker app)

Cross-platform app (e.g. Flutter) · offline-first with local event log · local DB (SQLite) · camera and PDF capture · barcode/QR · BLE for machine telemetry

One codebase for iOS and Android — staff often bring their own devices. Every action — time entry, measurement, site diary, photo, material list — is written locally as an event and cleanly synchronised when next online. Idempotent APIs prevent double-postings; conflict strategies handle simultaneous changes from office and field.

Job & service backend with GoBD audit

Typed API layer (e.g. NestJS, Go) · PostgreSQL · append-only event log · S3-compatible object store for receipts · hash protection of originals

Jobs, hours, materials, invoices in one database. Append-only event log as audit-grade trail for GoBD-compliant traceability, separate receipt storage in an S3-compatible object store with content hashes. Ten-year retention is anchored structurally in the data model, not hidden in a backup script.

E-invoicing pipeline (XRechnung / ZUGFeRD)

Mustang Project (Java) or Factur-X PHP · KoSIT validator · ZUGFeRD 2.x generator · DATEV export · XRechnung parser

Inbound pipeline: extract XRechnung XML from email attachment or supplier portal, validate against the KoSIT schema, map into your own accounting data model. Outbound pipeline: generate ZUGFeRD 2.x hybrid invoice (XML embedded in PDF/A-3), dispatch by email or Peppol. Libraries are open-source and mature — what matters is clean integration into the data model, not a third-party connector alongside the app.

BIM and IFC connectivity

IFC.js / web-ifc · xBIM Toolkit · IFC4 importer · Open-BIM data exchange · integration with GC platforms

IFC models from the general contractor are imported, components and quantities extracted, mapped into your own job and measurement data model. web-ifc (JavaScript/WebAssembly) enables browser-based display; xBIM Toolkit (.NET) is the choice for server-side processing of larger models. Open-BIM strategy instead of proprietary plug-in lock-in — the construction software stays connectable on the next GC change.

Office & customer portal

Web portal (e.g. Next.js, Astro) · OIDC identity (e.g. Authentik, Keycloak) · customer portal with job approval · GDPR-compliant self-service

Office staff see the same data as field teams; end customers get their own portal — job status, progress photos, approval workflows, e-invoice download. Self-hosted identity providers keep the auth layer in your own hands, without third-party SSO dependency.

Supplier & material management layer

Wholesaler API integration · barcode/QR capture · order workflow · delivery-note status · audit trail per line item

Orders, goods receipt, on-site material, returns in one data model. Integration with wholesaler APIs (e.g. Würth, Sonepar) cuts manual spreadsheet work. Optional as a supplier portal for structured multi-vendor workflows.

How we pick the stack

The concrete stack is decided per project — driven by data volume, compliance, existing systems, and team skills. This table lists the capabilities we cover and two to three tools we have shipped in production for each.

Capability	How we deliver it
Cross-platform app with offline-first	One codebase for iOS and Android — critical because trade staff often bring their own devices. Robust offline-first data models, camera and PDF capture, BLE for machine readings. Typical pick: Flutter, with native bridges for hardware-near paths (NFC, printers).
Typed backend for GoBD & GDPR audit	Structured backend with clear module separation, auditable for GoBD and GDPR. TypeScript (NestJS, Fastify) is our default, Go where throughput demands it; built-in validation pipelines for e-invoice XML and supplier interfaces.
Relational storage with event log	PostgreSQL for jobs, staff, materials, invoices — with the append-only event log in the same schema as audit-grade GoBD trail. Depending on project we use Prisma, Drizzle, or direct SQL; long retention without schema drift is the requirement, the data-access layer follows the team.
Open-source pipeline for e-invoicing & BIM	Mature open-source libraries for ZUGFeRD and XRechnung (e.g. Mustang in Java, Factur-X in PHP) — validated against the KoSIT schema. For BIM/IFC we use web-ifc in the browser or the xBIM Toolkit server-side. No third-party connector: logic stays in your own software, upgrade path in your own hands.
OIDC identity in your own hands	Identity provider for staff, office, and customer auth. Self-hosted options (e.g. Authentik, Keycloak) where data residency or multi-tenancy demands it; managed providers (e.g. Auth0) where time-to-market is the priority.
EU-hosted infrastructure	Data sovereignty for Mittelstand customer data — a clear argument towards public-sector clients and security-sensitive industries. We have shipped on Hetzner, DigitalOcean (Frankfurt), AWS Frankfurt, and own Kubernetes clusters among others; container orchestration (Kubernetes, Kamal) keeps the platform independent of any single hyperscaler.

In practice

LITE BLOX Platform — offline-first IoT as architectural pattern

Industrial IoT platform for intelligent starter batteries — refactor and extension of a system that has grown since 2018, with lifecycle data model, self-service portal, and append-only event log. Industry-adjacent to trades and construction: the same architecture patterns — offline-first mobile app, event-based backend, BLE connectivity, EU hosting — apply to a <strong>handwerker app</strong> and <strong>construction software</strong> that must work in dead zones.

Read case study →

Sources

Wirtschaftlicher Stellenwert des Handwerks 2024 (Handwerkszählung) — ZDH
Mittelstand-Digital Zentrum Handwerk — BMWE / ZDH / ZWH
Stufenplan Digitales Planen und Bauen — Endbericht — BMV
Masterplan BIM Bundesfernstraßen — BMV
FAQ E-Rechnung (Wachstumschancengesetz, § 14 UStG) — BMF
GoBD — BMF
Gebäudeenergiegesetz (GEG) — BMWSB

As of: 2026-05-01

Read on

Concrete project in this industry?

We build software that fits the regulatory, technical, and organisational realities of your industry — without excess complexity.

Send email