Tender & BoQ analysis
Tender documents and bill of quantities in – risk items, contradictions and bidder questions out.
Review in hours instead of days
Your project data.
Your knowledge.
Your agent.
AI for tenders, change orders and project knowledge – from an on-demand assistant to an agent with its own area of responsibility. Running on your own hardware or in a German data center. Not a byte leaves the EU.
Three use cases that save time from day one
Change order management
Site diary, correspondence and contract in – a documented chronology and a draft change order under VOB/B (German construction contract procedures) out.
Faster, with a complete evidence trail
Project knowledge on demand
“What was agreed on drainage in section 3?” – an answer with its source, drawn from the entire project folder.
Commitments and deadlines found instantly
0
project data outside the EU – technically ruled out
2
operating models: in your own server room or hosted in Germany
8
weeks from first conversation to an evaluated pilot
Why sovereign – and why in construction this is not an option but a prerequisite
Public-sector clients – rail, highways, municipalities – ask where project data is stored. On-premise makes the question moot.
Cost calculations and unit prices are never used to train third-party models – technically ruled out, not just contractually promised.
GDPR, NIS2, CLOUD Act – processing exclusively within the EU; subcontractors subject to US access are contractually excluded.
Court-proof – every query and answer is logged and attributable to a person. A prerequisite when AI-assisted documents enter a dispute.
The platform – two operating models, one software
On-premise · NN-Forge appliance
A pre-configured inference server in your own server room – no internet connection needed in operation.
Hosted EU · data center in Germany
Operated by Neuronetz; connected to your file server or DMS with permission-aware access.
OpenAI-compatible interface · open-weight models only · switch from hosted to on-premise at any time, with no data migration.
From assistant to agent – automation in three stages
STAGE 1 · ASSISTANT
The human asks, the AI answers
BoQ analysis, change order drafts, project knowledge – on demand, with sources.
STAGE 2 · AUTOMATION
The AI prepares the work, the human signs off
Inbox sorted, deadlines monitored, change orders and replies prepared – ready for sign-off in the morning.
STAGE 3 · AGENT
Its own role, its own mailbox
Runs a defined area of responsibility on its own; humans review spot checks and exceptions.
Each stage builds on the previous one. You set the pace – trust is built on results, not promises.
A pilot in 8 weeks – no investment decision required
WEEK 1
Scoping
Half a day: use case, pilot project, 3–5 users.
WEEKS 2–3
Setup
Platform, connection to your document store, permissions, onboarding.
WEEKS 4–7
Operation
Daily use in real work, weekly check-ins.
WEEK 8
Evaluation
Time saved, quality, adoption – roll out or stop.
You provide: one contact person from the business side and the documents of one project. We deliver: platform, setup, support and a final report. We discuss terms in the first conversation.
Let's talk about your first project.
Stephan Kasdorf · Managing Director · Neuronetz UG (haftungsbeschränkt)
Exposé as PDF