Construction / Bauunternehmen (DE/AT) · No open public API — bridged via GAEB file export
AI integration for RIB iTWO — automate without switching
RIB iTWO has no open public API — most agencies cannot touch it. We bridge it honestly via GAEB file export, without migrating.
In short: EBROTECH connects AI to RIB iTWO without migrating: iTWO has no open public API, so where most agencies tell you to switch, we bridge it honestly through GAEB, the standard German construction data-exchange format (D81/D83/D84) iTWO already reads and writes. iTWO stays exactly as it is, and the AI runs on top of the files it exports.
What is RIB iTWO and what is it for?
RIB iTWO is the construction and cost-management software used by larger contractors across Germany and Austria. It has no open public API the way a modern SaaS does, so most agencies cannot integrate it and tell you to switch. EBROTECH does not. We bridge it honestly through the GAEB files it already exchanges, and you keep iTWO exactly as it is.
What it's used for
- Keep RIB iTWO exactly as your construction team uses it
- Bridge it without any cloud API or migration
- Trigger AI workflows from the GAEB files it exports
- Chase tenders and answer clients on top of it
What frustrates RIB iTWO users?
- RIB iTWO has no open public API, so integrators say it is impossible
- Tender and cost data is locked inside the software
- You are told to migrate to integrate, which is out of the question
- Everything around iTWO is manual
What changes when AI works for you
30%
of lost appointments recovered with reminders
24/7
AI picks up the phone when you can't
5x
more Google reviews in 60 days
0
missed calls left unanswered
Typical results in the businesses we work with. We measure it with you from day 1.
What does EBROTECH automate on top of RIB iTWO?
RIB iTWO stays your source of truth. We add the layer it doesn't do on its own: answering, reminding, chasing and winning back customers with AI agents.
Bridge via the GAEB files (D81/D83/D84 and similar) iTWO imports and exports
AI workflows triggered by each new GAEB export
Automatic tender follow-up and client chasing on top of it
Voice AI answering calls while iTWO stays untouched
How does AI connect with RIB iTWO?
RIB iTWO does not expose an open public API for third parties. This is exactly where most agencies stop. We bridge it honestly through GAEB, the standard German construction data-exchange format that iTWO already reads and writes (D81/D83/D84 files). We parse the export, trigger the AI workflow, and feed structured data back via GAEB. No invented API, no migration. We confirm your file formats in discovery.
What the connector does NOT do
- It does NOT replace RIB iTWO. It only connects on top.
- It does NOT touch sensitive data without your approval.
- It does NOT migrate your data to another system (migration is Tier 3).
RIB iTWO API: can you connect AI?
RIB iTWO has no open API today, so we connect via scheduled export/import. The AI works on top of that data without touching RIB iTWO. We confirm the real path in discovery.
Are you the maker of RIB iTWO?
We build RIB iTWO's official API and MCP server in weeks, under your brand or white-label, so AI agents can recommend and use your product before they can only do it with your competitors'.
How we work with vendorsCloud connection with RIB iTWO
RIB iTWO lives on-premise/desktop, so the cloud connection runs through a local agent that bridges it to the cloud securely. You don't migrate to the cloud — we bring the AI to where your data already is.
RIB iTWO + ChatGPT, Claude, Gemini, Perplexity, Codex & MCP
Each AI tool does something different around RIB iTWO: ChatGPT (OpenAI) and Gemini (Google) draft and summarise text, Claude AI (Anthropic) reasons over complex cases, Perplexity searches and verifies facts on the fly, and Codex or GitHub Copilot help write the connector code. None of them, on their own, acts on your data — they don't read a contact, book an appointment or chase an invoice. EBROTECH builds the connector with Claude Code and OpenAI models, exposed as an MCP server where it fits, so those AI agents do act on top of RIB iTWO, safely and with your approval.
How to connect RIB iTWO with AI in 3 steps?
- 1
15-minute discovery
We confirm your GAEB file formats (D81/D83/D84) and which tender and chasing workflows to trigger first.
- 2
Connect the connector
We bridge iTWO via GAEB file export: we parse the export, trigger the AI workflow and feed structured data back, no API and no migration.
- 3
Automations live
Tender follow-up, client chasing and voice AI run by themselves on top, driven by each new GAEB export, iTWO untouched.
When NOT to connect with RIB iTWO?
If your tool is a modern construction platform with a real API (such as Procore), see that profile, since a direct API link is simpler there. This profile is for German/Austrian construction software bridged via GAEB.
Frequently asked questions about RIB iTWO
Does RIB iTWO have an API?
Not an open public one for third parties. That is why most agencies cannot integrate it. We bridge it honestly through the GAEB file format it already uses, which is the working route.
Do I have to migrate off RIB iTWO?
No. That is the whole point. iTWO stays exactly as it is. We bridge it via GAEB file exchange on top.
What is GAEB?
GAEB is the standard German construction data-exchange format (D81/D83/D84 files) for tenders and bills of quantities. iTWO already imports and exports it, so we use it as the honest bridge instead of pretending an API exists.
Is this secure without an API?
Yes. The GAEB bridge works with the files iTWO already produces, processed in a controlled environment you define. We scope exactly where files are read and written in discovery.
Keep exploring
Do you use RIB iTWO?
We'll tell you which AI automations make sense for your case and how long setup takes — without changing your software.