Reduce complexity. Build clarity. Gain sovereignty.
Permits, resources, change orders, damage, project knowledge live in ten channels today. levelbuild Logistics brings these five fields onto one platform – as an operational layer on top of TMS, ERP and DMS, without rip-and-replace.
The transport itself is rarely the problem – it is the coordination around it. Fragmented across ten channels, with no shared view for dispatch, escort, crane and customer. Three examples every heavy-lift dispatcher knows.
Waiting time at the lifting point, a second crane slot, a road closure – extra work happens on site and gets passed on via WhatsApp. Two weeks later the evidence is missing: half the change orders are never raised, the other half rejected without proof.
Answer: use case 01 →Transport damage? A smartphone photo, an e-mail to the dispatcher, eventually it reaches the insurer. Audit readiness: a matter of luck.
Answer: use case 02 →Plans, permits, conditions – scattered across individual employees’ Outlook folders. The next comparable transport gets planned from zero again.
Answer: use case 03 →Sounds like your day-to-day? 30 min discovery call – we show on one of your transports how levelbuild Logistics resolves this.
Book a discovery →Three core use cases that cost the most money and time in project cargo today – direct answers to the three symptoms above.
Five classes of information – permits, resources, change orders, damage, project knowledge – run on the same platform.
A structured permit file per order – application, conditions, correspondence, deadlines. Conditions become verifiable checks with an owner and a due date.
A shared order timeline with role-specific views for escort, crane, assembly, customer – changes trigger notifications along the dependency chain.
Trigger: extra work happens on site – and is forgotten later.
The driver reports waiting time, a second crane slot or restricted access via WhatsApp to the dispatcher. Two weeks later the dispatcher only half remembers. One half of the change orders is never raised – the other half rejected by the customer for lack of proof.
The driver opens the app on site, picks the category (waiting time / additional lift / aggravated access), photographs the situation and has site management sign on the tablet. The change order lands automatically in the project file and travels to the office as a draft invoice – with evidence, not from memory.
Mobile capture from live construction operations (web + mobile). Category, photo, status and role-bound approval – structured instead of a chat message. For project cargo the same platform is configured to change-order categories (waiting time / additional lift / aggravated access), with digital customer signature on site and automatic filing in the project file.
A TMS knows orders, but not semi-formal extra work. An ERP manages invoices, but does not draft them on site. Excel and WhatsApp document – but without signature, without order context, without an archive.
Trigger: damage occurs at the loading point – who records what, and when?
Photos on the driver’s phone, notes on the delivery slip, a WhatsApp description to dispatch. The documents surface days later in an e-mail – or not at all. Evidential value and insurance reimbursement suffer; customer disputes become a ritual.
A structured damage form on the smartphone – with mandatory fields, photos, geo stamp, signature. Automatically assigned to the right order file. Insurer, customer and dispatch see the same record with the same timestamp.
Damage pins on an object schematic, web and mobile. 16 events on a container schematic – each with photo, status (recorded / pending / resolved), cost estimate and surveyor flag. For project cargo the container becomes a transport schematic: rotor blade, transformer or cargo frame – damage documented at the source, audit-ready in the file.
A DMS stores what is put into it – it does not enforce capture at the source. A generic form tool does not know the order. The gap sits between incident and file.
Trigger: a similar transport returns in 6 months – who remembers the permit conditions?
Every project is an island. Plans, permits, lessons learned live in individual employees’ Outlook folders. When someone leaves, knowledge leaves with them. A comparable transport gets planned from zero again.
Every order is created in a structured project file: cargo, route, conditions, resources, documents, communication. Similar orders are suggested as templates. Knowledge stays in the company, not in an inbox.
Project file with 11 plans (web) and project overview (mobile). All documents, plans, approvals and communication central per record – instead of Outlook folders. For project cargo this becomes the transport file: cargo, route, conditions, resources – reusable as a template when the next similar order comes in.
An ERP archives commercially, not operationally. A DMS knows folders, not order patterns. A wiki is maintained voluntarily – and therefore unreliable. Project knowledge needs a home tied to the process.
levelbuild grew up in construction. With Mainka, Jaeger, Spitzke, Bickhardt and Baierl + Demmelhuber we learned what a platform must deliver when it reaches blue-collar teams in the field, maps many locations consistently and brings home-grown speciality tools together. We are now configuring the same engine for project cargo, heavy lift and abnormal transport — together with design partners from your industry.
Five construction customers in productive use · Siemens Energy on the product advisory board. References on levelbuild.com (German) →
For us, levelbuild is the spider in the web: the platform pulls data together from many different tools and condenses it into something we can actually work with.
This freedom of movement inside a standard solution can be implemented very quickly and easily thanks to a no-code platform.
“There are plenty of tools that are good at individual topics. But levelbuild’s role as the ‘bracket’ is the decisive thing for us. From the construction site through documentation to internal processes, controlling and BI tools.”
“From HR applications through dispatch and payroll to the construction file: levelbuild will be our standardised, data-optimised, connected, secure and above all efficient working environment for process-supporting application systems.”
“levelbuild is a very decent, clear and fair partner. You are taken seriously and advised honestly: what works, what does not, and what you had better leave alone.”
Tested in construction, configurable for project cargo – not newly developed. The segmentation into wind power, heavy lift and industrial assembly is not a future vision but the same mechanics that carry building construction, civil engineering and infrastructure today.
Acceptances, defect management, VOB conditions, trade coordination.
Measurements, soil classes, shift logs, change-order capture at the point of installation.
Closure windows, rail conditions, coordination duties towards third parties.
Roles, mobile app, condition checks, audit trail, integrations. Configured per world – not rebuilt.
Component handover at the wind farm, condition capture for rotor blades / transformers, wind farm file for repeat transports.
VEMAGS conditions as verifiable checks, escort (BF3) assignment, cargo-securing records, permit file per transport.
Crane slot sync, HSE briefing before deployment, qualification matrix with deadline alerts.
Concretely: a civil engineering customer uses the same condition check today that a wind power logistics provider will configure for VEMAGS conditions tomorrow. The same mobile form that documents defects on the construction site captures transport damage on a rotor blade at the wind farm. Different vocabulary, same mechanism – no custom development, no speciality software per segment.
Five partners, not a hundred licences. We are looking for a network of co-creators, not a customer list – the conviction being: when different perspectives converge on one platform, the result is not industry software but a mechanic with general validity. That is exactly what made levelbuild in construction what it is today.
We are launching levelbuild Logistics for project cargo with five design partners who take the first productive step together with us – not on a slide, but on a real transport. One prioritised use case, four to eight weeks to the pilot, and the platform underneath has been running in construction for years.
What you get as a design partner: the configuration is built with you, not bought for you. In return: preferential terms in productive operation, a direct line to our product team, and the right to shape the vertical standard everyone after you will adopt.
From construction – now for project cargo.
One prioritised use case – e.g. change order via app, VEMAGS file or damage documentation – goes live on a real running transport. No sandbox PoC.
Fixed scope, fixed duration, fixed go/no-go review after the pilot. No multi-year implementation debt, no hidden lock-in.
Design partners benefit permanently on licence, rollout and operations – in return for the configuration work that lets the project cargo standard come into being in the first place.
No support ticket funnel. Two weekly touchpoints with product & engineering, a fixed duo of contacts covering the construction and logistics perspectives.
Owner-operators with their own fleet / cranes / SPMT, 50–500 employees, recurring project transports (wind power, transformers, industrial components). Decision with the MD / COO – not with an 18-month committee.
Bring a current transport – one that hurts today or will hurt tomorrow. We show live how the construction reference maps this case and where levelbuild Logistics comes in for project cargo. At the end you will know whether a pilot makes sense. Or not.
Christopher Arndt · levelbuild · christopher.arndt@levelbuild.com · reply within 24h.
In construction we built levelbuild with five partner companies that work with it every day. For project cargo we are looking for five entrepreneurs to walk the same path with us – not as customers of a finished product, but as co-creators.
30-minute discovery – video or phone. Pick a window that suits you.
Loading the widget retrieves content from calendly.com (Calendly LLC, USA). This sets cookies and transfers technical connection data – including IP address and browser identifier – to Calendly. Details in our privacy policy.
The most important question first: levelbuild Logistics is not a replacement for your existing systems. No rip-and-replace. No migration. It is an operational layer that bundles the five classes of information – permits, resources, change orders, damage, project knowledge – across TMS, ERP and DMS.
No. levelbuild Logistics replaces none of your existing systems.
levelbuild Logistics is an operational coordination layer that sits on top of your TMS (own vehicles, internal dispatch), ERP (invoicing, financials) and DMS (document archive). Exactly the five classes of information that get lost between these systems today – permits, external resources, change orders, damage cases and project knowledge – are bundled by levelbuild Logistics into one truth for dispatch, customer and back office.
No rip-and-replace. No migration. No downtime.
Shared foundation: roles, integrations (TMS/ERP/DMS), mobile app, audit trail – proven in construction.
The construction platform comprises more than 80 productive modules. A selection – all equally usable in the logistics world:
These and further building blocks have been running productively at mid-sized construction companies for years. For project cargo they are configured, not rebuilt.
A TMS synchronises own vehicles and internal dispatch – but does not know third parties’ external resources. A project management tool plans dates but has no logistics taxonomy. Messengers transmit messages, but no order context.
levelbuild Logistics is not an alternative to these tools – it is the missing layer that coordinates project cargo information across them and ties it to an order.
levelbuild Logistics is based on a no-code platform from the construction industry. For every use case (permits, resources, change orders, damage, knowledge) there is a configurable module with data model, workflow and roles.
You start with the use case that hurts most today and expand step by step. Every configuration remains yours – no custom code, no consultant dependency, no multi-year implementation projects.
Building blocks instead of blank forms
VEMAGS, conditions, status central
Escort, crane, assembly in sync
Capture deviations on site
Structured, audit-ready
Lessons learned, reusable
Hosting in Germany / EU. Multi-tenant model with hard data isolation. ISO 27001, TISAX orientation, BSI baseline protection.
Open REST APIs, webhooks and SFTP for integrations — no proprietary lock-in. Documented AI models with EU inference; customer data does not flow into provider training.
Audit trail, export and offboarding capability. SLA and release cadence on request. For a technical evaluation with our CTO please request an appointment →
Use-case-based instead of big bang. Typically: one use case productive in the first quarter, more to follow.
Because levelbuild Logistics is a layer on top of your existing system landscape and forces no migration of existing data, the classic rollout risks of an ERP or TMS project do not apply.
No licence upfront. We pilot together on a real project transport.
You contribute time and domain expertise, we build the concrete use case and evaluate with you. Only after a successful pilot do we jointly decide on the commercial continuation.
No lock-in. Your data stays your data and can be exported at any time.
We at levelbuild learn what does not work for the next iteration. Your existing systems are untouched – there is nothing to unwind.
We are a no-code platform from the construction industry that has passed its operational stress test with construction companies.
Heavy lift and project cargo are the logical extension: every large construction project depends on project transports. We know the taxonomy, the supply chains and the operational pain points from the neighbouring industry and translate them into levelbuild Logistics.
Anything still open? Sort it out directly in the discovery →
