Your edge isn’t in any standard.

The levelbuild app closes the gap on site, the case file pulls everything together – and your existing systems get complete data:

No. levelbuild does not replace any of your systems. The layer sits on top and bundles exactly the information that gets lost between systems today – permits, change orders, damage, knowledge. No migration, no downtime, no rip-and-replace.

The first step is a joint pilot on a real process: no licence upfront – you contribute time and domain expertise, we build the use case. Only after a successful pilot do we jointly decide on the commercial continuation. The first five pilot customers join as design partners: a direct line to the product team and permanent preferential terms.

Fixed scope, fixed duration, fixed go/no-go review. Your data stays your data and can be exported at any time. Your existing systems are untouched – there is nothing to unwind. No multi-year implementation debt, no hidden lock-in.

Hosting in Germany/EU, multi-tenant model with hard data isolation, ISO 27001, TISAX orientation, BSI baseline protection. Open REST APIs, webhooks and SFTP – no lock-in. Documented AI models with EU inference; customer data does not flow into provider training. For the technical evaluation, our CTO works alongside your team.

No – that is the point. Replacing a legacy system is a two-year project with an open outcome; that is exactly why the processes around it stay stuck. levelbuild Logistics sits as a layer on top of your existing systems: TMS, ERP, DMS and industry solutions stay where they are and receive the data they are missing today via open interfaces. You can decide on replacement later – or never.

Yes – and it is usually bigger than you think: Excel lists for permit conditions, WhatsApp photos of damage, PDF change orders in inboxes, Access databases from 2014. Shadow IT is not born out of carelessness but because the standard system does not know the special case – and the special case still has to be handled today. Instead of banning it, levelbuild brings these processes into a guided interface: the same speed for your people, but with access control, history and a connection to the ERP.

What gets automated is hand-over and assignment: a change order captured and signed on site lands in the order file without any intermediate step, and as a booking proposal in the ERP. Permit conditions become scheduled inspection tasks with an owner and escalation. Approvals run on rules instead of follow-up calls. Not automated is the professional judgement – who is liable, what gets negotiated, whether a transport goes. That stays with your people; the platform just makes sure they no longer decide on incomplete information.

AI works where it can be verified: reading receipts and delivery notes and mapping them to the right fields, pre-sorting photos and classifying damage images, condensing free text from the field into structured data, spotting deviations against similar records. Every suggestion is traceable and correctable – with source and change history. We deliberately use no AI where a wrong answer is expensive and nobody would check it: liability questions, permit conditions, pricing. And: your data trains no third-party model.

As custom as your process – but rarely started from zero. In construction, our partner companies maintain more than 80 productive modules: for much of it there are templates we use as a foundation or install as a baseline – especially where a standard makes sense, such as personnel files. Only what truly sets you apart gets configured instead of coded: fields, mandatory data, approval paths, roles, reports. That is why the pilot stands in 4–8 weeks instead of 12–24 months. For maintenance afterwards there are two models – depending on your operating model: a) your team gets trained and takes over, with no tickets, no release cycles, no daily rates. b) levelbuild stays on board as your development partner and maintains the customisation with you. The entry point does not lock you in – you can switch at any time.

The platform has passed its stress test in construction: more than 80 productive modules, five partner companies on the product advisory board, 20,000+ daily users on construction sites and in back offices. For logistics, the same engine gets configured, not rebuilt – hence 4–8 weeks instead of 12–24 months.